You get fined first. Even when someone else made the error.
Carriers not registered in DIWASS cannot be selected by shippers - this is already in force for Orange List (hazardous) shipments. Without TMS or ERP integration, your planners manage DIWASS status manually - a separate portal login for every departure, every status update, every CMR. At scale, that breaks.
Registered
Your company has an active DIWASS account. Shippers can select you.
DIWASS ActiveAnnounced
Transport notification filed. You are linked as the carrier.
AnnouncedMoving
Driver confirmed departure. Status updated. Border check: ✓
In TransitReceived
Processor confirmed receipt. Your obligations complete.
ReceivedCompleted
Certificate issued. Administrative cycle closed.
CompletedWhat DIWASS means for carriers
Shippers can only choose registered carriers. If you're not in the system, they can't book you - and will go to a competitor who is.
Border controls check DIWASS live via plate recognition. Wrong status = illegal transport. Carrier is fined first.
The DIWASS notification ID must be on the CMR. Drivers need a reliable way to access and display it.
The document status must be "Moving" before the first wheel crosses the border. Manual portal update is not operationally scalable.
Never leave without a valid status
Carrier DIWASS onboarding
Full account setup, API client configuration, and operational go-live before your clients' first digital shipment.
Automatic status transitions
Announced → Moving triggered at driver departure. No manual portal login required from your planners.
Driver CMR support
DIWASS notification ID automatically available to drivers. Clear workflow for displaying it at border checks.
TMS / ERP work order sync
DIWASS status tied directly to your work orders. When a job dispatches in your TMS, the DIWASS notification is triggered. When the driver departs, Moving status updates automatically. No separate portal. No manual step between your system and DIWASS.
How many hours is manual DIWASS costing your team?
Every cross-border shipment requires a portal login, status update, and manual CMR check. At scale, this adds up fast.
Manual portal entry
Each shipment: login, enter transport data, submit notification, download DIWASS ID. Average: 8 minutes per shipment.
Status monitoring
Check Announced, update to Moving at departure, verify Received. Manual portal checks per shipment: 3-4 touchpoints.
With Evreka
All of this is a zero-touch background process. Status updates trigger automatically. DIWASS ID delivered to the driver without a portal visit.
Without TMS integration, DIWASS is a manual burden your planners carry for every shipment.
Every cross-border work order creates a DIWASS task: file the notification, trigger Moving status at departure, verify the DIWASS ID lands on the CMR. Without a direct connection to your TMS or ERP, that is a separate portal login for each one.
Evreka connects to your transport management system so DIWASS actions happen as part of your existing dispatch workflow - not alongside it.
Shippers are checking their carrier lists right now.
If your company is not in DIWASS, you cannot be selected - they'll book a registered competitor instead. Every day counts.