A remittance statement is a document a buyer sends a seller to confirm that a payment has been made and to show exactly which invoices it covers. It works as a cover letter for the money: when one check, wire, or ACH transfer settles several invoices at once, the remittance statement tells the vendor’s accounts receivable team how to split the payment across those invoices. Without it, the vendor has to guess, and guesses lead to misapplied payments, invoices that keep aging toward overdue, and collection notices for balances that were already settled.
The document itself is usually a single page or a single electronic record. Its job is narrow but important: link a payment to specific invoices, explain any difference between what was invoiced and what was paid, and give both sides a reference they can point to later if something needs to be reconciled or disputed.
What Goes on a Remittance Statement
A useful remittance statement pulls a handful of specific data points from your purchase orders and the vendor’s original invoices:
- Payer information: your company’s legal name, address, and contact details so the vendor can identify where the payment came from.
- Vendor information: the legal name of the company receiving the funds, matching their invoicing records.
- Invoice numbers: each invoice being paid, listed individually so the vendor can mark them closed.
- Amounts per invoice: the specific dollar amount applied to each invoice, which matters most when you’re making partial payments.
- Adjustments: any credits, returns, or early payment discounts that reduce the total from the original invoice amounts.
- Payment method and date: check, wire, or ACH, along with the date the funds were sent.
- Total payment amount: the sum actually transferred, equal to the invoice amounts minus any adjustments.
Federal agencies making payments must also include a valid Taxpayer Identification Number for the party entitled to the payment, which for a business is the Employer Identification Number issued by the IRS. An incomplete TIN makes the payment request itself incomplete under federal rules.1eCFR. 31 CFR 256.13 – Are Agencies Required to Supply a Taxpayer Identification Number (TIN) When Submitting a Request for Payment? Private businesses aren’t bound by that regulation, but including a TIN or account reference is common practice because it speeds up matching on the vendor’s side.
Most accounting software generates the statement automatically when you record a payment. If you’re filling in a template, check every invoice number against the vendor’s records before sending. A single transposed digit can leave the payment in an unapplied queue while the invoices it was supposed to cover keep aging.
Handling Discounts, Credits, and Partial Payments
Remittance statements matter most when the amount paid doesn’t match the amount invoiced. The most common reason is an early payment discount. Terms like “2/10 net 30” give the buyer a 2 percent discount for paying within 10 days, with the full balance due in 30. “3/10 net 30” works the same way with a 3 percent discount, and variations of this structure appear across industries where suppliers want to accelerate cash flow.
When you take a discount, the remittance statement needs to show the math: the original invoice amount, the discount percentage and dollar amount deducted, and the net amount actually paid. The same logic applies to credit notes for returned goods, volume rebates, and any other adjustment. If the vendor can’t immediately see why the payment is less than the invoice total, they’ll either short-apply it and leave a balance showing or contact you for an explanation. Either outcome costs time on both sides that the remittance was supposed to save.
How Remittance Statements Are Sent
Formats range from a tear-off stub on a paper invoice to a fully automated electronic transmission, depending on how the two businesses operate.
Paper and Email
The simplest version is the perforated slip attached to a paper invoice. You fill in the payment details, tear it off, and mail it back with the check. For wire or ACH payments, a PDF attached to an email does the same job. The remittance document arrives separately from the payment itself, so the two need to reach the vendor close enough in time that the accounting team can match them without confusion.
ACH With Addenda Records
ACH payments can carry remittance data directly on the transaction using addenda records. The CCD+ format allows a single 80-character addenda record, which fits a reference number or a short note but not detailed invoice-level data. For payments covering multiple invoices, the CTX format supports multiple addenda records carrying structured remittance information, often formatted as an EDI 820 transaction.2Federal Reserve Bank Services. Help With Health Care ACH Payments Embedding the remittance in the payment removes the matching problem entirely: the vendor doesn’t have to reconcile a separate document against a deposit.
EDI 820 for High-Volume Payers
Large enterprises processing thousands of invoices use the EDI 820 transaction set, a standardized electronic format that transmits payment and remittance data directly between accounting systems. An 820 document carries invoice numbers, payer and payee identification, billed and paid amounts, adjustment details, and tax information in a structured format the vendor’s system can process automatically.33M. 820 Payment Order/Remittance Advice The vendor’s system generates an automated acknowledgment confirming receipt, and the cycle runs without anyone manually keying in data.
How the Vendor Uses It
When the vendor’s accounts receivable team receives your payment, they pull up the accompanying remittance and match it against their open invoices line by line. Each invoice number gets matched to an invoice in their system, amounts are verified, and the invoices are marked as paid. For clean payments this is mechanical work.
The document earns its place when something doesn’t match. If your payment is $47 less than the invoice total because you deducted for a damaged shipment, the remittance statement says so before anyone has to pick up the phone. Without that explanation, the vendor sees an underpayment and has to decide whether to apply it partially, leave it unapplied, or start chasing you for the difference.
Clean reconciliation also stops the collections machinery from starting up unnecessarily. Businesses commonly send payment reminders at 30, 60, 90, and 120 days past due, with the final notices threatening formal collection action or credit bureau reporting. A matched remittance keeps invoices from aging into that cycle when they’ve already been paid. If a real dispute does arise later, the remittance is the primary evidence both sides use to sort it out.
Guarding Against Payment Redirection Fraud
Remittance instructions include routing information, and that makes them a target. Business Email Compromise scams cost American businesses $2.77 billion in reported losses in 2024.4FBI. 2024 IC3 Annual Report A common version has a scammer impersonating a vendor and asking that future payments be sent to a new bank account. The request usually arrives by email, sometimes from a spoofed address that looks nearly identical to the vendor’s real domain.5U.S. Secret Service. Understanding Business Email Compromise
These scams work because vendors switching banks isn’t unusual, so the request doesn’t feel suspicious. Scammers add urgency, claiming an account is being audited or can no longer accept payments, to push accounts payable into acting without verifying.5U.S. Secret Service. Understanding Business Email Compromise
Protection comes from internal controls. Separate the person who authorizes a payment from the person who updates vendor banking details in your system, so a single compromised email can’t redirect funds without a second set of eyes.6OCC (Office of the Comptroller of the Currency). Internal Control Questionnaires and Verification Procedures Confirm any change to remittance instructions by calling a known number for the vendor, not a number included in the email requesting the change.
How Long to Keep Remittance Statements
Remittance statements support your tax records. The IRS requires businesses to keep records that back up items of income, deduction, or credit on a return for as long as the period of limitations applies, which in most cases is at least three years from the date you file the return. For payroll-related payments, the retention period extends to four years after the tax is due or paid, whichever comes later.7Internal Revenue Service. How Long Should I Keep Records
The IRS doesn’t require a particular format. What matters is that your records clearly show income and expenses, backed by supporting documents like invoices, canceled checks, account statements, and paid bills. A remittance statement fits that description: it documents the amount, the date, the invoices covered, and the business purpose. If a canceled check isn’t available during an audit, other financial records showing the payment and its business purpose can substitute, and a remittance statement is exactly that kind of corroborating document.8Internal Revenue Service. Publication 583 – Starting a Business and Keeping Records