A mid-sized municipal government goes live on a new HCM platform. Six months later, the finance director discovers that the position control module was never configured to enforce authorized headcount. The system allowed hiring against vacant positions that had been frozen by the city council. Several hires that should have required council approval went through without it.
Position control is not a UKG feature. It is not a Ceridian feature. It is a governance requirement that the HCM system needs to be configured to enforce. The platform supports it. The implementation didn't configure it.
Position control
Position control is the foundational governance mechanism in public sector HCM: every employee occupies a funded, authorized position. Hiring against unfunded or unauthorized positions requires specific approval. Headcount by position type is reported to the governing body on a defined schedule.
RJR configures position control to reflect the client's specific authorization structure: what positions exist, how they are funded, what approval chain is required to fill a vacant position, and what reporting is generated for council or board review. This is not a default configuration. It requires mapping the client's appropriations structure, union contracts, and civil service rules to the position management module before any hiring activity goes into the system.
Public pension integration
Most public employees participate in defined benefit pension plans administered by state or local pension systems (PERA, PERS, CalPERS, TRS, and dozens of others) rather than private 401(k) plans. These pension systems have specific contribution structures, eligibility rules, and reporting requirements that differ from private retirement plans.
HCM integration with a public pension system requires:
- Correct identification of covered vs. non-covered employees and positions
- Contribution calculation using the pension system's definition of pensionable compensation, which often differs from gross wages
- Contribution remittance on the pension system's schedule, not the employer's payroll schedule
- Regular reporting to the pension system in the format it requires
RJR has implemented public pension integrations for municipal, county, and state agency clients. Each engagement begins with a review of the pension system's employer reporting requirements (the specific data elements, file formats, and submission timelines) before any configuration begins.
Bargaining unit step advancement
Many public sector employees are covered by civil service classification systems where pay advances through defined steps based on years of service, performance, or a combination. When multiple bargaining units are present (AFSCME, police and fire unions, management association), each may have different step structures, different advancement criteria, and different pay tables.
RJR configures step advancement logic as a scheduled process, not a manual one. Employees advance to the next step automatically when they meet the criteria, without requiring a payroll administrator to initiate the change. The configuration includes the rule that governs each bargaining unit, the effective date logic for step changes, and the retroactive pay calculation when a step advancement is approved after its effective date.
GASB reporting
Government entities follow Governmental Accounting Standards Board (GASB) reporting standards, not FASB. The HCM and payroll data that feeds into GASB-required disclosures (pension liability, OPEB obligations, compensated absence accruals) requires specific configuration to produce the data elements GASB reporting needs.
RJR works with the client's finance team to identify which payroll data elements feed into GASB disclosures and configures the reporting extracts accordingly. For clients preparing for their first audit under a new HCM platform, RJR participates in the auditor's data confirmation process.
Public records and transparency compliance
Public sector payroll data is generally subject to public records disclosure requirements. Employee names, job titles, and salary information are often releasable under state open records laws. Some jurisdictions publish payroll data proactively on transparency portals.
HCM configuration for government clients must account for the data elements that are releasable vs. protected. Social Security numbers, direct deposit information, performance evaluations, and medical information are protected even when general salary data is not. RJR reviews data access configurations and report outputs to ensure that records released in response to a public records request or posted to a transparency portal do not inadvertently include protected fields.
Topics
- government
- public sector
- HCM
- payroll compliance
- position control