When one remittance arrives as multiple bank deposits: reconciling split payments in Xero

Your customer sends a remittance for £50,000 covering 38 invoices. You go to reconcile it in Xero and the bank feed shows two deposits, £35,000 and £15,000, landing two days apart. The remittance does not tell you which invoices belong to which deposit. Welcome to one of the most common, least-documented frictions in Xero remittance matching.

Most guides treat a remittance as a one-to-one match: one PDF, one bank deposit, one batch payment. In practice, 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. This post walks through why it happens, what the manual reconciliation actually looks like, and the four realistic paths to a clean Xero record.

Why one remittance arrives as two (or more) deposits

It is worth understanding the underlying reasons before deciding how to fix the symptom. The pattern shows up across UK and Australian 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 Faster Payments, BACS files, or PayID 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 do not 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.

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 is no field on a Xero invoice or batch payment that says "this remittance was settled across these two bank lines." The remittance PDF itself is not even a first-class object in Xero unless you attach it manually to a batch payment after the fact.

That means the work of working out which invoices on the remittance correspond to which deposit falls entirely on the bookkeeper or finance manager. And because most customers do not 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 has not done this themselves, the workflow is unglamorous. A finance manager at one mid-size NDIS-adjacent provider described it like this: roughly 25 minutes to manually match the invoices on the remittance to open Xero invoices, then a further 40 minutes on the remainder when the bank deposit comes in lower than the remittance total and they need 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 £30 per hour loaded bookkeeper rate is £120 a month. 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

Once you accept that Xero will not link the remittance to multiple deposits for you, the question becomes which workaround you can live with.

1. 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 is not.
2. 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.
3. Lump-sum prepayment, then apply. Receive each deposit as a customer prepayment in Xero, then allocate against specific invoices when you have 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 is administratively heavier as invoice counts grow, because each deposit becomes its own allocation exercise.
4. Automate the matching and let the deposits sort themselves.The pragmatic path for any team running more than a handful of multi-deposit remittances per week. Match the remittance to the open Xero invoices once, identify which subset clears first based on 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 in Australia, public-sector contracts in the UK, 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

One soft product note. RemitClear 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, the same remittance can route to the correct Xero organisation automatically based on the invoices it touches. The manual cross-referencing disappears; the audit trail stays intact.

Summary

A single remittance arriving as multiple bank deposits is not an edge case. It is a recurring tax on any finance team handling concentrated B2B receivables in Xero, and it shows up across labour hire, NDIS, construction, and wholesale customer bases. Xero will not link the deposits for you, so you have four real options: match each deposit independently, use a suspense account, post lump-sum prepayments, or automate the underlying matching and let the deposit allocation fall out of it. The right answer is driven by frequency, predictability, and audit posture. For more on the underlying reconciliation workflow, see our guide on how to reconcile remittance advice in Xero, or the solution page for automated cash application in Xero.