Reconcile customer remittance advice against your open Xero invoices, line by line.
A customer pays twenty invoices with one bank transfer and emails you a remittance advice listing them. Someone still has to open that document and allocate the payment across the invoices it covers. AutoRemit reads the advice, matches each line to an open Xero sales invoice, scores the match, and holds anything it is unsure about for a person.
No credit card required during the trial period. Xero only.
One payment, twenty invoices, and one document standing between them.
If you invoice on account, your money does not arrive invoice by invoice. It arrives in batches. A plan manager, a hospital group, a distributor or a government payer runs its payment cycle, pays everything it owes you in one transfer, and sends a remittance advice that lists what the transfer covered.
That advice is the only document connecting the deposit to your invoices, and it is the worst possible format for the job:
- It is a document, not data. A PDF, a scan, or the body of an email. Sometimes a screenshot of a portal.
- The layout changes for every payer — and sometimes between runs from the same payer.
- The invoice references are unreliable. Truncated, prefixed with the payer's own numbering, listed against a purchase order instead, or simply absent.
- The bank reference rarely matches the advice. One payer identifier goes on the remittance, something shorter and reshaped reaches your bank statement, and neither is your invoice number.
- Part payments hide inside otherwise clean batches. Nineteen lines pay in full, one pays short, and the batch no longer balances against the deposit.
Unless something reads the advice for you, the work falls to a person: open it, find each invoice in Xero, record a payment against it, repeat. Twenty lines is half an hour of careful transcription. Two hundred lines across six payers is a day that has to happen again next week, and every line is an opportunity to allocate to the wrong invoice — which becomes a customer chasing an invoice they have already paid.
Two directions, one phrase — which one this page is about.
Search for remittance advice and Xero together and most of what comes back is the payables side. Xero's remittance-advice workflow is primarily about the advice a business sends when it pays a supplier bill: money going out, and a document Xero produces for you.
AutoRemit is built for the opposite direction — remittance advice received from customers, where the document's line items need to be matched against your open Xero sales invoices. It arrives as a PDF, an image or the text of an email, in whatever layout the payer uses, and its lines have to be reconciled against invoices already sitting in your ledger.
The two get confused constantly, and the confusion matters, because the tooling for one does nothing for the other. If you want to send remittance advice to your suppliers, Xero already does that and AutoRemit is not what you need. If you want to act on the remittance advice your customers send you, keep reading.
From an advice in your inbox to a payment in Xero.
Every remittance takes the same path, and you decide where the automation stops and a person starts. AutoRemit was tested against real plan-managed NDIS remittances — many participants, many invoices, one payment — which is the hardest version of this shape. If that is the remittance you are reconciling, the NDIS version of this page covers what changes.
The advice arrives
Your organisation gets a private inbound address. Forward the email — or ask the payer to send it there directly — and the attachment or the message body is picked up. You can also drop a PDF or an image straight into the app.
Every line is read
The document is read to pull out the payer, the payment amount, the payment date and the invoice references on each line. This runs through Amazon Bedrock within Australian AWS regions, using its Australian geographic inference profile.
Lines are matched to open invoices
Each extracted line is matched against your outstanding Xero sales invoices — reference, amount, payer and contact together. Every match carries its own confidence score, not one score for the whole document.
Uncertainty is held, not resolved
Anything below the confidence bar you set is referred for review rather than posted. You see what was read, what it was matched against, and why it was uncertain. Invoices that are not in Xero at all are flagged as exactly that.
Posting happens on your terms
Confirmed matches are held and posted the day after the remittance, at a time of day you choose — Xero does not expose bank feeds to connected apps, so this approximates the deposit's arrival. You can post a single payment or the whole remittance.
The trail stays attached
The original remittance document is attached to the payment record in Xero, and the payment carries a Smart reference. Alongside it, AutoRemit keeps its own record of how each line was decided — matched, held, overridden or posted — searchable, and exportable to CSV when an auditor or a customer wants to see the working.
What happens when the reference is missing or wrong.
Matching on the invoice number is easy and rarely sufficient. The reference on a remittance line is frequently not your invoice number, because one remittance covers many payments and the payer numbers the batch its own way. So the invoice number is one signal among several, not the whole match:
- The payer narrows the candidate invoices to one customer's outstanding balance before anything else is compared.
- The line amount against each open invoice's balance, which resolves most references that are absent or unrecognisable on their own.
- The payer's own reference, kept as its own field and scored against the match rather than overwritten.
- The remainder. A line that pays part of an invoice is presented as a part payment. Nothing is rounded, split or invented to make the batch balance.
Where those signals agree, the match is proposed with its reasoning visible. Where they do not, the line drops below your confidence bar and waits. This is the design decision that matters most on this page: a remittance line that cannot be matched confidently is held, not guessed. A wrong allocation is worse than an unallocated payment, because nobody goes looking for it.
Automation that stops rather than guesses.
Four situations account for nearly every remittance that does not reconcile cleanly. Each one has a defined behaviour, and none of them is “post it anyway”.
The match is not confident enough
The line is held and referred for review instead of posting. You see what AutoRemit read, what it matched against, and why it was unsure — then you confirm, correct or reject it.
The invoice reference does not exist
An invoice on the advice that has no counterpart among your outstanding Xero invoices is flagged as not in Xero. It is not matched to the nearest similar invoice, and it does not silently disappear from the remittance.
Only some of the invoice is paid
A short line is identified as a part payment rather than rounded or redistributed, and it waits for you: it is not posted automatically as part of an otherwise clean remittance, and while the treatment is unconfirmed nothing on that remittance posts on its own. Confirming the part payment settles how the line is treated, not that the money moves: the remittance then returns to the normal posting step, and only once you approve that posting plan is the remitted amount recorded against the Xero invoice, with the balance left outstanding where your aged receivables can still see it. The difference is never closed by rounding, by splitting the amount across other invoices, or by adding a line that was not on the advice.
The money may not have landed yet
Xero does not expose bank feeds or their timing to connected apps, so AutoRemit approximates: a confirmed match is held and posted the day after the remittance, at a time of day you choose. On a batch remittance that matters more than usual, because the whole deposit clears as one line — if the feed runs late, the payment waits in Xero until it appears.
Every decision is logged. Match, hold, override and post — each one is on the record, with searchable history and CSV reports. Role-based permissions decide who can review and who can post; two-factor sign-in is available.
A payment your bank feed can actually recognise.
Allocating the invoices is only half the job. The payment still has to be recognisable when it turns up in the bank feed, and a batch remittance makes that hard: the number on the advice, the text that reaches your statement and the reference recorded in Xero are typically three different things. AutoRemit writes the third one so it points back at the other two.
The payer numbers its payment run its own way. Your invoice numbers are usually nowhere in that identifier, because the run covers dozens of them at once.
The same payment after the banking system has shortened and reshaped it. AutoRemit stores this alongside the match and keeps it searchable, so a “what happened to our payment” email is a lookup rather than an investigation.
What AutoRemit records: the invoice it was applied to, plus 4471 carried across from the payer's own numbering so the statement line and the ledger entry visibly belong together. [AR] marks it as generated rather than typed.
Alongside the reference, the remittance document itself is attached to the payment record in Xero. Six months later, when someone asks why a payment was allocated the way it was, the evidence is on the transaction rather than in an archived mailbox.
One case will still not reconcile on its own: an amount mismatch. If the money that actually lands differs from the payment recorded in Xero, the two will not clear against each other, and a person needs to look at it. AutoRemit does not paper over that with an adjustment.
What AutoRemit can do in your Xero — and what it cannot.
AutoRemit connects through Xero's standard authorisation, and the access it asks for is deliberately narrow. This is the whole list, in both directions.
What it can do- Read outstanding sales invoices and the contacts attached to them, so a remittance line has something to match against.
- Record a payment against an invoice once the match has cleared your confidence bar and the posting time has arrived.
- Attach the remittance document to that payment, so the evidence travels with the transaction.
- Edit or delete invoices, change contacts, the chart of accounts or bank accounts.
- Touch anything already reconciled, run or export your reports, or see payroll.
- Store your Xero password. It never holds one, and you can revoke the connection in Xero at any time.
Xero only — AutoRemit is built specifically for Xero and does not connect to other ledgers. Xero is a trademark of Xero Limited; AutoRemit is independent and not affiliated with Xero, Anthropic or Amazon Web Services.
Australian-hosted, and specific about it.
A remittance advice is a list of your customers, what they owe and what they have paid. It deserves to be treated as sensitive, so where it is processed is stated rather than buried in a policy.
- The application, your stored remittance documents and matches, and the backups are hosted in Sydney, Australia.
- Document reading runs through Amazon Bedrock within Australian AWS regions, using its Australian geographic inference profile.
- Inbound remittance email is delivered by Amazon SES in the Sydney region, to the private address issued to your organisation.
- Connections are encrypted, passwords are hashed, and support is Australian — answered in Australian business hours, not routed offshore.
The full list of services, including subscription billing and this website, is in the Privacy, Security and Cookies policy.
Reconciling remittances in Xero — the usual questions.
How is this different from Xero's remittance advice feature?
Xero's remittance-advice workflow is primarily about the advice a business sends when it pays a supplier bill — money going out. AutoRemit is built for the opposite direction: remittance advice received from customers, where the document's line items need to be matched against open Xero sales invoices. AutoRemit reads that document, matches each line to an invoice, and scores the match before anything is recorded.
What happens when the remittance advice has no invoice numbers on it?
AutoRemit matches on more than the invoice number — the payer, the amounts on each line, and the payer's own reference all contribute to the score. Where the evidence is strong the match is proposed with the reason shown. Where it is not, the line stays below your confidence bar and waits for a person, with what was read and what it was compared against on screen. It is never guessed to make the remittance balance.
Does AutoRemit post payments into Xero without us seeing them?
Not below the confidence bar you set. Items under that bar are referred for review and wait for a person. Confirmed matches are held too — they post the day after the remittance, at a time of day you set, so nothing lands in Xero the moment a document arrives.
Will the payment reconcile against our bank feed?
Xero does not expose bank feeds or their timing to connected apps, so AutoRemit cannot see the feed. It approximates the wait instead, and writes a Smart reference on the payment that carries the invoice number and a fragment of the payer's own reference, so the Xero payment and the bank line are recognisable as the same money. The one case that will not reconcile on its own is an amount mismatch — if the money that lands differs from the payment recorded in Xero, someone needs to look at it.
Does AutoRemit work with accounting systems other than Xero?
No. Xero only. AutoRemit is built specifically for Xero and does not connect to other ledgers.
Where to go next.
Try it on a remittance you already have.
Connect Xero, forward one advice, and see what AutoRemit matches — and what it holds back. The trial is the test.
No credit card required during the trial period.