BY NUMBER7 AISTATEFUL PROCURE TO PAY · NEAR-TERM RELEASE
Keep purchase orders, receipts and invoices matched as deliveries change.
AIdaptIQ is extending its transaction model across purchase orders, partial receipts, cumulative invoices, corrections, tolerances and the accounting result.
Many documents.
One running balance.
PO 500 · open 500- Unsupported
- 0
- Open to bill
- 500
PO-1086 opens a commitment for 500 units. Nothing has been received or billed yet.
GRN-4102 and GRN-4129 accumulate to 300 received units while the purchase order remains open.
Two invoices consume 380 units. Eighty billed units still lack receipt support; 120 units remain unbilled.
GRN-4140 adds the missing 80 units. All 380 billed units now match; the remaining 120-unit commitment stays open and approval remains separate.
ONE COMMITMENT · MANY EVENTS
See the complete balance, not a one-time document comparison.
The near-term matching workflow carries every receipt and invoice forward, exposes the exact variance and leaves the unused commitment open.
Execution boundary: the match controls whether the transaction may proceed; configured approval remains separate, and the ERP retains the authoritative accounting result.
Do not make three-way matching a prerequisite for non-PO bookkeeping.
The sellable boundary includes partials, cumulative consumption, tolerances and corrections.
Non-PO processing engagements can begin without holding the workflow for this release.
DIRECT ANSWER
How will AIdaptIQ handle three-way matching as deliveries change?
The near-term stateful match will maintain the cumulative relationship between purchase orders, goods receipts and invoices across partial deliveries, repeated invoices, corrections and tolerances. Each new event changes the balance without erasing prior evidence or approval state.
THE RUNNING MATCH LEDGER
A partial receipt never resets the transaction.
The ledger retains the original commitment, every GRN, every invoice, cumulative consumption, unresolved variance and the quantity still open.
| Event | Change | Cumulative received | Cumulative invoiced | Match state |
|---|---|---|---|---|
| 01 PO-1086 | 500 ordered | 0 | 0 | Open commitment |
| 02 GRN-4102 | +180 received | 180 | 0 | 180 supported |
| 03 GRN-4129 | +120 received | 300 | 0 | 300 supported |
| 04 INV-2048 | +180 invoiced | 300 | 180 | Matched |
| 05 INV-2076 | +200 invoiced | 300 | 380 | 80 unsupported |
| 06 GRN-4140 | +80 received | 380 | 380 | Matched · 120 unbilled |
COMPLETE OPERATING PATH
From purchase intent to recorded outcome.
Nothing resets when the next document arrives.
Purchase order
Establish the commitment, line quantities and commercial terms.
Receipt
Accumulate partial deliveries, reversals and receipt evidence.
Invoice
Consume the commitment across one or many supplier claims.
Match & resolve
Evaluate cumulative quantity, value and tolerance state.
Approve
Apply configured authority after evidence is complete.
Record
Retain the accepted accounting result and payment state.
CASES STATIC MATCHING MISSES
Designed for transactions that change over time.
Partial receipts
One order fulfilled across multiple GRNs without losing the open balance.
Cumulative invoicing
Several invoices consume the same commitment without double counting.
Corrections
Reversed receipts, corrected invoices and credit notes preserve prior state.
Tolerance rules
Quantity, value and timing variances are consumed explicitly across the history.
NEW EVIDENCE REPLAYS CONTROLS
The 80-unit receipt gap closes when GRN-4140 arrives.
The match passes for 380 billed units, the remaining 120-unit commitment stays open, required approval remains explicit and the ERP stays authoritative.
EVIDENCEEmail · Upload · API
AIdaptIQState · Controls · Resolution
SYSTEM OF RECORDQuickBooks · Tally · ERP
Use one difficult P2P transaction.
Bring a partial receipt, cumulative invoice or correction scenario.