Pension reporting interfaces between payroll and retirement systems

Reference article · 6 min read

Every pay cycle, a public employer has to tell its retirement system who worked, what they earned, how much of that pay counts toward a pension, how much service credit it represents, and how much money is attached. The transfer is usually a file or a web service call produced by the payroll or HCM system and consumed by the retirement system's employer reporting portal. When it works, nobody notices. When it drifts, the damage accumulates quietly: members with gaps in service, contributions posted to the wrong period, suspense balances nobody owns, and an audit finding that asks why a whole category of pay was never reported.

Pension reporting is not one interface. It is a set of related obligations that happen to travel together on the same schedule, and each has its own failure mode. Treating the whole thing as "the pension file" is how agencies end up with multi-year cleanup projects.

What actually moves each cycle

Enrollment and demographics. New hires, eligibility determinations, name and address changes, membership tier assignment, separations, and death or disability events. A detail record for an unenrolled member is one of the most common rejection causes.
Compensation by type. Not a single gross figure. Retirement systems generally want earnings broken out so the plan can apply its own rules about what counts.
Service credit. Hours, days, or fractions of a period, depending on the plan and the employment type.
Contributions. Member amounts withheld and employer amounts owed, usually at rates the plan sets and changes periodically.
Adjustments. Corrections to periods already reported, which need their own record structure rather than being folded into current pay.

Reportable versus non-reportable compensation

Most audit findings start here. Plan statutes and administrative rules define which earnings are pensionable, and the answers are rarely intuitive. Overtime, lump-sum leave payouts at separation, longevity pay, shift and assignment differentials, vehicle and uniform allowances, stipends, and one-time bonuses are each treated differently across plans, and often differently across membership tiers within the same plan. Many plans also apply anti-spiking rules or caps on final average compensation, and qualified governmental plans are subject to federal limits on includible compensation that are adjusted from time to time. Confirm current definitions and limits with the plan and your counsel rather than with prior practice.

The durable control is a mapping document: every payroll earnings code, its plan compensation type, and its reportable flag, with the rule citation or plan guidance that justifies it. Make it a governance rule that no new earnings code is created without a pension determination recorded at the same time. Most unreported special compensation findings trace back to a code added for one bargaining unit and never classified.

Service credit and pay period alignment

Retirement systems usually want credit and compensation attributed to the period worked, not the date the check cleared. Payroll systems are built around pay dates. Reconciling the two is the source of persistent low-grade error, especially at fiscal and calendar year boundaries, in biweekly years that contain an extra pay date, and for retroactive contract settlements that pay this period for work performed over many prior ones.

Watch the edge populations specifically: part-time and hourly employees whose credit is computed from hours, employees on leave without pay or workers' compensation supplements, employees holding two positions or working for two participating employers, seasonal and temporary staff, elected and appointed officials, and rehired retirees subject to working-after-retirement limits. Military leave carries its own federal service and contribution obligations that require documented handling.

Contributions, remittance, and the three-way match

The detail file and the money have to agree. Member contributions withheld, employer contributions, and any separate unfunded liability or rate stabilization payment may arrive on different schedules and post to different accounts. Many governmental employers also treat member contributions as employer-paid for federal tax purposes under a pickup arrangement, which has to be properly adopted and applied consistently.

Reconcile three numbers every cycle before the file is transmitted: deductions on the payroll register, contribution totals in the detail file, and the amount actually remitted. A variance caught the same week is a correction. The same variance found at year end is a research project.

Corrections and the aging problem

Distinguish rejections from warnings, and never let warnings become background noise. Typical rejects include unrecognized identifiers, members not enrolled, invalid earnings or status codes, duplicate reporting periods, and contributions outside tolerance for the compensation reported. Establish who owns each reject category, how quickly it must clear, and how adjustment records are generated so a correction does not duplicate the original. Many plans assess interest or charges on contributions remitted late, so an unresolved record has a cost that grows.

Keep an aging report of unresolved records by cycle and by cause. If the same cause reappears, fix the mapping or the process, not the record.

A reconciliation cadence that prevents cleanup

Each cycle. Transmit, clear rejects, and complete the three-way match before closing the period.
Monthly. Age unresolved items, review suspense, confirm every remittance posted.
Quarterly. Compare the active payroll roster to reported members. Investigate anyone paid but not reported and anyone reported but not paid.
Annually. Reconcile year-end payroll totals to reported pensionable compensation by employee, revalidate the earnings code mapping against current plan guidance, and review exclusions and rehired retirees.

What to ask during an HCM replacement

Ask vendors to demonstrate the interface for your specific plan and its current published reporting specification, not a generic pension export. Ask how earnings codes are mapped, who can change a mapping, and whether the change is logged. Ask how prior-period adjustments and retroactive settlements are generated, how a rejected batch is reprocessed without duplication, and which reconciliation reports ship as delivered functionality.

In the contract, name the plan's reporting specification version as a deliverable baseline, assign responsibility for updating the interface when the plan changes that specification, and write acceptance as several consecutive cycles accepted by the plan with a clean three-way match, not as "file produced." Require parallel reporting through cutover and a documented method for correcting pre-conversion periods after go-live.

HQT works with state and local agencies on systems integration and data reconciliation between enterprise payroll platforms and external reporting partners.

Frequently asked questions

Why does our retirement system keep rejecting the payroll file?

Most rejections fall into a few categories: an identifier the plan does not recognize, a member who has not been enrolled or whose status does not match, an invalid earnings or employment code, a duplicate reporting period, or contributions that fall outside the plan's tolerance for the compensation reported. Read the plan's reject codes literally and group them by cause rather than fixing records one at a time. A cause that recurs across cycles is usually a mapping or configuration problem, not a data entry problem.

How do we know which types of pay are reportable to the pension plan?

Reportable compensation is defined by the plan's governing statutes and administrative rules, and it often differs by membership tier and hire date. Items such as overtime, leave payouts, allowances, and one-time bonuses are treated inconsistently across plans, so prior practice is not a reliable guide. Build a written mapping from each payroll earnings code to a plan compensation type, confirm it with the retirement system and your counsel, and update it whenever rules or codes change.

What causes unreported special compensation audit findings?

They usually trace to an earnings code created for a specific group, such as a stipend or differential negotiated in one bargaining unit, that was never classified for pension purposes and so defaulted to non-reportable. The exposure grows every cycle until someone reviews the code list. A governance rule requiring a pension determination before any new earnings code goes live prevents the most common version of this finding.

How often should payroll and the retirement system be reconciled?

Reconcile the payroll register, the detail file totals, and the remitted amount every cycle before closing the period. Age unresolved items monthly, compare the active payroll roster to reported members quarterly, and reconcile year-end payroll totals to reported pensionable compensation by employee annually. Variances found within a cycle are corrections, while the same variances found years later become cleanup projects with potential interest charges.

What should we require in an HCM contract for pension reporting?

Name the retirement system's current published employer reporting specification as the baseline deliverable, and assign explicit responsibility for updating the interface when the plan revises that specification. Define acceptance as several consecutive cycles accepted by the plan with contributions and detail in balance, not simply as a file being produced. Also require parallel reporting through cutover and a documented method for correcting periods that predate conversion.