Functionalities
- Purpose
- Licenses overview
- Core data model
- Monitoring Scope
- Drill-down to declarations
- Declaration API
- License Details Page
Purpose
The Monitoring functionality allows a BzCtrl. User to define the quantitative and/or financial scope of a customs licence, authorisation or other customs-related permit and continuously monitor the extent to which that scope has been consumed.
The functionality must support, in particular:
- Inward Processing authorisations;
- End Use authorisations;
- AGRIM/import licences;
- other licences or authorisations where quantities and/or values are limited;
- automated consumption of the available scope based on customs declarations;
- manual and API-based input;
- aggregation of multiple declarations into monitoring totals;
- drill-down from an aggregate figure to the underlying declarations;
- storage of supporting documentation;
- configurable threshold notifications.
The core principle is:
Authorised scope → actual declarations → calculated consumption → remaining scope → evidence/documentation
The Monitoring functionality should therefore provide both an operational overview and an auditable trail.
Licenses overview
Core data model
A Monitoring record consists of an authorisation/licence and one or more defined monitoring scopes.
The basic hierarchy is:
A Product is an existing BzCtrl master-data object, referring to the Taric service.
A Product may therefore occur in multiple monitoring scopes, depending on the authorisation.
The scope must support the relevant dimensions required by the particular licence. Not every monitoring record necessarily has both a quantity and a value limitation.
Monitoring Scope
A License can contain one or multiple scopes.
Example:
Product: Ethanol Tariff Heading: 2207 1000 Quantity: 500,000 HL
The scope must be capable of being defined at the appropriate product/tariff level.
Example including declaration level
Example sum on Licensed Product level (level relevant to Impala)
Drill-down to declarations
When a User clicks an aggregate monitoring figure, BzCtrl displays the transactions that make up that figure.
Example:
Monitoring / IP-2026-001 / Gas Oil / 2707 September 2026 ────────────────────────────────────────────────────────────────────────────── 7 declarations Total: 70,000 MT Value: €67,000,000 Date MRN Quantity Customs Value Source ────────────────────────────────────────────────────────────────────────────── 02 Sep 26NL001... 10,000 MT €9,000,000 SAP 05 Sep 26NL002... 10,000 MT €9,500,000 SAP 08 Sep 26NL003... 10,000 MT €9,700,000 Descartes 12 Sep 26NL004... 10,000 MT €9,300,000 SAP 17 Sep 26NL005... 10,000 MT €9,600,000 SAP 23 Sep 26NL006... 10,000 MT €9,900,000 SAP 29 Sep 26NL007... 10,000 MT €10,000,000 SAP ────────────────────────────────────────────────────────────────────────────── TOTAL 70,000 MT €67,000,000 [ Documents ] [ Export ] [ Back ]
This page provides the reconciliation between the Monitoring Overview and the underlying declarations.
Declaration API
Because declaration processes are increasingly automated, BzCtrl should provide an API through which external declaration systems can submit declaration information.
The API should be system-neutral.
Potential source systems include:
- SAP;
- Oracle;
- customs management systems;
- customs brokers;
- terminal systems;
- other ERP/WMS systems.
The principle is:
External Declaration System │ │ API ▼ BzCtrl Declaration │ ▼ Monitoring Engine │ ▼ Monitoring Overview
The API should allow the source system to provide structured declaration data.
It should also support, where technically appropriate, the original declaration/message so that BzCtrl can retain the source evidence and/or extract the relevant monitoring data.
The source system should provide a unique reference so that duplicate messages can be detected.
Minimum data
| Field | Description |
|---|---|
| Source system | Originating system |
| Source reference | Unique source-system reference |
| MRN | Customs declaration reference |
| Declaration date | Date/time |
| Legal entity | Relevant entity |
| EORI | Relevant EORI |
| Procedure | Customs procedure |
| Product | Commodity code |
| Quantity | Declared quantity |
| Quantity unit | MT, KG, L, etc. |
| Customs value | Customs value in EUR |
| Original declaration | Optional original declaration/message |
License Details Page
