Cash Balance Plan Annual Review: A 12-Point Checklist for Sponsors
Use this 12-point annual review checklist to organize cash balance plan governance, data, funding, notices, filings, and participant service.
Cash Balance Annual Review decisions should start with the written plan, complete data, and a documented review—not a shortcut based on a headline or prior-year practice.
A cash balance plan is a defined benefit plan with a promised benefit stated as an account balance, and investment changes do not directly change that promised benefit.[1] Annual review therefore needs both operational and actuarial perspectives. For a small or mid-size employer, the practical challenge is translating a technical pension rule into a repeatable decision process. That means identifying the business question, distinguishing a promised benefit from a planning estimate, and assigning the right questions to the sponsor, actuary, administrator, counsel, and participant-facing team.
At a glance
- Core question: What does the plan document require before this decision is carried out?
- Focus: cash balance annual review
- Reading path: define the issue, compare options, then implement and review.
Define the issue before choosing a path
Cash balance arrangements are defined benefit plans, although the promised benefit is commonly described as a hypothetical account balance.[1] That label makes the benefit easier to discuss, but it does not turn the arrangement into an individual investment account. The governing plan document, adoption materials, amendments, valuation work, and participant notices remain the starting points for action. A sound file records the decision date, the version of each document reviewed, the population affected, and the owner of each follow-up item.
Begin by separating facts from assumptions. Facts include the current plan provisions, participant census, payroll and service records, benefit calculations, prior communications, and completed filings. Assumptions include future employment, market conditions, participant elections, and implementation timing. Treating an assumption as a plan fact is a common source of avoidable rework. The sponsor should also define success in operational terms: accurate benefits, timely communication, defensible records, and no surprise handoff between providers.
Compare the practical lenses
| Lens | Question to ask | Useful evidence |
|---|---|---|
| Plan terms | What is permitted or required now? | Signed document and amendments |
| Participant impact | Who receives a different right, notice, or calculation? | Census and benefit records |
| Operations | Who owns data, timing, and quality control? | Project calendar and service agreement |
Use the table to compare plan-language, participant-impact, and operating constraints before directing a vendor or announcing a change. A comparison is not a vote for the easiest option. It is a way to expose which decision maker needs more evidence. For example, a sponsor may prefer speed, while a participant communication team may need finalized calculations first. Put that dependency on the calendar rather than resolving it informally.
Questions that make review more useful
Ask what has changed since the last review; which provisions are protected or time-sensitive; whether a participant notice, election, or disclosure is implicated; whether the actuarial work relies on clean inputs; and what written record will show the decision was carried out as approved. If the answer relies on a legal or tax conclusion, stop and request individualized advice. The goal is not to make every sponsor an actuary or lawyer. It is to make the escalation point visible early enough to preserve options.
Implement with owners and evidence
Run the review before filing deadlines compress the calendar. Reconcile census and payroll inputs, confirm document changes, ask the actuary about funding and assumptions, and maintain an evidence file for each control. Convert that work into a short written action register. For each item, identify the owner, required input, approval point, due date, and proof of completion. Keep the record with the plan’s administration files rather than in a single person’s inbox. This is especially important where payroll, census, actuarial valuation, notices, and benefit payments move through different vendors.
- Model facts: gather census data, objectives, and funding constraints.
- Test range: test contribution ranges, assumptions, and tradeoffs.
- Fund plan: approve funding, administration, and communication steps.
- Review: review results, changes, and annual readiness.
Decision flow: Define ➔ Compare ➔ Implement ➔ Review.
Implementation checklist
| Step | Owner | Completion evidence |
|---|---|---|
| Confirm facts and current document | Plan administrator | Version-controlled review file |
| Test actuarial and operational impact | Actuary and TPA | Written assumptions and reconciliation |
| Approve communications and actions | Sponsor with counsel | Approval log and final notices |
| Close the loop | Plan administrator | Filed records and exception log |
Review: test the result, not just the task list
After implementation, compare the completed work against the decision register. Confirm that affected participants were identified, calculations or notices used the approved version, required filings or records were routed correctly, and unresolved exceptions have a named owner. A brief post-mortem is useful when a handoff failed or a data field had to be corrected: capture the root cause, revise the control, and schedule the next test.
For sponsors, the best annual discipline is a standing review that joins finance, HR, payroll, the administrator, and the actuarial team. It should surface changes in workforce data, business strategy, document provisions, service-provider responsibilities, and participant questions before a deadline creates pressure. The review should also ask whether the plain-language explanation matches the technical documents; clarity is part of administration, not merely a communications preference.
Keep the decision record usable
A useful record is short enough to be read at the next handoff and specific enough to be tested. State the decision, the effective date or target date, the plan provision reviewed, the data cutoff, the people responsible, and any advice requested. Attach the final source documents rather than relying on a summary that may become stale. If an assumption changes, record who assessed the change and whether the prior approval still applies.
Build a participant-experience check into the workflow. Ask whether a person receiving a notice can identify the action, deadline, contact, and consequence without decoding internal jargon. Ask whether the service team has the same calculation version and explanation. Where the answer is no, pause and resolve the inconsistency before the communication is released. This simple control reduces rework and makes later review more credible.
Finally, preserve exceptions rather than hiding them in email. An exception log should identify the affected record, provisional treatment, responsible reviewer, next date, and final resolution. That discipline helps the sponsor distinguish a one-time correction from a recurring process weakness.
Takeaway
The durable approach is to use the plan document as the anchor, use current data as the evidence, and leave a written trail from decision through review. Technical pension decisions often have tax, legal, actuarial, investment, and compliance consequences. Obtain advice tailored to the plan and the people affected before acting.
Editorial disclaimer: This article is educational information, not tax, legal, actuarial, investment, or compliance advice. Plan terms and individual circumstances control; consult qualified advisers before taking action.
References
- [1] https://www.dol.gov/agencies/ebsa/about-ebsa/our-activities/resource-center/fact-sheets/cash-balance-pension-plans
- Supporting source: https://www.irs.gov/retirement-plans/defined-benefit-plan
- Supporting source: https://www.dol.gov/agencies/ebsa/about-ebsa/our-activities/resource-center/publications/reporting-and-disclosure-guide-for-employee-benefit-plans