DEV Community

Cover image for Designing an NCTS Phase 5 Declaration Workflow That Does Not Break at the Border
iCustoms
iCustoms

Posted on

Designing an NCTS Phase 5 Declaration Workflow That Does Not Break at the Border

Workflow shape

Phase 5's rejection pattern is upstream by design. A workflow that validates house consignment structure, commodity codes, GRN state and party EORIs before IE015 leaves your system is cheaper than one that reacts to IE056 after submission.

Checkpoints

  1. Manifest ingestion → build consignment and house consignment tree.
  2. Line normalisation → force six-digit HS codes.
  3. Guarantee check → confirm GRN, access code, EORI and available balance.
  4. Party validation → verify EORI shape and status.
  5. Optional safety and security → only when the full dataset is present. The end-to-end sequence is captured in the iCustoms NCTS Phase 5 declaration process guide.

Retries and dead letters

Route IE055 and IE056 into a queue with the field pointer parsed. IE051 is a policy decision by the office of departure, not a retry candidate — surface it to a human.

Ship it

Watch a demo to see how the workflow behaves under real traffic.

Top comments (0)