Three-way match compares the purchase order, the goods receipt and the vendor invoice before payment. Nexus anchors every invoice to a purchase order line, scores the match across twelve dimensions — vendor identity, amount, date, PO number, line items, tax, currency, payment terms and more — and reports each variance at the line, with the documents that produced it. Approved invoices are written back to Oracle or SAP as validated AP vouchers.
None of these is exotic. They are ordinary invoices that a busy team waves through because checking each line by hand takes longer than paying it.
The invoice bills 1,200 units. The receipt shows 1,140. Unless someone compares the lines, the missing 60 are paid for.
The PO says $18.40 a unit. The invoice says $19.10. Across a year of invoices from one vendor, that difference is real money.
The same invoice arrives twice — once by email, once through the portal — or is re-sent with a new number. Duplicates are checked on content, not just on the invoice number.
A plausible vendor name, a plausible amount, and no purchase order behind it. Nexus will not accept a document that cannot be traced to a PO line.
Payment terms or tax treatment on the invoice differ from the PO and the contract, and nobody notices until the payment run.
A mismatch is flagged, sits in a shared queue, and ages. Every break in Nexus gets an owner, a deadline and an escalation path.
Not a pass/fail flag. A named variance at the line, with the documents that produced it and the person who owns it.
Price and quantity differences isolated to the line that caused them, not reported against the whole document.
Content hash and fuzzy similarity, run before the invoice reaches the payment run rather than after.
Each exception is categorised, given a financial exposure, assigned to a role and tracked until it is closed.
Approved invoices published as validated AP vouchers into Oracle or SAP, with rollback if the write fails.
No. Nexus takes invoices from the channels you already use — email, EDI 810, supplier portals and cloud storage — and normalises them into one queue.
Per client, at deployment. A vendor scorecard can drive auto-approval thresholds, so a vendor with a clean history clears faster than one with a record of variances.
Only the uncertain fields are routed for review, and nothing is written to your system of record on a guess. Every automated decision is logged with the model version that made it and can be reversed.
No. Nexus sits on top of Oracle, SAP, NetSuite and the other systems you already run, reads from them and writes validated records back.
How the reconciliation engine works end to end, from intake to close.
Carrier and terminal charges checked against the contract and the physical record.
The source channels, the EDI sets, and how write-back works.
Bring one month of purchase orders, receipts and invoices. We will show you every break, and who should own it.
7-day free trial · Card required before the trial ends · No migration