Duplicate bookkeeping transactions often arise when bank feeds, manual imports and integrations overlap. Detect them by comparing dates, amounts and source identifiers, then correct them without deleting legitimate separate transactions that happen to look similar.
Preserve an audit trail and check whether duplicates affected a submitted return. Fix the import rule or workflow that created the error rather than repeating manual cleanup indefinitely.
Identify the duplicate's source
Start with the affected account and transaction references, then determine how each entry was created. A bank feed, manual statement import, sales integration and receipt tool can all record aspects of the same commercial event. The problem may be duplicate data, or it may be a legitimate invoice and matching payment that have not been linked correctly. Establish that distinction before deleting anything.
Self-employed business records need to support the reported income and expenses, so a duplicate that changes the figures requires a documented correction. Keep the original evidence and explain the relationship between the entries. The objective is an accurate ledger with a traceable history, not simply reducing the number of transactions until a dashboard total looks closer to the owner's expectation. [1]
Use several matching clues
Compare date, amount, counterparty, bank reference, invoice number and source identifier. Two equal payments on the same day can be genuine separate transactions, especially in retail or recurring supplier payments. A duplicate may also appear on different dates because one system uses settlement date and another uses the original sale date. Use the underlying statement or invoice to establish what actually happened.
Look at whether one entry is a bill or sales invoice and the other is its settlement. In that case, the supported action may be matching rather than deleting. Check the effect on receivables, payables and bank reconciliation before approving the correction. Removing the wrong record can make the bank balance look right while leaving the customer or supplier account inaccurate.
Review the reporting consequences
Identify whether the duplicate falls in an open period, a closed accounting period or a submitted tax return. Record the impact on income, costs, VAT and relevant balances. A bookkeeping change may require a separate reporting correction depending on the circumstances. Do not assume that editing the current ledger automatically amends information already sent to HMRC or supplied to an accountant.
Where many entries are affected, establish the date range and import event that created them. Reconcile a controlled group against the source before applying a bulk correction. Preserve the list of affected identifiers and the method used. A blanket deletion of every repeated amount can remove valid trading activity and make the original duplicate problem harder to reconstruct.
Correct through the supported workflow
Use the software's appropriate reversal, unmatching or deletion process for the actual record type and period. Keep the reason visible in the audit trail. If the system offers several options, check which preserves the invoice and settlement relationship correctly. Do not create a miscellaneous balancing journal merely to offset a duplicate that remains incorrectly represented in customer, supplier or VAT records.
After correction, reconcile the bank account and affected control accounts and trace the original commercial transaction once through the ledger. Check related attachments and payment status. A removed duplicate may leave an orphaned receipt or cause an invoice to appear unpaid if the wrong match was disturbed. The correction is complete when the whole transaction is coherent, not only when one report total has changed.
Remove the cause of recurrence
Review overlapping bank-feed start dates, repeated imports and integrations that create entries already recorded elsewhere. Decide which system owns each transaction type and how the other systems match or attach evidence to it. Keep the mapping and import history available to the bookkeeper. Repeating a manual clean-up every month is a sign that the underlying workflow still needs attention.
Use Reconciling bank feed interruptions where duplicates followed a bank-feed interruption and Accounting software migration support to discuss a bookkeeping reconciliation. Provide an anonymised example showing the two entries and their sources, together with the affected period. A focused review can then distinguish a matching issue, an import overlap and a wider reporting correction without requesting unrelated customer records at the outset.
Monitor the next import or integration run for the same pattern. Confirm that the corrected setting prevents recurrence and does not omit legitimate transactions. Record the outcome with the original issue so a later software change does not reintroduce the old workaround or reset a carefully chosen import start date. Keep the original import filename and time with the correction log, so a later operator can distinguish the rejected upload from the accepted replacement.
Illustrative scenario
A shop imports card settlements from two connected systems. Reconciliation shows duplicate gross receipts, and the team adjusts the integration settings after documenting the correction.
Preparation checklist
- Identify the source overlap
- Compare transaction identifiers
- Check reporting effects
- Correct the import process
Frequently asked questions
Are identical amounts on the same date always duplicates?
No. They may be separate genuine transactions. Compare source references and supporting documents before removing an entry.
Is an invoice plus its bank payment a duplicate?
Not necessarily. They may need to be matched through the supported process rather than deleted. Check the customer or supplier balance as well as the bank account.
Does correcting the ledger amend an earlier tax return automatically?
No. Assess whether a separate reporting correction is needed for a submitted period and retain the reason for the change.
How can repeated duplicates be prevented?
Identify the originating feed, import or integration and assign one clear recording route for each transaction type, with matching and date-range controls.
Official sources
Sources checked: 8 September 2026. Check the linked guidance for subsequent changes.
General information only. The appropriate action depends on your circumstances and the applicable jurisdiction.
Report a correction