For UK firms that safeguard client cryptoassets
Daily client-asset reconciliation for UK crypto firms, built in four weeks
Your internal records against custodian and chain data, every business day, per trust and per cryptoasset class, built up from each client's entitlement. Break handling and a daily evidence record. Fixed price. Runs in your own cloud.
We reply within one working day.
- Readiness build
- From £12,000, fixed
- Care plan
- From £750 a month
- Further chains, custodians or asset classes are fixed-price extensions, quoted before we start. No VAT is added.
The timetable
The FCA's application period for the new cryptoasset regime closes on 28 February 2027, and the regime is expected to come into force on 25 October 2027.
CASS 17 sets out how firms safeguard client cryptoassets, including reconciliations and the records behind them. Your application describes your systems and procedures, and the rules apply from the start of the regime. A system that already runs is easier to describe accurately and to answer questions about. Your advisers tell you what the rules ask of your firm; we build the system that does it. Dates from the FCA: how the gateway will operate and the new regime, fca.org.uk.
Three things to know
- 1
Built to your policy
Your advisers decide what the rules require; we build it. Sources, matching rules and any tolerance come from your written policy and show on every record.
- 2
Read-only by design
No keys, no wallet access, no writes to your ledger. The system reads your records, your custodians and the chain, and never changes any of them.
- 3
Evidence every day
A record of each run and each discrepancy, tamper-evident. Each day's record carries a fingerprint of the one before, so an edited or deleted record shows.
We do not give regulatory advice; your advisers decide what the rules require.
What we build
One system, from your data sources to the record your advisers can attach. It reads; it never writes.
- Connectors
- Read-only links to your ledger (a database replica or an export), your custodians' confirmations, and chain data from a node or indexer kept apart from your transaction systems. Internal records sit on one side of the check, external sources on the other.
- One position format
- Every source turned into the same shape: client, trust, asset, quantity, source and as-at time.
- Matching
- Each client's entitlement worked out every business day, then reconciled per trust and per cryptoasset class against the external sources. Exact match by default; any tolerance is the one written in your policy, shown on the record.
- Breaks
- Every difference opens a case, marked as an excess or a shortfall, with an owner and the deadline your policy sets. Overdue cases and late or failed runs are flagged; your team decides what to do and whom to tell. Nothing is ever fixed by quietly adjusting your ledger.
- Case workflow
- Notes, attachments, a proposed resolution, a second approval, a re-run and closure, each step logged.
- Evidence log
- A record of every calculation, confirmation and reconciliation: when it ran, what it found, the reasons for any difference and the actions taken. Append-only, each record linked to the one before, kept as long as your policy says. Daily record as PDF and CSV, plus the full history of each case.
- Alerts
- Email or chat on any break, and on any run that fails or is late.
- System description
- A plain description of how the system works, with screens and sample outputs, for your advisers to use in your application.
- Your cloud
- Deployed in your own cloud account with infrastructure as code and least-privilege credentials. Your data stays in your environment.
Four weeks, week by week
- Week 0
Read your policy, list the data sources, agree the independent source for each asset, fix the scope.
- Week 1
Connectors and the position format; the first raw comparison.
- Week 2
Matching, breaks and the evidence log; the first daily record.
- Week 3
Case workflow, alerts and exports; a break opened and closed end to end.
- Week 4
Hardening, tests, runbook, handover and the system description; five daily runs in a row.
What you can check
Done means these tests pass
The acceptance tests are written into the contract. The build is accepted when they pass on your system, with your data.
- 1Five consecutive business-day runs complete without manual intervention.
- 2A seeded discrepancy is detected, opens a case and notifies the named owner.
- 3A case cannot be closed without a recorded reason and a second approval.
- 4Editing or deleting a past record is detectable from the linked record chain.
- 5The system has no write access to your ledger, keys or wallets.
- 6A new joiner can run and read the system from the runbook alone.
A sample daily record
What the system produces each business day, for a made-up firm with made-up data.
See a sample record- Supplier
- Tyche Labs Ltd
- Company number
- 16716814 (opens Companies House)
- Registered in
- England and Wales
Prices
Scope and price are fixed in week 0, before any build work starts. No VAT is added.
One build, four weeks
Readiness build
From £12,000, fixed
- Up to three chains and one custodian
- Daily client entitlements, reconciled per trust and per cryptoasset class
- Break cases with owners, deadlines and second approval
- A daily evidence record, PDF and CSV
- A system description for your application
- Runbook, handover and five daily runs before acceptance
After handover
Care plan
From £750 a month
- Maintenance and monitoring of the runs
- Chain and API upgrades
- Changes when your policy or the rules change
- A monthly technical review
Monthly, with 30 days' notice.
What we don't do
We do not give regulatory advice; your advisers decide what the rules require.
- Regulatory advice or a view on what the rules require
- Writing your policies or procedures
- Holding keys, wallets or client assets
- Running your reconciliations for you: your team runs them, the system is yours
- Compliance sign-off of any kind
Questions we get asked
No one outside the FCA can promise that, and we don't. We build the working system your policy describes and the evidence it produces. Your advisers decide whether it meets the rules, and the FCA decides your application.
No. The system reads public chain data, your custodians' statements and a read-only copy of your ledger. It has no keys, no wallet access and no write access to your ledger, and one of the acceptance tests checks exactly that.
Your team. The system runs on a schedule in your cloud account, and your staff own the breaks and the sign-offs. We build it, hand it over with a runbook, and can look after it on a care plan.
Each further chain, custodian or asset class is a fixed-price extension, quoted before we start. We agree the full list in week 0, so the price doesn't move later.
Yes, and it often works best that way: they write the policy, we build the system it describes, and they use the system description in your application. Consultancies can also introduce us or have us build for their clients.
The kind of daily record the system produces each business day, for a made-up firm with made-up data. No real client or firm appears in it.
See what a daily record looks like.
Then book 20 minutes: tell us your chains, custodians and deadline, and we'll tell you what a build would cover.