Open with the deposit record

Start each batch with the bank's deposit record, not with the invoice list. The deposit record establishes the amount, the value date, and the reference numbers the bank actually received. If the batch starts from open invoices, the team tends to look for a payment that fits the balance instead of recording what arrived. That habit creates applications that later have to be reversed.

Reconcile the deposit total to the sum of the individual receipts before touching customer accounts. A difference at this stage usually means a missing page, a duplicate scan, or a bank fee that belongs in a separate line. Resolve the batch total first, because a mismatch inside a customer account is much harder to find after the work has spread across several records. If the total cannot be reconciled, stop the batch and resolve the bank record first.

Match the payer before the amount

Identify the payer from the remittance, the bank reference, and the customer master record. Do not let an amount that matches an open invoice decide the customer. Two customers can owe the same amount on the same day, and a wrong match is more expensive to unwind than an unmatched receipt. Confirm the legal entity and the billing account when the names are similar.

When the payer is unclear, keep the receipt unapplied and document the candidates. List the evidence for each candidate rather than choosing the most convenient one. If a customer has changed names through an acquisition, check the master record for the former name before assuming the payment belongs elsewhere. The checklist should make the evidence visible to the next reviewer.

Handle one payment across several invoices

Apply a single payment to the invoices the remittance actually identifies, in the order the customer states. If the remittance is silent, use the customer's documented payment instruction and the approved aging order. Do not invent a priority that favors the oldest invoice if the customer has disputed it. The application should reflect the agreement, not the collector's preference.

Record any unapplied remainder as its own item with the reason. A partial application can be correct when the customer has withheld a specific charge. The remainder should stay linked to the original receipt so a later reviewer can see the full amount. Do not split the payment into unexplained pieces just to make the aging report look cleaner.

Explore the related specialist service to define scope, ownership, and evidence.

Record what the remittance does not say

The absence of a remittance is information, and the checklist should capture it. Write down which fields were missing, what was used instead, and who approved the alternative. If the team applies a payment from the bank reference alone, say so. A future reviewer needs to know whether the match rested on evidence or on a reasonable guess.

Use a consistent note format so missing information is easy to find. The note should name the receipt, the customer, the invoices, and the unresolved question. If the customer promised a remittance by email, record the date and the sender. An unapplied payment with a clear note is easier to clear than one with a confident but unsupported application.

Stop when the evidence conflicts

Conflicting evidence is a stop condition, not a prompt to choose the better-looking record. If the remittance names invoice 2201 but the bank reference points to invoice 2198, preserve both and route the item for review. The reviewer should see the conflict exactly as it appeared. Forcing a match hides the problem and usually creates a second one.

The stop rule should name who decides and how quickly. A routine conflict might go to the cash application lead, while a suspected fraud or duplicate payment goes to the controller. Write the escalation path beside the checklist so the analyst does not have to invent one under pressure. The goal is a controlled pause, not a stalled batch.

IRS Publication 583, Starting a Business and Keeping Records provides public guidance that can inform a documented review.

Close the batch with a control total

At the end of the batch, compare the total applied, the total left unapplied, and the deposit total. The three numbers should reconcile to the bank record. If they do not, find the difference before the batch is marked complete. A control total that is checked only at month end allows small errors to compound for weeks.

Save the batch summary with the receipt count, the applied amount, the exception count, and the reviewer's name. The summary does not need to be long, but it should let someone reconstruct the work. If the next shift inherits an exception, the summary should point to it directly. A clean batch close is evidence that the checklist was followed.

Leave an audit trail for the next day

Every application should show the receipt, the invoice, the amount, the date, and the rule or instruction used. A reviewer should be able to follow the trail without opening a chat history. If a manual adjustment was needed, record the reason and the approver. The audit trail is the difference between a correction and an unexplained change.

Check a small sample of the day's applications before closing. Pick one clear match, one partial payment, and one exception. Ask whether the note would let a new analyst repeat the decision. If not, improve the note format rather than relying on the original analyst's memory. Small daily checks keep the checklist honest as volume changes.

Continue with a related workflow guide.

Common questions answered

Where should a lockbox batch start?

With the bank deposit record, reconciled to the individual receipts before customer accounts are touched.

What should happen when the remittance is missing?

Record the missing fields, the evidence used, and the approver, then keep the receipt traceable.

When should cash application stop?

When payer or invoice evidence conflicts, with the conflict preserved and routed to the named reviewer.

Trace a partial customer short-pay to the deduction codeReconcile an unapplied cash suspense balance at week endApply a customer overpayment to the next open invoice

Define one reviewable receivables workflow.

Bring the queue, owner, source records, and exceptions you need to make visible.

Book a free consultation