What founders should review weekly about receivables

Receivables do not go bad overnight. They drift. A small delay becomes a habit. Then it becomes a cash problem.

A weekly receivables review stops that drift. It gives you early signals, clear owners, and fewer awkward “just checking in” emails later.

This is a simple 20-minute routine. You can run it with a spreadsheet, Stripe, QuickBooks, Chargebee, or any mix.

Why a weekly receivables review beats “end-of-month panic”

End-of-month AR reviews create two problems:

• You find blockers late (PO, portal steps, vendor setup).
• You chase harder, because you feel behind.

ICAEW advice on chasing debtors starts with checking the basics (invoice accuracy, receipt, and what is blocking payment) before escalating. Weekly review makes that easy because you catch issues while they are still fixable.

The 20-minute weekly receivables checklist (what to look at)

1) Overdue total and over-30-day %

Start with two numbers:

• Total overdue (value).
• Over-30-day AR as a % of total outstanding.

Why: over-30-day AR acts like mould. If it spreads, it is harder to clean later.

2) Ageing movements (what changed since last week)

Do not stare at a static ageing chart. Look for movement:

• Which bucket grew? (0–30, 31–60, 61–90, 91+)
• Which customers moved backwards?
• Which invoices jumped buckets?

A rise in debtor days is a classic warning sign in cash management. Investigate sudden changes rather than accepting them as “seasonal”.

3) Top 10 risk invoices (value + age)

Pick your list. Keep it consistent:

• Top 10 overdue by value, plus
• Anything >45 days overdue (even if small)

In B2B, one large invoice can define your month.

4) Promise-to-pay list (and misses)

This is the most founder-useful list.

Track:

• Promised pay date
• Who promised it
• Whether it landed

Your team should treat missed promises as a process event, not a personal offence. You simply follow up fast and reset the plan.

5) Disputes and queries (new, stuck, resolved)

You want three counts:

• New disputes opened this week
• Disputes closed this week
• Disputes stuck >14 days

If disputes stick, you usually have an internal bottleneck. Product, support, sales ops, or implementation owns it. AR just holds the thread.

If you report under IFRS, remember that expected credit loss thinking uses ageing and ongoing updates to expected collectability. You do not need to be an accountant to benefit from the mindset: revise risk as facts change.

6) Blockers: PO, portal, onboarding, vendor setup

Founders often underestimate this bucket. It is not “collections”. It is admin workflow.

Look for:

• Missing PO
• Vendor onboarding not complete
• Portal submission required (Coupa/Ariba, etc.)
• Incorrect billing entity or address
• Payment batch cycles (only pays on Thursdays, etc.)

These blockers respond well to calm, structured follow-up. They do not respond to “please pay”.

7) Customer comms quality (tone + speed)

Review a small sample. Five threads is enough.

Check:

• Did we reply within one business day?
• Did we answer the question, or repeat the reminder?
• Did tone stay polite and specific?

Stripe’s guidance on dunning stresses choosing timing and frequency carefully and keeping messages concise and clear. The same applies to manual AR emails.

8) Next-14-days cash forecast (confirmed vs hoped)

Split your forecast into two lines:

• Confirmed: customers who gave a date (in writing).
• Unconfirmed: “should pay soon”.

This avoids founder maths like: “It’s £200k outstanding, so we probably get £200k.”

The BSB way (in one page)

This is how we keep weekly reviews useful:

• We plug into your tools.
• We run a customer-friendly cadence.
• We read every reply.
• We tag the reason (late / dispute / missing PO / portal).
• We push blockers to your team with an owner and due date.
• We report weekly with actions, not noise.

Reusable line we use often:
We read every reply, tag the reason, and push blockers to your team so cash keeps moving.

A weekly receivables review table you can copy

Use this format in your weekly doc. Keep it to one page.

What you review	What it tells you	Threshold to act	Owner	Action this week
Total overdue (£/$)	Cash pressure now	Any week-on-week rise	Finance/RevOps	Identify drivers
Over-30-day %	“Sticky” AR risk	Rising 2 weeks running	Founder	Escalate blockers
Ageing movement	Where drift is happening	Any bucket jumps	AR owner	Re-segment comms
Top 10 risk invoices	Concentration risk	Any >£X or >45 days	AR + CS	Personal follow-up
Promise-to-pay misses	Reliability of dates	Any miss	AR owner	Same-day reset
Disputes open/stuck	Internal bottlenecks	Stuck >14 days	Dept owner	Fix root cause
PO/portal blockers	Admin drag	Any blocker >7 days	Ops/Sales Ops	Complete workflow
Reply speed	Relationship risk	>1 business day	AR owner	Tighten SLA
Next-14-day forecast	Planning	Large gap vs last week	Founder	Decide priorities

Email snippet: the “missed promise-to-pay” follow-up

Subject: Quick follow-up on payment date for invoice 2481

Hi Sam,

Thanks again for confirming payment was scheduled for 24 November. We have not seen it land yet.

Could you confirm the updated payment date?

If anything is blocking payment (PO, portal step, or an invoice query), tell us what it is and we’ll help resolve it today.

Invoice 2481: $12,900
Pay link / portal link: [link]

Thanks,
BSB AR Team (on behalf of Your Company)

Short. Factual. Easy to answer.

Common pitfalls (and how to avoid them)

• Pitfall: talking about “AR” instead of specific invoices.
  Fix: make every discussion invoice-led with owners and dates.
• Pitfall: treating disputes as “collections problems”.
  Fix: assign disputes to the team that can resolve the cause.
• Pitfall: letting portal work sit in a queue.
  Fix: surface portal/PO blockers early and track them like tickets.
• Pitfall: chasing harder instead of chasing smarter.
  Fix: improve reply handling and blocker removal first.

What your team can do this week

• Create four reply tags: late / dispute / missing PO / portal.
• Add a “promise-to-pay date” field and track hits/misses.
• Define a one-business-day reply SLA for AR threads.
• Decide where blockers get posted (Slack/Teams channel) and who owns each type.
• Ship a one-page weekly report with actions.

Next step

If you want this weekly review to run without eating your time, we can handle the day-to-day.

• If you want a lightweight, done-for-you cadence and reporting, see Lite AR Essentials on services.
• If you want full triage, blocker pushing, and weekly reporting rhythms, look at Managed AR Ops.
• If vendor portals and onboarding slow you down, AR + Portals & Onboarding is built for that.

If you are ready to talk, Get in touch via contact.

---

Compliance & clarity: This article shares general operational guidance. It is not legal, tax, or accounting advice. Examples are illustrative and do not include private client data.