Run the scanner to see queue counts and top reasons.
View the sample report first. Then run a local AP CSV check.
Start with the public demo-data report, then load the demo sample or choose local CSVs in this browser. The scanner maps common AP fields, builds HOLD / REVIEW / CLEAR, adds explainable local review signals, and enables downloadable CSV and HTML reports without Python or cloud upload.
Local-first boundary
CSV scan is designed to run in this browser
Inputs are parsed in this static page. No ERP login, bank connection, account login, or cloud upload is needed for the scanner workflow. Use demo or redacted rows first.
- Blocked API attempts
- 0
- Storage writes
- 0
- Runtime
- Static file
Non-technical buyer path
1. View public sample report
2. Download free proof pack
3. Preview setup only if mapping is unclear
CSV-first and local-first.
Export spreadsheet tabs to CSV, then paste, click-select, or drag the CSV here. The demo is a static browser workflow; start with demo or redacted data before private AP files.
Fastest proof path: sample report -> demo sample -> queue
Inspect the public demo-data report first, then load bundled demo CSVs and run the scanner. No account, ERP login, bank connection, cloud upload, or Python step is needed.
1Load demo sample or drag CSV
2Generate HOLD / REVIEW / CLEAR
3Download CSV or HTML report
Header-only first step
Paste export headers before sharing any AP rows.
Check which duplicate-payment rules can run from column names alone. This is designed for QuickBooks, Xero, BILL, ERP, bank, or spreadsheet exports when you are not ready to paste private payment data.
Paste headers to see ready, partial, and blocked rules.
1. Current payment run
Required. Include vendor/payee, invoice number, amount, date, and any payment id or status columns you have.
Required input for the scan.
2. Paid history
Optional. Paid invoices make the historical paid comparison rule useful.
Optional, but improves already-paid checks.
3. Vendor aliases
Optional. Two columns are enough: alias, canonical_vendor.
Optional two-column alias map.
Waiting for demo sample or current payment-run CSV.
Pause before payment.
Needs AP confirmation.
No duplicate-payment risk found.
Recommended buyer action
Run the demo sample first.
The scanner will recommend free proof pack, USD49 self-serve bundle, USD149 setup, or do not buy yet.
No AP export has been scanned yet.
Run the scanner to enable CSV and HTML reports.
Detected field mapping
No input scanned yet.
Export Evidence Passport
Need mapping help?
Field fit, rule readiness, and local signals before any setup call.
Use this section to decide whether your AP export is ready for a first-run review. It stays local and does not change the HOLD / REVIEW / CLEAR queue.
Load demo samples or a local CSV to see source confidence.
Mapped fields and weak headers will appear here.
Ready and blocked checks are summarized here.
Local signals are review aids only; they do not change queue decisions.
Buyer decision
Run scanner first.
The scanner will recommend whether to use the free proof path, the self-serve bundle, or the first-run setup service.
Why this recommendation
Next steps
Profile evidence
Top local signals
When setup is the better path
Example: mapping unclear -> use USD149 setup before self-service.
If your export only has weak labels like `Name`, `Ref`, `Total`, or is missing invoice/date/payment references, the Passport should not push you straight to the bundle.
2/6 checks readyvendor + amount detected, invoice/date/payment id unclear
3 fields need reviewheader meaning should be confirmed before relying on the queue
Recommended actionsend headers, demo rows, or redacted rows for first-run setup
| Queue | Score | Vendor / Payee | Invoice | Amount | Date | Status | Reason |
|---|---|---|---|---|---|---|---|
| Run the scanner to build a review queue. | |||||||
Run the scanner to build a review queue.
Rules included in this demo
Same normalized vendor, same raw invoice value, and same amount inside the current run.
Same vendor and amount after removing invoice punctuation, spaces, and case differences.
Same vendor and amount within a configurable date window even when invoice numbers differ.
Identical payment run row signature appears more than once.
Current run item matches optional paid history by invoice or near-date payment evidence.
Flags likely aliases and buyer-provided alias mappings that need AP review.