Cash Balance Plan Census Data: What Your Actuary and TPA Need From You
Census data for cash balance plans: a practical checklist for sponsors, actuaries, and TPAs.
A clean census is the operating input that lets a cash balance plan be valued, funded, tested, and communicated reliably.
Cash Balance Plan Census Data: What Your Actuary and TPA Need From You becomes easier when the sponsor stops treating the question as a one-line compliance task. The durable answer comes from the plan document, a current census or valuation record, and a documented decision process.
At a glance
- Core question: What does the plan promise and what facts control the answer?
- Focus: Use plan documents, current records, and formal professional analysis.
- Reading path: Define the issue, compare alternatives, then implement and review.
Define the decision
A census should be treated as a controlled dataset, not a payroll export. The actuary needs data that identifies who is covered, when service began and ended, what compensation definition applies, and which plan elections or prior benefits change the calculation. DOL advises participants to review the employment date, service, and salary information used to calculate benefits, a useful sponsor-level quality check as well.[1]
A practical file begins with a stable participant identifier and name, date of birth, hire date, rehire date, termination date, status, work location if relevant, and ownership or highly compensated employee flags. Add plan-entry, eligibility, vesting, hours, compensation components, pay-credit tier, prior-year hypothetical balance, and distribution history where the document requires them. Preserve the source and “as of” date for each field. A spreadsheet can collect the fields, but it is not the governing plan record.
Compare the practical choices
The key comparison is not “what payroll has” versus “what the TPA wants.” It is the plan document’s definition versus the field supplied. For example, base salary, bonus, commissions, fringe amounts, and owner compensation may be treated differently. Build a reconciliation column for each material field and resolve exceptions before the valuation is finalized.
| Lens | Question to ask | Useful evidence |
|---|---|---|
| Plan terms | What formula, definition, or condition controls? | Signed document and amendments |
| Operations | Can the rule be administered consistently? | Payroll, census, and process records |
| Funding | What is the actuarial or financial consequence? | Current actuarial report |
Do not let a generic rule override a specific document provision. A good adviser can translate technical language, but the sponsor should retain the decision record, assumptions, and source data used for each material conclusion.
What a reliable answer includes
Technical plan questions often sound binary, but the answer usually depends on dates, defined terms, participant facts, and interactions with other plan provisions. A reliable review states the question in writing, identifies the governing provision, and distinguishes the legal or actuarial conclusion from the operational steps needed to carry it out. It also records information that is missing rather than silently assuming it away. That discipline reduces rework when advisers, payroll, or leadership review the same issue later.
Implement a controlled workflow
First, assign an owner for the issue and create a short evidence packet: the current plan document, amendments, latest valuation or administration report, current census, prior filings, and the business question that prompted the review. Second, have the actuary, TPA, investment fiduciary, and ERISA or tax counsel address only the questions in their respective roles. Third, record the decision, effective date, communications, and follow-up tasks.
- Map data: identify payroll fields, owners, and timing.
- Compare gaps: compare provider mappings, controls, and exceptions.
- Test handoff: test the handoff before relying on production data.
- Reconcile: reconcile results and retain exception evidence.
Implementation checklist
| Step | Action | Control |
|---|---|---|
| 1. Define | State the decision and applicable plan terms. | Use the current signed document. |
| 2. Compare | Model plausible alternatives with the actual facts. | Document assumptions and exceptions. |
| 3. Implement | Approve, communicate, and complete filings or deposits as advised. | Track owner and due date. |
| 4. Review | Reconcile results to the decision record. | Escalate material variances. |
Review questions for the next meeting
Ask whether the source data is complete, whether the document interpretation was confirmed, whether any effective-date or notice requirement applies, and whether the financial model uses current assumptions. Also ask what could change the result before the next valuation or filing cycle. This converts a technical discussion into a repeatable governance practice.
Takeaway
Coordinate before acting
Different advisers answer different parts of the problem. The actuary can explain benefit and funding calculations; the TPA can explain administration and records; investment fiduciaries can assess portfolio process; and ERISA or tax counsel can assess legal interpretation. Share the same fact packet with each professional, identify the version date, and ask them to flag inconsistent assumptions. A sponsor should not assume that a conclusion in one workstream automatically resolves another.
Finally, preserve evidence of what was decided and why. Meeting notes, approvals, workpapers, payroll reconciliations, and participant communications are more useful when they name the relevant plan period and responsible owner. If facts change, reopen the analysis promptly instead of trying to apply an old conclusion to a new plan year.
Document the result
Close the review with a concise decision memo. It should identify the question, plan year, data cutoff, plan provisions reviewed, advisers consulted, assumptions used, action approved, and open items. Give each open item a named owner and deadline. This record supports consistent administration and makes the next annual review faster because the team can see which facts and interpretations were previously considered. If a participant communication is needed, have it checked against the same approved facts before distribution.
Before closing the file, compare the final records with the question originally presented. Confirm that no unresolved exception, missing data item, or change in plan operations has been left outside the decision. A short confirmation step is often the difference between a technically plausible result and an administratively durable one.
Use a calendar-based check as well: confirm the current plan year, valuation date, next decision date, responsible owner, and record-retention location. This keeps technical work connected to the sponsor’s actual operating timetable and makes follow-up transparent to the entire plan team.
A clean census is the operating input that lets a cash balance plan be valued, funded, tested, and communicated reliably. The responsible path is to use current plan documents and verified data, then obtain coordinated actuarial, fiduciary, tax, and legal advice where the facts warrant it.
Editorial disclaimer: This article provides general educational information, not tax, legal, actuarial, investment, fiduciary, or compliance advice. Plan documents, facts, and applicable law control; consult qualified advisers before acting.
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