Five rules for matching remittances to the bank
Reading a remittance is the easy part. The rules for when and how it posts are where cash application goes right or wrong. Each of these five came from a real remittance that would otherwise have posted incorrectly.
The business case is in cash application without the spreadsheet. These are the rules the console enforces before anything posts.
1. The payment date is the bank date
Remittances carry the date the customer sent payment, often days before it reached the bank. Posting on that date makes the cash report disagree with the bank statement and moves cash between periods at month-end. The console posts on the date the matching deposit hit the bank and records the remittance’s own date in a note:
Payment date 2026-10-23 is the day the money hit the bank
(the remittance says 2026-10-16).When a deposit hasn’t arrived yet, nothing posts. That’s rule 3.
2. A label isn’t a payment method
Customers’ systems label references however they like. One customer’s remittance called every payment reference a “cheque number”, yet all two dozen of its payments in the past year had arrived by ACH. Trusting the label would have left each remittance waiting for a check that was never coming.
The rule: if a customer has paid electronically at least three times, and in at least 80% of payments over the past year, a remittance that says “check” is treated as electronic and matched to the bank. A manual override always wins and is never reversed by the console.
3. Checks wait until they clear
A check remittance can arrive days before the check. Posting it immediately overstates cash and understates receivables. Check remittances sit in a waiting for check state until a matching deposit appears or someone confirms the check is in hand, and that confirmation can be undone.
4. One deposit, one posting
The dangerous case: a remittance labelled as a check, for a payment that actually arrived by ACH. Worked from two angles — the check queue and the unmatched-cash queue — it posts twice. The console automatically matches a check-labelled remittance to a same-amount electronic deposit from the same customer, and warns whenever two remittances share an amount and customer within a short window.
5. Every deduction becomes a credit memo with a reason
A short-pay applied as a reduced payment loses the reason forever. Each deduction — damage, co-op, freight, pricing — becomes its own credit memo with a specific item and reason code, applied to the invoice, and the payment covers the cash. Deductions then show up in reporting by type and customer, where someone can decide whether to dispute them.
Two smaller lessons
- Scope your page scripts. A button handler that searched the whole page for elements, instead of only the console’s own panel, broke when the platform added elements with the same class. Query within your own container.
- Attach, then verify the attachment. Posting is supposed to attach the remittance to the payment. Check afterwards that the file is actually attached, and say plainly when it isn’t.
Related: cash application without the spreadsheet, and ACH addenda records.