Date | Changes |
---|---|
2023.01.30 | New page for VAT return for reverse tax liability |
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.
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 VAT return for reverse tax liability. 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 VAT return for reverse tax liability is launched.
In the test environment you can test:
After the VAT return for reverse tax liability is submitted from the ERP accounting system the submitting business will get a receipt in Altinn (https://tt02.altinn.no/ in test).
It will also possible to carry out a manual submission of the VAT return for reverse tax liability in the portal "Min merverdiavgift" on Skatteetaten.no.
Altinn roles for the VAT return for reverse tax liability:
You can fill out and submit the VAT return for reverse tax liabilitywith these roles:
You can fill out the VAT return for reverse tax liability with these roles:
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.
A Python script has been written in order to test the appliaction manually. For more information, please visit: Test application with Python script.
Service | Url |
---|---|
Validation Service | https://idporten-api-sbstest.sits.no/api/mva/grensesnittstoette/mva-melding/valider |
Submission Service | https://skd.apps.tt02.altinn.no/skd/mva-melding-innsending-etm2/ |
Instance API-url | https://skd.apps.tt02.altinn.no/skd/mva-melding-innsending-etm2/instances |
ID-porten integration | https://oidc-ver2.difi.no/idporten-oidc-provider/.well-known/openid-configuration |
Altinn token exchange uri | https://platform.tt02.altinn.no/authentication/api/v1/exchange/id-porten |
The production environment is functionally equal to the test environment.
Service | Url |
---|---|
Validation Service | https://idporten.api.skatteetaten.no/api/mva/grensesnittstoette/mva-melding/valider |
Submission Service | https://skd.apps.altinn.no/skd/mva-melding-innsending-v1/ |
Instance API-url | https://skd.apps.altinn.no/skd/mva-melding-innsending-v1/instances |
ID-porten integration | https://oidc.difi.no/idporten-oidc-provider/.well-known/openid-configuration |
Altinn token exchange uri | https://platform.altinn.no/authentication/api/v1/exchange/id-porten |