What is the difference between an overpayment and a prepayment in Xero?

Both leave a credit balance on the customer's account in Xero, but the timing differs. An overpayment arises when a customer pays more than the invoice amount. A prepayment is received before any invoice is raised. The distinction matters for VAT: on prepayments for undelivered goods or services, the VAT point may differ from when you actually invoice. Either way, the credit sits on the account until you manually apply it to a future invoice — Xero will not apply it automatically.

Can Xero bank rules automatically split a payment across multiple invoices?

No. Xero bank rules match on the description string of a bank statement line — the payee name, reference, or narrative — and code it to an account or contact. They have no access to your open invoice ledger and cannot solve the arithmetic of which invoices a payment covers. For any payment that needs allocating across multiple invoices or leaving a partial balance, bank rules provide no help. The split must be done manually through Find & Match.

What happens if I forget to apply a prepayment in Xero before year-end?

The credit sits on the customer's account indefinitely and does not auto-apply. At year-end your accountant will typically find unresolved prepayment credits on the aged debtors report — the invoice shows a balance still outstanding even though cash was received months earlier. This distorts your debtors figure and can cause VAT return errors if the supply has since been delivered. Applying the credit before the period closes keeps your books accurate.

What does the Split button in Xero bank reconciliation actually do?

When reconciling a bank statement line via Find & Match, the Split button lets you allocate part of the line's amount to one transaction and handle the remainder separately — for instance, £1,100 to one invoice and the balance to another. The Split button only appears for unreconciled lines. If you have already marked a line as reconciled by mistake, you must use Remove & Redo to reopen it before the Split option becomes available again.

How do I handle a BACS payment that covers multiple invoices in Xero?

In Find & Match, select the relevant invoices by ticking them individually. If the combined total of the ticked invoices equals the bank line exactly, Xero will reconcile all of them in one step. If the total is less than the bank line, click Split to allocate the remainder as a part payment or prepayment. If you have a remittance advice from the customer, use it to confirm which invoices are being settled before posting — especially where two combinations of open invoices could produce the same total.

What a Split Transaction Is (And Why Xero Struggles)

Q: Does JAX, Xero's automatic reconciliation, handle split transactions?

JAX handles clean, recurring single-line matches well — direct debits, standing orders, repeat supplier payments — and improves over time by learning from your reconciliation history. However, it cannot decompose a single deposit into multiple invoice settlements plus a prepayment, because that breakdown is not present in the bank data itself. A remittance advice or invoice arithmetic is needed to resolve ambiguous splits, and JAX leaves those lines for manual review. This applies to UK Grow-plan-and-above organisations, where JAX is currently rolling out.

A single £4,200 deposit lands in your Xero bank feed. A customer has sent it to clear two invoices in full, knock £700 off a third, and leave the rest sitting on account for next month. Xero sees one line. Your books need four distinct postings. You click Find & Match, tick the first invoice, notice the amount doesn’t balance, start again, click Split, enter £1,100, click Split again, frown at the prepayment and wonder whether to create a receive money or an overpayment.

Fifteen minutes later you’ve got something that looks right. Whether it is right depends on how well you know Xero’s prepayment model — and on whether you remember to apply that credit balance before the quarter closes.

This is a split transaction. Xero can handle it, technically. But it does not make it easy, and it absolutely does not do it for you.

What a Split Transaction Actually Is

A split transaction is any bank statement line that must resolve to more than one accounting event. The term is broader than most founders realise. Here are the shapes it takes in practice:

One payment, multiple invoices

A customer sends £3,800 to settle invoice 1041 (£1,100), invoice 1044 (£1,650), and invoice 1048 (£1,050). Three invoices, one bank line, three payment records to create and match.

One payment, partial settlement

A customer pays £2,500 against an invoice for £3,200. The bank line is reconciled, but £700 remains open on the invoice. Xero calls this a part payment. The invoice stays in “Awaiting Payment” at the reduced balance.

Partial settlement plus prepayment

This is the one that trips people up. A customer pays £4,200. Invoice 1041 is £1,100, invoice 1044 is £1,650, invoice 1048 is £900 (partial), and the remaining £550 is for work not yet invoiced. That £550 must become a prepayment or overpayment in Xero — not a payment against any specific invoice — and must sit on the customer’s account until you apply it.

Settlement plus write-off

The invoice is £2,500 but the customer pays £2,460 and expects the balance written off. The bank line reconciles to the partial payment plus a small bad debt or discount posting.

Each of these has a mechanically correct route through Xero. None of them is handled by Xero’s bank feed automatically, and only one of them — the simplest — is something JAX, Xero’s AI-powered auto-reconciliation layer, will attempt to resolve without your involvement.

Why Xero’s Default Model Strains Here

Xero’s bank reconciliation is built around a one-line-one-match assumption. You see a bank statement line; you find or create one transaction to match it. That model works for the majority of transactions: a direct debit for your hosting bill, a standing order to your landlord, a single customer payment that exactly matches the invoice. It is a sensible default.

The strain begins the moment the amounts don’t align.

Where JAX’s auto-reconciliation reaches its limit

JAX, Xero’s automatic bank reconciliation, released in beta in 2025 and rolling out to Grow-plan-and-above UK organisations through 2026, takes this a step further. It uses a multi-layered approach: direct matching, bank rules, and learned patterns across up to 5,000 prior reconciliations. For clean, recurring transactions it performs well — a direct debit that arrives on the same date from the same payee every month is exactly the kind of pattern JAX was built for.

But JAX’s confidence model works on the statement line. A £4,200 deposit from a known customer doesn’t carry a breakdown of which invoices it covers. JAX cannot decompose it into three invoice settlements plus a prepayment, because that breakdown isn’t in the bank data — it’s in the customer’s accompanying remittance advice, or in the fact that those four amounts happen to sum to £4,200, or in an email the customer sent yesterday. JAX leaves the line for you to review manually.

What Find & Match requires you to know

Xero’s Find & Match gives you the manual route: click through to the transaction, tick the invoices you want to settle, click Split if the total doesn’t balance, record the remainder as a part payment or prepayment. It works. It also requires you to know:

That the Split button only appears for unreconciled transactions — if you’ve accidentally marked something reconciled first, you’ll need Remove & Redo
The difference between an overpayment and a prepayment in Xero’s model (both leave a credit balance on the customer account; the distinction matters for VAT timing on prepayments for undelivered goods or services)
That the prepayment or overpayment you create today will sit invisibly on the customer’s account until you explicitly apply it to a future invoice — it doesn’t auto-apply

Why bank rules don’t help

Rule-based tools — Xero’s own bank rules, or third-party matching products — don’t close this gap. A bank rule can code a line from a known supplier to the right account. It cannot decompose a payment into three invoice settlements and a prepayment, because rules operate on the description string, not on the arithmetic relationship between the payment and the open invoice ledger.

The result: split transactions are manual work, every time.

How TheBookkeeper.ai Handles It

The output is simple to describe. You wake up, the £4,200 line is reconciled, invoices 1041 and 1044 are closed, invoice 1048 shows the correct partial balance, and the £550 prepayment is sitting on the customer’s account with a note explaining it. One item is flagged for your attention: the prepayment needs to be applied once the next invoice is raised. That’s it.

What happened behind the scenes:

Reading the open invoice ledger

TheBookkeeper.ai reads your unreconciled bank feed lines via Xero’s API alongside your open invoice ledger. It sees the £4,200 deposit and the four open invoices for Slate Badger Ltd — £1,100, £1,650, £900, and the fact that their account balance suggests an advance payment is expected.

Decomposing the payment

It solves the arithmetic: which combination of open invoices explains this amount? Two full settlements (£1,100 + £1,650 = £2,750) plus a partial settlement of the £900 invoice (£700 paid, £200 remaining) plus £550 left over. The combination is unambiguous — no other set of open invoices sums the same way.

Checking for context

If the arithmetic were ambiguous — say two invoices happen to share the same amount — TheBookkeeper.ai checks the email inbox (if connected) for a remittance advice. It checks the notes on the Xero customer account. It checks whether any invoice has a reference in its description that matches the bank line narrative.

Posting to Xero

It creates three payments — one against invoice 1041, one against 1044, one partial against 1048 — and applies them to the bank statement line as a split reconciliation. It creates a prepayment for £550 on Slate Badger Ltd’s account, with a narration explaining the origin. The bank line is reconciled. The invoice ledger is correct.

Flagging the residual

It sends a single notification: “£550 prepayment created for Slate Badger Ltd. Apply this credit when you raise invoice 1061.” You don’t have to remember — the flag is there.

What it will not post without your input: if the arithmetic yields two equally plausible invoice combinations, it surfaces both and asks you to confirm. If the customer account had a dispute note, it flags that before posting. Genuinely ambiguous cases get flagged; clear cases get posted.

Worked Example

The scenario

Slate Badger Ltd is a consultancy client of Green Puffin Ltd, a UK digital agency using Xero. On Thursday 4 June, Green Puffin’s Barclays current account receives a single BACS deposit of £4,200.00 from Slate Badger Ltd. Green Puffin has three open invoices to Slate Badger: INV-1041 for £1,100, INV-1044 for £1,650, and INV-1048 for £1,450.

The Xero state before

The bank feed shows one unreconciled line:

Date         Description                   Spent    Received      Status
04 Jun 2026  BACS SLATE BADGER LTD                  £4,200.00     Unreconciled

In the Invoices → Awaiting Payment view:

INV-1041  Slate Badger Ltd  £1,100.00   Due 31 May
INV-1044  Slate Badger Ltd  £1,650.00   Due 31 May
INV-1048  Slate Badger Ltd  £1,450.00   Due 14 Jun

The three invoices total £4,200.00 — but the assignment isn’t obvious, because £4,200 also equals INV-1041 + INV-1044 + £1,450 (the full third invoice) with nothing left over. Or it equals INV-1041 + INV-1044 + £700 partial on INV-1048 + £550 prepayment. The right answer depends on what Slate Badger intended.

What TheBookkeeper.ai does

Reads the £4,200 unreconciled line and the three open invoices.
Identifies two arithmetic solutions: full settlement of all three invoices (if INV-1048 is £1,450) or full settlement of INV-1041 and INV-1044 plus partial on INV-1048 plus prepayment.
Checks the email inbox: a remittance advice from Slate Badger (sent Wednesday) lists “INV-1041: £1,100, INV-1044: £1,650, INV-1048: £900, advance for July: £550.” Ambiguity resolved.
Posts two full invoice payments (INV-1041, INV-1044), a partial payment of £900 against INV-1048, and a prepayment of £550 on the Slate Badger customer account. All four are applied as a split reconciliation to the £4,200 bank line.
Reconciles the bank line.
Sends one flag: “£550 prepayment held for Slate Badger Ltd — apply when INV-1061 (July retainer) is raised.”

The Xero state after

Date         Description                   Spent    Received      Status
04 Jun 2026  BACS SLATE BADGER LTD                  £4,200.00     Reconciled ✓

INV-1041 and INV-1044 show Paid. INV-1048 shows “Awaiting Payment — £550.00 remaining.” The Slate Badger customer account has a £550 prepayment credit, with a narration: “Advance payment per remittance 04 Jun 2026. Apply to INV-1061.”

What it flagged

One item in the morning notification: the £550 prepayment needs to be applied to the July invoice when raised. No decision required today. Total founder time: reading the notification (under a minute).

If the email inbox had not been connected and the arithmetic had two solutions, the notification would have read: “Two plausible splits for £4,200 Slate Badger payment — confirm which matches the remittance.” The operator resolves it in one tap.

Takeaway

A split transaction is any bank line that must resolve to more than one accounting event: multiple invoice settlements, partial payments, prepayments, or a mix.
Xero’s Find & Match can handle splits manually, but requires step-by-step navigation — the Split button, the prepayment versus overpayment distinction, and the manual credit application later.
JAX, Xero’s AI reconciliation layer, handles clean single-line matches confidently and improves with pattern learning — but cannot decompose a mixed-settlement payment because the breakdown isn’t in the bank data.
Rule-based tools add nothing here: rules match description patterns, not invoice arithmetic.
The prepayment step is the one most likely to be missed: it sits silently on the customer account until explicitly applied, and year-end accountants regularly find unresolved prepayment credits from months prior. See also what your accountant fixes at year-end — unmatched credits appear on that list consistently.
Solving it properly requires reading the open invoice ledger, resolving the arithmetic (or checking the remittance), posting the split correctly, and flagging the residual for later action. For a post on where Xero’s rule-based matching gives up more broadly, see Why Rule-Based Reconciliation Breaks on Real Businesses.

Get on the waitlist

If your bank feed regularly lands deposits that need to be split across open invoices, we’d like to reconcile them for you. Get on the waitlist and we’ll reach out when we open the next UK Xero cohort.

Sources: