Key Takeaways
- CERTEX went live on 13 April 2026 for GB–NI movements requiring CHEDs and COIs
- The system performs real-time automated verification of licences and certificates against issuing authority databases
- Three error triggers cause hard blocks: reference mismatch, commodity mismatch, and quantity exceeded
- No bypass mechanism exists — declarations cannot proceed until discrepancies are resolved
- CDS Update 5.1.0 deployed 28 March 2026 prepared the system for CERTEX integration
What Is CERTEX and Why It Matters Now
The EU Certificate Exchange System — CERTEX — went live on 13 April 2026 for goods moving from Great Britain to Northern Ireland. This is not a future change or a consultation. It is operational now, and it fundamentally alters how certificate and licence references are validated on CDS declarations for affected movements.
CERTEX is a digital infrastructure that performs automated verification of licences, health certificates, and official documents against source data held by issuing authorities. It operates as a validation layer within the customs clearance process for GB–NI movements, sitting between CDS submission and acceptance. Under the Windsor Framework, certain goods moving GB–NI require certificates issued by DAERA or other competent authorities. Before CERTEX, declarants entered certificate references manually and CDS performed only format checks. Now, CDS queries CERTEX in real time to confirm the certificate exists, matches the declared details, and has sufficient remaining quantity.
This matters because CERTEX failures are hard blocks. A declaration cannot proceed until the discrepancy is resolved. There is no override mechanism, no exception process, and no manual bypass available at the border. If CERTEX rejects your reference, your goods do not move.
For operators handling GB–NI movements involving live animals, plants subject to 100% physical checks, or Certificate of Inspection (COI) movements from Rest of World to Northern Ireland, CERTEX compliance is now a daily operational requirement. The system replaced the previous Automatic Licence Control System (ALCS) and represents a significant tightening of the validation layer behind CDS submission.
What Changed on 13 April 2026
Before CERTEX activation, GB–NI declarants entered certificate references into CDS and the system performed basic format validation. If the reference looked structurally correct, the declaration proceeded. Verification of whether the certificate actually existed, whether it covered the declared commodity, or whether the authorised quantity had been exhausted happened downstream — often after the goods had already moved.
CERTEX changes this by inserting a real-time verification step between CDS submission and acceptance. When a declarant enters a certificate reference, CDS now queries CERTEX, which in turn queries the issuing authority’s database. The system checks three things: that the certificate exists, that it matches the declaration details, and that sufficient quantity remains available.
This shift from declarant-attested references to automated verification means errors that previously might have been caught days or weeks later — or not at all — now surface immediately at submission. A mismatched prefix code, a wrong commodity code, or a certificate that has already been fully utilised will trigger a hard-block error. The declaration will not accept. The goods will not clear.
According to HMRC guidance circulated via BIFA on 18 March 2026, CDS Update 5.1.0 deployed on 28 March 2026 included the document, information, procedure, and location code updates necessary to prepare for CERTEX integration. The update also included changes to Appendix 5A of the Tariff Volume to align with the new validation requirements. The system experienced a scheduled outage from 20:00 on Saturday 28 March to 05:45 on Sunday 29 March to complete the deployment.
It is important to understand what has not changed. Traders apply for and receive licences and certificates from DAERA and other agencies exactly as before. The CDS declaration process itself — the data fields, the submission workflow, the response codes — remains unchanged. Only the validation layer behind submission has been tightened. CERTEX does not alter how you obtain certificates. It alters what happens when you reference them on a declaration.
Which Movements Are Affected
At go-live, CERTEX scope is limited but operationally significant. The system applies to GB–NI movements requiring the following documents:
CHEDs for live animals and plants subject to 100% physical checks. CHEDs (Common Health Entry Documents) are required for sanitary and phytosanitary (SPS) goods moving under the Windsor Framework. At CERTEX go-live, the system covers CHED-A (animals), CHED-P (plants), and CHED-D (animal products) where 100% physical checks are mandated. This includes live animals, certain plant products, and composite products containing animal-derived ingredients.
COIs for Rest of World to Northern Ireland movements. Certificates of Inspection (COIs) are required for organic products entering Northern Ireland from countries outside the UK and EU. CERTEX now validates these references in real time at CDS submission.
CERTEX does not yet apply to all GB–NI trade. General merchandise movements not requiring SPS certificates or COIs are unaffected. Similarly, EU imports into Great Britain do not fall within CERTEX scope at this stage. The system is specifically a GB–NI Windsor Framework implementation.
However, industry sources indicate that CERTEX scope is expected to expand. According to analysis published by Customs Declarations UK on 16 April 2026, the activation signals the broader direction of travel for automated verification across UK import controls. Operators in sectors beyond the current scope should monitor for announcements of additional certificate types being brought into the CERTEX validation net.
The Three Error Triggers
CERTEX validation failures fall into three distinct categories. Understanding each trigger — and how to avoid it — is essential for operators filing GB–NI declarations.
Reference Mismatch
The certificate reference entered on the CDS declaration must exactly match the reference held by the issuing authority. This includes prefix codes, separators, capitalisation, and any trailing characters. A reference that differs by even a single character will fail validation.
Common causes of reference mismatch include: omitting the prefix code (e.g. entering “12345” instead of “CHED-A-12345”), using incorrect separators (hyphens vs underscores vs spaces), mismatched capitalisation, or including extraneous characters such as trailing spaces or punctuation marks.
The fix is procedural: implement a certificate-insertion step in your declaration workflow where the reference is copied directly from the source document, not manually typed. Use copy-paste where possible. Where manual entry is unavoidable, implement a two-person verification step before submission.
Commodity Mismatch
A certificate may be valid but issued for a different commodity code than the one declared. CERTEX checks that the commodity code on the declaration matches the commodity code(s) covered by the certificate. A mismatch triggers a hard block.
This error commonly occurs when operators hold a certificate covering multiple commodity codes but declare against a code not included in the certificate schedule. It also occurs when commodity codes have been updated or reclassified and the certificate was issued against an earlier version.
The fix is to reconcile commodity codes before filing. Verify that the commodity code on your commercial documentation matches both the certificate schedule and the current UK Trade Tariff. Where certificates cover multiple codes, maintain a mapping document that links each certificate reference to its authorised commodity codes.
Quantity Exceeded
CERTEX tracks the total quantity authorised on each certificate and the cumulative quantity declared against it. If the declared quantity would exceed the authorised remaining balance, validation fails.
This error occurs when operators exhaust a certificate’s authorised quantity across multiple declarations without tracking the remaining balance. It also occurs when the certificate was issued for a specific quantity but the commercial shipment exceeds that quantity.
The fix is to maintain a certificate reconciliation log. For each certificate, track the authorised quantity, the quantity declared on each submission, and the remaining balance. Before filing, verify that the declared quantity does not exceed the remaining balance. Where shipments exceed certificate quantities, apply for additional certificates before filing.
Practical Steps for Compliance
CERTEX compliance requires procedural changes, not just technical adjustments. Operators should implement the following steps immediately:
Verify references before filing. Do not assume that a certificate reference entered correctly on previous declarations will work again. Verify each reference against the source document before every submission. Implement a pre-filing checklist that includes certificate reference verification as a mandatory step.
Build a certificate-insertion step into your workflow. Where possible, copy certificate references directly from source documents rather than typing them manually. Where manual entry is unavoidable, implement a two-person verification step. Consider barcode scanning or OCR solutions for high-volume operations.
Reconcile commodity codes and quantities. Maintain a mapping document that links each certificate reference to its authorised commodity codes and quantities. Update this document whenever new certificates are received or existing certificates are amended. Use this document as the source of truth for declaration filing.
Tighten document collection for agents. If you work with customs agents, ensure they receive certificate documentation well in advance of filing deadlines. Provide clear instructions on reference formatting and commodity code reconciliation. Require agents to confirm certificate verification before submission.
Monitor for CERTEX error codes. CDS response codes will indicate CERTEX validation failures. Train your team to recognise these codes and understand the required corrective action. Do not attempt to re-submit without resolving the underlying discrepancy — the error will recur.
Looking Ahead
CERTEX activation is the first step in a broader shift toward automated verification of import documentation. According to analysis by Customs Declarations UK, the system is expected to expand beyond its initial scope of CHEDs and COIs to cover additional certificate types and potentially additional trade routes.
Operators should prepare for this expansion by building robust certificate management processes now. Ensuring your EORI number and customs registration details are current will become even more important as CERTEX scope widens. The procedural discipline required for CERTEX compliance — reference verification, commodity code reconciliation, quantity tracking — will remain essential as the system grows. Sectors currently outside CERTEX scope should monitor for announcements of additional certificate types being brought into the validation net.
For now, the priority is operational stability. CERTEX went live on 13 April 2026. It is not a pilot. It is not optional. For GB–NI movements requiring CHEDs or COIs, CERTEX validation is a mandatory step between CDS submission and acceptance. Operators who adapt their workflows to accommodate this reality will avoid delays. Those who do not will face hard-block failures at the border.
Frequently Asked Questions
What happens if my CERTEX validation fails? Your CDS declaration will not accept. The goods cannot clear customs until the discrepancy is resolved. There is no bypass or override mechanism. You must correct the error — whether reference mismatch, commodity mismatch, or quantity exceeded — and re-submit.
Does CERTEX apply to EU imports into Great Britain? No. At go-live, CERTEX applies only to GB–NI movements requiring CHEDs (live animals, plants subject to 100% physical checks) and COIs (Rest of World to Northern Ireland). EU imports into GB are not within CERTEX scope.
Do I need to apply for certificates differently now? No. The process for obtaining certificates from DAERA and other competent authorities is unchanged. CERTEX affects only the validation step at CDS submission, not the certificate application process.
Can I override a CERTEX failure manually? No. CERTEX failures are hard blocks with no override mechanism. The declaration cannot proceed until the underlying discrepancy is resolved. Attempting to re-submit without correction will result in the same error.
Will CERTEX scope expand beyond CHEDs and COIs? Industry analysis indicates that CERTEX scope is expected to expand over time. The system represents the broader direction of travel for automated verification of import documentation. Operators should monitor HMRC and BIFA communications for announcements of additional certificate types being brought into the validation net.