When you hire in a new country, the benefits conversation splits in two, and the split matters more than most people expect. There is what you have to provide, set by law and not up for negotiation, and there is what you choose to provide to be a good place to work. Mix the two up and you either overpay for things you assumed were optional, or you skip something that was never a choice.

You can feel the difference the first time you read a local employment framework. Half of it reads like a menu. The other half reads like a rulebook.

The line between required and offered

Statutory benefits are the ones the law puts on the employer. They are not perks, and they are not something you can trade away in exchange for a higher salary or a nicer laptop. In most countries this baseline includes some combination of paid annual leave, sick leave, public holidays, pension or social security contributions, and parental leave, with the exact shape varying by market.

Perks sit on top of that floor. Private health insurance where the state system already covers care, extra holiday beyond the legal minimum, a wellness budget, flexible hours. These are the discretionary layer, the part where you compete for talent rather than comply with statute.

The trap is assuming your home-country instinct for which is which travels. Something that is a generous perk in one country is a hard legal requirement in another, and the reverse is just as true.

What tends to be mandatory

Knowing statutory mandatory benefits for a given country is the starting point for any hire there, because it sets the real cost and the non-negotiable obligations. The categories that most often turn out to be required, rather than optional, include:

• Paid annual leave, often well above what a US employer would expect

• Public holidays, sometimes paid on top of annual leave rather than counted within it

• Sick leave, occasionally at full pay for a defined period

• Pension or social security enrolment and employer contributions

• Parental and family leave, with entitlements that can run for months

The amounts are where it gets specific. Statutory minimum leave might be a couple of weeks in one market and five or six in another. Employer social contributions can add a modest percentage to the salary or a substantial one. That variation is exactly why a hire that looks affordable on gross pay can cost meaningfully more once the mandatory layer is included.

Why treating perks like requirements (and the reverse) hurts

Two failure modes show up again and again. The first is offering a perk while missing a statutory duty, which is the dangerous one. If you provide private health cover but under-fund a mandatory pension contribution or under-count statutory leave, the shortfall is a compliance problem, not a hospitality one, and it can surface as back-payments and penalties.

The second is quieter. You treat a legal minimum as if it were a generous gesture, market it as a benefit, and pay a competitiveness cost when candidates realise you are offering them what the law already guarantees. Neither mistake is fatal on its own. Both come from not having drawn the line clearly before making the offer.

There is a planning angle too. Because the statutory layer is fixed cost, it belongs in the budget before the discretionary layer. You cannot sensibly decide how much room you have for perks until you know what the mandatory floor costs in that specific country.

Getting the floor right from the first hire

The reliable approach is unglamorous. Establish the statutory baseline for the country before the offer, cost it fully, then design the perk layer on top with a clear view of what you are actually adding versus what you are legally obliged to give.

For a single market you can build that knowledge in-house. Across several, the tracking gets heavy, because each country's floor shifts and the rules change over time. Hiring compliantly through an EOR hands the statutory side to a partner that already administers it correctly in-country. Boundless, a Payoneer company, becomes the legal employer through its licensed local entity and structures contracts, leave, and mandatory contributions to local law for the team you engage, so the required floor is met without you having to reverse-engineer it market by market. The perks then stay yours to design, which is where they belong.

The distinction matters just as much for contractors, though it runs the other way. Genuine contractors engaged through an Agent of Record are not owed statutory employee benefits, because they are not employees, and offering them employment-style entitlements can blur the classification you are relying on. So the first question is always which relationship you are in, and only then what the floor looks like.

Get the two layers straight and the whole thing calms down. You know what you owe, you know what you are choosing to add, and the benefits package stops being a source of quiet legal risk and goes back to being a tool for hiring well.