[Blog]()AI invoice review # Reading invoices with AI: fields, differences and review before posting Reading a total is not enough to post an invoice. Retain each field's origin and decide which differences require review. **[Jonathan Perez]()**Co-founder · Design, product and sales October 8, 2026 · 7 min read **Short answer** Use AI to propose invoice fields and retain the document needed to review them. Before posting, check identity, currency, components, totals and duplicates under your rules. Ambiguous cases need a pending state and owner; repeating extraction or posting must not create another payable. ## Test worksheet: Invoice AI: extraction, review and posting Reading a total is not enough to post an invoice. Retain each field's origin and decide which differences require review. Record inputs, expected outcome, evidence, owner and observed result. [Download CSV worksheet]() In this guide - [Define the data your process needs]() - [Fictional example: a 1,180 total with a missing component]() - [Test difficult documents and the destination step]() - [Confidence helps prioritize rather than decide alone]() - [Accept a complete flow for one document type]() ## Define the data your process needs A service company may record project expenses; a factory may link invoices to orders and receipts. One PDF can need different rules. Define required fields, format, source and destination. A read invoice is not yet authorized for posting or payment, and extraction does not replace tax or accounting review. [Microsoft Document Intelligence]() documents extracted invoice values and line items. [Google Document AI]() shows structured entities, normalized values and confidence in its response. These are reviewable model outputs, rather than guarantees that your identity, arithmetic or authorization is correct. ## Fictional example: a 1,180 total with a missing component Rehearsal invoice F-801 shows a 1,000 MXN subtotal, 160 tax and an additional 20 charge, totaling 1,180. Initial extraction returns subtotal and tax but misses the charge. The recovered components total 1,160, leaving a difference of 20. This synthetic calculation neither defines tax treatment of the charge nor represents customer savings. The case remains pending even if the extracted total has high confidence. The reviewer locates the charge, confirms its classification under the business rule and records the correction. Keep the initial extraction and decision. If currency is shown only as “$,” do not automatically assume MXN: verify authorized context or request review. | Field or relationship |Check |If unclear | | --- | --- | --- | | Supplier and identifier |Matches an authorized entity |Review before creating another supplier | | Currency and amounts |Components and total follow agreed rules |Do not guess currency or component | | Document and origin |File, pages and version remain locatable |Stop if evidence is missing | | Order and receipt |Relationship and quantity when required |Hold for purchasing owner | ## Test difficult documents and the destination step Include text PDFs, blurry scans, multiple pages and documents that are not invoices. Use authorized anonymized material; review access and handling scope before sending real documents to a provider. Keep extractor version and rehearsal rules. Results may vary by format, language and configuration. | Case |Expected result |Evidence | | --- | --- | --- | | F-801 misses the 20 charge |Pending difference; inconsistent total not posted |Document and proposed fields | | Currency appears only as $ |Review without unauthorized automatic inference |Passage and decision | | Supplier absent from catalog |Pending before creating an entity |Identity and checked catalog | | Same document arrives by email and folder |One business case with both origins |Key and references | | Posting fails before confirmation |Queryable pending or unknown state |Request and response | | Retry an applied posting |Same payable without duplication |Destination reference | ## Confidence helps prioritize rather than decide alone Agree which fields can be accepted under testable rules and which always need review. High confidence can accompany an incorrect reading; use it within criteria validated on your documents rather than as universal authorization. Separate reading errors, arithmetic differences and missing approval because they need different responses. The review queue should show doubtful field, original passage, proposal and owner. A human correction retains actor and change. Reprocessing the same file must not overwrite that decision without a rule. If the original changes, retain a new version and compare again rather than replacing earlier evidence. ## Accept a complete flow for one document type Start with bounded invoice formats and one destination. Verify extraction, review and posting before expanding suppliers or formats. Connect the pilot with [AI ROI](), [change auditing]() and [webhooks and retries]() when destination confirmation is deferred. The downloadable worksheet proposes ten cases with observed results empty. Bring anonymized invoices in different formats, approval rules and the destination reference field to a [free consultation]() for [AI for business](). We can review a useful extraction rehearsal and where it must pause for review. ## Review an invoice and its exceptions Compare authorized formats with the fields and calculations your posting needs. In a free consultation, identify which difference requires review and which reference identifies an existing invoice before repeating the send. - Authorized anonymized invoices in different formats - Required fields, arithmetic rules and approvals - Destination and reference used to recognize an existing posting [Book a free consultation]()[Ask on WhatsApp]() Related - [AI for business]() - [Process automation]() ## Frequently asked questions ### Can AI authorize payment? Extracting data and authorizing payment are separate tasks. Define approval permission, criteria and owner independently. This rehearsal covers review and posting under your process; it does not assume automatic payment authorization. ### What identifies a duplicate? Agree a document and destination key including issuer and relevant references. A filename is insufficient, and invoice numbers may repeat across suppliers. Test different intake channels and keep a review path for uncertain matches. ### Does a reconciled total establish invoice validity? It establishes only the arithmetic check performed. Identity, currency, components, authorization and tax or accounting review need their own criteria. A correct sum does not constitute complete document acceptance. ### Should every field share a confidence threshold? Do not assume so. A contact phone and invoice total can have different consequences. Set field-specific criteria and test representative formats. Retain errors and pending cases to review the rule. ## Sources 1. [Invoice data extraction]()Microsoft 2. [Handle processing response]()Google Cloud Last updated: October 8, 2026 ## Keep reading [Document AI evaluationOct 8, 2026 ### An AI assistant for your documents: test questions and limits]()[AIOct 2, 2026 ### AI ROI: how to tell if AI is actually making your business money]()[ProductionOct 8, 2026 ### Purchase orders: approvals, changes and verifiable receiving]() --- Canonical: https://nightlysoftware.com/en/blog/invoice-ai-human-review Updated: 2026-10-08 Description: Check amounts, currency, supplier and duplicates before posting an AI-read invoice. Includes a worksheet for human review and safe retries.