Does 37Act require replacing the pension administration system?

No. The product is positioned as a reporting layer around existing systems, beginning with controlled file intake and expanding into direct integrations where useful.

Can a system start with spreadsheets or CSV files?

Yes. A practical first implementation can begin with CSV, XLSX, SFTP, secure upload, and structured templates before direct API integrations are added.

37Act Guide

Plug into existing pension, payroll, finance, actuarial, and audit systems

How 37Act can connect around existing pension administration, payroll, finance, actuarial, audit, and document workflows without replacing core systems.

Abstract reporting workflow with connected files and evidence packets

The strongest adoption message for 37Act is practical: we plug into the reporting environment you already have.

County retirement systems are unlikely to replace a core pension administration platform just to improve annual reporting. They are also unlikely to trust a generic BI layer with the nuance of actuarial, audit, GASB, and board workflows. 37Act should sit in between: a governed reporting workspace that connects source data, validation, review, evidence, and final outputs.

Integration principles

Start with files, not fantasy APIs. Many public-sector reporting workflows still depend on CSV exports, Excel workbooks, PDFs, secure file transfer, and manually reviewed schedules.
Preserve the source context. Every import should retain file origin, upload date, owner, fiscal year, version, validation result, and downstream use.
Build rules around the reporting cycle. Completeness, totals, exceptions, and review status are often more valuable than generic charts.
Automate after the workflow is proven. Direct integrations should follow a validated reporting model, not precede it.

Integration path

Start with reliable intake. Productize deeper connections over time.

The website should make adoption feel realistic: no rip-and-replace, no giant ERP migration, no generic data lake project.

Phase 1

Source inventory

Map pension administration, employer payroll, finance, actuarial, audit, investment, and board packet sources by fiscal year.

Phase 2

Controlled file intake

Standardize CSV, XLSX, PDF, SFTP, secure upload, and template-driven intake with owners and due dates.

Phase 3

Validation model

Apply completeness, totals, roll-forward, contribution, status-change, and exception checks that are visible to reviewers.

Phase 4

Direct integration roadmap

Where a system has stable APIs or database exports, automate recurring extracts after the reporting model is proven.

Connected sources

Designed for the reality of public pension reporting data.

The first version should win by being flexible around messy source inputs while preserving traceability.

PAS

Pension administration data

Member records, retirement status, service credit, benefit calculations, demographic fields, and fiscal-year extracts.

PAY

Payroll and employer reporting

Pay periods, covered compensation, contributions, adjustments, employer files, and reconciliation totals.

FIN

Finance and accounting schedules

General ledger support, investment schedules, receivables, contribution totals, and financial statement workpapers.

ACT

Actuarial requests

Valuation extracts, assumption support, census files, reconciliation notes, and versioned responses to actuary questions.

AUD

Audit workpapers

Evidence packets, reviewer comments, approvals, adjustments, source references, and final export history.

BRD

Board and committee packets

Narrative summaries, exhibits, exception status, appendix materials, and public-facing packet files.

Bring your source map to the first working session.

We will map where files originate, who owns them, how they are reviewed, and which outputs they support.

Request integration assessment