Shipping and customs document processing

• Every document is read as it arrives, from any channel, and its key fields are extracted: parties, goods descriptions, quantities, weights, values, currency, Incoterm and origin.
• Documents are cross-checked against each other, and against the booking, before the goods arrive. Mismatches go to operations with the exact fields that disagree, so the shipper is chased days earlier.
• Each line gets suggested commodity codes, with the reasoning, the alternatives considered, and any previous confirmed code for the same product. The customs specialist decides.
• Lines that may need extra controls are flagged: SPS goods under the Border Target Operating Model, licensable goods, CBAM goods, and preference claims that need proof of origin.
• The declaration is drafted in the customs software, ready for the specialist to check, complete and submit. Nothing reaches CDS without a person.
• Every suggestion, the specialist's decision and the reason for any change are logged, so the forwarder can show HMRC how each declaration was made.

• HMRCCustoms Declaration Service and customs debt liability
  →

  CDS is now the only route for UK customs declarations; the legacy CHIEF system has closed. The declaration stays the forwarder's legal act. As an indirect representative, the forwarder shares liability for duty and import VAT, so the AI drafts and a named specialist submits through the existing customs software. The AI never talks to CDS directly.

• HMRCUK Trade Tariff, classification and Advance Tariff Rulings
  →

  The AI suggests commodity codes from the current tariff and the forwarder's own confirmed history, and shows its reasoning. The specialist confirms. For high-value or disputed products, the design prompts the client to apply for an Advance Tariff Ruling (or a Binding Tariff Information decision for Northern Ireland), generally valid for three years, and records the ruling against the product.

• Defra, APHA and port healthBorder Target Operating Model (SPS imports)
  →

  Animal products, plants and some food need pre-notification in IPAFFS and health certificates, with checks based on risk category. The AI flags lines whose commodity codes suggest SPS controls and checks a certificate is present. It never decides a risk category, and the rules are held as configuration, because they are changing.

• HMRCWindsor Framework (GB to Northern Ireland movements)
  →

  Goods moved from Great Britain to Northern Ireland may move under the UK Internal Market Scheme if they are not at risk of entering the EU. The AI flags NI-bound consignments and the information the route needs. Whether goods qualify as not at risk is the specialist's decision, with evidence kept.

• HMRCUK carbon border adjustment mechanism (from 1 January 2027)
  →

  CBAM applies to imports of specified aluminium, cement, fertiliser, hydrogen, and iron and steel goods, identified by commodity code. The importer is liable, with a £50,000 registration threshold. The AI flags CBAM lines and the embedded-emissions data the client will need from its supplier.

• HMRCStandard for Customs Intermediaries (June 2026)
  →

  The voluntary standard, published with BSI, sets expectations for intermediaries, and HMRC has consulted on making registration mandatory. A logged, reviewable process for every declaration, with named people making each decision, is the kind of evidence it asks for.

• ICOUK GDPR and the Data Protection Act 2018
  →

  Shipping documents carry names, addresses and contact details, plus clients' commercially sensitive prices. That means a light DPIA, collecting only what's needed, a clear retention period aligned with customs record-keeping, UK processing where possible, and a contract that stops providers training their models on your data.

On a phone, the table shows the platform you pick. Sovereign / on-prem means open, portable components you can run in your own data centre or with a UK or European provider; IONOS is shown as one example, and others exist. What sovereign cloud means →

• A named customs specialist submits every declaration, and their name is on the audit record.
• Override reasons are captured whenever a specialist rejects a suggested code, and fed into the weekly review.
• A weekly sample of confirmed codes is checked by customs compliance, weighted towards high-duty, SPS and CBAM goods.
• Confirmed classifications become the client's product master, so the same product is never classified from scratch twice.
• A named owner for the tariff index, the SPS and CBAM rule sets, and every prompt, with change control.
• Operations and specialists trained before go-live, including what the AI can't see: goods it has never been shown, and documents that weren't sent.

1. 2–3 weeks

   Discovery

   Map today's process, measure the baseline, collect last quarter's real document bundles, and agree how drafts reach the customs software.

2. Gate · must be true to passBaseline agreed, customs software integration route confirmed, DPIA started, and customs compliance involved.

3. 6–8 weeks

   Pilot

   Imports for a handful of clients and one mode (for example, road freight from the EU), in shadow mode: the AI checks and suggests, specialists work as normal, and the two are compared.

4. Gate · must be true to passExtraction accuracy and code acceptance within agreed limits on real documents, and compliance sign-off.

5. 4–6 weeks

   Production

   Drafts go live for the pilot clients, with monitoring, support, the weekly sample review and a rollback plan.

6. Gate · must be true to passMonitoring, support model, rollback plan and specialist training in place.

7. Ongoing

   Scale

   Add modes, exports and clients one at a time, then reuse the pattern for SPS pre-notifications and CBAM reporting.

8. Gate · must be true to passEach new flow passes the same pilot gate.

R ResponsibleA AccountableC ConsultedI Informed· not involved

Where I'd fit

1. 1

   Goes wrong

   The demo used clean, typed invoices. Real bundles are scans, photos and invoices in other languages.

   How the design avoids it

   Pilot on last quarter's real bundles, every mode and every client in scope, not a curated sample.

2. 2

   Goes wrong

   Suggested codes get accepted without thought, and duty is underpaid for months.

   How the design avoids it

   Reasons and alternatives shown with every suggestion, a weekly compliance sample, and acceptance rates watched for signs of rubber-stamping.

3. 3

   Goes wrong

   Two documents disagree and the AI quietly picks one.

   How the design avoids it

   Mismatches are always raised to a person with both values shown. The AI never reconciles them on its own.

4. 4

   Goes wrong

   The tariff index goes stale and suggests codes or measures that have changed.

   How the design avoids it

   A scheduled refresh from the official tariff, a version stamp on every suggestion, and an alert if the refresh fails.

5. 5

   Goes wrong

   Someone wires the AI straight to CDS to save a step.

   How the design avoids it

   The customs software stays the only route to HMRC, and the agents' credentials can't submit anything.

1. From 1 January 2027
   The UK carbon border adjustment mechanism starts for specified aluminium, cement, fertiliser, hydrogen, and iron and steel goods. The first accounting period is calendar 2027, registration opens on 1 January 2028, and the first return and payment are due by 31 May 2028.

   Flag CBAM commodity codes now, and help clients ask their suppliers for embedded-emissions data before the first goods land.

2. Mid-2027 at the earliest
   A UK–EU SPS agreement. A draft text was reported in early November 2026 but isn't final. The government's stated aim is for it to take effect in mid-2027, removing most export health and phytosanitary certificates for GB–EU agrifood trade. Until then, the Border Target Operating Model applies.

   Hold SPS rules as configuration, not code, so the change is a rule update rather than a rebuild.

3. After the 2026 consultation
   Mandatory registration for customs intermediaries. HMRC consulted from June to September 2026 on making registration a condition of using its systems, alongside the voluntary Standard for Customs Intermediaries. No date has been set.

   Keep the audit trail of who decided what on every declaration, so it can support registration and compliance checks.

4. 2027 onwards
   The future of customs data. HMRC and HM Treasury's call for evidence (June to September 2026) asked about customs data and digital trade. The Single Trade Window was paused in late 2024 and HMRC has re-engaged with industry, with no launch date.

   Keep the extracted data in a clean, structured model of your own, so it can feed whatever submission route comes next.