White-label actuarial support for accounting firms and TPAs

The firm sends source data and its templates; it gets back checked data, completed workpapers and a review file for the signing actuary. The table shows the usual exchange by engagement type. The last column says who signs. Where it names an enrolled actuary, the engagement letter confirms who that is.

Rows are examples of typical scope, not a fixed menu.

An engagement runs from your template to the signing actuary, in seven steps, with the client's data entering at the start and your firm delivering at the end. The diagram shows the order. The firm sends source data and its templates. Finbryn runs data checks and returns an exceptions list, builds the workpapers to your layout, runs the roll-forward where it applies and assembles a review file. The signing actuary reviews it and signs, and for filings the law restricts to an enrolled actuary the engagement letter confirms who signs. The firm then delivers the signed work to its client, and its client's auditor or the IRS receives it from you.

Each handoff is a written one. The exceptions list is a dated file, not a verbal note, so the signing actuary can see exactly which records were changed or queried before the model ran.

The signing actuary signs, and every professional judgment stays with that actuary. Hesham Khan is Finbryn's signing actuary and reviews and signs the accounting reports Finbryn prepares, such as ASC 715 figures. If your firm has its own actuary, such as a boutique practice, the work can go to that actuary instead, and the engagement letter says which route applies.

Some filings are different. Under 20 CFR 901.2, an entity engaged to provide ERISA actuarial services can provide them only through an enrolled actuary who is its employee, partner or consultant. The 2025 Form 5500 instructions say Schedule SB is prepared and signed by the plan's enrolled actuary. For those filings the engagement letter confirms who signs, and Finbryn stays on the support side of that line.

In practice that means the signing actuary picks the assumptions, reviews the data, decides what to rely on and signs. Actuarial Standard of Practice No. 23 on data quality lets an actuary rely on data supplied by others, with disclosure, and does not require an audit of that data. Finbryn labels every input as client-supplied or prepared by Finbryn, so the signing actuary can describe the reliance accurately in the report. Finbryn never labels data prep as actuary-reviewed.

Census files carry names, birth dates, pay and sometimes Social Security numbers, so they are handled as personal data under terms you set. Before any file moves, your firm sets in writing the transfer method, who can open the files and when they are returned or deleted.

If your client contract limits where data may go, that limit is written into the agreement. Finbryn does not claim a SOC 2 report or an ISO certificate; the security page lists what is in place today, and any control you need that is not listed is raised before the engagement starts, not after.

Cost depends on the work, and Finbryn quotes in writing after seeing a sample of your data. The quote names who signs. The main drivers are the number of plans and participants in the batch, how clean the census is, whether each plan needs a full valuation or only a roll-forward, how closely the work must follow your own template and how close the filing date is. A batch of similar plans can be quoted together, per plan.

We did not find a public fee schedule for private-plan white-label valuation work, so this page publishes no range. Public procurement records do exist for government pension valuations, but those are different plans and a poor guide for a TPA's book. Ask any provider for a per-plan quote that separates full valuations, roll-forwards and rework caused by late or changed data. See how pricing works.