The cash application process looks simple on a flowchart: money comes in, an invoice closes. In practice, one payment can sit in limbo for days because the bank file says one thing and the customer’s email says another.
This post follows a single payment through all six steps and points to the exact moment it stalls. If your AR team keeps a growing pile of unapplied cash, the cause is almost always in one of these steps.
Quick Answer The cash application process is the six-step path a customer payment takes from bank deposit to closed invoice: receive the payment, find its remittance advice, match it to open invoices, post it in the ERP, resolve exceptions, and fix the cause. Most delays start at step two, when remittance advice is missing or late.
It starts when money lands: an ACH credit, a wire, a check deposit, or a card settlement. At that point the bank knows an amount and a payer name. It rarely knows which invoices the customer meant to pay.
We use one model for the whole path, and the rest of this post reuses its stage names.
The QServices Framework Payment Path = Receive → Remittance → Match → Post → Exceptions → Prevent
The order matters because every later stage depends on the one before it. A payment you cannot match cannot be posted cleanly, and an exception you never trace back will return next month.
The cash application process works by pairing each incoming payment with the open invoices it settles, then recording that pairing in the ledger. Receive, Remittance, Match and Post are the routine stages. Exceptions and Prevent handle everything the routine stages could not.
For US accounts receivable payment posting, the main inflows differ in how much detail they carry:
Because the people who pay and the people who send the explanation are often different. The payer’s AP system releases the funds, and a separate email, portal download, or PDF carries the detail.
When remittance advice arrives separately from payment, the cash sits in the bank with no instructions. It might show up the same day, two days later, or in a shared inbox no one on your AR team watches.
This is the stall point in our walk-through. The money is real, but nothing tells you what it pays.
Key Insight A payment with no remittance is not a mystery, it is a lookup. The detail exists somewhere, and the delay is the time spent finding it.
Collect every source into one place: the lockbox file, the AP portal exports, and the inbox. A simple intake flow, like the ones in these Power Automate workflow examples, can route attachments to a single queue. Then each payment has a remittance record waiting for it, or a clear flag that none exists.
Payment matching is the step that links an incoming amount to specific open invoices, using the remittance detail, the amount, and the payer’s identity. A match is clean when the totals agree to the cent and every invoice is identified.
Why payments fail to match invoices usually comes down to data, not effort. The customer pays three invoices with one amount, quotes an old PO number, or nets a credit memo you never see.
Real-World Scenario A typical case we see: an AR specialist at a US distributor gets a $48,200 ACH credit from a customer with 14 open invoices. The remittance email arrives two days later and lists 13 invoices. The total is $620 short because the customer deducted a freight claim. In the naive approach, the whole payment is held as unapplied cash until someone sorts it out. At the Match stage, rules would apply the 13 invoices and route only the $620 difference to Exceptions.
| Manual matching | Rules-assisted matching | |
|---|---|---|
| Speed on clean payments | Minutes each | Seconds, applied automatically |
| Handling odd remittance formats | Flexible, depends on the person | Needs a rule or a review step |
| Consistency across staff | Varies by person | Same logic every time |
| Setup effort | None | Rules need weeks of tuning on real data |
| Audit trail | Notes and spreadsheets | Logged match reason per line |
The honest downside is the setup row. Rules produce wrong matches until you tune them, so we start with a review step on every automated match.
How to post payments to the ERP depends on your system, but the principle is constant: post only what you have matched, and post it with enough detail that nobody has to reopen it. Our guide to D365 Finance and Operations key modules shows where customer payment journals sit in that ERP.
A good accounts receivable posting carries the customer, bank account, payment date, each invoice settled, and a reason code for any write-off or deduction. Skipping the reason code is how a $620 short pay becomes a mystery six months later. Cash posting without that detail passes the audit but fails the next collector.
For ERP cash posting for US finance teams, we recommend a daily cutoff tied to the bank file, so the aging report matches the bank balance each morning. Batch what you can, but never batch an unresolved payment into a clean batch. See also how payment processing automation cuts rework at this step.
Standards & References
- Federal Reserve ACH services: how US ACH payments are cleared and settled
- Microsoft Learn: customer payments in Dynamics 365: how customer payments are entered and settled
Some payments will not match no matter how good your rules are. This is where unapplied cash is born, and where discipline matters more than software.
Handling short pays and partial payments starts with a rule: apply what you can prove, and isolate the difference. Apply the paid invoices, leave the shortfall open, and tag it with a reason (freight claim, pricing dispute, early-pay discount). The collector then works one open item, not a frozen payment.
Clearing unapplied cash exceptions works best as a queue with an owner and an age limit, not a ledger balance everyone ignores. For the full backlog method, read our post on why unapplied cash piles up and how to clear it.
Key Insight Unapplied cash is a timing problem until it is a week old. After that it becomes a customer-service problem, because the customer’s account looks overdue when it is not.
The Prevent stage is the one most teams skip. They clear exceptions every month and never ask why they appeared.
In the engagements we see, the breaks fall into four places:
Our target is posting matched payments by the next business day, with exceptions assigned within the same day and cleared inside a week. Your numbers will differ with volume and remittance quality. Measure your own baseline first.
We start at Remittance, because that is where the process most often stalls, and we work on the ERP you already run. Our team does the work, so you do not add a system for your staff to learn. Our cash application services follow the same Payment Path every time:
Implementation Checklist
- Every payment source (ACH, wire, check, card) is listed with its remittance format
- Remittance emails and portal downloads land in one shared queue
- Matching rules are written down and tested on last quarter’s payments
- Every posting carries a reason code for deductions and write-offs
- Unapplied cash has a named owner and an age limit
- The aging report is reconciled to the bank file daily
The cash application process stalls at the same place for most AR teams: a payment lands on day one and the remittance advice turns up on day three. Every day between those two events, the cash sits unapplied and your aging report overstates what customers owe.
Three things fix it: one intake queue for remittance advice, written matching rules with a review step, and reason-coded posting with an owned exception queue. None of them requires replacing your ERP.
Pilot it on one customer segment for 30 days. Track four numbers: time from deposit to posting, percent of payments matched without touching, dollars sitting in unapplied cash, and exceptions older than seven days. A clear drop in the last two tells you the Payment Path is working.
Ready to see where your own payments stall? Book the AR Cash Assessment.
Written by Rohit Dabra
Co-Founder and CTO, QServices IT Solutions Pvt Ltd
Rohit Dabra is the Co-Founder and Chief Technology Officer at QServices, a software development company focused on building practical digital solutions for businesses. At QServices, Rohit works closely with startups and growing businesses to design and develop web platforms, mobile applications, and scalable cloud systems. He is particularly interested in automation and artificial intelligence, building systems that automate routine tasks for teams and organizations.
The cash application process steps are: receive the payment, find the remittance advice, match the payment to open invoices, post it to the ERP, resolve exceptions such as short pays and unapplied cash, and then fix the root cause so the exception does not repeat.
Payment matching in AR links an incoming payment to the specific open invoices it settles, using the remittance detail, the amount, and the payer’s identity. A clean match agrees to the cent and identifies every invoice paid.
Unapplied cash is money received from a customer that has not yet been assigned to an invoice. It usually happens because remittance advice is missing, late, or does not match your open items. It needs an owner and an age limit.
Start with the amount and the payer. Check whether the total equals one open invoice or a known combination, compare against the customer’s purchase orders, and contact the payer’s AP team if two matches are plausible. Never guess, and keep the payment in the exception queue until confirmed.
Payment matching decides which invoices a payment settles. Cash posting records that decision in the ERP ledger. Matching comes first, and posting should only happen on matched items with reason codes attached for any deductions.
As a working target, matched payments should be posted by the next business day and exceptions assigned the same day. Your own baseline will differ with volume, payment types and remittance quality, so measure time from deposit to posting first.
Cost and timeline depend on payment volume, the number of remittance formats, and your ERP. We scope it after an assessment. A pilot on one customer segment is usually the fastest way to see results before committing to wider changes.
List every payment source and its remittance format, route all remittance advice to one queue, and pull last quarter’s unapplied items to see which of the four break points caused them. The AR Cash Assessment walks through that review with you.
Dynamics GP end of life is closer than it feels. See the real Microsoft dates, your three options, and what each one means for AR and open invoices.
Follow one payment through the cash application process, step by step, and see the exact moment it stalls so your AR team can clear unapplied cash faster.
UAE e invoicing requirements for Phase 2 businesses under AED 50M: the dates, the ERP data to fix first, and how to pick an accredited provider.
Unapplied cash can sit in your bank account for weeks. Learn the five causes behind it and clear the backlog in a week, before month-end close.
Azure OpenAI security for production apps: identity, private networking, content filters, prompt injection defenses and monitoring to set before go-live.
Business intelligence consulting services should give a mid-market company a governed way to make decisions. Attractive dashboards are only the visible part. The useful outcome is a system in which source data, metric definitions, access, releases, ownership, and support still work after the consultants leave.
Dynamics GP end of life is closer than it feels. See the real Microsoft dates, your three options, and what each one means for AR and open invoices.
Follow one payment through the cash application process, step by step, and see the exact moment it stalls so your AR team can clear unapplied cash faster.
UAE e invoicing requirements for Phase 2 businesses under AED 50M: the dates, the ERP data to fix first, and how to pick an accredited provider.
Unapplied cash can sit in your bank account for weeks. Learn the five causes behind it and clear the backlog in a week, before month-end close.
Azure OpenAI security for production apps: identity, private networking, content filters, prompt injection defenses and monitoring to set before go-live.
Business intelligence consulting services should give a mid-market company a governed way to make decisions. Attractive dashboards are only the visible part. The useful outcome is a system in which source data, metric definitions, access, releases, ownership, and support still work after the consultants leave.
Earning Global Recognition: A Testament to Quality Work and Client Satisfaction. Our Business Thrives on Customer Partnership
Founder and CEO
Chief Sales Officer
Join our live webinar on Sept 24 and see five
ways to automate meetings, approvals, and
document search with tools already in your
tenant.
