What Is a Remittance Advice? The Document That Tells a Vendor How to Apply Your Payment
A remittance advice is the document that tells a vendor how to apply a payment they've received. It accompanies a check, goes alongside an ACH transfer, or follows a virtual card payment — and it lists which specific invoices the payment is covering, how much of each invoice is being paid, and any credits or adjustments that were applied. Without a remittance advice, the vendor has a payment in hand and no clear information about what it's for.
The remittance advice is one of those documents that doesn't get a lot of attention — until something goes wrong. A payment applied to the wrong invoice creates an aging mismatch on the vendor's books, which surfaces during statement reconciliation and requires manual investigation to unwind. Hundreds of payments without proper remittance detail, across dozens of vendors, compounds into a significant amount of avoidable reconciliation work — for both the paying party and the vendor.
A complete remittance advice contains enough information for the vendor's AR team to apply the payment correctly.
Information on a remittance advice
- Paying party information — company name, address, contact
- Vendor information — who's being paid
- Payment method — check, ACH, wire, virtual card
- Payment date and payment amount
- Payment reference — check number, ACH trace number, or virtual card reference
- List of invoices being paid — for each: invoice number, invoice date, invoice amount, amount being applied from this payment
- Credits applied — any credit memos being used to offset invoices
- Discounts taken — early-pay discounts applied, with reference to the terms
- Any deductions or adjustments with explanations
- Total of applied amounts (should equal the payment amount)
Remittance advices come in three common forms. Paper remittance accompanies paper checks — typically a one-page stub attached to the check or on the same page. Email remittance sends the detail via email, usually as a PDF, often triggered by the ACH or wire being sent. Electronic Data Interchange (EDI) or API-based remittance delivers the detail as structured data that the vendor's AR system can ingest automatically.
EDI remittance — specifically the EDI 820 transaction set — is the most efficient format because it eliminates manual data entry on the vendor's side. The vendor's AR system receives the structured data, automatically applies the payment to the correct invoices, and updates balances without human intervention. For high-volume vendor relationships, EDI or API remittance is the clear choice if both sides support it.
ACH alone without remittance detail is actually worse than check with remittance detail, because the vendor receives the funds but has to figure out which invoices they cover. If you send ACH payments without accompanying remittance email, you're shifting the reconciliation burden entirely to the vendor — which they notice, and which affects the relationship.
When a payment lacks remittance detail, or the remittance detail is unclear, the vendor's AR clerk has to guess which invoices the payment covers. They usually guess reasonably — apply to the oldest invoice, or to the invoice whose amount matches exactly — but sometimes they guess wrong.
A misapplied payment creates an aging mismatch. The vendor's books show an old invoice as paid when it's actually a newer invoice that's paid. On the next statement, the customer's AP shows a newer invoice as paid while the vendor shows an older invoice as paid — same net balance, different invoice-level picture. Reconciliation catches the mismatch; unwinding it requires someone to figure out which invoice the payment actually covered.
Multiply this across hundreds of payments per year to a vendor, and the reconciliation work compounds. It's a quiet administrative cost that nobody budgets for but everyone pays. Good remittance advice practice eliminates the problem at source.
Frequent remittance advice failures
- Payment sent without any remittance detail — vendor has to guess how to apply
- Remittance email sent to a different person than the payment recipient — never connected to the funds
- Invoice references that don't match the vendor's invoice numbers — customer's internal reference not useful to vendor
- Discounts taken without explanation — vendor sees less than expected and opens a dispute
- Multiple invoices paid by one payment with no breakdown — vendor doesn't know the split
- Credit memos applied without reference — vendor can't tell which credit was used
- Remittance sent well after the payment — vendor applies based on guess before the detail arrives
Get AP insights in your inbox
Get our weekly roundup of AP automation tips and industry news. No spam, ever.
No spam. Unsubscribe anytime.
Remittance and Reconciliation
For vendor statement reconciliation, remittance advice quality is a leading indicator. Vendors whose remittance advices are consistent and clear have cleaner AR aging, which produces cleaner reconciliations. Vendors whose remittance is inconsistent have messier aging, which produces more discrepancies to investigate each month.
From the vendor's perspective: customers who send clear remittance are easier to serve. The AR clerk can apply payments quickly, statements are accurate, and when disputes arise, the documentation is available. The customer's 'professionalism' in how they pay is often judged largely by the quality of their remittance advice practice.
Modern AP platforms generate remittance advices automatically as part of payment processing. When a batch of invoices is approved for payment, the system produces the remittance detail (what invoices, what amounts, what credits, what discounts) and delivers it via the vendor's preferred method — email, EDI, vendor portal, or attached to a paper check.
For payment methods that carry limited remittance capacity (ACH traditionally carries a small 'addenda' field, often 80 characters), the automated system can split the remittance — send the ACH with a reference, and follow with an email containing the full detail. For paper checks, the remittance detail is printed directly on the check stub. The automation eliminates the 'forgot to send remittance' failure mode entirely.
International payments have specific remittance challenges. Wire transfers across borders carry limited remittance data in the SWIFT message. Currency conversion rates affect the amount received versus the amount sent. Bank fees deducted en route change the final amount the vendor receives. Sending clear remittance advice alongside international payments — usually by email — is essential for vendors to reconcile international transactions correctly.
Some international AP platforms provide enhanced remittance features specifically for cross-border payments — notification of the exchange rate used, breakdown of fees, expected receipt amount, and detailed invoice application. For companies with meaningful international AP activity, these features significantly reduce the reconciliation friction that international payments otherwise create.
The remittance advice is the document that turns a payment into an applied payment. Without it, vendors guess how to apply funds and reconciliation problems accumulate. With it, vendor AR applies payments correctly, statements stay accurate, and vendor relationships stay smooth. Good remittance practice is a small operational investment with an outsized effect on AP quality — the kind of thing that doesn't get praise when done well but creates friction across the whole payment function when done poorly.
Written by
Sarah Blake
Head of Product
Former AP Manager at a $200M construction firm, now leads product at Covinly. Writes about what AP teams actually need from automation — beyond the marketing promises.
View all posts