A supplier sends the same €1,240 invoice twice: once by email and once through a colleague who forwards it on WhatsApp. Both copies look legitimate. Both reach the accounts inbox. Without a clear process for how to identify duplicate bills, one can be approved, paid and claimed for VAT twice before anyone notices.
Duplicate bills are not always obvious copies. They can arrive with a slightly different file name, a revised PDF layout or a minor variation in the invoice number. They can also be created internally when two people upload the same document, or when an invoice is re-entered after a system migration. The result is the same: overstated costs, incorrect VAT figures, messy supplier balances and avoidable work at month end.
Why duplicate bills cause more than a payment error
The immediate risk is paying a supplier twice. That affects cash flow, especially for smaller businesses managing tight payment runs. But a duplicate entry can create wider problems even when it is caught before payment.
If both records are included in your bookkeeping, expenses are overstated. Where VAT has been claimed twice, your VAT return may be inaccurate. For Maltese businesses, that means more than a reconciliation issue: it can mean time spent correcting records, explaining variances and amending information before filing.
Duplicates also reduce confidence in reporting. A director reviewing a monthly profit figure cannot make good decisions if recurring costs are inflated. Accountants face the same issue at scale. One duplicate may be simple to resolve. Fifty across multiple client files are a month-end delay.
The aim is not to create another manual checking task. It is to make duplicate detection part of the invoice workflow, with clear exceptions for a person to review.
How to identify duplicate bills using the right fields
A duplicate check based only on supplier name will produce too many false matches. A business may receive several legitimate invoices from the same mobile provider, wholesaler or consultant in one month. The better approach is to compare a combination of fields.
Start with the supplier name, invoice number, invoice date, total amount and currency. An exact match across these fields is a strong signal that the bill is duplicated. If the same invoice number has been entered twice for the same supplier, treat it as a likely duplicate even where the dates differ slightly.
Then look at the source document. Compare the PDF, scan or image itself. Check line descriptions, quantities, VAT amounts, bank details and payment terms. A duplicate can have a new upload date while the underlying invoice is identical.
This matters for foreign-currency purchases. A USD or GBP invoice may convert to a different euro value if entries are processed on different days or with different exchange-rate settings. The totals in euros may not match, but the supplier invoice number and original-currency total will. Compare both the source amount and the converted value rather than relying on one figure.
Check invoice numbers, but do not trust them blindly
Invoice numbers are usually the best starting point, but they are not perfect. Some suppliers reuse simple references, issue separate invoice series for branches or include spaces and punctuation inconsistently. For example, INV-1048, INV 1048 and inv1048 may all refer to the same document.
Normalise the data before comparing it. Remove unnecessary spaces, standardise letter case and treat common punctuation changes as equivalent. This avoids missing duplicates that look different only because they were typed or extracted differently.
At the same time, do not automatically reject every repeated invoice number. A supplier may use a credit-note reference that resembles an invoice reference, or may reset its numbering each year. Review the document type, date and amount before deciding.
Use amount and date as supporting evidence
Matching totals are useful, especially for invoices without a clear invoice number. If the same supplier, date and amount appear twice, review both records. If the dates are a few days apart but the line items match, the second entry may be a resend rather than a new bill.
There are legitimate exceptions. Monthly rent, software subscriptions and utility payments may have the same or similar amount each period. They should not be marked as duplicates simply because they recur. The invoice date, reference and billing period should show whether the charge is new.
For recurring bills, use a defined matching window. Comparing invoices received within a few days is sensible. Comparing every invoice from the same supplier across a full year will create noise and slow the team down.
Build duplicate checks into invoice intake
Most duplicates enter the accounts process before anyone starts reviewing transactions. They appear because invoices are received through multiple channels: a shared email inbox, an employee’s mobile phone, a supplier portal and a dashboard upload. Chasing a single perfect submission route is rarely realistic.
Instead, create one central processing queue. Every bill should enter the same system, regardless of whether it was sent by email, WhatsApp or uploaded manually. The system should capture the document, extract the key data and compare it with existing records before the bill reaches approval.
A practical workflow has four controls:
- Capture each invoice once and retain the original document as the audit record.
- Check supplier, invoice number, date, currency and totals against previously processed bills.
- Flag exact and near matches for review before posting or payment.
- Record the outcome, including why a potential duplicate was accepted or rejected.
The final point is often missed. A flagged invoice may be valid, such as a recurring charge with the same value. Keeping a short review note prevents the same question returning at audit time or during the next month-end close.
Separate duplicate detection from approval
A duplicate flag is not a final decision. It is a prompt to check the evidence. If your workflow automatically blocks every match, valid supplier invoices can be delayed. If it merely displays a warning that people routinely ignore, the control has no value.
Use a simple exception path. The reviewer should see the new invoice beside the possible existing record, including both documents and the matched fields. They can then mark it as a duplicate, a valid separate bill or a document that needs supplier clarification.
For a confirmed duplicate, do not delete the record without a trace if it has already been reviewed or posted. Mark it clearly as duplicate, reverse any accounting impact where necessary and retain the source document. This preserves an audit trail and helps explain why the item did not proceed to payment.
Approval controls still matter. The person uploading a bill should not be the only person able to approve payment, particularly for higher-value invoices. However, small teams need proportionate controls. A founder may handle both activities, but should still review duplicate warnings before releasing payments and reconcile supplier statements regularly.
Reconcile supplier statements and bank payments
Invoice-level checks catch many duplicates early. Supplier statement reconciliation catches the ones that slip through.
Compare your supplier ledger with statements received from key suppliers. Look for invoices shown twice in your records but once on the statement, or payments that appear twice against one invoice. Suppliers may also spot a duplicate payment before your team does, but relying on them is not a control.
Bank reconciliation adds another layer. Two identical payments to the same supplier within a short period deserve investigation. That said, a duplicated payment does not always mean a duplicated bill. It may be a payment file error, an advance payment or a bank transfer that was reissued after a failed reference. Follow the evidence back to the original invoice and supplier account.
For businesses with frequent purchases, prioritise suppliers with high invoice volume, manual billing practices or multiple submission routes. This is where duplicate risk is highest and where automated matching saves the most time.
Make VAT part of the review
Duplicate bills can distort VAT even when no payment has been made. A second posting may duplicate input VAT, misclassify the transaction or place it in the wrong reporting period. The financial total may look plausible while the VAT treatment is wrong.
When reviewing a suspected duplicate, compare the VAT rate, VAT amount and tax category as well as the gross total. This is particularly useful for EU purchases, reverse-charge transactions and invoices containing more than one VAT treatment. A document that looks similar may not be an exact duplicate if its tax treatment or supply period has changed.
MyAccountant can automate this first line of control by extracting invoice data, learning supplier patterns and surfacing possible duplicates for review before they become another spreadsheet problem. The decision remains clear: review exceptions, not every document.
A cleaner process beats a longer checklist
The best duplicate-bill process is quiet. Invoices arrive through the channels your team already uses. Data is captured consistently. Exact matches and meaningful near matches are flagged early. Only the exceptions need attention.
That gives business owners cleaner cash-flow figures, gives accountants more reliable records and gives VAT reporting a stronger foundation. Start by reviewing the last two or three months of supplier invoices for repeated references, amounts and documents. The patterns you find will show exactly where your intake process needs tightening.