Test & Production

Norwegian

Changelog

DateChanges
2022.06.30New page for tax return for VAT compensation
2022.15.11Removed Jupyter notebook demo, added reference to Python script
2022.16.11Added information about testing the VAT-report for VAT compensation

Testing requirements

System providers are responsible for carrying out tests themselves. Focus should be to verify that the validation and submission services work as expected. The implementation guide is the essential guide for getting the solution in place for system providers.

The project team will contribute with debugging, bug fixing, and following up of cases that are sent into the test environment.

The project team is available via Slack for technical clarifications and for direct contact with developers and test managers. The project team can also be reached via mva-modernisering@skatteetaten.no. Contact us here to receive access to Slack.

The test environment and test data

System providers must have test environments which can make use of synthetic data

Connection to the test environment occurs through ID-porten and for the purpose of testing, Skatteetaten's ID-porten integration can be used. It is recommended that the providers order their own integration against ID-porten as soon as possible because the process is partly manual and can be time consuming. See more in implementation guide section 3. ID-porten integration.

The ERP system providers must find test users in Tenor test data search. The testdata are synthetic test users that should also be used to log into ID-porten and Altinn. These are the only test users that can be used to test the tax return for VAT compensation. Ordinary Digdir test users will not work for this purpose.Here is a guide to how to use Tenor test data search.

Skatteetaten's test environment will be available as long as it is needed, after the new tax return for VAT compensation is launched.

Test planning

From november 15th you can test:

  • Validation of a VAT-report in the "merverdiavgift kompensasjon" category, a VAT-report for VAT compensation.
  • Submit a VAT-report for VAT compensation directly from the ERP accounting system.
  • Make a auditors attestation of the VAT-report for VAT compensation in the portal "Min Merverdiavgift"

After the VAT-report for VAT compensation is submitted from the ERP accounting system the submitting business will get a notification in Altinn (https://tt02.altinn.no/ in test). The notification will contain a link to the portal "Min Merverdiavgift". Click on the link and log in with a user that has the correct role to carry out an auditors attestation of the VAT-report for VAT compensation.

Test planning - Roles

To add the right to carry out an auditors attestation of the VAT-report for VAT compensation, please use this guide: User Guide - give attestation rights.

Altinn roles for the VAT-report for VAT compensation:

  • You can fill out and submit the the VAT-report for VAT compensation with these roles:

    • Limited signing rights/Begrenset signeringsrettighet
    • Accountant with signing rights/Regnskapsfører med signeringsrettighet.
  • You can fill out the VAT-report for VAT compensation:

    • Responsible auditor/Ansvarlig revisor
    • Accounting employee/Regnskapsmedarbeider
    • Accountant without signing rights/Regnskapsfører uten signeringsrettighet
    • Assistant auditor/Revisormedarbeider
  • You can carry out an auditors attestation of the VAT-report for VAT compensation in the portal "Min Merverdiavgift" with these roles

    • Responsible auditor/Ansvarlig revisor
    • Auditor certifies validity of VAT compensation/Revisorattesterer - MVA Kompensasjon.

Summary of tests and moving into production

The system providers will, after the end of the test period and in advance of production, summarise their tests. The summary will show what has been tested, along with the status of the carried out tests, including a summary of bugs and inadequacies. The providers will, at Skatteetatens request, provide documentation on how the integration has been tested.

Test application - Python script

A Python script has been written in order to test the appliaction manually. For more information, please visit: Test application with Python script.

Test environment

Test URLS:

ServiceUrl
Validation Servicehttps://idporten-api-sbstest.sits.no/api/mva/grensesnittstoette/mva-melding/valider
Submission Servicehttps://skd.apps.tt02.altinn.no/skd/mva-melding-innsending-etm2/
Instance API-urlhttps://skd.apps.tt02.altinn.no/skd/mva-melding-innsending-etm2/instances
ID-porten integrationhttps://oidc-ver2.difi.no/idporten-oidc-provider/.well-known/openid-configuration
Altinn token exchange urihttps://platform.tt02.altinn.no/authentication/api/v1/exchange/id-porten

Production environment

The production environment is functionally equal to the test environment.

Production URLS:

ServiceUrl
Validation Servicehttps://idporten.api.skatteetaten.no/api/mva/grensesnittstoette/mva-melding/valider
Submission Servicehttps://skd.apps.altinn.no/skd/mva-melding-innsending-v1/
Instance API-urlhttps://skd.apps.altinn.no/skd/mva-melding-innsending-v1/instances
ID-porten integrationhttps://oidc.difi.no/idporten-oidc-provider/.well-known/openid-configuration
Altinn token exchange urihttps://platform.altinn.no/authentication/api/v1/exchange/id-porten