INV-000004
- Supplier
- Litware, Inc.
- Line
- 54
- Quantity
- 11
- Unit price
- £81.00
The invoice asks for payment, but the purchase order and warehouse receipt must agree before the reviewer can release it.
The report is generated from executed DuckDB views and retained reviewer records. It is not Power BI, a live Accounts Payable system or evidence that payment was made.
Accounts Payable decision
The reviewer sees what the supplier billed, what the buyer approved and what the warehouse accepted. A difference becomes a named question, not an unexplained status.
| Compared field | Supplier invoice | Approved order | Accepted receipt | Result |
|---|---|---|---|---|
| Quantity | 11 | 11 | 11 | Agree |
| Unit price | £81.00 | £75.00 | Not recorded | Price exception |
| Tax | £178.20 | £178.20 | Not applicable | Agree |
Procurement supplied an approved price-change record; the original price exception remains recoverable. The build records permission to enter a separate payment process; it does not make payment.
One controlled review route
Extraction, matching and the reviewer decision remain separate records. A passed rule or approved exception never overwrites the supplier's original value.
Minimum confidence 0.9900. One low-confidence field in the full population is withheld from matching.
four-way comparison records price difference under MATCH-1.0.0.
The retained rule register reports 0 failed fixtures, including exact, tolerance, receipt, tax, currency, unit-conversion and rule-version cases.
INV-000011 remains with the supplier master-data approver for £23,843.
Confirm whether the purchase-order price was formally changed before this invoice can proceed.
MANUALLY_ACCEPTED_EXCEPTION; 12 trace events remain inspectable and failed or errored retests released 0 invoices.
Whole review population
Received invoices first split into exact matches, approved tolerances or questions. Every question then ends as a continuing hold, a supplier return or a documented exception.
96.7% of held value is attached to missing warehouse receipts.
Reviewer report
This is native evidence for the contained SQL and Python build. It is deliberately not described as Power BI, Power Platform or a live Accounts Payable service.
outputs/reviewer-report/index.htmlwarehouse/supplier-invoice-review.duckdbsql/60_reporting.sqlOpen reviewer questions
The queue age is measured from the unanswered reviewer question to the reporting cut-off. It is not mixed with completed processing time.
| Invoice | Supplier | Held value | Reason | Owner | Next action |
|---|---|---|---|---|---|
| INV-002073 | Fabrikam, Inc. | £1,956,607 | Missing Receipt | Warehouse receiving lead | QUERY |
| INV-002074 | Litware, Inc. | £889,666 | Missing Receipt | Warehouse receiving lead | QUERY |
| INV-000005 | Northwind Electric Cars | £42,096 | Quantity Difference | Warehouse receiving lead | QUERY |
| INV-000011 | The Phone Company | £23,843 | Bank Detail Changed | Supplier master-data approver | HOLD |
| INV-000007 | Fabrikam, Inc. | £11,721 | Currency Difference | Accounts Payable reviewer | QUERY |
| INV-000012 | Fabrikam, Inc. | £7,994 | Low Confidence Extraction | Accounts Payable control owner | QUERY |
| INV-000006 | The Phone Company | £6,595 | Tax Difference | Accounts Payable reviewer | QUERY |
| INV-000003 | Graphic Design Institute | £3,289 | Invoice Before Receipt | Warehouse receiving lead | QUERY |
One invoice, retained history
The buyer's response does not erase the price difference. The independent rematch retains both records before the reviewer approves the exception.
Accounts Payable retained the arrived document and checksum.
supplier-invoices/INV-000004.jsonPredicted document fields remain separate from the matching result and reviewer decision.
Minimum confidence 0.9900The invoice supplier was matched to the retained supplier record.
Litware, Inc.The invoice references the approved purchase order and affected line.
Order 4The supplier charged more than the approved order-line price.
Invoice GBP 81.000000 / order GBP 75.00All receipts for the order line were combined before the quantity comparison.
1 receipt(s), 11.00 accepted outersThe effective price tolerance was applied and the original exception was retained.
PRICE_DIFFERENCE under MATCH-1.0.0Accounts Payable sent the exact price mismatch to the procurement buyer.
Confirm whether the purchase-order price was formally changed before this invoice can proceed.Buyer supplied the approved price-change record without replacing the original order comparison.
approved-price-exception-PO-4Independent rematch retained the price difference and attached the approved procurement exception.
MANUALLY_ACCEPTED_EXCEPTIONProcurement supplied an approved price-change record; the original price exception remains recoverable.
MANUALLY_ACCEPT_EXCEPTIONThe reviewer approved the invoice for the separate authorised process; no payment was executed by this build.
APPROVED_FOR_AUTHORISED_PAYMENT_PROCESSMonitoring and release boundary
Every retained invoice enters one review case.
Bad field records remain inspectable and do not disappear.
Each invoice receives one initial result under a versioned rule.
Questions name the person and record needed to resolve the mismatch.
Retests retain failed and errored attempts as well as the accepted exception.
The original price difference remains visible beside the approved exception.
A failed or errored retest cannot release an invoice.
The build records a review decision only; payment remains outside scope.
Microsoft Wide World Importers purchasing records, dated 2013-01-03 to 2016-06-09.
2,075 invoice headers and 8,371 invoice lines rebuilt under dataset 1.0.0.
Run status PASS with idempotency key supplier-invoice-workflow-1.0.0-450031; the verifier compares two consecutive material-output builds.
8,303 workflow events retain the questions, responses, rematches and decisions checked in the clean rebuild.
The rebuild instruction, SQL, test output and repeatability hashes are retained with the technical evidence. The reporting cut-off is 2026-07-31 14:00:00 UTC.
What the evidence proves
Built by Quanta Meridian using non-client example data. No confidential or protected data is used.
What it does not prove
Invoice, receipt, prediction and reviewer records are deterministic non-client data and do not describe the performance of a real wholesaler. The contained workflow does not prove production access control, enterprise monitoring, a live finance-system connection or operational adoption. No OCR or machine-learning service runs in this build; document-field predictions are retained test records. The build records approval for a separate authorised payment process but never executes payment. This project does not contain a Power BI report or Power Platform solution and makes no claim that either platform was used.
Bring one disputed invoice
Next step
Start with the files, joins and checks that make the current reporting route difficult to trust or maintain.