PRACTICAL IMPORT REVIEW
How to check duplicate invoices before a ledger import
A repeated invoice reference is a reason to inspect a record, not proof that a supplier has been paid twice. Before importing bills from several intake sources, compare the incoming records with relevant exported history using explicit company and vendor identifiers.
Start with the synthetic example
Open the free duplicate invoice checker and choose the flagged example. It has one historical bill and three incoming rows. The first repeats the same scoped reference and amount. The second changes the reference formatting. The third uses another vendor and is not flagged. The report shows two findings, not three duplicates.
| Incoming reference | Scope | Expected result |
|---|---|---|
| INV-101 | Same vendor, company, period, bill type, USD 123.45 (12,345 minor units) | Repeated identity: hold for review |
| inv / 101 | Same scope, date, currency and amount | Reference variant: review candidate |
| INV-101 | Different vendor | No supported flag |
Why vendor IDs and fiscal periods matter
Different suppliers can issue the same reference. A supplier can also reuse a numbering series in another financial period. Map stable IDs and the appropriate fiscal period before checking; this tool does not infer whether two supplier names identify the same legal entity. Exact references preserve leading zeroes. Formatting normalization only creates a review candidate and never merges records automatically.
Prepare the input
This is a JSON preflight, not PDF extraction or a raw spreadsheet upload. Each bill needs id, entityId, vendorId, fiscalPeriod, invoiceNumber, documentType, currency, amountMinor and billDate. Use bill or credit_note as the document type, an ISO date and integer currency minor units. Do not include bank details, contacts or credentials.
Download the complete synthetic request or try the free local n8n tutorial. The tutorial has no HTTP nodes or credentials and consumes no API requests. Local n8n import and both example outputs were verified; n8n Cloud was not tested.
Choose local or hosted checks
Use the free browser checker for a manual mapped batch that should stay on your device. For scheduled intake pipelines that need a structured response, compare the hosted API plans. BASIC has 25 requests/month free; PRO has 500 for $9/month with request hard limits. Platform bandwidth fees and terms are separate. Hosted requests transmit the JSON you send.
Route the result before a ledger write
An HTTP 200 may return hold_for_review. Inspect those findings and any truncated report before continuing. no_supported_flags means only that the documented checks found no candidate. It does not verify actual payment, taxes, bank information or the completeness of your history. The tool cannot authorize a payment, delete a bill or write to a ledger.
Read the API mapping and limits. Existing ledger duplicate controls or a free script may already meet your needs; use the hosted service only if it fits your recurring intake process.