Your 13-Week Cash Flow AR Curve Is Probably Lying to You

The Problem: Templates That Assume 100% of A/R Pays on Schedule

Walk into almost any small Chapter 11 or Subchapter V case and ask for the debtor's 13-week cash flow model. Nine times out of ten you will find an A/R collection schedule that looks like this: 98% of outstanding invoices collect, 50% in week 1, 30% in week 2, 10% in week 3, 10% in week 4. Clean, symmetrical, auditable. It also happens to be a fantasy.

In my experience working with UST analysts across Subchapter V cases, the most frequent fatal error in debtor-prepared cash flow forecasts is the overestimation of A/R collections — and the UST's own reporting machinery is built to surface it. Official Form 425C Part 7 requires the debtor to compare projected cash receipts and disbursements to actuals every month, and 11 U.S.C. § 1112(b)(4)(F) makes failure to comply with filing and reporting requirements cause for dismissal or conversion.² The reason the overestimation happens at all is structural rather than malicious: almost every off-the-shelf 13-week cash flow template ships with a default collection curve keyed to contract terms rather than to customer behavior. When a Subchapter V debtor opens one of those templates the day of the first-day hearing, the model's hard-coded optimism rides along into the filed budget, the DIP covenant tests, and the MOR variance reports — and then reality shows up.

Reality, in 2025, looks like this: across 240 surveyed US businesses, 52% of B2B invoices are paid on time, 43% are paid late, and 5% are written off as bad debt, with average US payment terms now running 46 days from invoicing rather than the 30 that off-the-shelf templates assume.¹ That pattern is echoed across industries in The Hackett Group's 2025 US Working Capital Survey, which found aggregate DSO deteriorating for the second straight year across the 1,000 largest nonfinancial US public companies — with pharmaceuticals at 70 days and semiconductors averaging 57 days in 2024.³ Distressed DIP debtors fare even worse because customers read the first-day filings, flag the debtor in their AP system, and push the payment to the back of the batch.⁴

If the collection curve in your model does not reflect any of that, the question is not whether the forecast will miss — it is which week it will miss first, and how the UST will score that miss.

The Data Every Calibration Should Start From

A defensible curve starts by letting three independent sources pressure-test each other.

Atradius 2025 US Payment Practices Barometer. The most recent Atradius benchmark of US B2B payment behavior reports 52% on-time, 43% overdue, and 5% written off as bad debt, with average US payment terms of 46 days from invoicing across 240 surveyed businesses.¹ This is the single most useful public number for anchoring a collection curve because it is the empirical distribution of reality, not the contractual terms. Any curve that implies better than 95% collection on a normal SMB A/R book should carry a written justification for beating the Atradius benchmark by 200 basis points or more.

Hackett Group 2025 US Working Capital Survey. Hackett's latest survey, which analyzes 2024 data from 1,000 of the largest nonfinancial US public companies, reports aggregate DSO deteriorating for the second straight year, with pharmaceuticals at 70 days, semiconductors averaging 57 days (a 17% jump — the steepest in 13 years), and accounts receivable now representing 35% of total excess working capital across the Global 1000.³ Hackett's sample is larger than a typical Subchapter V debtor, but the cross-industry pattern is the point: even among the best-run public companies, effective DSO commonly runs well above Net 30. A 13-week forecast that implies a 30-day DSO on a services debtor is silently assuming the business is a performance outlier before it files for bankruptcy.

Troutman Pepper Creditor's Rights Toolkit on DIP Financing. Distressed debtors face an additional known slow-pay pattern on top of the Atradius and Hackett baselines. The Troutman Pepper toolkit — written for vendors deciding whether to resume doing business with a Chapter 11 customer — explicitly advises creditors that the existence of DIP financing is "no guaranty of payment" and that they should continue to examine the post-petition creditworthiness of the debtor just as they would outside of bankruptcy.⁴ That creditor-side discipline, in aggregate across thousands of AP departments, is precisely what produces the DIP slow-pay overlay: customers read the first-day filings, flag the debtor, and push the payment to the back of the batch. Atradius surveys a non-distressed population, so the DIP overlay is always worse than the public benchmark.

Taken together, these three sources tell you that your 13-week model should bias conservative, that a reasonable curve for a services debtor has a collection peak 3 to 5 weeks out, and that "contract terms" belongs nowhere near your assumptions tab.

The 3-Step Calibration Method

Here is the method I used in a recent Subchapter V engagement with a commercial cleaning debtor. The numbers below are illustrative and anonymized, but the ratios and method are exactly what the model contains.

Step 1: Pull trailing 13-week collections from the bank register

Before touching the assumptions tab, open the bank register and tag every customer deposit in the trailing 13 weeks. Sum them. Divide by 13. That is your empirical weekly run-rate, and it is the single most important anchor in the entire model.

For the commercial cleaning debtor, trailing 13-week customer collections averaged roughly $100,000 per week. That is the number the model's steady-state inflow had to reconcile to, within a reasonable margin, after all the bucket and curve assumptions finished rolling forward.

Two process notes. First, use actual bank receipts, not the ledger's cash receipts journal — ledger entries can include journal transfers, write-offs, and reclassifications that inflate the apparent inflow. Second, exclude inter-bank transfers aggressively. A debtor with multiple operating accounts can easily show $100,000 a month of inter-bank noise that has nothing to do with customer cash. I'll return to that trap in a separate post; for now, just tag and exclude.

Step 2: Compute empirical DSO from the A/R book

Empirical DSO is simply:

Empirical DSO = (Accounts Receivable at snapshot) / (Monthly revenue / 30)

For the commercial cleaning debtor, A/R at snapshot was approximately $500,000 and trailing 3-month monthly revenue was approximately $430,000. That produced an empirical DSO of:

$500,000 / ($430,000 / 30) = ~35 days

35 days is Net 30 plus 5 days of slippage — a perfectly healthy collection cycle for a commercial services business. That single number told me two things at once: the business was collecting roughly on schedule, and any curve I built had to produce a weighted-average collection lag of about 35 days, not 15 and not 60.

A warning: the denominator here is monthly revenue, not annualized revenue divided by 12. Use the most recent trailing 3 months so the number reflects current customer behavior rather than year-ago conditions. And watch out for the A/R Aging total-row double-count trap — if you pull the A/R aging summary directly from QuickBooks or Xero and sum the bucket columns while also including the "Total" row, you will double your A/R balance and calculate a fictitious 70-day DSO that will panic everyone in the room. I learned that one the hard way.

Step 3: Design curve shape to match empirical DSO

Once you have the bank register run-rate and the empirical DSO, building the curve is almost mechanical. You solve for a weekly distribution whose weighted average lag matches the empirical DSO and whose output, when multiplied by the A/R aging balance, reconciles back to the trailing 13-week run-rate.

For the commercial cleaning debtor, I landed on these bucket-level assumptions:

A few things to notice about this table. The CURRENT bucket peaks at W2, not W1. That is because the average invoice in the CURRENT bucket is about 15 days old at the snapshot date, so the remaining lag to payment is roughly two weeks rather than zero — which is why W2 carries the most weight and W3 still takes a meaningful share. Front-loading 50% of the CURRENT bucket into W1 (the template default) would imply that every customer pays on the day the forecast starts, which is not what real customers do.

The 94% collectibility on the CURRENT bucket is not an accident either. It is Atradius's 5% bad-debt reality plus a 1% margin for the Chapter 11 filing effect. You can defend that 94% in open court; you cannot defend 98%.

The Before-and-After

Here is what the model's projected weekly inflow looked like before and after the calibration pass, using the commercial cleaning debtor's A/R snapshot and new-sales forecast. The "before" curve is the off-the-shelf template default; the "after" curve is the calibrated Option A curve above combined with a Net-30-realistic new sales curve (peak at W4) and a 5% Revenue Conservatism Factor.

The punchline is that the total 13-week inflow barely changed — but the shape changed completely. The template's 98%/50-30-10-10 default front-loads 28% more cash into week 1 than the bank register can support. That is precisely the kind of timing distortion that blows up DIP covenant tests in weeks 2 through 5, when the model says the cash should be there and the bank account says it is not.

The Chapter 11 Conservatism Layer

Calibrating the curve gets you a defensible forecast of the debtor's actual behavior. That is necessary but not sufficient for a Chapter 11 case. The UST and DIP lender are not scoring accuracy in isolation — they are scoring whether the debtor has built a buffer for the downside risk that the filing itself creates.

I handle that with what I call a Revenue Conservatism Factor: a single cell in the assumptions tab, set at 0.95, that the new-sales forecast formulas multiply through. The effect is a 5% haircut on the filed PL Budget's monthly revenue line, applied only inside the 13-week model, never in the filed budget itself. Three reasons this matters:

1. It anchors the model to trailing actuals, not to plan. On the commercial cleaning debtor, the filed Budget shows monthly revenue of approximately $445,000 growing to $465,000. The trailing 3-month actual was $430,000. Applying the 0.95 factor pulls the forecast's top line down to $423,000, which is below the trailing actual and comfortably defensible.

2. It gives the court a single adjustable lever. When the UST or DIP lender asks "what if the business softens another five points," you change one cell and regenerate the forecast. No formulas to rewrite, no assumptions to relitigate.

3. It protects the filed PL Budget. The filed Budget is a court document. You do not want to be modifying it every time the 13-week model gets an update. Applying haircuts through a formula reference in the cash flow model keeps the filed Budget clean and immutable.

When I deposed a budget once as lender-side restructuring advisor, the thing that made me trust it was not that the numbers were aggressive or conservative — it was that the CFO could point to a single cell and say "this is the adjustable knob, here is why it is set to 0.95, and here is what happens if you believe it should be 0.90." Conservatism as a dial, not as a hope.

Common Pitfalls to Avoid

Three pitfalls kill more 13-week cash flow models than any other:

1. The A/R Aging total-row double-count. Almost every accounting system produces an A/R aging summary with a "Total" row at the bottom of the bucket columns. If you paste that report into your model and sum the bucket columns while keeping the total row, you will double your total A/R and silently calculate a 70-day DSO on a 35-day book. I nearly told a CFO client to slash their revenue projection 25% before I caught this one. It is worth its own blog post — and it is coming.

2. MOR "Total Receipts" ≠ customer collections. The MOR's Part 2 receipts line includes inter-bank transfers, undeposited funds, and miscellaneous other income. On a debtor with multiple operating accounts, inter-bank noise can easily reach $100,000 per month. Do not compare your 13-week CF customer inflow line to the MOR receipts total directly; isolate the customer A/R portion first with SUMIFS or similar.

3. Modeling new sales at 100% collectibility. New sales have the same 5% Atradius bad-debt rate as any other A/R. A curve that collects 100% of every dollar billed post-petition is silently adding 5% to your forecast that reality will claw back. Separate the collectibility multiplier (0.95) from the timing curve so each is individually defensible.

Your Next Step

Open the last 13-week cash flow model you worked on. Compute three numbers:

1. Trailing 13-week bank-register customer collections (sum, divide by 13).
2. Empirical DSO = A/R at snapshot ÷ (trailing 3-month revenue ÷ 30).
3. Implied weekly run-rate from your model's current A/R collection curve.

If number 3 is more than ±10% different from number 1, your curve is not calibrated. If number 2 is less than 30 days and your curve peaks in week 1, you are front-loading. This exercise takes about 20 minutes and is the single highest-leverage sanity check on any Chapter 11 liquidity forecast.

For a calibrated Chapter 11 13-week cash flow template with the bucket assumptions, new-sales curve, and Revenue Conservatism Factor already built in — including a README walking through the calibration method above — use the email form below and the advanced edition will be in your inbox in a minute. Prefer a direct hand-off? Send a request to [email protected].