Quick Summary

• Cash application is the work of matching an incoming payment to the invoices it settles, then posting it to your ledger. Collections get the money in. Cash application decides whether your books know about it
• The payment and the remittance advice travel separately, and that single fact causes most of the pain in this process
• Paper checks used to carry their own remittance stapled to them. Checks fell from 81% of US B2B payments in 2004 to 26% in 2025. The remittance data never followed the money onto the new rails
• A payment either matches cleanly on its own or becomes an exception a person has to work. The split between those two piles is the number that runs your whole function
• Unapplied cash is money you've been paid that your ledger still shows as owed, so your team chases customers who already paid you
• Deductions are a separate discipline from late payment, and treating a short payment like a late one is how teams lose the recovery window

Getting paid and knowing you've been paid are two different jobs.

What is cash application?

Cash application is the process of matching a customer's payment to the specific invoices it pays. You then post that payment to your general ledger, so the invoices close.

It's the step where money that has arrived in your bank account becomes money your accounting system understands. Until that happens, the cash is in your account but the receivable is still open, and everything downstream is working from a picture that isn't true.

It usually gets treated as an unglamorous back-office task, and it's the point that decides how accurate your whole receivables ledger is.

Cash application vs reconciliation vs payment posting

People use these three as though they mean the same thing, and they don't. Getting them straight makes the rest of this guide easier to follow.

In practice they run together, and plenty of teams use "reconciliation" as shorthand for all three. When someone says their reconciliation is a nightmare, they almost always mean the matching step.

One more term you'll want early. Remittance advice is the note from your customer telling you what a payment is for, which invoices it covers, and what they've deducted. You'll see it called remittance, remittance detail, or just "the backup." It matters more than anything else in this guide.

Where cash application sits in order-to-cash

Order-to-cash is the full run from a customer placing an order to the cash being usable. It runs through six stages:

• Quote and order, where you agree the terms and extend the credit
• Fulfillment, where the goods ship or the work gets delivered
• Invoicing, where the invoice is raised and sent
• Collections, where the invoice gets followed up until it's paid
• Cash application, where the payment is matched to the invoice it settles
• Reporting, which covers the aging report, DSO, and the rest of the numbers

Cash application is the last operational step before the numbers get read. Everything upstream can run beautifully and you can still report a receivables problem you don't have, because the payment landed and nobody matched it.

That's the part teams underestimate. The cash collection cycle is measured on whether money arrives. Cash application decides whether your books ever find out. Chapter 2 walks the whole sequence step by step.

Who does this work

In most companies cash application isn't one person's job title, it's a set of tasks spread across a few roles.

If you're a smaller company, one person does all of it between other duties. That usually means a Monday morning, a bank statement, and a spreadsheet.

Payments stall at the handoffs. One payment can need remittance chased, a deduction validated, and a write-off approved, so it touches three people. Each pass is a chance for it to sit.

Why cash application is harder than it sounds

On paper this is simple. Money comes in, you tick off the invoice. In practice a few structural problems get in the way, and none of them are your team's fault.

The payment and the remittance travel separately

This is the root cause of nearly everything else, so let's be precise about it.

Back when a customer paid you by check, the check and the remittance advice arrived in the same envelope. What the money was for came physically attached to the money.

Electronic payments broke that link. An ACH credit or a wire arrives through your bank, carrying a very limited reference field. The remittance detail gets emailed separately, or posted to a portal, or sent as an EDI file, or not sent at all. So you get the money on Tuesday and the explanation on Thursday, from a different system, in a different format.

Customers really have moved off paper. In 2004, 81% of US and Canadian B2B payments were made by paper check. By 2025 that was down to 26%, an all-time low, according to the Association for Financial Professionals' Digital Payments Survey. Payments went electronic and the paperwork stayed behind.

Nobody designed this. It's an accident of how payment systems evolved, and your team absorbs the cost of it every single day.

One payment rarely equals one invoice

The tidy case is when a customer pays one invoice for the exact amount with a clean reference. Plenty of payments look nothing like that.

A customer pays eleven invoices in one lump sum from their weekly payment run. Another pays part of an invoice because they're querying a line on it. A third pays the right total but nets off a credit note from four months ago, so the figure matches nothing you can find. A fourth pays through a parent entity whose name doesn't appear anywhere in your customer master.

Each of these needs a person to work out what happened, and each one takes a different kind of detective work.

Volume grows faster than the team does

Payment volume in the US has grown fast. Nacha reports that B2B payment volume climbed 155% between 2015 and 2024, from 2.9 billion payments to 7.4 billion. The value of those payments rose from $28.3 trillion to $58.2 trillion.

More payments means more of them are ambiguous, and that's the part that needs a human. So the work grows faster than the payment count does, and it grows fastest at exactly the point you're scaling.

Straight-through processing and the exception pile

Every payment that arrives goes into one of two piles, and once you understand the split between them, you understand this whole function.

The first pile matches on its own. The reference is clean, the amount is exact, the remittance parsed correctly, and the system closes the invoice without anyone looking at it. That's straight-through processing, usually shortened to STP.

The second pile is exceptions. Something didn't line up, so a person has to open it, work out what the customer meant, and apply it by hand.

The ratio between those two piles is the single most useful number in cash application. It sets your headcount, your close timeline, and how current your aging report is on any given day.

The exception pile is also where the cost sits. A payment that flows through straight costs you close to nothing. A payment that needs investigating costs you a person's time, plus an email to the customer and a few days waiting for the reply.

Lunos's own product materials put the split at roughly 60% of payments arriving clear and exact. The other 40% is partial payments, combined payments, missing references, and amounts that are close but not quite right. Treat that as the shape of the problem rather than a precise benchmark, since the mix varies a lot by industry and payment method. Chapter 5 covers how to measure your own split properly.

What actually breaks the match

When a payment lands in the exception pile, it's usually for one of a short list of reasons. Knowing them by name helps, because each one has a different fix.

• No remittance at all: The money arrived and nothing explains it. Most common on ACH payments from smaller customers
• Remittance in an unreadable form: A PDF, a scanned image, a screenshot of a spreadsheet, or a portal you have to log into
• A short payment: The customer paid less than the invoice on purpose. That's a deduction, and it needs its own handling
• A combined payment: One amount covering many invoices, with no breakdown of which ones
• A netted credit: The customer applied a credit note or a rebate before paying, so the figure matches no invoice you have
• A name mismatch: The paying entity, the subsidiary, or the bank account name doesn't match the customer record
• An overpayment or a duplicate: Now you're holding money that isn't owed, which is its own problem
• A currency or fee difference: Bank charges or an FX rate leave you a few dollars short of the invoice

None of these are the customer being difficult. Almost all of them are a data problem that started somewhere upstream, which is why Chapter 4 spends time on the setup rather than the matching.

Unapplied cash, and why it's worse than it looks

When a payment can't be matched, it doesn't disappear. It sits on the customer's account as unapplied cash, sometimes called cash on account or an unapplied receipt.

The money is in your bank. The invoice is still open. Your ledger now believes the customer owes you something they've already paid.

That gap does damage in four directions at once:

• Your aging report overstates what's owed, so your DSO looks worse than your performance was
• Your collections team chases a customer who has already paid, which is the fastest way to lose their trust in every message you send
• Your cash forecast works from a receivables figure that was never true
• Your close gets held up while somebody works through the pile

The last one is the reason controllers care. Until the unapplied balance is cleared, the books aren't clean, and until the books are clean you can't close.

Build one rule into your process so nobody has to remember it. Never send a dunning message on an account carrying unapplied cash until someone has checked it. A customer who gets chased for an invoice they paid three weeks ago remembers it for a long time. Our roundup of dunning management software covers the tools that run those reminder sequences, or see how Lunos handles collections so a dunning message never goes out on an unapplied account in the first place.

Deductions are a different problem

A customer who pays $9,200 against a $10,000 invoice hasn't paid late. They've decided $800 isn't owed and paid the rest. That's a deduction, also called a short pay.

This is a genuinely separate discipline from lateness, and the most common mistake is treating it like one. A dunning reminder is the wrong response to a deduction, because the customer doesn't think they owe you anything.

The categories you'll want to code separately:

• Pricing or quantity discrepancy, where the invoice doesn't match what was agreed or what arrived
• Trade or promotional deduction, an agreed allowance, rebate, or co-op marketing claim
• Shortage or damage claim, where goods went missing, arrived short, or arrived unusable
• Chargeback, a compliance or logistics penalty a large customer applies to you
• Unauthorized deduction, taken with nothing agreed behind it

Valid ones get approved and written off quickly, because arguing a legitimate $200 allowance costs more in goodwill than it recovers. Invalid ones get documented and collected back with evidence attached, which is exactly the workflow a dispute management agent is built to run.

Speed matters more than being right on any single item, because an unresolved deduction ages exactly like an invoice nobody has paid. It sits in your aging, inflates your DSO, and eats analyst time that should be going somewhere else. Chapter 2 covers the mechanics.

Why this matters to the business

Late payment already squeezes cash hard. Atradius found that 43% of the value of US B2B invoices was overdue in 2025, with a further 5% written off as bad debt. Average payment terms sat at 45 days.

Weak cash application makes that picture worse in a specific way. It adds a second delay after the customer has already paid you, and it's a delay entirely within your own control.

The gap between good and bad here is measurable. The Hackett Group's 2025 US Working Capital Survey found an 18-day spread in DSO between top-quartile and median performers, across the largest 1,000 nonfinancial public companies. It also valued receivables as the single largest component of excess working capital.

Some of that gap is collections. A good chunk of it is cash that arrived and then sat for days before anybody recognized it.

There's a cost to your team too. Working an exception queue is repetitive, and it's the kind of work that makes good analysts leave. Most of it is looking things up, cross-referencing, and emailing customers to ask what a payment was for.

Cash application is a matching system, not a typing job

The instinct is to treat this as data entry that needs to happen faster. Hire another analyst, work through the queue quicker, clear the backlog before close.

That approach hits a ceiling almost immediately, because the work doesn't scale with effort. It scales with how much good information reaches you at the moment the payment lands.

The teams that do this well spend their energy upstream. They make it easy for customers to send remittance in a readable form, and they give payers a reference the bank file will carry. They also set matching rules that absorb small differences without a human, so their people can spend time on the exceptions that need judgment.

The difference shows up in how a busy week feels. On a queue-clearing desk, a busy week means a backlog. On a well-built one, a busy week means a few more exceptions and the same close date.

See how Lunos solves this

Most tools in this space guess. They score a payment against your open invoices and apply it to the likeliest match, which is fine right up until the guess is wrong. The Lunos cash application agent auto-matches only where the signal is clear, then asks the payer directly about anything ambiguous. So a wrong match never quietly corrupts your ledger.

Contents

This guide runs across 6 chapters. Work through it in order, or jump to whichever part you need.

• Cash Application: A Complete Guide (this chapter)
• The Cash Application Process: Step by Step, the full sequence from bank file to posted journal entry
• Cash Application Best Practices, what the teams with clean ledgers do differently
• How to Build a Cash Application Workflow, designing the identifiers, rules, and queues yourself
• Cash Application KPIs, the metrics worth tracking and how each one misleads you
• Cash Application Automation: Manual vs Software vs AI Agents, how the three approaches compare

FAQs

Is cash application part of accounts receivable?

Yes. It's one of the later stages of the receivables cycle, sitting after collections and before reporting. Collections gets the customer to pay. Cash application matches that payment to the right invoices and posts it, so the invoice closes and your aging report reflects reality.

What's the difference between cash application and reconciliation?

Cash application matches individual payments to individual invoices. Reconciliation confirms that your ledger balance agrees with your bank statement at the account level. The two get used interchangeably in conversation, and when people complain about reconciliation they usually mean the matching work.

What is unapplied cash?

Unapplied cash is money you've received that hasn't been matched to an invoice yet. It sits on the customer's account rather than against a specific invoice, so your ledger still shows those invoices as open. It overstates your receivables, inflates your DSO, and leads to customers being chased for invoices they've already settled.

What is straight-through processing in cash application?

Straight-through processing is the share of payments that get matched and posted with no human involvement. The payment arrives, the system identifies the invoices, applies the cash, and closes them. Everything else becomes an exception someone has to work by hand, which is where nearly all the cost of this process sits.

Who is responsible for cash application?

Usually an AR analyst or a dedicated cash application specialist handles the daily matching, with a controller owning the unapplied balance and the close. In deduction-heavy industries a separate deductions analyst handles short payments. In smaller companies one person does all of it alongside other finance work.

Start with the pile you can't automate away

Cash application gets treated as a clerical problem and solved with more hands, which is why so many teams are still working a queue every Monday. It's an information problem. The fix is upstream, in what reaches you when the payment does.

Lunos is an AI coworker for accounts receivable. It matches what's clear, asks your customer about what isn't, and writes clean journal entries back to your ERP.

Start for free and see what your ledger looks like when the matching keeps up with the money.

‍