Customs API integration for AES and NCTS
Export and transit declarations run through two systems: the Automated Export System (AES) for export and exit, and the New Computerised Transit System (NCTS) for goods moving under transit.
We integrate customs brokers' software with the customs API for both systems, so declarations go out from the tools the broker already uses and the customs responses come back into them.
Illustrative example
- Start
- Task
- Decision
- End
For customs brokers
You lodge export and transit declarations for your clients and want them to reach customs directly from your own software, without retyping them in a separate application.
We start from your current software and the declarations you lodge. Then we agree with you which messages to integrate first.
What the integration covers
Typical parts of a customs API integration. We agree the scope with you before we start.
Connection to the customs API
Access, authentication, and the message formats that AES and NCTS expect.
Declarations sent from your software
Export and transit declarations go out from the application you already use, checked before they are sent.
Customs responses back in your software
Acceptance, the MRN, rejections, and errors arrive where your team works.
Status of each movement
Where each export or transit movement is, and what it is waiting for.
How we engage
We build it as outsourcing or with our engineers in your team, with COST+ pricing.
Tell us what you want to build
Describe the product or process you have in mind. We will come back with questions and a first view of how we would approach it.