Xero will not let a single batch payment cover more than 200 invoices. Try it with a 500-invoice remittance from one of your biggest customers and you get a flat refusal: "A batch payment cannot contain more than 200 payments." It's a hard ceiling, enforced at the API level, and it turns one of the most routine acts in AR, matching a customer's payment to the invoices it covers, into a problem you have to design around.
The cap can't be lifted by Xero support, by your Xero partner, or by any app in the marketplace. If a single customer pays you against more invoices than that in one remittance, something in your process has to change.
What the 200-invoice limit is
Xero's batch payment feature lets you group multiple sales invoice payments into a single bank transaction. It's the natural Xero-side counterpart to a customer remittance, one deposit on the bank statement and many invoices marked paid. A single batch payment can't reference more than 200 invoices. The same limit applies whether you build the batch manually through the Xero UI, import it via CSV, or post it through the Xero Payments API. Xero support has confirmed this is enforced at the platform level.
The cap is a performance and data-integrity decision on Xero's side, and the consequence for you is that any customer who pays you against more than 200 invoices in a single remittance has broken your one-to-one mental model of "remittance equals batch payment."
Who hits this limit
Most Xero users never bump into the 200 cap, which is part of why it's such a shock when it happens. The people who do hit it cluster into a few predictable profiles.
Facilities contractors paid by grocery chains
A mid-size facilities or utilities supplier serving a national grocer is the textbook case. The contractor invoices each store in a supermarket estate individually, then receives a single remittance covering every store-level invoice for the period. When the customer is a brand like Morrisons, Asda, Sainsbury's, or Tesco and the supplier is posting one or two invoices per store per week, you can cross 500 invoices in a single remittance without doing anything unusual. A single Morrisons remittance to one facilities contractor can carry between 500 and 900 invoices.
Multi-entity labour hire and civil contractors
Labour hire firms in civil and mining invoice major principal contractors weekly for each placement. A major principal contractor might pay a single weekly remittance that clears 200 to 500 separate invoices, one per person per project. Retentions and partial payments make these remittances even harder to reconcile, because the remittance total doesn't match the gross invoice total. One contractor in this vertical runs around 400 remittances per month across 8 Xero entities, with the largest single remittance sitting above 500 lines.
NDIS providers receiving NDIA bulk remittances
NDIA payments to providers are the Australian disability sector's version of the same structural problem, since the agency pays in bulk against many participant-level invoices on a fortnightly cycle. Larger providers routinely receive remittances of 200-plus lines. This also applies downstream to plan managers, who consolidate service-provider invoices and pay them on behalf of participants. We cover this case in depth on the NDIS remittance reconciliation solution page.
Wholesale and distribution suppliers
Any wholesale supplier invoicing weekly to a handful of large retailers or chain customers can run into this without being anywhere near enterprise scale. A £2-5m-turnover wholesaler with one or two chain customers paying fortnightly across every depot can easily land a 250-line remittance and discover the cap.
If one of your top five customers pays you more than 200 invoices in a single remittance, the cap comes back every week the remittance lands, and no amount of process tweaking inside Xero alone will remove it.
The four ways people deal with it
Once you accept that one remittance can't become one Xero batch payment, the job is choosing the compromise you can most live with, and four of them show up in practice.
- Split the remittance into 4 (or more) batch payments. The standard Xero workaround. You take a 600-invoice remittance, break it into three groups of 200, and post three separate batch payments summing to the total. The bank transaction line still needs to be reconciled against the sum, so you end up allocating the deposit across multiple Xero receipts. This works if your team accepts the extra steps and the audit trail stays clean, and it goes badly if the CFO expects a single reconciled receipt matching the single bank credit.
- Invoice in aggregate instead of per-line. Some suppliers dodge the problem by consolidating multiple services into summary invoices, so the count per remittance stays under 200. This only works if your customer will accept the aggregated format. Most chain retailers and principal contractors insist on line-item invoicing for their own reasons (cost coding, internal approvals, retention tracking), so it's rarely an option in practice.
- Reconcile the deposit as a single receipt and then allocate invoices manually. Rather than use batch payments at all, some teams post the remittance as a lump-sum customer prepayment, then apply it to invoices one receipt at a time. This gets you the single-receipt reconciliation the CFO wants, but it destroys any audit trail that ties the specific invoice lines to the remittance PDF, and it becomes administratively heavier as invoice counts grow.
- Automate the matching and accept the split. For most high-volume teams this is the one that holds up. You accept that Xero will need multiple batch payments for a single customer remittance, but you remove the manual cross-referencing that eats hours every week. Tools that match remittance PDFs to open Xero invoices automatically (by invoice number, amount, and reference) can do in 30 to 60 seconds what a bookkeeper does in 2 to 4 hours, and then post the resulting batches back to Xero in one click, respecting the 200-line split automatically.
How to decide which route fits you
There's no universal right answer. The decision is driven by three things: who owns the reconciliation, how much your finance team's time is worth, and how strict your audit requirements are.
Start with volume. If you're running 10 or fewer oversized remittances per month, splitting manually is annoying but survivable. If you're running 50 or more, the cumulative time cost makes automation the obvious call. A finance manager spending 2 hours per mega-batch remittance at 50 per month is giving up 100 hours a month, which at a £25 per hour loaded bookkeeper rate is around £2,500 a month of time, or roughly £30,000 a year (about A$36,000 a year).
Then consider the receipt structure your CFO expects. Some finance leaders insist on a single bank receipt matching one reconciled document. Others are perfectly comfortable with a remittance that splits into 4 batches as long as the total reconciles to the deposit and the PDF sits against each batch as evidence. This preference is usually the deciding factor between options 3 and 4 above. If you're in a fit-for-audit environment (grant-funded, NDIS billing, public-sector contracts) you'll want the audit trail that comes from linking remittance documents directly to the batch payments.
Finally, check your contract structure. If you have one or two very large customers generating 90 percent of the mega-batches, it's worth a quiet conversation with their AP team about how they build the remittance. Some will agree to send a remittance per depot, per week, or per cost centre, which keeps individual counts below 200 without changing your invoicing, and others won't move. Knowing which is which saves you trying to fix the problem on the wrong side.
When the 200 limit is a signal to walk away from Xero
It's rare for the cap to be a reason to leave Xero, but if a single customer routinely sends you remittances of 1,000-plus invoices, and your CFO won't accept any form of split-receipt reconciliation, and the customer won't change their remittance format, you may simply have outgrown Xero for that workflow. Most businesses who hit this are at the upper end of Xero's natural fit and are often already evaluating NetSuite or similar. The batch cap on its own isn't a reason to migrate, though it's a fair prompt to check whether you're at the platform boundary for other reasons too.
How RemitClear handles the cap
RemitClear handles the cap for you. Its Xero remittance matching reads the remittance, matches every line against open Xero invoices, and posts the result back as a Xero batch payment, or as multiple batch payments split at the 200-line boundary where that's required, with the original remittance PDF attached to each batch. You still end up with more than one Xero transaction for a 500-line remittance, and the manual cross-referencing disappears while the audit trail stays clean. If your team can live with a multi-batch receipt, that's the quickest route through. Where one receipt per remittance is required regardless of line count, Xero itself is the constraint and no Xero add-on can fix that.
"Matching those by hand in Xero was slow and constantly ran into Xero's 200-invoice batch limit. RemitClear reads each remittance, matches every invoice and posts straight into Xero, splitting the large batches automatically. In our first six weeks it reconciled over 2,100 invoices for one client alone."
Summary
The cap mostly bites concentrated, high-frequency customer bases, grocery suppliers, labour hire firms, NDIS providers and wholesale distributors. Pick the workaround on volume, on the receipt structure your CFO expects and on your audit exposure, rather than muscling a 600-line remittance into groups of 200 by hand under a month-end deadline, or forcing a single receipt with a lump-sum prepayment that cuts every invoice loose from its remittance PDF, both of which cost more time and leave a worse audit trail than the cap itself does. The wider reconciliation workflow is covered in our guide on how to reconcile remittance advice in Xero, or the solution page for multi-invoice payment matching in Xero. If your AR work currently sits with an offshore team, our breakdown of offshore AR teams versus Xero automation covers when the maths flips toward bringing matching back in-house.
