DIWASS compliance: obligations, enforcement, and a practical checklist.
The rules of cross-border waste shipment are not new - but under DIWASS the way they are applied is more controlled and far less forgiving. This guide covers what compliance means in practice, the obligations on each party, how enforcement works, where companies most often slip, and a checklist to stay on the right side of it.
What DIWASS compliance means now
DIWASS digitised the EU Waste Shipment Regulation, it did not rewrite it. Waste classification, traceability and the obligations of each party all still apply. What changed is enforcement: the data is checked by the system before a movement can proceed, and at the border by live database lookups rather than paper inspection.
In short, compliance now means being registered, submitting complete and consistent data on time through an approved channel, and confirming each status event in its window. The flexibility that paper allowed - filling gaps later, fixing things at the border - is gone.
Compliance obligations by party
Compliance is a chain. Each party carries its own obligation, and one weak link blocks the whole shipment.
Notifier / exporter
Files the notification with complete, correctly classified data before departure and ensures all named parties are registered.
Carrier
Must be registered to be selected, carry the DIWASS notification ID on the CMR, and have a live status before crossing the border.
Receiving facility
Confirms receipt in DIWASS within 3 working days of arrival; missing this triggers automatic alerts to the sender and the authority.
Broker / notifier
Keeps every client chain registered and consistent, working from one shared version of the shipment data.
Enforcement & what non-compliance costs
There is no fine schedule in the regulation text, but the operational consequences are immediate and concrete.
Compliance deadlines you can't miss
Common compliance pitfalls
Manual processes built on email and spreadsheets that DIWASS no longer accepts.
Documentation completed after the transport is arranged, not before.
Different parties working from different versions of the same shipment data.
Unclear responsibility - no one owns the notification or the status updates.
Last-minute shipments relying on flexibility that the digital system removed.
An unregistered chain partner who simply cannot be selected in DIWASS.
A practical DIWASS compliance checklist
Register your company - and verify every chain partner is registered too.
Sort out access credentials: EU Login, and eHerkenning level 3 for Dutch companies.
Map your Annex VII / IA / IB workflows: where data is created, shared and stored.
Decide portal vs API - integrate above a few shipments a month to avoid double entry.
Make one party own each notification and its status updates.
Build the timing into planning: submit before departure, confirm receipt within 3 days, close within 30.
DIWASS compliance, in short
What does DIWASS compliance mean?
Being registered, submitting complete and consistent data on time through an approved channel, keeping every partner registered, and confirming status events in their windows. The rules aren't new - enforcement is now digital and far less flexible.
What are the penalties for non-compliance?
Movements are blocked and delayed. For Orange List at a live border check, a wrong status means illegal transport - the carrier is fined first. Repeated errors increase authority scrutiny.
Who is responsible?
Every party: notifier for the notification, carrier for status and border documents, facility for confirming receipt in 3 working days, broker for the chains they manage. An unregistered party blocks the whole notification.
Where do companies most often fall out of compliance?
Email/spreadsheet processes, documents done after the transport is booked, mismatched data between parties, unclear ownership, last-minute shipments, and unregistered chain partners.
Related DIWASS resources
What is DIWASS? →
Start here: what DIWASS is, who must register, and how a shipment works end to end.
DIWASS requirements →
What data you must submit, when, and how - fields, documents, timing and technical setup.
DIWASS for carriers →
How carriers register, automate status updates, and get the DIWASS ID onto the CMR.
DIWASS Guide - dates & full FAQ →
The complete reference: key dates, the full FAQ, and a glossary of DIWASS terms.
Make DIWASS compliance the default, not a scramble.
Evreka keeps your data complete, your partners registered and your status events on time - so every shipment clears the system and the border the first time.