Cash Application Process: How It Works, the Steps and How to Automate It

Cash application is the process of matching an incoming customer payment to the open invoices it was meant to pay, and posting it to the ledger. The cash application process runs in five steps: receive the payment, find the remittance advice, match the payment to invoices, post and close the invoices, then reconcile against the bank. Done well it is invisible. Done badly it quietly corrupts your aging report, your DSO and your collections.

It is also the least glamorous job in finance, which is why it is usually the last thing anyone fixes and the first thing that falls behind at month-end.

What is cash application?

When a customer pays, two separate things have to happen. The money moves into your bank account, and someone has to decide which invoices that money settles. Cash application is the second part. It answers the question "what did this $18,400 ACH actually pay for?" and then closes the matching invoices on your books.

If the answer were always obvious, the job would not exist. It is not obvious, because of a gap at the heart of B2B payments: the money and the instructions travel separately. The payment arrives through the banking system carrying almost no useful information. The explanation of what it pays, called remittance advice, arrives somewhere else entirely, or not at all.

Why is cash application difficult?

Because a payment rarely maps cleanly onto one invoice. The situations that eat an AR clerk's week look like this:

• One payment, many invoices. A customer pays $18,400 covering eleven invoices from three months. Nothing in the bank feed says which eleven.
• Short payments. They pay $9,660 against a $10,000 invoice. Is that a disputed line, an agreed discount, a credit note nobody logged, or a keying error? Each has a different resolution and a different owner.
• Decoupled remittance. The payment lands Tuesday; the remittance PDF is emailed to a shared inbox on Thursday by someone in the customer's AP team, if at all.
• Unhelpful references. The bank reference reads "PAYMENT" or a customer PO number that appears nowhere in your invoice numbering.
• Name mismatches. The paying entity is a subsidiary or a parent that does not match the name you invoiced.
• Checks. Still very much alive in US B2B, arriving with a paper stub that has to be read, keyed and matched by hand.

Each of these turns a two second match into a ten minute investigation, and there might be two hundred of them a week.

What are the steps in the cash application process?

Step 3 is where the time goes, and step 2 is what makes step 3 hard. A team that receives clean remittance with every payment can apply cash almost mechanically. A team chasing remittance around three inboxes cannot.

The exceptions are the job

Here is the thing that surprises people new to AR: the matched payments are not the work. Somewhere around 80 to 90 percent of payments from regular customers match without much trouble. The remaining slice, the short pays and the mystery deposits, consumes most of the hours. Any honest assessment of cash application, or of a tool that claims to automate it, has to be about how it handles exceptions, not how it handles the easy 85 percent.

What is remittance advice?

Remittance advice is the document or message from a customer that says how their payment should be applied: which invoice numbers, which amounts, and any deductions taken. The payment is the money; the remittance is the instruction. They are not the same thing and, in B2B, they very often do not travel together.

When remittance arrives detached from the payment, through a separate email, a supplier portal login, or a check stub, finance teams call it decoupled remittance, and it is the main driver of manual work in cash application. Keeping decoupled remittance below roughly 10 percent of your payment volume is a reasonable operational target, and the cheapest way to move toward it is unglamorous: ask for the invoice number in the payment reference, and put your remittance instructions on the invoice itself.

How do you automate cash application?

Automated cash application uses matching logic and AI to do what a clerk does, at machine speed: read the payment, pull remittance from wherever it landed, including a PDF attachment or the body of an email, identify the customer even when the paying entity name differs, propose the invoice matches, post the clean ones automatically, and route only the genuine exceptions to a human with the evidence attached.

The metric that matters is the straight-through processing rate, sometimes called the touchless rate: the share of payments posted end to end with no human involvement.

Treat vendor numbers with some skepticism, because the rate depends heavily on your customers' payment habits rather than the software alone. A book of business paying by check with handwritten stubs will not hit 95 percent no matter what you buy. If most of your customers pay by ACH with a reference, high rates are realistic.

One practical note for teams still doing this by hand: if you are keying deposits off a PDF bank statement each morning, getting that statement into a clean spreadsheet of transactions first turns an afternoon of retyping into a sort and a filter. It is not automation, but it removes the worst of the manual step while you evaluate something more permanent.

Why does slow cash application cost you money?

Because everything downstream of it is built on the assumption that it is current. When cash application falls behind:

• Your aging report lies. Invoices that are paid still show as open, so the report you make collections decisions from is wrong.
• You chase customers who already paid. Nothing damages a customer relationship faster than a dunning email for an invoice they settled two weeks ago.
• Your DSO reads high artificially. Unapplied cash keeps receivables inflated, so a metric your board watches is overstated by your own backlog.
• Credit decisions go wrong. A good customer looks over their limit because their payments are sitting unapplied, and you put a hold on a perfectly healthy account.
• Close drags. Reconciliation becomes an archaeology project instead of a check.

That first one is the quiet killer. A collections process running off a stale aging report will chase the wrong accounts with real conviction.

Should cash application sit with AR or the bank?

It belongs with AR, and specifically with whatever is doing your collections, because the two are the same loop. The system that chases an invoice needs to know the moment it is paid, and the system that applies cash needs to know which invoices are being chased. Split them across two tools, or two teams, and you get the classic failure: a reminder going out on Tuesday for money that landed on Monday.

That is the argument for handling both in one place. An automated cash application system that also runs the chasing closes the loop: it applies incoming payments to the right invoices as they land, stops chasing anything that just settled, and keeps the aging report accurate enough to actually trust. The follow-up in the wider AR process only works if the ledger underneath it is current, and cash application is what keeps it current.