ZOLLI

Smart Border Austria · Corridor traffic

Customs declarations for the Smart Border Austria corridor.

We build your pre-notification, transmit it under your own USP Webservicekonto, and bring back the BTN and confirmation slip — before the truck reaches the border.

Request access How it works

The corridor wants the declaration before the truck arrives.

  • Before arrival, not at the barrier

    The declaration has to be lodged and confirmed before the vehicle arrives. Declare at the border and you wait.

  • The interface is not a web form

    CTW is a poll-based SOAP service behind a USP Webservicekonto. Messages have to be fetched; there are no callbacks.

  • A mistake costs standing time

    A rejected declaration comes back as a fault code, not an explanation. The vehicle waits until it is corrected.

What you get.

  • Declaration built and transmitted

    We build the pre-notification from your consignment data and transmit it to Austrian customs under your own Webservicekonto — validated against the official schemas before it leaves the building.

  • BTN and slip back

    The confirmation is correlated automatically. You get the BTN and the driver's confirmation slip without polling for it yourself.

  • Rejections in plain language

    If customs rejects the declaration, we tell you which field and why — instead of handing you a raw fault code.

How it works.

  1. Hand over the consignment

    By API from your TMS, or as a file. No new system for your dispatchers to learn.

  2. We transmit it

    The declaration goes to customs under your own Webservicekonto, the response is correlated, and the whole transaction is logged.

  3. The driver gets the slip

    BTN and confirmation slip come back to you before the vehicle reaches the corridor.

For integrators.

  • Official schemas, not reimplemented

    Messages are generated from the published XSDs and validated against them.

  • No message is lost

    Fetching from customs is destructive: once collected, a message is gone from their side. Every inbound message is therefore persisted before anything parses it.

  • Full transaction history

    Every transaction is kept as an event log. State is rebuilt from it rather than overwritten, so every change stays auditable.

  • Multi-tenant

    Multiple declarants and branches kept separate, each with its own credentials.

On the roadmap: NCTS 6 and AES on the same foundation.

Let's talk about your corridor traffic.

Questions about integration, credentials, or onboarding? Write to us.

d.kryvashei@zolli.ai