Glossary

Cash application

Cash application is the accounts receivable process of assigning a customer payment that has already been received to the open invoice or invoices it is intended to settle. The process establishes how much of each receivable has been paid and identifies any amount that still requires review.

Why cash application matters in accounts receivable

Receiving money changes the company’s cash position, but the receipt alone may not show which customer or invoice it belongs to. Cash application connects the payment record with receivable records so finance teams can update allocations using supportable evidence and keep unresolved amounts visible.

Until a receipt is applied, the invoices it paid still look open in the aging report even though the money is already in the bank. Collections may contact a customer who has paid, credit limits can stay blocked, and the open-item detail by customer no longer shows what each customer actually owes.

Where cash application fits in order-to-cash

Cash application is the order-to-cash (O2C) step that follows collection. After an order is fulfilled, invoiced and paid, cash application matches the payment to the invoices it settles. Its result feeds collections follow-up, credit decisions and the period-end accounts receivable reconciliation.

In most companies, the work belongs to a cash application analyst or specialist on the accounts receivable team, who coordinates with collections and, when needed, with the customer.

How does cash application work?

  1. Capture the receipt and available remittance. Record the amount, date, currency, bank reference, and any remittance advice. Keep evidence that money was received separate from evidence of which invoice the customer intended to pay.
  2. Identify the customer and candidate invoices. Use customer identifiers, invoice references, and open balances to find possible receivables. The payment amount by itself may not identify a unique match.
  3. Allocate supported amounts. Apply the payment according to the available evidence and the team’s policy. One receipt may cover several invoices, and a partial payment may leave an open receivable balance.
  4. Review exceptions and document the result. Leave unidentified or unsupported amounts unapplied and route them for investigation. Record the final allocation and any remaining receivable or unapplied payment balance.

Cash application example with a partial payment

Northstar Medical has two open USD invoices: AR-8041 for $7,800 and AR-8067 for $5,100, for a total receivable of $12,900. The company receives $12,300, and the remittance instructions identify both invoices. The team applies $7,800 to close AR-8041 and $4,500 to AR-8067. The applied amount is $12,300, the unapplied payment balance is $0, and AR-8067 retains a $600 receivable. This illustrative example assumes one customer, one currency, and no discount, fee, write-off, or dispute.

InvoiceOpen balanceAmount appliedBalance after application
AR-8041$7,800$7,800$0
AR-8067$5,100$4,500$600
Total$12,900$12,300$600

The $600 on AR-8067 stays open until the team learns why it was not paid. It becomes a short payment, a disputed charge or an approved deduction only after that review. If the remittance had not named any invoice, the full $12,300 would have stayed unapplied until other evidence supported an allocation.

What makes a cash application match supportable?

A supportable match usually combines several fields: payment amount and currency, receipt date, payer or customer identifier, bank reference, invoice number, open balance, and remittance details. The useful combination depends on the records and controls available in the workflow.

A matching amount is useful evidence, but it may still be ambiguous. Two customers can owe the same amount, one payment can cover several invoices, and a payer name can differ from the customer account name. When the evidence does not support one allocation, the amount should remain available for review under the team’s policy.

Common cash application exceptions

Most cash application exceptions come from a gap between what the customer paid and what the remittance or the open invoices explain. Each type calls for a different treatment, so the team identifies the cause before it closes an invoice or chooses an account.

  • Missing or incomplete remittance. The payment arrives without a remittance advice, or the advice lists invoices whose total differs from the amount received.
  • Payment below the invoices named. The customer pays less than the invoices it lists. The difference stays open as a possible short payment until a dispute, deduction or error is confirmed.
  • Payment above the open balance. The excess is an overpayment and stays as a customer credit until the team applies, refunds or otherwise resolves it under policy.
  • Unidentified payer. The payer name or bank account does not match the customer master, for example when a parent company pays for a subsidiary. The receipt remains an unapplied payment until the payer is confirmed.
  • Fees and deductions. A bank or processor fee reduces the amount that arrives. A documented fee is recorded separately; a deduction the customer only claims is investigated.

Cash application KPIs

Teams usually measure cash application with four operational indicators: the share of receipts applied without manual review, the unapplied cash balance and its age, the number of open exceptions, and the time from receipt to application. Targets depend on payment channels, customer mix and remittance quality, so no single benchmark applies to every company.

Cash application vs. cash posting and bank reconciliation

Cash application establishes which receivables a payment settles. Cash posting records the payment and its approved application in the accounting system. Teams may perform these activities together, but the supporting match and the accounting record should remain traceable to the same receipt and invoices.

ProcessQuestion it answersMain recordsResult
Cash applicationWhich invoices does this payment settle?Receipt, remittance, open invoicesAllocation by invoice and any open or unapplied balance
Cash postingHow is the receipt recorded in the ledger?Receipt, approved allocation, chart of accountsJournal entry for cash, receivables and supported deductions
Bank reconciliationDo the books agree with the bank?Bank statement, cash account in the ledgerExplained differences between bank and book balances

How Simetrik supports cash application

Simetrik is an AI-native financial control platform. In a cash application workflow, Simetrik’s reconciliation engine can run configured, deterministic matching logic across payment, remittance, customer, and invoice records, including one-to-many sequences that compare one receipt with several open invoices. Records that do not meet the rules surface as unmatched records or exceptions for review. These controls over incoming payments and receipts rely on configurable matching rules and tolerances that the team defines.

Simetrik’s AI works around that deterministic core. It can suggest a parser for nonstandard bank or remittance files and map equivalent columns between sources during data preparation, and it proposes matching rules for the team to review. Unmatched receipts stay in a central pending queue with individual or bulk actions, and traceability around configured controls and actions helps the team review how each allocation was supported. The allocation policy, the treatment of deductions and any write-off remain decisions of the finance team.

Frequently asked questions

Can one payment be applied to multiple invoices?

Yes. One customer payment can settle several open invoices when the available evidence supports that allocation. The portion covered by the receipt cannot exceed the amount received; approved discounts or other adjustments are recorded separately. Remaining invoice or payment balances should stay visible.

What happens when remittance advice is missing?

The team can investigate other evidence, such as the payer identifier, bank reference, invoice references, currency, amount, and open balances. If those records do not support a unique allocation, the receipt should remain unapplied until the exception is resolved under the team’s policy.

Can cash application close an invoice when a balance remains?

A partial payment normally leaves the unpaid portion as an open receivable unless a separate, authorized adjustment changes that result. Cash application should not assume that the residual is a discount, fee, write-off, or approved deduction.

What is the journal entry for cash application?

Cash application decides the allocation, and the related entry is recorded through cash posting. When the receipt and its allocation are recorded together, the entry debits cash and credits accounts receivable for each invoice settled. When money arrives before the allocation is known, many teams first credit an unapplied cash account and later move the amount to the specific invoices.

How would you explain the cash application process in simple terms?

Cash application is matching each customer payment to the invoices it pays. It follows four moves: capture the receipt and its remittance, identify the customer and candidate invoices, apply the supported amounts, and document any exception. A short example, such as one payment covering two invoices and leaving a balance on one of them, shows the reasoning better than a definition.

What does a cash application specialist review?

A cash application specialist reviews payment and remittance records, customer identifiers, candidate invoices, allocation amounts, and unresolved exceptions. The role may also document why a payment was applied, left unapplied, or sent for further investigation according to company policy.

Can AI automate cash application?

Yes, AI can take on preparation and suggestion work, but the allocation itself should run on rules the team can audit. In Simetrik, AI can suggest a parser for nonstandard remittance files and propose matching rules based on historical patterns. The team reviews those suggestions, the deterministic engine applies the approved rules to fields that can be compared consistently, such as invoice number, amount, currency and customer reference, and receipts that do not match stay visible as exceptions.

Ready to transform your reconciliation workflows?

This site is registered on wpml.org as a development site. Switch to a production site key to remove this banner.