FY2027 Starts in 7 Weeks. Have You Actually Begun Your Budget — or Just Thought About It?
The Federal Budget lands tomorrow night. Every finance publication in the country will have a take on it by Wednesday morning. But here's the thing — while everyone is watching Canberra, most finance teams are already behind on something they have far more control over: their own organisation's budget for FY2027.
1 July is seven weeks away. If your budget process hasn't meaningfully started — not a shared folder with last year's file in it, but an actual structured process with a timeline, stakeholder engagement, and a set of agreed assumptions — you're going to feel it in August.
This post isn't about the mechanics of building a budget. It's about the process failure that happens before a single number gets entered, and what finance teams typically get wrong at this stage of the year.
Why Seven Weeks Isn't as Long as It Sounds
On paper, seven weeks looks reasonable. In practice, you're working with somewhere between 20 and 30 usable business days — accounting for the Queen's Birthday long weekend in June, the inevitable diary conflicts as people lock in end-of-year leave, and the fact that the people whose input you need most (operations managers, department heads, CEOs) are simultaneously trying to close out FY2026.
Finance teams that treat budget season as something that starts when the calendar says so typically end up producing a document that operations doesn't trust, leadership uses selectively, and the board receives with polite indifference. It's not a resource problem. It's a timing and sequencing problem.
The organisations that produce budgets that actually get used — that become genuine management tools rather than compliance documents — start the design work well before the numbers phase. The numbers are the easy part. The hard part is the architecture that sits behind them.
First, Let's Retire One Misconception: Earlier Is Not Always Better
There's a particular type of executive who, upon realising the organisation's budget process has historically been rushed, concludes that the solution is to start much earlier. January, perhaps. Maybe February. Get ahead of it. Give finance plenty of time.
This is a well-intentioned idea that doesn't work in practice — and it's worth being direct about why, because the finance team is usually the one who pays the price for it.
A budget built in January or February is missing the final quarter of the current financial year entirely. At that point you have results to roughly November or December — none of the year-end trading data, none of the final payroll runs, none of the accumulated variance picture that tells you whether this year's assumptions held up. That final quarter is often where the most instructive performance data sits: the Christmas trading result for retailers, the year-end activity volumes for NDIS and aged care providers, the accruals that reveal whether cost assumptions were right.
Building next year's forecast without that information doesn't make the process more rigorous — it makes it less accurate. Finance teams that start in January typically produce numbers they'll need to revise significantly once full-year actuals come in, which means doing the work twice under pressure.
January, if it belongs anywhere in the finance calendar, is reforecast territory — a time to update the current year's projections based on how the first half actually landed, not to start building next year's budget from scratch. Conflating the two creates confusion about what the process is for. And for most SMEs, even a formal mid-year reforecast is optional — an annual budget with disciplined monthly variance review is entirely sufficient. If your organisation isn't running quarterly or monthly reforecasts, starting the annual budget in January isn't sophisticated planning. It's an expensive way to produce a number you'll redo in May anyway.
May is the right starting point for most organisations. By May, you have ten or eleven months of actuals — enough to see how the current year is landing and build next year's assumptions on real data rather than projections-of-projections. The seven weeks between early May and 30 June is a tight window, but it's the right window. The answer to a rushed budget isn't an earlier start. It's a better-designed process. If there's pressure to begin in February, the more useful conversation is about why the process takes so long — which is almost always about stakeholder engagement and template design, not calendar position.
Three Ways Budget Season Typically Goes Wrong
1. Building it in a silo. Finance produces the budget, sends it to department heads for review, gets back numbers that don't reflect operational reality, reconciles them under time pressure, and delivers something that satisfies the process without informing the decisions. The root cause is almost always that operations wasn't involved early enough — before the template went out, not after it came back.
The most effective budget processes treat department heads as co-authors of their own line items, not respondents to a form. That requires a different kind of conversation, earlier in the timeline. Finance's role shifts from data collector to facilitator — asking the right questions about what's changing in each area, what's being planned, what assumptions the team is making about activity levels and staffing. That intelligence then shapes the numbers, rather than the other way around.
2. Using last year's budget as the base without interrogating it. This is the finance equivalent of accepting default settings. Last year's budget was built under last year's assumptions. If the operating environment has shifted — new award rates, different funding levels, a change in service mix, a strategic priority that didn't exist twelve months ago — a straight-line roll-forward embeds the wrong assumptions at the foundation level.
Zero-based budgeting for every line item is neither practical nor useful. But selectively challenging the major cost categories — particularly labour, which typically represents 60–80% of operating costs in service-sector organisations — is essential. If the wage bill is going up materially due to award changes or Payday Super, the budget needs to reflect it explicitly, not absorb it as a variance in October.
3. Treating the annual budget as the final answer. A budget built in May and June, for a full financial year starting in July, is making assumptions about twelve months of operating conditions. Those assumptions will be wrong in ways that are impossible to predict right now. The organisations that manage this well don't treat the annual budget as a fixed document — they treat it as the first iteration of a rolling process, with quarterly or monthly reforecast cycles built into the operating rhythm from the start.
That distinction matters because it changes what the budget is for. If it's a static compliance document, you measure against it in arrears and explain variances. If it's a live planning tool, you use it to make decisions in real time — adjusting resource allocation, flagging risk early, and presenting leadership with options rather than post-mortems.
|
7 weeks
Until FY2027 begins — and effective usable working time is considerably less once long weekends, leave, and end-of-year close are factored in.
|
60–80%
Typical labour cost as a share of operating expenses in service-sector organisations — the number that most needs active scrutiny in any budget build.
|
What a Budget Process Actually Needs at This Stage
Not a template. Not a timeline sent via email. What's missing in most budget processes at this point in the year is a shared understanding — between finance and the rest of the organisation — of what the budget is actually trying to achieve. Is it a revenue target? A cost control framework? A workforce planning tool? For many organisations the honest answer is "all of the above," which is why the document ends up satisfying none of them particularly well.
The most useful thing finance can do in the next two weeks isn't to build the spreadsheet. It's to have the conversations that establish the assumptions it'll be built on — what's changing in the operating environment, where the known cost pressures sit, and what leadership needs to be able to see in the finished product. Those conversations require finance to show up as a thinking partner rather than a data-entry coordinator — and that posture is harder to adopt under time pressure, which is exactly why starting late makes the whole process worse, not just slower.
The Federal Budget Context Matters — But It's Not Your Starting Point
Tomorrow night's budget will confirm funding levels, reform timelines, and cost parameters that will affect every organisation in the NFP, NDIS, aged care, and childcare sectors. Those numbers matter and they'll need to flow into your internal budget assumptions where relevant.
But waiting for the budget papers before starting your own process is a mistake. The structural decisions — who owns what, what the reforecast cadence will be, what assumptions are being made about wages and activity levels — don't require confirmed government numbers. They require internal alignment, and that's entirely within your control right now.
Get the process architecture right this week. Update the assumptions next week when the papers are out. That sequencing gives you a far better chance of delivering something useful by the end of June.
Where to Start This Week
If the budget process hasn't formally begun, the most useful thing to do right now is not to open a spreadsheet. It's to answer three questions:
What are the top three cost drivers that are different this year versus last year? Award increases, new headcount, capital expenditure, compliance costs from regulatory changes — identify these specifically and make sure they're in the building assumptions from day one, not discovered during the review process.
Who needs to be involved, and when? Map the stakeholders whose input the budget requires, and get time in their diaries before the end of May. The people you need to talk to are also the people who are hardest to schedule in June.
What does leadership actually need to see? A good management reporting pack at budget time does more than present a P&L projection. It tells a story about the year ahead — what the organisation is planning to achieve, what the key risks are, and what decisions leadership needs to make. Understanding what that story should look like before you build the numbers makes the whole process more purposeful.
Seven weeks. The window is open. The question is whether you use it well.
Need a Finance Function That's Ready for FY2027?
PFL works with NFP, NDIS, and SME finance teams on budget process design, management reporting pack structure, and the financial planning frameworks that turn budgets into genuine decision-making tools. If FY2027 planning is sitting at the top of your list and the process isn't moving fast enough, let's talk.
Get in Touch with PFL →
Comments
Post a Comment