What Good NCTS6 Software Should Do Before a Declaration Is Submitted
A customs agent in Birmingham is preparing a NCTS6 transit declaration for machinery moving from Great Britain to Lille, France.
The commercial invoice is complete, the packing list shows 14 pallets, and the haulier has supplied the vehicle details. Everything appears ready—until the software flags three issues:
The consignee EORI cannot be validated.
The Guarantee Reference Number does not match the expected format.
The French office of destination is missing.
Without those checks, the declaration might simply be submitted and rejected later.
Good NCTS6 customs software should therefore do more than transmit data. It should help users identify incomplete, inconsistent or invalid information before submission.
What Should NCTS6 Software Check Before Filing?
A strong NCTS6 declaration workflow should examine four areas:
Completeness: Are all mandatory fields present?
Logic: Do the declaration details make sense together?
Reference data: Are codes and identifiers valid?
User review: Has a person checked the final declaration before submission?
This matters because NCTS declarations contain interconnected information about the goods, guarantee, parties, route and customs offices.
The UK's current NCTS6 system went live on 1 June 2026 for Common Transit movements.
1. Are All Mandatory Fields Complete?
Before an NCTS Declaration is transmitted, software should identify missing information.
Depending on the movement, this may include:
Declaration type
Local Reference Number
Holder of the procedure
Guarantee details
Goods information
Commodity codes
Package details
Office of departure
Offices of transit
Office of destination
Transport details
HMRC's transit rules distinguish between mandatory, optional and conditional declaration fields. Good software should apply those requirements automatically rather than relying on the user to remember every field.
2. Does the Declaration Make Logical Sense?
Completeness alone is not enough.
Imagine a T1 document UK to France where:
The route says Dover–Calais.
The office of transit belongs to another country.
The destination is in Lille.
The declaration contains no French border office.
Every field may technically contain data, but the overall movement does not make sense.
Logical validation should therefore ask:
Does the route match the customs offices?
Does the T1/T2 transit type fit the movement?
Are package totals consistent?
Do transport details match the planned journey?
Is the destination appropriate for the route?
Are required guarantee details present?
This is where T1 Declaration Software becomes more useful than a simple electronic form.
3. Can It Validate EORI, GRN and Commodity Information?
Reference-data validation is particularly important.
Good NCTS Customs Software should help check identifiers such as:
EORI numbers
Guarantee Reference Numbers
Commodity codes
Customs-office codes
Country codes
Guarantee details must be included on every applicable transit declaration. HMRC states that NCTS checks the quoted guarantee reference against the principal's identification and access code, and a failed guarantee validation can cause the declaration to be rejected.
That means a simple typo in a GRN can become a real departure delay.
4. Should Software Check the Commercial Documents Too?
Increasingly, yes.
Suppose the documents show:
Invoice: 22 pallets / 7,450 kg
Packing list: 22 pallets / 7,280 kg
CMR: 21 pallets / 7,450 kg
A useful pre-submission workflow should not simply copy one set of figures into the T1 Customs Declaration.
It should flag:
Weight mismatch
Package-count mismatch
The customs operator can then resolve the discrepancy before filing.
This is especially valuable when NCTS6 Software includes document extraction from:
Commercial invoices
Packing lists
CMRs
Transport documents
5. Can Reusable Data Reduce Mistakes?
For regular movements, much of the declaration may already be known.
A transit declaration UK to France may repeatedly use the same:
Exporter
Consignee
Guarantee
Office of departure
French route
Office of destination
Reusable party and commodity profiles can reduce repeated typing.
But software should still validate the reused information against the current shipment.
Yesterday's trailer, weight or consignee should never be assumed to be correct today.
6. What Should Happen Before the User Clicks Submit?
A good workflow should present a clear review stage.
For example:
✓ Mandatory fields complete
✓ EORI validated
✓ Guarantee checked
✓ Commodity data checked
⚠ Packing-list weight differs from CMR
⚠ Office of destination needs confirmation
The user can then resolve the two exceptions before filing.
This is much safer than discovering problems after the declaration has already been rejected.
Can NCTS6 Software Help with UK–EU Routes?
Yes, but the declaration should always reflect the actual route.
For example:
UK to France
A T1 document UK to France should reflect the correct GB departure, French office of transit and destination.
UK to Ireland
A T1 declaration UK to Ireland should include the correct Irish transit and destination information.
UK to Netherlands
A transit declaration UK to Netherlands may continue from Rotterdam to an inland authorised consignee.
UK to Belgium
A T1 document UK to Belgium should reflect the actual Belgian entry point and customs destination.
Ireland to Europe via UK Transit
Ireland to Europe via UK transit may use T2 where Union goods need to retain their customs status while crossing Great Britain.
Good validation software should help users build the declaration around the actual movement rather than simply copy a previous route.
Where Does Customs Declarations UK Fit?
Customs Declarations UK is one independent example of cloud-based NCTS software UK.
HMRC currently lists AJ Software Solutions Ltd, trading as Customs Declarations UK, among known NCTS software developers, while stating that it does not recommend or endorse any particular supplier.
Its NCTS6 platform states that it provides:
Real-time declaration validation
EORI, HS code and GRN checks
Reusable party and commodity profiles
Movement cloning
Bulk CSV and Excel upload
AI document processing
MRN receipt
Transit Accompanying Document generation
Departure and arrival workflows
The platform also says its Intelligent Document Processing can read invoices, packing lists and CMRs, flag conflicting values and prepare NCTS6 T1/T2 drafts for human review.
This illustrates how modern cloud customs technology is moving beyond simple declaration transmission toward document-led preparation plus pre-submission validation.
Who Benefits from Better Pre-Submission Checks?
NCTS software for customs agents can reduce rejected declarations across multiple customers.
NCTS software for freight forwarders can connect shipment and transport data with the transit filing.
NCTS software for hauliers can help ensure the vehicle, route and declaration information remain consistent.
NCTS software for importers and NCTS software for exporters can provide more control over repeat transit movements.
For businesses using NCTS for transport companies, earlier validation can mean fewer last-minute calls when the driver is already heading toward the border.
Quick NCTS6 Pre-Submission Checklist
Before clicking submit, ask:
Goods: Are descriptions, commodity codes, packages and weights complete?
Parties: Are consignor, consignee and EORI details correct?
Transit: Is the correct T1/T2 status selected?
Guarantee: Has the GRN and guarantee information been validated?
Route: Are the offices of departure, transit and destination correct?
Transport: Do the vehicle and container details match the actual movement?
Documents: Do the invoice, packing list and transport document agree?
Review: Has a user checked every warning and exception?
If the answer to any of these is “no,” the declaration is not ready.
Good NCTS6 Software Should Catch Problems Before Customs Does
Returning to the Birmingham-to-Lille shipment, the software caught the missing destination, questionable EORI and guarantee issue before the customs agent submitted the declaration.
The operator corrected the details, reviewed the final movement and only then filed it.
That is what good NCTS6 software should do.
The objective is not merely to send a T1 Declaration electronically. It is to improve the quality of the declaration before it reaches customs.
Cloud platforms such as Customs Declarations UK demonstrate how reusable reference data, document extraction, logical checks and user review can be connected within one workflow.
For modern UK–EU transit operations, the best automation happens before the declaration is submitted—not after it is rejected.

Comments
Post a Comment