Onboarding carries its own evidence
Sanctions and PEP screening, risk scoring and enhanced due diligence triggers run inside the workflow. No file reaches approval without its evidence attached.
What you have to evidence, and where it lives
Jersey firms rarely get caught by a missing control. They get caught by a control that exists on paper and cannot be produced on the day. Each JFSC obligation below is paired with the module that records the decision as the work happens.
| The JFSC obligation | Where CoreAdmin evidences it |
|---|---|
| Meet the seven principles of the Code of Practice for Trust Company Business, issued under Article 19 of the Financial Services (Jersey) Law 1998 | Compliance estateThe registers, risk assessments and monitoring programme run as one statutory-cited system, so a principle maps to a record rather than to a paragraph in a policy document. |
| Demonstrate adequate risk management systems, on demand rather than on notice | Compliance monitoringThe Business Risk Assessment, Customer Risk Assessment and Compliance Monitoring Programme sit in one closed loop, with tests scheduled, assigned and closed against their findings. |
| Appoint a compliance officer under Article 7 and a reporting officer under Article 8 of the Money Laundering (Jersey) Order 2008, and evidence the separation | Access rightsThe reporting lines, deputisation and role-specific permissions are enforced in software rather than described in a procedure, so the arrangement is documented, evidenced and testable. |
| Keep records for five years past the end of the relationship, under Article 20 of the Money Laundering (Jersey) Order 2008 | Audit reportsRecords are append-only: added, never quietly rewritten. The register and the underlying file cannot drift apart, because they are the same object. |
| Show who exercised judgement on an activity named in the Sound Business Policy, and on what basis | Client onboardingSensitive and reputationally risky activities are not prohibited, so the judgement stays with the firm. The file carries the reasoning and the named approver alongside the screening result. |
| Meet the AML/CFT/CPF Handbook standard: who did it, when, on what basis, and under which provision | Compliance estateEach decision is attributed to the individual who took it, with the version of the policy that applied at the time, so an old decision is judged against the rules that were in force. |
| Keep suspicious activity report content inside the reporting officer perimeter | SAR handlingReport content is visible only to the officers holding that capacity, so tipping-off discipline is a control you can show rather than a convention you rely on. |
Regulatory horizon scanning tracks change across 40 jurisdictions, weighted for your firm, with AI gap analysis run against your own policies and procedures.
Three places the difference shows up first
The registers leave Excel
The spreadsheets and Word policies most firms maintain by hand become one statutory-cited system with an append-only audit trail.
Board packs take hours, not weeks
Papers assemble from live data, minutes are drafted from the recording, and approval runs chair-then-directors to a signed, versioned record.
The detail, when you want it
Why generic trust software does not fit a Jersey firm
Search for trust company software and the results are almost entirely North American. Those products are built around US fiduciary practice: probate administration, court accountings, state tax filings and estate settlement. None of that is what a Jersey trustee is examined on.
- A Jersey trust company business is registered under the Financial Services (Jersey) Law 1998 and held to the JFSC's Code of Practice for Trust Company Business, issued under Article 19 of that Law. The Code is built on seven principles, running from conducting business with integrity to demonstrating adequate risk management systems and dealing with the JFSC openly, each supported by detailed rules.
- The JFSC's AML/CFT/CPF Handbook, covering the prevention of money laundering and the countering of terrorist financing and proliferation financing, sets what a supervised person has to be able to demonstrate. The standard is evidence on demand: who did it, when, on what basis, and under which provision. Records have to survive five years past the end of the relationship under Article 20 of the Money Laundering (Jersey) Order 2008.
- The JFSC's Sound Business Policy names the activities Jersey treats as sensitive or reputationally risky. They are not prohibited, which puts the judgement, and the record of who exercised it, back on the firm and its onboarding file.
- Because no imported system has a place for any of this, the registers, the risk assessments and the officer sign-offs end up in Excel and Word, maintained by hand, and reconstructed under examination.
CoreAdmin was written in Jersey against that rulebook. It is the difference between a system that stores your data and a system that knows what the record is for.
JFSC compliance software that keeps the officer in the decision
The failure mode Jersey firms get caught by is rarely a missing control. It is a control that exists on paper and cannot be evidenced on the day. CoreAdmin closes that gap by making the sign-off the thing that moves the work forward.
- Named-officer sign-off. AI drafts, extracts and screens. It never approves. Each decision is attributed to the individual who took it, with the version of the policy that applied at the time.
- MLRO and MLCO responsibilities separated in software. The Money Laundering (Jersey) Order 2008 requires a compliance officer under Article 7 and a reporting officer under Article 8. CoreAdmin enforces the reporting lines, deputisation and role-specific permissions rather than describing them in a procedure, so the arrangement is documented, evidenced and testable.
- A real SAR perimeter. Suspicious activity report content is visible only to the officers who hold that capacity, so tipping-off discipline is a control you can show rather than a convention you rely on.
- Append-only audit. Records are added, never quietly rewritten. The register and the underlying file cannot drift apart, because they are the same object.
- Segregation of duties and four eyes. Where a second pair of eyes is required, the workflow will not complete without them, and the second reviewer cannot be the first.
What CoreAdmin runs for a Jersey fiduciary business
Client onboarding. A structured new-business workflow with sanctions and PEP screening, risk scoring and enhanced due diligence triggers. No file reaches approval without its evidence attached.
Compliance monitoring. The Business Risk Assessment, Customer Risk Assessment and Compliance Monitoring Programme in one closed loop, with periodic reviews scheduled by risk and re-baselined by trigger events.
SAR handling. Internal reports, the officer's decision trail and the register in one place, with the two-officer perimeter enforced end to end.
Invoice and accounts payable. Supplier invoices read, coded and matched automatically, then held for the approver who is actually authorised to release the payment.
Board meetings. Packs assembled in hours, minutes drafted from the recording, and a chair-then-directors approval chain to a signed, versioned record.
Dashboards. What is overdue, what is waiting on whom, and what a supervisor would ask for first, without anyone building a spreadsheet to answer it.
CoreAdmin sits alongside the administration system you already run rather than replacing it. Most firms start with one controlled workflow, usually the compliance layer, and switch on further modules when the operating model is ready. A Jersey trust company has been running CoreAdmin in production since it launched: read what their chief executive says about it.
Offshore fund administration on the same platform
Very few Jersey firms do only trust work. The same house typically administers funds, holding structures and corporate vehicles, and the back office carries all of it. Running an offshore fund administration platform separately from the trust compliance estate means two audit trails, two sets of user permissions and two answers to the same supervisory question.
CoreAdmin runs fund workflows in the same tenancy as the fiduciary ones: capital calls and distributions, invoice processing at volume, and the same named-officer approval chain over both. See what it looks like for fund administrators, or read how AI invoice processing works in Jersey fund administration.
See it against one of your own files
Bring a live Jersey workflow to a focused 30-minute session: a register, an onboarding file, a SAR decision trail or a board pack.