Remittance advice: Definition, components, and examples

Remittance advice is a document or message a payer sends a payee to confirm a payment and show which invoices it covers. Your accounts payable (AP) team sends it, and the vendor's accounts receivable (AR) team uses it to apply cash.

A complete advice names the payer and payee, lists each invoice number and amount paid, and states the payment method.

What is remittance advice?

Remittance advice is the payer's record of a payment, listing the invoices it settles and the amount applied to each. Your AP team sends it at the time of payment or just before. Its job is to let the vendor match the funds to open invoices without guessing.

It goes by other names, including payment advice, remittance notice, remittance slip, and remittance information. They all describe the same document.

Remittance advice confirms what the payer intended to pay and how. The bank deposit is what confirms the money arrived. Match the two before you close any invoice.

Remittance advice vs. remittance vs. invoice vs. receipt

Remittance advice explains what a payment covers, while an invoice requests payment and a receipt acknowledges it. Outside business-to-business (B2B) finance, a remittance usually means money a worker sends to family in another country. Remittance advice borrows the word because to remit means to send payment, and in AP it's always tied to specific invoices.

A customer document that lists your invoice numbers and amounts paid is remittance advice. Route it to cash application.

Components of remittance advice

Every remittance advice carries enough detail for the payee to apply the payment to the right invoices without contacting the payer. Six fields do that work.

Payer and payee details

Each party's legal name and vendor or customer ID, plus a contact for payment questions. IDs let AR find the right customer account when the legal name differs from the one on file.

Payment date and payment method

When the funds went out and how they were sent, with the expected settlement date. Automated Clearing House (ACH) payments usually settle the next business day or same day, and wires land the same day. Mailed checks take several days, so AR knows to wait before chasing.

Invoice numbers and amounts paid

A line for each invoice the payment covers, with the amount applied to it. This line-level mapping is how AR closes invoices with confidence. A lump sum with no invoice detail usually sits as unapplied cash until someone calls the customer.

Deductions, credits, and discounts

Each amount the payer held back, such as an early-payment discount or credit memo, with the reason for it. Without a reason, AR can't tell a taken discount from a disputed short-pay. Each unexplained gap becomes a follow-up with the customer.

Payment reference or transaction ID

The check number, ACH trace number, or wire reference that ties the advice to a specific deposit. AR uses it to find the matching line on the bank statement. It's the tiebreaker when two customers pay the same amount on the same day.

Total payment amount

The single figure the payee reconciles against the bank deposit. It should equal the sum of the invoice lines after deductions. A total that doesn't tie out stalls the whole payment.

Types of remittance advice

Remittance advice comes in a handful of delivery formats, and the format decides how much manual keying the payee does.

• Check stub: A paper stub attached to a check, listing the invoices the check pays. AR keys it in by hand or from a lockbox scan.
• Emailed PDF or portal notification: A document or alert sent when the payment releases. It's a typical format for ACH and virtual card payments.
• Electronic data interchange (EDI) 820: A structured electronic file exchanged between trading partners. It fits companies sending or receiving several hundred payments a month.
• Bank-embedded remittance data: Invoice details carried in ACH addenda records or wire reference fields. The data arrives with the funds, but field length limits how much fits.
• Healthcare remittance advice: An electronic remittance advice (ERA), sent as an 835 file, explains how an insurer paid a provider's claims. It follows its own standard and isn't used for B2B vendor payments.

Ask each customer which format they send so you know where to look when a payment lands.

Remittance advice example

A mid-sized manufacturer, Halvorsen Manufacturing, pays its packaging vendor, Brightline Packaging, for three invoices in one ACH payment. Halvorsen takes a 2% early-payment discount on the newest invoice and applies a $1,100 credit memo to the oldest.

Payment method: ACH credit, sent Sep 10, 2026

Reference number: ACH trace number 021000021234567

Brightline's AR team finds the $25,263.60 deposit by its trace number and sees three invoices to close, each with its deduction explained. Because the advice names the credit memo and the discount terms, AR closes all three invoices without a call to Halvorsen.

Received a remittance advice? What it means and what to do

If you received a remittance advice check or email, a customer has paid, or is about to pay, one or more of your invoices. The advice tells you which invoices the money covers. Before you post anything, take five steps in order:

1. Confirm it's legitimate by checking the payer against your customer records. Never act on changed bank details sent in a remittance email, and verify any change by calling a number already on file.
2. Match the payment reference to the deposit in your bank account. Use the trace or check number, then confirm the total.
3. Apply the payment to the invoices listed, using the amount shown on each line.
4. Log any short-pay or deduction and follow up with the customer. Record the reason so collections and sales work from the same facts.
5. File the advice with the invoice record for audit.

Remittance advice is the input that tells AR which open invoices to close. When it's missing or unclear, the deposit lands as unapplied cash, and your team spends hours tracing it back to a customer.

You can cut that tracing work with Ramp Accounts Receivable, whose cash application agent matches each incoming payment to the right open invoice using payer, amount, and invoice details. Ramp AR also keeps QuickBooks Online or NetSuite current as it applies each payment.

Apply cash the day it arrives, and your aging report stays accurate.

How to send remittance advice

Send remittance advice from the same process that releases the payment, so the details your vendor sees match the funds they receive.

1. Generate remittance advice when you schedule the payment

Create the advice from the record that releases funds. When AP builds it separately in a spreadsheet or email, invoice numbers and amounts drift from what you paid.

2. Include every component the payee needs

Cover payer and payee details, invoice-level amounts, deductions with reasons, the payment reference, and the total. Line-level invoice detail matters most, because the vendor's AR team closes invoices from it.

3. Deliver remittance advice through the vendor's preferred channel

Send it by email, portal, EDI, or check stub, depending on what the vendor has asked for. Store that preference on the vendor record so every payment follows it.

4. Time delivery to when the payment arrives

Send the advice so it reaches the vendor close to when the funds settle. For ACH and wire payments, that's the day you release the payment. For checks, mail the stub in the same envelope.

Advice that shows up days before the funds sends vendors looking for money that hasn't arrived.

Remittance advice decisions for AP leads and controllers

Once you're paying a steady monthly invoice volume, how you issue remittance advice becomes a control decision. Four choices shape how clean your vendors' cash application is and how exposed you are to fraud.

Remittance timing vs. payment arrival

ACH typically settles the next business day or same day, wires settle the same day, and checks take several days in the mail. Advice sent far ahead of the funds creates where's my money tickets, while late advice leaves deposits unapplied. Set one send rule per payment method and apply it to every vendor.

Centralizing remittance issuance

Issuing all advice from the system that executes payments gives you consistent formatting and a complete audit trail. The trade-off is less flexibility for one-off messages that clerks used to send from their own inboxes. Accept it because advice scattered across inboxes gives fraudsters more places to spoof.

Managing vendor delivery preferences

Keep each vendor's preferred format and remittance contact on the vendor record. Letting anyone update that contact by email saves time but invites fraud. Route every change through a verified process, such as a callback to a known number plus a second approver.

When to move to EDI

EDI 820 removes manual rekeying on both sides once you send several hundred payments a month or a large customer mandates it. The trade-off is setup cost, since each trading partner needs mapping and testing before go-live. Start with the partners who require it, then add others as volume justifies the work.

Review your remittance controls at least once a year:

• Single source of issuance: All remittance advice comes from the system that releases payments.
• Verified contact changes: Vendor remittance contacts change only after a callback and a second approval.
• Line-level detail: Every advice lists each invoice, its amount paid, and the reason for any deduction.
• Standard timing rule: Each payment method has a set send time tied to settlement.
• Retention policy: You keep remittance advice with the payment record for as long as you keep the invoices.

Fix any gap before a vendor or an auditor finds it.

Automate remittance and vendor payments with Ramp Bill Pay

Remittance advice breaks when payment data and payment communication live in separate places. When AP pays from one system and emails invoice details from another, the two drift apart. Vendors then call to ask what a deposit covers.

Ramp Bill Pay is a full-cycle AP solution that pays your vendors and sends their payment details from one record. Finance teams process invoices 2.4x faster with 86% fewer clicks than legacy software.

Here's what the payment cycle looks like with Ramp Bill Pay:

• Capture and code invoices automatically: AI invoice processing reads invoices with 99% optical character recognition (OCR) accuracy, and AP Agent codes each bill from your coding history.
• Route approvals by your rules: Custom rules pick the approver, and AP Agent recommends whether to approve.
• Pay the way each vendor prefers: Pay by ACH, check, virtual card, or wire, with payment details sent from the same record.
• Show vendors where payments stand: Vendor Portal gives vendors payment-status visibility, so AP fields fewer status emails.
• Keep your enterprise resource planning (ERP) system in sync: Two-way sync keeps paid status aligned with NetSuite, Sage Intacct, QuickBooks Online, or Xero.

If you also send invoices, Ramp AR runs on the same platform: Bill Pay pays the invoices you receive, and Ramp AR collects on the invoices you send.

Try an interactive demo to see how Ramp handles payments and remittance from invoice to ERP. More than 85,000 businesses use Ramp to save over $1 billion a month.