The EIDR data flow starts with a record in your own commercial books and ends with a supplementary declaration that closes. EIDR, Entry in Declarant's Records, replaces the upfront submission to customs for standard, non-controlled goods. If you build or maintain customs tooling, this is the sequence of identifiers and data your systems need to handle.
The flow at a glance
Movement happens
-> Record in own books (EIDR created, via TSS or your own tooling)
-> LRN + MRN + procedure code passed to transporter
-> Goods movement reference created on GVMS
-> Goods arrive in Northern Ireland
-> Draft supplementary declaration appears in your account
-> Complete and submit by the 10th calendar day of the next month
-> Declaration closes
Identifiers to carry through
The Local Reference Number (LRN) is generated when the EIDR form is saved. If you created the EIDR yourself, hand that LRN to the haulier or intermediary handling the entry summary declaration. The Movement Reference Number (MRN) and the procedure code go to the transporter too. For a deeper walkthrough, see the TSS EIDR explained guide.
Data for the supplementary declaration
The supplementary declaration needs parties, goods and transport information. These come from commercial invoices, packing lists and transport documents. TSS pre-fills some fields from your EIDR, so store the original EIDR data in a form you can compare against.
Design notes
- Treat the LRN, MRN and procedure code as required fields on any hand-off to a transporter.
- Model the supplementary declaration as a dated obligation tied to the movement.
- Keep the trader as the accountable party in your data model, even when TSS submits. Want to see how iCustoms connects these steps? Watch a demo.
Top comments (0)