Month-End Close and FP&A: When Are Actuals Ready?

Accounting says the books are closed.

FP&A opens the P&L and immediately finds three things it wants to ask about.

A large contractor expense moved departments. Revenue is lower than the operating data suggested. One cost center looks suspiciously good.

Nobody did anything wrong.

The books can be closed and still not be ready for the next finance conversation.

The handoff from Accounting to FP&A is one of those small operating processes that tells you a lot about a finance function.

Accounting and FP&A are looking at the same month differently

Accounting is trying to produce complete, accurate financial records for the period.

FP&A is trying to understand what those records say about the business and what they change about the outlook.

Those jobs overlap, but they are not the same.

A perfectly legitimate accounting entry can create a forecast question. A classification that is immaterial to the financial statements can matter quite a bit to a department leader trying to understand spend.

The trouble starts when each team assumes the other one sees the month the same way.

I like FP&A involved before the final numbers arrive

Waiting for the final trial balance before looking at the month wastes information Finance already has.

Before close, FP&A usually knows where the business changed.

Sales missed a large deal. Marketing launched a campaign early. A hiring class slipped. A vendor contract started. A customer churned.

Those operating facts give Accounting useful places to look, especially around accruals, classifications and unusual movement.

They also let FP&A begin forming questions before the close clock hits zero.

This does not mean FP&A should take over Accounting’s close. It means the teams should not behave like neighboring countries exchanging files at the border.

The handoff needs a small amount of context

I do not need Accounting to write the management commentary.

I do want material unusual items identified when possible.

Large true-ups. Reclasses. One-time expenses. Timing items. New accounting treatment that makes a comparison look strange. Anything FP&A is likely to spend an hour rediscovering.

A short close note can save a surprisingly long variance meeting.

It also improves variance analysis, because Finance can separate accounting movement from operating movement before explaining the result to management.

Reconciliation is where trust gets built

The fastest way to make a forecast meeting unpleasant is to discover that Finance and Accounting are using different actuals.

I like a clear source of truth and a repeatable reconciliation between the financial statements and whatever planning system or model FP&A uses.

Not because every system must contain identical detail.

Because somebody should be able to explain the bridge.

If the management P&L excludes certain items, document it. If departments are remapped for planning, make the mapping explicit. If the forecast uses operational revenue before the ledger is final, know when it gets replaced.

“These numbers are basically the same” has caused a lot of unnecessary meetings.

A faster close is not automatically a better close

Finance teams like to measure close days.

Fair enough. A 15-day close makes forward-looking analysis difficult.

But speed is not the only useful measure.

If Accounting closes on day four and FP&A spends days five through eight untangling unexplained movements, the business did not really get useful financial information on day four.

I care about the time from period end to decision-ready actuals.

That includes enough reconciliation and context for Finance to move from “what is this?” to “what does this mean?”

The forecast should learn something from close

Month-end is not just a reporting event.

It is where assumptions meet evidence.

Maybe payroll came in below plan because hiring slipped. Maybe cloud costs are scaling differently than the model assumed. Maybe collections are slowing. Maybe a recurring expense was classified as a one-time surprise for the third month in a row.

Those observations belong in the next forecast.

A forecasting process that simply loads actuals and rolls the calendar forward misses the most useful part of close.

The month just told you something.

The post-close conversation can be very short

I like a brief review between Accounting and FP&A after the dust settles.

What created friction? Which entries surprised FP&A? What did Accounting have to chase? Which recurring issue should be fixed before next month?

Not a committee. Not a 14-slide retrospective.

Ten useful minutes can be enough.

The point is to stop accepting the same avoidable confusion as a permanent feature of month-end.

Clean actuals are part of forecasting infrastructure

FP&A sometimes talks about actuals as though they simply arrive.

They do not.

They are produced through accounting processes, judgments, reconciliations and deadlines. The quality of that work shapes everything Finance does next.

That is also why I think the line between accounting support and FP&A matters operationally even when the roles stay distinct.

The forecast does not begin in the forecast model.

It begins with whether Finance trusts the number in the actual column.