Requirements for an agency HR, payroll, and time system replacement

Reference article · 5 min read

An agency that replaces an HR, payroll, and time system is usually replacing something that has absorbed decades of local rules. Those rules live in a personnel ordinance, in a stack of memoranda of understanding, in a civil service rule book, in a retirement system's reporting layout, and in code written by a programmer who left years ago. Whether the replacement goes well depends mostly on how much of that was written down before anyone spoke to a vendor.

Commercial HR software assumes an employer that can change its own pay practices when the software makes a practice inconvenient. Public employers generally cannot. Pay ranges are adopted by a governing body, classifications are governed by civil service rules, and many differentials exist because they were bargained. That makes public-sector requirements less a feature checklist and more a description of behavior the new system must reproduce exactly. What follows are the requirement areas that are distinctly public sector, and how to write each one so acceptance can actually be judged.

Classification, step plans, and position control

Keep three related objects distinct in your requirements, because vendors often collapse them:

Classification. The class specification adopted under civil service rules, with its bargaining unit assignment, exam and eligibility linkage, and its FLSA exempt or non-exempt designation.
Salary schedule. The range and steps adopted by the governing body, plus the rules for step advancement: months of service, anniversary versus fiscal date, evaluation on file, and any freeze in effect.
Position. The funded, budgeted slot, with its position number, its funding string or split across several funds and grants, and its authorized, frozen, or abolished status.

Position control is the item most often underspecified. Write it as behavior: the system must block appointment into an unfunded or unauthorized position, must allow a position to carry two incumbents during a planned overlap, must retain vacancy and incumbent history for budget reporting, and must allow a position's funding split to change mid-year without altering payroll history already posted.

Pay rules that come from labor agreements

Inventory every pay rule in every active agreement before writing this section. Typical items include out-of-class or acting pay that begins after a threshold of consecutive hours, bilingual and specialty assignment pay, standby and callback with minimum hour guarantees, shift differentials keyed to the shift assigned or to where the majority of hours fall, longevity steps, and allowances that may or may not be taxable.

Two federal points deserve care. Overtime under the Fair Labor Standards Act is generally computed on a regular rate that includes certain other compensation, not on base pay alone, and public safety employers may use an alternative work period provision for law enforcement and fire personnel. The details are fact specific and have been litigated often, so confirm your interpretation with counsel rather than assuming the vendor's default configuration matches it.

Retroactive pay and corrections

Retroactive pay is a routine consequence of settling an agreement after its term began, and it is where legacy systems most often required manual spreadsheets. Require the system to recompute pay across closed periods, recalculate the overtime regular rate for those periods, and handle employees who changed classification, changed funding, went on leave, or separated during the retroactive window. Require a per-employee audit trail showing the original amount, the recomputed amount, and the difference by pay period, and require that retirement reportable and non-reportable components be identified separately.

Retirement, tax, and outbound reporting

Retirement reporting is usually the single hardest interface. Specify the exact system or systems you report to, every membership tier or plan you carry, how reportable compensation is defined for each, how service credit is earned for part-time and seasonal staff, and how prior period adjustments are transmitted. Write the same specificity for wage reporting, new hire reporting, garnishments and support orders, deferred compensation remittance, dues remittance, and year-end tax forms. Formats, thresholds, and filing rules change, so require the vendor to maintain compliance updates as part of the maintenance obligation, and confirm current requirements with the retirement system and the taxing authorities rather than relying on secondary sources.

Time capture, scheduling, and leave

Most agencies have several distinct populations: office staff on exception reporting, field crews charging hours to grants and capital projects, and around-the-clock public safety staff on rotating schedules. Describe each population separately, including how hours reach the general ledger for cost allocation. Leave requires its own treatment: accrual rates that differ by bargaining unit and years of service, caps and cash-out rules, compensatory time in lieu of overtime with its own cap, donated leave, and the interaction between protected leave and paid leave balances.

Writing requirements that can be tested

Convert each rule into three parts: the condition, the expected result, and the evidence a tester would look at. "System supports shift differentials" cannot be failed. "When an employee assigned to the night shift works a holiday, the system pays the night differential on holiday hours and includes it in the FLSA regular rate" can be.

Use real scenarios. Build a scripted demonstration set from anonymized production cases, including an ugly one: a mid-period promotion with a retroactive adjustment and a grant-funded split.
Separate configuration from customization. Ask which rules are configurable by agency staff, which require vendor services, and which require source changes that you will have to carry through every upgrade.
Ask who converts and reconciles data. History, balances, and accruals must tie out, and the requirement should name the reconciliation standard.
Put the rule inventory in the contract. Attach the pay rule list and the acceptance scenarios as an exhibit, tie payment milestones to passing them, and state what happens when a new agreement adds a rule after go-live.

HQT works with state and local agencies on requirements definition, systems engineering, and software delivery for enterprise administrative systems.

Frequently asked questions

What is position control and why does it matter in a government payroll system?

Position control ties employment records to funded, authorized positions rather than only to people. It lets an agency block appointments into unfunded or abolished positions, track vacancies for budget purposes, and allocate salary costs across funds and grants. Commercial HR products often treat a position as an optional attribute of a job record, so agencies should state position control as a set of required behaviors and test it with real budget scenarios.

How much of our labor agreements should go into the RFP?

Include a complete inventory of pay rules, differentials, accrual rules, and overtime provisions, written as conditions and expected results rather than as narrative excerpts. Vendors cannot price or configure what they cannot see, and rules discovered after award are the most common source of change orders. You can attach the inventory as an exhibit and reference the agreements themselves for full text.

Should we buy the payroll module from our ERP vendor or a separate HCM system?

Either approach can work, and the deciding factors are usually how the time, labor distribution, and general ledger interfaces behave and who owns them when something breaks. A single vendor reduces integration ownership questions but may fit your pay rules less closely. Evaluate both against the same scripted scenarios rather than against product feature lists, and ask specifically how payroll results reach the general ledger and how errors are corrected.

How do we write retroactive pay requirements when contracts are still being negotiated?

Write them from the mechanics rather than the outcome, since the mechanics do not change with the settlement amount. Require recomputation across closed pay periods, recalculation of the overtime regular rate, correct handling of employees who changed classification, funding, or employment status during the window, separation of retirement reportable amounts, and a per-period audit trail. Then test those mechanics using a prior settlement as the scenario.

What should we do before we talk to vendors at all?

Assemble the rule inventory: classifications and salary schedules, every pay rule in every agreement, leave and accrual rules by unit, position and funding structures, and every outbound interface with the entity that receives it. Identify which rules are policy choices your agency could change and which are fixed by ordinance, bargaining, or statute. That document becomes the backbone of the requirements, the demonstration scripts, and the acceptance criteria.