Define the bank accounts, payment channels, entities, currencies, and posting dates included in the cash application run. Capture a dated list of receipts before matching begins, including unidentified deposits and amounts already routed to an exception queue. A stable opening population makes it possible to prove that every receipt was applied, held, or escalated.
How an offshore bookkeeper can support a cash application policy
Create a controlled cash application workflow that traces each receipt from bank evidence to an approved invoice allocation or visible exception.
Published · 8 minute read
The short answer
- Capture a dated receipt population before matching so every deposit receives a disposition.
- Support invoice allocations with payer and remittance evidence rather than amount alone.
- Quarantine ambiguous receipts and reconcile all applications, transfers, refunds, and open cash to the bank population.
Start with a controlled receipt population
Use remittance evidence deliberately
Link each deposit to the bank reference, payer identity, remittance advice, customer account, candidate invoices, fees or deductions, and prior correspondence. Record the source of a proposed match rather than relying on an amount that happens to equal an invoice. Where one payment covers several invoices, retain the allocation supplied by the customer or the documented client rule used to prepare it.
Keep proposed matches reviewable
The workpaper should show the receipt value, original candidate balances, proposed allocation, residual amount, preparer, timestamp, and status. Do not overwrite the bank description or open-invoice data with a cleaned value. If a match is revised, keep enough history for a reviewer to understand why the first proposal changed.
Draw the line before approval
An offshore bookkeeper can compare remittance evidence with open invoices and prepare an application under written rules. An authorized client reviewer should resolve disputed deductions, cross-customer transfers, refunds, write-offs, unusual currency differences, and any application requiring policy judgment. Payment release and changes to bank permissions remain outside the preparation lane.
Quarantine ambiguous receipts
Stop when the payer cannot be identified, invoice references conflict, the receipt appears duplicated, the customer has a live dispute, or an allocation would leave an unexplained balance. Route the item with the records checked and a specific decision request. Holding a receipt visibly is safer than forcing it to the nearest invoice to improve an unapplied-cash metric.
Reconcile the completed batch
Tie applied receipts, approved fees, refunds, transfers, and unapplied balances back to the bank population and the receivables ledger. Investigate missing deposits, applications posted to a different date, and changes made outside the workpaper. The sum of all dispositions should explain the opening receipt population without silent deletions.
Monitor the reasons cash remains open
Age unapplied receipts by payer, cause, and decision owner. Track remittance gaps, incorrect customer references, reversed applications, and proposed matches rejected in review. These measures point to a source or policy problem rather than encouraging unsupported matching for speed.
Retest the policy after changes
Revisit examples and access controls when payment channels, lockbox files, customer identifiers, currency handling, or approval limits change. Test a single-invoice receipt, a multi-invoice remittance, and an ambiguous deposit. A reliable cash application workflow increases preparation capacity while leaving exceptions and protected decisions with authorized client personnel.
Questions owners ask
How should a payment covering several invoices be handled?
Retain the customer’s remittance allocation or apply the client’s documented rule, show any residual amount, and route conflicting or incomplete instructions for review.
When should a receipt remain unapplied?
Keep it visibly unapplied when the payer is unknown, references conflict, several allocations are plausible, a dispute is active, or the proposed match would leave an unexplained balance.