Tutorials › CAS Exam 9 - Risk Management for Actuaries › Governance Of Regulatory Capital Calculations

CAS Exam 9 · Regulatory Capital in Practice · Tutorial 894 of 995

Governance Of Regulatory Capital Calculations

Build a traceable control framework for regulatory capital calculations, and practise identifying and resolving reporting errors before they become governance failures.

Advanced 13 min read

What You'll Learn

  • Assign ownership and validation responsibilities to each material data input.
  • Design reconciliations that test completeness and accuracy before calculation.
  • Use independent review to verify formulas, inputs, outputs, and reported results.
  • Establish approval and documentation standards for assumptions and model changes.
  • Escalate errors according to their impact, reporting status, and urgency.
  • Distinguish a documented control exception from evidence that a calculation is correct.

Why Governance Matters in Capital Reporting

A regulatory capital result is only as dependable as the process that produces it. A calculation can use a technically correct formula and still be unreliable if its data are incomplete, its assumptions are unauthorized, or a change is applied without review. Governance provides a defined way to establish who owns each input, who checks the calculation, which assumptions are permitted, and what happens when a control identifies an error.

The goal is not to add review steps for their own sake. Controls should create evidence that the reported result is complete, accurate, reproducible, and approved at the appropriate level. The design should reflect the calculation’s complexity and potential impact. A small clerical adjustment and a material change to a capital model should not automatically receive identical treatment.

Definition: Governance of regulatory capital calculations is the set of assigned responsibilities, controls, approvals, records, and escalation procedures used to produce and report a capital result. A control owner is accountable for performing or overseeing a specified control; a data owner is accountable for the definition, quality, and provision of a specified data set.

Governance does not make an incorrect method correct. It helps detect errors, establishes whether the method and assumptions were authorized, and makes it possible to reconstruct how a reported result was produced. Regulatory requirements differ by jurisdiction and reporting regime, so control procedures must be aligned to the applicable rules rather than treated as one universal checklist.

Designing the Control Chain

A useful control framework follows the calculation from source data to final reporting. Each stage should identify the person or function responsible, the evidence retained, and the action required if a control fails. Duties should be separated where practicable: the person who prepares a result should not be its only reviewer.

1
Define and assign ownership.
Specify the source, definition, reporting date, units, and responsible owner for each material input. Resolve ambiguous definitions before the data enter the calculation.
2
Validate and reconcile data.
Check completeness, reasonableness, permitted formats, and agreement to appropriate source records or control totals. Record unresolved differences as exceptions, not as silently accepted adjustments.
3
Calculate and review independently.
Have a reviewer who did not prepare the calculation test key inputs, logic, transformations, and output. The reviewer should be able to reproduce the result or explain a documented difference.
4
Approve assumptions and changes.
Use authorized assumptions and controlled versions of calculation tools. Assess proposed changes before use, document their impact, and obtain the required approval.
5
Retain evidence and escalate exceptions.
Keep enough information to reproduce the reported result. Route errors and control failures to the appropriate decision-makers, with urgency reflecting materiality and reporting status.

Data Ownership and Reconciliation

Data ownership means more than assigning someone to send a file. The owner should define what the data represent, identify the authoritative source, explain relevant transformations, and confirm the reporting period and units. The calculation team remains responsible for checking that received data are suitable for the calculation; receiving an owner’s certification does not remove that responsibility.

A reconciliation compares two representations that should agree, such as an extracted exposure total and a source-system control total. If the source total is \(T\) and the extracted total is \(E\), define the difference as \(D=T-E\). A nonzero difference is evidence requiring investigation. A zero difference supports agreement of those totals, but it does not prove that every record is correctly classified or that the underlying definition is appropriate.

Worked Example: Finding an Incomplete Exposure Extract

A hypothetical insurer calculates a capital component as 2% of eligible exposure. The data owner’s source report shows three exposure groups of $120 million, $80 million, and $50 million. The extract supplied to the calculation team shows $118 million, $80 million, and $50 million. Determine the reconciliation difference and its effect on the component. State the control response.

Method. Reconcile each group and the total before applying the stipulated 2% factor. The factor is hypothetical for this example, not a statement of a universal regulatory formula.

The source total is \(120+80+50=250\) million dollars. The extract total is \(118+80+50=248\) million dollars. Therefore the total difference is \(250-248=2\) million dollars. The group-level comparison identifies the difference in the first group: \(120-118=2\) million dollars.

Using the source total, the component is \(250 \times 0.02=5.00\) million dollars. Using the incomplete extract, it would be \(248 \times 0.02=4.96\) million dollars. The extract therefore understates the component by \(5.00-4.96=0.04\) million dollars, or $40,000.

Control response. The data owner and calculation team should trace the missing $2 million to its source and determine whether it is eligible for the reporting period. The team should not simply add $2 million to force agreement without evidence. Once resolved, the corrected extract, reconciliation, explanation, and review evidence should be retained.

Check. Applying the factor to the corrected source total gives $5.00 million, matching the result calculated directly from the source total. A common mistake is to regard a small percentage difference as immaterial without calculating its dollar impact or investigating its cause.

Independent Review and Calculation Evidence

Review should test the calculation, not merely confirm that a file exists or that a preparer completed a checklist. Depending on the process, a reviewer may independently recompute material steps, trace selected inputs to source evidence, confirm that formulas and mappings are unchanged, and investigate unexpected movements. The review record should identify what was checked, what evidence was used, what exceptions arose, and how each was resolved.

A difference between a reported result and an independent recomputation can be expressed as \(\Delta=C_R-C_I\), where \(C_R\) is the reported amount and \(C_I\) is the amount from the independent check. The percentage difference, when \(C_I\) is nonzero, is \(\Delta/C_I\). These measures quantify a discrepancy; they do not by themselves determine whether it is acceptable. A control policy should define how differences are assessed, considering applicable reporting requirements and the nature of the error.

Why independent recomputation helps: If the reviewer uses the same inputs, formulas, and processing steps without independently checking them, the review can repeat the preparer’s error. Independent tracing or recomputation introduces a separate test. It is most effective when the reviewer can explain the calculation path and has access to the underlying evidence, not only the final output.

Worked Example: Reviewing an Aggregated Result

Suppose a hypothetical reporting process specifies the illustrative aggregation rule \(C=\sqrt{A^2+B^2+C_3^2}\), with all component amounts in millions of dollars. The preparer reports \(A=6\), \(B=8\), \(C_3=0\), and total capital of $10 million. During review, source evidence indicates that the approved value of \(B\) is $9 million. Recompute the total and quantify the discrepancy.

Method. Apply the stipulated rule to the reviewed component values, then compare the independent result with the reported amount. This example’s rule is provided only for the problem; it is not asserted to be a universal regulatory aggregation formula.

The reported calculation is \(\sqrt{6^2+8^2+0^2}=\sqrt{36+64}=\sqrt{100}=10\) million dollars. Replacing the unsupported value of \(B=8\) with the approved value \(B=9\), the independently checked result is \(\sqrt{6^2+9^2+0^2}=\sqrt{36+81}=\sqrt{117}=10.8166538\ldots\) million dollars.

The reported amount is lower than the recomputed amount by \(10.8166538\ldots-10=0.8166538\ldots\) million dollars. Relative to the recomputed result, the difference is \(0.8166538\ldots/10.8166538\ldots=0.0755\), or 7.55% to two decimal places. Rounding the recomputed capital amount to the nearest $0.001 million gives $10.817 million.

Control response. The reviewer should trace the value of \(B\) to its approved source, document the discrepancy, and prevent the result from being treated as reviewed and resolved until its cause and reporting implications have been assessed. The preparer’s result cannot be accepted merely because its arithmetic is correct for the unapproved input.

Check. The corrected value is larger than $10 million because \(9^2\) exceeds \(8^2\), and the recomputed square root is approximately 10.817. A common mistake is to review only the aggregation arithmetic and overlook whether the component values themselves are supported.

Assumption Approval, Documentation, and Change Management

An assumption should have an identified owner, a stated rationale, an approval status, and an effective period. A reviewer should be able to distinguish an approved assumption from a proposal, a temporary sensitivity, or a value copied from a prior reporting cycle. Where the governing process requires a particular prescribed assumption, internal approval cannot authorize a conflicting value.

Change management applies to data definitions, calculation logic, software, mappings, and assumptions. Before a material change is used, the responsible team should describe what changed, why it changed, who approved it, when it takes effect, and what testing supports it. Where appropriate, compare the result under the prior and proposed versions and retain the comparison. A version identifier alone does not demonstrate that a change was authorized or tested.

Documentation should be sufficient for a qualified reviewer to reconstruct the reported result without relying on the memory of the original preparer. Depending on the process, useful evidence includes source files and dates, transformation rules, model or spreadsheet versions, assumption approvals, reconciliation results, review sign-offs, exception resolutions, and the final submitted output. Records should be protected from untracked alteration and retained according to the applicable policy.

Worked Example: Rejecting an Unapproved Assumption Change

A hypothetical capital component is calculated as exposure multiplied by an approved factor. Exposure is $200 million, and the approved factor for the reporting period is 1.2%. A proposed change would use 1.0%, but it has not received the required approval. Calculate both amounts and determine what should enter the controlled calculation.

Method. Apply each factor to the same exposure, label the results by approval status, and follow the stated control rule that only an approved factor may be used for the reporting calculation.

With the approved factor, the component is \(200 \times 0.012=2.4\) million dollars. With the proposed factor, it would be \(200 \times 0.010=2.0\) million dollars. The proposed change reduces the result by \(2.4-2.0=0.4\) million dollars, or $400,000.

Because the 1.0% factor is unapproved, the controlled calculation uses $2.4 million, subject to any applicable prescribed requirements. The $2.0 million result may be recorded as an analysis of the proposed change, but it must not be presented as the approved reporting result. The owner should obtain the required decision, document its effective date and rationale, and apply it only to the permitted reporting period.

Check. The decrease is \(0.002 \times 200=0.4\) million dollars, consistent with the difference between the two results. A common mistake is to treat a plausible proposed assumption as authorized because it produces a reasonable-looking number.

Escalating and Resolving Errors

An error should be assessed on more than its size. Relevant considerations include whether it affects a submitted or pending report, whether it changes a regulatory classification or threshold assessment, whether it indicates a broader control failure, and whether other periods or entities may be affected. The applicable reporting regime and internal policy determine notification and correction obligations; governance procedures should not invent a substitute for those requirements.

The initial response should preserve evidence and establish the facts: what was wrong, how it was detected, which outputs and periods are affected, and whether the calculation can be reproduced. The responsible decision-maker can then determine containment, correction, internal escalation, and any required external communication. Correcting a number without investigating its cause may leave the same failure in place for the next reporting cycle.

1
Record and contain.
Log the issue, preserve the relevant versions and evidence, and prevent an unverified result from being represented as resolved.
2
Assess impact.
Identify affected data, assumptions, calculations, periods, reports, and decisions. Quantify the difference where possible and state limitations where it is not.
3
Escalate and decide.
Notify the designated control owner and appropriate management level under the applicable policy. Determine any reporting, correction, or notification action required by the governing rules.
4
Correct and prevent recurrence.
Document the correction, obtain review, identify the root cause, assign remediation, and verify that the revised control operates as intended.

Common Governance Traps

  • Confusing ownership with review. A data owner’s confirmation does not replace the calculation team’s checks of suitability, completeness, and reconciliation.
  • Treating a zero reconciliation difference as proof of correctness. Two totals can agree while both omit the same records or use an incorrect definition.
  • Reviewing only the final answer. A plausible total can conceal an unsupported input, an incorrect mapping, or an unapproved assumption.
  • Using a proposed change before approval. A calculation must use the authorized assumptions and version applicable to its reporting period.
  • Closing an exception after changing the number. Resolution requires evidence of the correction and an assessment of cause, affected outputs, and required follow-up.
Key takeaway: A strong capital calculation control framework connects each material input and assumption to an owner, each result to independent review, each change to approval and testing, and each error to documented escalation and resolution.

Check Your Understanding

For each hypothetical scenario, identify the relevant control issue and calculate the requested result.

  1. A source report contains exposure groups of $35 million, $45 million, and $20 million. The calculation extract contains $35 million, $43 million, and $20 million. The stipulated component factor is 1.5%. Calculate the source and extract components and their difference. (Answer: Source total $100 million; extract total $98 million; components $1.500 million and $1.470 million; understatement $30,000.)
  2. A hypothetical process uses \(C=\sqrt{A^2+B^2+D^2}\), with components in millions. The submitted values are \(A=5\), \(B=12\), and \(D=0\), but approved source evidence shows \(B=13\). Recompute the result and find the increase over the submitted amount. (Answer: Submitted $13.000 million; recomputed \(\sqrt{194}=13.9284\) million; increase $0.9284 million, approximately.)
  3. A component is exposure multiplied by a factor. Exposure is $150 million, and the approved factor is 0.8%; an analyst proposes 0.7% without approval. Calculate both components and state which belongs in the controlled reporting calculation. (Answer: Approved $1.200 million; proposed $1.050 million; use $1.200 million unless the change is properly approved and applicable.)
  4. A data validation identifies 240 omitted records, each with a stipulated average severity of $2,500. A hypothetical calculation applies a 4% factor to the omitted loss amount. Calculate the missing loss amount and its component impact, and name two immediate governance actions. (Answer: Missing loss $600,000; component impact $24,000; preserve and investigate the extract, and escalate the exception to the designated control owner before treating the result as resolved.)
Clinical Biostats