Regulatory Guidance Notes
This page explains how the guidance layer should be read across the site. Framework pages define the structure, category pages explain activity scope, circulars set out targeted expectations or operational updates, and guidance notes help interpret how those pieces work together in practice. In plain English: this is the “how to read the map” page, so nobody drives into the lake because they misunderstood a label.
How to read the framework materials together
Different parts of the site answer different questions. The cleanest way to use the site is to know which page type answers which kind of problem.
Framework pages
These explain site-level structure, scope, category architecture, application stages, and how the licensing model is organized across activity types.
Guidance pages
These explain the supervisory logic behind control expectations: AML, custody, market conduct, governance, resilience, outsourcing, reporting, and related topics.
Circulars & notices
These provide targeted operational interpretation, updates, publication standards, branding expectations, reporting notes, or other focused directions.
Verification & register pages
These support due diligence and public record visibility. They are not substitutes for legal advice, enhanced diligence, or internal counterparty review.
The best reading order is usually: first identify the activity model and category logic, then review the relevant guidance modules, then check whether circulars or notices refine that topic. That sequence avoids the classic mistake of applying control depth before confirming what activity is actually being assessed.
- Identify the real operating model before interpreting controls.
- Use guidance to understand why expectations scale the way they do.
- Use circulars to confirm whether targeted clarifications apply.
- Keep evidence ready because interpretation without evidence is just academic cardio.
Guidance pages are interpretive and thematic. Circulars are more targeted and can refine an issue more precisely. Framework pages establish structure and scope. In practical use, the materials should be read as complementary layers, not competing documents.
- Framework pages explain the “what.”
- Guidance pages explain much of the “why” and “how.”
- Circulars often sharpen the “apply it this way” part.
- Register pages support public verification, not interpretive control analysis.
The same guidance logic can apply differently depending on activity scope, custody exposure, transaction complexity, client base, and outsourcing profile.
However elegant the guidance reading is, the supervisory question usually becomes: where is the policy, owner, log, review trail, and operating evidence?
Targeted circulars, register publication standards, or operational notes can sharpen specific expectations, so firms should review the guidance layer dynamically, not once and then ghost it forever.
Most common interpretation mistake
The classic mistake is reading one guidance page in isolation and treating it like the whole regulatory universe. It is not. The site works best when the framework, topic guidance, circulars, and public-record tools are read as layers that each do a different job.
Guidance sequence complete
The guidance layer is now covered. The clean next move is either to return to the Guidance Overview page or continue with any remaining framework or requirements pages you want built next.