The Norwegian Tax Administration (Skatteetaten) and Altinn have announced a mandatory change to the authorization scopes used for VAT Return Submission API integrations. If your organization submits VAT returns directly to Altinn from Dynamics 365 Finance & Operations (D365FO) — as described in my earlier guide, Configure Direct VAT Return Submission to Altinn in D365FO — this change directly affects your ID-Porten / Samarbeidsportalen client configuration.

What Is Changing

✅ New required scopes for VAT return submission:

• altinn:instances.read
• altinn:instances.write

✅ Validation continues to use:

• skatteetaten:mvameldingvalidering

❌ Deprecated scope:

• skatteetaten:mvameldinginnsending

Deadline: September 1, 2026. After this date, VAT return submissions that still rely on the deprecated skatteetaten:mvameldinginnsending scope will stop working.

Why This Change Is Happening

The new required scopes, altinn:instances.read and altinn:instances.write, are standard Altinn 3 scopes rather than Skatteetaten-specific ones. According to Altinn’s own authentication documentation, these scopes govern what a system is allowed to do on behalf of an end user once authenticated via ID-Porten: altinn:instances.read allows a system to read the contents of a user’s Altinn inbox and archive for the elements the user is authorized for, while altinn:instances.write allows a system to fill out, sign, and submit forms in Altinn on the user’s behalf.

In effect, Skatteetaten is retiring its own bespoke submission scope in favor of the generic Altinn 3 instance scopes that already exist for reading and writing data in the Altinn platform. This aligns VAT return submission with the standard Altinn 3 authorization model, rather than a service-specific scope maintained separately by the Tax Administration.

Action Required

If you own, maintain, or support integration points for customers in Norway, you should:

1. Review your ID-Porten / Altinn scope configuration. Log into Samarbeidsportalen and open the client used for your D365FO VAT return integration.
2. Replace the deprecated submission scope with the new Altinn scopes. Remove skatteetaten:mvameldinginnsending and add altinn:instances.read and altinn:instances.write. Keep skatteetaten:mvameldingvalidering and openid as they are — these are unaffected.
3. Validate the end-to-end submission flow in both your test and production environments after updating the scopes, including re-authorizing the D365FO Electronic Messages web application connection where required.
4. Ensure your integration remains fully operational before September 1, 2026.

Where to Make the Change

If you followed the setup process in my earlier article, the scopes live in two places that need to be kept in sync:

• Samarbeidsportalen → Integrasjoner → Clients → ID-Porten client → Scope tab — this is where the client’s available scopes are registered with DigDir/ID-Porten.

• D365FO → Tax > Setup > Electronic messages > Web applications (“NO ID-Porten”) — after changing the scope configuration in Samarbeidsportalen, the authorization code and access token in D365FO typically need to be re-obtained so the new consent (covering the updated scopes) is captured.

In practice, this means:

• Go to the ID-Porten client in Samarbeidsportalen.
• Remove skatteetaten:mvameldinginnsending from the scope list.
• Add altinn:instances.read and altinn:instances.write.
• Save the configuration.
• In D365FO, return to the “NO ID-Porten” web application record, select Get authorization code, complete the BankID re-authentication, and then select Obtain access token to activate a token issued under the new scope set.
• Submit a test VAT return in a non-production environment to confirm the full validate-and-submit flow still completes successfully end to end.

Don’t Wait Until the Deadline

Because the change requires re-consent through ID-Porten (a BankID authentication step performed by an authorized user), this isn’t purely a backend configuration change — it depends on the availability of whoever holds the relevant signing/API rights in Altinn. Plan this into your change calendar now rather than in the days before September 1, 2026.

If you support multiple Norwegian legal entities or multiple customers, review all Norway VAT reporting integrations under your responsibility and schedule the scope replacement and revalidation for each one, so no customer’s VAT submissions are disrupted when the deprecated scope stops working.

Summary

The transition to the Altinn 3 instance scopes is a small configuration change with a potentially significant operational impact.

Item	Old	New
Submission scope	skatteetaten:mvameldinginnsending (deprecated)	altinn:instances.read + altinn:instances.write
Validation scope	skatteetaten:mvameldingvalidering	Unchanged
Deadline	—	September 1, 2026

Getting ahead of this now — updating the scope configuration in Samarbeidsportalen, re-authorizing the D365FO connection, and testing the flow in a non-production environment — will avoid any interruption to VAT return submissions when the old scope is switched off.

Questions about updating your Altinn/ID-Porten scope configuration for D365FO VAT return submission? Feel free to reach out or leave a comment.

References

• Configure Direct VAT Return Submission to Altinn in Dynamics 365 Finance & Operations
• Altinn – Authentication with ID-porten
• Skatteetaten – Merverdiavgift og Altinn 3
• Microsoft Learn – Register an integration point in the ID-porten web portal
• Microsoft Learn – Prepare Dynamics 365 Finance for ID-porten and Altinn

Information and documentation status reviewed on August 4, 2026. Always verify the latest requirements from Skatteetaten, Altinn and Microsoft before making production changes.