A rule change that got surprisingly little attention has made life considerably harder for German subsidiaries of international groups: the deadline for producing transfer pricing documentation to the tax authorities has been halved from 60 days to 30, and it applies from financial year 2025 onward.
Thirty days sounds workable — until you consider what actually has to happen inside them. The documentation has to describe every cross-border transaction with the parent, sister and subsidiary companies: what was delivered, at what price, on what basis, benchmarked against what. If that information lives in five different systems, three spreadsheets and one colleague's memory, thirty days is not a deadline. It's a crisis.
This guide covers who is actually affected, what the documentation contains, what non-compliance costs — and the part nobody frames correctly: why the 30-day rule is a data problem long before it becomes a tax problem.
In short: since financial year 2025, German companies must produce transfer pricing documentation within 30 days of a request (previously 60), and it can now be requested at any time — automatically at the announcement of a tax audit, without a separate demand. A Local File is required once cross-border goods transactions exceed €6 million or services exceed €600,000 per year; a Master File applies above €100 million total revenue. Failure to produce it carries a penalty of 5–10% of the estimated income adjustment, with a €5,000 minimum, plus late-filing surcharges of at least €100 per day up to €1 million. The practical implication for finance: the documentation is written by your tax advisor, but it can only be written from data your finance function produces — and thirty days is not enough time to go looking for it.
What changed in transfer pricing documentation — and why it matters now
Transfer pricing documentation is the file that justifies the prices charged between related companies across borders — the German subsidiary buying goods from the parent, paying a management fee to headquarters, licensing a brand, or receiving a group service allocation. Tax authorities care because those prices move profit between countries.
Two things changed for financial year 2025 onward. First, the deadline for producing the documentation dropped from 60 days to 30 days. Second — and this is the part that catches finance teams out — the documentation can now be requested at any time, and is effectively triggered automatically when a tax audit is announced, without a separate explicit demand. The old rhythm, where a company had two months and a formal prompt to get organised, is gone.
The clock now starts when the audit is announced. Not when someone gets around to asking for the file.
The 30-day clock: what has to happen inside it
Thirty calendar days — not working days — to assemble, reconcile and hand over a defensible file covering every cross-border related-party transaction of the period. In a well-run finance function that's a document-retrieval exercise. In a typical one it means: identifying which intercompany transactions actually occurred, reconciling the German books against the group's records, finding the agreements that govern them, confirming which pricing method was applied, and producing the numbers that support it. Companies that have to reconstruct rather than retrieve routinely miss the deadline — and the penalty attaches to missing it, regardless of whether the underlying prices were correct all along.
Local File and Master File: the thresholds that decide if this applies to you
| Document | Required when | What it covers |
|---|---|---|
| Local File | Cross-border goods transactions with related parties exceed €6 million per year, or services exceed €600,000 per year | The German entity's own related-party transactions: what, with whom, at what price, on what basis |
| Master File | Total revenue exceeds €100 million | The group-wide picture: global structure, value chain, overall transfer pricing strategy |
| Below both thresholds | No formal file required | But you must still be able to demonstrate that prices between related parties are appropriate |
Two things worth underlining. The €600,000 services threshold is low — a management fee, an IT service allocation and a shared-services charge from headquarters add up faster than most subsidiaries expect, and services are where mid-sized groups most often cross the line without noticing. And being below the thresholds removes the formal file, not the obligation: the prices still have to be defensible if anyone asks.
Penalties: what non-compliance costs
The penalties are structured to make delay expensive rather than to punish honest error:
- Failure to produce usable documentation: 5–10% of the estimated income adjustment, with a minimum of €5,000 — so even a small adjustment carries a four-figure floor.
- Late submission: a surcharge of at least €100 per day of delay, up to a maximum of €1 million.
- The compounding effect: missing documentation weakens your position on the substantive question too. Without a defensible file, the authority is in a much stronger position to estimate an adjustment — and you are in a much weaker one to argue.
Note what triggers the exposure: not having the file ready in time. A company whose transfer prices were entirely correct, but whose documentation took forty-five days to assemble, is exposed anyway.
Why 30 days is a data problem, not a tax problem
This is the framing that matters, and it's the one most articles on this topic miss entirely.
Your tax advisor writes the documentation. They know the methods, the regulations, the defensible arguments — that is their expertise and it is not in question. But no advisor can write a file describing transactions they can't see. What they need is a complete, reconciled, retrievable picture of what actually flowed between the German entity and the rest of the group, backed by the agreements that govern it.
That picture is produced by the finance function, not the advisor. And in most German subsidiaries it isn't produced continuously — it's assembled in a panic, once, when someone asks. That's precisely why the halving of the deadline hurts: companies weren't using the old sixty days efficiently either, they were using them to find things. Cut the window in half and the underlying weakness becomes visible immediately.
The advisor can only document what your finance function can produce. Thirty days is enough to retrieve. It is not enough to reconstruct.
German subsidiaries: why this hits mid-sized groups hardest
Large groups usually have a transfer pricing function, a documented policy and a standing process. Small purely domestic companies aren't affected at all. The pressure lands squarely in the middle: German subsidiaries of international groups that are big enough to have substantial intercompany flows, but not big enough to have someone whose job is managing them.
The typical pattern: intercompany charges are booked correctly enough for the monthly close, the group has an agreed policy somewhere, and nobody in the German entity owns the connection between the two. It works — until the thirty-day clock starts. This is the same structural gap covered elsewhere on this blog around building the finance function for a German entity: the operational layer works, the documentation layer was never assigned to anyone.
The intercompany data checklist
What a finance function should be able to produce, at any time, without a search party — this is the practical core of readiness:
- A complete list of related-party transaction types — goods, services, management fees, licences, financing, cost allocations — with the annual volume of each, so you know which thresholds you're near.
- Intercompany accounts reconciled with counterparties, ideally monthly. If the German books and the parent's books disagree on what was charged, that gap has to be explained under time pressure.
- The agreements — intercompany contracts, service agreements, cost allocation keys — stored where finance can find them, not only in a legal folder at headquarters.
- The pricing basis actually applied, documented as it is used rather than reconstructed afterwards: which method, which margin, which cost base.
- Consistency between the local books and group reporting — the same transaction should tell the same story in both, which connects directly to the reconciliation between local and group accounting standards.
None of these is exotic. All of them are ordinary finance-function hygiene. And a company that has them can hand the tax advisor a complete package in days rather than weeks.
What your tax advisor needs from you — and what stays theirs
A clean division of labour makes the thirty days workable:
| Your tax advisor | Your finance function |
|---|---|
| Chooses and defends the pricing methods | Produces the transaction data and volumes |
| Writes the Local File and Master File | Delivers reconciled intercompany balances |
| Handles the benchmarking analysis | Supplies agreements and allocation keys |
| Manages the tax audit interaction | Answers "what actually happened" — fast |
The failure mode is not a disagreement between the two columns. It's an assumption in both directions: finance assumes the advisor has the documentation covered, the advisor assumes the data is available when needed, and nobody discovers otherwise until an audit is announced. One conversation before that happens is enough to close it.
Where an interim controller fits in
Getting a German subsidiary transfer-pricing-ready is a scoped project with a clear finish line — exactly the shape of an interim controller mandate. The work is unglamorous and entirely within the finance function: map the intercompany flows and check them against the thresholds, put a monthly reconciliation in place with the counterparties, collect the agreements into one accessible place, document the pricing basis as applied, and agree the data hand-off with the tax advisor so it works on demand instead of on request.
Done as a project, it's a few weeks. Done under an announced audit, it's the same work compressed into thirty days alongside everything else the audit demands — which is how most companies end up doing it, and why most companies end up paying for it.
Conclusion
The thirty-day rule didn't create a new obligation — it removed the slack that was hiding an old weakness. Transfer pricing documentation has always required a clear picture of intercompany flows; companies simply had two months and a formal prompt to assemble one. Now the clock starts when the audit is announced, and the penalty attaches to being late even when the prices themselves were right.
The fix isn't a tax project. It's a data project, run once, so that when the request comes the answer is retrieval instead of reconstruction. Your advisor writes the file. Your finance function decides whether they can.
This article shares general information from a controlling and process perspective. It is not tax or legal advice — for your company's specific documentation obligations, thresholds and transfer pricing methods, please speak to your tax advisor.
Could your German entity produce a complete intercompany picture in thirty days?
Let's make the answer boring.
Book a call → or get in touch directly.
Frequently asked questions (FAQ)
How long do you have to submit transfer pricing documentation in Germany?
Thirty days from the request, applicable from financial year 2025 onward — halved from the previous 60 days. The documentation can be requested at any time and is effectively triggered when a tax audit is announced, without a separate explicit demand.
Who has to prepare transfer pricing documentation?
A Local File is required when cross-border related-party goods transactions exceed €6 million per year, or services exceed €600,000 per year. A Master File applies above €100 million total revenue. Companies below the thresholds don't need a formal file but must still be able to demonstrate that related-party prices are appropriate.
What are the penalties for missing transfer pricing documentation?
5–10% of the estimated income adjustment with a minimum of €5,000 for failing to produce usable documentation, plus late-submission surcharges of at least €100 per day up to €1 million. The exposure attaches to being late, even if the underlying prices were correct.
What is the difference between a Local File and a Master File?
The Local File covers the German entity's own related-party transactions — what was exchanged with whom, at what price and on what basis. The Master File gives the group-wide picture: global structure, value chain and overall transfer pricing strategy. Different thresholds apply to each.
Is transfer pricing documentation the tax advisor's job or the finance team's?
Both, in sequence. The tax advisor selects and defends the pricing methods and writes the file. The finance function supplies the raw material: reconciled intercompany balances, transaction volumes, agreements and allocation keys. The advisor can only document what the finance function can produce — which is why thirty days is a data-readiness question.