Remittance Advice: What It Is, Examples, and How to Automate It (2026)
A remittance advice is a document or message a payer sends to a payee to confirm that a payment has been made and to identify which invoices the payment covers. It's the connective tissue between an outgoing payment and the supplier's accounts receivable team. Without it, the AR team can't apply cash to the right invoices without picking up the phone.
If you've ever had a vendor email asking "what was this $47,283.91 wire for?", you've felt the pain a remittance advice solves. Most AP teams handle hundreds of payments a month across checks, ACH, wires, and virtual cards. Without a clear remittance advice riding along with each one, the supplier's AR team is left guessing, and your AP inbox fills up with reconciliation questions.
Key Takeaways
A remittance advice is a payment confirmation document that tells the supplier which invoices a payment covers, what was deducted (credits, discounts, short pays), and how the payment was sent.
Common formats include the paper check stub, removable invoice tear-offs, scannable remittance, email or web-based notices, and the EDI 820 electronic remittance advice used in high-volume B2B environments.
Manual remittance creation is one of the hidden labor costs of AP. Ardent Partners pegs the average cost to process a single invoice at $12.88, and remittance generation is part of that load.
Automated AP platforms generate and deliver remittance advice with every payment, then sync the data back to the ERP, eliminating the spreadsheet exports and email chains most teams rely on today.
Remittance advice isn't legally required in most jurisdictions, but it's table stakes for keeping vendor relationships clean and cash application fast on both sides of the payment.
What Is Remittance Advice?
A remittance advice is a notification from the payer to the payee that explains a payment. It says what the payment covers, how it was sent, and what (if anything) was deducted before it went out. In B2B finance, it's the document that connects the dollar amount hitting a supplier's bank account to the specific invoices that dollar amount is meant to settle.
The term goes back to the days when most B2B payments traveled by mail with a paper stub attached. The check went into one envelope, the remittance information went into another, and the supplier's AR team matched them up by hand. Mechanics have changed since most payments now move electronically. The underlying purpose hasn't. The payer still owes the payee a clear explanation of what's being paid and why.
A remittance advice isn't a receipt, a confirmation of payment authorization, or proof that funds have cleared. It's a statement of intent and detail, telling the supplier exactly which invoices the payment covers and what adjustments were made. The payment itself moves through a separate channel (bank wire, ACH file, virtual card transaction, or check), and the remittance advice rides alongside it as the explanatory document.
What information does a remittance advice include?
A remittance advice typically includes the payer's name and account or vendor ID, the payment amount, the payment date, the payment method (check, ACH, wire, virtual card), and an itemized list of the invoices the payment is settling. For each invoice, it shows the invoice number, invoice date, gross amount, any credits or early-payment discounts taken, any short pays or disputed amounts, and the net amount applied.
A clean remittance advice also includes a check or transaction reference number that ties back to the actual payment, so the supplier's AR team can match the document to the bank deposit. If the payment includes deductions like a credit memo applied, a discount taken under terms, or a withholding for a quality issue, each deduction needs its own line with a code or short description. Otherwise the supplier sees a number that doesn't match the invoice total and has to dig in to figure out why.
Is remittance advice the same as proof of payment?
No. Proof of payment is bank-side evidence that funds actually moved: a wire confirmation, a cleared check image, an ACH return code, a virtual card authorization. A remittance advice is the payer's accompanying explanation of what the payment was for. They have different jobs and live in different systems.
In practice, suppliers often ask for both. AR teams want the remittance advice to apply cash correctly in their ERP, and they want proof of payment to confirm the funds are real and irreversible before they release goods or close the receivable. Some payment methods (ACH with addenda records, EDI 820 inside a banking file) bundle the two together. Most don't.
What Are the Different Types of Remittance Advice?
Five common formats turn up in B2B AP operations today: the paper check stub, the removable invoice tear-off, scannable remittance, email or web-based remittance notices, and the EDI 820 electronic remittance advice. Each one reflects a different stage in the evolution of B2B payments. Most large AP operations use several at once, depending on which suppliers they're paying.
Choosing among them usually comes down to two factors: how the payment is being sent, and how technically capable the receiving supplier is. A small landscaping vendor paid by check every other month wants a paper stub. A national distributor processing thousands of inbound payments a day wants EDI 820 files dropped to an SFTP folder. Most AP teams sit in the middle of that range and end up supporting three or four formats at once.
Format | How it travels | Best for |
Paper check stub | Attached to a printed check | Low-volume vendors paid by check |
Removable invoice advice | Tear-off section on the bottom of an invoice | Recurring billing where payer returns the slip with payment |
Scannable remittance | OCR-readable document accompanying the payment | Mid-volume operations transitioning from paper to electronic |
Email or web-based | PDF, HTML, or portal-delivered document | Most modern AP-to-AR communication |
EDI 820 (electronic) | Structured data file via EDI VAN, AS2, or SFTP | High-volume trading partners with EDI infrastructure |
What is electronic remittance advice?
Electronic remittance advice (ERA) is a structured digital document that conveys remittance information between trading partners using a defined data standard, most commonly the ANSI ASC X12 EDI 820 transaction set in the United States. Instead of a human-readable PDF, an ERA is a machine-readable file that the supplier's ERP can ingest directly and apply cash automatically.
The EDI 820 is the workhorse format for high-volume B2B in North America. It carries the same information you'd find on a check stub (payment amount, invoices being paid, deductions, references) but in a format that flows straight into AR systems without anyone keying it in. Healthcare uses the related X12 835 for claim payment remittance, which works similarly but carries clinical claim adjustment codes alongside the dollar amounts.
The advantage is straight-through processing on the supplier's side. The supplier receives the payment, receives the matching ERA, and the ERP applies cash to the right invoices automatically. The disadvantage is the lift to set up. EDI requires either a value-added network connection, an AS2 setup, or an SFTP pipeline, plus mapping work to translate between the partner's flavor of the spec and your own. For trading relationships where both sides do millions of dollars a year, the lift pays off. For smaller suppliers, it's overkill.
How does email and web-based remittance advice work?
Email and web-based remittance advice deliver the same payment detail as a paper stub, but as a PDF attachment, an HTML body, or a record in a vendor portal. The supplier's AR team opens the document, reviews it, and keys the relevant detail into their ERP. If the document is well-structured, they may run it through an OCR or extraction tool to pull the data automatically.
This is the most common format in mid-market B2B today. It's flexible (any vendor with an email address can receive one), it's cheap to produce (no postage, no print costs), and it's better than nothing for cash application. The downside is that PDFs and HTML emails aren't structured data. Even if the layout is consistent, the supplier still has to extract values and match them to open invoices, which is part of what makes manual cash application a slog.
Vendor portals are a step up from email. The payer pushes the remittance into the supplier's portal account, and the supplier can view it in the browser or download a CSV or structured file with the underlying data. This sits between email PDFs and full EDI: easier to consume than a PDF, easier to set up than an EDI 820 connection.
Why Does Remittance Advice Matter for Your Business?
Remittance advice matters because it determines how much friction sits between your AP team sending a payment and your supplier's AR team applying cash to the right invoices. When that friction is high, you get vendor inquiries, late-payment disputes, blocked credit lines, and an AP inbox clogged with "what was this payment for?" emails. When the friction is low, the payment lands, the invoices clear, and the relationship runs.
The business case for clean remittance advice is more about avoided cost than direct cost reduction. A payment without proper remittance information doesn't break the payment, since the money still moves, but it generates a downstream tail of follow-up work that lands on people who are already busy. The supplier calls, the AP analyst pulls up the payment record, both sides hunt through invoices to figure out what got paid, and an hour of two people's time evaporates over a single misapplied cash entry.
If you're running mostly paper checks, the cost is even higher. Each check costs $2 to $4 to issue (median) according to AFP's 2022 Payments Cost Benchmarking Survey, and the remittance information typically rides on the stub or in a separate envelope, adding to the labor and the chance of mismatch. Moving payment volume to virtual card or ACH consolidates the remittance into the same workflow as the payment itself.
How does remittance advice speed up reconciliation?
A complete remittance advice lets the supplier's AR team apply cash to the right invoices on the same day the payment lands, rather than parking it in a suspense account while they figure out what it covers. On the payer side, when the remittance information ties back to specific invoice numbers in your ERP, your AP reconciliation closes out cleanly without manual matching.
Speed of reconciliation is one of those metrics most finance teams under-measure. The cost isn't usually a single big number. It's a thousand small drags: cash sitting in supplier suspense accounts that should be applied to your AR, open POs that should be closed, trial balance reconciliations taking an extra day because half the entries lack proper backup.
According to Ardent Partners' 2024 State of ePayables report, only 32.6% of B2B invoices achieve straight-through processing, meaning the other two-thirds touch human hands at some stage. A clean remittance advice doesn't fix all of that, but it removes one of the most common reasons a payment gets stuck.
What happens when remittance advice is missing or incomplete?
When remittance advice is missing or incomplete, payments land in supplier suspense accounts until someone manually researches what the payment covered. The result is delayed cash application, vendor calls to your AP team, and in worst cases, suppliers placing your account on credit hold because they can't reconcile what they've been paid against what's open.
The pattern is predictable. A consolidated payment for $200,000 hits a supplier's bank account. The supplier's AR team has $250,000 in open invoices for that customer. Without a remittance advice itemizing which 14 invoices the $200,000 covers, the AR analyst either calls your AP team or guesses. Most won't guess.
So the payment sits unapplied for days while the supplier waits for someone on your end to clarify. If the supplier has any kind of credit policy, that delay can trigger a hold on future shipments, and the cost of the missing remittance advice ends up being measured in the goods you couldn't get because your vendor stopped shipping.
How Do You Send Remittance Advice?
You send remittance advice the same way you send the underlying payment, with the format matched to the supplier's preferences and capabilities. Mechanics fall into two camps. First is manual creation, where a person assembles the remittance information from your AP system and sends it to the supplier. Second is automated delivery, where your AP platform generates and transmits the remittance with every payment without human involvement.
For manual delivery, the workflow is usually some version of pulling payment details from your ERP, formatting them in a template (Excel, Word, or a check stub layout), and sending by email, mail, or upload to a vendor portal. It works at low volumes. Past about 100 payments a month, the labor and error rate become hard to ignore. Most teams who've crossed that threshold end up looking at accounts payable automation as a way to bundle remittance creation into the payment workflow itself.
What should a remittance advice template include?
A remittance advice template should include the payer's company name and contact details, the payment amount and date, the payment method and reference number, and an itemized list of every invoice the payment covers with invoice numbers, dates, gross amounts, deductions, and net amounts. It should also include a clear payee name and any vendor ID or account number the supplier uses to identify your account on their side.
Detail level matters more than formatting. A plain text email with the right information beats a polished PDF that's missing references. The two fields suppliers ask about most often are the check or transaction reference number, so they can tie the document to the actual deposit, and the deduction reasons, so they can post credits or short pays correctly without opening an investigation.
How does automated remittance advice work?
Automated remittance advice is generated by your AP or payments platform at the moment the payment is initiated, then delivered to the supplier through whatever channel they've specified, whether that's email PDF, EDI 820 to their VAN, or a push to a vendor portal. The data ties directly to the payment record and the underlying invoices in your ERP, so there's no manual assembly and no chance the remittance drifts out of sync with the actual payment.
A modern AP platform handles the delivery format on a per-supplier basis. A small vendor gets a PDF email. A national distributor with EDI capability gets an EDI 820 file. A supplier on the platform's own network has the data pushed directly into their AR system. That's the part hard to replicate manually: supporting four delivery formats at once and getting each one right for the supplier on the other end. The same platforms that handle virtual card payments usually treat remittance delivery as a built-in feature, not a separate workflow.
Streamline Payments and Remittance Advice with Corpay
If your AP team is hand-building remittance advice in Excel and emailing it out after each payment run, the math is working against you. The Ardent Partners cost-per-invoice figure mentioned earlier captures all the touches downstream of approval, and remittance creation (plus the follow-up vendor inquiries that come with it) is part of that cost, even if most teams don't track it separately.
Corpay's AP automation platform generates and delivers remittance advice with every payment, in the format each supplier expects. Pay a vendor by virtual card, ACH, check, or cross-border wire, and the matching remittance goes out automatically with the invoice detail your supplier's AR team needs to apply cash on day one. The data syncs back to your ERP so your AP reconciliation closes cleanly without manual matching.
For high-volume trading partners on EDI, the platform produces 820 files in their preferred spec and delivers them through their VAN, AS2, or SFTP setup. For everyone else, email PDF and portal delivery handle the rest. And because Corpay's payments automation is built as an ERP complement rather than a replacement, the remittance data flows back into NetSuite, Sage Intacct, Microsoft Dynamics, or whichever system you're running, without forcing your team to leave the workflows they already know.
The payoff isn't just fewer remittance documents to assemble. It's fewer vendor inquiries, faster cash application on your suppliers' side, cleaner audit trails, and AP staff who can spend their time on exception handling instead of formatting payment stubs. See how Corpay handles remittance delivery for a customer of similar size and complexity to your operation. Ask for before-and-after metrics, like number of vendor inquiries per month or days to close AP reconciliation, and compare them to your own. That's the test that matters.
Frequently Asked Questions
These are the questions AP and AR practitioners ask most often when they're trying to clean up their remittance process or move from manual to automated delivery.
What does remittance advice mean?
Remittance advice means a notification from a payer to a payee that confirms a payment has been issued and explains what the payment covers. The term comes from older paper-based payment workflows where a remittance slip accompanied a check, but the concept applies to any modern B2B payment. The document tells the supplier which invoices the payment is settling and how the funds were sent.
Is remittance advice legally required?
In most U.S. and Canadian B2B contexts, remittance advice is not legally required. It's a business practice rather than a regulatory one. Some industries do have format-specific requirements; U.S. healthcare claim payments under HIPAA, for example, use the X12 835 electronic remittance advice as the standard for claim payment information. Outside of regulated contexts, the obligation is contractual or relational, not statutory.
What is the value of a remittance advice?
The value of a remittance advice is reduced friction in cash application. The payee can apply funds to the correct invoices on receipt rather than chasing the payer for clarification. For the payer, the value is fewer vendor inquiries, cleaner AP reconciliation, and stronger supplier relationships. The cost of skipping remittance advice usually shows up in indirect ways: delayed credits, calls to AP, and occasional credit holds when suppliers can't tie payments to open invoices.
What is the difference between remittance advice and a receipt?
A remittance advice is sent by the payer to the payee to explain an outgoing payment. A receipt is sent by the payee to the payer to acknowledge that a payment was received and applied. They flow in opposite directions and serve different sides of the transaction. In some workflows, a supplier issues a paid-invoice acknowledgment after applying a remittance advice, but the two documents are not interchangeable.
Can you automate remittance advice?
Yes. AP automation and payments platforms generate remittance advice automatically as part of each payment run, deliver it to the supplier in their preferred format (PDF email, EDI 820, vendor portal), and sync the underlying data back to the ERP. Automation removes the manual step of assembling remittance information for each payment, which is one of the more tedious parts of running an AP function at any volume.
What is an ACH remittance advice?
An ACH remittance advice is the payment detail that accompanies an ACH transaction. The ACH network supports an addenda record (the CTX format) that can carry structured EDI 820 remittance data inside the same payment file, which means the supplier's bank can route both the funds and the remittance information together. Many ACH payments still travel without addenda. In those cases, the payer sends remittance separately by email, portal, or EDI.
Switch to Corpay
Discover how making the move to Corpay streamlines payments and strengthens your business.
Talk to an ExpertSmarter payments. Stronger growth. Keep business moving.
Corpay powers payments for 800,000+ businesses worldwide. Let’s build what’s next for yours.