.png?lang=en-GB&ext=.png)
Ilona Orbók
Every company in Hungary that is not a small or micro enterprise must price its related-party transactions at arm's length and document them by the corporate income tax deadline. From the 2026 tax year, Decree 45/2025 (XII. 23.) NGM sets new thresholds and stricter content rules. BDO Hungary's transfer pricing team supports international groups with Hungarian local files, benchmarks, data reporting and tax audits.
The most important points in brief
Transfer prices are the prices applied in transactions between related parties, such as a Hungarian subsidiary and its parent or sister companies. Since 1992, the Hungarian Corporate Tax Act has required these prices to follow the arm's length principle, in line with the OECD Transfer Pricing Guidelines. The price must match what independent parties would agree under comparable conditions.
Two obligations follow from this rule:
Small and micro enterprises are exempt from the documentation obligation. A Hungarian company's foreign permanent establishment and its Hungarian head office also count as related parties.
Decree 45/2025 (XII. 23.) NGM on transfer pricing records and data reporting replaced Decree 32/2017 on 23 January 2026. It applies mandatorily from the 2026 tax year. For the 2025 tax year, taxpayers may already apply it to individual Local Files. The new decree raises some thresholds, but it also asks for considerably more detail.
Table 1
Key rules under Decree 45/2025 from the 2026 tax year
| Item | Rule under Decree 45/2025 |
|---|---|
| Local File | Required if the arm's length value of a transaction (after aggregation) exceeds HUF 150 million a year, excluding VAT |
| Data reporting only | Transactions between HUF 100 and 150 million still have to be reported in the tax return |
| Master File | Required if Local File transactions exceed HUF 500 million in total |
| Pass-through recharges | Exempt from a Local File up to HUF 500 million a year |
| Simplified Local File | Low value-adding services (5% net cost plus mark-up test), free transfers of funds, pass-through recharges |
| Language | Hungarian, English or German |
| Retention | At least 8 years for the Local File and its appendices |
| Benchmark updates | New database search at least every 3 years, financials updated yearly |
In short: a Local File is needed above HUF 150 million per transaction and a Master File above HUF 500 million in total. Between HUF 100 and 150 million, only data reporting applies. Pass-through recharges are exempt up to HUF 500 million. A simplified file is available for low value-adding services, free transfers of funds and pass-through recharges. Files can be prepared in Hungarian, English or German, must be kept for 8 years, and the benchmark search must be renewed every 3 years.
The content requirements have become stricter at the same time:
A group-prepared Local File can be a good starting point, but it rarely meets Hungarian requirements without local adjustment. Group templates are usually built for many countries at once. As a result, they often miss the points the Hungarian decree checks explicitly: the benefit test, segmented and traceable financials, the Hungary-first benchmark order, and the link between the Local File and the data reported in the tax return.
Table 2
Options for preparing the Hungarian Local File
| Approach | Works well when | Main risk in Hungary |
|---|---|---|
| In-house | The team has TP expertise and access to databases | Workload around the tax return deadline; benchmarks may not follow the regional order |
| Group file used as delivered | Transactions are simple and close to the thresholds | Missing Hungarian content elements; inconsistency with the data reporting |
| Group file reviewed and localised by a Hungarian advisor | The group already has a policy and a Master File | Requires early data collection from the group |
| Full local preparation by an advisor | Several transactions are above the thresholds, or an audit is expected | Higher one-off cost in the first year |
In short: in-house preparation needs TP expertise and database access. A group file used without changes risks missing Hungarian content. A group file reviewed locally combines the group policy with Hungarian requirements. Full local preparation suits companies with several documented transactions or an expected audit.
As a rule of thumb, it is worth reviewing the group file locally if any transaction exceeds HUF 150 million, if the Hungarian entity receives management or IT services from the group, or if the company acts as a contract manufacturer or limited-risk distributor for the group. In these cases, the right choice depends on the group's existing documentation and on internal capacity.
For a calendar-year company, the transfer pricing work for one tax year falls mostly between January and the end of May of the following year. A typical cycle has five steps:
If a price turns out to fall outside the arm's length range at year end, the adjustment belongs in the same tax year. This is one more reason to check the profit levels before the books are closed.
Missing or deficient transfer pricing records can lead to a default penalty of up to HUF 5 million per record, or up to HUF 10 million for repeated failure. The larger risk is usually a tax base adjustment. If the price falls outside the arm's length (interquartile) range, the profit before tax must as a rule be adjusted to the median of the range, not to its nearest end. Tax shortfall penalties and late payment interest may come on top of the adjustment.
The National Tax and Customs Administration (NAV) also checks transfer pricing more often. Since 1 January 2025, it can examine transfer pricing records and data reporting within compliance verification audits. As a result, gaps can surface outside a full tax audit as well. Groups with consolidated revenue above EUR 750 million also have country-by-country reporting (CbCR) duties, where failures can lead to a penalty of up to HUF 20 million.
The transfer pricing team of BDO Hungary supports companies across the full transfer pricing cycle:
For data collection, BDO Hungary also offers a digital tool, the BDO Transfer Pricing Questionnaire. Related topics such as permanent establishments, CFC rules or group restructuring are covered by the international tax team.
BDO Hungary is part of the global BDO network. Through its Budapest regional centre, it supports cross-border transfer pricing coordination with BDO member firms in other Central and Eastern European countries and beyond.
The documentation must be ready by the deadline of the corporate income tax return for the tax year, which is 31 May of the following year for calendar-year taxpayers. It is not filed with the return, but it must be available if the tax authority requests it.
No. The new decree is mandatory from the 2026 tax year. For 2025, taxpayers may choose it for individual Local Files. Because the choice affects content and thresholds, it is worth assessing it transaction by transaction.
Yes. Under Decree 45/2025, transfer pricing records and the supporting documents may be prepared in Hungarian, English or German.
Yes, if the arm's length value of the financial transaction exceeds the HUF 150 million threshold. Financial transactions form a separate category and cannot be aggregated with services or goods.
Transfer pricing means setting arm's length prices for transactions between related parties. In Hungary, the Corporate Tax Act sets the arm's length principle. Decree 45/2025 (XII. 23.) NGM sets the documentation and data reporting requirements from the 2026 tax year.
Several international advisory networks provide transfer pricing documentation in Hungary, including BDO Hungary. When choosing a provider, it is worth checking experience with Hungarian Local Files under Decree 45/2025, access to regional benchmark databases, and support in NAV audits.
Tax advisors and tax lawyers can represent a company before NAV. BDO Hungary supports companies in transfer pricing audits, from reviewing the documentation to communicating with the tax authority.