What Is Cash Application and How Does It Work?

Cash application is the accounts receivable process that matches incoming customer payments to the specific open invoices they are meant to pay. Every check, ACH deposit, wire, and card payment a business receives has to be tied back to a customer account and the invoices it clears. When that matching is quick and accurate, customer balances stay correct, collectors chase the right people, and leadership sees a reliable picture of available cash. When it breaks down, the errors compound.

The function sits between the bank and the accounting system. The bank confirms that money arrived. The accounting system knows which customers owe what. Cash application connects the two. Without that connection, cash sits in the bank with no link to a customer or an invoice.

What Cash Application Is Responsible For

The core job is keeping customer balances accurate. When a payment posts correctly, the customer’s outstanding balance drops, the collections team knows not to chase that invoice, and the cash account reflects the deposit. Those balances feed the AR aging report, which management uses to gauge how quickly sales convert into actual cash.

One point worth clearing up: cash application does not trigger revenue recognition. Under accrual accounting, revenue is recorded when goods are delivered or services are completed, regardless of when payment arrives.1Library of Congress. Cash Versus Accrual Basis of Accounting: An Introduction Receiving payment converts a receivable already on the books into cash. Timely cash application still matters to the financial statements, but because it keeps balance sheet accounts accurate, not because it validates a sale.

How Payments Arrive

Payments come in through several channels, each with its own quirks:

  • Paper checks, still common in industries with older payment infrastructure. A check may arrive with a detachable remittance stub or with nothing at all.
  • ACH transfers routed through the Automated Clearing House network. Processing fees are low, but remittance detail sometimes arrives separately or not at all.
  • Wire transfers, faster than ACH and typically used for large-dollar or international payments. Wires cost more to receive, and remittance information is often limited to a short reference field.
  • Credit card payments, processed through a third-party processor that batches transactions and disburses funds after deducting fees. Matching individual invoices within a batch settlement adds complexity.

The payment is only half the picture. What makes or breaks the process is the remittance advice, the documentation that tells the AR team which invoices the customer intended to pay. Remittance data takes many forms: a printed stub stapled to a check, an email listing invoice numbers, or a structured electronic file. Large trading partners often transmit remittance data through EDI, specifically the 820 transaction set, which feeds invoice-level detail directly into the recipient’s accounting system and enables automated matching.

When remittance advice is missing or incomplete, the payment sits in limbo. The team sees the deposit in the bank but cannot post it to a specific invoice. That unmatched money is called unapplied cash, and resolving it usually requires contacting the customer or digging through purchase orders.

How Payments Get Matched and Posted

Once a payment and its remittance are paired, the application work itself begins. The goal is straightforward: reduce the customer’s open invoice balance and record the cash deposit. Several layers of processing sit behind that.

Lockbox Services

Companies that receive a high volume of checks often use a bank lockbox. Customers mail payments to a designated post office box controlled by the bank. The bank collects the checks, scans the remittance documents, captures payment information, and transmits electronic files to the company’s accounting system.2Investopedia. Lockbox Banking Explained This gets funds deposited faster and gives the AR team digital images to work from instead of paper.

Automated and Manual Matching

Modern ERP systems try to match payments to invoices automatically using predefined rules. The system looks for an exact dollar match, an invoice number in the remittance data, or a purchase order reference. When the data is clean and structured, especially with EDI remittance files, payments can process end-to-end without human involvement. That is called straight-through processing, and it is the benchmark for cash application efficiency.

Payments that fail automated matching get routed to a specialist. The specialist examines the available data, checks the customer’s open invoices, and determines the correct allocation. This is where experienced people earn their keep. Manual application often involves payments that bundle multiple invoices without clear detail, or amounts that don’t match any open invoice exactly.

The Journal Entry

When a payment posts, the accounting entry debits cash (increasing it) and credits accounts receivable (decreasing what the customer owes). The entry hits both the general ledger and the customer’s sub-ledger, keeping the two in sync.

Short Payments, Discounts, and Credits

This is where cash application gets genuinely difficult. Customers frequently pay less than the invoice amount, and the AR team has to figure out why before posting anything. Common causes include disputes over damaged or missing goods, pricing disagreements, unauthorized deductions for promotional allowances, early payment discounts the customer claims to have earned, and plain data-entry errors.

Early payment discounts create short payments by design. A term like “2/10 net 30” means the customer can deduct 2% if payment arrives within 10 days; otherwise the full amount is due in 30 days. When the customer takes the discount and pays 98%, the AR team needs to confirm the payment arrived inside the discount window and then write off the 2% difference to a discount expense account. If the payment was late, the team either pursues the remaining balance or escalates the unauthorized deduction.

Credit memos add another layer. If the company issued a credit memo for a return or billing error, the customer may pay the invoice net of that credit. The specialist applies both the payment and the credit memo against the original invoice to close it out. If the credit memo was never created in the system, the payment looks like a short pay until someone investigates.

Each scenario calls for a different accounting treatment. Lumping them into a generic short-pay bucket creates a mess that compounds over time. The best AR teams resolve deductions as they arrive rather than letting them age into a backlog nobody wants to touch.

Unapplied and Misapplied Payments

Even well-run departments deal with exceptions. Unapplied and misapplied cash sound similar but require completely different fixes.

Unapplied cash is money deposited but not yet matched to an invoice, usually because the remittance data is missing or unclear. These funds typically sit in a temporary holding account, often called a suspense account, until someone identifies the correct allocation.3Investopedia. Suspense Account: Definition, Uses, and Key Examples The longer unapplied cash sits, the harder it becomes to resolve. Customers stop remembering the details, and the AR team is effectively holding cash that isn’t reducing anyone’s balance.

Misapplied cash is worse in some ways. The payment posted, but to the wrong invoice or the wrong customer. This usually comes from a keying error or a bad assumption during manual matching. The effects show up immediately: the customer whose invoice was incorrectly cleared stops receiving collection notices even though they haven’t paid, while the customer whose payment was misapplied keeps getting dunning letters for an invoice they already covered. Fixing a misapplied payment requires a reversing entry to undo the original posting, followed by a new entry applying the funds correctly.

Both problems inflate the reported AR balance and distort financial metrics. Regular reconciliation of suspense accounts and periodic audits of applied payments are the only reliable ways to keep the issues under control.

Why Cash Application Affects the Numbers Management Watches

Speed and accuracy in cash application influence several metrics closely. The most prominent is Days Sales Outstanding (DSO), calculated by dividing total accounts receivable by total credit sales for a period and multiplying by the number of days in that period. DSO shows how many days, on average, it takes to collect payment after a sale. Slow or inaccurate cash application artificially inflates DSO because invoices that have actually been paid remain open in the system.

The AR aging report is equally exposed. It groups outstanding invoices by how long they have been open: current, 30 days, 60 days, 90+ days. When payments sit unapplied or land on the wrong account, invoices that should have cleared weeks ago appear in older buckets. That skews the aging profile, triggers unnecessary collection activity, wastes staff time, and can damage customer relationships.

Cash flow forecasting depends on clean AR data too. If the finance team projects future inflows from an aging report full of ghost receivables (invoices actually paid but not yet applied), the forecast overstates expected collections. For companies managing tight liquidity, that kind of error leads to bad borrowing decisions or missed payment obligations.

Controls That Keep the Function Honest

Because cash application handles incoming funds and modifies customer balances, it is a natural target for internal controls. The most fundamental is segregation of duties: no single person should receive cash, record the payment, and reconcile the bank account. Splitting those responsibilities means one employee’s work checks another’s, making it much harder to divert funds and cover the trail.

In practice, the person opening the mail or receiving lockbox files should not be the person posting payments in the ERP system. The person applying cash should not have unchecked authority to issue refunds, write off balances, or adjust accounts without supervisory approval. When a company is too small to fully separate every role, compensating controls like mandatory supervisory review of postings and regular bank reconciliations become essential.

Monthly bank reconciliation acts as the final safety net. Comparing the bank statement to the cash account in the general ledger catches deposits that were never recorded, payments recorded twice, and discrepancies between what the bank received and what the accounting system shows. Bank reconciliation and cash application are related but distinct: cash application matches payments to invoices, while bank reconciliation matches total cash records to the bank’s records.

Where Automation Fits Now

The traditional pain point has always been unstructured remittance data: a scanned check stub with handwriting on it, a PDF attached to an email, or a payment with nothing but a dollar amount and a customer name. Manual processing of these items is slow, expensive, and error-prone.

AI-powered optical character recognition has shifted that equation. Unlike earlier OCR tools that struggled with formatting variations and poor scan quality, newer systems use machine learning to recognize text patterns across different document layouts. They extract invoice numbers, payment amounts, and customer identifiers from scanned remittances and feed that structured data directly into the matching engine. Natural language processing handles the messiest formats, pulling relevant details from free-text emails that would otherwise require a human to read and interpret.

The combination of structured EDI data from larger customers and AI-driven extraction from smaller ones has pushed automated matching rates well above what was possible a decade ago. For AR departments, the practical result is fewer manual touches per payment, faster clearing of open invoices, and more staff time available for the genuinely complex exceptions that still need human judgment, such as disputed deductions or payments that span dozens of invoices across multiple business units.