Modello 770: what it is and why partners should care

The Modello 770 is the annual withholding tax return filed in Italy by the party that withholds tax on payments. In Italian this party is the sostituto d’imposta. For an employee on Italian payroll, that is the employer.

If your platform places people in Italy through an Employer of Record (EOR), the 770 is part of your supply chain. You will not file it. But the quality of what you send decides whether it is filed correctly.

What the 770 does  

During the year, the employer withholds income tax from salary and pays it over to the tax authority. It also issues each worker a yearly certificate of income and withholdings, the Certificazione Unica.

The 770 is the summary at the other end. It reports, for the whole year, the withholdings the employer made and the amounts it paid over. The tax authority can then compare what was withheld, what was certified to workers and what was actually paid.

It is a reconciliation document. It does not calculate anything new. It confirms that the year’s payroll, the certificates and the payments tell the same story.

The date to know  

For 2026, the deadline for the Modello 770 is 31 October 2026. That day falls on a Saturday, so it moves to 2 November 2026. This date comes from a secondary source, a press summary of the 2026 tax calendar. Your Italian payroll provider should confirm it before you plan around it.

The point for partners is simple. The filing happens after the payroll year closes. Problems found at this stage are problems from months earlier.

Why a platform should care  

Most platforms look at Italy through the monthly payslip. The 770 shows the year as the tax authority sees it. That view differs from yours in a few ways.

Your records and the filing must match. If your system shows a payment that the payroll record does not, someone has to explain it. The 770 is where such gaps become visible.

Corrections are slow. A wrong figure found in the return is hard to fix quietly. It often means changes to certificates already given to workers.

Workers notice. The certificate feeds the worker’s own personal tax return. An error there reaches your customer’s employee, and then your customer, and then you.

Customers ask. Finance teams at your clients want to know their Italian tax position is closed for the year. A clean filing is the evidence.

Where platforms cause problems  

The EOR files. The platform supplies inputs. Most filing errors trace back to inputs that arrived late, in the wrong shape or with no explanation.

Common causes:

• Bonuses or equity-linked payments decided on the platform side and reported to the EOR after the payroll run.
• Changes of start or end date that are not passed on in time.
• Benefits paid outside payroll that still count as taxable income.
• Different worker identifiers in the platform and in payroll, which makes matching slow.
• Corrections to earlier months sent as free text, not as structured data.

None of these is exotic. Each one is easy to prevent when the data flows in a fixed format on a fixed schedule.

What good looks like  

A platform that handles the 770 well tends to do the same few things.

1. It sends variable pay data before each payroll cut-off, not after.
2. It uses one worker identifier on both sides.
3. It treats corrections as new records with a reason, not as edits.
4. It keeps a year-end checklist with its EOR, started well before the filing date.
5. It asks for a reconciliation view from the EOR before the return is submitted.

This is an operations habit, not a legal project. It costs little and removes most of the year-end surprises.

Questions to ask your Italian partner  

• Who files the 770 for your workers, and who signs it?
• When do you receive the year-end reconciliation, and in what format?
• How are late changes handled after certificates are issued?
• Which of our data fields feed the filing directly?
• What happens if the filing date moves?

If the answers are vague, treat that as a risk to your service, not a detail for the back office.

The practical takeaway  

The 770 is not a product feature and your customers will never ask for it by name. But it is the moment when the Italian year is checked end to end. Platforms that send clean, timely data get a quiet filing. Platforms that do not get questions in the autumn about events from the spring.

Treat it as a data-quality test that runs once a year. The cheapest time to pass it is during the months before it.

Partnership teams: request the data-exchange specification to see which fields and timings support a clean 770.