When the FCA asks about your claims decision, you must prove not just what you decided, but when you decided it.

Documenting each stage of a claims decision: initial assessment, investigation, coverage determination, and outcome, in the claims management system.

immut hashes the claims decision file the moment it is finalised, creating a blockchain-timestamped record on the XRP Ledger. If a customer later alleges the decision was fabricated after their complaint arrived, the timestamp is independently verifiable without relying on the insurer's own systems. The hash proves the document existed, unchanged, at the moment of creation.

Insurance complaints were upheld at 41% by the FOS in 2024/25, above the all-sector average of 34%. Liberty Mutual Insurance Europe SE fined £5.3M by the FCA in part for inadequate investigation records on declined claims (2018).

Preparing and approving the annual Consumer Duty board report (required under PRIN 2A.8 by 31 July each year) and the management information submitted to the governing body.

immut timestamps the MI data sets and the board report at the point of sign-off. When the FCA requests evidence that monitoring existed at the relevant reporting date, the blockchain timestamp proves the document predates the enquiry. It also timestamps each iteration of the monitoring data, so trend evidence is independently dateable.

The FCA reviewed 20 large insurers in June 2024 and found most could not demonstrate that monitoring had directly led to action; the regulator stated it will consider taking action where it sees examples of poor practices. Consumer Duty (PS22/9) requires ongoing evidence of fair outcomes across all open products and services.

Publishing, approving, and issuing policy documents, key facts documents, and schedule endorsements at point of sale and renewal.

immut timestamps each version of the policy wording document at the moment it is approved and made available. In a coverage dispute, the insurer can produce a blockchain-verified hash of the exact document issued on the sale date, proving it has not been retrospectively amended. Intermediate drafts are excluded: only the file that was hashed and timestamped at approval is verifiable.

The FCA's 2024 thematic review (TR24/2) found that many firms provided no minutes or records to evidence product approvals, leaving them unable to demonstrate when a product version was approved and what it contained.

Quarterly and annual Solvency II regulatory reporting (Pillar 3 QRTs), Own Risk and Solvency Assessment (ORSA), and actuarial function reports submitted to the PRA.

immut timestamps the data extract and the actuarial sign-off document at the moment they are approved. This creates an independent, contemporaneous record that the data lineage used to calculate SCR and MCR existed and was locked before the reporting date. If the PRA or auditors question whether figures were retrospectively adjusted, the blockchain timestamp is conclusive.

U K Insurance Limited (Direct Line Group) fined £10.625M by the PRA in March 2026 after a Solvency II balance sheet miscalculation, overstating solvency by up to £99.9M across 2023 to 2024, went undetected because preventive and detective controls failed.

Logging and responding to every complaint under FCA DISP 1.6: acknowledging within three to five business days and issuing a final response within eight weeks.

immut timestamps each complaint-handling document (acknowledgement letter, investigation memo, final response) the moment it is created. If a customer disputes timing or a FOS case turns on whether the firm responded within the statutory window, the timestamp is independently verifiable and does not rely on the firm's own CRM logs.

The FOS received 305,726 complaints in 2024/25, the highest in six years, and upheld 34% overall. Failure to issue an eight-week final response under DISP 1.6 is a breach of FCA rules and gives customers an automatic right of FOS referral.

Implementing and evidencing pricing model changes required under FCA PS21/5 (general insurance pricing practices, effective 1 January 2022), and providing annual attestations to the FCA confirming compliance.

immut timestamps the approved pricing model at the moment the change is deployed. If the FCA's attestation review questions whether the model was updated by the required date, or whether it was updated retrospectively to appear compliant, the blockchain timestamp of the model file is the independent proof. It also timestamps each subsequent version, creating a verifiable version history.

The FCA's pricing attestation multi-firm review found that only 11 of 66 firms submitted records meeting its expectations; many smaller firms had few or no records to demonstrate how they had complied with the pricing rules.

Quarterly and annual reserving returns to Lloyd's (RRA/RRQ) and the PRA; actuarial function reports and peer review sign-offs required before submission.

immut timestamps the reserving model output and the actuarial sign-off document at the moment the Signing Actuary approves them. If Lloyd's or the PRA conducts a walk-through of reserving files and questions whether estimates were adjusted after the period end, the timestamp is not the firm's own word. It is a public blockchain record.

The PRA fined U K Insurance Limited £10.625M in March 2026 because a Solvency II reporting error remained undetected for a significant period, illustrating the enforcement risk when data lineage and sign-off timing cannot be independently verified.

Managing agents issuing, amending, and renewing binding authority agreements (BAAs) with coverholders; coverholders maintaining records of which authority applied at each binding decision.

immut timestamps each version of the binding authority document the moment it is executed or amended. When a coverage dispute or Lloyd's audit turns on which authority was in force on a given date, and whether a coverholder exceeded it, the timestamp on each BAA version is independently verifiable on the public blockchain, creating an unbroken chain of which document was live at each moment.

Disputes over binding authority scope are a recurring source of Lloyd's market litigation. FCA SYSC 9 requires records of all services and transactions sufficient to enable monitoring of compliance. Lloyd's coverholders are subject to audit under Lloyd's Coverholder Compliance and Operations standards.