Implementing Duplicate Invoice Detection Workflows in Practice

Accounting practice software helps firms manage client work, but duplicate invoice detection needs to be configured at the client AP workflow level, not just at the practice management level. This tutorial covers how to implement a duplicate detection workflow in practice - specifically for clients running Xero or MYOB - including what to configure, what to monitor, and where the process needs a human checkpoint.

Why Duplicate Invoices Are More Common Than Expected

Duplicate invoices enter accounting systems through predictable routes: the same invoice emailed twice by a supplier, a re-sent invoice after a payment query, a bookkeeper entering a bill they didn't realise had already been processed, or a supplier numbering system that reuses reference numbers across different periods.

Manual invoice processing creates errors in 5-10% of invoices, with duplicate payments among the most common. For a business processing 100 invoices per month, that represents five to ten potential errors each cycle. Not all of them are duplicates, but duplicates are the error type most likely to result in an overpayment that is difficult to recover.

For accountants and bookkeepers managing multiple clients through accounting practice software, duplicate detection is typically a reactive process: catch it at reconciliation, query the supplier, request a credit note. The workflow described below makes it proactive: detect before the ledger, not after.

What Duplicate Detection Should Check

A duplicate invoice detection workflow should match against at least three fields:

1. Invoice reference number - the most obvious check, but not sufficient alone. Suppliers occasionally reuse reference numbers, and different suppliers may use the same number format.

2. Supplier identity and amount - an invoice from the same supplier for the same amount within a defined time window is a strong duplicate signal, even if the reference number differs.

3. Invoice date range - a 60-90 day lookback window catches re-submitted invoices without flagging genuinely recurring bills (monthly service invoices, regular supply deliveries).

The combination of supplier + amount + reference number + date window is more reliable than any single field. Detection logic that checks only reference numbers will miss duplicates where the reference has been manually adjusted. Detection that checks only amounts will generate too many false positives for suppliers with consistent pricing.

Step-by-Step: Implementing Duplicate Detection in Xero

Step 1: Review your current intake process

Before configuring detection logic, map where invoices currently enter the workflow. Common intake points:

• Direct email to a shared AP inbox

• Supplier portal or e-invoicing connection

• Manual upload from Dext or Hubdoc

• Direct entry by a bookkeeper into Xero

Each intake point is a potential duplicate entry point. If the same supplier sends to both the AP inbox and a project manager's email, both versions may be entered separately without a shared review step.

Control checkpoint: Consolidate all invoice intake to a single channel before attempting to configure detection logic. Detection against a fragmented intake process generates incomplete results.

Step 2: Configure Xero's duplicate bill detection settings

Xero includes a basic duplicate bill detection feature that flags bills with the same supplier, reference number, and amount. To check and configure:

1. Navigate to Settings - Invoice Settings in Xero

2. Review the duplicate detection toggle - ensure it is enabled

3. Understand its limitations: Xero's native detection checks reference number and supplier combination only. It does not apply a date window or check amount independently of the reference number.

Control checkpoint: Xero's native detection catches the most obvious duplicates but misses reference-changed or amount-only duplicates. Note which supplier types in your client's ledger are most likely to use non-standard reference numbering.

Step 3: Build a supplier reference register for high-risk suppliers

For suppliers the client invoices frequently and at high value - subcontractors, major materials suppliers, equipment hire companies - create a reference register that tracks the last five to ten invoice numbers and amounts for each supplier. This can be maintained in a simple spreadsheet or within the AP workflow tool.

When a new invoice arrives from a high-risk supplier, cross-check it against the register before entry.

Control checkpoint: This manual step is a temporary measure until automated detection is in place. Flag any supplier that has submitted a duplicate in the previous 12 months as a permanent high-risk supplier requiring manual reference cross-check.

Step 4: Apply a 90-day lookback rule

In Xero, run a monthly check using the Bills list filtered by supplier, sorted by amount, covering the previous 90 days. Any supplier with two or more bills at the same amount within that window should be manually verified.

This takes approximately 15 minutes per client per month for a business with 50-100 invoices per month.

Control checkpoint: Document the check in a monthly control log. The log entry should record: date checked, number of potential duplicates identified, outcome of each review (legitimate or duplicate), and action taken.

Step 5: Configure automated detection through an AP workflow tool

For clients processing more than 50 invoices per month, manual detection is insufficient as a primary control. Platforms that integrate with Xero and MYOB can apply automated detection before invoices reach the ledger.

Automated detection should:

• Check reference number + supplier + amount against the previous 90 days of bills

• Flag the invoice for review rather than auto-rejecting (some duplicates are legitimate rebills after a dispute)

• Record the flag in the audit trail even if the invoice is subsequently approved

A bookkeeper at a wholesale distribution firm in Sydney managing 130 invoices per month through MYOB implemented automated duplicate detection through Pulsify's validation and exception review workflow. In the first month, three duplicate invoices were flagged: two were genuine re-submissions from suppliers, one was a data entry error from a new accounts staff member. All three were caught before ledger publication.

Step 6: Establish a review and escalation process for flagged invoices

When a duplicate flag is raised, the review process should follow a defined path:

1. The bookkeeper or accounts staff receives the flag notification

2. They cross-check the flagged invoice against the matching entry in the system

3. If it is a confirmed duplicate: reject the invoice and notify the supplier with a reference to the original bill

4. If the flag appears to be a false positive: document why in the audit trail and approve

5. If uncertain: escalate to the financial controller before approval

Control checkpoint: Every flag should result in a recorded outcome. A flag with no recorded outcome is a control gap.

Implementing Duplicate Detection in MYOB

MYOB's duplicate detection capabilities are similar to Xero's native functionality: it checks invoice number and supplier combination but does not apply date-windowed amount matching. The configuration path:

1. In MYOB Business, navigate to Purchases - Bills

2. MYOB will warn when an identical invoice number is entered for the same supplier - this is the native detection

3. For more robust detection, use MYOB's accounting integrations with an AP automation tool that applies multi-field matching logic before the bill reaches the MYOB ledger

The workflow steps above (reference register, 90-day lookback, automated detection) apply equally to MYOB clients. The platform-specific difference is in how flagged bills are held before publication: MYOB's native hold function for queried bills differs slightly from Xero's awaiting approval state, but the principle is identical.

Maintaining the Detection Workflow Over Time

Duplicate detection is not a one-time configuration. Suppliers change their reference numbering systems. New suppliers enter the system with unfamiliar patterns. Staff changes alter who is applying the detection logic.

Monthly maintenance tasks:

• Review the duplicate flag log to check that all flags have recorded outcomes

• Check whether any suppliers have changed their invoice numbering in the period

• Confirm that the 90-day lookback window is still being applied to the Bills list

• Update the high-risk supplier register with any new additions

Quarterly:

• Review whether the current detection logic (reference number + supplier + amount + date window) is catching the types of duplicates the client is actually experiencing

• Assess whether invoice volume growth has made manual detection steps unmanageable

For clients whose invoice volume is growing rapidly, moving from manual lookback checks to automated detection is the most effective upgrade. The cost of implementing automated detection is typically less than the bookkeeper time spent on manual checks at 80+ invoices per month.

Frequently Asked Questions

What fields should a duplicate invoice detection workflow check?
The most reliable combination is supplier identity, invoice reference number, invoice amount, and a date lookback window of 60-90 days. Checking any single field in isolation generates either false positives (amount only) or missed duplicates (reference number only). The combination reduces both error types.

Does Xero detect duplicate invoices automatically?
Xero has a basic duplicate detection feature that flags invoices with the same supplier and reference number. It does not apply date-windowed amount matching or catch duplicates where the reference number has been altered. For businesses with high invoice volumes or complex supplier relationships, a dedicated AP workflow tool provides more comprehensive detection.

How does duplicate detection work in MYOB?
MYOB warns when an identical invoice number is entered for the same supplier, which catches the most obvious duplicates. It does not check for amount-only matches or apply a date lookback window. The same limitations as Xero's native detection apply.

At what invoice volume does manual duplicate detection become inadequate?
Manual lookback checks become unreliable as a primary control above approximately 50-60 invoices per month per client. Above that level, automated detection that runs before the invoice reaches the ledger is more reliable and less time-intensive than monthly manual review.

What should happen when a duplicate is flagged?
The flagged invoice should be held before ledger publication. The bookkeeper should cross-check against the matching entry, confirm whether the flag is a genuine duplicate or a false positive, document the outcome in a control log, and either reject the invoice (with supplier notification) or approve it with the false positive reason recorded. Every flagged invoice should have a recorded resolution.