37Act Guide

A reporting control plane for California retirement teams

Explore platform modules for 1937 Act retirement reporting: contribution intake, actuarial data packages, GASB support, audit trail, and board packet automation.

37Act is the reporting control plane between existing systems and final public-facing outputs. It is designed for the annual work that county retirement teams repeat: collecting source files, validating inputs, resolving exceptions, preparing actuarial and GASB support, preserving audit evidence, and assembling board materials.

Explore the operating pages for reporting pain points, integration strategy, implementation planning, and security and governance. Then continue into the SEO pillar pages for 37 Act reporting software, CERL reporting requirements, GASB 67 and GASB 68 support, actuarial valuation data preparation, and board packet automation.

Product architecture

Purpose-built modules for a specialized reporting cycle.

The product should sell focus: not an ERP, not a core pension system, not generic BI — a reporting layer designed around recurring 1937 Act obligations.

01
INTAKE

Source intake hub

Controlled imports for payroll, employer contributions, member records, actuarial files, accounting schedules, and reviewer uploads.

02
RULES

Validation rules

Reusable checks for fiscal-year completeness, totals, status changes, contribution logic, and exceptions requiring human review.

03
GASB

GASB workspace

Structured support for GASB 67 plan reporting and GASB 68 employer disclosure packages, with source references and version history.

04
AUDIT

Evidence binder

An organized audit-supporting packet with imports, assumptions, adjustments, review notes, approvals, and final exports.

05
BOARD

Board packet builder

Generate executive-ready summaries, status exhibits, unresolved exception lists, and appendix files for board and committee meetings.

06
API

Integration-ready model

Start with CSV/XLSX/SFTP-style ingestion, then add direct integrations for each retirement system’s pension, payroll, and finance stack.

Packaging hypothesis

Start high-trust, high-touch, then productize.

For a niche govtech product, the website can sell software plus implementation support before the full product is mature.

Assessment

Discovery

Map current report cycle, source files, pain points, and board/audit deliverables.

  • ✦Reporting workflow inventory
  • ✦Data/source-system map
  • ✦Implementation readiness score
Start assessment

Pilot workspace

Design partner

Build the first fiscal-year reporting workspace around the system’s actual files and outputs.

  • ✦Validated import model
  • ✦Exception queue
  • ✦GASB/board packet prototypes
  • ✦Implementation support
Request pilot

Enterprise

Annual platform

Recurring reporting operations with support, integrations, role-based access, and controlled export workflows.

  • ✦Multi-cycle reporting history
  • ✦Role and approval workflows
  • ✦Integration roadmap
  • ✦Support and governance cadence
Discuss enterprise

CERL system index

Explore county pages

California 1937 Act retirement systems

Jump into county-specific reporting context pages for the CERL systems identified from VCERA’s 1937 Act systems reference.