1. Define scope and requirements before contacting vendors
Vendors will shape your requirements if you let them. Do the internal work first.
Start by mapping the current state with HR, payroll, finance, and IT in the room:
- Headcount and entities: employees by country and state, legal entities, and expected growth over the contract term.
- Pay complexity: pay frequencies, union or collective agreements, shift differentials, overtime rules, commissions, equity, and garnishments.
- Modules in scope: core HR, payroll, time and attendance, benefits administration, performance, recruiting. Decide which are required now and which are future options.
- Integrations: general ledger, ERP, identity provider, benefits carriers, expense tool, and any downstream reporting.
- Pain points: list the specific failures of the current setup, such as manual retro pay calculations or off-cycle runs that take two days.
Sort each requirement into must-have, important, or nice-to-have. Keep the must-have list short. Every must-have should be something that would disqualify a vendor if it were missing.
2. Build a shortlist and write the RFP document
Send the full RFP to three to five vendors. With more than that, evaluation gets shallow. A short RFI can narrow a longer list if you need to.
Filter early on the hard constraints: countries supported natively versus through partners, company size the vendor actually serves, and whether payroll is run in-house or through a third-party engine.
A practical RFP structure:
- Company overview and project goals
- Scope, headcount, and entity details
- Requirements matrix, with each line answered as Standard, Configurable, Custom, Roadmap, or Not supported
- Integration and data migration questions
- Security and compliance questionnaire
- Implementation approach, team, and timeline
- Pricing template you provide, so quotes are comparable
- Timeline, contacts, and submission rules
The answer categories in step 3 matter. "Yes" is not a useful answer. Asking vendors to state how a feature is delivered exposes gaps that a sales deck will not show.
For pricing, require a per-employee-per-month (PEPM) breakdown by module, plus one-time implementation fees, and list the charges vendors often leave out: off-cycle runs, year-end forms, additional entities, API access, and sandbox environments.
3. Run scripted demos, not sales demos
A vendor's standard demo shows its best paths. Send your own scripts one to two weeks before the demo and ask every vendor to follow them in the same order.
Good scripts use your real scenarios. For example:
Scenario 4: An hourly employee in California works 11 hours on Tuesday, is promoted to salaried on the 18th of the month, and then receives a retroactive raise back to the 1st. Show the pay calculation, the approval flow, and the resulting journal entry.
Other scenarios worth scripting:
- A new hire through first payroll, including onboarding documents and tax setup
- A termination with final pay rules for a specific state
- Moving an employee between entities or countries
- Running a custom headcount and cost report without vendor help
- An employee self-service change, such as a bank account update, with its audit trail
Have the people who will use the system every day score each scenario live on a shared sheet. Ask for a sandbox afterward so your payroll team can repeat the hardest scenarios on their own.
4. Score responses with a weighted model
Agree on scoring weights before responses arrive. If you set them afterward, people will adjust them to favor the vendor they already like.
A common starting split, which you should adjust to your priorities:
- Functional fit and demo performance: 30 to 35%
- Payroll accuracy, compliance, and tax filing coverage: 15 to 20%
- Integrations and data migration: 10 to 15%
- Implementation approach and support model: 10 to 15%
- Total cost of ownership over the term: 15 to 20%
- Security and vendor viability: 5 to 10%
Score each area on a 1 to 5 scale with written definitions, so a 3 means the same thing to every evaluator. Collect scores independently before any group discussion.
Calculate cost over the full contract term, typically three years, including implementation, internal staff time, parallel payroll runs, and expected PEPM increases at renewal. The vendor with the lowest first-year price is often not the cheapest over the term.
5. Check security, compliance, and references
An HRIS holds Social Security numbers, bank details, salaries, and health-related data. Treat due diligence as a gate, not a formality.
Checklist:
- Current SOC 1 Type II (relevant for payroll controls) and SOC 2 Type II reports, plus a list of any exceptions noted
- Data residency, subprocessors, and GDPR or other regional compliance where it applies
- SSO, role-based access, and field-level permissions for sensitive data
- Tax filing responsibility: who files, who pays penalties for vendor errors, and in which jurisdictions
- Business continuity plan and the process for payroll if the system goes down on pay day
For references, ask for customers similar to you in size, industry, and countries, and ask for one who went live in the last 12 months. Useful questions: How long did implementation take compared with the plan? How many payroll errors came up in the first three cycles? How quickly does support resolve a payroll-blocking issue?
6. Negotiate the contract and implementation terms
Negotiate with at least two finalists so you keep leverage in the talks. Focus on the terms that protect you after signing, not only the discount.
Key terms to secure:
- Price protection: a cap on renewal increases, for example no more than a set percentage per year.
- Headcount flexibility: the ability to true down as well as true up, with a minimum commitment you can realistically meet.
- Implementation scope: a statement of work with named deliverables, the number of parallel payroll runs, data migration responsibilities, and fixed fees or a cap.
- Payroll accuracy remedies: vendor liability for tax penalties and interest caused by its errors.
- Service levels: uptime commitments, support response times for payroll-critical issues, and service credits.
- Exit and data return: full export of historical data in a usable format at no extra charge, plus transition assistance.
Example clause wording:
Vendor shall reimburse Customer for any penalties, interest, or fines assessed by a taxing authority to the extent caused by Vendor's error in calculating, filing, or remitting payroll taxes, provided Customer supplied accurate and timely data.
Do not sign until the statement of work and go-live plan are final. Most HRIS projects that fail do so in implementation, and a vague statement of work leaves you no way to hold the vendor to account.
Let pingpong run it for you
pingpong drafts the RFP, finds and invites vendors, collects proposals through a private portal, scores them with five AI models and flags the gotchas above. It drafts every negotiation message for your approval, then keeps watching the market so you renegotiate before renewal. $100 for the first month, then $799 a month.
Common questions
How long does an HRIS or payroll RFP usually take?
From requirements gathering to signed contract, many teams take roughly two to four months, depending on complexity and the number of countries involved. Implementation is separate and often runs three to nine months. Time your go-live around payroll calendars, and avoid year-end if you can.
Should we buy HRIS and payroll from the same vendor?
A single platform reduces integration work and avoids data syncing problems between systems. However, some all-in-one vendors are weaker at payroll in certain countries or for complex pay rules. Evaluate payroll on its own merits in your demos and score it separately before deciding.
How many parallel payroll runs should we require?
Two to three parallel runs is a common practice. Include at least one cycle that has unusual items such as bonuses, retro pay, or terminations. Write the number and the pass criteria into the statement of work so go-live depends on reconciled results, not on the calendar.