Prepare a cash disbursement cutoff packet for review

Cash disbursement cutoff asks which payments belong in the period under review and what evidence supports that answer. Start with the entity, bank accounts, payment methods, statement date, and ledger accounts. Include wires, ACH items, checks, card settlements, and manual payments if they fall within scope. The bookkeeper can assemble the population from the payment register and bank activity. The finance owner approves the scope and applies the accounting policy. Write exclusions down. A missing payment method or closed account can create a false sense of completeness. Keep the extraction date so a later reviewer knows which version of the register was used.

Compare the payment register with the bank statement, cleared transactions, and ledger activity. Match by amount and date only after checking payee, reference, and account. A same-amount match can still be a duplicate or an unrelated payment. Mark each item as cleared, outstanding, returned, voided, duplicated, or unresolved. The bookkeeper prepares the comparison and links the evidence. The authorized reviewer decides how an exception should be recorded. Do not delete a payment from the register because it did not clear. Record the reason and next action. The retained population helps the business distinguish timing from an incorrect or unauthorized disbursement.

An invoice approval, purchase record, or payment authorization answers a different question from bank clearance. Keep those records separate in the packet. Check whether the approver was authorized, whether the amount agrees, and whether the approval references the item being paid. If approval is missing, hold the item and state the decision needed. A bookkeeper can request permitted evidence and maintain the queue. It should not approve a payment it prepared or use a bank transaction as proof that a purchase was approved. When a payment is urgent, the written stop condition matters even more because pressure can turn a missing record into an informal exception.

Dates around a cutoff often reflect different events: payment initiation, bank processing, clearing, posting, invoice receipt, and service delivery. List the dates available and explain which one the policy uses. If the source records disagree, do not choose the most convenient date. Escalate with the conflicting evidence and a bounded question. The reviewer can decide whether the item belongs in the period, whether a correction is required, or whether further investigation is appropriate. A remote bookkeeper adds value by making the conflict visible and easy to answer. A polished reconciliation that hides timing uncertainty is not a reliable close packet.

Preparation and payment release should remain separate. Use named accounts, multifactor authentication, and least-privilege access for banking and accounting systems. A bookkeeper should not add a beneficiary, change bank details, release funds, or approve its own exception. If the workflow requires a temporary access change, document the approver, purpose, and removal date. Store payment evidence in the controlled workspace and limit downloads containing account information. A cutoff procedure cannot compensate for a person having end-to-end control. The role boundary should appear in the task instructions, approval matrix, and escalation template, not only in onboarding conversations.

For each uncleared item, record payment reference, amount, payee, initiation date, expected clearing date, source evidence, owner, and next review date. Separate normal bank timing from items that may be returned, duplicated, or unauthorized. Age the item from initiation and update the status only when evidence changes. A manager can use counts by age, payment method, and owner to decide where attention is needed. Do not treat a lower outstanding count as improvement if returned or voided payments were removed without a disposition. Keep the original register and add the final outcome after review.

Sample ordinary items and exceptions. Include a payment that cleared after cutoff, a returned payment, a duplicate-looking amount, a manual check, and a transaction with incomplete approval. Ask whether the source chain is complete and whether the conclusion follows the stated policy. Track rework and questions returned by reviewers. If the same exception appears repeatedly, repair the intake or approval process instead of adding another reminder. Offshore bookkeeping support should make the finance lead’s decision quicker, not replace it. The review sample shows whether the cutoff packet is usable under deadline conditions.

Operations, accounts payable, treasury, and finance may each hold part of the payment story. Name which team supplies the invoice, which team confirms receipt, which team controls release, and which team reviews the cutoff. The bookkeeper can note when an input arrived and where it came from. The responsible owner decides whether the input is sufficient. This mapping prevents a payment from being marked unresolved simply because it crossed a team boundary. It also makes a time-zone handoff concrete: the next person receives the source, question, owner, and deadline instead of a request to search an entire mailbox.

Retain the scoped population, bank statements, payment register, approval references, outstanding register, and reviewer decision. Add posted journal references or follow-up actions without changing the evidence used for the original review. Update the procedure when payment methods, banking access, or close dates change. A clear cash disbursement cutoff packet gives the owner a defensible explanation of what cleared, what did not, and what remains open. It also gives the next offshore bookkeeper a starting point that does not depend on private memory.