Run the scanner to see queue counts and top reasons.
Drop in AP CSVs. Get a duplicate-payment risk queue in minutes.
Start with the fake sample, or drag in a current payment-run CSV plus optional paid history and vendor aliases. The scanner maps common AP fields, builds HOLD / REVIEW / CLEAR, and enables downloadable CSV and HTML reports.
Inputs are parsed in this static page. No ERP login, bank connection, account login, or cloud upload is needed for the scanner workflow. Use fake or redacted rows first.
- Blocked API attempts
- 0
- Storage writes
- 0
- Runtime
- Static file
1. Current payment run
Required. Include vendor/payee, invoice number, amount, date, and any payment id or status columns you have.
2. Paid history
Optional. Paid invoices make the historical paid comparison rule useful.
3. Vendor aliases
Optional. Two columns are enough: alias, canonical_vendor.
Pause before payment.
Needs AP confirmation.
No duplicate-payment risk found.
Run the scanner to enable CSV and HTML reports.
Detected field mapping
No input scanned yet.
| 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.