Xero reconciles every bank deposit as its own separate line. That's fine 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 the split becomes yours to solve, by hand, every time it happens.
Most guides treat a remittance as a one-to-one match: one PDF, one bank deposit, one batch payment. Anyone receiving high-value B2B remittances knows the truth is messier. Customers split payments across multiple deposits all the time, for reasons that have nothing to do with you, and Xero on its own offers no native way to link a single remittance to several incoming bank lines.
Why one remittance arrives as two (or more) deposits
It's worth understanding the underlying reasons before deciding how to fix the symptom. The pattern shows up across Xero customers in four recurring shapes.
Cash-flow staging on the customer side
The most common reason is mundane. The customer's AP team approves the full remittance, but their treasury function only releases part of the cash on the scheduled run, and the balance follows once funds clear from elsewhere. You see a tidy remittance for the full amount, but the bank sees two staggered transfers. This is 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. A £50,000 remittance can hit the daily limit and split automatically into two payments without any human intervention on the customer side. The remittance email lands intact, but the bank deposits 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 (retention, agreed deductions, or disputed lines) for later release. 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. Anyone reconciling for a contractor paid by a Tier-1 civil or construction principal has lived this.
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, say, your trading company and your service company will hit two different Xero organisations on the same day.
Among Xero teams handling concentrated B2B receivables, labour hire, NDIS, construction, wholesale, partial-payment splits rank as a top-three reconciliation pain, behind only volume and remittance-format complexity. This is routine, not an edge case.
Why Xero on its own will not link them
Xero treats each bank deposit as an independent reconcilable line. The bank feed shows £35,000 on Tuesday and £15,000 on Thursday, and Xero 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." The remittance PDF itself isn't even a first-class object in Xero unless you attach it manually to a batch payment after the fact.
That means the job of working out which invoices on the remittance correspond to which deposit falls entirely on the bookkeeper or finance manager. And because most customers don't annotate the split (the remittance just lists 38 invoices in the order they were entered into AP), the reconciler is left to back-solve the allocation.
What the manual process actually looks like
For anyone who hasn't done this themselves, the workflow is unglamorous. 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, but the reconciliation itself, the part that creates the audit trail, still has to be posted by hand.
At a small client, this might cost 4 hours a month, which at a £25 per hour loaded bookkeeper rate is £100 a month (around A$120). At a high-volume firm running 400 remittances a month across multiple entities, the same problem at the same rate is 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, the choice comes down to which workaround you can stomach. Four of them show up in practice.
- 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. Clean audit trail, but front-loads the analytical work onto whoever is reconciling. Acceptable when the split is obvious (for example a clear retention release on a known schedule) and unbearable 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. This keeps the remittance intact as a single posting, but it muddies the bank reconciliation in the interim and requires 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. It's 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. Most finance teams default here 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. The trick is making sure suspense never becomes a black hole.
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. This is the territory where automation earns its keep. 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
A reasonable rule of thumb: 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 cross-entity routing problem (option above, multi-account or multi-entity) compounds.
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. Having the original remittance PDF attached to both batch payments, with the line allocation explicit, is the cheapest way to make that conversation a non-event.
How RemitClear handles split deposits
RemitClear does this the way you would by hand, only faster. It reads the remittance, matches every line against the open invoices 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 deposits arrive in tranches, you reconcile each bank line against the relevant subset of matched invoices rather than back-solving from a spreadsheet. 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. The manual cross-referencing disappears; the audit trail stays intact.
Summary
The mistake most teams make here is forcing the numbers. Under a Friday deadline they either jam the whole remittance against the larger deposit and let a suspense balance quietly rot, or they back-solve the split from a spreadsheet and mis-allocate a line nobody catches until an auditor does. Neither is laziness; both come from treating a routing problem as a matching one. 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 split is self-evidencing. 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.