Xero reconciles every bank deposit as its own separate line, which works right up until one remittance arrives as several deposits. A £50,000 remittance covering 38 invoices lands in the feed as two deposits, £35,000 and £15,000, two days apart, and the advice never says which invoices belong to which deposit. Nothing in Xero links a single remittance to more than one bank line, so working out the split falls to you, by hand, every time it happens.
Most guides assume one PDF settles as one bank deposit and one batch payment, and anyone receiving high-value B2B remittances knows the truth is messier. Customers stagger payments across several deposits all the time, for reasons that have nothing to do with you, and Xero on its own offers no way to link a single remittance to several incoming bank lines.
Why one remittance arrives as two (or more) deposits
The pattern shows up across Xero customers in four recurring shapes, and it's worth knowing which one you're looking at before you settle on a way to handle it.
Cash-flow staging on the customer side
The commonest reason is ordinary cash management. The customer's AP team approves the full remittance, their treasury function releases only part of the cash on the scheduled run, and the balance follows once funds clear from elsewhere, so you're holding a tidy remittance for the full amount while the bank shows two staggered transfers. It's especially common with mid-market customers running tight working capital, and with NDIS plan managers releasing funds as they receive plan instalments.
Payment-rail and banking limits
Some banks impose per-transaction caps on outbound bank transfers, particularly for newly onboarded payers, so a £50,000 remittance can hit the daily limit and split automatically into two payments with nobody on the customer side deciding anything. The remittance email lands intact, while the deposits behind it don't match it line-for-line.
Retentions, credits, and disputed lines
Construction, civil, and labour-hire customers routinely settle the bulk of a remittance immediately and hold a portion back for later release, whether that's retention, agreed deductions, or disputed lines. The remittance shows the gross figure, the first deposit shows the net release, and a smaller second deposit appears weeks or months later for the retained amount, which is familiar ground to anyone reconciling for a contractor paid by a Tier-1 civil or construction principal.
Multi-account or multi-entity routing
If the customer's AP system pays from more than one bank account, or if the remittance covers invoices from more than one of your trading entities, the deposits can land in different bank feeds entirely. A remittance that aggregates across your trading company and your service company will hit two different Xero organisations on the same day.
Among Xero teams handling concentrated B2B receivables in labour hire, NDIS, construction and wholesale, partial-payment splits rank as a top-three reconciliation pain, behind only volume and remittance-format complexity. That makes them routine work for those teams.
Why Xero on its own will not link them
Xero treats each bank deposit as an independent reconcilable line, so the feed shows £35,000 on Tuesday and £15,000 on Thursday and waits for you to tell it what each one represents. There's no field on a Xero invoice or batch payment that says "this remittance was settled across these two bank lines", and the remittance PDF isn't a first-class object in Xero at all unless you attach it manually to a batch payment after the fact.
That leaves the bookkeeper or finance manager to work out which invoices on the remittance correspond to which deposit. Most customers don't annotate the split, since the remittance just lists 38 invoices in the order they were entered into AP, so the reconciler ends up back-solving the allocation.
What the manual process actually looks like
The work is clerical from start to finish. On a mid-size NDIS-adjacent remittance it runs to roughly 25 minutes to match the invoices on the advice to open Xero invoices, then a further 40 minutes on the remainder when the deposit comes in lower than the remittance total and you have to work out which invoices were actually settled in the first tranche.
Steps usually include opening the remittance PDF, listing the invoice numbers in a spreadsheet, eyeballing the deposit amounts on the bank feed, and trying combinations of invoice totals until two subsets sum to the two deposits. A few teams have started using consumer AI chat tools to suggest the split, which speeds the maths, though the reconciliation itself, the part that creates the audit trail, still has to be posted by hand.
At a small client that's maybe 4 hours a month, and a bookkeeper's loaded rate of £25 per hour puts it at £100 a month, around A$120. Run the same problem at a high-volume firm doing 400 remittances a month across multiple entities and it becomes a five-figure annual line item, before you count the Friday-afternoon mistakes that have to be unwound on Monday.
Four ways to reconcile a split-deposit remittance in Xero
Since Xero won't link the remittance to multiple deposits for you, you're choosing between workarounds, and there are four in common use.
- Match each deposit independently. Treat the two bank lines as two separate batch payments. Work out which invoices belong in each batch from the remittance, then post two batch payments in Xero, each tied to its own bank line. The audit trail is clean, though all the analytical work lands on whoever is reconciling, which is fine when the split is obvious, say a clear retention release on a known schedule, and hard going when it isn't.
- Post the full remittance against the first deposit and use a suspense. Some teams reconcile the entire remittance against the larger first deposit and park the difference in a clearing or suspense account, then clear it when the second deposit arrives. The remittance stays intact as a single posting, at the cost of muddying the bank reconciliation in the interim and needing the discipline to clear suspense balances on a fixed cadence. Auditors generally tolerate it if the suspense is short-lived and well-evidenced.
- Lump-sum prepayment, then apply. Receive each deposit as a customer prepayment in Xero, then allocate against specific invoices once you've worked out the split. This works if your CFO is comfortable seeing customers carry temporary credit balances, and if your AR ageing reports can handle prepayments, and it gets administratively heavier as invoice counts grow, because each deposit becomes its own allocation exercise.
- Automate the matching and let the deposits sort themselves.Once you are past a handful of multi-deposit remittances a week, this is the option that stops costing you hours. Match the remittance to the open Xero invoices once, identify which subset clears first from the deposits already in the bank feed, post the matched batches against the right deposits, and let the tooling carry the audit trail.
A quick decision guide
If splits are rare (one or two a month, mostly retentions on a known release schedule), option 1 is fine, and most finance teams default there without thinking about it.
If splits are frequent but predictable (the same handful of customers split payments the same way every cycle), option 2 with a disciplined suspense process keeps the books clean and lets you batch the cleanup into a weekly review, as long as the suspense balances actually get cleared on that cadence.
If splits are frequent and unpredictable (any meaningful share of your B2B customers staggers payments, retains amounts ad hoc, or routes through multiple banks), options 1 and 3 both eat hours every week, and that's usually where automation starts to pay for itself. Tools that read the remittance, match against open Xero invoices, and post the batch (or batches) back to Xero with the PDF attached collapse the 25-and-40-minute exercise above into something closer to a minute per remittance, and they handle the multi-deposit allocation as a side effect of matching invoice-by-invoice rather than deposit-by-deposit.
When automation becomes the obvious call
As a rough rule, if you process more than 50 remittances a month and at least 20 percent of them split across multiple deposits, the manual cost is already in the thousands of pounds a year, and any reasonable automation pays back in well under a quarter. The sums shift even further if you run multiple Xero entities, because the multi-account or multi-entity routing described above compounds it.
The other forcing function is audit. If you operate in a regulated environment (NDIS billing, public-sector contracts, anything grant funded), the auditor will eventually ask why a remittance for £50,000 sits against a £35,000 batch payment and a separate £15,000 batch payment with no explicit link between them. Attaching the original remittance PDF to both batch payments, with the line allocation explicit, gives them the answer without anyone having to reconstruct it.
How RemitClear handles split deposits
RemitClear does the same work you would by hand, only faster. It reads the advice, matches every line to an open invoice in your Xero ledger, and lets you post the matched batch, or batches where the bank deposits are already split, back to Xero with the PDF attached for audit. When the cash arrives in tranches, you reconcile each bank line against the subset of matched invoices that belongs to it, instead of trying combinations in a spreadsheet until two totals agree. For teams running multi-entity setups, each Xero organisation has its own inbound address and payer mapping, so a remittance lands in the right organisation before anyone has to decide, and the audit trail survives the split.
Summary
The two shortcuts teams reach for under a Friday deadline are jamming the whole remittance against the larger deposit and letting a suspense balance sit there, or back-solving the split from a spreadsheet and mis-allocating a line that nobody catches until an auditor does. Pick the workaround that fits how often your customers actually split, match each deposit to its own subset of invoices, and keep the remittance PDF against every batch so the allocation can still be read back months later. For more on the underlying reconciliation workflow, see our guide on how to reconcile remittance advice in Xero, or the solution page for cash application automation.
