Remittance Advice, Explained: The Payment Slip That Tells Your Supplier Which Invoices You Paid

You send your biggest supplier one wire for $48,200. It covers eleven invoices, takes an early-pay discount on three of them, and short-pays a twelfth because half the shipment arrived damaged. The money lands in their account the next morning — and nobody on their side has any idea what any of it is for. Their clerk guesses, applies your cash to the wrong invoices, and three weeks later you get a past-due notice on bills you already paid, plus a hold on your next order. The payment was perfect. The explanation was missing. That explanation has a name: remittance advice.

The 30-Second Version​

Remittance advice is the note you send with (or just ahead of) a payment that says exactly which invoices it covers, what adjustments you took, and what is left over. It is not mandatory, but without it your supplier's accounts-receivable team has to match your money to your invoices by guesswork — and guesswork produces misapplied payments, phantom past-dues, and strained vendor relationships. A good remittance lists every invoice number, every discount and credit, and the payment reference, in a format the other side can process without retyping.

What Remittance Advice Is (and Is Not)​

Remittance advice — also called a remittance notice or payment advice — travels from payer to payee. It answers one question: "this money pays for what, exactly?" If you have ever paid by business check, you have already used the oldest form of it: the perforated stub at the bottom of the check, itemizing the invoices the check settles, which the supplier tears off and keeps while the check goes to the bank.

Three nearby documents are easy to confuse with it, so keep them straight:

• Invoice. Sent by the seller before payment to request money. Remittance advice flows the other direction, with the money.
• Proof of payment. A bank confirmation or receipt showing that funds moved. It proves that you paid, not what you paid for — a wire confirmation with no invoice detail is exactly the problem remittance advice solves.
• Purchase order. Sent by the buyer before delivery to request goods. The remittance may reference PO numbers, but only to help the supplier match lines.

One more point worth internalizing: nobody requires you to send remittance advice. No law, no accounting standard, and no bank rule mandates it. It survives purely because both sides of a transaction are better off when the matching step takes seconds instead of phone calls.

What Every Remittance Advice Must Include​

There is no statutory template, but a remittance that omits any of the following will generate the follow-up email it was supposed to prevent:

• Your business name and contact details, plus the supplier's name. Payments sometimes arrive from an entity name the supplier has never seen — a DBA, a subsidiary, a new bank account — so identify yourself the way their system knows you, ideally with your customer or vendor number.
• The payment date, amount, method, and reference. Date sent, total dollars, how it traveled (check number, ACH trace number, wire reference), so the supplier can find the money on their bank statement and tie your note to it.
• A line-by-line breakdown of every invoice covered. For each invoice: the invoice number, the invoice date or PO number, the gross amount, any discount taken, any credit applied, and the net amount you are paying against it.
• Adjustments, stated plainly. Early-pay discount, damaged-goods short-pay, returned merchandise, a credit memo applied — each gets its own line with the reason. A lump sum that is $300 less than the invoice total with no explanation reads as an underpayment, not a discount.
• The remaining balance, if any. If you are partially paying an invoice, say what is left and when you plan to pay it.
• A contact for questions. One name, one email. When the supplier's clerk finds a mismatch at 4:45 p.m., this line is the difference between a same-day fix and a week of phone tag.

Who Sends What to Whom​

The direction is always payer to payee: you pay, you explain. But the choreography varies:

• You build the remittance. The common case. Your accounts-payable process generates the advice from the payment batch and sends it to the supplier's AR inbox.
• The supplier pre-prints a slip. Some vendors include a tear-off remittance slip with their invoice — account number and invoice pre-filled — for you to complete and return with payment. Fill it in and send it back; that slip is the remittance advice.
• The platform generates it. If you pay through AP automation software or your bank's bill-pay portal, the system usually emails the supplier a remittance automatically. Verify that what it sends actually includes invoice-level detail and not just "payment of $X sent" — several portals send the useless version by default.

Whichever route the note takes, send it to the address the supplier actually monitors for payment mail. Remittance emailed to a sales rep's inbox is remittance unsent.

The Five Formats, From Paper Stub to Structured Data​

Remittance advice has been reinvented for every payment rail. In roughly chronological order:

1. Check stub. Itemization printed below the check. Zero technology, survives to this day, dies with the check itself.
2. Mailed or faxed letter. A standalone remittance letter accompanying the payment details. Still seen in industries where checks linger.
3. Email with PDF or spreadsheet. Today's default for small businesses: a human-readable breakdown attached to a "payment sent" email. Readable by anyone, processable by no one — the supplier still retypes every line.
4. Remittance data inside the payment. Electronic formats that carry machine-readable detail with the funds, so the supplier's system can match invoices without touching a keyboard. This is the ACH story, covered in the next section.
5. Portal and AP-automation notifications. Shared platforms where buyer and supplier see the same payment record. The richest option when both sides are on it, useless when they are not.

Each step up the ladder removes one round of manual transcription — and transcription is where matching errors are born.

ACH Remittance, Decoded: CCD+ vs. CTX​

Here is the part most small-business guides skip, and it matters the moment you start paying vendors by ACH instead of check: the ACH network can carry your remittance detail inside the payment itself, in machine-readable records the supplier's bank passes through to their accounting system. No separate email, no retyping, no guessing.

The mechanism is the addenda record — an optional attachment to an ACH entry that carries payment-related information. Two corporate entry formats use it:

• CCD+ (Cash Concentration or Disbursement, plus one addendum). Carries exactly one addenda record of up to 80 characters. Enough for a single invoice number and a short note. Fine for one-invoice payments, useless for a batch covering eleven invoices.
• CTX (Corporate Trade Exchange). Carries up to 9,999 addenda records per payment — enough to itemize dozens or hundreds of invoices, each with its adjustments, in a single transfer. This is the format built for real B2B remittance.

Under the Nacha Operating Rules, the remittance content in those addenda records is structured as EDI (Electronic Data Interchange), following the ANSI ASC X12 standards — most commonly the 820 Payment Order / Remittance Advice transaction set. In plain terms: there is a decades-old, standardized grammar for "invoice 1042, gross $5,240, discount $48, net $5,192," and any supplier whose system speaks it can apply your payment the moment it arrives. Nacha has also blessed ISO 20022 XML message formats for remittance through its XML-ACH program, giving international-facing businesses a second standard vocabulary.

Two practical consequences fall out of this:

• If you pay vendors by ACH, ask what remittance format they can receive. Sending a bare CCD credit with no addenda is the electronic equivalent of a check with the stub torn off — the money arrives naked. Even a CCD+ with one invoice reference beats nothing.
• Wires are worse than ACH for remittance. A domestic wire carries only a short free-text field (often truncated downstream), so wire payments almost always need a separate emailed remittance. If you wonder why your wire "got lost" for a week, it did not get lost — it got parked in unapplied cash while someone figured out whose it was.

Why Missing Remittance Data Is a Cash-Flow Problem​

This is not paperwork for paperwork's sake. When payments arrive without explanation, the supplier's AR team parks them in an unapplied cash account and starts an investigation: emails, calls, statement comparisons. Industry data consistently shows that missing remittance detail is one of the top drivers of slow cash application, and every day your payment sits unapplied has a cost:

• For the supplier: inflated days sales outstanding, distorted cash forecasts, and staff time burned on detective work instead of collections.
• For you: misapplied payments that trigger false past-due notices, late fees you then have to dispute, and — at the extreme — a credit hold that stops your next shipment over invoices you paid a month ago.

Good remittance also protects you at audit time. A payment record stapled to a remittance showing exactly which invoices it settled is self-documenting; a bare bank line reading "ACH debit $48,200" forces you to reconstruct the story two years later from memory.

Five Mistakes That Unravel the Whole Point​

1. Sending a lump sum with no breakdown. "Payment of $48,200 — thanks!" is not remittance advice. It is a mystery with a dollar sign.
2. Citing the wrong identifiers. Your internal voucher number means nothing to the supplier. Reference their invoice numbers, exactly as printed, digits and prefixes intact.
3. Burying adjustments. Taking a discount or short-paying without a line item explaining it converts a legitimate adjustment into an apparent underpayment — and an underpayment into a collections call.
4. Sending it nowhere. Remittance faxed to a dead number, emailed to an ex-employee, or uploaded to a portal the supplier never logs into has the same effect as silence. Confirm the AR contact once, then reuse it.
5. Paying under an unrecognizable name. If the entity on the payment differs from the name on the supplier's account — new subsidiary, DBA change, acquisition — say so on the remittance. "ABC Holdings (formerly ABC Supply Co., customer 4417)" saves a week.

A Simple Template You Can Steal​

You do not need software to start. A plain-text email with this skeleton beats most of what suppliers receive:

REMITTANCE ADVICE — [Your Company] (customer #[number])
Pay to: [Supplier name]
Payment date: [date] | Method: [ACH / check # / wire ref]
Payment reference: [trace / check / confirmation number]
Total paid: [amount]
 
Invoice #    Inv. date    Gross      Discount   Credits    Net paid
INV-1042     09/02        5,240.00   48.00      0.00       5,192.00
INV-1048     09/15        8,100.00   0.00       210.00     7,890.00
...
Totals:      gross [__]  discounts [__]  credits [__]  paid [__]
 
Notes: [short-pay reason, partial-payment balance, name change]
Questions: [name, email, phone]

Save it as a reusable template, fill in the lines from your payment batch, and send it with every vendor payment. Fifteen minutes of discipline per pay run buys you out of an entire category of vendor disputes.

Booking a Remittance-Covered Payment in Your Ledger​

The remittance is also your bookkeeping source document: it tells your ledger exactly how to split one cash outflow across payables, discounts, and credits. Say a batch pays Acme two invoices totaling $13,340 and takes a $48 early-pay discount on one of them — the entry mirrors the remittance lines:

2026-10-15 * "Acme Supplies" "ACH payment, remittance RA-2026-1042"
  Liabilities:Accounts-Payable:Acme-Supplies  13340.00 USD
  Income:Purchase-Discounts                      -48.00 USD
  Assets:Checking                               -13292.00 USD

Accounts payable is debited for the full invoiced amount, the early-pay discount is credited as discount income, and checking is credited for the cash that actually left. File the remittance with the entry — attach it in your accounting system or keep it alongside your ledger — and the payment explains itself to your future self, your accountant, and your auditor. If you are new to double-entry plain-text bookkeeping, the documentation walks through payables and payment entries step by step.

Keep Your Payables Organized From Payment to Proof​

Every vendor payment you send tells two stories: the money's story, written by your bank, and the matching story, written by your remittance advice. Send both, every time, and past-due disputes over paid invoices mostly disappear. Beancount.io provides plain-text accounting that gives you complete transparency and control over your financial data — no black boxes, no vendor lock-in. Get started for free and see why developers and finance professionals are switching to plain-text accounting.