OCR to ledger: VAT coding, reversals and your own workbook

The document-intelligence engine behind scans now has a name: AVERQIS AI. Underneath it still runs on best-in-class cloud document AI; in your guides and workspace it is simply AVERQIS doing what it does.

Scans now follow an accountant's route into the books. Approve the extraction, then code it: a UK VAT scheme code (S20 through PEX, OUT), a chart-of-accounts GL code, the tax point and payment due date — credit notes must reference the invoice they correct. Everything is re-checked at posting: VAT must equal net times the code rate to the penny, only GBP posts, and a duplicate invoice number from the same supplier is rejected rather than quietly doubled.

Posted documents are permanent. Correcting one means reversing it: a mirrored entry is added, the audit trail stays intact and the document reopens for a fresh post. Fully coded postings also create a balanced double-entry journal — expense debit, VAT control, creditors credit — ready for approval and export to your accounting platform.

The client VAT return is now computed from those codes: standard and reduced-rate output to box 1, reclaimable input to box 4, zero-rated, exempt and out-of-scope values to boxes 6 and 7, with credit notes subtracting automatically. Anything still uncoded is flagged so you can finish the paperwork before filing.

Exports level up too: batch workbooks take a document-date period, every row carries an evidence link back to the original scan, and each generated file is recorded with its row count, period and SHA-256 checksum — the exact file you sent a client can be proven later. The headline addition is the accountant template workbook: upload your own master file once, and each export fills its Transactions sheet — formulas, charts and validation intact, recalculated the moment Excel opens it.

Guides for every step live in the support hub: search 'coding and posting' or 'accountant workbook'. Questions? We would rather you asked — contact support from inside the app.