Finance Index
What is remittance advice and why do vendors need it?
Reference guide to remittance advice best practices, including payment timing, method choices, control points, reconciliation, and vendor communication.
Remittance advice is the detail that tells a vendor what a payment covers: which invoices, the amounts, any discounts taken, credits applied, and short-payment reasons. Without it, the vendor's AR team can't apply your payment correctly, leading to misapplied cash, false past-due notices, and "where's my payment" disputes - even when the money arrived exactly as intended.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| Remittance advice | Remittance advice is the detail that tells a vendor what a payment covers: which invoices, the amounts, any discounts taken, credits applied, and short-payment reasons. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Payment impact | Good remittance is line-level: every invoice number, the amount paid against each, discounts and credits with reasons, and a short-pay explanation where applicable. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| What should a good remittance | Invoice numbers and amounts paid, discounts taken, credits applied, short-payment amounts with reason codes, the payment method and date, and a reference number - enough that the vendor's AR team applies it without contacting you. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Vendors keep applying | Send complete line-level remittance with every payment, match your invoice numbers to the vendor's exactly, and deliver it in a format their AR system can consume (CTX addenda or portal) - most misapplication is a remittance-quality problem, not a vendor error. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Related terms | CTX carries remittance inside the payment for straight-through application (best for high-volume vendors); a separate email or portal works when the vendor's bank can't pass addenda - match the method to what the vendor's AR system can actually ingest. | Reduces payment errors, timing issues, and reconciliation cleanup. |
What makes good remittance, and how should it travel with the payment?
Good remittance is line-level: every invoice number, the amount paid against each, discounts and credits with reasons, and a short-pay explanation where applicable. Delivery options: CTX addenda carried inside the ACH payment (so the vendor's system auto-applies it), a separate email, or a vendor portal. The best practice is to make remittance self-service and complete enough that the vendor never has to call.
What should a good remittance include?
Invoice numbers and amounts paid, discounts taken, credits applied, short-payment amounts with reason codes, the payment method and date, and a reference number - enough that the vendor's AR team applies it without contacting you.
Vendors keep applying our payments to the wrong invoices and our statements show false past-dues - how do I fix remittance quality?
Send complete line-level remittance with every payment, match your invoice numbers to the vendor's exactly, and deliver it in a format their AR system can consume (CTX addenda or portal) - most misapplication is a remittance-quality problem, not a vendor error.
How do I send remittance with ACH - ctx addenda vs separate email vs portal?
CTX carries remittance inside the payment for straight-through application (best for high-volume vendors); a separate email or portal works when the vendor's bank can't pass addenda - match the method to what the vendor's AR system can actually ingest.
What is the addenda record limit on ACH and what happens when one payment covers 200 invoices?
CCD allows one addenda record; CTX allows up to 9,999, enough for hundreds of invoices' remittance - for very large counts, CTX or a portal/email file is required so all invoice detail travels with the payment.
A vendor says they got the money but no remittance and is holding our account hostage - fastest fix?
Send the line-level remittance immediately by email (invoices, amounts, reference), then set up a durable channel (addenda or portal) so it travels automatically next time - the money arrived; the missing detail is the whole problem.
How should remittance handle credits, short payments, and chargebacks?
Show each as a distinct line with a reason: invoice, gross, deduction amount, and reason code, so the vendor can self-serve the explanation and dispute the right item rather than the whole payment.
What is electronic remittance delivery via vendor portals vs email - what do large vendors require?
Large vendors increasingly require structured electronic remittance (portal or EDI/addenda) their AR system auto-applies; email PDFs work for smaller vendors but don't scale - confirm each major vendor's preferred remittance channel during enablement.
Should remittance go to the vendor's ar email or the sales rep, and how do we maintain contacts at scale?
Always to the AR/remittance contact, never the sales rep; maintain a dedicated remittance email per vendor in the vendor master and let vendors self-update it through a portal so contacts stay current without manual upkeep.
Stampli perspective
Stampli keeps remittance detail attached to the payment as part of execution, and its vendor-facing capabilities give suppliers self-service visibility into what each payment covers - so cash application is clean and remittance questions get answered by the system rather than by AP's inbox.