Budget Planning 2027: What the Group Template Doesn't Ask Your German Subsidiary

It usually arrives in the second week of September. An email from group finance, a spreadsheet attached, a deadline in the subject line. Twelve months by cost centre, growth rates pre-filled, a currency that isn't the one your ledger runs in, and a set of line items that don't quite exist in your books.

Three weeks to complete it. Then a review call, then a revision, then a second revision after the group consolidates everything and discovers the total doesn't reach the number the board wants.

Most German entities treat this as an administrative exercise: fill in the boxes, defend the numbers once, move on. That is a mistake — not because the template is unimportant, but because the plan you send back in October is the number you will be measured against for the whole of the following year. Every variance conversation, every hiring approval, every request for capital expenditure runs off it.

In short: a group budget template is built for consolidation, not for local reality. It arrives in the group chart of accounts, in group currency, with growth assumptions set centrally, and it does not ask the questions only the local team can answer. The three failure points are consistent: a mapping gap between the local ledger and the template structure, planning assumptions that are imported without being challenged, and a set of German cost effects — collectively agreed wage increases, social security ceilings that are not yet published when the budget is due, statutory notice periods — that no central model contains. The fix is not a better spreadsheet. It is deciding, before you start filling anything in, which numbers you own and which ones the group owns, and writing that down.

What the group template actually asks for

A consolidation-driven planning template is designed backwards from the group income statement. It needs every entity to deliver the same line items, in the same structure, at the same level of granularity, so the numbers can be added up without manual intervention. That design goal is legitimate, and it explains almost everything that feels wrong about the file when you open it.

What the group template typically demands:

• Revenue split by group product or service hierarchy, not by how you actually sell
• Cost by group cost-centre structure, not your local one
• Headcount in full-time equivalents, usually with a central salary inflation percentage already applied
• Monthly phasing, often with a default seasonality curve you're expected to override
• Intercompany balances that must match the counterparty's plan exactly
• Everything in group currency, translated at a rate set centrally

What it almost never asks: what changed in your market, which customer is at risk, what your local wage agreement will actually cost, and whether the growth rate in cell C14 is achievable with the people you have.

The template collects what the group needs to consolidate. It does not collect what the local entity needs to steer.

Why budget planning takes three months, and what that actually costs

Published benchmarks put the standard planning cycle at around three months from template distribution to approved plan, with finance teams caught between accuracy and hitting the date. In practice that means the process starts in September and finishes in December, running straight into year-end close.

For a large group with a dedicated planning team, three months is manageable. For a German entity where the same one or two people handle the monthly close, the tax advisor relationship, the group reporting pack and now the budget, it is not. Something gives, and it is almost always the same thing: the local analysis. The boxes get filled, the totals reconcile, the file goes back on time — and nobody has asked whether the plan is right.

This is worth being blunt about, because it is where most of the value is lost. The cost of a rushed budget planning cycle is not the hours. It is spending twelve months explaining variances against a number nobody believed in October.

The chart of accounts gap: your ledger is not their template

This is the most common technical problem and the most under-estimated one. Your books run on a German standard chart of accounts — in most cases one of the two common frameworks covered in our comparison of SKR03 and SKR04. The group template runs on a group account structure designed for consolidated reporting. These are not the same shape, and the mapping between them is rarely one-to-one.

Typical symptoms:

• A single group line item corresponds to six local accounts, so any split is a judgement call
• Local accounts that have no group equivalent get dumped into "other", where they become invisible and unexplainable later
• Personnel cost is structured differently — employer social contributions sit in one place locally and another in the group model
• The mapping is maintained in a separate spreadsheet by one person, and it is not the same mapping used for the monthly reporting pack

That last point is the expensive one. If the budget mapping and the actuals mapping differ even slightly, every monthly variance report for the next year contains noise that isn't real. People stop trusting the numbers, and then stop reading them. Getting the mapping right once — and using the same one for plan and actuals — is the single highest-return hour of the entire planning cycle. The same discipline that makes a management reporting pack credible applies here, and for the same reason.

Planning assumptions: whose numbers are these?

Every planning template arrives with assumptions already embedded. Salary inflation of a certain percentage. A market growth rate. An exchange rate. A cost-reduction target. These are usually set centrally and applied uniformly across all entities.

Some of them are legitimately group decisions — the exchange rate, the cost of capital, group-wide strategic targets. Others are local realities that a central model cannot know. The problem is that both categories arrive in the same file, formatted identically, and it is not obvious which is which.

The single most useful thing you can do before filling in a number is to split the planning assumptions into two lists:

Write this list down and send it with the plan. It takes an hour and it changes the nature of every review call that follows: instead of defending a total, you are explaining a structure. That is a much stronger position.

One German specific worth flagging early, because it catches groups out every year: employer social security contributions are calculated against ceilings that are adjusted annually, and the figures for the coming year are frequently not confirmed when the budget is due. Building the plan on the current year's ceilings without saying so creates a personnel cost variance in January that looks like a planning error and isn't one. Note the assumption in writing at the time you make it.

Group template on your desk and nobody with time to actually think about it?

A free 20-minute assessment call is enough to work out which numbers you should be pushing back on before the file goes back. No preparation needed on your side.

Forecast accuracy: what a 10 to 15 percent deviation actually costs

Industry benchmarks put the average deviation between plan and actual result at roughly 10 to 15 percent across many sectors, and materially higher in volatile markets. That number deserves a moment's thought, because most people read it as a technical statistic rather than as a business fact.

A 12 percent deviation on a plan means that in practice you did not know, twelve months out, what one euro in eight was going to do. That is not a failure of skill — it is the honest condition of planning under uncertainty. The failure is treating a single-point plan as if it were a commitment, and then spending the year explaining why reality disagreed with it.

The practical response is not to chase precision. It is to change what you deliver:

• Plan the year, forecast the quarter. The annual plan sets direction. A rolling forecast, updated quarterly, is what you actually steer with. Improving forecast accuracy comes from updating more often, not from planning harder in September.
• Give the group a range where a range is honest. A base case plus a downside on the two or three drivers that actually move the result is more useful than a single number carried to two decimal places.
• Name the drivers, not the outcome. "Revenue depends on whether these four contracts renew" is information. "Revenue is 14.2 million" is not.
• Connect the plan to cash. A profit plan that has never been converted into a liquidity view is half a plan. Our guide to the 13-week cash flow forecast covers the short-horizon version; the annual plan should reconcile to it at least at the quarterly level.

This matters more than usual for the coming year. Forecasts for the German economy in 2027 sit in a narrow and unenthusiastic band — research institutes broadly in the range of 1.0 to 1.6 percent, the federal government planning around 1.4 percent, and the Handelsblatt Research Institute notably lower at 0.9 percent. Expectations have been revised downward rather than upward. That is a picture of fragile stabilisation, not recovery, and a plan built on a single confident growth number is planning against the weight of the evidence.

Where HGB and the group plan quietly disagree

The group plan is built on group accounting policy. Your statutory books are prepared under German commercial law. Those two frameworks measure some things differently, and if the plan ignores the difference, the local result will not behave the way the plan says it should.

The recurring areas are the familiar ones — provisions and accruals are treated more conservatively under HGB, capitalisation thresholds differ, and some items recognised in one framework are not recognised in the other. Our comparison of HGB and IFRS for German subsidiaries covers the mechanics; the planning consequence is simpler and often overlooked: you are frequently planning two different results at once.

If the group plan is the only plan that exists, then the local statutory result for the year is effectively unplanned — which becomes a problem when the managing director has to sign off on statements, when a bank asks what the local equity ratio will look like, or when a dividend decision depends on a distributable result nobody modelled. It does not require a second full budget. It requires knowing the two or three bridging items and carrying them explicitly.

Planning 2027 in a German subsidiary: what only the local team can see

Here is the argument for taking this seriously rather than treating it as form-filling. The group has better data than you on almost everything: market size, competitor moves, group cost of capital, portfolio strategy. There is exactly one category where the local entity has information the centre structurally cannot have, and that is the ground truth of the local business.

For a German subsidiary planning 2027, that category includes:

• Which customer relationships are genuinely secure and which are being quietly re-tendered
• What the local labour market actually costs right now for the roles you need
• Which supplier contracts renew next year and what the counterparty is likely to ask for
• Whether the receivables book contains a name that should worry you
• How long a hire actually takes from approval to productive, in your city, for your function
• Which regulatory or reporting change lands next year and what it will consume in effort

Sentiment among German small and mid-sized companies has improved for four consecutive readings, but the underlying balance remains negative — conditions are getting less bad rather than good. In that environment, a plan whose value comes from the local knowledge in it is worth considerably more than a plan whose value comes from arriving on time.

The spreadsheet risk nobody prices in

Almost all of this happens in spreadsheets, and the research on that is not comfortable reading. Published studies have found that a large majority of business spreadsheets — figures around 88 percent are commonly cited — contain errors of some kind. Separately, a PwC study found 47 percent of companies reporting collaboration problems with spreadsheet-based processes: version conflicts, files circulated by email, changes that overwrite each other.

Germany is not well positioned here. Bitkom research has put the share of companies with fully digitalised finance processes at around 38 percent in Germany, against over 60 percent in the Netherlands and Denmark. In a planning cycle involving a dozen contributors, four revision rounds and a mapping table maintained by hand, that gap turns into real risk.

The honest answer for a mid-sized entity is usually not to buy planning software in the middle of September. It is to reduce the surface area:

• One file is the master. Everything else is an input, clearly labelled as such.
• One person owns the mapping between the local ledger and the template, and it is documented, not remembered.
• No manual re-typing between the actuals export and the plan file — pull the base data straight from the system. If the underlying DATEV setup is clean, this is a five-minute export rather than an afternoon.
• Every hard-coded number gets a comment explaining where it came from. Future you, in March, will need it.
• Check the totals against last year's actuals before sending. Most catastrophic planning errors are order-of-magnitude errors that a five-minute sanity check would have caught.

A working sequence for the next six weeks

If the template is already on your desk, this is a realistic order of operations:

1. Week 1 — Read the template, not the cells. Understand what the group is actually trying to consolidate, and identify every line where your books don't map cleanly. Write the mapping down.
2. Week 1 — Split the assumptions. Group-owned versus locally-owned, using the table above. This is the document that protects you later.
3. Week 2 — Build the personnel plan first. It's usually the largest controllable cost, it has the longest lead times, and it's where local knowledge matters most. Names, start dates, notice periods, contractual increases.
4. Week 3 — Revenue by customer or contract, not by growth percentage. Bottom-up, then compare against the group's top-down target and quantify the gap explicitly rather than smoothing it away.
5. Week 4 — Build the downside. Two or three drivers, one adverse scenario. Half a day of work, and the single item most likely to get read at group level.
6. Week 5 — Bridge to the statutory view and to cash. What does this plan mean for the local result and for liquidity through the year?
7. Week 6 — Submit with a one-page cover note. Assumptions owned locally, the top-down gap, the downside case, and the three risks you want on record. This page is what makes the plan defensible in month seven.

Note what is not on this list: perfecting the monthly phasing of minor cost lines. It absorbs enormous time and changes nothing.

Planning cycle underway and the local view keeps losing to the deadline?

In a free 20-minute assessment call we go through your template, where the mapping is likely to break, and which assumptions are worth challenging before submission. Or get in touch directly.

Where an interim controller fits in

Planning season is a capacity problem with a hard edge. The work is finite, it lands on top of a team that is already fully loaded, and it collides with year-end. That combination is close to the definition of an interim controller mandate: a defined scope, a fixed window, and a deliverable that has to be right the first time.

In practice the work is building the mapping properly, running the bottom-up revenue and personnel models, producing the downside case, bridging the plan to the statutory view and to cash, and writing the cover note. Six to eight weeks, part-time, ending when the plan is approved. And because it runs directly into year-end close preparation, the same person can carry the calendar through December rather than handing it over at the worst possible moment.

The alternative — the existing team absorbing it alongside everything else — is what produces the plan that was submitted on time and believed by nobody.

Conclusion

The group template will get filled in either way. The question is whether what goes back is a set of numbers that satisfied the deadline, or a plan the local entity can actually stand behind for twelve months.

The difference is not effort — it's sequence. Fix the mapping before you enter a number. Separate the assumptions you own from the ones you were given, and put that in writing. Build the personnel and revenue detail from the bottom up. Add a downside case. Send a cover note that says what you assumed and where you disagree.

None of that requires new software or more people. It requires deciding, in the first week, that the plan is yours rather than the group's — because in twelve months of variance meetings, everyone will treat it as yours regardless.

This article shares general information from a controlling and process perspective. It is not tax or legal advice — for your company's specific obligations, including the treatment of statutory provisions and payroll-related contributions, please speak to your tax advisor.

Frequently asked questions (FAQ)

When does budget planning for the next financial year normally start in a German subsidiary?

Most international groups distribute the planning template in September, with submission due in October and approval in November or December. Published benchmarks put the full cycle at around three months. For an entity on a calendar financial year, that means planning runs straight into year-end close preparation, which is why capacity is usually the binding constraint rather than analysis.

Why doesn't the group template match our local chart of accounts?

Because it is designed for consolidation, not for local steering. The template collects the line items the group needs to add up across all entities, in the group account structure. A German entity's books run on a local standard chart of accounts, so a mapping layer is always required. The critical point is to use the same mapping for the plan and for monthly actuals — otherwise every variance report for the following year contains noise that isn't real.

How accurate should a budget be?

Industry benchmarks put the average deviation between plan and actual at roughly 10 to 15 percent, and higher in volatile markets. Chasing greater precision in the annual plan generally does not pay. Updating a rolling forecast quarterly, and presenting a range on the two or three drivers that actually move the result, improves steering quality far more than additional planning effort in September.

Which planning assumptions should a German entity push back on?

Anything that depends on local facts the group model cannot see: personnel cost increases driven by local wage agreements and contracts, employer social security cost, hiring lead times and notice periods, local supplier and energy contract renewals, and customer-specific revenue and bad debt risk. Group-set items such as the exchange rate, cost of capital and strategic direction are normally accepted as given. Documenting which is which, and sending that list with the plan, is the cheapest protection available.

Do we need a separate plan for the German statutory result?

Not a second full budget, but the bridge should exist. Group accounting policy and German commercial law measure provisions, accruals and some capitalisation items differently, so the group plan does not describe the local statutory result. If that result matters — for a bank covenant, a dividend decision or the managing director's sign-off — the two or three bridging items should be identified and carried explicitly rather than discovered at year-end.

About the author

Mert Ilter is an interim financial controller based in Hamburg, Germany. He works with small and mid-sized German companies, startups, and German subsidiaries of international groups — building and repairing finance functions, accelerating month-end and year-end close, and preparing companies for funding rounds, due diligence and lender conversations. He works solo: no agency, no layer in between, onboarding within days.

Areas of focus: interim controlling · finance function build-up for German entities · HGB and IFRS reporting · DATEV · month-end and year-end close · liquidity planning and covenant reporting · investor-grade reporting.

Connect on LinkedIn · Book a free 20-minute assessment call · Contact