AP Reconciler Paid Diagnostic v1
AP-067 sample package explorer
Buyer-facing, no-upload and no-submit sample package explorer for understanding what a future redacted AP diagnostic package would contain. It uses AP-063 synthetic/redacted fixtures only and performs no external action.
What this helps a buyer understand
Required files, optional files, accepted columns, provenance fields, freshness fields, redaction requirements, hard-stop exclusions, and which AP-064/AP-065 diagnostic outputs each file supports.
Open AP-068 public buyer evaluation cockpit | Open buyer readiness checklist
Package file map
| file_name | required | accepted_columns | provenance_fields | freshness_fields | diagnostic_outputs_supported | sample_template |
|---|---|---|---|---|---|---|
| invoices-redacted.csv | True | invoice_id, vendor_label, invoice_date, due_date, amount, currency, po_id, receipt_id, status, source_ref, freshness_label, redaction_status, synthetic_marker | source_ref, provenance, synthetic_marker | freshness_label, source_date_or_period, period_covered | invoice support checks, invoice-without-statement support, duplicate-risk, amount mismatch, source refs in AP-064/AP-065 | AP-067-sample-templates/invoices-template.csv |
| vendor-statements-redacted.csv | True | statement_id, vendor_label, statement_date, line_item_reference, invoice_reference, amount, currency, aging_bucket, source_ref, freshness_label, redaction_status, synthetic_marker | source_ref, provenance, synthetic_marker | freshness_label, source_date_or_period, period_covered | statement item without invoice, unmatched statement item, amount mismatch, stale/open aging discrepancy, exception summary in AP-064/AP-065 | AP-067-sample-templates/vendor-statements-template.csv |
| vendor-master-redacted.csv | True | vendor_id, vendor_label, master_data_date, payment_method_label_redacted, source_ref, freshness_label, redaction_status, synthetic_marker | source_ref, provenance, synthetic_marker | freshness_label, source_date_or_period, period_covered | vendor master mismatch, payment/status boundary review, hard-stop context in AP-064/AP-065 | AP-067-sample-templates/vendor-master-template.csv |
| purchase-orders-redacted.csv | False | po_id, vendor_label, po_date, expected_amount, currency, receipt_reference, source_ref, freshness_label, redaction_status, synthetic_marker | source_ref, provenance, synthetic_marker | freshness_label, source_date_or_period, period_covered | purchase order or receipt mismatch, amount/context support in AP-064/AP-065 | AP-067-sample-templates/purchase-orders-template.csv |
| receipts-redacted.csv | False | receipt_id, po_id, vendor_label, receipt_date, received_amount, source_ref, freshness_label, redaction_status, synthetic_marker | source_ref, provenance, synthetic_marker | freshness_label, source_date_or_period, period_covered | purchase order or receipt mismatch and owner-review routing in AP-064/AP-065 | AP-067-sample-templates/receipts-template.csv |
| payments-status-redacted.csv | False | payment_ref_id, vendor_label, invoice_reference, amount, currency, status_label, sensitive_payment_data_removed, source_ref, freshness_label, redaction_status, synthetic_marker | source_ref, provenance, synthetic_marker | freshness_label, source_date_or_period, period_covered | paid/open status contradiction and hard-stop-sensitive payment/status reference handling in AP-064/AP-065 | AP-067-sample-templates/payments-status-template.csv |
Sample templates for buyer inspection
Manifest template and CSV template artifacts are synthetic/redacted templates only, not real customer data.
What happens next product path
AP-063 contract -> AP-064 deterministic diagnostic -> AP-065 interactive workbench/export -> AP-066 evaluation room/validation instrument.
AP-068 public buyer evaluation cockpit | AP-063 contract | AP-064 deterministic diagnostic | AP-065 interactive workbench/export | AP-066 evaluation room/validation instrument
No-upload / no-submit / no-contact / no-payment boundary
No upload fields, no forms that submit, no contact controls, no booking buttons, no payment links, no pricing or quote authority, no checkout or invoice language, and no live/private-data instructions. Closed DA gates remain closed.
Hard-stop exclusions: no live/private data; no bank details, account identifiers, credentials, tokens, API keys, or logins; no payment instructions or route details; no invoice approval/rejection or pay/do-not-pay decisions; no ERP/writeback or system-of-record posting/sync/update; no legal/tax/accounting/procurement/payment guidance; no contact, booking, quote, pricing, checkout, invoice, payment route, outreach, or customer delivery action.
Closed DA gates
| gate | status | later_scope |
|---|---|---|
| lead_sourcing_DA | closed | identify or inspect source/lead lists only after Janez approval |
| outreach_DA | closed | send approved outreach or demo invitations only after Janez approval |
| quote_DA | closed | present commercial terms only after Janez approval |
| payment_ask_DA | closed | ask a qualified buyer for payment only after Janez approval |
| payment_route_DA | closed | create or present a payment route only after Janez approval |
| delivery_DA | closed | accept customer materials or deliver a customer diagnostic only after Janez approval |
| live_data_DA | closed | evaluate any live/private/customer/provider data path only after Janez approval |
AIOS2 reusable capability notes
- Generic package explorer, sample template pack, and readiness checklist patterns may belong in AIOS2 later.
- AP-specific file semantics, AP exception support, AP redaction requirements, and AP buyer readiness prompts stay in AP Reconciler.
Revenue truth
0 EUR until verified Stripe/bank funds. Checklist completion, template views, and package-readiness claims are not customer evidence, WTP proof, delivery, or payment evidence.