Decisions to Finalize Before HRIS Configuration Starts (2026)
Finalize these HRIS configuration decisions before the build starts, from GL mapping and position management to timekeeping rules, benefits and workflows.

.png)
Most HRIS rework comes from decisions that were still open when configuration began.
Use this checklist of HRIS configuration decisions, from general ledger mapping and position management to timekeeping rules, to settle the choices your vendor needs before the build starts.
Key Takeaways
- Your vendor's implementation team configures the choices you give it, so the decisions about how your business should run inside the system belong to you.
- Ten decision areas shape almost every HRIS build: organization structure, staffing model, job architecture, pay groups and calendars, earnings and deductions, general ledger mapping, timekeeping rules, benefits eligibility, workflows and security, and data and integrations.
- Some of the most expensive decisions to change later are position versus job management, general ledger mapping and timekeeping rules, because they flow into payroll, finance and compliance.
- Timekeeping rules carry legal weight: federal overtime applies after 40 hours in a fixed 168-hour workweek, and states such as California add daily overtime after 8 hours.
- Settling these decisions before kickoff, in a "Phase 0," gives the build a stable blueprint and keeps change orders down.
Configuration is where your new HRIS starts to look like your company.
It is also where unfinished decisions become expensive.
When a vendor's implementation team asks how overtime should calculate, which cost center a shift differential should post to or whether a role needs an approved position before a hire, someone on your side has to answer.
If the answer is "we will figure it out later," the build either waits or moves ahead on a default that may need rework during testing.
This guide lists the HRIS configuration decisions to finalize before the build starts, who should own each one and why each one is hard to change later.
All figures and rules in this guide were verified in November 2026.
OutSail helps mid-market companies select and implement HR systems that go live on time and get used – not just go live on paper.
Get your free readiness assessment to find out which configuration decisions are still open before your vendor starts building.
The Short Answer
Before HRIS configuration starts, finalize the decisions that every later step depends on.
That means your organization structure and legal entities, your staffing model, your job architecture, your pay groups and pay calendars, your earnings and deduction codes, your general ledger mapping, your timekeeping and overtime rules, your benefits eligibility rules, your approval workflows and security roles, and your data conversion and integration scope.
Each decision needs a named owner, a documented answer and sign-off before the vendor builds on it.
HRIS Configuration Decisions at a Glance
Why These Decisions Belong to You, Not the Vendor
Most vendors will show you several ways to configure the same process.
What they will not do is decide which one fits your policies, your budget controls or your union rules.
The implementation team's job is to configure the system to your decisions, which is why buyers who expect the vendor to supply best practices often end up with default settings instead.
For more on that split, see Your Vendor's Project Manager Works for the Vendor.
Late decisions also turn into scope changes.
PMI's 2018 Pulse of the Profession found that 52% of projects completed in the prior 12 months experienced scope creep or uncontrolled changes to scope.
And implementation problems are where most software regret begins: Capterra's 2026 Software Buying Trends Report found that 89% of buyers who regret a software purchase first hit an unexpected disruption during implementation.
What Is Phase 0 in an HRIS Implementation?
Phase 0 is the work your team does before the vendor's formal kickoff and configuration begin.
It turns the requirements from selection into concrete design decisions, names an owner for each one and confirms your team, data and integrations are ready.
Paycom describes the same starting point in its HRIS implementation timeline guide, listing pay groups, EINs, tax jurisdictions and approval workflows among the first things to scope.
OutSail's HRIS implementation support is built around this phase, so the requirements and decisions made during selection transfer directly into the implementation blueprint.
A free HRIS implementation readiness assessment is a fast way to see which of these decisions are still open.
The HRIS Configuration Decisions to Finalize
1. Organization Structure and Legal Entities
Start with the skeleton every other setting attaches to.
Confirm your legal entities and EINs, work locations, departments, divisions and reporting lines.
Decide which structures are for payroll and tax, which are for reporting and which are for approvals, since they are often not the same.
Decide before the build: a signed-off org structure with every entity, location and department listed.
2. Staffing Model: Position Management or Job Management
This is one of the most consequential HRIS configuration decisions, and one of the hardest to reverse.
Under position management, each role exists as a position that can be filled, vacant or frozen, and it persists when an employee leaves, which supports headcount control and budgeting (ERP Research).
Under job management, employees are tied to job definitions without dedicated seats, which is faster and more flexible but gives finance less control over headcount.
A UK government HR design document puts the timing plainly: deciding between job and position management is an important decision that should be made prior to the design phase of implementing an HCM solution.
Many mid-market companies use a mix: position management for salaried and leadership roles where budgets matter, and job management for high-volume hourly roles where speed matters.
Decide before the build: which staffing model applies to which parts of the organization, and who approves new positions or hires.
3. Job Architecture and FLSA Classification
Clean job codes, titles and grades make every downstream report and pay range easier.
They also carry compliance weight.
The Department of Labor's Fact Sheet #17A states that job titles do not determine exempt status, so each job's FLSA classification should be reviewed on its duties and salary, not its name.
Use the move to a new system to consolidate duplicate titles and retire codes no one uses.
Decide before the build: a final job catalog with codes, grades, pay ranges and an exempt or nonexempt classification for each job.
4. Pay Groups, Pay Frequencies and Pay Calendars
Decide which employees are paid on which schedule, such as weekly for hourly staff and semimonthly for salaried staff.
Build pay calendars for at least the first year, including pay dates, period end dates and holiday adjustments.
Plan the go-live date around them, since switching mid-quarter or near year-end adds reconciliation work.
Decide before the build: pay groups, frequencies and a full calendar of pay periods and pay dates.
5. Earnings and Deduction Codes
Every earning and deduction in your current payroll needs a home in the new system, with the right tax treatment.
That includes regular pay, overtime, bonuses, commissions, shift differentials, retroactive pay, pre-tax and post-tax deductions, garnishments and employer contributions.
This is also the moment to retire codes that no longer serve a purpose.
Mistakes here land directly in paychecks: an updated EY analysis commissioned by Paycom estimates that each payroll error costs an average of $339 to correct.
Decide before the build: a mapped list of every earning and deduction code, old to new, with tax treatment confirmed.
6. General Ledger Mapping
Every payroll produces journal entries, and finance needs them to land in the right accounts and cost centers.
Decide how earnings, taxes, deductions and employer costs map to your chart of accounts.
Decide whether labor costs post by department, location, project or a combination, and whether employees who split time need labor allocation.
GL mapping is easy to treat as a finance detail and hard to fix after go-live, because every payroll that posts incorrectly needs a correcting entry.
Decide before the build: a signed-off GL mapping that finance has reviewed line by line, plus the format and timing of the journal entry file.
7. Timekeeping, Overtime and Accrual Rules
For companies with hourly employees, timekeeping rules are where configuration decisions carry the most legal risk.
Start with the workweek: under the FLSA, overtime is owed for hours over 40 in a workweek, defined as a fixed and regularly recurring period of 168 hours, and hours cannot be averaged across two or more weeks (DOL Fact Sheet #23).
Then layer in state rules.
California, for example, requires overtime for hours over 8 in a workday and double time for hours over 12 in a workday (California Labor Commissioner).
Decide your rounding rules carefully: federal regulations accept rounding to the nearest 5 minutes, tenth of an hour or quarter hour only where it averages out so employees are paid for all time actually worked (29 CFR 785.48).
Also settle meal and rest break rules, shift differentials, holiday pay, on-call pay and how paid time off accrues, caps and carries over.
Decide before the build: a written timekeeping policy covering workweek start, overtime by state, rounding, breaks, differentials and accrual rules for every employee group.
8. Benefits Eligibility Rules
Benefits configuration depends on eligibility rules your team has to define.
Decide which employee groups are eligible for which plans, what waiting periods apply and when coverage starts and ends.
For applicable large employers, the IRS treats an employee as full-time for a month if they average at least 30 hours of service per week or 130 hours of service per month (IRS), so decide which measurement method you will use for variable-hour employees.
Decide before the build: eligibility rules by plan, waiting periods, ACA measurement method and carrier file requirements.
9. Approval Workflows and Security Roles
Workflows decide who approves hires, pay changes, time off and timecards.
Security roles decide who can see and change salaries, Social Security numbers and bank details.
Map both to your current org chart, and decide what happens when an approver is out or a manager changes.
Decide before the build: approval chains for each major process and a role-based access matrix that HR and IT have both signed.
10. Data Conversion Scope and Integrations
Decide how much history moves into the new system and how the rest will be archived.
The FLSA requires employers to keep payroll records for at least 3 years and the records behind wage computations for 2 years (U.S. Department of Labor), so the archive needs to stay accessible.
Then confirm the system of record for each data element and list every integration, such as benefits carriers, retirement plan providers, the general ledger and timekeeping.
OutSail's complete guide to HRIS data migration covers the conversion side in depth.
Decide before the build: conversion scope, archive plan, system of record for each data element and an integration inventory with an owner for each connection.
OutSail helps mid-market companies select and implement HR systems that go live on time and get used – not just go live on paper.
Explore OutSail Guide to turn your selection decisions into an implementation blueprint and track every open configuration decision through go-live.
How to Run Phase 0 Decision-Making
A list of decisions only helps if someone drives them to closure.
- Name an owner for every decision: one person accountable for the answer, even when several teams weigh in.
- Set a decision deadline before kickoff: give each owner a date, and track open items weekly.
- Use real scenarios: test each decision against real employees, such as a California hourly worker who works a double shift or a manager who changes departments mid-period.
- Write it down: keep a decision log the vendor receives at kickoff, so nothing has to be re-explained.
- Get sign-off from finance and payroll: GL mapping, earnings, deductions and timekeeping rules should never be approved by HR alone.
- Protect the decision-makers' time: the payroll and HR leads who own these decisions often carry two to three days a week of project work, as covered in How Many Hours Will Your Team Spend on an HRIS Implementation?
What Happens If You Start Configuration Without These Decisions?
Open decisions do not stop a vendor from building.
They lead to defaults, placeholders and assumptions that look fine until testing.
The most common symptoms are parallel payroll results that do not match, journal entries finance cannot reconcile, overtime that calculates differently from your policy, benefits offered to the wrong employees and approval chains that route to people who no longer manage the team.
Each of those means reopening configuration, retesting and often a change order.
A few weeks of Phase 0 decisions usually costs far less than one round of rework after testing begins.
How Can OutSail Help You Finalize HRIS Configuration Decisions?
OutSail is an independent HR technology advisory firm built to help mid-market companies select, implement and get real value from the systems that run HR.
Brett Ungashick and the OutSail team specialize in HR technology advisory, HRIS selection and consultant matching – working alongside your team so the system your vendor builds reflects how your company actually works.
OutSail treats Phase 0 as part of getting implementation right.
OutSail Select, which is free for most HR technology selection projects, includes an implementation readiness assessment (OutSail pricing).
OutSail Elevate, which starts at $30k, adds implementation prep work, IT and integration mapping and a handoff of the blueprint to implementation.
OutSail Guide, which starts at $7.5k, covers implementation readiness, blueprint knowledge transfer, vendor accountability tracking, project milestone management and escalation management through go-live.
For the hands-on configuration, OutSail's consultant matching connects you with specialists vetted for platform expertise, client references and delivery record.
The guidance is independent by design.
OutSail runs on a software broker model: more than 220 partner vendors each pay a similar commission, and roughly 90% of clients never pay a cent for the core selection service.
That approach shows up in outcomes like Olo saving $300K over three years and VetnCare choosing its HR tech in 30 days, just in time for a year-end transition.
We know a configuration built on open decisions costs more to fix in testing than to settle up front.
Every recommendation we make points at one outcome – a system configured for your policies, not the vendor's defaults.
Meet the Founder of OutSail
Meet the founder and CEO of OutSail – Brett Ungashick:
- As founder and CEO of OutSail, Brett brings years of hands-on experience in HR technology selection, negotiation and implementation, drawn from advising 1,500+ organizations on their HR systems.
- Brett began his career selling HR technology at LinkedIn, where he saw how hard it was for buyers to compare an increasingly crowded market, and founded OutSail in 2018 to put independent, buyer-side expertise into the process.
- OutSail's data-driven approach has supported more than $100M in HR software purchases, saved clients 100,000+ hours of work and earned an 83 NPS, working with companies such as DoorDash, Salesloft, Olo, Houzz and AuditBoard.
What Does Working With OutSail Look Like?
OutSail operates as a dedicated extension of your team – not a vendor that disappears after a kickoff call.
Every engagement includes direct access to advisors, transparent guidance tied to real project outcomes and a plan built around your systems, budget and internal bandwidth.
It runs from a tech stack audit and requirements building through selection and negotiation, and on to Phase 0 readiness, implementation support or a matched consultant when the work moves to the build.
OutSail helps mid-market companies walk into configuration with decisions made – not questions waiting for answers.
Final Thoughts: Decide First, Then Configure
Every HRIS build runs on decisions.
The ones you make before kickoff become a clean blueprint, and the ones you leave open become defaults, rework and change orders.
Give each of the ten decision areas an owner and a deadline, test the answers against real employees and hand the vendor a signed decision log on day one.
OutSail helps mid-market companies select and implement HR systems that go live on time and get used – not just go live on paper.
Talk to an OutSail advisor to work through your GL mapping, staffing model, timekeeping rules and other configuration decisions before your build starts.
Frequently Asked Questions
What decisions should be made before HRIS configuration starts?
Finalize your organization structure, staffing model, job architecture, pay groups and calendars, earnings and deduction codes, general ledger mapping, timekeeping rules, benefits eligibility rules, approval workflows and security roles, and data conversion and integration scope.
Each needs a named owner and sign-off before the vendor builds on it.
What is Phase 0 in an HRIS implementation?
Phase 0 is the preparation work before the vendor's formal kickoff and configuration.
It turns selection requirements into design decisions, names owners for each one and confirms your team, data and integrations are ready for the build.
Should we use position management or job management in our HRIS?
Use position management where finance needs tight headcount and budget control, such as salaried and leadership roles.
Use job management where hiring speed matters more, such as high-volume hourly roles.
Many mid-market companies use a mix, and the choice should be made before design begins.
Why does general ledger mapping need to be decided early?
Every payroll posts journal entries to your general ledger.
If earnings, taxes, deductions and employer costs map to the wrong accounts or cost centers, finance has to correct every affected payroll.
Settling the mapping with finance before the build avoids that rework.
What timekeeping rules should be set before HRIS configuration?
Set your workweek start, overtime rules for each state you operate in, rounding rules, meal and rest breaks, shift differentials, holiday pay and paid time off accruals.
Federal overtime applies after 40 hours in a fixed 168-hour workweek, and some states, such as California, add daily overtime.
Who should own HRIS configuration decisions?
Your company should, not the vendor.
HR typically owns org structure, jobs and workflows, payroll owns pay groups, earnings, deductions and timekeeping, finance owns GL mapping and staffing budgets, and IT owns security and integrations.



.png)
