When the Group Moves Accounting to a Shared Service Center — What Stays Behind in Germany

It's a familiar sequence. The group decides to consolidate finance operations. Bookkeeping for the German entity moves to a shared service center — often in Poland, the Czech Republic or Portugal. The local accounting roles are closed. On the project plan, the German entity is marked green: migrated, done.

Then the first year-end arrives, and a set of questions surfaces that nobody assigned to anyone: who reconciles the local books to German commercial law, who works with the tax advisor, who owns the disclosure filing, who answers when the tax office asks a question about a transaction booked 1,200 kilometres away.

The transactional work moved. The German obligations did not. This guide is about the gap between those two facts.

In short: a shared service center takes over transaction processing — general ledger, payables, receivables, payments, intercompany postings. It does not take over the German entity's statutory obligations, which remain with the entity and its managing director regardless of where the bookkeeping physically happens. Three things routinely get missed: relocating the books abroad generally requires prior approval from the German tax office, the SSC rarely has German GAAP judgement at the level the local statements require, and intercompany services flowing from the group without being properly charged create a transfer pricing exposure that surfaces years later. What has to stay behind is not a bookkeeping team — it's a thin controlling layer that owns the local close, the tax advisor interface and the statutory calendar.

What actually moves to the shared service center — and what doesn't

A finance shared service center typically absorbs the high-volume, rules-based work: general ledger posting, accounts payable and receivable, fixed asset accounting, payment processing, dunning, and intercompany postings. These are the right things to centralise — they're repeatable, they scale, and they benefit from standardisation.

What does not travel well is anything requiring local judgement or local relationships. In practice, that means:

• Measurement decisions under German commercial law — provisions, accruals, valuation questions
• The relationship with the German tax advisor and the annual statements they prepare
• The statutory calendar: preparation deadlines, disclosure filing, tax deadlines
• Responding to a tax audit with knowledge of what actually happened in the business
• Explaining local numbers to group in a way that survives questions

Research on SSC transitions makes the same point in general terms: country-by-country exceptions — different statutory formats, tax calendars, filing portals and documentation requirements — are exactly where centralisation stalls and manual workarounds appear. Germany is one of the more demanding versions of that problem.

The approval most groups don't know they need from the tax office

Here is the fact that surprises people, and it's worth checking before a transition rather than after: relocating electronic bookkeeping abroad is generally subject to prior approval by the German tax office, under the rules governing where books may be kept (§ 146 of the German fiscal code). It is not automatic, and it is not a formality that project managers can assume was handled by someone else.

Companies that migrate first and ask later can find themselves in an awkward position during an audit — with the underlying accounting records held in a jurisdiction the tax authority never approved. Whether approval is required in your specific structure, and what conditions attach to it, is a question for your tax advisor; the point for a finance lead is simply to make sure someone asks it before the migration date, not during the first audit.

The books can move. The obligation to keep them properly does not move with them.

Responsibility stays in Germany

This is the structural fact everything else follows from. German commercial law places the duty of proper bookkeeping on the entity itself — and by extension on its managing director. Outsourcing the execution to a shared service center, whether inside the group or to an external provider, does not transfer that duty. The managing director of the German subsidiary remains answerable for whether the books comply with HGB requirements, regardless of who physically makes the entries.

The practical consequence is uncomfortable: after a transition, the person legally responsible for the accounting often has the least direct visibility into it. Closing that visibility gap is not optional — it's the core of what the retained function has to do.

The qualification gap nobody plans for

Shared service centers are built for throughput. They are staffed and measured for processing volume with consistency and speed, and they do that well. What they typically do not have is someone at the seniority level German statutory accounting requires — the equivalent of a senior qualified accountant who can make and defend a judgement call on a provision under German commercial law.

This is not a criticism of SSC staff. It's a design characteristic: a center serving eight countries cannot maintain deep statutory expertise in each one. But it means that after the transition, the German entity's books are being produced by people who are excellent at posting transactions and structurally not positioned to make German-specific accounting judgements. Someone has to supply that layer, and by default nobody does.

Has your German entity been through an SSC transition — and is anyone actually owning the local close?

A free 20-minute assessment call is enough to map what moved, what didn't, and where the gaps sit. No preparation needed on your side.

What stays behind: the retained finance function

The concept has a name in transformation projects — the retained finance function, sometimes just "the retained organisation": everything that does not move to the center. Most transition plans document it thoroughly for the group. Far fewer document it properly at the level of a single mid-sized country entity like a German subsidiary.

The realistic size of that retained layer for a mid-sized German subsidiary is not a department. It's a fraction of one experienced person — which is precisely why it so often ends up assigned to nobody: too small to justify a hire, too important to leave unowned.

The tax advisor interface becomes more important, not less

A common assumption before a transition is that centralising the bookkeeping reduces the need for local advisory support. In practice the opposite tends to happen. The tax advisor still prepares and files the statutory statements, but now receives data from a team that doesn't know the entity's history, can't explain unusual transactions, and works to a group chart of accounts rather than the local one.

Established practice in cross-border setups is to maintain advisors both at the SSC location and locally, with deliberate knowledge transfer about the entity's specifics. That works — but somebody on the company side has to organise it, and that somebody is exactly the role the transition eliminated. The same alignment discipline covered in our DATEV setup guide applies here with more force: if the group chart of accounts and the advisor's environment don't map cleanly, every month generates queries across three parties instead of two.

Intercompany: the exposure that shows up two years later

Centralisation creates a specific and under-appreciated risk. When a group provides services to subsidiaries through shared structures, those services sometimes flow informally — delivered without a clear contractual basis and without being properly charged.

That is a transfer pricing problem waiting for an audit. As covered in our guide to transfer pricing documentation, German rules now require the documentation to be produced within 30 days of a request — and the request is effectively triggered when an audit is announced. A German entity that receives shared accounting services from the group needs those services documented, priced and reconciled like any other intercompany transaction. After an SSC transition, that documentation frequently doesn't exist, because everyone treated the move as an internal reorganisation rather than a service relationship.

The first year-end after the transition

The year-end following a migration is where the design either holds or doesn't. Typical failure pattern: the SSC delivers a trial balance on schedule; nobody in Germany can explain three of the larger balances; the tax advisor's questions go into a queue in another country; and the preparation deadline — three months after year end for medium and large corporations — arrives with the statements unfinished.

The fix is unglamorous and entirely preventable: run the year-end preparation as a defined process with named local ownership, starting in the autumn rather than in January. Reconcile early, agree the intercompany balances with counterparties while everyone still has capacity, and make sure someone in Germany can answer "what is this balance and why" without escalating to another time zone.

Where an interim controller fits in

This is one of the cleanest cases for an interim controller mandate there is. The work is well-defined and finite: map what actually moved and what didn't, document the retained function so it's owned rather than assumed, rebuild the tax advisor interface, get the local-to-group reconciliation working, and run the first year-end so the design is proven before it's relied on.

It is also the exact shape of a gap that permanent hiring handles badly. A German subsidiary post-transition doesn't need a full-time accountant — the transactions are gone. It needs a fraction of an experienced controller who understands both German statutory requirements and group reporting, for a defined period, until the retained function runs itself. That's the same finance function build-out logic applied to a subtraction rather than an addition.

Migration finished, but the German close still feels fragile?

In a free 20-minute assessment call we go through what the retained function actually needs to cover, and what's currently unassigned — before the year-end tests it. Or get in touch directly.

Conclusion

Shared service centers do what they're designed to do: process transactions consistently and at scale. The mistake is treating the migration as complete when the transactions stop being processed locally, because the German entity's obligations never moved in the first place.

What stays behind is small and easy to overlook — statutory judgement, the advisor relationship, the local calendar, the bridge between local books and group reporting. Assign it deliberately and the SSC model works exactly as intended. Leave it unassigned and it will assign itself, at the worst possible moment, to whoever is holding the statements in March.

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 whether tax office approval is required to keep books abroad, please speak to your tax advisor.

Frequently asked questions (FAQ)

What does a finance shared service center typically take over?

High-volume, rules-based work: general ledger posting, accounts payable and receivable, fixed asset accounting, payment processing, dunning and intercompany postings. Work requiring local statutory judgement or local relationships generally stays with the entity.

Can a German company move its bookkeeping abroad?

Generally yes, but relocating electronic bookkeeping abroad is subject to prior approval by the German tax office under the rules governing where books may be kept. It is not automatic. Whether approval is required in your structure and what conditions apply is a question for your tax advisor — ideally before the migration, not during an audit.

Who is responsible for the accounting after a transition to an SSC?

The German entity and its managing director. German commercial law places the duty of proper bookkeeping on the entity itself, and outsourcing execution — whether within the group or externally — does not transfer that responsibility.

What is a retained finance function?

Everything that does not move to the shared service center: statutory measurement decisions, the tax advisor interface, annual statements and disclosure, tax audit response, and the reconciliation between local books and group reporting. For a mid-sized German subsidiary this is typically a fraction of one experienced person, not a department.

Why does an SSC transition create transfer pricing risk?

Because shared services provided by the group to a subsidiary are intercompany transactions and need to be documented, priced and charged accordingly. After a migration this documentation frequently doesn't exist, since the move was treated as an internal reorganisation rather than a service relationship — and German rules require transfer pricing documentation to be produced within 30 days of a request.

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