Remittance advice is information sent by a payer to explain how a payment should be allocated. In accounts receivable operations, it usually identifies the payer, payment amount and currency, bank reference, invoices being settled, credit notes, discounts, deductions, and any amount intentionally left open.
Remittance advice supports cash application, but it is not the payment itself and it does not prove that funds settled. The operator must link the advice to a verified bank receipt and to valid open items in the correct customer account.
What remittance advice should include
| Field | Operational use |
|---|---|
| Payer legal name and customer number | Identifies the party sending funds and the intended account |
| Payment date, amount, and currency | Supports matching to the bank receipt |
| Bank or payment reference | Links the advice to a specific settlement transaction |
| Invoice numbers and amounts | Defines the open items the payer expects to clear |
| Credit notes or discounts | Explains reductions supported by existing customer-account items |
| Deductions or short-pay reasons | Separates disputed or adjusted amounts from missing cash |
| Payer contact and document ID | Provides a route for clarification and prevents duplicate processing |
| Beneficiary entity or account | Helps allocate payments where a group operates several legal entities or bank accounts |
Common remittance-advice formats
Advice can arrive in an email body, PDF, spreadsheet, customer portal, bank lockbox file, EDI message, or other structured payment file. A human-readable document may be easy to review but inconsistent to process at volume. A structured file may be easier to validate automatically, yet still contain the payer's invoice references rather than the seller's numbers. The format does not remove the need to reconcile totals, identities, and open-item status.
| Format | Strength | Control concern |
|---|---|---|
| Email text | Fast and accessible | Unstructured, easy to overlook, and may omit line-level detail |
| PDF advice | Readable and often contains a complete schedule | Requires reliable extraction and duplicate-document checks |
| Spreadsheet | Useful for large invoice populations | Columns, formulas, and invoice formats can change without notice |
| Customer portal | Can provide controlled payer context | Retrieval may be manual and advice may be updated after first download |
| Bank or lockbox file | Connects payment and remittance in one controlled channel | Customer and invoice identifiers still need mapping to AR |
| EDI or structured message | Supports repeatable line-level processing | Invalid codes, missing references, and version changes need exception handling |
How remittance advice is processed
- Capture the original advice. Retain the source message or file, received time, sender, attachment name, and document identifier.
- Extract header and line data. Capture payer, amount, currency, bank reference, invoice numbers, credits, deductions, and stated totals without overwriting the original.
- Validate the document total. Confirm that invoice allocations, credits, discounts, deductions, and residuals reconcile mathematically to the stated payment.
- Match to settled cash. Compare the advice with a verified bank or lockbox receipt using amount, currency, value date, payer evidence, and transaction reference.
- Map the customer and invoices. Translate payer identifiers and invoice references to valid customer master and open-item records.
- Apply clean lines and route exceptions. Post supported allocations while separating unknown invoices, duplicates, short pays, currency differences, and cross-entity items.
- Retain the evidence chain. Link the original advice, extracted data, bank receipt, AR posting, exceptions, and reviewer actions.
Worked remittance example
A payer sends an illustrative 31,500 and lists two invoices: 20,000 for Invoice 7001 and 12,000 for Invoice 7002. The advice also shows a 500 approved credit note applied against the second invoice. The allocation reconciles: 20,000 plus 12,000 less 500 equals the 31,500 bank receipt. The operator validates that both invoices and the credit note are open on the same customer account, then posts the application and retains the advice with the bank reference.
| Remittance line | Gross invoice | Credit | Cash applied |
|---|---|---|---|
| Invoice 7001 | 20,000 | 0 | 20,000 |
| Invoice 7002 | 12,000 | (500) | 11,500 |
| Total | 32,000 | (500) | 31,500 |
If the credit note does not exist in AR, the operator should not create or assume it solely because the payer listed a deduction. The 500 becomes an exception for commercial and finance review under the organization's policy.
Common remittance exceptions
| Exception | Risk | Investigation |
|---|---|---|
| No bank receipt | Advice may be premature, duplicated, or fraudulent | Wait for verified settlement; do not clear invoices from advice alone |
| Payment and advice totals differ | Cash may be over- or under-applied | Recalculate lines, credits, deductions, fees, and currency |
| Invoice number not found | Wrong entity, payer reference, closed invoice, or data-entry error | Search controlled cross-references and request clarification |
| Invoice already paid | Duplicate payment or duplicate advice | Review prior allocations and bank transactions before reallocating |
| Unapproved deduction | AR may be cleared without commercial authorization | Leave the residual open or record it under the approved dispute process |
| One payment for several entities | Cross-entity allocation can create ledger and intercompany breaks | Confirm beneficiary, legal entity, and approved settlement arrangement |
| Bank fee or net settlement | Gross invoices do not equal cash received | Identify contractual payer obligations and record fees under approved policy |
| Changed bank instructions in the message | Potential payment-diversion fraud | Do not update master data from remittance alone; follow independent verification controls |
Remittance advice versus proof of payment
Remittance advice explains intent. A bank receipt or controlled bank confirmation establishes that cash reached the account. A payment screenshot or forwarded transfer instruction may help an investigation, but it should not replace verified settlement evidence. Keeping these roles separate prevents invoices from being cleared before cash arrives.
Remittance advice and the AR aging report
Missing or unprocessed advice can leave paid invoices open in the AR aging report. The report then overstates the amount requiring collection even when the GL and bank show cash. A controlled process links remittance, allocation, and aging so collection teams can distinguish a true overdue balance from an application backlog.
Automating remittance processing without losing control
An automated workflow can monitor controlled inboxes or file channels, extract line items, test the arithmetic, locate the bank receipt, map payer aliases, and propose invoice matches. It should route low-confidence references, new customer relationships, unapproved deductions, cross-entity payments, and master-data changes for authorized review. The original document and extracted values should remain available so a reviewer can reconstruct every decision.
Aetherix connects remittance evidence to receipt allocation and close exceptions within managed reconciliation operations. For the wider control, see accounts-receivable reconciliation and the treatment of source billing data in billing reconciliation.
Frequently asked questions
Is remittance advice the same as a receipt?
No. Remittance advice explains which invoices a payer intends to settle. A receipt or verified bank transaction establishes that funds were received. Both may be needed to apply cash accurately.
Who sends remittance advice?
The payer or its payment service sends it to the supplier or recipient. In a group, a shared-service centre may send advice covering payments made for several operating entities.
What should finance do when remittance advice is missing?
Record the receipt transparently as unapplied cash, use controlled payer and invoice evidence to investigate, and request clarification when needed. Do not force a match based only on a similar amount.