Skip to main content
2,200+ contractors in the research universe benchmarked. Do you know your gross profit per labor hour? See where you stand →
Level
Cash Flow

Stop Tracking DSO. Track 30-Day Collection Rate Instead.

Sam YangEx-CFO across trades, SaaS & services · $2.5B in total PE/banking transactions · Stanford MBA
Updated October 8, 2026·Originally published April 29, 2026·9 minute read
Share

Invoice-cohort operating method

DSO and an invoice-level 30-day collection rate answer different questions. Test a clearly defined cohort measure alongside due dates and aging. A 55% versus 80% scenario is illustrative, not published Level percentiles.

Practitioner method, not a measured Level 30-day benchmark

9 minute readCash Flow

If this is you

Every fractional CFO post you read tells you to track Days Sales Outstanding. Your accountant talks about it. Your industry trade publication runs articles on it. So you started tracking it. And it didn't change anything. There's a reason.

I'm going to make a contrarian argument: DSO alone is insufficient for an operating decision. Its aggregate balance/revenue ratio can hide differences in customer mix, contract terms and invoice age. It remains useful alongside a clearly defined cohort measure.

The metric that actually moves cash flow is 30-day collection rate. It is a matured historical cohort outcome, not a forecast. Invoice-level due dates, partial receipts, disputes and customer mix help explain what action is appropriate now.

Here's the case.

What DSO actually measures

Days Sales Outstanding = (Average AR / Daily Revenue). It estimates a balance-to-sales interval, not the actual mean of invoice payment days; that requires invoice-level receipt dates.

A $10M contractor with $1.65M in AR has a DSO of 60 days. Sounds simple. Here are the problems with using it as your operational metric:

1. It's an average. A DSO of 60 days could mean: every customer pays at exactly 60 days (boring but consistent). Or: 80% of equal-dollar invoices pay at 30 days and 20% at 180 days: the weighted average is 60 days, with a long tail hidden by that average. The average hides the distribution.

2. It's lagging. DSO calculated at month-end of June reflects collection patterns from invoices issued in April-May. By the time you see DSO get worse, the underlying problem is two months old. Your operational lever, what you do this week, isn't reflected for 60+ days.

3. It moves slowly. A bad month doesn't show up dramatically in DSO because it's averaged with all the other months. So the alarm bell rings late, if at all.

4. It doesn't tell you what to do. "DSO went from 55 to 62 days", what's your action? Vague.

5. It's gameable. Owners (and their accounting teams) have hundreds of ways to make DSO look better than it is, selective writing-off, timing of invoices, including/excluding retainage. Most people aren't manipulating it intentionally; they're just choosing definitions that make their number look better.

What 30-day collection rate measures

30-day collection rate = dollars received and applied within 30 days of each invoice's issue date, divided by original billed dollars in the issue-month cohort. Include partial receipts, retain invoice IDs and issue/receipt dates, and disclose treatment of credits, write-offs and retainage. Do not count cash applied after an invoice's individual deadline.

In a fictional April cohort with $1M billed, assume $720K is applied within each invoice's individual 30-day deadline. The matured cohort rate is 72%. May 31 is only a convenient reporting cutoff after all April deadlines; it is not a common deadline for every invoice.

Here's why this metric is operationally superior:

1. It's specific. Each month's invoices have their own collection rate. April's collection rate. May's collection rate. You can see whether April was a bad cohort or a one-off.

2. It has a fixed observation window. April invoices mature individually 30 days after issue; by May 31 all are mature. Early-month and late-month invoices do not receive unequal collection windows.

3. It's actionable. If April's 30-day collection rate is 60% and May's is 75%, something specific changed. Maybe you tightened up dunning. Maybe a particular customer slowed down. The change identifies a cohort to investigate, not its cause.

4. It surfaces the slow-pay tail. A matured 60% rate means 40% was not collected within its invoice deadline. Some may have arrived later or still be within longer contractual terms. Check current balances and due dates before chasing. DSO blends this in with everything else.

5. Reconcile the applied cash. Receipt date alone does not establish amount or invoice application. Preserve partial receipts, credits, reversals and each deadline so the numerator and denominator can be reproduced.

Free benchmark review

See how your cash cycle benchmarks.

Start with a free conversation about your priorities. With agreed access to the relevant records, we compare your numbers with applicable benchmarks and identify what to review first.

What good looks like

I don't have published-research data on 30-day collection rate the way I do for total collection rate (which we've benchmarked across 464 contractors, per Level Index published metric (see its eligible sample and definition)). But the following are illustrative practitioner planning scenarios, not statistical percentiles or customer-type outcome claims:

  • Illustrative high scenario: 75-85% collected within 30 days, not a measured quartile. Collection timing may differ with cards, terms and billing methods; match those before comparing.
  • Illustrative middle scenario: 55%, not a measured median. 55% of dollars collected in 30 days, 45% taking longer.
  • Illustrative low scenario: under 40%; more than 60% was not collected within 30 days, not a measured quartile. Longer terms, retainage, disputes or process issues are possible explanations, not established causes.

In a fictional $5M annual-billing scenario, moving 55% to 80% within 30 days shifts $1.25M of annual billings earlier; it is not extra annual cash or profit. At an assumed 30-day acceleration in a steady, evenly billed business, $1.25M x 30/365 is about $103K of one-time working-capital release. Actual balances, receipt dates and seasonality determine the result.

How to track it weekly

The mechanic:

  1. Pull a list of every invoice issued in calendar month X. From your accounting software (QuickBooks, Sage, whatever).
  2. At each invoice's issue date plus 30 days, sum applied receipts. Include partial payments and retain later receipts separately.
  3. Calculate: dollars applied within each invoice's individual 30-day window, divided by original billed dollars in the issue-month cohort.
  4. Report maturation weekly. In early May, only early-April invoices have completed 30 days. Show matured billed dollars and matured rate separately from immature invoices; do not label an incomplete April cohort a final 30-day outcome.

Verify that the accounting export exposes stable invoice IDs, issue dates, partial receipt applications, credits and current balances. Some systems need multiple reports and reconciliation before this measure can be reproduced.

What changes when you track this

When the metric shifts from DSO to 30-day collection rate, the operational behavior changes:

  • AR review meetings happen weekly, not monthly. Because the metric updates weekly, the conversation does too.
  • The escalation cadence tightens. Track approaching contractual due dates while the cohort matures; an approved follow-up cadence can address missing documentation or disputes without treating every 30-day balance as delinquent.
  • You spot bad cohorts faster. Once both invoice cohorts have matured, investigate a supported difference. An individually fixed30-day window does not identify a June-end problem before the later invoices have reached their deadlines.
  • You see the tail. The 30-day collection rate forces you to look at what didn't collect, not just at what did. Investigate whether the uncollected tail reflects terms, disputes, later receipts or credit loss; the metric alone does not establish bad debt.

When DSO still matters

DSO isn't useless. It matters in three places:

  1. External reporting. Banks, lenders, and PE buyers will ask for DSO. They're using it as a comparable across companies. Have it ready.

  2. Long-term trend tracking. DSO over 12 months tells you whether your collection efficiency is structurally improving or degrading. Useful at the annual review level.

  3. Comparative benchmarking. When you want to know how you stack up against industry peers, public DSO data is widely available. 30-day collection rate is harder to benchmark because it's not a standardized metric.

So track DSO for those purposes. Just don't use it as your operational cash flow KPI. Use 30-day collection rate.

Make the switch

Concrete action this week:

  1. Pull last month's invoices from your accounting system.
  2. Retain issue dates and receipt applications, then identify invoices whose individual 30-day windows have matured.
  3. Calculate the 30-day collection rate.
  4. Set a weekly recurring report that tracks the prior month's rate as it matures.
  5. Stop using DSO in your weekly cash flow conversations. Replace it with 30-day collection rate.

A 55% or 85% result is a starting point, not a verdict on collection quality. Compare like contract terms and customer mix, inspect uncollected balances and reconcile cash before deciding what to change.

Calculate your collection gap in 2 minutes, see what your number looks like compared to Level's 2,200+ contractor research universe. The tool's published collection metric is cash collected/billed, median 85.1%, n=464 with an unpublished window; it is not this 30-day measure. Or book a free 30-min audit and we'll connect to your books and rebuild your collections cadence around the metric that actually moves cash.

Share

Get the next one

Want next week's benchmark in your inbox?

One email a week. Real numbers from 2,200+ contractors in the research universe. No fluff. Unsubscribe anytime.

Sam Yang

About the author

Sam Yang

Founder & CEO

Founder of Level, the always-on finance team for contractors, service businesses, and ecommerce brands. Ex-CFO across trades, SaaS, and service businesses. 4 years as Director of Growth Product at BuildOps, building financial tooling used by 1,000+ commercial contractors. Four years in PE and investment banking rolling up and acquiring service businesses, $2.5B in total transactions including M&A and IPOs. Stanford MBA, Brown undergrad. The Level founding team's analysis of 2,200+ contractors ($13.25B in job revenue) across operating, private-equity, and CFO roles anchors the Level Index benchmark research.

LinkedIn

See how your cash cycle benchmarks.

Start with a free conversation about your priorities. With agreed access to the relevant records, we compare your numbers with applicable benchmarks and identify what to review first.

2,200+ businesses benchmarked$13.25B in revenue analyzedWeekly action cadence

No credit card. Start with a 15-min call. We only follow up if we can actually help.

No commitment. Real numbers, not generic advice.