HCM implementation contracts: milestones, parallel payroll, and holdback

Reference article · 6 min read

An HR and payroll modernization deal has two halves: the license or subscription for the software, and the implementation services that make it run your agency's pay rules. The second half carries most of the risk and is usually described in the least detail. A vendor proposal may quote a single fixed implementation fee with payments tied to calendar dates or to the start of each phase, and never state what the agency has to see before a payment is earned.

That gap matters more in payroll than in almost any other system. Payroll has an unusually clear definition of correct: it either produces the right net pay, the right deductions, the right employer contributions, and the right tax and retirement reporting, or it does not. A payment schedule keyed to elapsed time gives away the leverage an agency needs to insist on that standard. Fixing it is mostly a matter of writing down a few things the parties otherwise leave to good intentions.

Tie milestones to signed deliverables, not dates

A milestone is only useful if a person can look at something and decide whether it exists. Replace "Phase 2 begins" with a named artifact and an acceptance step.

Named deliverable. Each milestone lists the document, configuration, or test result that must be produced, and who on the agency side reviews it.
Acceptance window. The agency gets a stated number of business days to accept or reject in writing. Include a deemed-accepted provision so the vendor is not exposed to indefinite silence, but make the window long enough for real review by payroll, HR, finance, and IT.
Rejection and cure. A rejection must state the deficiency. The vendor re-delivers, and the clock restarts only on the items rejected.
No payment for mobilization alone. Some up-front payment is normal and reasonable. Front-loading most of the fee before any configuration is demonstrated is not.

Make configuration sign-off mean something

Configuration sign-off is the milestone agencies most often accept without knowing what they approved. Define its contents in the statement of work: pay codes and earning types, accrual rules for each leave category, overtime and premium calculations by bargaining unit, benefit plans and deduction schedules, retirement plan tiers and employer contribution rules, garnishment handling and priority, labor distribution and position funding, and the security roles that control who can change any of it.

Require that sign-off be supported by a demonstration in the configured system using your own data, not a generic demonstration environment. Require a written record of open items at sign-off so nobody later disputes what was known.

Parallel payroll is the acceptance test

Parallel payroll is the only test that proves the system computes your pay correctly. Write it into the contract rather than treating it as an informal step.

Same inputs, both systems. The legacy system and the new system process the same pay period from the same time and attendance and personnel data.
Employee-level comparison. Compare gross to net for every employee, not totals. Totals can match while individual errors offset each other.
Define "clean." A clean cycle means every variance is either zero or documented, explained, and accepted in writing by the agency, usually because the new result corrects a known legacy error.
Require consecutive clean cycles. Two or three consecutive clean cycles is a common standard. Consecutive matters: one clean run after several failures may reflect manual intervention rather than working configuration.
Cover real complexity. Specify that the cycles include retroactive pay, shift and assignment differentials, overtime across bargaining units, garnishments and arrears, off-cycle and supplemental payments, and employer contribution reporting to your retirement systems.

Also test the downstream products, not only the paycheck. Confirm general ledger postings, retirement system reporting files, state unemployment and new hire reporting, and the balances that will feed quarterly federal payroll returns and year-end wage statements. Reporting requirements and formats change, so confirm current specifications with each receiving agency rather than relying on the vendor's description.

Assign data conversion responsibilities explicitly

Conversion disputes consume schedule and budget. Say in writing which party extracts, which party cleanses, which party maps, which party loads, and which party validates. Name the specific data sets: employee demographics, position and job history, pay rates and step placement, leave balances, deduction elections, year-to-date balances for the conversion year, and any history needed for retirement service credit or grievance defense. Require a written reconciliation of record counts and control totals after each load, and decide in advance how many conversion cycles are included before change orders apply.

Name key personnel and keep them

Implementation quality tracks closely to the individuals assigned. Name the implementation manager, payroll functional lead, and technical lead in the contract by person. Require advance written notice of any substitution, agency approval of replacements, and equivalent qualifications. Consider a minimum commitment through the end of the acceptance period so the experienced team does not rotate off immediately after go-live.

Hold retainage through the first quarter-end and year-end

Go-live is not the end of payroll risk. Quarter-end and year-end processing exercise logic that never runs during a normal pay period: tax reconciliation, wage statement production, taxable fringe handling, and adjustments to prior-period balances.

Withhold a stated percentage of the implementation fee, released in parts: a portion after the required clean parallel cycles and successful first live payroll, a portion after the first live quarter-end close and reporting, and the balance after the first year-end close and wage statements are produced and reconciled. Retainage, prompt payment timelines, and withholding terms are governed by state and local procurement law, and those rules vary and change, so have counsel confirm what your jurisdiction permits before drafting.

Questions to ask before signing

What exactly must the agency approve at each milestone, and what percentage of the fee does each release?
How many parallel cycles are included in the fixed fee, and what happens if more are needed because the configuration failed?
Who is accountable for data cleansing, and how many conversion loads are included?
Which named individuals will be assigned, and what is their availability through year-end close?
What support level applies between go-live and final acceptance, and is it included?

HQT works with state and local agencies on systems engineering and technology advisory work, including reviewing acceptance criteria and implementation terms for enterprise administrative systems.

Frequently asked questions

How many parallel payroll cycles should we require before go-live?

Two or three consecutive clean cycles is a common standard for public sector payroll. Consecutive matters more than the raw count, because a single clean run following several failed ones may reflect manual fixes rather than correct configuration. Choose the number based on your complexity, including how many bargaining units, pay cycles, and retirement tiers you support. Write the required number and the definition of clean into the contract rather than leaving it to project discretion.

What counts as a clean parallel payroll cycle?

A clean cycle means the new system and the legacy system were run on the same pay period using the same source data, and every employee-level difference in gross to net is either zero or documented and accepted in writing by the agency. Comparing only totals is not sufficient, because individual errors can offset one another and still produce matching sums. Accepted variances are usually cases where the new system corrects a known legacy error. Keep the reconciliation records, since they become the evidence supporting milestone payment.

Can a government agency hold retainage on a software implementation contract?

Many state and local jurisdictions allow withholding on services contracts, but the rules differ and are often addressed in procurement codes, prompt payment statutes, or standard terms issued by a central purchasing authority. Requirements change over time, so confirm the current rules with your procurement office and counsel before drafting a holdback provision. Where retainage is permitted, tie each release to a specific verifiable event rather than to a date.

Who should be responsible for cleaning up payroll data before conversion?

Data cleansing usually belongs to the agency, because only agency staff can decide what a record should say, but the contract should state that explicitly rather than assume it. The vendor typically owns mapping, load execution, and error reporting. Specify how many conversion loads are included in the fixed fee and require a written reconciliation of record counts and control totals after each one. Ambiguity here is one of the most common sources of schedule slip and change orders.

Why hold part of the fee until after year-end close?

Quarter-end and year-end processing exercises logic that never runs in a normal pay period, including tax reconciliation, wage statement production, taxable fringe handling, and prior-period adjustments. A system can process regular payrolls correctly for months and still fail at those events. Holding a portion of the implementation fee until the first live quarter-end and year-end close keeps the vendor engaged through the period when those defects surface.