Wise EDI Connector

The Centara eMessaging Connector for Wise EDI enables bidirectional exchange of customs documents between Business Central and the Icelandic customs authority (Tollur) — directly through CentaraIQ’s eDelivery platform.

Why this matters

Traditionally, exchanging customs declarations with Tollur requires an X.400 connection — a legacy messaging protocol that means:

• A dedicated X.400 subscription with a provider
• Long setup process (weeks to months)
• Expensive monthly fees
• Separate infrastructure to maintain

With the Wise EDI Connector, you skip all of that. Your customs declarations flow through CentaraIQ’s eDelivery platform using the address o=centara;a=isholf;c=is. You connect with your kennitala and start transmitting immediately — no X.400 subscription, no special EDI connection, no waiting.

How it works

The connector plugs into Business Central’s TOLL (customs declaration) framework as a file handler. When the TOLL module creates a customs declaration, it automatically routes through CentaraIQ instead of requiring a direct X.400 connection.

Sending customs declarations

1. The TOLL framework in Business Central creates a customs declaration
2. The connector picks it up automatically (registered as a TOLL file handler)
3. The declaration is written to the Centara Messages table, encoded, and sent to CentaraIQ
4. CentaraIQ delivers it to the customs authority via its X.400 gateway as a SKOT message
5. The outbound message is logged with a unique tracking ID

Receiving customs responses

1. The customs authority sends a response (approval, rejection, query)
2. CentaraIQ receives it and creates an inbound message in the Centara Messages table
3. The connector automatically detects the customs response and forwards it as a SKOT message to the TOLL framework
4. The response is decoded and passed to the TOLL module for processing
5. On success, the message status is set to Imported

Automatic retry

If an inbound response fails to process (e.g., the TOLL module can’t parse it), the connector retries automatically up to the configured maximum. Each attempt is logged with error details for debugging.

Attempt	Status
First failure	Error (re-trying)
Subsequent failures	Error (re-trying), counter incremented
Max retries reached	Error (final)

Setup

1. Enable the connector

1. Open Centara Setup in Business Central
2. Enable Wise EDI Connector

That’s it — no X.400 provider to set up, no special network configuration.

2. Configure your customs identity

1. Open TOLL EDI Setup in Business Central
2. Set your X400 Id — this is your sender party code (your kennitala-based address)

3. Verify connectivity

Send a test declaration through the TOLL module. Check the message log in Centara Setup to confirm delivery.

Configuration reference

Setting	Location	Purpose
Wise EDI Connector Enabled	Centara Setup	Master on/off switch
Web Service URL	Centara Setup	CentaraIQ endpoint (pre-configured)
Max retries of message sent	Centara Setup	Retry limit for inbound processing failures
X400 Id	TOLL EDI Setup	Your sender party code (kennitala-based)

Message tracking

Every customs message — inbound and outbound — is stored as a message record with:

• Direction — Outbound (declaration) or Inbound (response)
• Status — Sent, Imported, Error (re-trying), Error (final)
• Error details — Full error text when processing fails
• Retry count — Number of processing attempts for inbound messages
• Tracking GUID — Unique identifier for tracing through CentaraIQ

Supported document types

Type	Direction	Description
Customs Declaration	Outbound	Declarations sent to Tollur
Customs Response	Inbound	Responses from Tollur (approvals, rejections, queries)

Requirements

Dependency	Minimum version
Business Central	27.0
Centara eMessaging	1.19.0
TOLL Module	Required

Related documentation

• eMessaging Overview — the core Centara platform
• Supported Formats — all formats supported by CentaraIQ eDelivery