An accounts receivable aging report is useful only if it becomes a work queue.

The report tells you which invoices are current or overdue. It does not tell you whether the balance is correct, whether the customer disputes it, who owns the follow-up, what was promised, or what happens next.

For a startup, the better operating loop is:

Validate → classify → prioritize → contact → document → escalate → reconcile

That sequence matters. If the aging report is wrong, collection activity can damage a customer relationship instead of improving cash flow.

This guide shows how to turn the report into a controlled weekly collection process, with a real owner, evidence, next action, and escalation path for every material invoice.

Start by validating the aging report

An aging report is a point-in-time view. Microsoft’s current Dynamics 365 documentation describes aging snapshots as containing aged balances at a specific point in time, which is a useful reminder that the report can become stale as payments, credits, disputes, and new invoices move. Microsoft documents that behavior here.

Before anyone contacts a customer, confirm that the queue is trustworthy.

Check for:

• unapplied cash;
• payments received but not matched to an invoice;
• credit memos that have not been applied;
• duplicate invoices;
• invoices missing from the report;
• incorrect due dates;
• canceled or superseded invoices;
• customer balances that do not match the underlying ledger; and
• a mismatch between the aging total and the accounts receivable balance in the general ledger.

Do not send collection emails from a report you have not reconciled.

Give every invoice one operating state

Aging buckets are not enough.

Two invoices can both be 61 days overdue while requiring completely different next actions.

Use a small set of operating states:

Xero’s current AR aging guidance specifically recommends capturing context such as disputes, promised payment dates, and credit holds. Microsoft’s collections tools likewise distinguish disputed transactions and collection activities. (Xero)

The point is not to copy a software status list. It is to stop treating every overdue invoice as “send another reminder.”

Prioritize by more than age

Age matters, but age alone is a weak prioritization rule.

A $75,000 invoice that is 15 days late may matter more to runway than a $600 invoice that is 95 days late. A disputed invoice needs resolution, not more collection pressure. A customer who promised to pay tomorrow may not need another email today.

Build priority using several signals:

• Age: how far past due the invoice is.
• Amount: how much cash is at risk.
• Cash impact: how important the collection is to near-term liquidity.
• Customer concentration: whether one customer represents a large share of total receivables.
• State: valid overdue, disputed, says paid, admin blocked, promise to pay, etc.
• Promise date: whether the customer made a specific commitment.
• Relationship or contract context: whether escalation could create a commercial issue that needs a senior owner.
• Evidence quality: whether the invoice and supporting documents are complete enough to defend the request.

Xero’s current guidance also recommends looking beyond age to the size of balances, concentration, disputes, and payment behavior. (Xero)

A useful queue therefore answers:

What should we work next, and why?

Not:

Which invoice is oldest?

Run a weekly collection cadence

A startup does not need a giant collections department. It needs one reliable operating rhythm.

A practical weekly cycle looks like this:

1. Refresh and reconcile the aging

Pull the current aging report and reconcile the total before changing statuses or starting outreach.

2. Review new exceptions

Look for:

• invoices newly overdue;
• missed promised-payment dates;
• new disputes;
• customer claims of payment;
• unapplied cash;
• invoices that crossed an internal escalation threshold; and
• accounts whose balance has become material to cash forecasting.

3. Assign the next action

Every material invoice should have:

• an owner;
• one current operating state;
• last contact date;
• next action;
• next action date;
• evidence link;
• promise date and amount, if any;
• dispute owner, if any; and
• escalation status.

4. Perform outreach

Keep outreach proportional to the account state.

Ordinary overdue invoices may need a reminder or call. A dispute needs the right internal owner. A broken promise may need escalation. A customer saying “we paid this” needs payment tracing before another demand.

5. Record what happened

Do not rely on email search as the collection system.

Document:

• channel;
• date;
• contact;
• response;
• promise;
• dispute;
• missing document;
• next action; and
• supporting evidence.

Stripe’s AR aging guidance notes that aging reports often include comments about collection efforts and payment agreements, and that businesses can use the report to support reminders, dispute resolution, payment plans, and credit-policy decisions. (Stripe)

6. Escalate only when the state calls for it

Do not threaten legal action because an invoice crossed an arbitrary bucket.

Route consequential decisions separately.

Treat promises to pay as commitments, not notes

“Customer said they will pay” is not a resolved invoice.

For each promise to pay, record:

• promised amount;
• promised date;
• person who made the commitment;
• method of communication;
• evidence or message link;
• whether the promise covers the full invoice;
• next follow-up date; and
• what happens if the promise breaks.

If payment arrives, match it and close the promise.

If the promise date passes without payment, change the state. Do not keep carrying an old promise forward as if it is current.

This is one reason collection notes belong in the operating queue rather than in someone's inbox.

Handle disputes on a separate path

A disputed invoice should not move through the same cadence as an undisputed overdue balance.

Capture:

• dispute reason;
• customer position;
• internal owner;
• contract, PO, invoice, or delivery evidence;
• amount disputed;
• amount undisputed;
• missing documentation;
• decision required;
• target resolution date; and
• next customer communication.

A dispute may be commercial, operational, contractual, or accounting-related.

The AR operator can coordinate the evidence and follow-up. They should not invent a legal conclusion, approve a material credit outside their authority, or decide accounting treatment merely to make the aging report cleaner.

Microsoft’s collections documentation explicitly exposes disputed balances and cases/activities as separate collection-management concepts. (Microsoft)

Define where the operating playbook stops

The collection process should have clear escalation boundaries.

Pause ordinary outreach and route the decision when the issue involves:

• a material credit or invoice adjustment;
• changing contractual payment terms;
• a bad-debt allowance or write-off;
• bankruptcy or insolvency;
• threatened or actual litigation;
• referral to a collection agency;
• customer fraud concerns;
• tax treatment;
• accounting judgment; or
• a contractual dispute that needs counsel.

This article does not prescribe when to write off a receivable, what reserve percentage to use, how to pursue legal collection, or when a payment plan should be legally documented. Those decisions depend on facts, accounting policy, contracts, and jurisdiction.

Use one AR Collection Control Workbook

Your working tracker should make the state of every material invoice obvious.

Recommended fields:

That workbook should be a work queue, not an archive.

A simple collection cadence and ownership matrix

Your exact contact cadence should reflect customer relationships, contract terms, invoice size, and risk. Do not copy a universal 30/60/90 script and treat it as policy.

Use a decision structure instead:

The table creates consistent ownership without pretending every customer should receive the same communication sequence.

Close the monthly loop

Weekly collections should feed a monthly control review.

At month end:

1. reconcile the refreshed aging to the books again;
2. review how balances moved between aging buckets;
3. identify large or concentrated exposures;
4. review broken promises and unresolved disputes;
5. update cash-flow assumptions;
6. inspect credits, adjustments, and other exceptions;
7. identify recurring root causes; and
8. change the upstream process where needed.

Recurring issues often point upstream:

• invoices sent late;
• unclear payment terms;
• missing purchase orders;
• incorrect customer contacts;
• weak approval workflows;
• billing errors;
• missing proof of delivery;
• poor dispute ownership; or
• no consistent follow-up owner.

The goal is not to become better at chasing invoices forever. It is to reduce the number of invoices that require chasing.

For the broader accounting cycle, connect this process to Chore's month-end close checklist. If collections are part of an outsourced bookkeeping engagement, define the exact ownership and completion evidence in the monthly bookkeeping delivery specification.

Where Chore fits

If your aging report is accurate and someone internally can own this weekly cadence, the process above can be run in-house.

If the problem is recurring operational ownership, Chore currently describes Accounts Receivable work as part of its Finance offering, including systematizing, processing, reviewing, tracking, customer billing, and collections management. Those capabilities should be rechecked before publication because service scope can change. (Chore pricing, Chore Finance)

The commercial decision should come after the operating process is clear:

First reconcile the aging. Then classify every material invoice. Then assign the next action. If nobody owns that cadence consistently, solve the ownership problem.