Most invoices are not the problem. The ones that become exceptions — partial deliveries, price variances, duplicates under another supplier name — are where your team actually goes, and no e-invoicing mandate anywhere touches them.
In your words rather than ours. If three of these are true, we have built for your situation before.
Every competitor on this search sells invoice recognition. In much of the world that problem has a legislated end date, and in several countries it has already passed. Verified August 2026.
| Where | Model | Status |
|---|---|---|
| Mainland China | Clearance | Fully digitalised e-fapiao nationwide since Dec 2024; the new VAT Law from Jan 2026 makes it the legal invoice format. Golden Tax Phase IV monitors invoices against contracts, payments and logistics records. |
| Hong Kong | None possible | No VAT, no GST — so no mandate can exist. E-invoices need only the counterparty's consent; B2G runs through the government portal. |
| UAE | Post-audit | Above AED 50m turnover: accredited provider by 30 Oct 2026, live 1 Jan 2027. Below: live 1 July 2027. Government 1 Oct 2027. |
| Saudi Arabia | Clearance | ZATCA wave 25 — threshold halved to SAR 187,500, integration by 1 Feb 2027. Effectively the whole business population. |
| Malaysia | Clearance | Mandatory since 1 Jan 2026 above RM 1m; penalties from Jan 2027. Invoices validated by LHDN before they are valid. |
| Singapore | Post-audit | InvoiceNow for new voluntary GST registrants since 1 Apr 2026. Existing registrants phased through to 2031. |
| Poland | Clearance | KSeF mandatory Feb 2026 above PLN 200m, Apr 2026 for all other B2B. |
| France | Post-audit | All must receive from 1 Sept 2026; large and intermediate must issue. SMEs issue from Sept 2027. |
| Germany | Post-audit | Receiving since Jan 2025. Issuing from Jan 2027 above €800k, Jan 2028 below. |
| United States | None | No federal mandate. PDFs by email remain normal indefinitely. |
Two incompatible architectures sit in that table. Under clearance the invoice passes through a tax authority and does not legally exist until approved — a third party on the critical path of your billing, with its uptime and its rejection codes. Under post-audit it goes straight to the buyer and reporting happens separately.
Look at the first two rows. Mainland China runs one of the most complete regimes on earth; Hong Kong has no VAT, so no mandate can exist. Forty minutes apart, and we operate on both sides of it — which is why we treat the mixed estate as the permanent state rather than a migration, and build for it.
Nobody trading across borders gets one format this decade. Full map, both models and the sources →
We turn down more AP automation than this market does, and the first reason is one no competitor will raise with you.
Scoped against what survives the map above, in descending order of what it is worth. Note the third column — no competitor on this search has one.
| First | Second | Not at all |
|---|---|---|
| Three-way matching, exception triage and resolution, the mixed estate of formats | Approval routing, supplier-behaviour anomaly detection, cross-border document sets | Plain PDF recognition where a structured format arrives inside your payback period |
The third column is not modesty. It is the single largest line item most vendors would happily sell you, and in several jurisdictions on the map above it is money you would not get back.
Partial deliveries, price and quantity variances inside and outside tolerance, currency differences, duplicates under a slightly different supplier name — triaged, explained and routed to the person who can resolve them, with the evidence attached.
This is where the hours are, and it is untouched by every mandate on the map.
Invoice against purchase order against goods receipt. Deterministic where the criterion is arithmetic — tolerance, tax, currency, duplicates — and a model only on the residue, such as whether two differently worded line descriptions mean the same item.
Reasoning, not reading. A perfectly structured invoice makes it no easier.
Structured invoices from the UAE, Malaysia and the EU arriving alongside PDFs from every country without a mandate — two input paths, one normalised representation, one set of approval rules. Templates on your high-volume suppliers, models only on the tail.
Built as permanent, because the timetables run to 2028, 2031 and never.
Invoice against packing list against bill of lading against certificate of origin and export licence — quantities, descriptions, HS codes, consignee, incoterms. A mismatch here does not produce an accounting correction; it holds a shipment or fails a letter-of-credit presentation.
No mandate anywhere addresses this. The set has to agree with itself, and no mandate timetable checks that.
Client names withheld under NDA. The closest thing we have shipped is the same mechanic under a different rulebook — a document pack checked against a regulation, with the machine annotating and a specialist signing.
The same mechanic applied to maintenance packages: classify each page into six document types, detect missing signatures and stamps, find unfilled checklist cells, verify date-and-signature pairing, and return an annotated report before a specialist signs off. Cross-document agreement, machine-checked, human-approved. Read the case →
The pipeline can run on-premises or air-gapped on open-weight models — no invoice, contract or shipping document leaves your network — with the GPU hardware quoted in the same contract. Details in security and compliance and private AI infrastructure.
Tolerances, tax and currency handling implemented as versioned deterministic rules rather than learned from history, so the same invoice produces the same decision permanently — and an auditor can be shown why, not told that a model thought so.
Fixed price against a scope agreed before the build starts, and a scope that excludes anything a mandate is about to make redundant. No time and materials, no discovery that bills indefinitely.
Scope first, price second, and both numbers are published. The specification is a product: the AI Solution Blueprint, one system, 5–6 weeks, from $30,000, credited in full against the build if implementation starts within 90 days. It measures your current exception rate, checks the mandate dates across your supplier footprint, and returns a routing design, a fixed price and a timeline. Builds of this kind typically start around $150,000 over 4–6 months.
Yes, but not the extraction part. Check the dates first: if your suppliers go structured inside your payback period, an extraction component never earns out and we will tell you to skip it. What the mandates do not touch is matching, exceptions and running structured and unstructured invoices side by side — and that mixed state is permanent, not transitional, because the timetables run to 2028 in Germany, 2031 in Singapore and never in the United States.
Not measurably. Matching an invoice against a purchase order and a goods receipt is a reasoning problem about three documents that disagree; the format of one of them was never the obstacle. The same applies to exceptions — partial deliveries, price and quantity variances, duplicates under a slightly different supplier name. This is the work, and it is untouched by any mandate anywhere.
Most of the volume. Quantity and price within tolerance, tax and currency arithmetic, duplicate detection on number and supplier are all deterministic — and better done that way, because the result must be identical every time and explainable to an auditor. Models earn their place on the residue: whether two differently worded line descriptions mean the same item, or which partial delivery a short invoice belongs to.
Yes, and it is the part we know from operating rather than from reading. A shipment generates an invoice, packing list, bill of lading, certificate of origin and often an export licence, and they must agree with each other on quantities, descriptions, HS codes and consignee. A mismatch does not produce an accounting correction, it produces a held shipment or a rejected letter-of-credit presentation.
Yes. The pipeline can run on-premises or air-gapped on open-weight models, with no invoice or contract leaving your network, and the GPU hardware quoted in the same contract. For finance functions with data-residency constraints this is usually the only configuration that clears review.
The full map, clearance versus post-audit, and the matching tasks that need a model.
Read →Counterparty screening at procurement volume, including export control.
Explore →Choosing a capture method per document type — the framework this page applies to invoices.
Explore →The wider IDP practice across any document-heavy process.
Explore →An engineer replies, not an account manager. You get back an exception profile and a fixed price.
Want the spec first? AI Solution Blueprint — from $30,000, credited against the build.