How to price Italian offboarding into your EOR plan

Most EOR plans price Italy as a monthly payroll run. Offboarding gets a line item, or nothing at all. Then the first Italian exit arrives and the team finds that the last month is the most work-intensive month of the whole employment.

The cause is TFR and the final pay calculation. This article explains why they add workload, where the effort sits, and how to price it so the plan holds.

What TFR is, in operational terms  

TFR is the Italian end-of-service entitlement. It builds up through the employment. It is paid when the employment ends, whatever the reason for the exit.

For a platform, the point is not the legal theory. The point is that TFR is a liability that exists from the first payslip. It has to be tracked, revalued and reconciled. At exit it becomes a payment with its own tax treatment.

If your system treats TFR as a note on the payslip, offboarding will be manual. If it treats TFR as a ledger per employee, offboarding is a report and a check.

Where the workload sits  

The final pay is a bundle of separate calculations. Each one needs input from a different source.

• Last salary. Prorated to the exit date. The proration rule depends on the applicable national contract.
• Unused leave and permits. The balance must be correct. Balances kept in a spreadsheet by the client are rarely correct.
• Notice. Worked or paid in lieu. The length depends on the contract, the role and the seniority. The choice changes cash flow and the exit date.
• Additional monthly payments. Many contracts pay extra monthly instalments through the year. At exit, the unpaid share accrues and must be settled.
• TFR. The accumulated amount, revalued, with the right tax treatment.
• Conguaglio. The year-end tax adjustment is brought forward to the exit month.

None of these is hard alone. Together they require the employment history, the contract terms and the leave ledger to agree. When they do not agree, someone reconciles by hand.

The hidden cost is the data, not the calculation  

A payroll engine can compute the final pay in seconds. The time goes into the inputs.

Typical gaps we see in handovers:

• The contract level changed during the employment and the history was not updated.
• Leave balances differ between the client’s records and the payroll records.
• The exit date is agreed late, so the notice period is disputed.
• A TFR choice made at hiring is not recorded where payroll can read it.

Each gap creates a query to the client. Each query adds days. Meanwhile the employee waits for money they are owed, and your support team takes the complaint.

Why a flat offboarding fee fails  

A flat fee assumes every exit costs the same. It does not.

A short employment with no leave balance and a clean contract history is quick. A long employment with several contract changes, a leave backlog and a negotiated exit is slow. A flat fee set for the average case loses margin on the hard exits and overcharges the easy ones. Clients notice the second and you absorb the first.

A pricing structure that holds  

Separate three things.

1. A base offboarding fee. It covers the standard final pay run, the TFR payment and the documents. Set it for a clean exit with complete data.

2. Complexity tiers. Define them by observable inputs, not by effort after the fact. Examples: contract level changes in the history, leave balance disputes, notice paid in lieu, a negotiated exit agreement. Each trigger moves the case to a higher tier. The client can see the rule before the exit happens.

3. A data-quality condition. State what the client must supply and by when. If the inputs arrive late or incomplete, the case moves up a tier. This is the cheapest lever you have, because it rewards the behaviour that removes the cost.

Also decide who carries the TFR liability view. If you show it to the client during the employment, the exit amount is no surprise and the budget conversation happens early. If you reveal it at exit, expect a dispute about the number.

Build the cost side before the price side  

Before you set a fee, time a handful of real exits. Record where the hours went. In most cases the split is mostly data chasing and review, with little time on the calculation itself. That tells you where automation pays and where a tier is the honest answer.

Then check three controls:

• TFR is held as a per-employee ledger from the first payslip.
• Leave balances are reconciled on a schedule, not at exit.
• Contract level and national contract are stored as dated history.

If these are in place, the base fee can be low and the tiers rarely trigger. If they are not, price for the manual case and fix the process before you cut the fee.

What to ask your Italian delivery partner  

Ask how they hold TFR, how they reconcile leave, and what they need from you at notice stage. Ask for the exit checklist and the list of fields they require. A partner who answers in fields and timelines is one you can price against. A partner who answers in reassurance is one you will end up covering.

Partnership teams that want to see the fields, timing and ownership we use for Italian exits can request the data-exchange specification.