By process · Matching
Three documents, one balance to reconcile.
Purchase order, delivery note and invoice live in different departments — often still as PDFs. LOCRAI extracts aligned fields (quantities, prices, codes, references) so your ERP can match or flag only exceptions, instead of someone typing everything by hand.
The problem
Where matching breaks down.
- 01Line-by-line comparisons in Excel at month-end.
- 02Scanned delivery notes with incomplete or unreadable PO references.
- 03Invoices arriving days later with no clear link to receipt.
- 04Quantity and price errors discovered only at payment or reconciliation.
How LOCRAI helps
Comparable data, not just archived files.
- 01
Same schema across three documents
PO, delivery note and invoice extracted with homogeneous fields: supplier, lines, quantities, prices, references.
- 02
SKU matching on every line
Supplier code → internal SKU on all three documents, for consistent ERP comparisons.
- 03
Automatic checks
Total mismatches, VAT ID, IBAN, duplicates and plausible dates flagged before import.
- 04
Export to your matching engine
Webhooks and API deliver structured data to the ERP that runs three-way matching or highlights exceptions.
- Documents in the flow
- Purchase orders · Delivery notes · Supplier invoices · Credit notes · Order confirmations · Generic documents
The flow
From three PDFs to match-ready data.
- 01
Intake PO, DN, invoice
Upload, email, API or FTP: all three documents enter the same extraction engine.
- 02
Aligned extraction
Lines, quantities, prices and PO references extracted with a consistent schema across types.
- 03
SKU matching and verification
Supplier codes → internal SKUs; automatic checks on totals and tax anomalies.
- 04
Exception review
Documents below threshold or with obvious discrepancies in a human queue, with audit trail.
- 05
Delivery to ERP
CSV, JSON, XML or webhook: ERP runs three-way matching or flags only what doesn't add up.
Questions about matching
No. LOCRAI structures PO, delivery note and invoice into comparable data with aligned SKUs. Operational matching — quantities, prices, approvals — runs in your ERP or flags exceptions.
You can start with one (often delivery notes or invoices) and expand. What matters is consistent extracted fields, not per-supplier templates.
Pick a high-volume supplier, connect export or webhooks to the flow where you already match (or want to), measure exceptions and minutes per document.
See matching on your documents.
Show us real PO, delivery note and invoice from the same flow: we'll show comparable fields.
