Why will my batch deposit not match the bank line?

The batch total and the credit are not equal. The usual causes are a short paid line still carrying its invoiced amount, a negative line on the remittance that was skipped, or an invoice included that this run did not pay. Work back from the remittance total rather than from the invoice list, because the remittance total is the figure the bank credit was built from.

How many invoices can go in one Xero batch deposit?

The sources disagree and neither was confirmed against Xero for this page. ToTheCent's guide of 8 Jul 2026 states fifty per batch. RemitClear's guide of 23 Apr 2026 states two hundred and quotes the error a larger batch returns. A Xero App Store review read on 3 Sep 2026 describes 130 invoices posted as one batch payment. Build the batch, and split it if Xero refuses it.

Should I build the batch from the remittance or from the invoice list?

From the remittance. The remittance is the only document that agrees with the credit in the bank, so a batch built from it balances by construction. A batch built by ticking likely looking invoices has to be corrected against the remittance anyway, only later and with less to go on.

What do I do with a rejected claim inside the run?

Keep it out of the batch. A rejection that reverses a claim paid in an earlier run arrives as a negative line and is posted as a credit note against the original invoice, or as a reversal of that earlier payment. Treating it as a short payment inside this batch leaves the original invoice looking settled when it is not.

What date should the batch deposit carry?

The date the funder paid, which the remittance states. That closes every invoice in the run on the day the money actually moved, so the debtor ledger and the bank agree. Dating it on the day you do the reconciling makes a whole run of invoices look paid late.

Xero how to

Record a batch deposit from a remittance

Build the batch from the remittance, not from the Xero invoice list. Take the paid lines the remittance carries, collapse them to one amount per invoice, allocate each amount against that invoice in one batch deposit dated on the payment date, and check the batch total equals the credit in the bank feed before you match anything.

Key facts

What one batch deposit is: One Xero document that pays many invoices together and is tied to a single bank line, so the whole set reconciles against one credit³
What the batch total has to equal: The sum of the allocations inside it, so a short payment, a reversal or a withheld fee has to be dealt with before the batch is saved rather than after¹
Where the rows come from: The remittance file, collapsed to one paid amount per invoice, because a funder pays claim lines and the practice raised invoices⁶
Why the remittance total is a net figure: Rejected or clawed back claims arrive as negative amounts inside the run, so the total at the bottom is not the sum of the positive lines¹
Invoice cap, the first figure: ToTheCent's plan manager guide of 8 Jul 2026 states a cap of fifty invoices per batch and splits large runs to respect it¹
Invoice cap, the second figure: RemitClear's guide of 23 Apr 2026 states two hundred, and quotes the error a larger batch returns: a batch payment cannot contain more than 200 payments²
A batch size somebody reports posting: One review on the Xero App Store describes a remittance covering 130 invoices posted as a single batch payment⁵
When the deposit arrives split in two: Nothing in Xero records that one remittance was settled by two bank lines, so the split stays with the person reconciling³
The two legs a plan manager deposit touches: The settlement leg is 103 Plan manager clearing, coded BAS Excluded. The revenue leg is already on the invoice the deposit closes, at 405 Clinical services, NDIS plan-managed⁷
Order of work with a practice system: Splose tells Xero users to reconcile the lump sum in Xero against the remittance first, then mark the claim as finalised with no payment applied⁴

What a batch deposit is doing

A batch deposit is one Xero document that receipts many invoices together. You tick the invoices, Xero writes one payment against each one, and the whole set presents itself to the bank feed as a single amount. That is the shape a funder deposit already has: one credit in the bank, many invoices closed behind it.

The alternative is receipting each invoice on its own and then using find and match to tie a pile of payments to one statement line. That works, and some practice system integrations do it by default, but it fills the bank account in Xero with payments that no bank line produced. A batch deposit keeps the count honest: one document in, one line out.

Start from the remittance, not the invoice list

This is the part the generic answers skip. If you open the awaiting payment tab and start ticking invoices that look about right, you are guessing at what the funder paid. The remittance already holds the answer, line by line, and it is the only document that agrees with the credit in the bank.

The steps, in order

Outside Xero, in the funder or plan manager portal. Download the remittance as a file rather than working from the emailed PDF, so the paid amounts can be totalled instead of retyped.
Outside Xero, in a spreadsheet. Collapse the claim lines to one paid amount per invoice number, and set every negative line aside for separate treatment.
Sales, Invoices, Awaiting payment. Open the awaiting payment tab and filter to the funder's contact, so only that debtor's invoices are in view.
Sales, Invoices, Awaiting payment. Tick the invoices the remittance paid and start a deposit, which opens a batch carrying one row per invoice.
New batch deposit. Set the payment date to the date the funder paid, which the remittance states, rather than to the day the work is being done.
New batch deposit. Edit any row the funder paid short so it carries the paid figure rather than the invoiced figure, and note the balance for later.
New batch deposit. Check the batch total against the credit sitting in the bank feed before saving, because the statement line matches the batch only when the two are equal.
Accounting, Bank accounts, Reconcile. Open the bank account, find the credit, and match it to the saved batch, so one statement line settles the whole set.

The batch total has to equal the deposit

Xero matches a statement line to a batch when the amounts are equal. There is no tolerance to lean on, so anything that made the money smaller than the invoices has to be handled inside the batch or outside it before the batch is saved. That is the whole discipline, and it is why building from the remittance is faster than correcting afterwards.

Plate 1An illustrative plan manager remittance built into one batch deposit, with the short paid invoices allocated at the figure the remittance actually paid.

What makes the two totals differ

Four things account for most of the gap between what you invoiced and what landed. Each one has a different home in the batch, and putting a reversal where a short payment belongs is how a clearing balance quietly stops clearing.

Why the invoice total and the deposit rarely agree¹⁶

What happened	How it shows on the remittance	What the batch carries
The funder approved less than you invoiced	A paid amount lower than the claimed amount on the same line	The paid amount, with the balance left open or written off separately
A claim paid in an earlier run was reversed	A negative line netted against this run's total	Nothing, because a reversal is posted as a credit note against the original invoice
One invoice was claimed as several support items	Several rows carrying the same reference	One allocation, once the rows are collapsed to one amount per invoice
The funder changed the reference on the way back	Your invoice number with a system identifier appended to it	The invoice your known number is a prefix of

How many invoices fit in one batch

Two guides that both sell remittance matchers state two different ceilings, and neither figure could be confirmed against Xero's own documentation for this page. Rather than pick one, here is what each says and when it said it.

What the sources say about the invoice cap¹²⁵

Source	Dated	The figure it states
ToTheCent, plan manager remittance guide	8 Jul 2026	A cap of fifty invoices per batch, with large runs split to respect it
RemitClear, batch payment limit guide	23 Apr 2026	Two hundred payments, quoted as the error a larger batch returns, and described as enforced through the interface, a CSV import and the payments API alike
A review on the Xero App Store listing for RemitClear	Read 3 Sep 2026	A remittance covering 130 invoices posted as one batch payment

The practical answer does not depend on which figure holds. Build the batch, and if Xero refuses it, split the remittance into two batches dated the same day. The one credit in the feed then has to be split as well, so that each part meets the batch it belongs to and the two parts add back to the credit. A plan manager run can pass 500 rows, so this is a normal part of the job rather than an error.

When one remittance settles across two bank lines

The harder case is the reverse of the one above: one remittance, one batch you could have built, and two credits in the bank because the funder released the money in parts. RemitClear puts it plainly, that Xero treats each bank deposit as an independent reconcilable line and holds no field on an invoice or a batch saying a remittance was settled across two of them.

Split the batch to match the money. Build one batch per credit, each holding the invoices that credit actually paid, so each statement line has an exact partner.
Hold the difference. Post the whole remittance against the first credit and park the balance somewhere visible until the second lands, which keeps the debtor ledger right and moves the problem to one account you can see.
Receive on account. Take each credit as a payment on account against the funder and allocate it to invoices afterwards, which suits a funder that pays on its own rhythm rather than per remittance.
Whichever you pick, write down which one this practice uses. The cost of a split deposit is rarely the posting; it is two people solving it differently in the same ledger.

Dates, and what the batch does to aged receivables

A batch deposit closes its invoices on the payment date you give it, so the date is a reporting decision rather than a formality. Date the batch on the day the funder paid and the debtor ledger tells the truth about when the money moved. Date it on the day you did the work and every invoice in the run looks as though it was paid late.

There is a consequence worth naming. Because the invoice stays open until the money lands, aged receivables carry the whole claim through the funder's lag. For a funder that pays days after adjudication that reads correctly. For a claim a fund approved at the counter it overstates what you are owed, which is one of the reasons a clearing account is the better fit for some rails.

The clearing account alternative

A batch deposit and a clearing account answer the same question differently. The batch closes invoices on the day the bank credit arrives. A clearing account closes them on the day the funder approved the claim, and then the bank credit is matched as a movement out of that account.

The allied health template gives each rail its own clearing account, and the plan manager rail lands on 103 Plan manager clearing, coded BAS Excluded.
The revenue and its tax rate belong to the invoice line, not to the clearing leg, so the two legs are set separately and stay that way.
A clearing balance that will not return to nil is a claim approved but not banked, or banked but not matched, and both are worth chasing while the remittance is still open.
The batch deposit route needs no new accounts, which is why it suits a practice with one funder and a short lag.

What an allied health remittance adds

A funder pays claim lines, some short, some reversed, under a reference it changed on the way back. Almost all of the work sits before the batch screen opens, in turning a claim line file into one paid amount per invoice.

The payoff is visible in what practitioners say about it. One reviewer describes a remittance covering 130 invoices posting as a single batch payment, leaving one bank line to reconcile instead of 130. That is the difference the batch makes: the matching work is the same either way, but the reconciliation stops being 130 separate decisions.

If you are using the Xero integration, reconcile the lump sum payment from the NDIS in Xero using the NDIS remittance PDF. Once all invoices are paid in Xero: Under Actions, click Mark as finalised.⁴

What Ledger Map does with a remittance

Ledger Map holds one standing map for the practice, approved before anything syncs. It does not auto reconcile. It reads the remittance, resolves each line to the account and tax rate the approved map names, posts one balanced document set for the deposit, and leaves one exact match in the bank feed for a person to accept. A line the map cannot resolve becomes a question with the options laid out, not a silent posting.

Nothing on this page is a treatment Ledger Map picked. The accounts and tax rates come from the canonical template a practice starts from. If you want the steps either side of this one, find and match covers the manual route, how a plan manager pays covers where the money and the file come from, and the product walkthrough shows the map and the question queue.

Questions

Why will my batch deposit not match the bank line?
The batch total and the credit are not equal. The usual causes are a short paid line still carrying its invoiced amount, a negative line on the remittance that was skipped, or an invoice included that this run did not pay. Work back from the remittance total rather than from the invoice list, because the remittance total is the figure the bank credit was built from.
How many invoices can go in one Xero batch deposit?
The sources disagree and neither was confirmed against Xero for this page. ToTheCent's guide of 8 Jul 2026 states fifty per batch. RemitClear's guide of 23 Apr 2026 states two hundred and quotes the error a larger batch returns. A Xero App Store review read on 3 Sep 2026 describes 130 invoices posted as one batch payment. Build the batch, and split it if Xero refuses it.
Should I build the batch from the remittance or from the invoice list?
From the remittance. The remittance is the only document that agrees with the credit in the bank, so a batch built from it balances by construction. A batch built by ticking likely looking invoices has to be corrected against the remittance anyway, only later and with less to go on.
What do I do with a rejected claim inside the run?
Keep it out of the batch. A rejection that reverses a claim paid in an earlier run arrives as a negative line and is posted as a credit note against the original invoice, or as a reversal of that earlier payment. Treating it as a short payment inside this batch leaves the original invoice looking settled when it is not.
What date should the batch deposit carry?
The date the funder paid, which the remittance states. That closes every invoice in the run on the day the money actually moved, so the debtor ledger and the bank agree. Dating it on the day you do the reconciling makes a whole run of invoices look paid late.

Sources

Open questions

Neither invoice cap figure is confirmed against Xero. Xero Central and the Xero developer documentation both returned nothing readable to an automated fetch on 3 September 2026, on the batch deposit article, the reconcile a batch payment article and the batch payments API page.
The two vendor guides disagree. ToTheCent states fifty per batch on 8 July 2026 and RemitClear states two hundred on 23 April 2026. The research corpus already records that the fifty figure rests on a Xero Central question title rather than on an article body, and that question page is listed here as unverified for the same reason.
Whether the two guides describe the same object is unsettled. The ToTheCent guide batches invoices and does not use the words batch payment anywhere, while the RemitClear guide is about batch payments throughout, and Xero uses both words.
Whether one bank statement line can be matched against two saved batch deposits was not confirmed against Xero's own documentation, so the split remittance section states the arithmetic the two batches have to satisfy rather than a screen sequence.
The Xero screen names in the step list rest on the research corpus rather than on a fresh read of Xero Central, for the same reason.
The current answer landscape was not sampled. The session's web search budget was spent, and three attempts to read a results page directly on 3 September 2026 returned either nothing or results for a different query, so the top five for the target query and what an answer engine cites today were not read.
The Xero App Store review that describes a batch of 130 invoices carries no visible date on the listing, and it is a review on a vendor's own product page rather than an independent report.

Reconcile NDIS plan manager remittances in Xero
ToTheCent. Retrieved 3 Sep 2026. Source updated 8 Jul 2026.
secondary
Xero's 200 invoice batch payment limit
RemitClear. Retrieved 3 Sep 2026. Source updated 23 Apr 2026.
secondary
Reconciling a remittance settled across two bank deposits in Xero
RemitClear. Retrieved 3 Sep 2026. Source updated 25 May 2026.
secondary
NDIS bulk upload
Splose. Retrieved 3 Sep 2026. Source updated 2 Aug 2026.
primary
RemitClear on the Xero App Store, customer reviews
Xero App Store. Retrieved 3 Sep 2026.
secondary
NDIS remittance processing in Xero
RemittanceGo. Retrieved 3 Sep 2026. Source updated 2 Jun 2026.
secondary
The canonical configuration templates, allied health by funding source
Ledger Map. Retrieved 3 Sep 2026.
primary
Batch deposits for more than 50 invoices, a Xero Central question
Xero Central. Retrieved 3 Sep 2026.
unverified
Record payment of a sales invoice
Xero Central. Retrieved 4 Sep 2026.
primary

Review

Last reviewed 3 Sep 2026 by Shane

General information for Australian allied health practices, not tax advice. Confirm a treatment with your BAS agent or accountant before you post it.

Guided onboarding

Run one real month before you go live.

Sign up, connect Zanda and Xero, and replay a month you already closed. The map is reviewed with whoever owns the books, and nothing posts until you approve it.

Start your map

Every practice starts from a template. Nothing posts until the map is approved.