Cash Application Process: Matching Customer Payments to Invoices
A practical cash application process for distributors: capture remittance from ACH, wire, card and check, match lump-sum payments and clear unapplied cash.
Photo: Pixabay
On this page 7 sections
- The Five Steps of the Cash Application Process
- Why Distributors End up With Unapplied Cash
- Where Remittance Data Lives for ACH, Wire, Card and Check
- Worked Example: One ACH, 31 Invoices, Three Exceptions
- Apply the Gross Card Amount, Not the Deposit
- Automate the Accounts That Send the Most Payments
- A Month-End Routine for Unapplied Cash and Credit Balances
Key takeaways
- Post a lump-sum payment to the customer's account the day it arrives, even before you match it to invoices, so paid accounts don't land in collections.
- Close a short-paid invoice in full and move the difference to a coded deduction item. Don't leave unexplained balances on the original invoice.
- Apply the full card amount to every invoice whether your processor funds net or gross, and book fees to expense.
- A CCD+ ACH has room for about 80 characters of remittance, while a CTX can itemize a long invoice list. Ask your bank whether you can see either one.
The cash application process is how accounts receivable matches each incoming payment to the invoices it pays and then posts it, so the aging report shows what every customer still owes. It has five steps: identify the payment, tie it to the right customer, find the remittance, apply the cash and work the exceptions. Distributors lose nearly all their time in the third step, because the money and the explanation of the money rarely arrive together.
When remittance never shows up, the payment sits as unapplied cash and paid invoices keep aging. A customer who paid on time gets a collection call or, worse, a credit hold on next week's order.
The Five Steps of the Cash Application Process
The sequence is the same in a spreadsheet or in AR software:
- Identify the payment. Record amount, date, method and payer from the bank deposit or processor report.
- Identify the customer. Tie the payer to the right account. A parent company paying for eight locations makes this harder than it sounds.
- Gather the remittance. Find the detail that says which invoices the payment covers and what was deducted.
- Match and apply. Apply cash to specific invoices, and record short-pays, credits and discounts as their own items.
- Resolve exceptions. Research what doesn't match, then post it or park it with a written reason.
Once step three is done, the rest is mechanical. The payoff comes from clean remittance and from handling lump-sum payments and card deposits correctly.
Why Distributors End up With Unapplied Cash
Wholesale buyers pay the way their AP department is built, and that rarely lines up with how you invoice. Their AP team pays against its own purchase order number, and one PO might have shipped as four partial invoices. A restaurant group or grocery chain pays centrally for stores you bill as separate accounts. Retail and grocery customers deduct for shortages, damage, promotional allowances and pricing disputes, then pay the net with little explanation.
The remittance travels separately. The deposit hits on Tuesday, and the spreadsheet explaining it arrives Thursday through a supplier portal or in the format of the buyer's AP automation tool. Route drivers bring back checks and card receipts with no invoice reference at all. All of this is normal for B2B receivables, so it calls for a standing process rather than a one-time cleanup.
Where Remittance Data Lives for ACH, Wire, Card and Check
Each payment rail carries remittance differently, and each has a predictable gap.
| Payment Type | Where Remittance Lives | Common Gap |
|---|---|---|
| ACH | Addenda record, or a separate email | Addenda blank, or vendor ID only |
| Wire | Remittance field, or a separate email | Payer name you don't recognize |
| Card | Gateway invoice/PO field, or payment portal | Field left blank when keyed |
| Check | Stub, memo line, enclosed letter | Stub missing or doesn't match the amount |
ACH: Ask for CCD+ or CTX, Then Check What Your Bank Shows You
Under the Nacha Operating Rules, a corporate ACH payment in the CCD format can carry one addenda record with an 80-character payment-related information field. Bankers call that version CCD+, and it has room for a few invoice numbers. The CTX format allows up to 9,999 addenda records and is designed to carry structured remittance in the ANSI X12 820 format. That's enough to itemize a long list of invoices in a single payment, as Nacha's user guide for electronic payments lays out.
There's a catch on both ends. Plenty of AP systems send a plain CCD with no addenda, and not every bank displays addenda by default. Ask your bank's treasury team whether addenda appear in your transaction detail and bank file. Then ask your largest payers to put invoice numbers in the addenda, and print a line on invoices and statements asking for the same. For the broader trade-offs of the rail, see our look at ACH payments for small business and their slower settlement.
Wires: Build a Payer-Alias List
The Federal Reserve moved the Fedwire Funds Service to the ISO 20022 message format on July 14, 2025. With the change, the free-text field banks used to call "Additional Information" is now labeled "Remittance Information". That only helps if the sending bank fills it in and your bank shows it to you, so keep chasing wire remittance by email until your customers' AP teams change their habits.
The bigger wire problem is the payer name. A wire from a parent company, a holding entity or an overseas affiliate shows a name nobody in AR recognizes. Keep a payer-alias list on each customer record. Once someone ties "ABC Holdings LLC" to the Main Street Grocers account, the next wire from that entity matches on its own.
Cards: Capture the Invoice Number at the Moment of Payment
Card payments are the easiest to match because the remittance is created at checkout. Make the invoice or PO field required in your gateway and in the virtual terminal your team uses for phone orders. A B2B customer payment portal where buyers pay invoices online goes further, because the buyer picks the invoices being paid and the remittance comes attached to the money.
AP virtual cards are the exception. The card number arrives from a payment provider, and the invoice detail comes in a separate email. Treat those like a wire, and hold the payment as identified but unapplied until the email is matched.
Checks: Scan Everything in the Envelope
Stubs go missing, don't match the check, or show only a PO. Scan the check, stub and any letter together, and attach the images to the payment record.
Worked Example: One ACH, 31 Invoices, Three Exceptions
Assumptions (illustrative, not customer data): a grocery chain has 31 open invoices with you totaling $51,720.00. It sends one CTX payment for $48,250.00, and the remittance spreadsheet arrives the next day.
| Remittance Line | Invoice Amount | Paid | Left Open |
|---|---|---|---|
| 29 invoices paid in full | $47,620.00 | $47,620.00 | $0.00 |
| Invoice A, short-paid for a shortage claim | $2,140.00 | $1,830.00 | $310.00 |
| Invoice B, not listed | $1,960.00 | $0.00 | $1,960.00 |
| Promotional deduction, no invoice reference | None | −$1,200.00 | $1,200.00 |
| Total | $51,720.00 | $48,250.00 | $3,470.00 |
Post the $48,250 to the customer's account the day it lands, as unapplied but identified, so their balance drops and collections stays quiet. Import the remittance file instead of retyping 31 lines, then apply the 29 exact matches.
The common mistake comes next. Teams apply $1,830 to invoice A and leave $310 hanging on it, then absorb the $1,200 promotional deduction by shorting whichever invoice is handy. Instead, close invoice A in full using the $1,830 of cash plus a new $310 deduction item coded "shortage claim." Applying $47,620 to the 29 invoices and $1,830 to invoice A uses $49,450, which is $1,200 more than the cash received. Create a second deduction item for $1,200 coded "promotional allowance" to cover the difference, and request the backup for it.
The customer's open items are now three lines that add up to $3,470.00, each with a reason: invoice B at $1,960, the $310 shortage claim and the $1,200 promotional deduction. Invoice B gets a call to the customer's AP team, since it was either disputed or missed. The two deductions go into your research workflow. Our guide to handling wholesale deductions when a customer short-pays covers how to validate and recover them.
If remittance never arrives at all, apply the payment to the oldest open invoices only when your customer agreement or written policy allows it. Then send the customer a statement showing exactly what you did.
Apply the Gross Card Amount, Not the Deposit
Your processor settles in batches, so one card deposit mixes several customers' payments. Fees either come out of each deposit (net funding) or are debited separately, commonly once a month (gross funding). Your processor agreement decides which one you have. Visa and Mastercard rules don't.
Illustrative example: one day's batch holds three customer payments of $4,200.00, $1,875.00 and $960.00, or $7,035.00 gross. Assume batch fees of $211.05, a blended 3% picked to keep the arithmetic simple. It isn't a quoted rate.
| Funding Setup | Bank Deposit | Apply to Invoices | Book to Fee Expense |
|---|---|---|---|
| Net funding | $6,823.95 | $4,200.00, $1,875.00, $960.00 | $211.05 from the deposit |
| Gross funding | $7,035.00 | $4,200.00, $1,875.00, $960.00 | $211.05 when the fee debit posts |
Under either setup, the invoices get the gross amounts. If you spread the net deposit across the three invoices instead, every card-paying customer ends up with a few dollars of phantom balance that triggers statements and calls. Split each batch with your gateway's transaction-level report and match on the captured invoice number.
Surcharges cause the opposite problem, because the customer pays more than the invoice. Apply the invoice amount to the invoice and record the surcharge as your accountant directs. Card network rules govern surcharging, and some states add their own limits. Our rundown of Visa and Mastercard surcharge rules on caps, signage and registration covers the details. MannyPay offers surcharging programs where permitted, along with cash discount and dual pricing. Refunds and chargebacks that reduce a deposit get their own entries. Never net them against an unrelated customer's payment.
Automate the Accounts That Send the Most Payments
Automation can't fix missing remittance, but once the data exists it removes most of the keying. Ask your bank for daily transaction reporting in BAI2, the cash management reporting format developed by the Bank Administration Institute, which AR software can import for matching. With a lockbox service, the bank opens your check mail, scans checks and stubs, and sends you a data file with images. Large retail and grocery customers that run EDI can send an X12 820 payment order/remittance advice, the transaction set built for payment detail, which feeds matching rules directly.
Cash application software matches on rules (amount, invoice number, PO, payer alias) and routes the leftovers to a person. When you take card and ACH payments inside your accounting system, those payments skip matching entirely because the invoice link is created when the customer pays. On the acceptance side, MannyPay offers a QuickBooks integration and supports gateways including Authorize.net and NMI through its payment gateway options. Our comparison of adding card and ACH to NetSuite, Acumatica or QuickBooks covers the ERP side.
Write rules and alias entries for your highest-volume payers first. A rule that fires 40 times a month is worth more than one that fires twice.
A Month-End Routine for Unapplied Cash and Credit Balances
Set an age threshold for unapplied cash, review everything past it each month and note the research done. Send unresolved items to the customer's AP department, since the buyer who placed the order rarely knows how it was paid. Look for duplicates, such as an invoice paid by check and again by card because the check was slow. Reconcile card deposits to processor reports and confirm the fees are booked. Age open deductions and escalate the ones past your research deadline.
Credit balances need a decision: apply them to open invoices, refund them, or hold them with the customer's written approval. Long-standing credits can become reportable under state unclaimed property laws, and the rules differ by state. This is general information, not legal or tax advice, so confirm your obligations with your accountant or another qualified professional.
One caution about the customer who insists they paid: before you assume a posting error, confirm the bank details they used. In invoice redirection fraud, a scammer sends your customer altered payment instructions, and the money goes to an account you will never find in your own bank records.
This week, pull your unapplied cash report and sort it by customer. Start with the names at the top. Ask their AP teams for invoice-level remittance in the ACH addenda or through a portal, and add their payer aliases. If the way you take card and online payments is part of the problem, MannyPay can review how you accept them today. Request a free quote, and a MannyPay specialist will respond within one business day.
Sources
- Nacha, User Guide for Electronic Child Support Payments (CCD+ and CTX addenda formats)
- PCBB, ISO 20022 FAQs (Fedwire Funds Service conversion on July 14, 2025)
- INTRUST Bank, Wire Transfer Migration to ISO 20022 (field terminology changes)
- BAI (file format), Wikipedia
- 1EDISource, EDI 820 Payment Order & Remittance Advice Specifications
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.
