Remittance Terms and Definitions

Remittance Advice: What It Is and What It Should Include

A remittance advice explains what a payment covers and which invoices it settles. See what to include—and which documents it isn't.

Daniel R. Whitaker 6 min read

A remittance advice is a document the payer sends to the payee explaining what a payment covers. The money itself arrives with a reference number and little else. The advice fills in the rest: who paid, how much, which invoices or obligations the money settles, and when it was sent. Banks and large buyers call it an electronic remittance advice (ERA) when it travels as a data file rather than a PDF or printed page.

The document does not move money. It is an allocation notice. When it is complete, the recipient can post the cash to the right account on the first attempt. When it is missing or vague, the payment sits unapplied while both sides trade emails.

What a remittance advice is not

Three documents get confused with it, and the difference matters when someone asks you for paperwork.

  • A payment confirmation comes from the provider and proves the transfer was sent. It shows fees, exchange rate and a tracking reference, but not what the money is for.
  • An invoice is the request for payment. The advice answers it.
  • A proof of payment such as a bank slip or wire confirmation shows the debit on the sender's side. It still may not tell the recipient which invoice the transfer settles.

A complete remittance advice can stand in for all three in a dispute, but only if it carries the payment reference the receiving bank or provider issued. That is the line most templates leave out.

What a remittance advice should include

Treat every field as something the recipient's accounts team needs to post the cash without calling you. The core set is short.

  1. Payer legal name, address and a contact for payment questions.
  2. Payee name exactly as it appears on the receiving account.
  3. Payment date and the date funds are expected to land.
  4. Amount sent, currency sent, and the amount received in the payee's currency if a conversion happened.
  5. Any fees and who paid them, kept separate from the principal amount.
  6. Exchange rate applied, with the rate source and the time it was locked.
  7. Payment reference or tracking number from the provider.
  8. Invoice numbers, account numbers or obligation descriptions the payment covers, each with its own amount.
  9. A clear statement when one payment covers several invoices, including any short payment or overpayment and the reason.

Two fields are optional but save time. The first is the sending account or card used, useful when a business pays from several accounts. The second is a remitter reference the payee assigned, so their system can match the payment automatically.

Extra fields for cross-border payments

International transfers add items a domestic advice can skip: the intermediary bank if one is used, the purpose-of-payment code some corridors require, and the screening status if the provider reports one. Keep screening language factual. "Held for review" is useful; a guess about why is not.

How to build a remittance advice template

A workable template has four blocks in a fixed order. Fixed order matters more than design, because the payee's software may read the file rather than a person.

  • Header: document title, advice number, issue date.
  • Parties and payment: payer, payee, amount, currency, date, reference.
  • Allocation table: one row per invoice or obligation, with invoice number, invoice date, amount due, amount paid and balance remaining.
  • Footer: totals, a note on fees and rate, and a contact name, email and phone number.

Build the template around whatever your provider's payment reference looks like. If the reference is 16 characters, give it its own labeled line. Never bury it in a free-text note, and never let a spreadsheet truncate it.

Choosing the file format

Send a PDF when a person will read it. Send a CSV or the structured file your accounting system exports when the payee's system will process it. If the payee runs automated matching, ask which format their system expects before the first payment, not after. Standardized business-to-business formats exist, but small payers rarely need them. A clean CSV and a consistent reference do most of the work.

A remittance advice sample with illustrative numbers

Here is a simplified allocation block for one cross-border payment. The figures are illustrative only.

Invoice Invoice date Amount due (USD) Amount paid (USD) Balance
INV-2041 March 3 1,200.00 1,200.00 0.00
INV-2047 March 9 850.00 800.00 50.00
Total 2,050.00 2,000.00 50.00

Below the table, the advice should state the reason for the short payment, for example a disputed delivery charge of 50.00 USD withheld pending credit. Without that line, the payee sees a 50.00 gap and assumes a bank fee. The payment section would also list the amount sent in USD, the amount received in the payee's currency, the rate applied and when it was locked, and the provider's tracking reference.

An individual sending money to family can use a stripped version: payer name, recipient name, amount, date, reference, and a one-line note on what the money is for. The same discipline applies. A clear purpose line resolves most queries before they start.

Common mistakes that cause unmatched payments

Most failed matches trace back to a handful of errors, and each is avoidable.

  • Missing payment reference. The payee can see the money but cannot link it to an account.
  • One lump sum, no allocation. A single payment covering five invoices needs five rows. Otherwise the payee guesses, and often guesses wrong.
  • Mixing fees into the principal. If the advice says 1,000 but the payee received 985, the 15 gap needs an explanation on the document.
  • Name mismatch. The payee name on the advice must match the account name at the receiving institution, or screening may hold the payment.
  • No exchange rate detail. The payee's currency amount will not reconcile without the rate and when it was locked.
  • Silent short payments. Deductions without a stated reason look like errors.
  • Sending the advice to the wrong person. Route it to the address the payee nominated for billing, not to an individual's inbox.

Rules for purpose-of-payment codes, identifiers and supporting documents differ by jurisdiction and provider, and they change. Check the sending provider's current instructions and the receiving country's official rules before you finalize a template.

Make the advice part of the payment, not an afterthought

Build the remittance advice before you send the money, not after. Pull the invoice numbers and allocation into the document first, then copy the payment reference from the provider into it the moment the transfer is confirmed. That sequence lets the advice go out the same day the funds do, with nothing missing.

Keep one template for domestic payments and one for cross-border payments, each with the fields above, and store the last three months of advices with the matching payment confirmations. When a payment is queried, you will have the document that answers the question in one file. For individuals, a two-line note with the reference and purpose is enough. For a business paying several invoices at once, the allocation table does the real work. Review the template once a year against your provider's current reference format, since a field that once fit can silently break automated matching.

This article is general information, not financial, legal or tax advice.

Related Articles