What Is a Remittance Advice? Definition, Contents, and Examples

A wire lands in your account for $4,300. You sent four invoices last month totaling more than that. Which ones did this payment cover? Without a note from the client, you're guessing — and guessing wrong means chasing money that's already been paid, or missing a short-pay you should have flagged.

That note is a remittance advice: a message from the payer to the supplier saying which invoices a given payment settles. It flows the opposite direction from a receipt — the buyer sends it, not the seller — and it exists for one reason: reconciliation. When one payment covers several invoices, or arrives short by a credit, the remittance advice is what lets you match the cash to the right line items.

This guide explains what a remittance advice is, what it contains, how it differs from a receipt and an invoice, and how to read (or request) one as a freelancer.

The short answer

A remittance advice is the payer's note telling the supplier which invoices a payment covers — sent with or just before the payment itself.

Sent by: the payer (the customer/buyer)
Sent to: the supplier (you)
Sent when: at the moment of payment, or shortly before
Purpose: reconciliation — match incoming cash to specific invoices
Not a: legal requirement, proof of payment, or invoice — it's a courtesy that saves both sides hours

Why a remittance advice exists

The problem it solves is simple: one payment, many invoices.

A client who receives three of your invoices in a month often pays them in a single batch run — one ACH transfer, one wire, one check. The bank shows you a lump sum. Your accounting shows three open invoices. Nothing in the bank record tells you which invoices that lump sum was meant to clear.

Multiply that across a busy AP department paying dozens of suppliers from one payment run and you see why remittance advices became standard practice. They let you:

Apply cash correctly — close out invoices INV-100 and INV-101 instead of guessing.
Catch short-pays — if they deducted $200 for a credit note, the advice says so.
Avoid false follow-ups — you won't chase an invoice that's actually been paid inside a batch.
Reconcile faster at month-end — your books match the bank with no detective work.

Without it, you reverse-engineer the payment from amounts, which breaks the moment two invoices share a total or a deduction is involved.

What a remittance advice contains

There's no legally mandated format, but a useful one includes:

Payer details — who's paying (company name, sometimes their AP contact)
Payment date — when the payment was issued
Payment method and reference — ACH/wire/check, plus a transaction or check number
Total payment amount — the lump sum hitting your account
A list of invoices being paid — invoice number, original amount, and amount paid per line
Deductions or adjustments — credit notes applied, early-payment discounts taken, short-pays with a reason
Net amount — the total after adjustments, which should match the deposit

A clean remittance advice reads like a mini statement. The key columns are invoice number, gross amount, deduction, and net paid — that's what makes reconciliation a 30-second job instead of a spreadsheet session.

Remittance advice vs receipt vs invoice

These three documents are easy to confuse because they all reference the same invoices and amounts. The difference is who sends them and when.

| | Direction | Sent by | Purpose | |---|---|---|---| | Invoice | Seller → Buyer | Supplier | Request payment | | Remittance advice | Buyer → Seller | Payer | Announce which invoices a payment covers | | Receipt | Seller → Buyer | Supplier | Confirm payment was received |

Read top to bottom, it's a full cycle: you invoice the client, the client sends a remittance advice with their payment, and you (optionally) send back a receipt once the money clears. The invoice and receipt are both your documents; the remittance advice is the one that comes from the client.

The practical distinction that trips people up: a remittance advice and a receipt point opposite directions. A receipt is you telling the client "I got your money." A remittance advice is the client telling you "here's the money, and here's what it's for." Same event, opposite authors.

A worked example

Say you've sent a client two invoices and issued one credit note:

INV-100   Design retainer, May      $2,500
INV-101   Extra landing page        $2,000
CN-12     Credit note (overbill)     -$200

The client batches everything into one payment. The remittance advice that arrives with it looks like this:

Remittance Advice — Northwind Co.
Payment date:   2026-06-08
Method:         ACH
Reference:      ACH-99821

INV-100    Design retainer        $2,500.00
INV-101    Extra landing page     $2,000.00
CN-12      Credit applied          -$200.00
                                  ----------
Net payment                       $4,300.00

Now the $4,300 deposit makes sense at a glance. You mark INV-100 and INV-101 as paid, apply CN-12, and you're done. Without the advice, you'd see $4,300 land and have to work out that it equals $2,500 + $2,000 − $200 — solvable here, but a nightmare when ten invoices and three deductions are in play.

How freelancers should request one

Most small clients won't send a remittance advice unless you ask — they pay and assume you'll figure it out. You can fix that with one line.

Ask upfront. When you onboard a client, add: "When you pay, please send a short note listing the invoice numbers the payment covers." Most will, especially if they batch payments.
Put your invoice numbers everywhere. The easier you make it to reference INV-100, the more likely the client cites it. Clear invoice numbering is half the battle.
Request one after an unexpected amount. If a payment lands that doesn't match a single invoice, email: "Thanks for the payment — can you confirm which invoices the $4,300 covers?" That's not pushy; it's reconciliation.
Treat a missing advice as a follow-up trigger. If you can't tell what a payment covered, that's a reason to reach out — same muscle as chasing an unpaid invoice, just gentler.

Digital and EDI formats

Remittance advices range from a one-line email to a structured data file:

Email or PDF — the most common form for small business and freelance work. Often just the payment confirmation screen or a short list pasted into the email body.
Remittance slip — a tear-off section on a paper check (the bottom stub) listing invoice numbers. Old-school but still around with clients who pay by check.
EDI 820 — the electronic data interchange standard for remittance advice, used by large enterprises. Their system emits a structured 820 file that your accounting software (or your client's portal) can ingest automatically, applying cash to invoices with zero manual entry.
Bank-attached remittance — some ACH and wire systems carry remittance data in the payment file itself (the "addenda" record), so the detail travels with the money.

For most freelancers, an email listing the invoice numbers is plenty. EDI 820 only matters if you're invoicing a corporation big enough to run automated AP — and in that case, their payment terms and portal usually dictate the format anyway.

Practical advice

Always reconcile to the net line, not the headline total — credits and discounts hide in the gap.
Don't mark invoices paid until the funds clear, even if the advice arrived. The advice is intent, not money.
Save every remittance advice alongside the matching invoice and bank record — it's your audit trail for which payment closed which invoice.
Cross-check deductions against your records. If they applied a credit note you don't recognize, query it now, not at year-end.
Ask for one by default on any client who batches payments — it costs them nothing and saves you reconciliation time every month.
If a deduction looks like an unexplained short-pay, treat it as a disputed amount and follow up before writing it off.

FAQ

Who sends a remittance advice — the buyer or the seller?

The buyer (the payer) sends it to the seller (the supplier). That's the opposite direction from an invoice or a receipt, both of which the supplier sends. The remittance advice travels with or just before the payment.

Is a remittance advice the same as a receipt?

No. A receipt is the supplier confirming "I received your payment." A remittance advice is the payer announcing "here's a payment and the invoices it covers." Opposite authors, opposite directions — see invoice vs receipt for the related distinction.

Is a remittance advice legally required?

No. In most jurisdictions it's a courtesy, not a legal obligation. It exists to make reconciliation easier, not to satisfy a regulation. That said, large AP departments treat it as standard practice and EDI-based ones generate it automatically.

Does a remittance advice prove I've been paid?

No. It states an intent to pay and what the payment covers, but the actual proof is the money landing in your account. Always confirm the deposit before applying cash to invoices — advices can precede payments that are later held or returned.

What does a remittance advice contain at minimum?

At minimum: the payer, the payment date, the total amount, and a list of invoice numbers with amounts. Better ones add the payment method and reference, plus any deductions (credit notes, early-payment discounts, short-pays) so the net matches your deposit.

What is an EDI 820?

EDI 820 is the electronic data interchange standard for remittance advice. Large enterprises emit a structured 820 file that accounting systems ingest automatically, applying payments to invoices without manual entry. It's the machine-readable version of the email a small client would send you.

How do I get a client to send remittance advice?

Ask at onboarding. Add a line to your terms requesting they list the invoice numbers each payment covers. Make your invoice numbers easy to cite, and request an advice whenever a payment lands that doesn't match a single invoice.