AI Invoice Reconciliation & 3-Way Matching Software for ERP
Data Alchemy automates invoice reconciliation by matching every supplier invoice against the corresponding purchase order and delivery note (DDT). The platform extracts line-level data, performs three-way matching, validates the values against your ERP master data and posts the result into SAP, Zucchetti or TeamSystem — 99.8% accuracy, 3 seconds per document, no templates.
From raw invoices to reconciled ERP entries
Invoice reconciliation is the most time-consuming control in accounts payable: matching every supplier invoice with the corresponding purchase order and delivery note (DDT). Data Alchemy assigns the best LLM to each document model — today Claude AI, which outperformed GPT, Gemma and DeepSeek in our tests — to read each document, extract line items and align them by SKU, quantity and price. The reconciled entry is validated against ERP master data and posted automatically, so your finance team stops re-keying invoices and reviews only genuine exceptions. Automating accounts payable means extending this control across the whole flow, from purchase order to payment.
Everything you need to reconcile invoices automatically
Line-level AI extraction
A dedicated LLM reads every invoice, purchase order and delivery note and extracts line items (item, quantity, unit of measure, price) with no templates, at 99.8% accuracy.
Automatic three-way matching
Each invoice line is aligned with the matching purchase-order line and goods-received line by SKU, quantity, unit of measure and price. Discrepancies surface before posting.
ERP master-data validation
Suppliers, items, price lists and payment terms are checked in real time against SAP, Zucchetti or TeamSystem. Clean matches flow straight through.
Duplicate and anomaly detection
The AI compares each incoming invoice with the history of posted documents, blocking duplicates, double submissions and tampered totals before payment is approved.
Email-first acquisition
Connect Google Workspace or Microsoft 365 and the platform pulls invoices, POs and DDTs from supplier mailboxes, filters out spam and queues only relevant documents.
Pay-per-use pricing
From €0.50/document on Starter to €0.35/document on Corporate, billed on actual processed volume. No subscription, no minimum, no hidden setup fees.
This is PO matching performed at line level, not a check on document totals: discrepancies in unit price, delivered quantity — as recorded on the delivery note or goods received note (GRN) — or item code surface before the entry reaches the ERP, so the invoice approval workflow only ever sees the lines that genuinely need a human decision.
Four steps from inbox to reconciled ERP entry
1. Capture
Invoices, purchase orders and delivery notes are captured from email, scanners or upload — PDF, XML, FatturaPA and international formats.
2. Extract with the LLM
Data Alchemy assigns the best LLM per document model — today Claude AI — and extracts structured line-level data in under 3 seconds.
3. Three-way match
Each invoice line is matched with the corresponding PO and DDT line by SKU, quantity, unit of measure and price.
4. Validate and post
Reconciled data is validated against SAP, Zucchetti or TeamSystem master data and posted into the ERP via native connector or REST API.
Two-way, three-way and four-way matching: which control you need
Not every invoice needs the same level of verification. Data Alchemy automatically applies the right control based on the documents available in your management system.
Two-way matching
Compares the supplier invoice against the purchase order alone, checking SKU, ordered quantity and agreed price. It is the typical control for services and supplies with no physical delivery of goods, where no delivery note exists.
Three-way matching
Adds the delivery note: the invoice is compared with the purchase order and with the goods actually received on the DDT. It is the accounts-payable standard for goods and materials, because it is the only control that stops you paying for quantities never delivered.
Four-way matching
Also brings in the inspection report or quality acceptance record: you pay only for what was ordered, delivered and formally accepted. It is the control required in manufacturing and in purchases of plant and critical components.
Data Alchemy handles all three scenarios on the same platform: the LLM classifies incoming documents, recognises which ones are available for each order line and triggers the applicable matching level, with no separate configuration per purchase type.
Once the match clears, a second layer of verification remains on the payable cycle — duplicates, altered IBANs, amounts outside tolerance, suppliers not on file: see document anomaly control.
What happens when the three documents do not match
A real accounts-payable cycle never matches at 100%. The validation rules, configured with you during onboarding, decide line by line what passes automatically and what stops for human review.
Price tolerance
Accept a deviation from the order price within a threshold you define, as a percentage or an absolute value. Anything outside the range is flagged before posting.
Quantity tolerance
Handle over- and under-deliveries by absolute quantity or percentage, and let the platform decide whether to accept, partially match or hold the line.
Partial and split deliveries
One purchase order can be closed by several delivery notes, and one invoice can cover several DDTs. Data Alchemy reconstructs the many-to-many link between order lines, delivered quantities and invoiced quantities instead of forcing a one-to-one document match.
Ancillary charges
Transport, packaging, surcharges and rounding present on the invoice but not on the order are recognised and routed to the correct accounting rule rather than treated as a mismatch.
Exception routing
Every line that fails the check is queued to the responsible reviewer — buyer, warehouse or accounting — with the three source documents side by side, so the exception is resolved by reading rather than rebuilt from scratch.
The discrepancies three-way matching catches
Three-way matching compares three documents — supplier invoice, purchase order and delivery note (DDT) — before approving payment. Data Alchemy automatically surfaces the deviations that would otherwise require manual checks.
Price mismatch
The invoice price does not match the agreed order price or price list: the exception is flagged before posting.
Under-delivered quantity
The invoiced quantity exceeds what was actually received on the DDT: the line stays on hold until verified.
Duplicate invoice
Same supplier, same number or amount already posted: the system blocks the double payment.
Off-catalogue item
An item code missing from the ERP master data is highlighted for coding or approval.
Built for finance, logistics and procurement teams
Accounts payable automation
The end-to-end order-DDT-invoice process: from reconciliation to posting, with the ROI for the finance team.
Learn more →Finance & APAP automation by department
Reconcile supplier invoices with POs and DDTs, validate against the ERP and post entries with no manual re-keying.
Learn more →GPT reconciliationGPT invoice reconciliation
See the LLM-powered angle: how a dedicated GPT-class model per document drives zero-template 3-way matching.
Learn more →IDP PlatformFull IDP solution
Beyond invoices: orders, contracts, price lists and bank statements processed by the same AI platform.
Learn more →Frequently asked questions about invoice reconciliation
What is automated invoice reconciliation?
Automated invoice reconciliation uses artificial intelligence to read supplier invoices, match each line against the corresponding purchase order and delivery note (DDT), and post the result into the ERP. Data Alchemy assigns a dedicated LLM to each document model — today Claude AI — reaching 99.8% extraction accuracy and 3-second processing per document, without templates.
What is three-way matching (invoice-order-DDT)?
Three-way matching is the standard accounts-payable control that compares three documents — supplier invoice, purchase order and delivery note (DDT) — before approving payment. Data Alchemy automates this control: the LLM extracts line items from each document, the platform aligns them by SKU, quantity and price, and the system flags discrepancies (price mismatch, missing goods, duplicate invoice) before the entry hits the ERP.
How is it different from traditional OCR reconciliation?
Traditional OCR converts pixels into text but cannot decide whether an invoice line belongs to a specific purchase order or whether quantities match the delivery note. An LLM-powered reconciliation engine understands document semantics: it identifies suppliers, items, units of measure and prices, then performs three-way matching against the ERP master data. The result is structured, validated and ready to post — no human re-keying required.
Does it integrate with SAP, Zucchetti and TeamSystem?
Yes. Reconciled invoices flow directly into SAP, Zucchetti, TeamSystem and other ERPs through native connectors, REST APIs, webhooks and direct SQL access. Master data (suppliers, items, price lists) is read from the ERP in real time so the AI can validate against the system of record on every document.
Which invoice formats does the platform handle?
The platform processes PDF, XML, FatturaPA and international electronic invoice formats, as well as scanned paper invoices. It also ingests purchase orders and delivery notes from email (Google Workspace, Microsoft 365), scanners or upload, classifying each document automatically before reconciliation.
How much does AI invoice reconciliation cost?
Data Alchemy uses a transparent pay-per-use model: from €0.50/document on the Starter plan down to €0.35/document on the Corporate plan. No monthly subscription, no minimum commitment — you pay only for invoices the AI actually reconciles and posts to your ERP.
See invoice reconciliation in action
Book a free 30-minute demo on your real invoices. We run the AI live, show the three-way match against your POs and DDTs and calculate your ROI — no commitment, no cost.
Book a free demo