Most business owners have had this moment: QuickBooks shows a customer is overdue, cash is tight, and the instinct is to follow up right away.
But an overdue balance is not always money you should chase. Sometimes the customer already paid. Sometimes a credit memo is sitting in the file. Sometimes the aging report is technically true, but operationally misleading.
In the walkthrough below, a customer appeared to owe $2,000. After checking the credits and payments behind the aging report, the net balance was actually zero.
Watch the YouTube Short on MosoFin’s channel.
That is the real lesson. A good collections workflow does not start with pressure. It starts with verification.
Which guide do you need? This one shows how to build a structured A/R aging and collections workbook as a review output. If you want the underlying 15-minute review method — validating the report, measuring concentration, and prioritizing exceptions — start with the companion guide: QuickBooks overdue invoices: a 15-minute A/R review.
The risk: treating an aging report like a call list
A/R aging reports are useful because they show who owes money, how long balances have been open, and where cash may be stuck. But the report is only the first layer.
For business owners, the risk is emotional and practical: you see a large overdue balance and assume cash is available if someone just pushes hard enough.
For bookkeepers and financial professionals, the risk is reputational: if you tell an owner to chase a customer who actually has a credit or zero net balance, the finance process looks careless.
Before outreach, the team needs to answer five questions:
- Is this the right QuickBooks company and report date?
- Does the aging summary tie back to the invoice-level detail?
- Are any credits, payments, or unapplied amounts changing the real balance?
- Which customers are priorities because of age, amount, or concentration?
- What should happen next, and who owns it?
That is where a workbook helps. It turns a raw overdue list into a review process.
The better workflow: explain first, contact second
The workflow shown in the video uses MosoFin inside Claude: Bea, MosoFin’s accounting software agent, retrieves the authorized read-only QuickBooks data, and Claude reviews the A/R aging, reconciles exceptions, and prepares a downloadable workbook for human review.
The important part is not just the answer in chat. The important part is the structure: six tabs that move from context to action.
| Workbook tab | What it does | Why it matters |
|---|---|---|
| Run Context | Documents the workspace, QuickBooks company, report date, source, and whether anything changed | Gives the review a documented history |
| Aging Summary | Rolls customers into aging buckets and shows the A/R picture | Shows where the money is stuck |
| Aging Detail | Breaks totals down invoice by invoice | Makes every dollar traceable |
| Collection Plan | Ranks customers and assigns suggested next actions | Turns reporting into work |
| Drafts | Prepares review-only outreach messages | Saves time without sending anything automatically |
| Exceptions | Explains credits, payments, and reconciliation differences | Prevents collection mistakes |
The sequence matters. You do not want the collection plan before the exceptions. You do not want draft messages before checking whether a customer nets to zero.
What the example found
The figures below are a product demonstration using an illustrative QuickBooks workbook — they are not a customer’s file. In the demo, Claude confirms that the QuickBooks data is live and builds a six-tab workbook. The example analysis shows:
- $155,646 in total A/R;
- 91% overdue;
- $40,656 over 90 days;
- 63.1 weighted average days late;
- 54.3% of A/R concentrated in the top five customers;
- a $4,500 reconciliation difference explained by two credits and one payment;
- 31 overdue customers ranked for review;
- 12 draft messages marked review required and not sent.
The detail that matters most is Cedar Works. It looked like a $2,000 overdue balance, but a credit brought the customer to a zero net balance.
That changes the action completely. The right next step is not “call the customer.” It is “apply or verify the credit first.”
Why this matters to owners
Owners usually care about three things in collections:
- How much cash might come in?
- Which customers need attention first?
- What can the team do today?
A raw QuickBooks aging report answers the first question only partially. It shows open balances, not certainty. It does not automatically explain disputes, credits, unapplied payments, recent customer conversations, or whether the report was run against the right workspace.
A better review gives the owner a short operational answer:
Here is the total exposure, here are the risky customers, here are the exceptions to verify, and here is the next action owner for each priority account.
That is much more useful than sending a spreadsheet and hoping someone knows what to do with it.
Why this matters to bookkeepers and finance teams
For bookkeepers, accounting firms, and fractional CFOs, the goal is not just to find overdue invoices. The goal is to produce a review the client can trust.
That means preserving the context around the report:
- which client or entity was selected;
- whether the source was live QuickBooks data;
- the as-of date;
- whether any records were changed;
- how totals tie to invoice detail;
- which exceptions need bookkeeping attention;
- which outreach drafts still require human review.
This is why the Run Context tab is not a throwaway. It is the control sheet. When a client asks, “Where did this number come from?” the answer should not depend on someone remembering which filters they clicked.
The six-tab review pattern
If you want to apply the idea manually, use the six-tab pattern from the walkthrough.
1. Run Context
Start with the basic control information: company, workspace, report date, source, and whether any records changed. For a client-facing workflow, this is the control record.
In the MosoFin example, the workflow is read-only. The review can prepare analysis and drafts, but it does not send messages or write changes back to QuickBooks.
2. Aging Summary
Summarize the total A/R and aging buckets by customer. Look for the biggest balances, the oldest balances, and the bucket where risk is building.
This is the owner view. It answers, “Where is the money stuck?”
3. Aging Detail
Move from customer totals to invoice-level evidence. Each line should show the customer, invoice number, due date, days past due, bucket, and open balance.
This is where totals become traceable. If the summary says a customer owes money, the detail should show the invoices behind it.
4. Collection Plan
Turn the aging data into a ranked worklist. Include the customer, overdue balance, oldest days past due, worst bucket, open invoices, suggested next action, owner, and status.
This is where finance becomes operations. Someone should be able to open the tab and know what to do next.
5. Drafts
Prepare draft messages for priority customers, but keep them review-only. That distinction is important.
A finance workflow can speed up writing without removing judgment. The person sending the message still needs to confirm the customer, amount, tone, context, and relationship.
6. Exceptions
This is the mistake-prevention tab. List credits, payments, reconciliation differences, and any item that changes the action.
If a customer nets to zero, do not contact them like they owe money. Fix or verify the accounting trail first.
The safest rule: no automatic sending
Collections touches customer relationships. That makes human review non-negotiable.
In the walkthrough, the workflow prepares 12 drafts, but every draft is marked review required and not sent. It also confirms that nothing was changed in QuickBooks.
That is the right posture for most small businesses and finance teams:
- structure the analysis;
- organize the worklist;
- prepare the draft;
- keep the final action human.
Want to try the full setup?
The Short shows the result. The full setup walkthrough shows how to connect MosoFin and get the workflow ready inside Claude:
You can also open the setup video directly here: watch the full MosoFin setup walkthrough.
FAQ
What should I check before contacting a customer about an overdue QuickBooks invoice? Check whether credits, payments, unapplied amounts, or zero-net balances explain the overdue amount before anyone contacts the customer.
What does an A/R aging collections workbook include? A useful workbook includes run context, aging summary, invoice-level aging detail, a ranked collection plan, review-only message drafts, and exceptions for credits or payments.
Can MosoFin send collection messages automatically? No. MosoFin is designed as a read-only review layer. It can prepare review-only drafts, but nothing is sent and nothing is changed in QuickBooks by the workflow shown here.
Who is this A/R review workflow for? It is useful for small business owners, bookkeepers, accounting firms, fractional CFOs, and finance teams that need to turn overdue invoice reports into clear next actions.
The bottom line
Collections should not start with a call. It should start with a clean review.
Before you chase an overdue invoice, check the credits, payments, and exceptions. Then build the worklist. Then review the draft. Then contact the customer when the numbers actually support it.
