CBAM group controls for imports through multiple EU Member States

Start with the entity, then reconcile the movement

Regulation 2023/956 Article 17(1) places authorisation with the competent authority of the establishment Member State and says the status is recognised in all Member States. Article 16 assigns an account number to each authorised declarant. Neither provision creates a corporate-group account merely because several subsidiaries share a finance team.

A port of entry, broker, importer, representative and authorised declarant are not interchangeable keys. Build the operating view around their evidenced relationships. An entity importing through two Member States should not acquire two disconnected annual populations; two entities using one broker should not silently become one population. The legal actor assessment remains a separate review, not an inference from a spreadsheet grouping.

Maintain an entity–movement–representation matrix

Use stable internal references while preserving source identifiers exactly as received. This is a proposed reconciliation model, not an official customs or Registry schema. It adds relationship evidence to identifiers rather than assuming a name match proves responsibility.

Do not infer representation from who supplied the file

Union Customs Code Article 18 distinguishes direct representation, in the name and on behalf of another person, from indirect representation, in the representative’s own name but on behalf of another person. A broker logo on an export establishes neither capacity. Article 19 addresses declaration of that capacity and empowerment evidence.

The customs broker representation model belongs with the underlying mandate review. Regulation 2023/956 Article 5(1a) conditions the appointed indirect representative’s CBAM role on agreement to act, with a separate rule in Article 5(2) for importers not established in a Member State. Preserve the facts and obtain the applicable assessment instead of assigning every broker the same CBAM role.

Where a central team prepares material or submits on another declarant’s behalf, Article 5(7a) leaves the authorised declarant responsible. Show who prepares, reviews and performs the official action without suggesting responsibilities are pooled at group level.

Reconcile source rows before adding country totals

Retain raw extracts and build a candidate identity key from available declaration, item, entity and source context. Do not call that an official universal unique identifier. A reused declaration reference, an amendment and a repeated delivery can look similar; resolving them requires source evidence.

Mark each row as accepted-current, superseded, duplicate-copy or unresolved. Preserve links between versions, with the reason and reviewer for exclusion from the accepted view. A cancelled source row is not an instruction to erase its history. An amendment changes the current population only after its relationship to the earlier row has been established.

Run two reconciliations: every source row needs a disposition, and every accepted movement needs an entity and actor mapping. An unresolved row remains visible in an exception subtotal and completeness bridge, even though it is not allocated to a settled entity total. Excluding it from settled totals must not hide possible exposure.

Work a two-entity, two-country exception case

This synthetic case concerns quantity reconciliation only; it makes no threshold or liability conclusion. ENTITY-A uses entry countries NL and DE, while ENTITY-B also uses DE. Three broker deliveries contain six rows. Quantities are invented tonnes, not real customs records.

The delivered rows sum to 105 t, which is not an import total. Removing the superseded 24 t and repeated 22 t leaves 59 t of current movement candidates. Of that, 52 t is entity-mapped: 40 t to A and 12 t to B. The remaining 7 t stays visible and unallocated. The bridge is 105 − 24 − 22 = 59 = 52 + 7.

If W is later evidenced as B’s movement, preserve the resolution event and move 7 t from unresolved to B; the movement population stays 59 t. Do not record an additional shipment on the date the mapping was repaired.

Keep group visibility separate from entity decisions

Show country and broker drill-downs as completeness controls. Apply the importer-year threshold review on its proper legal basis, using the dedicated threshold guidance rather than resetting the assessment at each border or pooling separate importers because they share a parent. An unresolved importer identity prevents a reliable entity-level assessment.

A local procedure tracker should distinguish EU legal sources from Member-State access instructions, correspondence and administrative steps. Record who checked the current official NCA page and which question remains unanswered. This is more defensible than a universal country checklist assembled from undated broker advice.

Once the population is stable, the Registry module handoff map connects the responsible actor’s records to the appropriate official workflow. There is no implied automatic feed from this proposed matrix into the Registry.

Make sign-off explain settled and unsettled work

Recommended sign-off fields are extract coverage, source-row disposition counts, accepted quantities by entity, unresolved quantities, representation exceptions, reviewer and next action date. The cadence is an internal recommendation, not a statutory reporting interval. Require an explanation for an unexpectedly empty feed as well as one containing duplicates.

Pass the accepted population and exception bridge together to the first financial close controls. Finance needs to know whether a change is a new movement, a source amendment or an identity resolution. A total without that distinction cannot support an intelligible change explanation.

The outcome is a traceable group-to-entity reconciliation, not certification of legal responsibilities. Preserve disputed mappings and refer legal or customs questions to an appropriate qualified reviewer before official reliance.