AP Reconciler Paid Diagnostic v1
Sample Diagnostic Report
AP-057 buyer-grade sample diagnostic report. Static/redacted/synthetic local/static synthetic report artifact for buyer-readiness review, not customer delivery.
Executive summary
This static/redacted/synthetic sample report shows how AP Reconciler Paid Diagnostic v1 packages messy AP evidence into a buyer-readable Exception Evidence Pack: exception family summary, source references, confidence/freshness/provenance labels, owner-review routing, hard stops, and next evidence needed. It is a local/static synthetic report artifact and is not customer delivery.
Scope and inputs
- Synthetic/redacted invoices, vendor statement lines, purchase orders, receipts, ledger/AP aging, safe payment/export references, and vendor master boundary items.
- No live/private/customer/accounting/bank/payment/provider data is used.
- Payment references are evidence labels only; payment instructions, bank details, credentials, and route data are hard-stopped.
Exception categories
- missing invoice
- unmatched vendor statement item
- duplicate-risk, not confirmed duplicate
- purchase-order/receipt mismatch
- amount mismatch
- stale/aging discrepancy
- vendor master mismatch
- payment-instruction hard stop
- owner-review required
- no exceptions detected in provided evidence
Source/provenance/freshness/confidence
Source/provenance/freshness/confidence labels show where each finding came from, how current the evidence is, and how bounded the diagnostic confidence is.
| Source ID | Type | Reference | Provenance | Freshness | Confidence |
|---|---|---|---|---|---|
| SRC-INV-001 | invoice | fixtures/ap-030/demo-invoice-redacted | static/redacted demo input | demo_current | high |
| SRC-STMT-001 | vendor_statement | fixtures/ap-030/demo-vendor-statement-redacted | static/redacted demo input | demo_current | high |
| SRC-PO-001 | purchase_order | fixtures/ap-030/demo-po-synthetic | synthetic demo input | demo_current | medium |
| SRC-RCPT-001 | receipt | fixtures/ap-030/demo-receipt-synthetic | synthetic demo input | demo_current | medium |
| SRC-PAY-001 | payment_export_reference | fixtures/ap-030/demo-payment-reference-placeholder | synthetic boundary fixture | demo_current | low |
| SRC-APEXP-001 | accounting_export | fixtures/ap-030/demo-accounting-export-redacted | static/redacted demo input | demo_current | medium |
Fact / inference / customer-decision-required
Fact / inference / customer-decision-required labels separate what appears directly in provided evidence from derived risk signals and items that require customer owner judgment.
Directly present in provided static/redacted evidence.
Derived match/mismatch/risk signal with confidence limits.
Needs internal owner judgment; not an approval, payment action, advice, or final reconciliation decision.
Exception detail examples
| ID | Family | Label | Finding | Source refs | Confidence | Freshness | Next evidence needed |
|---|---|---|---|---|---|---|---|
| EX-AP002-POS-STMT-001 | statement_missing_invoice | Inference | Vendor statement references an invoice not present in provided invoice evidence. | fixtures/ap-002/statement-missing-invoice-positive.json#AP002-POS-STMT-001 | medium | static_2026-06-24 | Static/redacted invoice copy or AP export row for the referenced invoice. |
| EX-AP003-SYNTH_VENDOR_DUP_A | possible_duplicate_invoice | Inference | Two invoice-like records look similar enough to require duplicate-risk review. | fixtures/ap-003/duplicate-invoice-positive.json#AP003-POS-INV-001 | fixtures/ap-003/duplicate-invoice-positive.json#AP003-POS-INV-002 | medium | static_2026-06-24 | Internal AP owner review of original invoice references and policy context. |
| EX-AP004A-AP004A-POS-INV-001 | po_receipt_mismatch | Inference | Invoice evidence does not align cleanly with provided purchase order and receipt references. | fixtures/ap-004a/po-receipt-mismatch-positive.json#AP004A-POS-INV-001 | fixtures/ap-004a/po-receipt-mismatch-positive.json#AP004A-POS-PO-001 | fixtures/ap-004a/po-receipt-mismatch-positive.json#AP004A-POS-RCPT-001 | medium | static_2026-06-24 | Updated PO/receipt reference or receiving note. |
| EX-AP004B-AP004B-POS-INV-001 | amount_mismatch | Inference | Amounts differ across provided invoice and purchase order evidence. | fixtures/ap-004b/amount-mismatch-positive.json#AP004B-POS-INV-001 | fixtures/ap-004b/amount-mismatch-positive.json#AP004B-POS-PO-001 | medium | static_2026-06-24 | Redacted source document clarifying amount basis, credit note, or receipt quantity. |
| EX-AP005-AGING-001 | stale_aging_discrepancy | Inference | Aging and statement freshness labels indicate stale or conflicting evidence. | fixtures/ap-005/aging-discrepancy-positive.json#AP005-AGING-STMT-001 | medium | stale | Updated vendor statement or current AP aging export. |
| EX-AP006-VMM-001 | vendor_master_mismatch | Inference | Vendor alias/master-data fields conflict across provided sources. | fixtures/ap-006/vendor-master-mismatch-positive.json#AP006-VMM-INV-001 | fixtures/ap-006/vendor-master-mismatch-positive.json#AP006-VMM-MASTER-001 | medium | static_2026-06-24 | Redacted vendor master reference or internal owner confirmation. |
| HS-AP006-PAY-001 | payment_instruction_hard_stop | Customer-decision-required | Payment-instruction ambiguity appears in provided placeholder evidence. | fixtures/ap-006/payment-placeholder-hard-stop-positive.json#AP006-PAY-HS-001 | high | static_2026-06-24 | Remove payment instruction ambiguity and provide non-payment evidence only. |
Next evidence needed
- Static/redacted invoice support for missing statement references.
- Updated PO, receipt, or goods-received evidence when source amounts or references conflict.
- Current vendor statement or AP aging export when evidence is stale.
- Internal AP owner review when the row is decision-sensitive, low-confidence, conflicting, or payment-sensitive.
Hard stops
- HS_PAYMENT_INSTRUCTION_DRIFT: AP Reconciler does not process payment instructions, bank details, payment routes, invoice approval/rejection, ERP/accounting writeback, or payment advice. Next step: Remove payment-sensitive content and provide static/redacted non-payment evidence.
Limitations and no-authority boundary
- This sample diagnostic is not accounting, tax, procurement, legal, or payment advice.
- It does not approve/reject invoices.
- It does not issue payment instructions.
- It does not write back to ERP/accounting systems.
- It does not claim full reconciliation or final truth.
- Owner review is required before any operational decision.
Service-burden estimate
Sample scope: single synthetic/redacted diagnostic pack. Expected operator time: 60-180 minutes for a bounded repeatable diagnostic after intake is clean. Service-burden estimate is internal delivery planning, not billing authority, customer evidence, payment evidence, or final truth.
What a paid diagnostic would deliver
- Buyer-readable exception-family summary and source inventory.
- Row-level exception detail with source refs, provenance, freshness, confidence, and redaction labels.
- Fact / inference / customer-decision-required labels for each finding.
- Owner-review routing and next-evidence-needed list.
- Hard-stop register for payment/advice/writeback/live-data boundary issues.
- Limitations/no-authority statement and local HTML/JSON/CSV export artifacts.
Local/static synthetic report artifact downloads
Download/export buttons on this page only reference local/static synthetic report artifacts. No live data, no payment route, no customer send, no provider/accounting connection, and no writeback.
Revenue truth
0 EUR until verified Stripe/bank funds; sample report is not customer evidence, WTP evidence, payment evidence, or revenue.