Invoice Validation & Controls is where ERP discipline either begins or breaks.
Duplicate Invoice Detection and Prevention looks operational from far away. In a real finance team, it is a chain of assertions: the right actor started the work, the required records existed, the control policy was applied, the state change was preserved, and the outcome can be explained later without rebuilding the transaction from emails and spreadsheets.
The expected business outcome is specific: Duplicate payment rate ≤ 0.01 % of total invoice volume; duplicate detection runs on 100 % of incoming invoices before any payment is authorized.
The control flow a finance team actually needs.
Step 1
Exact Duplicate Check On
Step 2
Fuzzy Duplicate Check On Returning...
Step 3
Block Exact Duplicates Automatically
Step 4
Present Fuzzy Candidates With...
Step 5
Override Requires Reason Code And...
The ERP surface involved.
Module
Invoice Validation & Controls
Actors
AP Automation System, AP Clerk, AP Manager
Tier
Tier 1
Finance area
Accounts Payable & Procure-to-Pay
Region lens
US and UK finance teams
Publication date
March 11, 2026
Exact duplicate check on (entity_id, vendor_id, invoice_number); fuzzy duplicate check on (vendor_id, invoice_date ± 7 days, total_amount ± 1 %) returning ranked candidates; block exact duplicates automatically; present fuzzy candidates with similarity score for human decision; override requires reason code and manager approval for invoices above $1 k configurable; voided invoice numbers permanently blocked for reuse by same vendor; duplicate checks execute ≤ 500 ms; false-positive rate on fuzzy match ≤ 5 %; all detections logged with match criteria and actor decision.
US and UK teams have different compliance hooks, but the same control problem.
US teams usually care about clean evidence for audit support, vendor records, payment controls, tax reporting, and management review. UK teams usually care about VAT-ready records, approval evidence, digital-record discipline, and traceable postings. The country-specific details differ, but the operating pattern is the same: the ERP needs controlled records, explicit ownership, defensible state changes, and evidence that survives beyond the person who completed the task.
The control matrix.
| Control area | Requirement | Acceptance proof |
|---|---|---|
| Control 1 | Exact duplicate check on (entity_id, vendor_id, invoice_number | Given a vendor invoice with a specific vendor_id and invoice_number already exists |
| Control 2 | fuzzy duplicate check on (vendor_id, invoice_date ± 7 days, total_amount ± 1 %) returning ranked candidates | when a new invoice is submitted with the same vendor_id and invoice_number |
| Control 3 | block exact duplicates automatically | then the system returns 409 with error code DUPLICATE_INVOICE and blocks record creation |
| Control 4 | present fuzzy candidates with similarity score for human decision | negative) when a fuzzy-match candidate is presented and the AP clerk overrides without a reason code then 422 with error code REASON_CODE_REQUIRED is returned. |
| Control 5 | override requires reason code and manager approval for invoices above $1 k configurable | Duplicate payment rate ≤ 0.01 % of total invoice volume; duplicate detection runs on 100 % of incoming invoices before any payment is authorized. |
| Control 6 | voided invoice numbers permanently blocked for reuse by same vendor | Duplicate payment rate ≤ 0.01 % of total invoice volume; duplicate detection runs on 100 % of incoming invoices before any payment is authorized. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | When a new invoice is submitted for processing, the system checks for duplicates before creating a record. It searches existing invoices for the same vendor and invoice number, and also runs fuzzy matching on (vendor, amount, date) to catch duplicate invoices with altered numbers. A confidence-scored duplicate candidate list is presented to the AP clerk. The clerk confirms whether the new invoice is a true duplicate (reject and archive) or a legitimate separate invoice (override with reason code). All duplicate detections and overrides are logged. Prevention rules also block re-submission of a voided invoice number by the same vendor. |
| Control rules | Exact duplicate check on (entity_id, vendor_id, invoice_number); fuzzy duplicate check on (vendor_id, invoice_date ± 7 days, total_amount ± 1 %) returning ranked candidates; block exact duplicates automatically; present fuzzy candidates with similarity score for human decision; override requires reason code and manager approval for invoices above $1 k configurable; voided invoice numbers permanently blocked for reuse by same vendor; duplicate checks execute ≤ 500 ms; false-positive rate on fuzzy match ≤ 5 %; all detections logged with match criteria and actor decision. |
| Acceptance proof | Given a vendor invoice with a specific vendor_id and invoice_number already exists; when a new invoice is submitted with the same vendor_id and invoice_number; then the system returns 409 with error code DUPLICATE_INVOICE and blocks record creation; (negative) when a fuzzy-match candidate is presented and the AP clerk overrides without a reason code then 422 with error code REASON_CODE_REQUIRED is returned. |
| Data record | |
| System event | |
| Lifecycle state | |
The useful version of this workflow is not only fast. It is inspectable. A controller, auditor, or operator should be able to move from source event to system record to state transition to final business outcome without guessing.
Implementation contracts.
Reference data model
`invoices` { id, vendor_id, invoice_number, invoice_date, total_amount_minor, currency_code, status, external_id }; `duplicate_detection_log` { id, new_invoice_ref, candidate_invoice_id, match_type: enum(EXACT|FUZZY), similarity_score: decimal, resolution: enum(CONFIRMED_DUPLICATE|OVERRIDE), resolver_id, reason_code, timestamp_utc }; (reference, product may differ).API and events
`POST /v1/invoices/duplicate-check` { vendor_id, invoice_number, invoice_date, total_amount_minor } -> 200 { exact_duplicate: bool, fuzzy_candidates: [{invoice_id, similarity_score}] }; `POST /v1/invoices/{id}/duplicate-override` { reason_code } -> 200; emits `ap.duplicate.detected` and `ap.duplicate.overridden` events; idempotent via `external_id` on invoice creation.State transitions
`PENDING_DUPLICATE_CHECK -> CLEAR -> STAGED`; branch `PENDING_DUPLICATE_CHECK -> EXACT_DUPLICATE_BLOCKED` (terminal for that submission); branch `PENDING_DUPLICATE_CHECK -> FUZZY_CANDIDATE -> (OVERRIDE_APPROVED | CONFIRMED_DUPLICATE)`; guard: EXACT duplicate is a hard block with no override path.Common implementation traps.
Treating the workflow as data entry
If the ERP only stores the final record, the team loses the decision trail that explains how the record became valid.
Hiding exception logic
Exceptions need owners, reason codes, and time stamps. A vague pending state is not a control.
Posting without recovery design
Retries, duplicate submissions, and partial failures must be explicit so the system does not create inconsistent records.
Skipping evidence design
A workflow that cannot produce evidence on demand will eventually push finance teams back into manual screenshots and spreadsheets.
Where Rivane fits.
Rivane is built for finance workflows where automation must stay tied to source documents, approvals, state transitions, ledger impact, reporting, and audit evidence. Use this guide as a checklist for evaluating whether an ERP workflow is merely digitized or actually controlled.
References and source basis.
These sources provide the standards, regulatory, or government context around the flow. They are included so the guide is useful to finance operators, auditors, and implementation teams, not only buyers reading software copy.