Rewriting HRIS and ATS data structures for Virginia pay transparency law HRIS compliance
Virginia’s new pay transparency law HRIS obligations now apply to every employer in the state, from a single employee start up to a multi site enterprise. The law requires that employers disclose a good faith wage or salary range in all external and internal job postings, including promotions and transfers, and it bans any request for a candidate’s salary history during the hiring process. For HRIS managers, this shifts pay and job data from optional fields to regulated records, with direct consequences compliance if systems are not reconfigured quickly.
The first configuration change is structural, because core HR and recruiting systems must stop collecting salary history while still supporting accurate compensation decisions. In Workday, SAP SuccessFactors, UKG or BambooHR, that means deactivating any custom fields that store prior wage salary details, scrubbing historical application forms, and updating integrations so that no upstream ATS or background check vendor can push salary history into the employee record. The same logic applies in Greenhouse, iCIMS or Lever, where application templates, recruiter forms and interview scorecards must be rebuilt so that employers employees cannot accidentally ask for or log prior pay, even in free text notes.
At the same time, HRIS teams must expose structured salary ranges and pay ranges inside the job requisition workflow, because the law requires that employers disclose a clear salary range or hourly range for every posted role. That means defining compensation ranges and total compensation bands in the compensation module, linking each job profile to a specific pay range, and ensuring that job postings automatically pull the correct salary range and description benefits into the posting template. Without this linkage, recruiters will improvise ranges, which increases the risk of fines violation, civil action, and damages costs when employees or candidates challenge whether the posted ranges were set in good faith.
Data governance must now treat pay transparency as a regulated data domain, not a communications choice. HRIS leaders should align with HR business partners and legal counsel to define which fields count as compensation, which benefits compensation elements must be shown in postings, and how to handle current employees who move into new roles under the new transparency laws. A practical next step is to run a configuration audit against all job templates, offer letter templates and internal mobility workflows, then log remediation tasks in your HR change management plan, ideally aligned with a formal policy such as the one described in this guide to building a robust change management policy for HR information systems.
Operationalising good faith salary ranges and job posting workflows
The second configuration change focuses on how salary ranges are calculated, stored and surfaced in operational workflows that touch employees and candidates. Virginia’s law requires that employers disclose a good faith salary range or hourly pay range that reflects what they honestly expect to pay for the job, which means that six figure wide ranges or vague statements about competitive compensation will not satisfy the law’s requirements. For HRIS teams, this turns compensation bands and job architectures into auditable artefacts that must align with both internal equity and external market data across all relevant laws states.
Practically, HRIS managers should work with compensation specialists to define a methodology for setting each salary range, including the midpoint, minimum, maximum and any geographic differentials within the state. Those ranges must then be loaded into the HRIS compensation tables, mapped to job codes, and synchronised with the ATS so that every new job posting automatically includes the correct salary ranges and any description benefits that form part of total compensation, such as bonuses, equity or critical benefits. A structured approach also helps when current employees apply for internal roles, because the same pay transparency rules apply to internal postings, and employees will compare posted ranges with their existing compensation and benefits packages.
Workflow changes extend beyond data tables, because recruiter scripts, interview scorecards and hiring manager training must all reflect the new law. Recruiters need standard language for how they disclose salary, how they explain benefits compensation, and how they respond when candidates volunteer salary history without prompting, since the law only allows employers to rely on voluntarily disclosed history to increase an offer, not to anchor a lower one. HRIS teams should also align compliance calendars and filing processes, using tools similar to those described in this overview of HRIS related filing deadlines, so that audits of pay transparency data, job postings and compensation ranges occur on a predictable cadence rather than after a complaint.
Risk management now has a clear financial dimension, because the law authorises administrative fines for each violation and allows the Attorney General to bring a civil action, while employees have a private right of action with potential damages costs. Initial fines can reach significant amounts per incident, with higher fines for repeat offences, and only some posting violations benefit from a short cure period once notified. For HRIS leaders, the message is simple, because every misaligned job posting, missing salary range or stray salary history field is no longer a minor configuration bug, but a potential compliance failure that can trigger fines violation, legal scrutiny and reputational damage across the organisation.
Aligning Virginia pay transparency law HRIS changes with broader equity and multi state compliance
The third configuration change is strategic, because Virginia’s pay transparency law HRIS requirements are part of a wider pattern of transparency laws across multiple states. Jurisdictions such as Colorado, California, New York and Washington already require employers disclose salary ranges in job postings, and many also restrict the use of salary history to set compensation, which means multi state employers must harmonise their HRIS configuration rather than treating Virginia as an isolated edge case. For HRIS managers, this is an opportunity to standardise pay transparency, wage salary structures and compensation governance across the entire workforce, instead of building one off rules for each state.
That standardisation starts with a single source of truth for job architectures, pay ranges and total compensation elements, ideally maintained in a central HRIS like Workday or SAP SuccessFactors and then propagated to satellite systems such as ADP, Rippling or regional payroll engines. When employers employees operate across several states, the system should tag each job and employee record with jurisdictional attributes so that the correct transparency laws and posting requirements apply automatically, including whether a salary range must be shown and how benefits compensation should be described. A compliance calendar, such as the one outlined in this guide to using a compliance calendar for HRIS management, can help coordinate audits of job postings, pay data and employee communications across all relevant locations.
Internal equity pressures will intensify as current employees see public ranges for roles similar to their own, and HRIS data will be the first place they look for evidence of fair pay. Compensation analytics tools that sit on top of the HRIS can help identify outliers, but only if the underlying job, pay and benefits data is clean, complete and aligned with the law’s requirements on transparency and salary history. For HRIS leaders, the real test of Virginia’s pay transparency law HRIS impact will not be the first week of configuration changes, but whether the system still produces consistent, compliant and trusted compensation data eighteen months after go live, when audits, employee questions and cross state comparisons all converge on the same set of records.
References
Asanify – analysis of Virginia’s salary history ban and pay transparency requirements.
Epstein Becker Green – Workforce Bulletin coverage of Virginia’s pay transparency and salary history restrictions.
Gartner – research on HR technology risk, compliance and pay equity analytics.