Worked example
Simple cash application
Payment
$1,250.00 ACH
Invoice records
INV-10487 $1,250.00
Review result
Invoice balance becomes $0 after confirmation
The accounting system remains the final ledger. The match is verified before posting or export.
Cash application versus bank reconciliation and collections
These processes answer different questions. Collections follows up on money still owed. Cash application allocates money already received. Bank reconciliation checks the recorded bank balance against the bank statement and explains differences. A payment can reach the bank before anyone knows which invoices it should settle.
| Process | Question | Example |
|---|---|---|
| Collections | What still needs to be paid? | Follow up on an overdue $1,250 invoice |
| Cash application | Which balance does this receipt settle? | Allocate a $1,250 ACH to INV-10487 |
| Bank reconciliation | Do bank records and the books agree? | Explain a deposit recorded in a different period |
The basic information flow
The invoice system says what customers owe. The bank or payment processor says what money arrived. Remittance advice says what the customer intended to pay. Cash application brings these records together and creates a reviewed allocation.
When the customer pays through a tightly linked payment channel, much of the information may already travel together. External ACH, wires, checks, and processor deposits often require more investigation.
A clean payment is straightforward
Suppose invoice INV-10487 has $1,250 outstanding and an ACH for $1,250 includes INV10487 in its memo. After checking customer, currency, date, and duplicate status, the evidence supports a strong one-to-one application.
The confirmation should still record the source transaction and reviewer. Strong automation shortens the review, but it does not erase accountability.
The difficult cases
One receipt can pay several invoices. Several receipts can settle one invoice. A customer can pay partially, overpay, deduct an amount, omit a reference, or use a different legal entity name. A processor can combine receipts and subtract fees.
These are normal operating exceptions, not reasons to hide a difference. A useful queue gives each case a factual explanation and a set of deliberate actions.
- Exact and reference matches
- Combined and partial applications
- Fees, deductions, and overpayments
- Payer name variations and missing references
- Duplicates and unresolved receipts
A small-team operating procedure
Import posted receipts and current open balances on a set cadence. Confirm strong matches, assign exception follow-up, export only confirmed applications, and verify the accounting system. Keep unresolved payments visible between cycles.
Store payer aliases and mapping rules transparently. If the only person who knows that HORIZON MGMT means Horizon Property Management is out of office, the process should still be understandable.
What automation should and should not do
Automation can parse files, normalize references, detect duplicates, find combinations, rank candidates, and organize exceptions. It should not silently decide accounting treatment for a discrepancy or change the books without deliberate confirmation.
Measure whether reviewers reach a correct result faster, not merely whether the software labels more transactions as matched.
Key takeaways
- Cash application connects receipts with customer obligations.
- Remittance is often the best evidence for grouped payments.
- Keep difficult cases in a visible exception queue.
- Make aliases and rules inspectable.
- Require deliberate confirmation before ledger changes.
Try the payment-matching step
InvoiceReconcile helps compare invoice and payment files. It does not reconcile your general ledger or automatically post to your books.
This material is general educational information, not accounting, tax, legal, or investment advice. Verify financial records and consult the appropriate professional for decisions that require judgment.