DEV Community

Cover image for Building a Pre-Lodgement Checklist for CDS Filing
John Hall
John Hall

Posted on

Building a Pre-Lodgement Checklist for CDS Filing

Most CDS pre-lodgement errors are avoidable with a short, consistent checklist. The mistakes that cause hold-ups at the frontier tend to repeat across different agents and shipments, which makes them easy to guard against once identified.

What tends to go wrong

Filing a declaration as arrived when the port needs a pre-lodged entry, forgetting to build the MRN into a GMR before travel, a wrong expected arrival port or date, a missing arrival notification, and mismatched data between the declaration and the movement reference. These five account for most of the hold-ups agents actually see.

Turning that list into a checklist

Confirm which model the port uses, pre-lodged or arrived, before filing anything. Double-check the expected port and date against the actual movement. Build the MRN into the GMR before the vehicle travels, not after. Submit the arrival notification as its own step once the goods reach the border. Cross-check the declaration data against the movement reference before closing the job. This guide to CDS pre-lodged entry requirements covers the full data and process detail behind each step.

Why a checklist beats memory

Under time pressure, these are exactly the details that get skipped. A written checklist, run the same way every time, catches what a rushed manual process tends to miss.

Watch a demo

Top comments (0)