Stateful three-way matching · live product

Deliveries change.
The match remembers.

Keep purchase orders, partial receipts, cumulative invoices and corrections in one running balance. See what is supported, what is still missing and what remains on the order before the next accounting step.

PO-5086 · final balance

380received & invoiced
0unsupported units
120PO units not yet invoiced

Those 120 open PO units have no receipt support yet.

Match passed · approval still required

Direct answer

How does stateful three-way matching handle changing deliveries?

AIdaptIQ maintains the cumulative relationship between a purchase order, goods receipts and invoices across partial deliveries, repeated invoices and corrections. New evidence changes the balance while prior evidence and the required approval remain attached. Configure the integration and purchasing controls for your rollout.

One commitment · many events

Every new receipt changes the same balance.

PO-5086 receipt timeline. Select an event to see how the balance changes.

  1. Received 0Invoiced 0Unsupported 0
  2. Received 180Invoiced 0Unsupported 0
  3. Received 300Invoiced 0Unsupported 0
  4. Received 300Invoiced 180Unsupported 0
  5. Received 300Invoiced 380Unsupported 80
  6. Received 380Invoiced 380Unsupported 0

From purchase intent to accounting outcome

Keep the operating path complete.

  1. 01

    Purchase order and receipt

    Establish the commitment and accumulate delivery evidence, including partials and reversals.

  2. 02

    Invoice and cumulative match

    Count the current claim and all prior invoicing. Evaluate quantity, value and applicable tolerances.

  3. 03

    Resolve and approve

    Route missing evidence or a permitted policy decision to its owner. Apply required authority after controls are satisfied.

  4. 04

    Record and retain the response

    Keep the accounting system’s accepted result or returned failure. Record reported payment state without moving funds.

PO-4101 · receipt correction

The next invoice cannot forget the previous one.

Receipts300 + 150 − 20
= 430

Received units after the correction

Invoices250 + 200
= 450

Cumulative billed units

Zero quantity tolerance

20 units
unsupported.

Keep the original receipts, reversal and prior invoice. Resolve the 20-unit gap before the permitted approval and accounting action.

Watch the animated explanation A correction changes the next invoice’s balance.

Animated workflow explanation.

What changes when evidence returns?

Re-check the balance. Keep approval explicit.

In scenario A, GRN-5140 adds the missing 80 units. The 380 invoiced units are now matched. The remaining 120 PO units stay open, with no additional received units available for another bill.

The next step is the configured approval, then a controlled accounting handoff. A match is evidence; it is not permission to bypass authority.

Matched quantity
380 units
PO quantity not yet invoiced
120 units
Supported quantity available
0 units
Next control
Required approval

Fit to your workflow

Use the PO path where it belongs.

Does this apply to non-PO invoices?

No purchase order should be required when the client’s policy permits non-PO spending. Non-PO invoices use the relevant business-purpose, coding, evidence and approval checks.

Does matching cover partial deliveries and repeated invoices?

Yes. AIdaptIQ carries partial receipts, cumulative invoicing and corrections into the next match instead of comparing only one isolated set of documents.

How are tolerances applied?

Evaluate quantity and value variances under the applicable purchasing and approval controls for the rollout. A tolerance does not silently replace the designated approval.

Next step

Use one difficult P2P transaction.

Bring a partial receipt, cumulative invoice or correction scenario.

Request the diagnostic→