A remittance report is a document the payer sends to the recipient explaining which invoices a payment covers, how much is being applied to each, and what discounts, credits, or other adjustments account for any difference between the invoice totals and the amount deposited. Also called remittance advice, it turns a deposit into something the recipient’s accounts receivable team can actually post against open invoices. Without it, a wire or ACH credit is just a number in a bank feed.
What a Remittance Report Contains
The content varies by company and system, but a usable report has three parts.
The header identifies the payer, the recipient, the payment date, the method, and the total amount. It usually carries a reference number the payer assigns to the batch.
The line-item detail is the working section. Each invoice being paid gets its own entry showing the invoice number, the original billed amount, and the amount being applied from this payment. If one payment covers five invoices, all five appear individually. Partial payments show both the original balance and the portion paid so the recipient knows what remains open.
The adjustment section explains anything that reduces the net below the invoice total. Early payment discounts are the most common, driven by standard trade terms such as 2/10 net 30, which give the buyer two percent off for paying within ten days. Other adjustments include credits for returned goods, allowances for damaged shipments, and agreed rebates. Each adjustment should reference the specific invoice or credit memo it relates to rather than just shrinking the total with no explanation.
How the Report Travels From Payer to Recipient
Remittance advice moves through several channels, and the format largely decides how much manual work the recipient has to do.
Paper, PDF, and Email
Paper advice still exists, typically as a detachable stub on a check or a document mailed with it. Some companies fax or email a PDF. These work, but they force manual data entry on the receiving end, which slows reconciliation and introduces mistakes. Lockbox services can digitize incoming paper remittances for a per-item fee.
EDI 820 and ACH Addenda
Electronic Data Interchange is the structured option for higher-volume trading partners. The ANSI X12 820 transaction set was built as a payment order and remittance advice format, carrying payment amount, effective date, bank routing, invoice references, and adjustment codes in a machine-readable layout.1SAP Help Portal. Ariba Network 820 Remittance Advice Implementation Guidelines An 820 maps directly onto what an AR system needs, so most of the reconciliation can be automated.
For ACH payments, the transaction format controls how much remittance data can ride along. A CCD entry supports only a single addenda record, so the remittance detail is limited to a short note. A CTX entry supports up to 9,999 addenda records and can carry a full ANSI X12 message inside the payment itself.2Nacha. ACH File Details CTX is the better choice for payments covering multiple invoices, assuming both banks support it.
ISO 20022
The payments industry is converging on ISO 20022, a messaging standard with over 350 remittance data elements available for structured information.3Federal Reserve. New Guide Provides Clarity on Use of ISO 20022 Remittance Information That is far more than legacy wire transfers could carry. FedNow, RTP, Fedwire, and CHIPS are either on the standard or migrating to it, which supports higher straight-through processing rates and better transparency along the payments chain.
How the Recipient Uses It
On the receiving side, work begins the moment cash hits the bank account. The AR specialist first matches the deposit amount to the total on the remittance advice and confirms the payer. This step catches wire errors and duplicate payments early.
Once the deposit is verified, the specialist works through the line items, closing each listed invoice against the open receivables ledger. A payment covering four invoices clears four separate entries.
Adjustments get closer scrutiny. If the advice shows a discount, the AR team checks that the payment actually arrived inside the discount window. A buyer claiming a 2/10 net 30 discount on day fifteen doesn’t qualify, and the difference becomes a short payment to follow up on. Credits and returns on the advice get matched to previously issued credit memos. If there’s no matching memo, the adjustment is flagged as a deduction dispute.
When the deposited amount doesn’t match the remittance total, the AR team contacts the payer’s accounts payable department. The usual culprits are data entry mistakes, a credit memo that crossed in transit with the payment, or a bank fee that trimmed the wire. Speed matters because unresolved variances age on the receivables report and distort the picture of what customers actually owe.
Common Discrepancies the Report Helps Resolve
The same handful of problems come up repeatedly, and the remittance report is where diagnosis starts.
- Unauthorized deductions, where the buyer subtracts an amount that doesn’t match any agreed discount, credit, or allowance. This often happens when the buyer’s AP system auto-applies a promotional rebate the supplier hasn’t approved.
- Expired discount claims, where the buyer takes an early payment discount after the window closed. The AR team verifies the payment date against the invoice terms.
- Tax exemption adjustments, where a tax-exempt buyer deducts sales tax from the invoice total. If the supplier didn’t have the exemption certificate on file at invoicing, it looks like a short payment until the certificate is collected.
- Duplicate payments and credits, where a buyer pays the same invoice twice or references a credit memo that was already applied. Cross-referencing the remittance to the AR ledger catches these before they compound.
- Human error, including transposed invoice numbers, decimal mistakes, and payments posted to the wrong vendor account.
The remittance report doesn’t prevent these problems, but it gives both sides a shared document to work from. Without one, every conversation starts from scratch.
How It Gets Created and Sent
Most ERP and accounting systems generate the remittance report automatically when a payment batch is approved, pulling invoice references, amounts, and adjustment codes from the AP ledger. The report should leave at the same time the payment does, whether that’s an ACH, wire, or check.
The document records the payer’s intent for how the funds should be applied. If a company sends $15,000 to cover three specific invoices, the remittance report is what locks in that allocation. Suppliers that receive money with no context will apply it however they see fit, which might mean crediting an older disputed invoice rather than the three current ones the buyer wanted cleared.
For electronic payments, the strongest practice is to embed the remittance data in the payment transaction itself through CTX format or to transmit an EDI 820 at the same time. Sending the advice as a separate email days later undercuts the point, because the AR team has already started guessing.4Federal Reserve Bank of Minneapolis. ACH Payments and Remittance Information Solutions for Businesses
What Happens Without a Remittance Report
When a payment arrives with no advice attached, the AR team has to reverse-engineer it. They check the amount against open invoices looking for an exact match. That works for single-invoice payments and falls apart when one payment covers several invoices or includes deductions. A $47,312 deposit with no explanation could match dozens of combinations.
The consequences stack up fast. Invoices that have actually been paid keep aging on the receivables report, pushing the over-90-day bucket higher and making collections performance look worse than it is. Staff lose time calling the buyer’s AP department to ask what the payment was for. In the worst case, the supplier applies the payment to the wrong invoices and sends collection notices on bills the buyer believes are settled. That damages the relationship and creates a dispute that takes longer to untangle than sending the advice would have taken in the first place.
How Long to Keep Remittance Records
Remittance reports are tax-relevant business records. The IRS general rule is to keep records for three years from the date you filed the return or two years from the date you paid the tax, whichever is later. If you underreport income by more than 25 percent of gross income, the retention period extends to six years. Employment tax records must be kept for at least four years.5Internal Revenue Service. How Long Should I Keep Records
If you store remittance data electronically, the IRS requires that machine-readable records stay accessible and processable for the entire retention period. The data must be retrievable, sortable, and printable on demand. Using a third-party service to host the records doesn’t shift the obligation; the business remains responsible wherever the data physically lives.6Internal Revenue Service. Revenue Procedure 98-25
Beyond the tax rules, most companies keep remittance records for at least seven years. Contract disputes, audit questions, and vendor reconciliation issues can surface well after the minimum IRS window closes, and the remittance report is often the cleanest proof of what a payment was meant to cover.