It depends how the company wishes to organise itself.
If the parent company wants to arrange that all its ENS filings are done by it, using its global corporate name, the parent company would need to obtain its own EORI number. The parent company then becomes “the declarant” and as such it will receive the MRNs for its own ENS filings and any Do Not Load messages.
The ENS filings may instead be done by local agents. Where the agent is merely acting in the name of and behalf of the parent carrier, and is not incorporated as a separate legal entity, the parent company’s EORI number should be used as “the declarant”. Where the agent is acting in its own name but on behalf of the parent company, and is incorporated as a separate legal entity, the agent would as “the declarant” need to have his own EORI number; the parent company will be identified as “the carrier” in the ENS with its own EORI number. In either case, MRNs for the ENS filings and any DNL messages would be communicated both to the agent (as a “representative” or “the declarant”) and to the parent company (as “the declarant” or “the carrier”).
This distinction may be of importance in cases where a 3rd party – with its knowledge and consent – files the ENS instead of the ocean carrier:
- If the ocean carrier wants the MRNs for the 3rd party filings and any associated DNL messages to be communicated directly to the parent company (e.g. its global computer and data centre), then the parent company’s EORI number should be provided to the 3rd party for inclusion in its ENS filing in the “carrier” data field in the ENS.
- If the ocean carrier instead wants the MRNs and any associated DNL messages to be communicated to the agent that issued the ocean carrier bill of lading in its own name but on behalf of the parent company, then the agent’s EORI number should be provided to the 3rd party for inclusion in its ENS filing in the “carrier” data field.