Also called: Remittance advice, Remittance data
What remittance information is
Remittance information is data a payer sends to explain what a payment covers. It can identify the payer, invoice numbers, purchase orders, amounts paid, discounts, deductions, and payment references. You use those details to connect incoming funds to the right customer and open accounts receivable items.
The information is separate from the money itself. Remittance information explains the purpose or allocation of a payment; remittance is the money sent to pay an obligation. For example, a buyer can send one payment covering three invoices and provide the invoice numbers and amount assigned to each.
The payment tells you how much arrived; remittance information tells you which invoices that money is meant to cover.
How the information reaches you
A payer can send remittance information inside a payment message or separately. With ACH payments, many businesses send the details separately by email or web portal, while only a small share include them in an ACH addendum. Some payment formats limit how much detail fits in the message.
Other delivery routes include electronic data interchange files, payment portals, bank files, lockbox records, and paper checks or check images. When the payment and its details arrive through different routes, your staff must identify which advice belongs to which deposit before applying the cash.
Why complete details matter
If a payment arrives without a usable invoice reference, your accounts receivable team cannot reliably assign it to the right open balance. A consolidated payment, partial payment, short pay, discount, or deduction adds another detail to verify. The funds can remain unapplied while staff investigate the difference.
Remittance information itself is not a card-processing fee, and it does not have a standard merchant-statement fee line. Its business impact is the work required to match and reconcile payments. Structured fields that connect the payment, payer, and invoice reduce manual entry and make exceptions easier to identify.
What you can actually change
You cannot control every format a customer sends, but you can set clear requirements for the details your team needs and define how exceptions are reviewed.
- Specify required fields, such as payer ID, invoice number, amount paid, and deduction reason.
- Ask customers to send remittance details through a consistent channel and identify the related payment.
- Match payment totals against invoice allocations, and route missing or conflicting details for review.
- Track unapplied cash, exception counts, and manual handling to find recurring gaps.
- Set required fields. Give customers a standard list of references and amounts your team needs to apply each payment.
- Connect the records. Keep the remittance advice linked to its bank deposit and invoice records during reconciliation.
- Review exceptions. Measure unmatched payments and investigate missing references, partial payments, and unexplained differences.
Frequently asked questions
Is remittance information the same as remittance?
No. Remittance is money sent to pay an obligation. Remittance information is the accompanying or separately delivered data, such as invoice numbers and amounts, that explains how the payer intends the money to be applied.
What should remittance information include?
Include enough detail to identify the payer and connect the payment to the correct obligation. Useful fields include invoice or purchase-order numbers, amounts paid, payment references, discounts, deductions, and the reason for any adjustment.
Does remittance information affect payment-processing fees?
Remittance information is not a card-processing fee and does not have a standard fee line on a merchant statement. Incomplete details create operational work, such as manual matching and investigation of unapplied cash, rather than a direct processing charge.