When a bank feed shows a transaction twice, an accountancy practice should establish whether there were two real movements of money or one transaction imported more than once. Deleting a feed line just because the amount and date match can hide a genuine second payment. Matching both lines to separate expenses can create a false cost. A controlled investigation compares the bank’s source statement with the bookkeeping entries and records exactly how the discrepancy was resolved.
A duplicate-looking line is not necessarily a duplicate payment
Two card purchases may have the same amount and merchant on the same day. A weekly standing order can resemble a previous transfer. Pending card authorisations can be followed by completed transactions, while imported banking data may sometimes be re-synchronised after a connection problem. These situations require different accounting responses.
Start with the account and period affected. Does the official bank statement show one debit or two? Are transaction references identical? Has either line already been reconciled or matched to a supplier bill? A team carrying out the month-end close and exception review should treat unexplained feed differences as open items rather than forcing the reconciliation to balance.
Build a three-way comparison
Compare the bank statement, the feed entry and the accounting ledger. The statement is independent evidence of the bank movement, while the feed is a method of transferring data and the ledger records what the practice has posted. Keep timestamps, payee information, currency and any reference from the bank. Beware of transactions that have slightly different dates due to weekends or settlement timing.
| Evidence | Question it answers |
|---|---|
| Official bank statement | Did the money actually move once or twice? |
| Feed import or sync history | Was the same transaction received in multiple imports? |
| Reconciled ledger entry | Has a transaction already been accounted for? |
| Supplier bill or receipt | Which business expense does the payment relate to? |
| Adjustment log | Who changed the record and why? |
This three-way approach also helps distinguish duplicate feed lines from duplicate bills in capture software. The workflow behind document capture tools such as Dext and AutoEntry concerns source documents; a duplicated source document and a duplicated bank movement are different problems, even though both can lead to overstated expenses.
Investigate the status before editing
In common cloud accounting systems, a feed line may be unmatched, matched, categorised or reconciled. The exact labels and actions depend on the provider and version. Review the audit history before changing anything. If a line is already matched to the wrong bill, the problem may need to be reversed and correctly re-matched, not simply hidden.
Look for recent events: a bank connection was disconnected and reconnected; someone imported a CSV for dates already covered by a live feed; two employees posted the same payment through different workflows; or a payment batch was split. Do not assume that a feed provider error is the cause until the bank’s own records support that conclusion.
Do not delete evidence to make the balance look right
If the bank statement proves one debit but two imported entries exist, identify which representation can be safely excluded or removed through the accounting application’s supported procedure. Preserve an audit note containing the transaction ID, amount, reason, person and date. If the statement shows two debits, both need investigation even when the client insists that they only purchased one item.
Do not post an unexplained balancing journal merely to close the month. That would conceal the issue without explaining it. Different systems handle deleted, excluded or unreconciled feed entries differently; the practice should test its standard procedure in its chosen software and document permissions accordingly. The distinctions between accounting-platform workflows in Xero and QuickBooks Online for UK practices are useful when designing a repeatable control.
When the duplicate is a supplier payment
Find the underlying bill, remittance advice and any supplier credit. If the client actually paid twice, there may be a recoverable overpayment or credit, rather than two deductible expenses. Contact the client before requesting a refund or offset from the supplier. Link the agreed action to the ledger so the credit can be traced later.
Where a credit note is involved, consult the separate explanation of supplier credit notes and reconciliation. A feed discrepancy, purchase return and credit-note adjustment are distinct accounting events. Treating them as interchangeable is a common route to double-counting.
Example: one subscription, two imported lines
Imagine a monthly software subscription of £45. The bank’s statement shows one card payment on 14 October. The live feed contains one line from the bank connection and another from a CSV imported during a temporary sync interruption. Both have matching references. The practice first confirms that the ledger contains only one genuine charge, then follows its application’s controlled method to exclude the duplicate feed record. The audit note records the comparison and the reason for the change.
Now change one fact: the bank statement has two distinct £45 debits. It would be unsafe to exclude one based on similarity alone. The practice must ask whether the provider charged twice, whether two subscriptions exist or whether the payments relate to different accounts.
Responsibilities and approvals
Assign a named person to investigate each exception and define who can approve edits to reconciled periods. A client may know why two similar payments occurred, but the accountant should record the explanation and supporting evidence. A brief summary such as “One source payment; duplicate import after CSV upload; no ledger change required” is more useful than a bare status label.
The controls for client approvals and a clear audit trail can be adapted to unresolved bank-feed items. Set a cut-off for reporting material discrepancies, but don’t invent a legal requirement for a particular number of days where none has been established.
Questions from small practices
Can I rely on a matching reference number?
It is useful evidence, but the official statement and ledger status still need checking. References can be truncated, reused or displayed differently by providers.
Should a duplicated transaction automatically be refunded?
Only if there were two real payments and a refund is the appropriate agreed remedy. A duplicated feed record does not itself move money.
What if the duplicate is in an already filed period?
Determine whether the bookkeeping or filed returns were affected. If only the import view contains a duplicate with no ledger impact, the response differs from a duplicate expense already recognised in the accounts. Review the actual effect before preparing corrections.