What Is Remittance Advice?
Jun 17, 2026
Try it now: upload an invoice and get the data in Excel or CSV
PDF, JPG, PNG, BMP, HEIC, TIFF
Upload your invoices
Drop files here or click to upload
Up to 50 files
Uploading...
If you have ever stared at a $12,400 deposit in your bank account with no idea which invoices it covers, you already understand why remittance advice exists. When a customer pays several invoices in one lump sum, the payment alone tells you nothing about how to apply it. Remittance advice is the note that explains it: this payment covers invoice 1042, invoice 1051, and invoice 1063, minus a 2 percent early-payment discount on the first one.
It is a small document that quietly keeps accounts payable and accounts receivable in sync. This guide explains what remittance advice is, what it should contain, the different formats businesses use, how to send one cleanly, and how it differs from an invoice and a receipt. Everything here is framed for US businesses paying and getting paid by ACH, check, and wire.
What is remittance advice?
Remittance advice is a notice the payer sends to the payee to confirm that a payment has been made and to spell out exactly which invoices it covers. It travels with or alongside the payment, listing invoice numbers and the amount applied to each. The supplier uses it to mark those invoices paid without guessing how to split a lump-sum deposit.
The key thing to remember is the direction of travel. An invoice flows from the seller to the buyer asking for money. Remittance advice flows the opposite way, from the buyer back to the seller, saying the money is on its way and here is what it settles. It is a courtesy and a control, not a payment itself: the actual money moves by ACH, check, or wire, and the remittance advice is the explanation attached to it.
What is the difference between remittance advice and an invoice?
An invoice is a request for payment sent by the seller before money changes hands. Remittance advice is a confirmation of payment sent by the buyer after they pay. The invoice says what is owed and when; the remittance advice says what was just paid and which invoices it settles. They move in opposite directions between the same two parties.
The confusion usually comes from the fact that they reference each other. A remittance advice quotes the invoice numbers it is paying, so the two documents are linked by design. Here is how they line up side by side.
| Invoice | Remittance advice | |
|---|---|---|
| Who sends it | Seller (payee) | Buyer (payer) |
| When | Before payment | At or after payment |
| Purpose | Requests payment | Confirms payment and what it covers |
| Contains a balance due | Yes | No, it shows amounts paid |
| Legally required | Often, for the sale record | No |
If you want a deeper breakdown of the document that starts the cycle, see our guide on how to read every field on an invoice.
What information does a remittance advice include?
A useful remittance advice includes the payer and payee names, the payment date, the payment method and reference number, and a line for each invoice being paid showing the invoice number and the amount applied. It should also note any credit memos, early-payment discounts, partial payments, and the remaining balance so the payee can reconcile to the penny.
At minimum, every remittance advice should carry these fields:
- Payer and supplier contact details
- Payment date and total payment amount
- Payment method and reference (ACH trace number, check number, or wire reference)
- Each invoice number and the amount applied to it
- Credit memos, discounts, or adjustments applied
- Any partial-payment amounts and the balance still outstanding
The invoice numbers are the load-bearing detail. Without them, the payee is back to guessing, which is the exact problem the document is meant to solve. When you receive remittance advice as a seller, matching those invoice numbers against your open receivables is the whole job, and clean, structured invoice data on your side is what makes that match instant rather than manual.
What are the types of remittance advice?
There are four common types: a basic remittance advice listing invoice numbers and amounts, a removable or perforated slip attached to a printed invoice that the payer detaches and returns with a check, a scannable slip designed to be read into an accounting system, and electronic remittance advice (ERA) sent by email, PDF, or EDI. Most US businesses now use the electronic forms.
The format you choose tracks how you pay. Companies still mailing paper checks often use the detachable stub or a printed slip. Anyone paying by ACH or wire sends an electronic version, usually a PDF emailed to the supplier or an EDI message in a batch run. In regulated settings the format is fixed: US healthcare claim payments use the standardized X12 835 electronic remittance advice under HIPAA, but that is a specialized case rather than the everyday B2B document most AP teams send.
How do you send remittance advice?
The most common way is email: send a short message or PDF the moment the payment goes out, listing the payment amount, date, reference number, and the invoices it covers. You can also use a detachable slip with a mailed check, an AP portal, or an EDI feed for batch payments. Email is the default for ACH and wire payments.
A few habits make remittance advice actually useful instead of one more attachment nobody reads. Send it at the same time as the payment, not days later, so the supplier can match it while the deposit is fresh. Put the payment reference in the subject line, the ACH trace number works well, so it does not get buried. And keep the invoice numbers exact, because a transposed digit forces the supplier to chase you for clarification, which defeats the purpose. Many teams that run high payment volumes automate this step inside their accounts payable automation software so a remittance notice goes out with every payment run.
Is remittance advice legally required?
No. Remittance advice is not legally required in standard US B2B transactions; it is a best practice rather than a regulatory obligation. The one exception is format-specific: US healthcare payments under HIPAA must use the X12 835 electronic remittance advice. Outside of those regulated cases, sending it is optional but strongly recommended.
The reason most finance teams send it anyway is purely practical. It cuts down on payment disputes, gives both sides a paper trail of intent, and stops the supplier from misapplying a payment or calling to ask what a deposit was for. For the cost of one email, it removes a whole category of back-and-forth, which is why it has become standard practice even though no rule demands it.
Is remittance advice proof of payment?
No. Remittance advice notifies the payee that a payment has been sent, but it does not prove the money was received or cleared. It states the payer's intent and what the payment is meant to cover. Actual proof of payment comes from a cleared check, a settled ACH transaction, or a bank statement showing the funds landed.
This distinction matters during a dispute. If a supplier claims they were never paid, a remittance advice shows you said you paid and identified the invoices, but it is the bank record that closes the argument. When the two sides still disagree, our guide to resolving vendor payment disputes covers the evidence to pull together first. That is why reconciling remittance advice against your actual bank activity is the step that confirms a payment really happened. Turning statements into clean records with a bank statement converter makes that match-up far faster than scrolling a PDF line by line.
What is the difference between remittance advice and a receipt?
A receipt confirms a payment was received; remittance advice confirms a payment was sent. The buyer issues remittance advice when they pay, and the seller issues a receipt once they have the money in hand. One looks forward to a payment in transit, the other looks back at a payment already collected.
In a clean transaction you might see both: the buyer emails remittance advice with the ACH, and the seller later sends a receipt acknowledging the funds cleared. They are easy to mix up because both reference invoices and amounts, but they sit on opposite ends of the same payment. If you handle a lot of these documents, our breakdown of an invoice versus a receipt covers the related distinction between requesting and confirming payment.
How does remittance advice help reconcile accounts payable and receivable?
Remittance advice tells the receiving side exactly how to apply an incoming payment, so receivables get marked paid against the right invoices instead of sitting unmatched. On the paying side, it documents which payables a payment cleared. Both effects depend on accurate invoice numbers and amounts, which is where clean, structured invoice data earns its keep.
The bottleneck in reconciliation is rarely the remittance advice itself; it is matching it to the invoices behind it. If your open invoices live as PDFs and email attachments, every match is a manual hunt. Pull the header fields and totals into structured records with invoice data extraction software, and a remittance line that says "invoice 1051, $4,200" snaps straight onto the matching record. Capturing invoices the moment they arrive with invoice data capture software keeps that ledger current, and invoice line item extraction preserves the line-level detail you need when a remittance applies a partial payment or a discount to specific lines. The remittance advice closes the loop, but only if the invoice data on your side is clean enough to match against.
How to ask for remittance advice
Ask in the payment confirmation thread, name the payment, and make it easy to answer. A short email works better than a formal request: give the payment date, the exact amount received, and the paying bank reference, then ask which invoices it covers. Most AP departments can generate the remittance from their system in under a minute once they know which payment you mean.
Wording that gets a fast reply looks like this: "We received a payment of $14,280.00 on March 4 with reference ACH-88214. Could you send the remittance advice so we can apply it to the correct invoices?" The specifics matter more than the politeness. A request that just says "please send remittance" forces the other side to go looking, and it tends to sit.
If you are chasing these regularly, the better fix is upstream. Ask to be added to the vendor's automatic remittance list when you onboard, so the advice arrives with every payment run instead of on request. Many AP systems email remittances automatically once a contact address is on file, and nobody has to remember. If a customer repeatedly pays without any advice at all, raise it as a process issue rather than a one-off, because every unexplained lump sum becomes manual detective work in your cash application.
What is a bank remittance advice?
A bank remittance advice is confirmation that a payment has been sent through the banking system, showing the amount, the date, the payer, and a reference. It comes from the bank or the payer's banking platform rather than from the customer's accounts payable team, and it proves a transfer was initiated. What it usually does not tell you is which invoices the money is for.
That distinction trips people up. A bank advice answers "did the money move?" A remittance advice from the customer answers "what is this money paying for?" You need the second one to apply cash correctly, and receiving the first is not a substitute. A single wire covering eleven invoices with three short-payments looks identical on a bank advice to a wire covering one.
The paper equivalent is the stub attached to a check. If you have received a check with a detachable section listing invoice numbers and amounts, that stub is the remittance advice, and it should be kept and matched rather than thrown away with the envelope. Checks paid against many invoices are exactly the case where the stub is doing real work, and where losing it means reconstructing the allocation by hand from your open receivables.
The takeaway
Remittance advice is the buyer's note to the seller confirming a payment and spelling out which invoices it covers. It is not legally required and it is not proof of payment, but it prevents misapplied payments and the phone calls that follow them. Send it the moment you pay, list exact invoice numbers and amounts, and put the payment reference in the subject line.
The document only works if both sides can match it quickly, and that comes down to data hygiene. Keep your invoices as clean, structured records so an incoming remittance reconciles in seconds, and connect the related pieces of the payment trail: route and pay approved bills with accounts payable automation, and pull invoices and remittance notices out of your inbox automatically with email parsing software. Handle the document as part of one connected payment cycle, and reconciliation stops being a guessing game.