Jersey regulator confirms changes to reliance and MLCO rules from 31 October
The Jersey Financial Services Commission published feedback on its consultation on the reliance and Money Laundering Compliance Officer regimes, with changes taking effect on 31 October 2026.
On 21 October 2026 the Jersey Financial Services Commission (JFSC) published feedback on its consultation about changes to the reliance regime and the Money Laundering Compliance Officer (MLCO) regime. The JFSC said the changes aim to lower compliance costs and complexity while keeping financial crime controls and international obligations in place. It said they support the financial services competitiveness programme developed with the Government of Jersey.
For the MLCO regime, the JFSC will add guidance on when an MLCO may not need to be appointed. Firms must still keep appropriate compliance monitoring arrangements even without an MLCO. The JFSC decided against fixed size thresholds for MLCO appointments, saying size alone is not a reliable measure across sectors and business models.
For reliance, which lets a firm depend on another party's customer due diligence, the JFSC is moving to a risk-based approach. Written assurance will be enough for lower-risk arrangements, while higher-risk relationships will need additional measures to meet a new "adequate steps" requirement. Testing is one possible measure but is not mandatory. Up to five working days will generally count as "without delay" when obtaining identity evidence through reliance arrangements, and there will be additional guidance on group reliance.
The remaining MLCO changes and the reliance changes take effect on 31 October 2026, and the JFSC will update its website and supporting materials on 2 November 2026. From 2 November 2026 to 31 January 2027, AML service providers can submit one-off MLCO notifications in bulk for multiple client firms. From 1 February 2027 they should use the MLCO notification form for any client firm not already notified.
Why it matters to AML professionals
Reliance lets firms avoid repeating customer due diligence, but the relying firm usually keeps responsibility if the checks were poor. A risk-based approach means compliance teams must decide which reliance arrangements are higher risk and what extra steps they take, and record that reasoning. Firms that decide not to appoint an MLCO still need someone monitoring compliance.
Red flags in this case
- A relied-upon third party that cannot produce identity evidence promptly when asked
- Reliance arrangements with introducers in higher-risk jurisdictions or sectors supported only by a written assurance
- Customer files where due diligence was obtained through reliance but key ownership information is missing
- No named person or function monitoring AML compliance in a firm that has not appointed an MLCO
If this landed in your queue
- List the firm's reliance arrangements and rate each as lower or higher risk
- For higher-risk arrangements, set and record additional steps, such as sample testing of the third party's files
- Check that identity evidence obtained through reliance can be produced within the expected time
- If no MLCO is appointed, confirm the alternative compliance monitoring arrangements and notification to the JFSC
Key terms
- Reliance
- When a firm uses customer due diligence already carried out by another regulated party instead of repeating it.
- MLCO
- Money Laundering Compliance Officer, the person responsible for monitoring a firm's compliance with AML requirements.
Interview angle
What are the risks of relying on a third party's customer due diligence?
Mention that responsibility usually stays with the relying firm, the need to assess the third party's standards, get documents promptly, and apply extra checks for higher-risk arrangements.
Sources
Go deeper on AMLift
Every fact in AMLift News Desk stories comes from an official source: a regulator, court, government gazette or the company's own filing.
Report an error
Every report is checked against the official source. If we got something wrong, the story is corrected.