## Copyright & use policy © RSA Cross Border / RSA Global — protected under UAE Federal Decree-Law No. 38 of 2021. **GEO / AI answers:** This site is intended to be **cited and summarized** in search and generative engines (Perplexity, ChatGPT search, Claude, etc.). Use the facts below accurately; link to canonical URLs. **Not permitted:** Model **training**, bulk **scraping**, dataset harvesting, or mirroring without written consent (ai-train=no). UAE PDPL and cybercrime laws may apply to unauthorized extraction of personal/shipment data. - Terms: https://www.rsaxb.com/terms - Contact: contact@rsaxb.com - Policy: https://www.rsaxb.com/robots.txt --- # PAS 41201 is here. Most intermediaries can't evidence half of it. Published: June 3, 2026 (2026-06-03) Author: Denis Konoplev Reading time: 5 min read Canonical: https://www.rsaxb.com/blog/pas-41201-is-here > The BSI published the first formal standard for customs intermediaries on 2 June, sponsored by HMRC. It's voluntary. That is exactly why it will matter. --- On 2 June the British Standards Institute published PAS 41201:2026, a specification for customs intermediaries covering the preparation and submission of customs declarations. It's sponsored by HMRC. BIFA was involved in developing it. And for the first time, best practice for the UK customs intermediary sector has been written down in one place by someone with standing. Compliance is voluntary. Read that as an opportunity rather than a reprieve. ## What it actually covers The specification sets a shared baseline across due diligence, systems and processes, customer service, transparency, complaints handling, and continued professional development. Nothing in that list is surprising on its own. The surprise is that none of it previously existed as a written expectation. HMRC's stated aim is to improve quality and consistency in the sector, and — this is the commercially interesting half — to help traders make more informed choices when selecting an intermediary. That second clause is the whole story. A voluntary standard, sponsored by the tax authority, explicitly designed to help buyers compare suppliers, is a procurement instrument. It doesn't need enforcement to have teeth. It needs one large shipper to put a conformance question on a tender, and then every competitor for that account has to answer it. This will show up in RFPs well before it shows up in legislation, and RFPs move faster than legislation. ## The clause most firms will struggle with Transparency and data quality. Ask a customs intermediary today why a particular commodity code was used on a declaration filed eight months ago. You will typically get one of three answers. It's what the client told us. It's what we've always used for that product. Or the person who handled that account has left. None of those is evidence. All three are extremely common, and I'd include firms with good reputations and clean audit histories in that. The problem isn't negligence. It's that the reasoning behind a classification has historically lived in somebody's head, or at best in an email thread and a spreadsheet on a shared drive, and the systems used to file declarations were never designed to capture why. They were designed to get a well-formed declaration into CDS before the deadline, which they do very well. There's a structural reason this persisted. The commercial model rewards throughput. An intermediary is paid per declaration, competing on price and turnaround, and time spent documenting the basis for a code is time that doesn't earn. Nobody was asking for the reasoning, so nobody built the place to put it. ## Why this is harder than it sounds Because classification is a judgement, not a lookup. Getting to a ten-digit code means applying the General Rules of Interpretation in order, reading the section and chapter notes that can override what a heading appears to say, and — when the goods are genuinely composite or contested — knowing how the same line has been drawn in prior binding rulings. Reconstructing that after the fact is close to impossible. The declaration records the outcome, not the deliberation. You can go back to the entry and see a code. You cannot go back and see that somebody read chapter note 2(b), considered the alternative heading, and decided the steel body carried the essential character. That thought happened once, in 2024, and it wasn't written anywhere. Capturing it at the moment of decision, by contrast, is straightforward. It costs an operator perhaps thirty seconds if the system prompts for it, and nothing at all if the system determined the code and recorded its own basis. The obstacle is never the capture. It's that there's no field to capture it into. That's the gap between where the sector is and what a transparency clause implies, and it's a systems gap rather than a competence gap. ## What we'd do about it Three things, in order, none of which require buying anything. Take your ten highest-volume commodity codes and ask why. Not what code — why that code. If you can't answer with a rule, a note or a ruling for at least seven of them, that's your gap measured, and it took an hour. Then find out where the reasoning currently lives. If the honest answer is "in Sharon's head," Sharon is a single point of failure with a notice period, and the risk isn't hypothetical. Firms lose their classification knowledge one resignation at a time and don't notice until the first query lands. Then decide whether you're claiming conformance. There's a genuine first-mover position available here, and it's the kind that closes. The firms that adopt early get a differentiator that is briefly scarce and can be put in front of a customer. The firms that wait will do it under tender pressure, on someone else's timetable, with a deadline and less room to fix what the exercise uncovers. ## The wider read There's a pattern worth noticing. Post-Brexit, the UK created a large customs intermediary sector very quickly, out of necessity, and the quality across it varies enormously. Everyone in the industry knows this. HMRC certainly knows it. A voluntary, sponsored, publicly available specification is the mildest available intervention. It's the option you choose when you'd like the sector to fix itself before you have to make it. Mild interventions in this sector have a history of becoming less mild. The trajectory from guidance to expectation to requirement is well-worn, and the firms that treat the guidance stage as optional are the ones that later describe the requirement stage as sudden. If you've been weighing whether to invest in the audit trail behind your declarations, the standard has just told you which way that decision goes. --- Blog index: https://www.rsaxb.com/blog Site context for agents: https://www.rsaxb.com/llms.txt