The $150K MOR Reconciliation Trap: Why Your Numbers Look Like They're Shrinking

The Panic Moment

The pattern repeats itself so consistently across small Chapter 11 cases that I can almost predict the week it will happen. The debtor files its first MOR. The UST signs off. The CEO reviews the filed budget. Three weeks later, the fractional CFO delivers the updated 13-week cash flow, and the projected inflow line is 30–40% below the last MOR's reported receipts.

The CEO's first thought is that the business is collapsing. The CEO's second thought is that the 13-week cash flow must be wrong. The CEO's third thought is to call debtor's counsel in a panic. By the time all three thoughts have finished, someone is drafting an email to the UST explaining an apparent collapse that does not exist.

Here is the number from a real (fully anonymized) Subchapter V engagement I worked on recently: the debtor's March MOR reported approximately $608,000 in Total Receipts, and the updated 13-week cash flow model projected approximately $361,000 of customer inflow for April. On a naive comparison, that looks like a $247,000 month-over-month contraction — roughly 40% down. Terrifying number to put in front of the CEO of a Subchapter V debtor in an active restructuring.

Except the business was not down 40%. It was down roughly 19%, which is the difference between the filed-Plan expected April revenue and the trailing-three-month run rate, and that 19% was already baked into both the filed budget and the 13-week model. The apparent $247K contraction was a reconciliation artifact. And it was a reconciliation artifact that appears in almost every small Chapter 11 debtor's first-MOR vs. cash-flow comparison.

Understanding where the extra $161,000 came from — and how to isolate it — is the subject of this post.

What Actually Lives Inside the MOR's "Total Receipts" Line

Official Form 425C's Part 2 asks the debtor to report Total Receipts for the period. That number, as filed, is the gross cash that hit the debtor-in-possession bank accounts during the month. It is a clean number in the sense that it ties to the bank statements. It is a dirty number in the sense that it aggregates three categories that have nothing to do with each other from a forecasting standpoint.

The three categories inside a typical MOR Total Receipts line are:

Category 1: Customer A/R collections. The real cash from the real customers for real invoices. This is the only component that the 13-week cash flow forecast is actually trying to model. If you want to know whether the business is collecting on schedule, this is the number you need.

Category 2: Inter-bank transfers between operating accounts. Every Chapter 11 debtor with more than one operating account is moving cash between accounts routinely — from a DIP operating account to a payroll account, from a payroll account back to the operating account after a run, from a deposit account to a concentration account for bill payment. These transfers hit the MOR receipts line every time a dollar lands in any DIP-monitored account, even though they are the same dollar that left another DIP-monitored account a few hours earlier. On a debtor with 3–5 operating accounts, inter-bank transfer noise can easily reach $120,000–$180,000 per month.

Category 3: Undeposited funds, refunds, and miscellaneous other cash. Refunds from vendors, interest on DIP operating accounts, insurance rebates, a one-time sale of scrap or surplus equipment, credit card refunds, timing-driven undeposited funds clearing through the bank — all of the one-off receipts that are real cash but do not reflect ongoing customer collections.

Only Category 1 belongs in the comparison to the 13-week cash flow forecast. Categories 2 and 3 need to be identified and separated before any variance analysis is meaningful.

The Numbers From the Real Case

Here is the actual reconciliation I ran on the commercial cleaning debtor I mentioned above, rounded and anonymized:

Compare the Category 1 number ($447,000) to the April 13-week cash flow projection ($361,000). That is a month-over-month decline of about $86,000, or 19%. The April projection was already on the CFO's desk and already in the filed plan assumptions — the 19% reflects expected seasonality and a known timing shift where two large customers batch-pay monthly in the last week rather than mid-month.

In other words, the "40% collapse" story is wrong by $161,000. The actual story is "customer cash down 19% in a predictable timing pattern, rest is transfer noise". That second story is the one the CEO needs to hear, the UST needs to see in the next MOR narrative, and the DIP lender needs to read in the borrowing base certificate.

The SUMIFS That Isolates Customer A/R

The mechanical fix to prevent this panic is a simple SUMIFS formula that only sums the bank register rows that represent customer deposits. You build it once, copy it every month, and you never again compare a mixed number to a clean one.

Here is the logic:

Customer_A_R =
  SUMIFS(
    bank_register.Amount,
    bank_register.Account_Type, "Deposit",
    bank_register.Description, "NOT containing TRANSFER",
    bank_register.Description, "NOT containing REFUND",
    bank_register.Amount, ">0"
  )

In Excel, using a tagged bank register that includes a Type column (Deposit / Transfer / Other), the formula becomes:

=SUMIFS(amount_range, type_range, "Deposit", date_range, ">="&month_start, date_range, "<"&month_end_plus_one)

The prerequisite is that you have tagged your bank register. That is the one piece of setup that makes this reconciliation one-click rather than one-hour. When you import the monthly bank register into your reconciliation workbook, add a single Type column and mark each row as one of:

• Deposit — customer A/R collection
• Transfer — inter-bank transfer (identifiable by the paired matching amount in the source account)
• Other — refunds, interest, misc.
• Outflow — anything on the disbursement side

Inter-bank transfers are particularly easy to tag if you import all operating accounts into a single register: every transfer appears as a matched pair (one debit, one credit, same amount, same or adjacent date). A simple conditional formatting rule flags the pairs, and you mark them both as Transfer in 30 seconds.

Once the tagging is in place, the isolation formula runs instantly and the three-category breakdown above builds itself.

The 7-Step MOR Reconciliation Protocol

Here is the protocol I run every month on Subchapter V cases. It takes about 30 minutes after the first month's setup.

Step 1 — Export the full DIP bank register. Every DIP operating account, every payroll account, every concentration account. One monthly export per account.

Step 2 — Consolidate and tag. Merge the exports into one bank register. Add a Type column. Tag every row as Deposit, Transfer, Other, or Outflow. Inter-bank transfer pairs reveal themselves as matched amounts across accounts.

Step 3 — Isolate customer A/R. Run the SUMIFS against Type = "Deposit" for the month. That is your Category 1 number.

Step 4 — Identify transfers. Run the SUMIFS against Type = "Transfer". Sanity check: the sum of all transfer-tagged rows should be zero (every transfer in is matched by a transfer out within the DIP-monitored perimeter). If the sum is not zero, you have a transfer pair split across a month boundary or an incorrectly tagged row.

Step 5 — Identify undeposited funds and misc. Run the SUMIFS against Type = "Other". Sanity check: these should be explainable line by line. If you cannot explain a row in Category 3, it is probably a mis-tagged customer deposit — investigate before finalizing.

Step 6 — Compare Category 1 to the 13-week cash flow forecast. The apples-to-apples comparison is:

• Numerator: Category 1 (real customer A/R collections) for the month
• Denominator: 13-week cash flow forecast's "Existing A/R collections" + "New sales" lines, summed over the same calendar month

A variance of ±10% is normal timing. A variance of ±20% deserves a written note. A variance over 30% usually indicates either a customer payment change or a forecast calibration problem — go back to the AR curve.

Step 7 — Document the three-category breakdown in the MOR narrative. This is the strategic move. Instead of letting the UST or the creditors' committee ask why the MOR receipts total and the cash flow forecast do not tie, preempt the question in the variance narrative:

"March Total Receipts of $608,000 consist of $447,000 in customer A/R collections, $132,000 in inter-bank transfers between DIP operating accounts, and $29,000 in miscellaneous receipts. The 13-week cash flow forecast projects customer A/R collections only; comparing the forecast to Total Receipts overstates apparent inflow by approximately $161,000 per month due to transfer and other noise. Against customer A/R only, the March actual of $447,000 tracked to the 13-week forecast of $431,000, a favorable variance of $16,000 (3.7%)."

That paragraph does four things at once: it explains the apparent gap, demonstrates analytical rigor, shows the UST you are tracking the right number, and forestalls the panicked phone call from the CEO to counsel. Ninety seconds of writing, dozens of hours of downstream headache avoided.

The Court-Defense Angle

The three-category breakdown is more than an internal analytical convenience. It is a court-defensible narrative that can withstand cross-examination.

At a plan confirmation hearing, the debtor's witness — usually the CFO or the founder — will be asked whether the business is maintaining scale. If the only metric anyone is looking at is the MOR Total Receipts line, a witness answering "yes, we are steady at roughly $608K per month" will immediately walk into questions like "So why does your own cash flow forecast show April at $361K?" A CFO who has not separated the categories will stammer.

A CFO who has done the reconciliation answers differently: "Total Receipts on the MOR include inter-bank transfers between our three DIP operating accounts, which run approximately $132,000 per month and are the same dollars moving twice inside the estate. The business's actual customer A/R collections have been $438,000, $425,000, and $447,000 for January, February, and March respectively. Our April forecast of $361,000 reflects a known seasonal timing shift where two customers that normally pay in the middle of the month batch-pay in the first week of May, so approximately $75,000 of April's forecast shifts into May. Against a normalized monthly customer collection rate of roughly $435,000, the business is maintaining scale."

That is the testimony you want. It requires the three-category breakdown, the monthly normalization, and the timing-shift explanation — all of which live in the MOR reconciliation workbook.

The Bank Architecture That Makes This Easier

If you are at the very start of a Chapter 11 case and you have not yet set up DIP account architecture, a few structural choices now make the monthly reconciliation much easier later:

Minimize the number of DIP operating accounts. Every additional account is another source of inter-bank transfer noise. Unless there is a legitimate operational reason (payroll segregation is common and fine), one operating account is the cleanest setup.

Name accounts descriptively and consistently. "DIP Operating — BankCo 1234" beats "Main Checking" because you can search and tag by name. Consistency across export pulls makes SUMIFS formulas stable month over month.

Segregate customer A/R collections from transfers at the depository level if possible. Some debtors use a lockbox or a separate depository-only account that receives customer checks and then sweeps to the operating account. If the lockbox account is itself a DIP account, you can SUMIFS on "Deposit, Account = Lockbox" and the Category 1 number is computed without any tagging at all.

Keep one clean bank register workbook month over month. Do not create a new file every month. One file, one tab per month, one consolidated register, formulas copied forward. The marginal cost of each additional month is under ten minutes once the workbook exists.

Your Next Step

Pull the last MOR you filed. Pull the underlying DIP bank register for that month. Run steps 1 through 5 of the protocol above and compute your Category 1 (customer A/R) number. Compare it to the same month's "Existing A/R collections" line from your last 13-week cash flow forecast.

If the numbers reconcile within 10%, your MOR reporting is clean and you are free to write a simple variance narrative for the next filing. If they do not reconcile — in either direction — you have either a tagging issue, a transfer noise issue, or a forecast calibration issue. In all three cases, the 30-minute reconciliation pass will tell you exactly which.

For a pre-built MOR reconciliation workbook with the tagging schema, the SUMIFS formulas, and the three-category variance narrative template ready to drop into your filings — plus a 1-page PDF checklist as a companion — use the email form below and both files will be in your inbox in a minute. Prefer a direct hand-off? Send a request to [email protected].