Short executive summary
A regulatory publication is not the same thing as an operational change. The useful review question is: what kind of document is this, what proposition has legal or supervisory significance, what was the verified prior position, what changed, who might be in scope, and what evidence would a reviewer need before changing a control?
Two September 2026 examples show the distinction. OSFI’s statement on tokenized deposits is framed as a clarification of a technology-neutral stance. FCA FS26/1 is a Feedback Statement that summarizes responses, reiterates principles and feeds planned roadmap work. Neither source supports a generic claim that a new tokenisation law came into force on its publication date.
The review chain
| Step | Question | Failure to avoid |
|---|---|---|
| Source | Authority, jurisdiction, exact title/version, URL and section? | Working from a social summary. |
| Status | Requirement, expectation, clarification, feedback, proposal or plan? | Calling every publication a new rule. |
| Scope | Which entity × instrument × activity × jurisdiction? | Using “tokenised” as the legal category. |
| Delta | Verified prior proposition → current proposition? | Inventing the baseline. |
| Impact | Which workflow might need review? | Turning a hypothesis into an authority requirement. |
| Evidence / owner | What object proves the review and who can decide? | Treating evidence found as compliance closure. |
Example 1 — OSFI: clarification is useful, but it is not blanket permission
OSFI’s 10 September 2026 Statement on Tokenized and Other Digitally Represented Deposits says it clarifies a technology-neutral stance under federal financial-institution legislation. The technology does not determine legal nature, and OSFI gives tokenized deposits as an example of deposits that are not legally distinct merely because of tokenisation.
This is not blanket permission for a particular product or launch. OSFI points institutions to applicable law and guidance, including B-13 Technology and Cyber Risk Management and B-10 Third-Party Risk Management, and says FIs are expected to engage their lead supervisors in advance of launching novel products or services.
Verified delta: B-13 (2022) and B-10 (2023) predate the statement. A prior tokenized-deposit-specific public OSFI baseline was not established in this review. The defensible outcome is clarification/reaffirmation; a new obligation from the 10 September statement itself is not established.
A synthetic / illustrative product-governance workflow might therefore request a legal-classification memo, product terms, B-13 technology/cyber evidence, B-10 third-party evidence and the relevant supervisory-engagement record. Those review objects do not prove the product is legally permissible or compliant.
Example 2 — FCA / Bank of England: feedback and planned work are not “rules now in force”
The May 2026 joint Call for Input set out initial principles and questions for industry. It was a consultation, not a former binding rulebook.
On 14 September the FCA published FS26/1. The full Feedback Statement summarizes feedback, reiterates regulatory principles, records authority responses and says firms should continue applying the existing prudential framework while further clarity is developed. The FCA also says the feedback will inform a joint roadmap later in 2026.
Verified delta: May → September is a publication-process comparison: Call for Input → Feedback Statement. The safe classification is feedback + reaffirmed principles + planned work. A new general obligation from FS26/1 itself is not established.
For a synthetic / illustrative wholesale-tokenisation programme, the next task is to map the actual entity, instrument and activity to the underlying rules, separate current requirements from roadmap items, and set a refresh trigger for the roadmap and consultations. A legally sensitive settlement-assets passage in FS26/1 is treated in this package only as a blocked research lead because its underlying conditions and amendment chain were not frozen here.
The Regulatory Change Impact File
The public-clean template separates source/evidence state, applicability review, implementation review and publication state. A publication date is not an effective date. Publication, adoption, entry into force, application/compliance date, transition end and consultation deadline are separate fields.
It also separates an authority-required requirement from an internal control hypothesis. Evidence found ≠ requirement identified ≠ control changed ≠ control effective ≠ compliance established.
Download the template: Download the Regulatory Change Impact File template (PDF)
The PDF is a public-clean review handoff: it contains the reusable template and clearly labelled synthetic / illustrative OSFI and FCA / Bank of England examples.
Common false inferences
- “Published” does not mean “new rule”. Classify the proposition, not only the cover.
- Consultation → feedback is not automatically law → law. Verify the underlying legal source.
- Tokenisation does not erase legal form. Review entity, instrument, activity and jurisdiction separately.
- Missing prior baseline means change not established. Do not manufacture a before/after story.
- Evidence is not closure. Implementation and effectiveness need their own records.
Questions for qualified owners
For Canada, the unresolved questions include the concrete instrument’s legal classification, the relevant entity/branch, material B-10/B-13 expectations and appropriate supervisory engagement. For the UK, they include the exact regulated activity and underlying rules, whether any referenced amendments are operative for the design, and which items remain roadmap or consultation work.
Those determinations belong with jurisdiction-appropriate regulatory counsel and the responsible compliance, risk, product or FMI owner.
Use the Impact File as a review handoff: start with the official source, record its status, freeze scope, verify the prior baseline, describe only potential workflow impact, and name the evidence and qualified owner required for the next decision.
Final caveat
This Brief is educational public-source issue spotting. It does not establish the legal classification, authorisation status, settlement finality, safeguarding sufficiency, accounting treatment, control effectiveness or compliance of any specific product or organization. Current-status claims are verified only as of the stated research/source-refresh dates and should be revalidated after material source updates.
Sources and notes
- OSFI — Statement on Tokenized and Other Digitally Represented Deposits
- OSFI — Guideline B-13
- OSFI — Guideline B-10
- FCA — FS26/1 landing page
- FCA — FS26/1 Feedback Statement PDF
- FCA / Bank of England — Joint Call for Input PDF
Treasury Desk Brief is educational public-source analysis. It is not investment, legal, tax, accounting or compliance advice.