Read-back verification
Short answer: Read-back verification reads every replacement in the new file again after saving, to check that what was actually written is what should have been written. It checks the output, not the process.
Why it is needed
Recognition can misread characters, and replacements are affected by fonts and layout. Looking only at a preview makes it easy to miss problems. Read-back changes the question from “what did I intend to change” to “what does the file actually say”.
Rules
- Amounts, dates and reference numbers are compared strictly, and a second recognition model must give the same result.
- Thai digits are treated as equivalent to Arabic digits, and thousands separators are optional.
- For Devanagari and Kannada, you can install a read-back pack as a second recognizer. (The current version does not yet support searching or replacing Arabic text, so the Arabic pack is not used for now.)
Results
The “Read-back” column in the results list shows ”✓ Passed / Needs review / ✕ Failed”, and the results are written to the operation record (manifest.json). In command-line mode, the exit code is 3 when problems are found.