There's a particular Monday morning ritual in a lot of finance departments: an AR manager spends two hours pulling together a weekly report that the CFO glances at for 45 seconds and asks the same three questions they always ask. The report answers about 12 of those questions in exhaustive detail. None of those 12 happen to be the three they actually want answered.
Bad AR reporting wastes time twice: once to produce it, and once to interpret it. And the interpretation problem is usually worse — a 12-tab workbook with aging detail, historical comparison, customer-level breakdowns, and collection activity logs requires active work to extract the signal. Most CFOs don't do that work. They ask the questions they could have answered in one page.
This piece is about what that one-page report looks like, how to build it, and why most AR reporting goes in the wrong direction.
What CFOs Are Actually Asking About AR
After working with AR operations at a handful of mid-market companies, the CFO's real AR questions compress to four:
- Are we getting worse or better? Trend, not point-in-time. DSO this week versus last week versus four weeks ago. They want to see the direction, not the absolute number.
- What's the risk concentration? How much of the overdue balance sits in the top 10 accounts? If the top three accounts resolved their balances, what would DSO look like? Concentration risk is the question they're really asking when they scan the aging report.
- Is the team working it? Collection activity — how many outreach contacts were made, what percentage of overdue invoices have been touched in the last 7 days. This isn't a micromanagement signal; it's a process health check.
- What needs my attention? Not everything — just the specific accounts or situations that require a CFO decision or a leadership relationship call. Flag 2–3 items at most. More than that and nothing gets attention.
If your weekly AR report answers these four questions clearly, it will get read. If it answers 40 other questions and buries these four, it will get skimmed and then set aside.
The One-Page AR Summary Format
Here's the structure that works. This is a single page — not a dashboard with 14 panels, not a spreadsheet workbook. One page, in email or PDF format, delivered Monday morning before the weekly finance review.
Section 1: DSO Trend (4-Week View)
A simple 4-number row: DSO this week / DSO 4 weeks ago / DSO 12 weeks ago / industry benchmark. That's it. No chart required — the four numbers tell the story. If DSO is 54 / 58 / 61 / 48, you know it's improving but still above benchmark. If it's 62 / 58 / 54 / 48, you have a problem trend that's accelerating.
Include the total accounts receivable balance this week and the week-over-week change. "$4.2M AR balance, +$180K from last week" tells the CFO immediately whether overall exposure is growing or shrinking.
Section 2: Aging Bucket Change
Three rows: Current (0–30 days), 30–60, 60–90, 90+. For each bucket: balance this week and change from last week. The change is the key signal. A growing 60–90 bucket while the 30–60 bucket is shrinking means your 30–60 bucket problem from last month is now aging through. A growing 30–60 bucket while current is shrinking means new invoices are hitting their terms and starting to age.
Color-code the changes: green for improvement (bucket shrinking), amber for flat, red for growth. CFOs read this in 10 seconds.
Section 3: Top 10 At-Risk Accounts
A table with: customer name / outstanding balance / days overdue / last contact / status (In follow-up / Escalated / Dispute / Silent). Ten rows maximum. Sort by outstanding balance, not by days overdue — the CFO's risk instinct is amount-weighted, not time-weighted.
Mark any account that the CFO should know about — a relationship account, a large balance that has gone unexpectedly silent, an account in dispute where the CFO may want to involve sales leadership. Keep flags to 1–2 items per week. If everything is flagged, nothing is.
Section 4: Collection Activity Summary
Two numbers: outreach contacts sent this week (emails + calls) and the percentage of overdue invoices touched in the last 7 days. If you had 320 invoices overdue and 280 received some form of contact, your coverage rate is 87.5%. This tells the CFO that the AR process is running — invoices aren't sitting unworked.
Add collection rate for the rolling 30-day window: amount collected as a percentage of amount invoiced. For most mid-market B2B companies with net-30 terms, a healthy collection rate is 88–94%. Below 85% is a signal worth investigating.
Why the Detailed Backup Matters (Even If the CFO Doesn't Read It)
We're not saying throw away the detailed aging report. The detail is necessary — for audit trails, for dispute documentation, for AR manager planning. The argument is about what gets presented in the weekly CFO touchpoint. Summary goes to leadership; detail stays with AR operations.
The one-pager should reference where the backup detail lives: "Full aging detail in [shared drive/system]. Customer-level contact log available on request." This signals that the data exists — the CFO just isn't being asked to wade through it every Monday.
The Real Problem With Most AR Reports
Most AR reports are built to satisfy a request that was made once, years ago, and then never revised. A CFO asked for "a full aging breakdown" in 2021, and the team has been delivering 14-column spreadsheets every week since then — even though the CFO's real question, week after week, is "are we getting worse or better, and what do I need to act on?"
There's also an organizational dynamic at play. Detailed reports protect the person producing them. If something goes wrong, they can point to the fact that the information was in the report on week 12. A more summary-level report shifts accountability toward decisions made, not data delivered. That can feel uncomfortable. But it's closer to the actual value of the AR reporting function.
The CFO's job is to make decisions with limited time and imperfect information. Your job in AR reporting is to give them the highest-signal input you can in the time they've allocated. That's one page, once a week, with the four things they actually need to know.
We're not saying detail is useless — it's essential for the AR team running operations. But the report that goes to the CFO every Monday morning should earn its read time by being genuinely scannable in 90 seconds. If it isn't, it's being skimmed anyway, and you're spending hours producing something that's providing less value than you think.