This hub explains what is mandatory at EU level (EMSA MIG), what Finland requires in practice, and how to submit/report through National APIs or AS4/RIM.
Finland has documented deviations from harmonised EMSWe MIG data requirements. In the affected cases, declarants must follow Finnish national requirements when submitting formalities to the Finnish MNSW. This section is documentation only; implementation and validator changes are handled separately.
For HZA reporting under MIG 2.0.1, Finland does not apply the requirement in R-HZA-008 concerning the use of value SF. The deviation applies to the HZA formality.
Traficom has deemed the requirement incorrect for dangerous goods reporting in Finland.
Declarants submitting HZA formalities to the Finnish MNSW must follow Finnish national requirements instead of R-HZA-008 in this case.
For SEC reporting under MIG 2.0.1, Finland does not apply R-GENERAL-040 in the affected case where applying the rule would prevent reporting an event taking place during the same date.
Declarants submitting SEC formalities to the Finnish MNSW must follow Finnish national requirements instead of this MIG rule in the affected case.
Additional Finnish deviations can be added to this section as separate topic cards.
EMSA MIG defines the common EU data model: which formalities exist and which data elements/member-state interfaces are harmonized by the Commission.
Finland follows EMSA MIG, but not every data element is required in every national process. The Finland data-elements view and RCG explain the practical minimum and conditional requirements.
Use National APIs (Declarant or Port) for REST-based integration, or AS4/RIM messaging where applicable. Both paths use the same formalities concepts and code lists.
Finnish ports can submit statistics either through the National Port API
(postStatistics) or by using the Excel-based template process.
Both options are documented with required fields, validation rules, and examples.
Check environment endpoints, authenticate with OAuth2 client credentials, and contact support for onboarding, production access, and operational questions.
Primary EU reference for the harmonized reporting model, formalities, and interoperability concepts that all member states align to.
National interpretation of formalities: which data elements are used in Finland and where reduced data sets are acceptable depending on context.
Consolidated rules and business conditions used when validating/reporting formalities and related data in national and EMSA contexts.
Schema artifacts for formality payload validation in MIG 2.0.1.0 integrations.
REST interface for declarants: create/manage port calls, submit/update/withdraw formalities, and attach supporting information.
REST interface for ports: view port calls and formalities, access vessel/ship data, and submit post-port statistics.
Location reference data (including national datasets) used by integrations for place and movement context.
Hazardous material reference data used by relevant formalities and domain-specific reporting flows.
Code lists used across Finnish formalities, validation, and API payloads.
Browsable location dataset index for EMSA and national context.
Tilastoryhmien tarkennukset, tilastoryhmäkoodit ja edustavat HS-koodit.
Mapping table between declarant vessel types and Finnish Customs vessel type categories.
| Environment | Base URL | Auth | Status | Notes |
|---|
Apply for credentials, roles, and onboarding support before integration testing.
Implement REST-based declarant flows for submitting and maintaining formalities.
Implement port-side retrieval and reporting flows, including vessel and statistics use cases.
Set up sender access point, certificates, and message flow for RIM-based reporting.
Slides and recordings that explain concepts, changes, and practical integration examples.
Email us for onboarding and technical support.