Year-End Readiness Checklist for Italian ICP Operations

Year-end in Italy is not a normal payroll cycle. The extra monthly salary, final adjustments and new-year recalculations all land close together. Platforms that treat it as routine tend to find the gaps late.

This checklist is for partnership, operations and payroll managers who rely on an Italian ICP to run local payroll for their workers. It covers what to confirm before the year closes and what to expect once the new year starts.

Agree the calendar early  

Ask your Italian partner for a written year-end calendar. It should show the cut-off for employee data changes, the date payroll inputs are frozen, the payment run and the point where reports are released to you.

Your own systems also have cut-offs. Match them to the partner’s calendar. If your platform sends changes after the freeze, they will fall into the next cycle. Make sure your support teams know this, so they can tell customers and workers what to expect.

Confirm who owns each input  

Most year-end errors come from unclear ownership. Write down who supplies each of these and in what format:

• New hires, leavers and contract changes
• Salary changes and bonuses
• Unpaid leave, sickness and other absences
• Benefits and expense reimbursements
• Tax and social security data that changed during the year

If your platform is the source of truth for some of these, say so. If the ICP is, say that too. A field with two owners will produce two different values.

Check the extra monthly salary  

Italian employees usually receive an additional monthly salary at the end of the year, commonly called the tredicesima. Some contracts and collective agreements add further extra payments. Your platform should not assume one pattern fits every worker.

Before the payment run, confirm these points with your partner:

• Which workers are entitled to it under their contract and applicable collective agreement
• How it is calculated for part-year employees, part-time staff and people with unpaid absences
• How it appears on the payslip and in your reports
• What it adds to employer cost, so your invoices reflect the true figure

Finance teams are often surprised here. The payment affects employer contributions as well as net pay. Show your customers the expected cost before the run, not after it.

Review the year-end payroll run  

The final payroll of the year carries more weight than usual. Ask for a pre-run preview and review it against your own records.

Look for headcount differences, unexpected zero payments, workers missing from the run and large swings in cost compared with the previous month. Check that leavers are handled correctly, including any final entitlements that must be paid out.

Agree a clear sign-off step. Someone on your side should approve the preview, and the partner should record that approval. If a problem appears after payment, you will want a trail showing what was reviewed and when.

Plan for recalculations after year-end  

The new year often brings adjustments. Some come from late information about the old year. Others come from rule changes that apply from the start of the new period, such as updated contribution parameters or tax settings.

Ask your partner how they handle three cases:

• A late change that affects a payslip already issued
• A correction that crosses the year boundary
• Updated parameters applied to the first payroll of the new year

For each case, find out whether the correction is paid in the next run, issued as a separate payment or handled through a later adjustment. Then check that your platform can display it clearly. Workers who see an unexplained difference will contact support, and your teams need a ready answer.

Align reporting and data exchange  

Year-end creates a surge in reports, certificates and data requests. Confirm in advance which documents your partner will issue, who receives them and how they reach the worker.

Also test your data exchange. If you use an API or file transfer, run a trial with realistic year-end data before the busy period. Check field mappings for the extra payment, adjustments and corrections. A mapping that works for a normal month can fail on a retroactive item.

Prepare your support teams  

Workers ask the same questions every year. Why is the payment larger than usual? Why is a deduction different? When will the certificate arrive? Prepare short, accurate answers with your partner and keep them in your knowledge base.

Set an escalation path with named contacts on both sides, including response expectations over the holiday period. Italian offices often run with reduced staff at year-end, so do not assume normal turnaround.

A short summary list  

• Get the partner’s year-end calendar in writing
• Assign an owner to every payroll input
• Confirm entitlement and calculation rules for the extra monthly salary
• Review a payroll preview and record the sign-off
• Agree how late and cross-year corrections are handled
• Test data exchange with realistic year-end items
• Brief support teams and name escalation contacts

None of this is complicated. It only needs to be done before the pressure starts. Platforms that agree the process early spend the busy weeks resolving real exceptions rather than basic misunderstandings.

Partnership teams are invited to request the data-exchange specification.