California 1937 Act retirement reporting software
37Act turns payroll, member, employer, actuarial, financial, and audit inputs into one governed reporting workspace for California county retirement systems governed by CERL.
Focus
CERL scope
Focus
Evidence lineage
Focus
Board-ready output
CERL
A narrow reporting workspace for California county retirement systems — not generic BI retrofitted for public pensions.
GASB
Organize plan schedules, employer disclosure support, source references, and reviewer signoff in one reporting cycle.
AUDIT
Preserve imports, exceptions, assumptions, approvals, exports, and review notes by fiscal year.
BOARD
Create executive summaries, exhibits, status views, and appendix materials without rebuilding everything from scratch.
Reporting cockpit
Direct answer
37Act is a reporting operations workspace for California 1937 Act / CERL retirement systems. It does not replace the pension administration platform, ERP, actuary, auditor, or finance team. It gives those teams a shared place to manage the annual reporting cycle: source file intake, validation, exception resolution, actuarial data packages, GASB support schedules, audit evidence, and board packet production.
The product is designed for the reporting work that happens between systems and people: employer payroll and contribution files, member data, financial schedules, actuarial requests, audit workpapers, review comments, approvals, exports, and public-facing board materials.
Market signal
The 1937 Act universe is focused enough for a deeply opinionated product and complex enough that spreadsheets, email, and shared drives leave too much reporting risk behind.
20
SACRS describes twenty California counties operating retirement systems under the 1937 Act.
3 yrs
Government Code section 31453 requires valuations at intervals not to exceed three years.
Dec 31
Government Code section 31597.1 sets a December 31 filing timing where adopted by county resolution.
A site style built for one market
37Act now leans into a more ownable visual language: county-office paper trails, actuarial workpapers, board-packet ribbons, source lineage, and validation signals. The design should feel precise enough for auditors and warm enough for public-sector teams who live in documents all year.
Retirement teams already have source systems, auditors, actuaries, finance tools, and board processes. The gap is the governed workspace connecting them.
Current state
With 37Act
Every module is framed around a real 1937 Act reporting job-to-be-done: gather the data, validate it, explain exceptions, prepare outputs, and preserve evidence.
Normalize employer payroll, member, contribution, pay-period, service-credit, and adjustment feeds into a fiscal-year reporting model.
Flag missing files, contribution mismatches, status changes, unresolved review notes, and stale assumptions before they become audit or board questions.
Prepare repeatable valuation extracts and supporting schedules with versioning, assumptions, reconciliation notes, and source-file context preserved.
Support GASB 67 plan reporting and GASB 68 employer disclosure packages with source references, draft/review states, and export history.
Keep imports, overrides, comments, approvals, workpapers, and final exports tied to a fiscal year and reporting cycle.
Generate management summaries, exhibits, status dashboards, exception logs, and appendices for retirement board and committee review.
Use the site and demo narrative to show a repeatable reporting cadence, not a black-box compliance promise.
Step 1
Set up the reporting year, source list, owners, due dates, expected employer files, actuarial requests, audit requests, and board milestones.
Step 2
Bring in payroll, member, contribution, actuarial, investment, and accounting files; run checks for completeness, totals, status changes, and roll-forward consistency.
Step 3
Assign issues, capture reviewer notes, document assumptions, attach workpapers, and preserve why adjustments were made.
Step 4
Produce actuarial data packages, GASB support schedules, audit binders, management summaries, exhibits, and board-ready packets from the same traceable model.
Workflow visual
From source files to evidence-backed board materials
Payroll, member, employer, finance, actuarial and audit files arrive with owners and due dates.
Completeness, totals, status changes, contribution mismatches and stale assumptions are surfaced early.
Reviewers assign, comment, attach evidence and resolve open reporting questions.
Actuarial extracts, GASB support, audit binders and board packets share the same traceable record.
Explore the operating model
Each page answers a different buyer question: why the reporting cycle hurts, how 37Act fits around existing systems, what implementation looks like, and how governance is handled for sensitive public pension workflows.
The site now supports more than a single landing page: it gives buyers paths into the problem, integration model, implementation plan, governance story, and SEO pillar topics.
Speak directly to administrators dealing with source file uncertainty, late exceptions, audit pressure, and board packet deadlines. Read the pain-point guide.
Explain how 37Act plugs into existing pension, payroll, finance, actuarial, audit, and document workflows without a rip-and-replace project.
Frame the offer as a focused workflow assessment and design-partner pilot that becomes a repeatable annual reporting platform.
Build trust with role-based access, source lineage, evidence management, approval history, and controlled exports.
Give teams practical source-file inventories, validation maps, exception logs, evidence checklists, and board packet readiness reviews.
Keep public sources, Government Code references, report examples, and buyer questions flowing into guide updates and product assumptions.
Own long-tail searches around 37 Act reporting software, CERL requirements, GASB support, actuarial data, and board packets.
Give serious buyers a clear next step: map their actual reporting cycle, files, owners, exceptions, and outputs.
The site should answer the practical questions a CFO, administrator, reporting manager, or board-support team will ask before a design-partner conversation.
37Act is for California county retirement systems governed by the County Employees Retirement Law of 1937, especially finance, reporting, operations, actuarial, audit, and board-support teams.
It replaces disconnected spreadsheet assembly and scattered evidence tracking. It does not replace the core pension administration system, finance system, auditor, actuary, or legal review.
BI tools visualize data. 37Act is positioned around the reporting cycle itself: source intake, validation, exceptions, evidence, schedule preparation, review, approvals, and packet output.
The workspace organizes source schedules, supporting calculations, employer disclosure package inputs, reviewer signoff, and export history so GASB support is traceable and repeatable.
Yes. The current offer is best framed as a workflow assessment and pilot workspace built around one system’s actual reporting cycle, source files, and board/audit deliverables.
We are looking for a small group of retirement-system finance, operations, actuarial, audit, and executive teams to pressure-test the reporting model with real workflows.
Book a working sessionResearch-backed explainers and positioning notes for California 1937 Act retirement reporting, GASB support, audit evidence, and board packet workflows.
A practical source-file inventory checklist for California 1937 Act / CERL reporting teams preparing actuarial data, GASB support, audit evidence, and board materials.
How to market 1937 Act reporting software credibly without overclaiming legal, actuarial, audit, or official government approval.
The recurring operational reasons 1937 Act retirement reporting gets rebuilt in spreadsheets — and the workflow layer that can make it repeatable.
CERL system index
Explore county pages
Jump into county-specific reporting context pages for the CERL systems identified from VCERA’s 1937 Act systems reference.