Norway’s Pillar Two regime applies to groups with annual consolidated revenue of at least EUR 750 million in at least two of the previous four accounting periods. Norwegian constituent entities within scope have to think about three distinct filings:
The GIR is the detailed information return. It must be filed digitally in XML and in English. A Norwegian entity may either file it itself or be covered by a foreign or group filing, but if it relies on another filer it must notify Skatteetaten.
The notification tells Skatteetaten which entity will file the GIR for one or more Norwegian entities and in which jurisdiction that GIR will be filed.
This is separate from the GIR. It is required for Norwegian entities that must actually pay Norwegian top-up tax and must show the tax amount in NOK.
As such, even if a group is using a centralized or foreign GIR filing, Norway can still require a Norwegian notification, and any entity with Norwegian top-up tax still has a separate domestic tax-return obligation.
The GIR deadline and the notification deadline are aligned. Both are generally 15 months after the end of the ultimate parent entity’s fiscal year, with an 18-month deadline for the first year the group is in scope. The first Norwegian GIR and the first Norwegian notification are due on 30 June 2026. The Norwegian top-up tax return is due one month later; the first due date published by Skatteetaten is 31 July 2026.
| Workstream | Who files? | General deadline | First-cycle date published by Skatteetaten | Extension? |
|---|---|---|---|---|
| GIR | In-scope Norwegian constituent entity unless another filer covers it | 15 months after UPE year-end; 18 months for first year | 30 June 2026 | No extension or exemption |
| Notification | Norwegian entity relying on another GIR filer | Same as GIR | 30 June 2026 | No extension |
| Top-up tax return | Norwegian entity that must pay Norwegian top-up tax | One month after GIR deadline | 31 July 2026 | No extension or exemption |
Skatteetaten routes the GIR, notification, validation service, and top-up tax correspondence through its online suppleringsskatt environment. To use the services, the entity must be registered in the Enhetsregisteret and the user must have the right Altinn roles or access package.
Every Norwegian constituent entity in scope starts from a GIR filing obligation. If another entity will file a GIR that includes the Norwegian entity, the Norwegian entity must notify Skatteetaten who that filer is and where the GIR will be lodged. But the Norwegian obligation does not disappear if the other filer’s GIR does not contain enough information for Norway to determine the Norwegian top-up tax position.
The GIR must be prepared in English and filed digitally in XML. Norway’s guidance points filers to the OECD XML Schema and the OECD XML Schema User Guide, and the tax authority also publishes example XML files on GitHub. Skatteetaten recommends both an external XSD validation and use of Norway’s own validation service before filing.
Norway publishes local rules on what values must be used in the key OECD fields.
| Area/XPath family | Norway rule | Operational consequence |
|---|---|---|
| Language / format | The GIR must be in English and in XML. | No paper, PDF, spreadsheet, or Norwegian-language return. |
MessageHeader/SendingEntityIN | Use the Norwegian organisation number of the entity filing the GIR. | The sender is identified by the local Norwegian organisation number. |
MessageHeader/TransmittingCountry | NO | Fixed domestic inbound header value. |
MessageHeader/ReceivingCountry | NO | Even if the file is intended for exchange, the inbound filing is addressed to Norway. |
MessageHeader/MessageType | GIR | No alternative message type. |
MessageHeader/MessageRefID | Free text, but unique; Skatteetaten gives an example such as StatusNO2024xxx. | You need a uniqueness convention and versioning discipline. |
MessageHeader/MessageTypeIndic | GIR101 only. GIR102 and GIR103 must not be used. | Norway does not accept OECD-style correction or nil-return message types in the inbound file. |
MessageHeader/ReportingPeriod | Use the last day of the UPE fiscal year and match the Filing Info period end. | Header and Filing Info must reconcile. |
MessageHeader/Warning and Contact | Do not populate them. | These fields are effectively left blank for Norway. |
FilingInfo/FilingCE/ResCountryCode | NO | The filing constituent entity must be Norwegian for a Norwegian filing. |
FilingInfo/FilingCE/TIN | Use the organisation number of the filing entity. | Norway uses the organisation number as the local TIN in the filing record. |
FilingInfo/FilingCERole | Use GIR401, GIR402, GIR403, or GIR404 as applicable. GIR405 must not be used. | Role drives the exchange logic and the permitted RecJurCode logic. |
AdditionalInfo | Do not use it in Norwegian filings. | No Norway-specific message-splitting or comments field in AdditionalInfo. |
DocTypeIndic in Filing Info / General / Summary / Jurisdiction | OECD1 only. | Norway does not accept alternative OECD document-type values in inbound GIR filings. |
DocRefId | Free text, but unique; Skatteetaten gives examples such as GIR2024delII. | Build deterministic, unique doc-reference logic across the file. |
RecJurCode | Exchange filings use recipient-country codes for jurisdictions Norway can exchange with; local filings use only NO. | This is one of Norway’s most important overlay rules. |
AdditionalDataPoint | Normally do not use it for Norwegian filings unless another jurisdiction’s local guidance requires it in a centralized filing. | Do not populate speculative extra fields. |
Norway uses the OECD role codes, but with clear local consequences:
–GIR401 (UPE): use where the ultimate parent entity files for itself and other group entities and the file is intended for exchange with other jurisdictions.
–GIR402 (DFE): use where a designated filing entity other than the UPE files for all or several group entities and the file is intended for exchange.
–GIR403 (Designated Local Entity): use where a Norwegian entity files for itself and other Norwegian entities and the file is not intended for exchange; Skatteetaten also says this code is used for national groups headed in Norway.
–GIR404 (Constituent Entity): use where the entity is only filing for itself.
The role you choose affects both RecJurCode and the expected scope of the data. The most important filing patterns are:
-Centralized exchange filing: use GIR401 or GIR402; the RecJurCode values in General Section, Summary, Jurisdiction Section, and where relevant UTPR Attribution, must list the jurisdictions that should receive the data and with which Norway has an activated GIR exchange relationship.
-National groups: use GIR403 or GIR404; use only NO in RecJurCode.
-Local filing by Norwegian entities in foreign-headed groups: use GIR403 or GIR404; use only NO in RecJurCode; include Norway and any non-Norwegian jurisdictions or subgroups where Norway has taxing rights.
-Local filing by a Norway-headed multinational group that is not using centralized exchange filing: use GIR403 or GIR404; use only NO in RecJurCode; but the filing must still include Jurisdiction Sections for all countries where the group operates.
If you haven’t got a subscription you can join up below to carry on reading.
| Cookie | Duration | Description |
|---|---|---|
| cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
| cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
| cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
| cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
| viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |