The Jersey Codes, pre-built.
The regulatory library's first jurisdiction: the JFSC Codes of Practice for Trust Company Business, Investment Business, Fund Services and Banking, and the AML/CFT/CPF Handbook, broken into obligations, mapped to the risk taxonomy and a starter set of controls, and kept current as the sources change.
What is in the library on day one.
- Source at jerseyfsc.org
Trust Company Business Code of Practice
Trust Company Business
- Source at jerseyfsc.org
Investment Business Code of Practice
Investment Business
- Source at jerseyfsc.org
Fund Services Business Code of Practice
Fund Services Business
- Source at jerseyfsc.org
Deposit-taking Business Code of Practice (the Banking Code)
Banking
- Source at jerseyfsc.org
AML/CFT/CPF Handbook
All supervised persons, incl. DNFBPs
Each source is broken into obligations by section, and each obligation is mapped to the risks it gives rise to and the controls that satisfy it. That structure is what a regulatory change is assessed against: when the JFSC amends a Code, the system flags it with a line-by-line diff of what moved, lists the obligations it touches, and the action to deal with it is one click away, with approval recorded and every affected entity alerted. Add your own obligations for internal policies and non-regulatory standards, and they sit in the same library, mapped to the same risks and controls.
Questions about the Jersey library.
- Which Jersey sources are pre-built in the regulatory library?
- The Jersey Codes of Practice for Trust Company Business, Investment Business, Fund Services Business and Banking, alongside the AML/CFT/CPF Handbook. Each source is broken into obligations, mapped to the risk taxonomy and to a starter set of controls, so a Jersey firm is assessing risk against real obligations from the first day rather than typing them in.
- What happens when the JFSC amends a Code or the Handbook?
- The system flags the change against the affected source with a line-by-line diff, lists the obligations it touches, and offers the action to deal with it one click away. Nothing changes silently: an obligation update goes through approval, and the action carries an owner and a deadline like any other. For a fund administrator or an outsourced compliance officer, the review is done once and the action is raised per entity where it applies.
- What about Guernsey, the Isle of Man and other jurisdictions?
- Jersey is pre-built today. Guernsey and the Isle of Man are next on the library roadmap, with further jurisdictions to follow. A new jurisdiction is a library expansion, not a new product: the risk taxonomy, controls and monitoring already know how to consume it, and a firm can add its own obligations for any source in the meantime.
- Can we add obligations the JFSC does not require?
- Yes. Internal policies, group standards and non-regulatory frameworks sit in the same library, mapped to the same risks and controls, so the coverage picture includes what you hold yourselves to as well as what the regulator requires.
From the library to the rest of the system.
- ModuleRegulatory library: pre-built obligations, kept current
- ModuleRisks: the taxonomy the obligations map to, scored against your appetite
- ModuleControls: mapped to the obligations they satisfy
- SolutionFor fund administrators & TCSPs: one library review, actions per entity
- SolutionFor AML-supervised businesses: the Handbook obligations at modular scope
- GuideRegulatory change without re-reading the Code
- GlossaryRegulatory change, defined
See the library running on your licences.
A 30-minute walkthrough using your entities, your licences and a real workflow you bring to the call. No slide deck.