<media type="image" src="…"/>
as a child of <hero>, switching this page to the
full-bleed dark variant.
Recommended : 1920 × 1080 px (16:9)
Formats : PNG · JPEG · WebP · SVG
Off-spec uploads are rejected — aspect ratio outside 16:9 ±2 %, dimensions outside 800 × 450 … 3840 × 2160.
PO, receipt and invoice reconciled by the engine — before the payment queue.
The match runs automatically across quantity, price, currency and tax. Within-tolerance auto-clears; out-of-tolerance routes to the operational owner with the discrepancy named, not to a payables queue with the invoice held.
Engine, not policy
The match is performed by the engine the moment the invoice posts — not by a clerk reading paper documents.
Tolerance configuration
Per-category tolerances on quantity, price, currency and tax. Within tolerance auto-clears; out of tolerance routes.
Operational routing
Discrepancies route to the buyer (price), the receiver (quantity) or the controller (tax) — not held in a finance queue.
Audit trail
Every match decision recorded with the user, the timestamp and the supporting documents. Reversals create new decisions; originals are preserved.
What the matching engine covers
Quantity tolerance
Per-category quantity tolerances, absolute and percentage. Receipt of 100.5 against a PO of 100 within 1% tolerance auto-clears; outside tolerance routes to the receiver.
Price tolerance
Per-category price tolerances. Invoice price against PO price within tolerance auto-clears; outside tolerance routes to the buyer for confirmation against the framework contract or RFQ.
Currency and FX
Multi-currency invoice against multi-currency PO with rate handling per the operational regime — historical PO rate, current invoice rate, or contract-fixed rate.
Tax reconciliation
VAT / IVA / IGV applied at the line level; mismatches against the PO routed to the tax controller; reverse-charge and intra-EU acquisitions handled by configuration.
Document linkage
Goods-receipt note, supplier invoice (PDF or e-invoice), PO history and approval chain all linked from the match decision.
Exception management
Out-of-tolerance items live in a routed queue with named operational owners. Ageing against SLA, escalation rules and resolution-time analytics.
Why match-as-engine changes the payables team
In a policy-driven match, the payables team reads invoices and chases discrepancies. The team's day is structured around exceptions: invoices held, queries open, follow-ups overdue. The closing of a month is a sprint to clear backlog.
In an engine-driven match, the team's day is structured around resolution. Within-tolerance cases never reach them; out-of-tolerance cases arrive in their queue already routed to the operational owner who can fix them. The payables team becomes a control function — verifying that the engine routed correctly — not a backlog-processing function.