DIWASS requirements: what you must submit, when, and how.
Under Regulation 2024/1157, every cross-border waste shipment must be backed by structured digital data submitted through DIWASS before the truck moves. This guide breaks down exactly what data is required, which documents apply, who is responsible, the timing rules, and the technical setup needed to submit it.
What DIWASS actually requires
DIWASS does not change the underlying rules of the EU Waste Shipment Regulation - waste classification, traceability and documentation obligations all remain. What changes is how the information is handled: every shipment's data must be submitted digitally, in a structured format, and validated by the system before the movement can proceed.
In practice that means five things: complete data, in the right fields, from registered parties, submitted on time, through an approved channel. Miss any one and the shipment stalls. The sections below cover each in turn.
What information must be submitted
DIWASS expects structured fields, not free text or PDF attachments. For each shipment you must provide:
Party identification
The exporter/notifier, consignee, carrier and any broker - each named with their registered DIWASS identity.
Waste classification
The waste description and codes (EWC / Basel), correctly classified for the chosen procedure.
Quantity & packaging
The amount of waste and how it is packaged for transport.
Origin & destination
The collection point, the receiving facility, and the route across the border.
Transport details
Carrier information and the means of transport for the movement.
Supporting documents
Annex VII data, contracts between parties, and any compliance documents the authority requires.
Document requirements by waste type
Notification procedure
The Annex IA notification and Annex IB movement document are required digitally through DIWASS. Mandatory with no paper fallback since 21 May 2026.
General information requirement
The same Annex VII information as before - now submitted digitally. A transition allows paper without sanctions until 31 December 2026; full enforcement from 1 January 2027.
Key point: the regulatory content of Annex VII has not changed - digitisation is the change, not the substance. The same data you prepared on paper is what DIWASS now expects in structured form.
Timing requirements
Information must be in DIWASS before the shipment takes place. There is limited flexibility for late changes, so coordination across the chain has to happen in advance.
Portal or API - and what registration takes
Government web portal
Manual entry, suitable for occasional shipments. Means double data entry and manual status monitoring - no automatic sync with your own records.
API integration
A direct connection - data flows automatically. DIWASS uses SOAP/XML with WS-Security; calls run sequentially and systems sync at least every 12 hours. Necessary above a few shipments a month.
Before you can submit anything you must be registered. That requires an EU Login, and for Dutch companies eHerkenning level 3, plus API client setup if you integrate. Every chain partner must be registered too - you cannot name an unregistered party on a notification.
What happens when requirements aren't met
Validation errors - incomplete or wrongly-coded data is rejected at submission.
Processing delays - the movement cannot proceed until the record is complete and consistent across all parties.
Increased scrutiny - repeated errors draw closer attention from the competent authority.
Rejection & fines - for Orange List shipments, a missing or wrong status at a live border check makes the transport illegal. The carrier is fined first.
DIWASS requirements, in short
What information must be submitted for DIWASS?
Structured data per shipment: party identification, waste classification and codes, quantity and packaging, origin and destination, transport details, plus the relevant Annex VII or IA/IB document data - not email or PDF.
When must it be submitted?
Before the shipment. Annex VII: min. 2 working days before departure; Orange List: min. 3 working days. Receipt within 3 working days of arrival; completion certificate within 30 days of processing.
Portal or API?
Both meet the requirement. Portal for occasional shipments; API (SOAP/XML, WS-Security) for regular flows. Dutch companies also need eHerkenning level 3 and an EU Login to register.
What if the data is incorrect?
Validation errors, delays, more scrutiny, and possible rejection. At a live Orange List border check, a wrong status means illegal transport - the carrier is fined first.
Related DIWASS resources
What is DIWASS? →
Start here: what DIWASS is, who must register, and how a shipment works end to end.
DIWASS compliance →
How to stay compliant: obligations per party, enforcement, and the common pitfalls.
DIWASS Guide - dates & full FAQ →
The complete reference: key dates, the full FAQ, and a glossary of DIWASS terms.
Wasteform - EU waste documents →
Annex VII, IA, IB and national waste transfer forms, DIWASS-native.
Meeting every DIWASS requirement, automatically.
Evreka maps your shipment data to DIWASS fields, files on time, and keeps every chain partner in sync - from first registration to final completion certificate.