AP Reconciler Paid Diagnostic v1
AP-064 concise sample report for Controller / AP Manager / CFO inspection
This buyer-facing sample report shows how the deterministic local reconciliation runner turns the AP-063 synthetic redacted package into source-backed AP exceptions and evidence ledger entries. Open AP-068 public buyer evaluation cockpit, open AP-066 customer evaluation room, open AP-067 sample package explorer, or open AP-065 interactive buyer diagnostic workbench.
Executive diagnostic summary
The runner found statement support gaps, invoice support gaps, possible duplicate invoice evidence, amount mismatch evidence, vendor master mismatch evidence, purchase order or receipt mismatch evidence, stale/open aging discrepancy evidence, paid/open status contradiction evidence, and hard-stop excluded content. These are diagnostic evidence findings, not final accounting decisions.
What the report uses
Static synthetic/redacted AP package inputs only: manifest, invoices, vendor statements, vendor master, purchase orders, receipts, and status-label export. No live/private data dependency.
Exception detail examples
| category | severity | source_refs | source_freshness | confidence | label | summary | owner_review_note | next_evidence_needed |
|---|---|---|---|---|---|---|---|---|
| schema_validation | info | manifest.json#files | package_contract | high | Fact | AP-063 manifest and fixture CSV schemas parsed successfully as static synthetic/redacted package evidence. | No customer decision is implied by schema validation alone. | None for the synthetic package. |
| statement_item_without_invoice | high | vendor-statements-redacted.csv#LINE-001 | current_period | high | Inference | Vendor statement item references an invoice not present in the AP-063 invoice fixture. | Owner review required to decide whether more static/redacted invoice support exists. | Static/redacted invoice evidence or AP export row for the referenced invoice. |
| invoice_without_statement_support | medium | invoices-redacted.csv#INV-063-100 | current_period | medium | Inference | Invoice evidence has no matching vendor-statement support in the provided package. | Owner review required before treating this as a vendor statement gap. | Static/redacted vendor statement line or AP aging support. |
| invoice_without_statement_support | medium | invoices-redacted.csv#INV-063-100-DUP | current_period | medium | Inference | Invoice evidence has no matching vendor-statement support in the provided package. | Owner review required before treating this as a vendor statement gap. | Static/redacted vendor statement line or AP aging support. |
| possible_duplicate_invoice | high | invoices-redacted.csv#INV-063-100; invoices-redacted.csv#INV-063-100-DUP | current_period | medium | Inference | Multiple invoice-like rows share vendor alias and amount; this is possible duplicate invoice evidence, not a final duplicate conclusion. | Customer owner review required before any operational decision. | Original static/redacted invoice references or AP export context. |
| amount_mismatch | high | invoices-redacted.csv#INV-063-200; vendor-statements-redacted.csv#LINE-002; purchase-orders-redacted.csv#PO-063-200; receipts-redacted.csv#RCPT-063-200 | mixed_current_stale | high | Inference | Invoice, statement, purchase order, and receipt amounts do not fully align in the synthetic package. | Owner review required to decide whether credit, partial receipt, or source-period differences explain the mismatch. | Static/redacted credit, receipt detail, or updated statement evidence. |
| vendor_master_mismatch | medium | vendor-master-redacted.csv#VM-063-B-ALT; package-sources#vendor-alias-b | mixed_current_stale | medium | Inference | Vendor alias in transactional evidence does not align with the redacted vendor-master label set. | Customer owner review required for vendor alias/master-data interpretation. | Redacted vendor master reference or alias mapping from customer owner. |
| purchase_order_or_receipt_mismatch | medium | purchase-orders-redacted.csv#PO-063-200; receipts-redacted.csv#RCPT-063-200 | current_period | high | Inference | Purchase order expected amount and receipt amount differ in the provided synthetic evidence. | Owner review required; AP Reconciler does not decide whether receiving or invoicing is correct. | Static/redacted goods-received note, PO revision, or invoice support. |
| stale_open_aging_discrepancy | medium | vendor-statements-redacted.csv#LINE-002 | stale_review | medium | Inference | Statement aging and freshness labels indicate a stale/open review risk in the provided evidence. | Owner review required to decide whether newer evidence is needed. | Current redacted statement or AP aging extract. |
| paid_open_status_contradiction | medium | payments-status-redacted.csv#PAYSTAT-063-200; vendor-statements-redacted.csv#LINE-002 | mixed_current_stale | low | customer-decision-required | Synthetic status label evidence exists while the vendor statement still shows aged/open context; customer decision is required. | Customer owner must decide whether status timing, partial payment, or missing credit explains the contradiction. | Static/redacted status export and current vendor statement for the same period. |
| hard_stop_excluded_content | blocked | manifest.json#hard_stop_exclusions | package_contract | high | customer-decision-required | Hard-stop excluded content is refused rather than processed into normal reconciliation authority. | Remove prohibited data or keep it outside AP Reconciler before any future diagnostic. | Status labels only, with bank identifiers, route details, credentials, and private data removed. |
AIOS2 reusable capability notes
- Generic CSV/source parsing, provenance/freshness labels, evidence-ledger contracts, and no-authority guard patterns are candidates for AIOS2 reusable capabilities.
- AP-specific matching categories, vendor statement semantics, PO/receipt checks, and AP exception copy stay in the AP Reconciler product repo.
Hard-stop and no-authority boundary
Customer owner review is required for operational decisions. AP Reconciler does not approve, reject, pay, post, sync, close invoices, contact vendors, use live/private data, create routes, or provide professional finance/legal/tax/procurement guidance.
Revenue truth
0 EUR until verified Stripe/bank funds. This sample report is not payment evidence, customer evidence, WTP evidence, or revenue.