Invoice evidence
Supplier, invoice number, line description, quantity, unit price, tax, total and referenced PO.
PO · GRN · invoice
Three-way matching that explains every exception.
NexumFlow compares invoice lines with purchase-order and goods-receipt data, applies your tolerances, blocks or routes mismatches and preserves the evidence used for approval.
Line-level matchingConfigurable tolerancesPartial receiptsManual reviewERP-aware
The decision
Was it ordered, received and invoiced correctly?
A green match should be based on all three records—not merely a PO number found in the document.
Purchase-order evidence
Ordered item or service, price, quantity, UOM, vendor, entity, open balance and commercial terms.
Receipt evidence
Posted goods or service receipt, accepted quantity, receipt status, reversals, returns and available billable quantity.
Matching workflow
Deterministic controls, assisted resolution.
Identify the intended PO lines
Use PO references, item identifiers, descriptions and commercial context to propose invoice-to-PO line assignments.
Load current receipt state
Retrieve the relevant ERP goods or service receipts and consider quantities already billed.
Apply tolerances and business rules
Check price, quantity, amount, tax and receipt requirements using tenant-specific thresholds.
Block or route the mismatch
Invoices outside the policy remain visible with the exact reason and are sent to an authorized reviewer.
Revalidate before final approval
Refresh critical receipt and billed-quantity conditions so an earlier match does not approve stale information.
Exception clarity
Show what failed—not just “no match.”
| Exception | Control | Typical next action |
|---|---|---|
| Invoice quantity exceeds receipt | Compare current received and billed-to-date quantities | Wait for receipt, correct the invoice or authorize an exception |
| Price outside tolerance | Compare invoice unit price with the PO and allowed variance | Seek procurement confirmation or supplier credit |
| Receipt reversed or returned | Exclude unavailable receipt quantity | Hold until ERP state is corrected |
| UOM differs | Apply configured conversion only when authoritative mapping exists | Confirm conversion or reassign the line |
| Service invoice | Use approved service-entry or equivalent receipt evidence | Route to the service owner if evidence is incomplete |
Questions
Three-way matching, answered.
Can a user manually match an invoice line?
Yes, where policy allows it. Manual assignment should still run the same receipt and tolerance validations and should record who made the change.
What about multiple receipts for one PO line?
The matcher can aggregate eligible receipt quantities while respecting reversals, returns and quantities already consumed by prior bills.
Does a match automatically approve an invoice?
Not necessarily. A successful match removes one class of exception; the invoice must still satisfy tax, duplicate, business-rule and approval requirements.
Test the edge cases, not only perfect PO invoices.
Bring partial receipts, returns, quantity mismatches and difficult line descriptions. Those are the transactions that reveal whether a matching product is production-ready.