Remittance Advice Email to Suppliers: Template and Automation

Why "have you paid?" emails cost more than they look

Every unanswered payment question is a small piece of staff time. Someone searches the bank statement, opens the supplier ledger, finds the right invoice and replies. Then the supplier replies to confirm. Two or three exchanges can take longer than the payment itself took to make.

The problem grows with volume. A business paying a few suppliers a month may only lose an afternoon. A business paying hundreds of suppliers in a run can have a steady stream of messages after every run. The cost is mostly staff hours and delayed cash for the supplier, who cannot close the invoice until it knows what was paid.

Late payment is a wider background issue. Atradius's Payment Practices Barometer for 2025 reported that 47 percent of B2B invoices in Western Europe were overdue at the time of its survey. That report covers customers paying suppliers, not remittance emails specifically, but it shows why suppliers ask so often. They want proof that a payment is on its way and what it covers.

No public figure was found for the average staff time spent answering supplier payment queries, so this guide does not put a price on it. The free audit measures your own volume and shows what the queries cost you.

What the email must contain

Keep the email short enough to read on a phone. The supplier needs to answer four questions: what was paid, for which invoices, when, and by which bank reference. Anything else is optional.

1. Your company name and the supplier's account name or vendor number, so the email matches their records.
2. The payment date and the total amount sent.
3. One line per invoice: invoice number, invoice date, amount paid against it, and any amount withheld or discounted.
4. The bank reference or transfer ID, exactly as it appears on your bank statement.
5. The name of a contact in accounts payable and the instruction to reply to that person if a line looks wrong.

Put the detail in the body of the email, not only in an attached PDF. A supplier's system or a clerk can then read it without opening anything. If you do attach a PDF, use the same numbers as the body.

Some payments will not match a single invoice cleanly. A partial payment, a bundled payment covering several invoices, or a payment net of a bank fee needs a plain note. Write the note in one sentence and avoid explaining your internal approval process.

Template you can adapt

Use this as the starting text. Replace the bracketed items with the values from your payment record. Do not send the bracketed text to a supplier.

Subject: Payment sent on [date], reference [bank reference]

Hello [supplier contact], we have sent a payment of [total amount and currency] on [payment date]. It covers the invoices listed below. The bank reference is [bank reference].

[Invoice number], dated [invoice date], amount paid [amount].
[Invoice number], dated [invoice date], amount paid [amount], less [amount withheld, with a short reason].

If any line does not match your records, reply to this email and copy [accounts payable lead's name and address]. Please do not reply to the payment system or the bank.

Kind regards,
[Name], Accounts Payable, [company name]

Manual way and automated way compared

The two approaches differ mainly in who builds the email and when. Both can produce the same message. The difference is how often a person has to copy numbers by hand, and how quickly the supplier hears back.

For a business that pays a handful of suppliers each month, the manual way is often enough, provided one person owns the task. The automated way pays off when payment runs are frequent or when the same questions come back every week.

How to automate it, step by step

Work through these steps in order. Each one is useful on its own, so you can stop after any step and still gain something.

1. Fix the payment record first. Every remittance email is only as good as the link between a bank payment and the invoices it settles. Agree on one reference format, for example the supplier code plus the invoice number, and use it on every payment instruction.
2. Export the payment run. Most accounting packages, including Xero, QuickBooks Online, Zoho Books and Tally, record bill payments against invoices. Check whether your package can export those payments with the invoice numbers and bank reference. If it cannot, a scheduled spreadsheet export from the payment file does the same job.
3. Build the email from the export. A spreadsheet mail merge, a workflow tool such as Power Automate or Zapier, or a short script can turn each supplier's rows into one email. Test the output on five suppliers before turning it on for all of them.
4. Send by email first. Email works with any supplier and needs no approval from anyone. Send from a shared accounts payable mailbox, not a personal address, so replies go to a place that stays staffed.
5. Add WhatsApp only where suppliers use it. In markets where suppliers run their business on WhatsApp, a WhatsApp Business Platform message can carry the same details. Meta's documentation says that a business can start a conversation with a message template outside the 24-hour customer service window, and that templates are reviewed before use. Utility templates are the category for messages about a transaction. Template body text is limited to 1,024 characters, and placeholders must be numbered, for example {{1}}. Text placeholders are not currently supported in some setups, so check the current template guidance before you design one. A list of invoice lines can run past the limit, so for long runs send the detail by email and the short notice by WhatsApp.
6. Handle replies with a lookup, not a guess. When a supplier asks whether an invoice was paid, a person or a program looks up the invoice in the payment record and replies with the date, amount and reference. Where the record shows no payment, the reply says the invoice is open. It does not guess.
7. Check bank confirmations before you send. Some banks return a structured status report, called pain.002 under the ISO 20022 standard, to the business that sent the payment file. It shows whether each payment was accepted or rejected. Accepted does not always mean settled. Treat a settlement code as the trigger for the final notice, and send a note about a rejected line to the accounts payable lead instead of the supplier.
8. Route disputes to a named person. Any reply that says a line is wrong, a payment is missing or an amount differs goes to the accounts payable lead with the invoice list and the reference. The automated step stops there. The lead decides and writes back.

Routing "has this been paid?" without sending the wrong answer

Most of the repeat questions come from suppliers who sent an invoice and have not seen a payment. The fastest answer is the payment record itself. Keep one place where a payment is marked as sent, and one place where it is marked as settled. Those two states are not the same, and a supplier who hears "sent" may still be waiting for funds to arrive.

Write the reply in the same language as the remittance email. Give the date sent, the amount, the bank reference and the invoices covered. If the record shows the invoice as open, say that. A reply that says the invoice is open is better than a reply that guesses it is in the post.

What breaks, and how to prevent it

The most common failure is a mismatch between the accounting record and the payment file. An invoice number typed with a different prefix, or a supplier who has two vendor accounts, will cause the email to list the wrong invoices. Run a check that compares the total in the email with the total in the bank file before anything sends. If the totals differ, hold the batch.

The second failure is a send that repeats. A script that re-runs after an error can send the same remittance twice. Store a record of each sent email, keyed by payment reference, and skip any reference that already has a sent record.

The third failure is sensitive data sent to the wrong address. Supplier contact lists go stale. Staff change jobs. Check the recipient list each quarter, and keep bank account details out of the remittance text. The email needs the reference, not the account number.

The fourth failure is an email that sounds like a legal notice. Keep the tone plain. Do not describe the supplier's account as overdue in the same email that confirms a payment. Put overdue discussions in a separate message from the accounts payable lead.

Automation also cannot tell whether a payment was agreed. It can only report what was paid. A person must still decide whether a short payment is a discount, a withheld amount or an error, and must still answer a supplier who disagrees with the figures.

When not to automate

Do not automate this if you pay only a few suppliers a month and the same person already sends clear emails without difficulty. The setup work will take longer than the emails it replaces.

Do not automate it if your payment records are not reliable. A program that builds emails from wrong data sends wrong data faster. Fix the reference format and the ledger first.

Do not send automated messages to suppliers in a dispute, after a complaint, or where a contract sets specific notice terms. Those messages need a person to read the contract and write the reply.

Do not use automation to chase unpaid invoices in a way that pressures the supplier or the customer. Remittance emails report what you paid. They are not a debt collection tool.

Remittance advice is generally treated as good practice rather than a legal obligation, and most guidance describes it as a courtesy. Your own supplier contracts may set requirements, so read them before you change the process. This explains the rule in general terms; it is not legal or tax advice for your case.

What it typically takes

The setup is mostly time spent on data, not money. Expect the first week to go on agreeing the reference format and checking a sample of past payment runs against the supplier ledger. The second week goes on building the export and the email template, then testing on a small group of suppliers.

Set a short review after each run for the first month. Check ten or so emails against the bank file, and check every dispute that came back. Once the lines match consistently, reduce the review to a spot check each week. Keep the accounts payable lead as the named owner of disputes throughout.

If you have WhatsApp-first suppliers, add the second channel after the email version works. Test each WhatsApp template with a few suppliers before using it for a whole run.