# Duplicate Deposits and Payroll Debits Not Matching the Bank

> Duplicate deposits in the bank feed or payroll debits not matching? A diagnosis order for Australian bookkeepers, including Payday Super timing.

**Source:** https://agentive.au/blog/duplicate-deposits-payroll-feed-mismatches-bank-reconciliation/ · **Published:** 2026-10-23 · **Updated:** 2026-10-22 · **Author:** Dr. Ash Khalilian

---

Short Answer

**Check the bank's own statement first. If the bank shows a deposit once, the second feed line is a duplicate and can be removed. If the bank shows it twice, it is real money. For payroll debits that do not match, rebuild each debit from the pay run report: net pay, super and tax are often debited separately, on different days.**

Last reviewed: October 2026

Key takeaways

-   The bank's own statement is the only reliable test of whether a deposit is duplicated or genuinely received twice.
-   Xero says deleting a bank statement line changes the statement balance, so lines should only be deleted when they are duplicates.
-   Payroll platforms often debit lump sums that do not line up one-to-one with the payslips recorded in the accounting file.
-   Under Payday Super, from 1 July 2026, the ATO requires super guarantee contributions to reach the fund within 7 business days after payday in most cases.
-   A duplicated deposit coded as a sale overstates GST, which the ATO treats as a credit error that can usually be corrected on a later BAS.
-   Australian bookkeepers should diagnose before they delete, and write down why each line was removed.

Two problems turn up in almost every bank reconciliation question bookkeepers ask each other. The first is a deposit that appears twice in the feed, and nobody is sure whether the client was paid twice or the software imported it twice. The second is payroll: the platform takes one debit, the accounting file shows a stack of separate wage payments, and the numbers will not agree. Our position is that both are diagnosis problems, not data entry problems. Find out what actually happened at the bank, then fix the file to match. This is exactly the repetitive checking Agentive builds [dedicated AI for Australian finance teams](/ai-employee/) to carry, with a bookkeeper making the calls.

## Why does the same deposit appear twice in the bank feed?

Usually because two routes delivered the same transaction into the file. Xero's help article on the [Duplicate Statement Lines report](https://central.xero.com/s/article/Duplicate-Statement-Lines-report-New) says duplicate statement lines can be imported through a bank feed or through a statement that was manually imported. In practice, the common causes fall into a short list:

-   **Feed plus manual import.** Someone uploaded a CSV or statement file to fill a gap, and the feed later delivered the same dates.
-   **Reconnected feed.** A feed that dropped out and was reconnected pulled history that was already in the file.
-   **Recorded on both sides.** The payment was marked as received against the invoice, and someone also created a separate receive money transaction for the same bank line.
-   **Gross and net income.** Sales were recorded from the point of sale or payment processor, and the processor's payout deposit was then coded to sales again.
-   **A genuine double payment.** The customer really did pay twice. This is not a duplicate at all. It is an overpayment that needs a refund or a credit.

Each cause has a different fix, so the first question is always the same: what does the bank itself say?

## How do you tell a real double payment from a duplicate line?

Compare the lines with the statement downloaded from the bank, not with the feed. If the bank's statement shows the deposit once, the second line in the file is a duplicate. If the bank shows it twice, the money arrived twice and both lines are real. Xero's own guidance makes the same point: when its report finds potential duplicates, it says to compare them to your actual bank statement before deleting anything.

Then check the running balance. A duplicate statement line pushes the file's statement balance above the closing balance on the real statement by exactly the duplicated amount. A genuine double payment does not, because the bank's balance moved too.

| What you see | Likely cause | What to do |
| --- | --- | --- |
| Two identical lines, bank statement shows one | Duplicate import (feed plus manual file, or reconnected feed) | Delete one statement line, then confirm the statement balance agrees |
| Two identical lines, bank statement shows two | Customer paid twice | Keep both; record the overpayment and agree a refund or credit |
| One bank line, income recorded twice | Payment applied to the invoice and also entered as a separate receipt | Remove the extra transaction; leave the statement line alone |
| Sales higher than the deposits support | Gross sales and processor payouts both coded to income | Code payouts against a clearing account, not sales |
| Similar lines, slightly different amounts or text | Partial match: could be two real payments | Treat as real until the bank statement and remittances prove otherwise |

A word on that last row. Same-amount payments a week apart are common with instalments and retainers. If a "duplicate" looks suspicious for a different reason, such as a payment going out to a supplier twice on new bank details, our guide to [fake invoice and registry scams](/blog/fake-invoice-and-registry-scams-australian-small-business/) covers what to check before money leaves the account.

## How do you find and remove duplicate statement lines in Xero?

Run Xero's Duplicate Statement Lines report, confirm each hit against the bank statement, and only then delete. Xero says the report compares the date and amount of statement lines in a bank account and, where it finds a match, then looks for an exact match across the reference, particulars or payee fields. It also says the report does not show partial matches, which you need to find manually, and does not show duplicates Xero picked up and deleted automatically at import. Those appear on the Statement Exceptions report in the Bank Reconciliation report pack.

Deleting is the step to be careful with. Xero's article on how to [delete or restore a bank statement line](https://central.xero.com/s/article/Delete-or-restore-a-bank-statement-line) says the statement balance changes when you delete a line, so you should only delete a statement line if it is a duplicate. If a line is reconciled to the wrong transaction, Xero says to unreconcile it instead. If you delete a line that is reconciled, Xero deletes the statement line and reverts the account transaction to unreconciled, so the transaction still needs dealing with.

## Why do payroll debits not match the pay run in the accounting file?

Because the bank sees how the money was grouped, and the file records how it was earned. A payroll platform can collect one lump sum for a whole pay run and then pay each employee from its own account. The accounting file, meanwhile, may hold one wage payment per employee, a PAYG withholding liability and a super liability. None of those will match a single bank line on its own.

Timing makes it worse. Net wages, super contributions, PAYG withholding and any platform fees can each leave the account on different days, and some platforms collect them in one debit while others split them. Before changing anything, get the pay run report and the platform's payment or funding report for the same period, and build each bank debit from its parts. Common mismatches are a debit covering two pay runs, a re-run payment, or a fee taken in the same debit.

The clean way to record it is a payroll clearing account. Post the pay run's wages, withholding and super to their liability accounts, reconcile each bank debit against the clearing or liability account it paid, and check that the clearing account returns to zero after each cycle. A clearing account that drifts away from zero is the most useful payroll error signal a bookkeeper has, because it points to the exact pay run that does not reconcile.

## How has Payday Super changed super debits in the bank feed?

Super debits now follow the pay cycle instead of the quarter. The ATO's page [About Payday Super](https://www.ato.gov.au/businesses-and-organisations/super-for-employers/about-payday-super) says that from 1 July 2026, super guarantee contributions must be received by employees' super funds within 7 business days after paying employees, with enough information to allocate the contributions to member accounts. Before that date, contributions were due 28 days after the end of each quarter. The same page notes that the Small Business Superannuation Clearing House has now closed, so many employers have moved to a commercial clearing house or to payroll software.

For reconciliation, that means a file with fortnightly pays should now show a super debit roughly every fortnight, not four times a year. A quarterly-sized super debit after July 2026 is a question worth asking. The ATO's page on [payment deadlines for Payday Super](https://www.ato.gov.au/businesses-and-organisations/super-for-employers/paying-super-on-payday/payment-deadlines-for-payday-super) adds that employers using a clearing house, including one used through payroll software, need to allow enough time for it to process the payment within the 7 business day timeframe. It also says longer timeframes apply in some situations, such as the first contribution for a new employee, which must be received within 20 business days after payday.

Late super is not a reconciliation tidy-up. The ATO says that from 1 July 2026, the super guarantee charge applies when amounts are not received by the fund within the deadline, and that it includes interest compounding daily at the general interest charge rate and an administrative uplift amount. Treat a missing super debit as urgent.

## What is the right order to diagnose a bank feed mismatch?

Statement first, then grouping, then coding. This is the order we would follow for any account where the feed and the file disagree:

1.  **Download the real statement.** Get it from the bank for the affected months, not from the feed.
2.  **Find the first month that is out.** Compare the file's statement balance with the bank's closing balance month by month. The difference in the first bad month is usually the amount you are looking for.
3.  **Run the duplicate check.** Use the software's duplicate report, then search manually for partial matches with the same amount.
4.  **Classify each suspect line.** Duplicate import, double-recorded transaction, gross and net income, genuine double payment, or unrelated. Use the table above.
5.  **Rebuild each payroll debit.** Match it to the pay run and platform reports: net wages, super, withholding and fees, by date.
6.  **Fix in the right place.** Delete statement lines only for true duplicates; remove or correct transactions for everything else.
7.  **Check GST.** If a duplicate was coded with GST in a lodged period, work out whether it is a credit or debit error and correct it within the ATO's limits.
8.  **Write it down.** Note each deleted line, the reason and the statement page you checked it against, so the next reviewer does not undo it.

Steps 2 to 5 are where the time goes, and they are rules-based. Our walkthrough on [automating bank reconciliation with AI](/blog/how-to-automate-bank-reconciliation-with-ai/) shows how matching rules carry that load, and our piece on [trusting AI to categorise transactions](/blog/can-you-trust-ai-to-categorise-transactions/) covers where automated coding is reliable and where it is not. If the account is many months out rather than a few lines, start with our [bookkeeping cleanup order for messy books](/blog/messy-books-where-to-start-catch-up-or-start-fresh/) instead.

## Does a duplicate deposit or expense affect the BAS?

Yes, if it was coded with GST in a period that has been lodged. A duplicated deposit coded as a taxable sale overstates GST on sales. The ATO's page on [types of GST errors](https://www.ato.gov.au/businesses-and-organisations/gst-excise-and-indirect-taxes/gst/completing-your-bas-for-gst/correcting-gst-errors/types-of-gst-errors) calls that a credit error, meaning too much GST was reported or paid. It says a credit error can be corrected on a later BAS within the period of review, which starts on the day the BAS was lodged and ends 4 years and one day later, and that credit errors are not subject to value limits.

A duplicated expense works the other way. If a supplier bill was entered twice and a GST credit was claimed twice, too little GST was reported, which the ATO calls a debit error. For a business with GST turnover under $20 million, the ATO says a debit error must be corrected on a BAS lodged within 18 months of the due date of the BAS in which it was made, and the debit error value limit is less than $12,500. Outside those limits, the original period needs revising. Our article on [BAS preparation in Australia](/blog/how-to-automate-bas-preparation-australia/) sets out the checks that should sit before every lodgment so these errors are caught earlier.

## What does this look like on a real account?

Here is a clearly labelled illustration, not an Agentive client. A small café's bank account in the file is $4,350 higher than the September closing balance on the bank statement. The duplicate report shows a $4,350 customer deposit on 12 September twice. The bank statement shows it once, and the file shows a manual statement upload for early September followed by the feed reconnecting. The bookkeeper deletes the second line and the balance agrees. Because the deposit was coded as a catering sale with GST, and the quarter has not been lodged yet, no BAS correction is needed.

The same account shows a $18,420 payroll debit that matches nothing. The pay run report shows net wages of $15,960 for the fortnight; the payroll platform's funding report shows that debit also collected $2,460 of super for that pay run. Payday Super is doing what it should. The bookkeeper splits the debit across wages payable and super payable, and the payroll clearing account returns to zero.

## Where does AI help, and where should a person decide?

AI is well suited to finding these problems and poorly suited to deciding them alone. Comparing every month's balance to the statement, flagging same-amount lines, rebuilding payroll debits from pay run reports and checking that clearing accounts return to zero are repetitive and rules-based. That is the work Agentive's [AI for bank reconciliation](/ai-employee/bank-reconciliation/) is designed to carry, and our [AI bookkeeping](/ai-employee/bookkeeping/) page covers the wider monthly routine.

Agentive's view, from building this for Australian bookkeepers and BAS agents, is that deleting a statement line is a decision, not a match. A duplicate that is really a double payment means a customer is owed money. So the AI should propose and explain, and a bookkeeper should approve each deletion with the statement reference attached. Our guide to [human review checkpoints in AI bookkeeping](/blog/human-in-the-loop-ai-bookkeeping-review-checkpoints/) sets out where those approvals belong.

Where the AI runs matters as well, because bank and payroll data are among the most sensitive records a business holds. Agentive's AI Employee runs on a dedicated single-tenant server on AWS Sydney, with client data stored onshore and never used to train models. Our article on [AI data governance in Australia](/blog/ai-employee-security-data-governance-australia/) explains why that design matters, and the [Agentive AI Employee overview](/ai-employee/) covers the rest.

## Diagnose before you delete

Duplicate deposits and unmatched payroll debits feel like software faults. Most of the time they are grouping and timing problems that the bank statement and the pay run report will explain in minutes. Use the statement as the referee, delete only true duplicates, rebuild payroll debits from their parts, expect a super debit after every pay run under Payday Super, and correct any GST effect within the ATO's limits. Then write down what you did, so the fix stays fixed.