BILL (formerly Bill.com) is an accounts-payable automation platform. Bills are captured into it, routed for approval, paid through it, and synced back to an accounting system, and a duplicate warning is one control inside that ongoing workflow. It is a process: adopting it changes how your payables run, month after month.
This page is not a process and does not want to be. It answers one retrospective question about payments you have already made: did any of these go out twice — read from a CSV export in your browser, with nothing uploaded, nothing migrated, and nothing to subscribe to.
| Question | Where to answer it |
|---|---|
| How do I stop a duplicate bill being entered and approved in the first place? | An AP automation platform like BILL — preventive controls inside the entry and approval workflow are the thing it is for. |
| Did we already pay any vendor twice, in payments made before today? | This tool — export your payment history as CSV, get a reviewed list of candidate pairs in seconds. |
| Can I check that without migrating our AP process or buying seats? | This tool — a static page, no account, no sync, no subscription, no data leaves the browser. |
| Who routes approvals, schedules the payment, and syncs it to the ledger? | An AP automation platform — this tool does none of that and takes no action on your behalf. |
| Is this flagged pair actually a duplicate, or is it our monthly rent? | This tool's confidence tiers — the same-amount/near-date tier is labelled “review” and says outright that recurring charges match it too. |
| Our finance data cannot be uploaded to a third party. Can we still check? | This tool — the CSV is read in your browser and never sent anywhere; nothing is stored server-side. |
No account and nothing installed: it is a static page, the parsing and matching run in your browser, and your vendor names, amounts, dates, and the file itself stay on this device — nothing is uploaded anywhere.
They operate at different scopes. BILL is an accounts-payable automation platform: bills are captured into it, routed for approval, paid through it, and synced back to an accounting system, and duplicate warnings are one control inside that ongoing workflow. Adopting it means moving how your AP process runs. This page does not run your AP process and never will. It reads one CSV export of payments you have already made, in your browser, and returns a short reviewed list of likely double payments with the reason each pair matched. If your AP already runs on a platform, this is a second opinion over its output; if it does not, this is a check you can do this afternoon without changing anything.
Yes, and that is the specific gap this page exists to close. Platform duplicate warnings are preventive: they fire while a bill is being entered, inside the system the bill was entered into. That does nothing about payments already made, payments made outside the platform, or the period before you adopted one. A CSV export of payment history is something almost every accounting system can produce, and checking it needs no migration, no subscription, and no per-user seats — you export, you check, you keep the review list.
Sometimes, because it looks at a different thing. A preventive control compares a bill being entered against bills already in that system. This runs four retrospective checks across the whole export at once: the same vendor and invoice number paid twice for the same amount, the same vendor and invoice number paid twice at different amounts, the same vendor and amount under invoice numbers that are a likely typo of each other, and the same vendor and amount landing within a date window you set. The last tier is labelled “review” rather than “duplicate”, because rent, subscriptions, and retainers match that pattern by design. Nothing here proves a payment was duplicated — it produces candidates for you to verify against your vendor statements.
No. This site is not affiliated with, endorsed by, or sponsored by BILL (formerly Bill.com), and this page is not a review of it. BILL is a trademark of its owner, named here only to describe the category of software this tool is and is not. Platform pricing, plans, and feature sets change; check BILL's own site for its current terms rather than relying on any description here.
Also: matching processor payouts to bank deposits instead? The payment reconciliation workbench matches Stripe/Square/PayPal payouts to bank deposits — nothing uploaded there either.