For a bookkeeper retyping supplier invoices: get a batch into rows, with the doubtful ones listed

Count whole invoices

A tool can be 92% right per field and still get far fewer invoices right in full. In one small public test, three set-ups scored the same pooled field accuracy of 91.7% twice, yet 60% and 75% of invoices were fully right. Ask for the whole-invoice rate beside the field rate.

Keep an exceptions list

Every invoice should end up as rows or as an entry on a list with a reason. Nothing should vanish. If the files in do not equal the invoices out plus the exceptions, something was dropped.

• The number of files in equals the invoices out plus the exceptions.
• Lines plus tax equal the total, flagged when they do not.
• A missing field comes back empty, not as a plausible value.

Expect most trouble outside the reading step

One benchmark summary says most exceptions are purchase-order mismatches and vendor-master problems, not extraction. Better reading will not clear those. They need a person who knows the supplier.

Which job fits

For one batch in up to 40 layouts, the one-off job builds the reading step and tests it on 30 invoices you label and we have not seen. For every month's batch, the monthly service repeats the checks. Staff expense receipts have their own job, because they read less well and carry card digits; pairing receipts with a card statement is a separate finance job.