Expat Payroll HQGlobal Hiring, EOR & Payroll Intelligence
Payroll

Nine Mistakes That Sink a Global Payroll RFP, and What to Ask For Instead

Most teams pick the slickest demo and discover a weak in-country partner after go-live. Here are nine common global payroll RFP mistakes, each paired with the question, scoring weight or contract clause that fixes it.

By the Expat Payroll HQ editorial team · November 2026 · 8 min read

Sending a Generic Template Instead of a Country Requirements Matrix

The first mistake happens before any vendor sees the document. Someone downloads a 200-question template, adds a logo and sends it out. Every vendor answers "yes" to almost everything, and the scoring tells you nothing. A global payroll RFP should start with your countries, not their features.

Build a one-page matrix with a row per country. Include headcount today and in 18 months, pay frequency, statutory extras, benefits and equity, filings you need handled, and required payslip languages. Statutory extras are things like the 13th-month payment in Brazil and the Philippines, or the additional annual salary payments (often called 13th and 14th salaries) common under collective agreements in parts of Europe.

Advertisement

Ask instead: "For each country in Appendix A, classify every requirement as native, configurable, manual workaround or not supported, and name the team that performs it." A vendor that won't fill in the grid has already answered.

Scoring the Demo Instead of a Gross-to-Net in Your Hardest Country

Demos use clean data in easy jurisdictions. Your problems show up elsewhere: a mid-month joiner in India, or a Brazilian employee taking vacation with the one-third bonus while an overtime adjustment lands in the same cycle.

Pick your hardest country and write an anonymized scenario. For India, that might be a new hire with provident fund, professional tax, a variable bonus and a mid-cycle salary change. Ask each finalist to return a full payslip and employer cost breakdown within about five business days. Then check the results against your current provider or a local adviser.

Ask instead: "Produce a gross-to-net calculation for the attached scenario, showing every statutory deduction and employer contribution with its rate and basis." Give this test real weight on the scorecard. One wrong social security ceiling tells you more than an hour of polished screens.

Not Asking Who Actually Runs Payroll in Each Country

Most multi-country providers own operations in some countries and use local partners in the rest. That's normal. The problem is the vendor that says "our global network" and never shows a country-by-country table.

Sound global payroll vendor selection depends on that table. You need to know whose staff process your data in Mexico, whose filing credentials are used in South Africa, and how long that relationship has lasted.

Payroll RFP questions to include:

  • Per country: owned operation or partner? If partner, how long have you worked together, and how many partner changes have you made in the last 24 months?
  • Who holds the employer's tax and social security portal credentials, and can we access them?
  • Can our team escalate directly to the in-country partner, or only through your support desk?
  • What happens to our service if a partner is replaced mid-year?

Red flag: a vendor that won't name partners even under NDA.

Accepting SLAs That Stop at the Aggregator

This is the most expensive mistake on the list. The master agreement commits the aggregator to answering tickets within one business day. Nothing commits the German or Philippine partner to deliver the preliminary register on time, file correctly or fix errors before payday. When something breaks, the aggregator points at the partner, and you have no contract with the partner.

Insist on an in-country payroll partner SLA that is flowed down and enforceable through the prime contract. Metrics should cover:

  • Input cutoff and preliminary register delivery, in days before pay date, per country
  • Calculation accuracy, measured as error-free payslips per cycle, with a very high target (vendors often offer 99% or better)
  • On-time statutory filing and payment, with no tolerance band
  • Response and resolution times for errors that affect pay, in hours, not days

Clause to request: "Supplier shall impose service levels no less stringent than this Schedule on each subcontractor and remains fully liable for subcontractor performance. Supplier shall reimburse penalties, interest and correction costs arising from supplier or subcontractor error." Service credits matter less than that reimbursement language.

Comparing Per-Employee Prices Without the Full Cost Stack

Vendors want you to compare the per-employee-per-month (PEPM) price, and it's often the least important number. The figures below are typical 2026 market ranges. They vary widely by country, volume and contract, so confirm them with each vendor.

Cost lineTypical 2026 range (USD)What to ask
PEPM processing$25–$120 depending on country and volumeMinimum fee per country?
Implementation$1,000–$6,000 per countryFixed or time-and-materials?
Off-cycle runs$50–$300 eachHow many are included?
Year-end and statutory certificates$5–$40 per employeeIncluded in PEPM?
FX on payroll funding0.2%–2% over mid-marketStated margin or "competitive rate"?

Hypothetical example: a 60-person company in six countries funds $350,000 of payroll a month. Vendor A quotes $45 PEPM, adds a 1% FX margin and charges $3,000 per country for implementation. Vendor B quotes $60 PEPM, a 0.25% FX margin and $2,000 per country.

Over the first year, Vendor A costs about $32,400 in processing, $42,000 in FX margin and $18,000 in implementation: roughly $92,000. Vendor B costs about $43,200, $10,500 and $12,000: roughly $66,000. The cheaper headline price loses, and FX is the reason.

Weighting the Scorecard Toward Polish

When the evaluation panel is mostly HR users, interface quality ends up weighted like accuracy. Your payroll vendor evaluation criteria should reflect what costs you money and trust when it fails. For many companies with 20 to 500 employees across several countries, this split works as a starting point:

CriterionWeight
Gross-to-net test accuracy25%
Compliance and filing ownership20%
SLA flow-down and service model15%
Three-year total cost15%
Integrations and data flows10%
Security and data protection10%
User experience and reporting5%

Fix the weights before the first demo and have finance sign off. Changing them after you've seen vendors usually just justifies whoever demoed best.

Writing "Integrates With Our HRIS" and Calling It a Requirement

Every vendor integrates with every popular HRIS, at least in the sales deck. What matters is which fields move, in which direction, how often, and who fixes a sync that fails two days before cutoff.

Write each integration as a data-flow requirement. Name the system of record for each data type and say whether changes are effective-dated. Specify GL journal mapping by legal entity and cost center, bank payment file formats (they differ by country) and whether connectors use APIs or scheduled file transfers.

Ask instead: "Provide a reference customer using our HRIS and ERP in at least two of our countries. State who builds and maintains the connector and the annual cost." If the answer is a services quote for a custom build, add it to the cost stack.

Treating Data Protection as a Checkbox

Payroll data is among the most sensitive you hold, and the rules vary by country. The EU and UK GDPR, India's DPDP Act, Brazil's LGPD, South Africa's POPIA, and data-protection laws in the Gulf states each set their own terms for cross-border transfers and breach notification. An aggregator's ISO 27001 certificate says nothing about a partner's laptop in a regional office.

Payroll RFP questions to include: a sub-processor list by country naming every in-country partner. Ask for the transfer mechanism for each data flow, breach notification timelines in hours, and where data is stored. Request a SOC 1 Type II report, which covers controls relevant to your financial reporting, plus a SOC 2 or ISO 27001 report, and ask which in-country partners those reports actually cover. Have privacy counsel review the answers, because transfer obligations depend on where your entities and employees are.

Signing Without an Exit Plan

Payroll contracts are easy to sign and painful to leave. That's especially true in countries with cumulative tax calculations, such as UK PAYE or Indian TDS, where a new provider needs exact year-to-date figures to calculate correctly mid-year. Record-retention periods, commonly several years and sometimes a decade depending on the country, also mean you need historical registers in a usable format.

Clause to request: "On termination, Supplier shall provide, within 15 business days and at no additional charge, complete payroll registers, year-to-date and cumulative tax data, and filing confirmations for all periods, in CSV or another agreed machine-readable format. Supplier shall also provide up to 90 days of transition assistance." Also set notice periods that let you switch at a tax-year boundary.

Your next step: shortlist no more than three vendors, run the gross-to-net test in your hardest country, and red-line the SLA flow-down and exit clauses before you discuss price. A vendor that resists any of those three has shown you what the next three years will look like.

Quick answers

How long does a global payroll RFP usually take?

Plan on roughly two to three months from requirements matrix to signed contract. Allow about three weeks for vendor responses, two for the gross-to-net test, and the rest for references and negotiation. Implementation is a separate phase, often a few months per wave of countries.

Should we use one aggregator or contract in-country providers directly?

With two or three countries, contracting local providers directly can cost less and give you more control. Past five or six countries, one aggregator's consolidated reporting, single contract and single funding process usually pay for themselves. Many companies run a hybrid: direct contracts in their largest country, an aggregator for the long tail.

How many vendors should we invite to the RFP?

Four to six is enough to see a real range of answers without overloading the panel. Take two or three finalists into the gross-to-net test and reference calls. Inviting more mostly adds scoring work without improving the choice.

Do we need outside advisers for a payroll vendor selection?

Have counsel review the liability, subcontractor and data-transfer clauses, since those terms decide who pays when something goes wrong. A local tax or payroll adviser in your hardest country is also worth paying to check the gross-to-net results, because your own team may not spot a wrong contribution ceiling.

Written by the Expat Payroll HQ editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.