Per-employee fee vs percentage of payroll for Italy: what it does to platform margins

Every global EOR and payroll platform has to decide how to price an Italian partner. The choice is usually between a flat fee per employee and a percentage of payroll. Both work. They protect different things.

This article looks at the choice from the platform side. The question is what each model does to your margin, your forecasting and your relationship with the local partner.

Why Italy makes the choice harder  

Italian payroll is not a single number. Cost depends on the collective agreement that applies, the employee’s level, the mix of fixed and variable pay, and a set of contributions and allowances that differ by case. Two employees with the same gross salary can produce different workloads and different totals.

That matters for pricing. A percentage tracks the size of the payroll. A flat fee tracks the number of people. Neither tracks the effort of running the case.

Flat fee per employee  

Pros for the platform

• Easy to quote. Your sales team can put a single line in a proposal and the customer understands it.
• Predictable cost of goods. If you pay the partner per head, your cost and your price move together.
• Stable margin per seat. A large raise for one employee does not change what you pay or what you charge.
• Simple invoicing and reconciliation. Headcount is easier to audit than payroll totals.

Cons for the platform

• Weak link to complexity. A simple case and a hard case cost the same. If the partner treats them equally, you carry the risk of unusual cases.
• Pressure on high-salary roles. Senior hires pay the same fee as junior ones, so you leave revenue on the table. Customers with senior teams will also compare you with cheaper options.
• Exposure to mix shifts. If your Italian base moves toward lower-cost roles, margin per seat can look fine while total revenue stays flat.
• Hard to price extras. Visas, relocation and benefits changes tend to end up as add-ons, which makes the quote less clean.

Percentage of payroll  

Pros for the platform

• Revenue grows with the customer. Raises, bonuses and promotions lift your income without a new conversation.
• Better fit for senior and variable pay. Higher earners usually bring more complexity, and the fee follows.
• Easy to bundle. One rate can cover a range of services, which keeps the proposal short.
• Natural alignment with large accounts. Big payrolls pay more, which matches the support they ask for.

Cons for the platform

• Margin depends on the partner’s pricing structure. If your partner charges per head and you charge a percentage, your margin swings with salary levels you do not control.
• Forecasting is harder. Payroll totals change with bonuses, end-of-year items and one-off payments. Monthly revenue becomes noisier.
• Customers push back. Buyers see a percentage fee on a large salary as paying more for the same work. Expect discount requests on bigger accounts.
• Reconciliation is heavier. You need clean payroll data to bill correctly, and disputes about the base are common. Is it gross pay, total employer cost, or something narrower? Every definition needs to be written down.

Match the model to the partner agreement  

The most important rule is simple. Your customer price and your partner cost should use the same unit.

If you buy per head and sell per head, margin is stable. If you buy as a percentage and sell as a percentage, margin is stable. Mixing the two creates a margin that moves with the customer’s salary mix. Sometimes that is a deliberate bet. Most of the time it is an accident.

If your market requires a different unit on the sales side, consider a hybrid. A flat base fee per employee covers the fixed work of running a case. A smaller percentage component covers the variable part. This keeps a floor under margin and still lets revenue grow with larger payrolls.

What to check before you choose  

• Define the base for any percentage. Write down which pay elements are included.
• Decide how variable pay, one-off payments and corrections are treated.
• Decide how off-cycle runs and retroactive changes are billed.
• Set rules for minimum fees on very small payrolls.
• Agree how terminations and short-term assignments are priced.
• Make sure your reporting can show margin per employee and margin per payroll euro. You need both views to see where the model leaks.

A practical way to decide  

Look at your existing Italian or similar European base. Group employees by salary band and by case complexity. Then compare cost to serve against revenue under both models.

If most of your base sits in a narrow salary band, a flat fee is usually safer and easier to run. If your base is spread wide, with many senior roles and variable pay, a percentage or a hybrid captures value better.

The data you need is mostly operational: headcount, pay components, case types and support effort. Getting it in a consistent format from your Italian partner is what makes any of these models workable.

Partnership teams that want to see how that data can be exchanged can request the data-exchange specification.