Executive summary

The accounts receivable aging report is one of the most-trusted numbers in finance. It sets collections priorities, informs working-capital decisions, and shapes what gets reported to the board. It is also routinely wrong. A meaningful share of what shows as "overdue" has already been paid. It just hasn't been matched to an invoice yet.

That gap, between cash that has been paid and cash that has been applied, is the cash application problem. IDC ranks it as the single hardest part of accounts receivable, ahead of collections, credit, and disputes. HighRadius, the category leader, puts the cost of doing it by hand at $7.82 per payment and roughly a quarter of a finance team's capacity. And it lands hardest at period end, when the numbers most need to be right.

This piece is about that problem. What it is, what it costs, and why a generation of software still hasn't solved it.

The numbers that frame it:

• Cash application (matching, posting, remittance) is the #1 most challenging aspect of AR (IDC).

• As many as 4 in 5 businesses that fail can point to cash flow as the cause (IDC).

• $7.82 to process a single remittance by hand (HighRadius).

• ~25% of a finance team's capacity goes to manual cash application (HighRadius).

• ~Half of North American B2B invoices are currently overdue (Atradius / Quadient, 2025).

• +59% year-on-year growth in businesses planning to adopt SaaS for AR (IDC SaaSPath).

The number the board trusts is the number that's wrong

A controller I spoke to last month described her month-end like this. The aging report says customers owe €4.2m past due. She knows a chunk of that is already sitting in the bank. The money arrived. Nobody has matched it to an invoice yet. So every month she walks into the board meeting holding a number she knows is wrong, and spends the first ten minutes explaining which part of "overdue" isn't.

She is not bad at her job. She is good at it, which is why she knows the number is off. The problem is structural, and most finance teams have a version of it. The aging report gets treated as ground truth. It decides who gets chased, how much credit gets extended, how working capital gets planned, and what number leadership sees. And part of it is fiction.

That part has a name: unapplied cash. It is the least glamorous line in finance and one of the most expensive.

What cash application actually is

Cash application is the work of taking a payment that has landed in your bank and answering three questions. Who sent it. Which invoices does it clear. How do you post it. When it works, nobody notices. When it doesn't, the payment sits as unidentified or unapplied cash: money you have that your system can't yet assign.

There are three layers to it, and a payment can break at any of them. First is identification. Which customer does this wire, ACH, or check belong to, when the name on the payment doesn't match the name on the account? Second is application. Which open invoices does it clear, when the amount doesn't tie out, the remittance came in a separate email, or one payment from a distributor covers a dozen end customers? Third is reconciliation. Making the posted payment agree with the bank and the ledger so it lands cleanly in the close.

Each layer is a judgment call. Judgment calls are exactly what software has historically pushed back to a person.

Why it's the hardest part of AR

This is not one company's bad week. When IDC surveyed enterprise finance teams on the most challenging aspect of accounts receivable, cash management came out on top, ahead of collections, credit management, and disputes. It is the hardest part of the function according to the people who run it.

And what it governs is not optional. IDC's own framing is blunt: as many as four in five businesses that go under can point to cash flow, running out of money, as the main reason. Cash application is the plumbing that decides how quickly money you have already earned becomes money you can use. Get it wrong and you have a liquidity problem, not a clerical one.

The cost shows up even in the leaders' own marketing. HighRadius, a three-time Gartner Magic Quadrant leader in this space, puts the price of processing a single remittance by hand at $7.82, and manual cash application at roughly a quarter of a finance team's capacity. Multiply that by every payment, every day, across a whole team. Then set it against the backdrop. Across North America, nearly half of all B2B invoices are currently overdue, and the average business waits more than 40 days to get paid. A real share of that "overdue" was never overdue. It was paid. It just wasn't applied.

The costs that never reach a line item

The obvious cost is labor. The expensive costs are the ones that don't show up as a number anywhere.

Working capital gets understated. Cash sitting unapplied in a suspense account is real money you can't deploy and can't see clearly. It inflates your receivables, depresses your reported liquidity, and pushes teams toward larger credit facilities than they actually need.

The close gets distorted. This is the part that is easy to miss. Cash application is not really a matching task, it is a close task. Unapplied cash corrupts the aging and the working-capital picture at the exact moment those numbers have to be right and signed off. A backlog that is a nuisance on the 12th of the month is a reporting problem on the 30th.

The problem scales with you. Every new customer adds another payment format, another remittance quirk, another portal, another way for money to arrive without a clean reference. Grow the business and you grow the pile of unmatched cash with it.

It pulls your best people off real work. Identifying and applying payments by hand falls to capable people who could be doing analysis. Instead they spend the back half of every month matching payments.

It strains customer relationships. When a paid invoice still shows open, the customer gets a reminder for money they already sent. It is a small thing, it lands on your best-paying customers, and it is avoidable.

Why a generation of software didn't fix it

None of this is new, and it is not for lack of spending. Companies have spent billions on AR software. So why does the controller still walk into the board meeting with a number she knows is wrong?

Because most of that software solved the wrong half of the problem. It promised to fix cash application and mostly delivered better dashboards, which is to say faster ways to do the same manual work. The hard part was never the screen. It was the matching: the judgment, the exceptions, the messy reality of how money arrives.

So the same patterns persist. Systems assume the data is clean and route anything unusual to a human queue. Matching tolerances are so blunt, a flat "anything within $X," that teams switch them off and turn every small mismatch back into a manual exception. Integrations default to batch instead of real time, so the data is stale before anyone touches it. One team I spoke to only found out their bank feed had broken during a banking migration when payments stopped showing up.

An O2C advisor we work with, who has implemented these platforms inside large finance teams, put it plainly: "Workflow automation is a finished category. Finance teams will pay for outcomes, DSO down and cash applied faster. They won't pay for another screen to organise the work."

His sharper point is about what's missing. "The biggest unmet need here isn't another collections worklist. It's a system a finance team can defend, to its auditors and to its CFO."

What solved would actually look like

The bar is simple to state. Cash application is solved when a payment lands and gets identified, applied, and reconciled without a person stepping in. For the cases that do need a human, the system hands them the context instead of a five-letter exception code. Matching runs in real time, not overnight. The system can explain why it applied a payment a given way, clearly enough to satisfy an auditor. And the result lands in the close, rather than in a separate tool someone has to reconcile back later.

Most of all, cash application is solved when it is treated as part of the close, not as an island. The aging report and the close are the same story from two ends. Fix one and ignore the other, and you haven't fixed the problem the controller actually has.

That is the problem we have been sitting with. We have spent two years getting good at the close, and the cash that lands on the other side of it is the natural next thing to get right.

Go deeper on this

On June 30, our CEO Albert is hosting a live masterclass with Christian Martinez, who has trained more than 20,000 finance leaders on applying AI to finance. The session covers exactly this problem: why unapplied cash distorts your aging and your working capital, the three layers of the matching problem, and how to read DSO, past-dues, and write-offs as one connected story instead of three separate numbers. Sixty minutes, free.

Save a seat here

If your aging report and your bank account disagree every month-end, that hour is for you.