What is the NCTS5 message flow?
The NCTS5 flow is message-based. The filer sends IE015 to the office of departure. On successful validation, the office returns the MRN and generates the Transit Accompanying Document. The movement stays under transit control until discharge confirmation.
Data model hierarchy
NCTS5 uses a three-tier consignment structure: consignment at the top, house consignments in the middle, and goods items nested inside. Every goods item requires a six-digit Harmonised System code. Filing a goods item without a house consignment above it fails validation immediately.
For the full NCTS transit declaration walkthrough, see how each layer maps to the underlying message structure.
Required references
- Authorised EORI matching user permissions
- Guarantee reference number and access code
- Office of departure, transit offices where applicable, office of destination
- Consignor and consignee for each house consignment ## Handling validation errors
Invalid IE015 messages return functional error responses with rule identifiers and field pointers. The response identifies the exact node that failed, allowing programmatic fixes before resubmission.
Test environment
HMRC's Transit Test Application supports full IE015 submission cycles without generating live rejections. Use it to validate new declaration flows or updated software integrations.
Want to see message-level automation for NCTS5? Watch a demo.
