How data flows through the platform.

Every Congruent Calculations™ engagement runs through a defined data schema, validated on receipt, lodged via the My Congruent portal, and tracked in the platform's audit log. The schema is what makes calculation reproducible. The portal is how clients see the work in flight.

The schema

Each productised Solution carries its own data schema. The schema specifies which fields are required, which are optional, the format of each field, and the cross-field validation rules that apply on receipt. Calculation cannot begin until the schema validates clean — missing or anomalous data is flagged in the audit log, and the engagement-lead engages the client to resolve before proceeding.

Pension Sharing Order

Member identification (date of birth, scheme membership dates, accrual basis), scheme identification (CETV basis, funding-basis spread, scheme rules summary), and matrimonial-specific fields (date of separation, spouse details where required for pension-share calculation).

Redress & remediation

Per-customer cohort data: identification, transaction history, current holdings, regulatory cohort flags. Product data: charges, alternative-investment performance benchmarks, hypothetical-pathway parameters. Engagement parameters: cohort definitions, scope boundaries, materiality thresholds.

Pension valuations

Scheme data (member records, accrual rules, indexation rules, retirement-age conventions), valuation parameters (discount-rate basis, salary-growth assumptions, longevity assumptions), and reporting context (regime: sponsor-side funding / BPA transaction / litigation).

Value for Money

Member-level cohort data, contribution histories, charge structures (cost transparency disclosures), investment-performance histories, service-quality metrics, and the arrangement's pooling structure (in scope: LTAFs, with-profits, exotic structures).

Validation on receipt

Inputs are validated against the schema on receipt — before calculation begins. Validation operates at three levels:

Field-level: each required field present; each format-constrained field within format; each enumerated field one of the permitted values.
Cross-field: internal consistency (dates ordered correctly; cohort flags consistent with cohort definitions; member-level totals consistent with scheme-level aggregates).
Regulatory: the data set as a whole satisfies the regulatory regime's data-quality requirements (e.g. DISP App 4 sample completeness; TPR member-data adequacy for funding valuations).

Failures are logged with engagement-specific control IDs, surfaced via the portal, and routed to the engagement-lead for resolution. Calculation does not begin on a non-validating data set.

The My Congruent portal

The portal is the client's interface to the platform. Per-engagement, per-named-individual access; accountability for each lodgement and each calculation tracked at the user level.

Lodge data

Upload data sets to the engagement schema. Validation runs on receipt; the audit log records each lodgement with timestamp and named user. Re-lodgement is permitted; each version is preserved in the audit chain.

See engagement progress

View engagement state in real time: data lodged, validation status, calculations queued, calculations executed, CMC™ artefacts produced. The audit log is visible to the named users on each engagement.

Retrieve CMC™ artefacts

Calculations complete, CMC™ artefacts are produced and indexed in the portal under the engagement's calculation control ID. Per-customer artefacts (redress) or per-deliverable artefacts (litigation) are retrievable with version history.

The audit log

Every action on the platform is logged: data lodgement, validation outcome, calculation execution, CMC™ generation, revision, and access. Logs are immutable, named-user-attributed, and reproducible — given the schema and the configuration in use, every output can be reconstructed from the audit log alone.

This is the apparatus that supports skilled-person review under FSMA s.166, FCA enquiry response, and any other regulatory engagement where the firm's calculation chain has to be reviewable independently. The log is not a paper trail bolted on for compliance — it is the platform's primary engineering artefact.

Schema documentation and access

Per-engagement schema documentation is supplied at the outset of each engagement. For institutional clients running the platform under license (in their own environment), schema documentation includes the validation logic, the integration points, and the audit-log contract. Schema documentation for the productised retainer / subscription / outsourced models is engagement-specific.

For technical questions about the schema or the portal — integration questions, validation-rule queries, or data-quality questions ahead of an engagement — the firm responds within one working day to scoping enquiries.

Cross-reference

The platform is owned by Congruent Risk Limited (CH 09465877); calculation engagements are delivered by Congruent Actuarial Limited (FCA FRN 831289). For the platform's CMC™ convention, the four-tier architecture, and the four delivery models (license / retainer / subscription / outsourced), see Congruent Calculations™. For platform production statistics, see Track record.

Schema and portal questions

Integration questions go through a scoping conversation.

Whether the question is about license deployment, schema integration, portal access for a specific engagement, or audit-log requirements, the firm responds within one working day with whether it can assist and what it would need to scope the work.

team@mycongruent.com · 020 3143 3150 · Contact form