What does remittance mean in accounting?
In accounting, a remittance is a payment a payer sends to settle an obligation, most often a customer paying a supplier’s invoice. To remit is the verb: the customer remits $12,000 when it sends that amount to the supplier. “Remitted” describes funds that have left the payer, and the remitter, or remitting party, is the one who sends them. The supplier receiving the funds is the payee.
Businesses also remit money they collected on behalf of someone else. A company remits sales tax to the tax authority, payroll withholdings to the government and, in marketplaces, seller proceeds to each seller. Checking that each of those outgoing transfers matches what was owed is the job of payout reconciliation. The filing calendar and the form for tax remittances depend on each jurisdiction.
Outside accounting, remittances also name the transfers that workers abroad send to family at home, and a person’s remit is the scope of their responsibility. This entry covers the business payment.
Is remitted the same as paid?
Not quite. Remitted means the payer sent the funds; paid, from the payee’s side, means the funds arrived and the open invoice was settled. In between, the transfer can be in transit, be returned or arrive short, so a remittance on the payer’s records does not prove the supplier’s invoice is closed.
A remittance receipt, sometimes called proof of remittance, is the confirmation a bank or payment service gives the payer after it processes the transfer, with the amount, date, beneficiary and a reference. It proves that the payer sent the money. The payee confirms receipt with its own bank record, and only then does the receivables team apply the amount to invoices.
What is remittance information?
Remittance information is the data that tells the payee what a payment is for: payer, amount, currency, date, invoice references and other available identifiers. A payment can reach a bank account without enough of that detail to identify the customer or obligation, which is why the remittance information often matters as much as the funds.
The information can travel inside the payment or separately. Bank payment formats reserve space for it: in ACH, a CCD+ entry carries a short addenda record and a CTX entry can carry a full EDI 820 remittance, while ISO 20022 payment messages include a remittance information field that can be structured or free text. When the details arrive in an email, a PDF or a portal instead, the separate document is a remittance advice.
Useful remittance data preserves the relationship between the payment and the documents it is intended to cover. Invoice numbers, document dates and the amount attributed to each item are more informative than a free-text message such as “account payment.” Where those fields are available, retaining them allows finance to investigate the intended purpose without reconstructing it from the total alone.
Identification and confirmation answer different questions. A recognizable invoice reference can explain the payer’s intention even while the transfer remains unconfirmed. Conversely, confirmed funds may still lack enough information to identify an obligation. Keeping those conditions separate prevents a complete-looking advice from being treated as evidence of cash receipt, or an unidentified receipt from being assigned to an invoice without support.
How does a remittance work?
- Create the payment instruction. The payer instructs a bank or payment service to send funds and includes the available beneficiary and obligation details.
- Confirm the funds movement. Bank or payment records show the amount and status actually processed. That confirmation is distinct from a payer’s notice or advice.
- Connect payment information. Finance compares payer, reference, invoice, date, currency, and amount fields to understand which obligation the payment is intended to cover.
- Review differences and hand off. Missing references, unexpected amounts, or conflicting records remain exceptions for investigation. Supported information can then feed the separate cash application process.
Remittance example
A customer sends instructions for a $48,000 remittance intended to cover invoice INV-610 for $30,000 and invoice INV-624 for $18,000. The advice lists both references, but the bank confirmation shows only $47,650 received. The difference is $350: $48,000 – $47,650 = $350. The remittance review flags that shortfall as unresolved. It does not assume the $350 is a bank fee, discount, write-off, or approved deduction. Cash application later determines the supported invoice allocation after the difference is investigated.
| Record | Source | Amount | What it establishes |
|---|---|---|---|
| Remittance advice | Customer | $48,000 ($30,000 + $18,000) | The payer’s intended split across INV-610 and INV-624 |
| Bank confirmation | Payee’s bank | $47,650 | The funds actually received |
| Unresolved difference | Remittance review | $350 | An open item to investigate, not an approved deduction |
For this payment, the useful investigation package includes the original advice, the two invoice references, and the bank record for the amount received. Finance can then seek evidence explaining the $350 shortfall. The intended $30,000 and $18,000 split remains information from the payer; it does not establish how the smaller receipt should be allocated. Until that question is resolved, the records should distinguish the confirmed total from the proposed invoice treatment.
The same distinction protects the history if further information arrives. A corrected advice may improve identification, but it is not a second receipt. Retaining the relationship to the original payment helps the reviewer interpret the update without counting the funds twice.
Remittance vs. remittance advice, receipt and cash application
| Record | Who produces it | What it shows | What it does not prove |
|---|---|---|---|
| Remittance | Payer | Funds sent to satisfy an obligation | That the payee received the full amount |
| Remittance advice | Payer | What the payer says the payment covers | That the funds moved |
| Remittance receipt or bank confirmation | Bank or payment service | The amount and status actually processed | Which invoices the payment settles |
| Cash application | Payee’s receivables team | How supported received amounts are assigned to open items | That an unexplained difference is approved |
Why remittances fail to match invoices
Most remittance exceptions come from a gap between the payment and the information that explains it:
- Missing or truncated references. The payment field holds a customer name or a partial invoice number, so the funds arrive without a clear obligation and can end up as an unapplied payment.
- One payment for many invoices. A single remittance covers several invoices, credit memos or deductions, and the split exists only in the advice.
- Less money than expected. Intermediary bank charges, customer deductions or disputed lines leave a short payment that needs a reason before anyone writes it off.
- Timing. The advice and the funds arrive on different days, sometimes in different periods.
How Simetrik supports remittance control
Simetrik is an AI-native financial control platform. In a remittance control workflow, Simetrik can compare available payment and invoice fields under configured deterministic rules, surface unmatched records or differences for review, and preserve traceability around configured controls and actions. Finance teams define the data sources, identifiers, rules, and final treatment.
In practice, Simetrik ingests bank statements, payment processor files and receivables data, and its configurable matching rules can run one-to-one or one-to-many sequences, so one $48,000 remittance can be compared against two open invoices. The $350 gap in the example would stay visible as an exception instead of being absorbed into an invoice. These controls over incoming payments hand cash application a confirmed amount and a documented difference.
Before configuring a comparison in Simetrik, the team should establish which fields refer to the same business event across sources, as part of preparing data for reconciliation, because a bank reference and an invoice number may identify different objects. A rule that finds a correspondence supports a control result within that configuration; the supporting records and any unresolved amount still matter when deciding the next action. The guide to modern payments reconciliation covers that groundwork in more detail.