Digitoll moves critical customs and transport information earlier in the process. The main challenge is therefore not only system connectivity, but getting complete, linked and validated data ready before goods reach the border.
In brief
- Digital notification and disclosure become mandatory on 15 September 2026.
- From 1 March 2027, declarations must be submitted no later than at the border crossing, and the direct transport scheme ends.
- Readiness depends on responsibilities, linked messages, timely source data and a controlled exception process.
Norwegian Customs is making digital notification and disclosure mandatory from 15 September 2026. From 1 March 2027, declarations must be submitted no later than at the border crossing, and the direct transport scheme will be discontinued.
This changes more than the submission channel. It changes when information must be available, who depends on it and how errors can affect the physical movement of goods.
For customs and logistics operations, Digitoll is therefore a data-flow and exception-handling challenge before it is an integration project.
The deadline exposes upstream problems
A customs declaration is rarely built from one complete source. Relevant data may arrive through commercial invoices, packing lists, transport documents, orders, master data and messages from several parties.
When a required field is missing, inconsistent or received too late, the problem is normally created upstream. The customs team sees the consequence, but cannot always resolve it alone.
Digitoll makes that dependency more visible because information about transport and goods must be submitted before, or no later than at, the border crossing. Norwegian Customs also requires messages to be linked so the authority can see the relationship between the transport, the consignments and the declaration.
The practical question is not only whether a system can send a message. It is whether the organisation can produce the right information, connect it correctly and handle exceptions in time.
Start by clarifying responsibility
Digitoll includes different obligations and message types. A business may be responsible for declarations, notification and disclosure messages, both, or neither. The answer depends on its role in the movement of goods and how it works with customs representatives and system providers.
That responsibility should be documented before technical work starts. For each transport flow, clarify:
- who owns the required information and who receives it first
- who validates and submits the declaration and messages
- how transport, master consignment, house consignment and declaration references are linked
- who resolves an error before the border crossing
Without this ownership map, an API connection can simply move incomplete data faster.
Build the data chain, not only the final message
A reliable Digitoll process starts before the customs system. The full chain should be mapped from document and order intake to the final declaration and transport messages.
- Source data: Which documents, messages and systems contain the required fields?
- Timing: When is each source available relative to departure and border crossing?
- Structure: Which information is already structured, and which must be extracted from documents?
- Validation: Which rules, lookups and cross-checks are needed before the data can be used?
- Linking: How are shipments, consignments, declarations and means of transport connected?
- Exceptions: What happens when information is missing, conflicting or changed late?
This is where much of the operational work sits. It is also where targeted automation can remove repetitive manual handling without replacing the existing Customs Management System.
Make exceptions part of the design
No customs workflow is fully standard. Suppliers use different document layouts. References can be missing. Quantities and weights may conflict. A transport can change after the declaration process has started.
A robust solution therefore needs two paths: a straight-through path for complete and validated data, and a controlled exception path for cases that require review.
The exception path should show the user what failed, where the value came from and what must be confirmed. This is more useful than a process that either stops without explanation or passes uncertain data into the next system.
Where automation can help
A controlled automation layer can support Digitoll readiness by:
- receiving invoices, packing lists, transport documents and order data
- identifying document types and relevant references
- extracting and structuring header and line-item data
- consolidating information from several sources
- applying validation rules and lookups
- routing incomplete or uncertain cases for review
- delivering approved data to the relevant CMS, TMS or backend process
The exact scope depends on the organisation’s role, systems and existing Digitoll setup. The aim is not to add another isolated system. It is to improve the flow of data into the systems and messages already used. See how the Edentri Platform captures, validates and delivers structured operational data.
A practical way to start
Do not begin with every flow, border crossing and exception at once. Select one representative flow with meaningful volume. Map the inputs, required fields, timing and exceptions. Test the process with real documents and operational users. Measure where manual work and delays remain. Then expand to additional document types, routes and customers.
This creates value earlier, limits the upfront investment and gives the business a working foundation that can be improved over time.
Digitoll readiness checklist
- Responsibilities are documented for each transport flow.
- Required data is available before the relevant deadline.
- Declarations and notification messages can be linked correctly.
- The submitting business has the required registration, authentication and certificates.
- Integrations have been tested with realistic data.
- Users know how to handle rejected messages and incomplete inputs.
- The exception process has a clear owner.
Digitoll readiness is achieved when the complete operating flow works — not when the first API call succeeds.
Frequently asked questions
When does Digitoll become mandatory?
Digital notification and disclosure become mandatory on 15 September 2026. From 1 March 2027, declarations must be submitted no later than at the border crossing, and the direct transport scheme will be discontinued.
Is Digitoll only an integration project?
No. Connectivity matters, but the operating model also needs timely source data, clear responsibilities, linked references, validation and exception handling.
Does Edentri replace the customs system?
Normally, no. Edentri can capture, structure and validate data before delivering approved output to an existing CMS, TMS or other operational system.
Prepare the data flow before the border
Edentri helps customs and logistics teams capture, validate and deliver structured data into their existing operational systems.
