Setting Up a Remittance Email Inbox That Processes Itself

The remittances piling up in someone's personal inbox aren't a discipline problem, and no amount of nagging will fix them. Email is the wrong container for a shared queue of documents that several people need to act on, and blaming whoever owns the mailbox doesn't change what the container is doing. Most remittance advices arrive by email and stack up until a reconciliation deadline forces a scramble, and there's no remittance-inbox button in Xero to switch on, so the fix is a small workflow you build yourself.

If your customers only ever pay you one invoice at a time, you can skip most of this and just file the email. What makes it worth solving is dozens of remittances a week, landing in different mailboxes, in different formats, many of them covering several invoices each. The workflow below captures all of them in one place and takes the manual opening of each message off your plate, and it says where Xero stops and a tool has to take over.

Why personal inboxes are the wrong home for remittances

A remittance advice is a working document. Someone has to read it, find the invoices it pays, split the payment correctly, and post it. The moment it lands in an individual's inbox, three things go wrong.

• It gets buried. A remittance from a large customer looks, to an email client, exactly like every newsletter and internal thread. It scrolls off the first screen within an hour and is out of sight by the next morning.
• It becomes key-person risk. If remittances go to one person and that person is on leave, the queue stops moving, and nobody else can see what's waiting, because they can't see into a colleague's mailbox.
• There's no backlog you can measure. When remittances are scattered across personal inboxes, "how far behind are we?" has no answer anyone can give, so the work only surfaces as a month-end surprise.

So the first move is to stop routing remittances like personal mail and give them a home built for shared work. Everything below does that in three steps, each one closing a gap the last left open.

Step 1: Create a shared remittance mailbox

Create a single shared mailbox with an obvious name, something like remittance@yourco.com or ar@yourco.com. In Microsoft 365 this is a shared mailbox; in Google Workspace it's a group or a delegated mailbox. Give your AR and finance team access so anyone who's free can triage it, rather than routing everything through one named person.

That one move solves the visibility problems above, because the backlog becomes a countable list everyone can see, cover during leave happens on its own now the queue is shared, and you've got a single durable address to hand to customers who ask where to send their remittance advice.

A shared mailbox stops remittances getting lost, but it doesn't stop someone opening every single one and doing the matching by hand.

Step 2: Auto-forward with a mail rule

Customers will keep sending remittances to whatever address they already have on file, usually a salesperson, a generic info@ address, or an individual in finance. You don't want to chase every payer to update their records, so set a rule that forwards anything looking like a remittance into the shared mailbox.

In Outlook

Go to Settings, then Rules, and add a new rule. Set a condition such as subject contains "remittance" or subject contains "payment advice", and the action forward to remittance@yourco.com. Add a second rule for your handful of high-volume payers using a from condition on their known sender addresses, so their remittances are captured even when the subject line is vague.

In Gmail

Open Settings, then Filters and Blocked Addresses, and create a new filter. Use search criteria like subject:remittance or a list of known sender addresses, then choose Forward it to and pick the shared address (you may need to add and verify it as a forwarding address first). You can stack several filters for different senders.

Before you over-tune the rules, resist filtering on "has attachment" on the assumption that a remittance is always a PDF. Plenty of smaller payers skip the attachment entirely and type the invoice numbers and amounts straight into the body of the email, and if you filter those out you'll drop a slice of your remittances without ever seeing it happen. Match on subject and sender, and let attachment-less emails through.

Step 3: Turn the remittance email inbox into matched entries

You've now got a tidy shared mailbox fed by forwarding rules, and the backlog is visible and shared, but a human still has to open each message, read the remittance, find the matching open invoices in Xero, split the payment across them, and post it. For one or two a day that's fine, and for thirty a week it's hours of careful, error-prone clicking that nobody needs to be sitting through.

This is where the workflow stops being something Xero or your mail client can do, and where a dedicated tool takes over. RemitClear gives each workspace its own unique inbound address ending in inbound.remitclear.com, which you copy from RemitClear's Settings. You then point step two at it: instead of forwarding remittances only to your shared mailbox, also forward them to your unique address at inbound.remitclear.com. The address is shared across the workspace, so team members can forward manually too, and there's no per-email limit.

Every forwarded email is read automatically, whether the remittance came as a PDF, Word, Excel, CSV or TSV attachment, or as one of the attachment-less emails where the payer just lists invoice numbers and amounts in the body. Within seconds the extracted details are matched against your open accounts receivable invoices in Xero or QuickBooks Online and queued with a confidence score, so you review rather than retype. You approve, and the payment posts back to your ledger with the source document attached for the audit trail. On Xero you choose a single batch payment or separate payments; on QuickBooks Online one payment covers every invoice that customer is paying.

Remittances then arrive, get captured, and turn into matched entries waiting for a quick check, with no one opening attachments by hand, which is the part the mail rule alone can't give you. If you want the full picture of this approach, see RemitClear's email remittance capture page, and the matching engine behind it on the Xero remittance matching page. For the manual version of the matching it replaces, our walkthrough on reconciling a remittance advice in Xero shows which steps disappear.

Scaling it across multiple entities or clients

The forwarding pattern pays off most when you have more than one set of books. A bookkeeping practice running a dozen client files, or a group with several trading entities, can't realistically have a person uploading PDFs into the right Xero org all day, and email forwarding takes the routing decision away.

1. Give each entity or client its own shared remittance mailbox, or at least its own subject or sender conventions.
2. Each RemitClear workspace has its own unique inbound address, so set one forwarding rule per mailbox that routes that client's remittances to the matching workspace.
3. Whoever is on triage that day reviews the queued matches across whichever workspaces need attention, instead of hunting through inboxes to work out which file a remittance even belongs to.

The workflow is identical whichever payment rail the money arrives on, and only the wording on the document changes, and our guide to the four names a payment advice goes by covers what each one means. For the structure of running this cleanly across several books, see our guide on reconciling remittances across multiple Xero orgs.

Summary

Stand up one shared mailbox, remittance@ or ar@, and give the whole AR team access, so a scatter of personal inboxes becomes a queue you can count. Then add a forwarding rule in Outlook or Gmail, matching on subject and sender, and resist the urge to filter on attachments so the body-only remittances still get through. Those two steps stop remittances getting lost, and pointing the same forwarding at an inbound address that matches and queues each one is what stops a person having to open them at all.