Your Month-End Close Is a Post-Mortem

It’s the sixth of the month and your finance head is sitting across from you with the closing numbers. He’s done a good job — it’s all there, clean and reconciled. Margins on the big run for that auto-component customer came in four points below where you’d quoted. Receivables aged badly; nearly forty lakhs slipped past ninety days. One steady customer ordered noticeably less than usual. You study it all carefully. You ask good questions. And somewhere in the middle of that meeting, the quiet truth settles in: there is nothing — not one single thing — you can do about any of it. It already happened. The month is over. You’re holding a beautiful, detailed report about a fire that finished burning a week ago.

I want to talk about that meeting, because almost every manufacturing CEO I know treats it as the financial heartbeat of the business. And it is the single most backward-looking hour of your month.

A careful examination of something already dead

A post-mortem is exactly that — a meticulous study of something that is already gone. The pathologist is brilliant, thorough, precise. He tells you exactly what went wrong and why. He saves no one, because by the time the body is on his table, saving was never on the table.

Your month-end close is the same act, performed on your business. By the time those numbers reach you, every event inside them is history. The slipped margin happened across thirty days you can’t get back. The customer who drifted started drifting weeks before the report noticed. The receivables aged one quiet day at a time while everyone was looking elsewhere. The close tells you all of it — accurately, completely, and far too late to matter.

This isn’t a criticism of your finance team. They’re doing the job exactly as it’s designed to be done. The problem is the design. A monthly close is built to look backward. That’s its entire nature. Asking it to help you prevent something is like asking a rear-view mirror to tell you what’s coming around the next bend. It was never made for that, and no amount of polishing the mirror will change it.

Why the cost hides in the timing

Here’s the part that genuinely costs you money, and it’s not the size of any single problem — it’s when you find out.

Take the forty lakhs in aged receivables. The trouble didn’t appear fully formed on the last day of the month. It built. One invoice slid to forty-five days. Then a second customer started stretching to sixty. Then the first one quietly crossed ninety. Every one of those moments was a day on which you could have picked up the phone, had an easy conversation, and pulled the payment back in before it hardened into a problem. Caught on day three, a slow payment is a friendly call. Caught on day ninety, in a report, it’s a write-off you’re now negotiating to recover a fraction of.

Same money. Completely different outcome. The only variable that changed was how late you found out. That’s the hidden tax of running on month-end: you don’t just lose to the problem, you lose to the delay in seeing it. And because the delay is invisible — it never shows up as a line item — most owners never realise it’s the single most expensive thing in the building.

The problems don’t wait for your calendar

There’s a deeper issue with letting the calendar decide when you learn things. Your business doesn’t run in months. It runs continuously — by the hour, by the order, by the shipment. But you’ve agreed, by habit, to only really look at it once every thirty days. So for twenty-nine days out of thirty, the business is moving and changing and occasionally heading off a cliff, and the person responsible for all of it has agreed not to check until the month is done.

Think about what that means for the things that build quietly. A job whose material costs are creeping past the quoted price — by the time the close reveals the eroded margin, you’ve already shipped it and lost the money. A customer cooling off — by the time the smaller order shows in the monthly sales summary, he’s already halfway out the door. A vendor whose slipping reliability is about to stall a production line — the close will explain the lost output beautifully, next month, after the line has already sat idle.

In every one of these, the information existed while there was still time. The month-end didn’t create the knowledge. It just delayed it until it was useless.

The opposite of a post-mortem

So what’s the alternative? Not a faster close. Not a weekly close instead of a monthly one — that just gives you the same post-mortem four times as often. The opposite of a post-mortem isn’t a quicker autopsy. It’s knowing the patient is in trouble while you can still do something about it.

Picture the same forty lakhs, handled differently. On the day an invoice quietly crosses the line you care about, you simply get told — that afternoon, while it’s small. On the day a steady customer’s order comes in lighter than his pattern, and you notice his last payment was slow too, you get a quiet heads-up that this account is starting to slip. On the day a job’s costs cross the price you quoted, someone flags it before the next batch ships, not after. None of this requires a bigger finance team or a heroic controller. It requires only that the business be watched continuously instead of once a month — and that you be told the moment something needs you, rather than the moment it’s already over.

That’s the whole shift. Not better reporting on the past. Early warning about the present. The close becomes what it should always have been — a record you keep for the books — instead of the one moment a month you find out how the business is actually doing.

Keep the close. Stop running on it.

I’m not telling you to abandon the month-end. It has its place; you need a clean set of books and a formal record. Keep it. Just stop treating it as the heartbeat of how you run the company, because a heartbeat you only check once a month isn’t really telling you whether the patient is alive — it’s telling you whether they were alive last month.

The factory runs in real time. The cash moves in real time. The customers drift in real time. The only thing running on a thirty-day delay is you — and only because that’s how it’s always been done, not because it has to be. The owners who break that habit don’t work harder or hire more. They simply arrange to find out while it still matters. And once you’ve run a business that way, even for a quarter, the idea of waiting until the sixth of next month to learn what happened starts to feel exactly like what it is: studying the body, long after you could have saved it.

Part of Manufacturing Week. Start with the overview — The Factory Runs in Real Time. Why Doesn’t Your Information? — or go deeper on the data problem in Seven Systems, Zero Answers.