Assessment
Entry in the declarant’s records
Entry in the declarant’s records (EIDR), known in Spain as EIR, integrates the customs declaration into the company’s electronic system, under customs authorisation and supervision. It replaced Spain’s former customs domiciliation procedure, a national scheme, and can be used when the business lodges its own declarations or through a representative.
The NCLE entry triggers the workflow set out in the authorisation: the I2 notification (or its waiver) and then the supplementary declaration.
The key is to organise each stage properly so you lose neither traceability, nor time, nor control over what actually happens.
We design a clear workflow linking the record, the notification, the release of goods and the supplementary declaration.
The goods are at a location covered by the authorisation.
The company enters the declaration data in its electronic records.
The I2 notification is lodged, unless waived, and the release of the goods is managed.
The operation is completed with the applicable supplementary declaration.
EIR adds value when systems, people and procedure all work in line with what has been authorised.
Defines the scope of the operation.
Allow every operation to be tracked and controlled.
Clearly defined owners and procedures.
Including the conditions set by Customs.
The declaration is built into the normal workflow.
It can speed up release where a waiver has been authorised.
It connects data, owners and evidence within a single workflow.
It makes handling higher volumes easier without losing visibility.
EIR works best when the team can clearly see what happens at each step: the record, the I2 notification, declaration type Z / V and the supplementary declaration.
The workflow is triggered and the operation is recorded.
The notification accompanies the release, unless a waiver applies.
The declaration follows on in whichever format the operation requires.
Traceability is closed out with the applicable supplementary declaration.
It is worth exploring when transaction volumes, recurring operations or organisational needs justify reviewing how declarations are made. The decision also depends on data quality, internal controls and the team’s ability to maintain the system. Entry in the declarant’s records requires authorisation, and its value must be assessed for the specific operation rather than treated as an automatic benefit. We compare the current workflow with the requirements of the model. For an initial assessment, tell us about your flows, how often you operate and where records or coordination become difficult.
Start by identifying what information exists, where it is held and how it relates to each transaction. We review goods data, commercial documents, movements and declarations to check that they can be traced consistently. With entry in the declarant’s records, declaration particulars must be available to customs in the declarant’s system when the declaration is lodged through the entry. The specific preparation depends on the authorised scope. To assess your position, send us a sample of records and tell us how you currently detect incomplete data or discrepancies.
Responsibilities must be defined according to who holds the authorisation, who acts as declarant and the form of representation involved. External support does not replace the obligations that apply to each party. When preparing the model, it is necessary to specify who makes entries, who checks the information, who handles communications and who resolves exceptions. Customs retains its supervisory and control functions. To assess the arrangement, we need to understand your current representation structure and the people or teams involved at each stage of the operation.
Implementation is prepared in stages, starting with a review of the operation and the gaps that need to be addressed. Records, responsibilities and controls are then defined, and the workflow is checked using representative cases before it is put into use within the authorised framework. The stages and staff involvement required depend on the business’s starting point. It is sensible to plan who will handle normal activity while the change is prepared. To define a possible project, tell us about the current workflow and the availability of the teams involved.
There should be clear criteria for detecting a difference, preserving its traceability and deciding who needs to resolve it. Not every incident has the same effect: incomplete data, a documentary discrepancy and a system failure call for different responses. The procedure should allow the affected obligations and any necessary communications to be reviewed according to the authorisation and the circumstances. It is also useful to consider whether the problem recurs and which control needs adjusting. To assess ongoing support, we start with examples of incidents and how they are currently recorded and resolved.
Tell us how your operation works and we will review whether EIR is a good fit, what requirements you need to prepare and how to implement it.