The difficult part of accounts receivable management is often the handoff. One person updates the books, another answers a customer, and a third sends the next reminder. Each action can be sensible on its own while the combined workflow becomes confusing.

This is a proposed weekly routine for a bookkeeping practice, not a universal collection policy. Choose timing, authority, and escalation boundaries with each client. The aim is to end a review with a reliable record and an understandable next step.

Start with a defined responsibility

Before the first review, agree who can approve customer messages, confirm disputes, change invoice details, or accept a payment arrangement. Do not assume that access to the accounting system gives your firm authority to make every commercial decision.

Keep that agreement somewhere your team can find. A small responsibility table is more useful than an unwritten understanding:

These are example assignments. Your engagement and the client's organization determine the actual owners.

1. Refresh and reconcile the starting view

Choose a review date and make sure the accounting information reflects the period you intend to inspect. For QuickBooks, the aging summary gives a customer-level view and the detail report helps you inspect individual overdue transactions. Intuit explains both in its aging report documentation.

Check that the selected company, reporting date, and currency are correct. If the operational workspace and the accounting source disagree, investigate before approving a message. The difference may be a recent payment, an unapplied credit, a stale export, or a filter.

Do not add balances in different currencies into one unlabeled number. A useful practice-wide view can show several currency totals without pretending they are directly comparable.

2. Sort exceptions before preparing reminders

Create a small set of decisions rather than one undifferentiated overdue list:

• Ready for follow-up: the balance and contact are checked, and there is no conflicting conversation.
• Waiting on a commitment: a customer has provided a specific amount and date.
• Needs clarification: a dispute, purchase-order issue, or missing information needs attention.
• Needs accounting review: the balance or payment allocation is uncertain.
• Needs a contact fix: the email bounced or the billing contact changed.

Those labels describe the work. They should not change the accounting balance by themselves. A promise is still outstanding money until the relevant payment is recorded.

For example, two invoices may both be 32 days overdue. One needs its first reminder; the other is waiting on a correction agreed yesterday. Sending the same message to both discards the most useful context you have.

3. Review the message queue together

Give the reviewer enough information to make a decision: client, customer, invoice, current amount, recipient, latest conversation, and proposed text. A queue that only says "12 reminders ready" is not enough to judge whether those reminders are appropriate.

Batch similar work where it helps concentration, but inspect each recipient and balance. If another platform is already sending reminders, agree how to avoid overlapping outreach. Start with the invoice email templates and adapt the message to the actual situation.

In Clawrk, drafting and approval are separate steps. Connected QuickBooks balances are checked again before sending. Delivery status remains separate from payment status, so the team can investigate a bounced message without treating it as an accounting event.

4. Give replies and promises a review point

A routine is incomplete if it only schedules outgoing messages. Set aside attention for what came back: a question, a payment reference, a promised date, or a request to stop reminders.

Record the next action and who owns it. "Customer replied" is less useful than "Client to confirm revised line item; review Thursday." If the response changes the context, pause the previous follow-up plan until someone reviews it.

Business.gov.au's unpaid-invoice guidance distinguishes checking the issue from later escalation. It is Australian guidance; legal steps must be assessed for the relevant jurisdiction and engagement. A bookkeeper's working queue should make the point for client escalation visible rather than turning reminders into unreviewed legal demands.

5. Close the review with a short client update

Use an update that separates the financial record from the work in progress. Here is an original example structure:

Receivables review - [date]

Confirmed recorded payments: [amount by currency].

Open balances requiring attention: [amount by currency].

Awaiting promised payments: [count and dates].

Decisions needed from you: [specific questions].

Next review: [date and owner].

Do not describe all reductions in receivables as recovered cash. Credits and write-offs can reduce a balance without producing a bank receipt. Keep those explanations separate.

The next reviewer should be able to continue from the record without reconstructing a week of messages. That is the test of the routine: the work remains understandable when the person doing it changes. Clawrk's workspace features bring those balances, conversations, and next steps into one practice view.