Last updated: 2025-11-05
Reporting the transport of waste in Finland to the SIIRTO register
In this Price item
The SIIRTO register is a transport document storage system set up by the Ministry of the Environment and the Finnish Environment Institute. The obligation to register data is based on the amendment to the Waste Directive which entered into force in 2022. See Collection and transport of waste within Finland for more information.
Organisations can submit data to the SIIRTO register via an API. Opter is integrated with the SIIRTO register via this API, so data about waste can be entered in Opter and this will be automatically reported to the SIIRTO register when the order is saved in Opter. A transport document is created in the SIIRTO register and the document’s ID number is then displayed in Opter. The transport document that is created is at the order level, but it is possible to have several different types of waste at the package level.
For the above to work, it is necessary to contact those who are responsible for the SIIRTO register first and ask them to arrange for you to submit data to the SIIRTO register via the API. See Collection and transport of waste within Finland for more information. You can then contact Opter’s EDI team and order a link between your Opter and the SIIRTO register.
Once everything is set up, check that each order containing waste packages has the correct information relating to the sender, receiver, date of shipment, as well as the package’s weight, goods text and waste code. When the order is saved, the data is sent from Opter to the SIIRTO register via the EDI link and the API. If the information has been received correctly, the SIIRTO register returns a document ID for the order to Opter. Once Opter has received the document ID, it will be displayed on the order in order reception, if you have opted to have that field displayed. If in Opter you later change information about the waste, such as its weight, Opter and the SIIRTO register will use this document ID to update the information in the correct transport document in the SIIRTO register.
The following information must be recorded for each type of waste transported:
-
From whom and from what location the waste is to be transported.
-
Date of shipment.
-
Mode of transport, e.g. transport by road or sea.
-
The vehicle registration number.
-
The weight of the waste in kilograms (i.e. the weight of the package).
-
The goods text for the waste (i.e. the goods text on the package). There should be a description of the waste.
-
To whom and to what location the waste is to be transported.
If the waste is transported by several carriers, the above records should only cover the carrier’s part of the shipment.
Waste codes
The waste codes are listed in Finnish and usually in Swedish and English as well, see Code lists of the waste and product information system.
For each order containing packages of waste, enter the waste codes for the package in the following fields/columns in Opter; see the table below. Not all codes are always required, in which case the field can be left blank.
The table below shows how the fields/columns in Opter are structured in accordance with the default implementation. If the fields/columns are to be structured differently to better suit your business, you can notify the EDI team when the integration is created (see step 1 below).
|
Field/column in Opter |
Waste codes |
|---|---|
|
ExtraID2 (package) |
Required for all waste, both hazardous and non-hazardous. The six-digit waste code, also known as the “LoW code” (List of Waste code) and “EWC code” (European Waste Catalogue code). For example, if the waste comes from the purification of fuels using bases, enter the code "050111*". Waste codes marked with an asterisk (*) indicate that the waste type is hazardous waste. The codes are listed in Waste codes (LoW/EWC). If the waste is non-hazardous according to the six-digit waste code entered in ExtraID2 (package) (i.e. it does not contain an asterisk (*)), it is not necessary to fill in anything in ExtraID3 (package). |
|
ExtraID3 (package) |
Only required for hazardous waste, i.e. if the code in ExtraID2 (package) contains an asterisk (*). Enter the following four pieces of information:
Enter the information in the ExtraID3 (package) field according to the format below, i.e. with a dot after the composition, a semi-colon after the hazardous properties and a colon after the type of packaging applicable to the waste. "composition.properties;packaging:form" For example, you can enter “Dusty sand mixture.HP1;5:2” in ExtraID3 (package). The hazardous waste data requirement (i.e. the data entered in ExtraID3 (package) and the transport type code for the waste entered by the EDI team in your EDI link) is validated based on the waste code entered in ExtraID2 (package). |
|
ExtraID4 (package) |
Required if the waste contains persistent organic pollutants. The code for persistent organic pollutants is also known as the POP (Persistent Organic Pollutant) code. For example, if it is toxaphene, enter code “24”. The codes are listed, in Codes for persistent organic pollutants. If the waste contains persistent organic pollutants, the waste packaging type cost must be indicated in ExtraID3 (package); see above. Waste containing persistent organic pollutants is always hazardous waste. |
|
ExtraID5 (package) |
Required for all waste, both hazardous and non-hazardous. Enter one of the following two options here:
|
|
Extra dimension1 |
Required for all waste, both hazardous and non-hazardous. The code indicating where the waste was generated, also known as the “code of origin”. For example, if the waste was generated in industrial processes, enter code “2”. If it was caused by mining, enter the code '5'. The codes are listed in Codes of origin. Code 8 “Other (specify)” cannot be entered, because in the current implementation in Opter there is no field to specify/describe the origin of the waste. If you have to use code 8, contact so that they can add a “code of origin description” to your EDI link. |
|
Extra dimension2 |
Required for all waste, both hazardous and non-hazardous. The code for the type of waste, also known as the “waste type code”. For example, if the waste is “hazardous waste, enter code “3”, if it is “non-hazardous waste”, then enter code “1”. The codes are listed in Waste type codes. |
Conditions
The SIIRTO register’s API
Contact those who are responsible for the SIIRTO register and ask them to arrange for you to submit data to the SIIRTO register via the API.
Vehicle registration number
The registration number of the vehicle transporting waste is also sent to the SIIRTO register. Check that all your vehicles transporting waste in Finland have the correct registration numbers in Opter under Register > Vehicles on the tab General in the Registration number field.
When a vehicle is added to a waste transport order, that vehicle’s registration number will be sent to the SIIRTO register. If you will use several vehicles for each waste transport order, you can ask the EDI team to implement this for you.
Step 1: Contact Opter’s EDI team
After you have contacted those who are responsible for the SIIRTO register and asked them to arrange for you to submit data to the SIIRTO register via the API, proceed as follows:
-
Request an EDI link between your Opter and the SIIRTO register by contacting the EDI team at . For information about the cost of EDI work, see your agreement with Opter.
In order to set up the EDI link to the SIIRTO register, the EDI team needs the following information from you:
-
Your corporate ID number.
-
Your company name.
-
Your contact person’s name (first and last names).
-
Your contact person’s email address.
-
Your contact person’s telephone number including the country code in front of the number, e.g. +46 70 xxx xx xx.
-
Mode of transport, e.g. transport by road and/or sea. (The transport type code is required if the waste is hazardous and/or contains persistent organic pollutants).
-
If one or more vehicles is used per waste transport order. For more information, seeVehicle registration number above.
-
The country of origin of the waste.
-
The receiver’s corporate ID number (i.e. the corporate ID number of the company receiving the waste after shipment).
-
-
When the EDI link is ready, you and someone from the Opter EDI team jointly test that the link with the SIIRTO register is working.
Step 2: Add waste code columns and document ID fields in Opter
This is how to add new columns for waste codes in the Packages section of order reception and a new field for document IDs at order level in order reception:
-
In Opter, click on Settings > Offices > Terminology.
-
Name the field and columns, preferably as indicated below if the fields/columns in Opter are structured in accordance with the default implementation:
-
ExtraID1(order) - ”Document ID SIIRTO”
The document ID number sent to Opter by the SIIRTO register is displayed in this field on the order.
-
ExtraID2 (package) – “LoW code”
The six-digit waste code, also called the “LoW code” and “EWC code”. For example “050111*”.
-
ExtraID3 (package) – “Hazardous waste”
Description and codes for hazardous waste and/or persistent organic pollutants. Enter the information in the field in the “composition.properties;packaging type:form” format. For example, “Dusty sand mixture.HP1;5:2”.
-
ExtraID4 (package) – “POP code”
The code for persistent organic pollutants is also known as the POP code. For example, if it is toxaphene, enter code “24”.
-
ExtraID5 (package) – “R code/D code”
The code for the recovery procedure, for example “R2”, or the code for the disposal procedure, for example “D10”.
-
Extra dimension1 – “Code of origin”
The code indicating where the waste was generated, also known as the “code of origin”. For example, if the waste was generated in industrial processes, enter code “2”.
-
Extra dimension2 – “Waste type code”
The code for the type of waste, also known as the “waste type code”. For example, if the waste is “hazardous waste, enter code “3”, if it is “non-hazardous waste”, then enter code “1”.
For more information about waste codes, see Waste codes above.
If the fields/columns have been structured in a different way to better suit your business, name the fields and columns you use.
-
-
Click on
to save all changes. -
Click on Settings > Order reception > Order settings and the Form flow tab. Select the configuration to be changed from the list on the left.
-
Search for Extra ID1 and select the checkbox in the Visible column.
Once the changes have been saved, the Extra ID1 field will be displayed under Data in order reception. The document ID sent to Opter by the SIIRTO register is displayed in this field.
-
Click on the Tab settings tab and check that the Data section is displayed in order reception. For detailed instructions, see Organising the groups in Order reception.
-
Click on
to save all changes. -
Click on the Control tab in the Order settings window. In the Control settings box next to the Packages field, click on
. -
Click on the Columns tab. Drag and drop the waste code columns (Extra ID2, Extra ID3, Extra ID4, Extra ID5, Extra dimension1, Extra dimension2) from Excluded to Included, if they are not already in the Included list.
Drag and drop columns Quantity, Goods text, Weight and preferably also Package ID from Excluded to Included, if they are not already in the Included list.
-
Choose the order of the columns in the Packages section in order reception by moving the columns up or down in the Included list, which is done by dragging and dropping them where you want to have them.
-
Click on
to save all changes. -
Close the Package settings window.
The new waste code columns should now be displayed in the Packages section and the document ID field should be displayed in the Data section in order reception.
Step 3: To display the waste codes and document IDs in Opter Driver
You can set whether the waste codes and/or document IDs are to be displayed in the Opter Driver app. The waste codes and document IDs can be displayed in the following two places in Opter Driver:
-
In the detail view/shipment view in the Packages section. The waste code and document IDs cannot be changed here, only displayed.
-
In the package view.
The package view is displayed when a shipment is opened, the menu in the top right corner is tapped, Packages is tapped and then a package is tapped.
The waste codes and the document ID number can be changed in the package view in Opter Driver after adding the fields, for example “LoW” or “LoW code” (ExtraID2 (package)). It is possible to define whether or not the changes need to be manually approved by dispatch before they are saved, see Step 4 below.
If someone accidentally changes the document ID number, future updates on waste codes in the SIIRTO register for that order will be reported to the wrong document ID number at SIIRTO. To reduce the risk of this problem, there is an option not to display the field with the document ID number and/or set it up so that changes have to be manually approved in dispatch before they are saved on the order, i.e. before any updates are sent to the SIIRTO register.
Follow the instructions:
If you choose to add all possible package fields, not all of them will fit in the app (widthwise). We recommend that you choose to display the fields/columns that are most relevant for you.
If you use the App.OpterDriver.Design or App.Design XML file, the width of each column can also be adjusted, thus allowing you to maximise the information displayed about each package in the Packages section of the app.
There are two ways to set which fields and columns are displayed in the detail view/task view in Opter Driver for iOS and Opter Driver Labs for Android. For Opter Driver (classic) for Android, only App.Design works, that is, the first option below. Choose the way that suits you best:
-
Edit the App.OpterDriver.Design or App.Design XML file.
If the App.OpterDriver.Design or App.Design XML file is used, the fields/columns can be given their own names, such as “LoW” or “LoW code” (ExtraID2 (package)). For example, if you do not choose your own name, it will show “Ex. ID 2” or “Dim. 1”, which is not particularly clear. The width of each column can also be adjusted, thus making it possible to maximise the information displayed about each package in the Packages section of the app.
For information on how to choose whether to use App.OpterDriver.Design or App.Design, see Customising the layout and features of Opter Driver.
For instructions on how to display fields and columns, name fields and columns and adjust the column width, see App.OpterDriver.Design or App.Design.
-
Using the Design field for mobile window.
This only works for Opter Driver for iOS and Opter Driver Labs for Android, not for Opter Driver (classic) for Android.
The Design field for mobile window is easier to use than the App.OpterDriver.Design XML file, but neither the names of the fields/columns nor the width of the columns can be changed in the Design field for mobile window.
For more information, see Setting which fields are displayed in Opter Driver.
To display waste codes and/or document IDs in the package view, proceed as follows:
-
In Opter, click on Settings > Mobile data > Settings mobile data.
-
Click on an empty row in the Name column and then on the down arrow in the row being added. For example, select SPA_ExtraId2Permission from the list.
-
Enter one of the following in the cell to the right:
-
“True”: if the “LoW code” (ExtraID2 (package)) should be displayed in the package view.
All SPA_Permission settings are “true” by default, which means that they are all displayed if no setting is applied at all.
If SPA_ExtraId2Permission is set to “true” then all the other SPA_Permission settings that should be displayed in Opter Driver must be set to “true”, for example SPA_WeightPermission, SPA_VolumePermission and SPA_QuantityPermission.
-
“False”: if the “LoW code” (ExtraID2 (package)) should not be displayed in the package view.
If SPA_ExtraId2Permission is set to “false” then all the other SPA_Permission settings that should be displayed in Opter Driver must be set to “true”, for example SPA_WeightPermission, SPA_VolumePermission and SPA_QuantityPermission.
-
-
To change the name of the field, click on an empty row in the Name column and then on the down arrow in the row being added. Select SPA_ExtraId2Name from the list.
-
In the cell on the right, enter the name that the field should be given in the package view, for example “LoW code”.
-
To set where the “LoW code” (ExtraID2 (package)) should be located in the package view list, click on an empty row in the Name column and then on the down arrow in the row that is being added. Select SPA_ExtraId2Order from the list.
In the cell on the right, enter a number to indicate where in the package view list the “LoW code” (ExtraID2 (package)) should be located. For example, enter the number “1” if the field should be at the top of the list. Enter the number “2” if the field should be the second field in the list. For more information, see Mobile data settings (window).
The field with the lowest number appears at the top. This means that setting one of the SPA_Order settings to "2" is not enough for it to appear in second place. If "2" is the lowest number, that field will be at the top anyway. In that case, you need to set another field to "1".
-
Click on Save.
The waste codes can be changed when the field has been clicked in the package view in Opter Driver. It is possible to define whether or not the changes need to be manually approved by dispatch before they are saved, see Step 4 below.
Step 4: If changes made to the waste code fields in Opter Driver have to be approved
It is possible to choose whether or not changes to the waste code fields made in Opter Driver have to be manually approved in dispatch before the changes are saved. Proceed as follows:
-
Follow the instructions in Setting how changes made in Opter Driver are approved.
-
If App.ApproveChanges has been set to “true”, exceptions can be made for certain changes; these do not then have to be manually approved in dispatch.
If changes to the “LoW code” (ExtraID2 (package)) should not have to be approved in dispatch, click on Settings > Mobile data > Shipment Change Elements. Select Extra ID 2 (package) from the list on the left and deselect the Require Approval checkbox. Click on Save.
Each time the order is saved, Opter checks whether anything has changed on the order. If something has changed on the order, the data is sent to the SIIRTO register in accordance with one of the following scenarios:
-
If it has been defined that, for example, changes to the “LoW code” (ExtraID2 (package)) in Opter Driver do not need to be approved manually in dispatch, the data is sent to the SIIRTO register when the Opter Driver user clicks on Save in the package view.
-
If it has been defined that, for example, changes to the “LoW code” (ExtraID2 (package)) in Opter Driver need to be approved manually in dispatch, the data is sent to the SIIRTO register when the dispatcher has approved the changes in dispatch. If the dispatcher does not approve the changes, no new data is sent to the SIIRTO register.
-
Step 5: Record and report data about waste
Record the data about the waste before the shipment begins. When the order is saved, the data is sent from Opter to the SIIRTO register via the EDI link and the API. Proceed as follows:
-
Check that the order has the correct details (especially the name, address, telephone number and date) in the Sender and Receiver boxes in order reception.
-
Check that the weight of the package is indicated on the package row in the Weightcolumn in the Packages section in order reception for each package containing waste.
-
Check that the goods text for the package is indicated on the package row in the Textcolumn in the Packages section in order reception for each package containing waste. The goods text for the package should be a description of the waste, e.g. “Mining waste from Kaivos Yritys AB’s nickel mine”.
-
Enter the waste codes in the Packages section of order reception on the package row in the columns as follows if you have the fields in Opter structured according to the default implementation:
-
ExtraID2 (package) (“LoW code”) – The six-digit waste code, also known as the “EWC code”. For example “050111*”.
-
ExtraID3 (package) (“Hazardous waste”) – Description and codes for hazardous waste and/or persistent organic pollutants. Enter the information in the field in the “composition.properties;packaging type:form” format. For example, “Dusty sand mixture.HP1;5:2”.
-
ExtraID4 (package) (“POP code”) – The code for persistent organic pollutants, also known as the “POP code”. For example, if it is toxaphene, enter code “24”.
-
ExtraID5 (package) (“R code/D code”) – The code for the recovery procedure, for example “R2”, or the code for the disposal procedure, for example “D10”.
-
Extra dimension1 (“Code of origin”) – The code indicating where the waste was generated. For example, if the waste was generated in industrial processes, enter code “2”.
-
Extra dimension2 (Waste type code”) – The code for the type of waste. For example, if the waste is “hazardous waste, enter code “3”, if it is “non-hazardous waste”, then enter code “1”.
For more information about waste codes, see Waste codes above.
If the fields/columns have been structured in a different way to better suit your business, name the fields and columns you use.
-
-
Save the order by clicking on
. When the order is saved, all the data about the order’s packages and their waste codes is sent from Opter to the SIIRTO register.
If the information has been received correctly, the SIIRTO register returns a document ID for the order to Opter. Once Opter has received the document ID, it will be displayed on the order in order reception, if you have opted to have that field displayed. If in Opter you later change information about the waste, such as its weight, Opter and the SIIRTO register will use this document ID to update the information in the correct transport document in the SIIRTO register.
If the data has not been received correctly by the SIIRTO register, this can be seen in the EDI log, see the EDI log tab in the Order log section in order reception.
Each time the order is saved, Opter checks whether anything has changed on the order. If something has changed on the order, the data is sent to the SIIRTO register.
It is also possible to record data about waste in Opter Driver if it has been set up to allow this, see Step 3 and Step 4 above.
Step 6: Check that the data has been reported to the SIIRTO register
How to check that the data about waste has been received correctly in the SIIRTO register:
-
There is a document ID in the ExtraID1(order) (“Document ID”) field on the order in order reception. If you do not have the default implementation, the document ID may be in another field.
The document ID can also be displayed in Opter Driver if it has been set up to allow this, see Step 3 and Step 4 above.
If there is a document ID, the data has been received correctly at least once, but the fact that there is a document ID is no guarantee that the latest updates to the data, if there are any, have been received correctly. To check this, it is necessary to open the EDI log, see below.
-
More detailed information is available in the EDI log on the EDI log tab in the Order log section in order reception.
If the data has been correctly received in the SIIRTO register, this can be seen in the EDI log, as “ACCEPTED” is indicated in the Response column. If the data has not been received correctly, “FAILED” is indicated in the Response column.
Step 7: Change data that has already been reported, if necessary
The data can be updated for 90 days after the data for a new order has been sent to the SIIRTO register, i.e. when the order is first saved in Opter.
To add or amend data that has already been reported to the SIIRTO register via Opter in accordance with the instructions in Step 5 above, proceed as follows:
-
Open the order in Opter and edit the data you want to change, such as the goods text or waste codes for one or more packages of waste. It is also possible to amend the data in Opter Driver if it has been set up to allow this, see Step 3 and Step 4 above.
-
Save the order by clicking on
.When the order is saved, all the data about the order’s packages and their waste codes is sent to the SIIRTO register. If the data is received correctly, the data will be updated in the SIIRTO register.
If the data has been received correctly, this can be seen in the EDI log, see the EDI log tab in the Order log section in order reception. If the data has been received correctly, “ACCEPTED” is indicated in the Response column. If the data has not been received correctly, “FAILED” is indicated in the Response column.
Each time the order is saved, Opter checks whether anything has changed on the order. If something has changed on the order, the data is sent to the SIIRTO register.