BY NUMBER7 AIOpen AIdaptIQ ↗Book a demo →Stateful three-way matching · live product
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 & invoicedThose 120 open PO units have no receipt support yet.
Match passed · approval still requiredDirect answer
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
PO-5086 receipt timeline. Select an event to see how the balance changes.
From purchase intent to accounting outcome
Establish the commitment and accumulate delivery evidence, including partials and reversals.
Count the current claim and all prior invoicing. Evaluate quantity, value and applicable tolerances.
Route missing evidence or a permitted policy decision to its owner. Apply required authority after controls are satisfied.
Keep the accounting system’s accepted result or returned failure. Record reported payment state without moving funds.
PO-4101 · receipt correction
Received units after the correction
Cumulative billed units
Zero quantity tolerance
20 unitsKeep the original receipts, reversal and prior invoice. Resolve the 20-unit gap before the permitted approval and accounting action.
What changes when evidence returns?
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.
Fit to your workflow
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.
Yes. AIdaptIQ carries partial receipts, cumulative invoicing and corrections into the next match instead of comparing only one isolated set of documents.
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
Bring a partial receipt, cumulative invoice or correction scenario.
Different purchase-order workflows
Supplier PO / receipt / invoice matching verifies what your business owes. Customer PO intake reads the orders your customers send to you.
Explore customer PO data entry and SKU mappingScope and action
Maintains cumulative purchase-order, receipt and invoice state across partial receipts, cumulative invoices and corrections, with the applicable matching and approval controls.
Action: Approval required.
Read the workflow scopeThe JSK case documents customer-PO intake, structured order lines and SKU mapping. Agree the downstream order-system handoff separately.
Action: Automatic with review.
Read the workflow scopeRecording or reconciling payment status does not execute a payment or move funds. Confirm the configured status source.
Action: Records state only.
Read the workflow scopeThis website does not offer execution or movement of money as part of payment status recording.
Action: Not supported.
Read the workflow scopeThe recorded product-owner confirmation applies to the named capabilities. Deployment scope, integration permissions and approval requirements are agreed separately.