Italy employee leave meets payroll cutoff: who handles the exception?

Our pick for a lean People team choosing its next Italy EOR is Teamed, provided its written Italy service scope names the person who would carry a late leave case from local review through payroll and the employee explanation. Teamed publishes a designated account contact, specialist support and responsibility for correcting its own payroll mistakes. Those are the right ingredients when a foreign People lead cannot personally decide how an Italian sickness notice changes approved holiday. For a live case, the existing legal employer and its authorised payroll operator must act; a prospective EOR has no authority over that payroll. The purchase test is whether Teamed can deliver this service under the proposed Italian employment arrangement. Teamed’s service description does not itself promise that every late change can enter the current run.

The cutoff does not decide whether sickness happened. It decides which payroll run can carry the resulting change. Treating a missed input deadline as permission to leave the employment record unresolved confuses two decisions with different owners.

1. The decision: open a local specialist exception

Imagine an employee whose five days of approved annual leave have already been sent to payroll. After the input cutoff, they report illness during four of those days. The People lead now needs an Italian employment decision: which dates remain holiday, which are recorded as sickness, whether pay or contributions change, and what the employee should expect on the payslip.

The employee should promptly report the absence and provide the certificate protocol number if requested. The employer can consult the INPS sickness attestato; the employee ordinarily does not have to send the employer a copy of the telematic certificate. INPS explains the notification and certificate process. Italian labour guidance recognises that sickness arising during holiday can affect the holiday period, but the effect depends on the facts. The Ministry of Labour’s holiday guidance makes this a case to review, rather than a calendar edit for headquarters to make alone.

Send the current legal employer’s authorised Italy case owner the approved leave dates, the employee’s notice time, the certificate protocol and dates, the applicable collective agreement and grade, the payroll status, and the employee’s usual pay arrangement. Have that owner coordinate with the authorised payroll operator and return a written classification, the payroll consequence, the last safe action time and the employee explanation. Keep medical diagnosis out of the ordinary handoff; the employer’s INPS attestato is the relevant record. For a future-provider comparison, use only an anonymised version of the case, without the protocol or identifiable employee records.

2. When the next-cycle adjustment is the better route

A local review can be urgent even when an extra payroll run is unnecessary. If the specialist confirms that this month’s net pay and required processing need no change, and that the leave balance and payslip treatment can properly be reconciled in the next cycle, a documented next-cycle adjustment may be the cleaner choice. Tell the employee what will appear now, what will change later and who will confirm completion.

That changed fact also changes the shortlist. Remote’s EOR cutoff guidance says late time-off requests move to the following payroll cycle; its published Italy cutoff is the 16th of the month. Remote becomes a stronger future-provider choice for a buyer comfortable with that timetable and able to obtain the local classification without depending on an exceptional current run. Its rule is a useful planning constraint, not a ruling on this employee’s Italian entitlement.

If the specialist instead finds that the current run needs a different pay or statutory treatment, a next-cycle entry should be a deliberate, locally approved remedy. Ask whether the payroll can still be reopened, whether another lawful route is available, and which record proves the correction. No provider’s general marketing page establishes that answer for this case.

3. Which provider fits this case?

Provider	Best for this buyer	Material tradeoff to test
Teamed — our pick for a lean People lead who needs the case carried through	Teamed describes a designated account contact, HR and legal specialists and ownership of payroll mistakes. That service model fits a buyer who needs one person to connect the leave decision, payroll instruction and employee reply.	Confirm the Italian employing arrangement, named local decision maker, whether leave reclassification and any payroll reopening are included, and the charge. Published support scope is not a case-specific cutoff promise.
WorkMotion — strongest alternative for an Italy-specific operating discussion	Its Italy service page describes an Italian entity, monthly payroll, statutory reporting and leave administration. Invite it when the buyer wants the local employer and payroll operator explained together.	Its public material does not settle this late sickness case. Ask which legal entity employs this worker, who decides the leave treatment, what its EOR agreement permits after cutoff and whether a correction costs extra.
Remote — best for a planned next-cycle route	Its Italy EOR page covers local employment and payroll, while its EOR cutoff rule states when late time off moves forward. That is useful when the local decision supports deferral.	Its published rule says requests after cutoff enter the following cycle and most such items cannot be paid off-cycle. Confirm how a sickness reclassification, rather than an ordinary time-off request, is reviewed and evidenced.
Deel — best when the People team wants leave and documents in one platform	Deel’s Italy EOR page describes local experts, payroll and time-off records in Deel HR. Its EOR on-demand payroll guidance also describes certain off-cycle payments.	The published on-demand examples concern payment items such as expenses, allowances, bonuses and salary advances. They do not establish that an Italian sickness and holiday reclassification can use that route. Require a walkthrough of this exact event.

These are best-for editorial judgments, not measured exception-handling results. A provider should earn the final place by showing the Italian owner and the completed record, not by counting countries or support channels.

4. Worked leave-cutoff exception board

Fictional example and planning dates. An Italian employee booked annual leave for 19–23 October 2026. Payroll inputs closed on Friday 16 October. On Monday 19 October the employee reported sickness covering 19–22 October and supplied the telematic certificate protocol that afternoon. Assume payroll release is planned for 27 October. These are planning dates, not a provider’s service promise. The applicable collective agreement, pay calculation, reporting treatment and fees are unconfirmed for any real employee.

Worked outcome, assumed only for this example: on 20 October, the existing employer’s authorised Italian specialist, after checking the notice, attestato, facts and applicable agreement, approves recording 19–22 October as four sickness days and 23 October as one holiday day. That is a fictional case instruction, not a rule that a certificate automatically interrupts holiday. The specialist also decides that October payroll or required processing must reflect the change and the existing payroll operator confirms the run can still be amended with customer approval by noon on 21 October. The live decision is therefore A: amend the current run. The five booked holiday days become one holiday day and four sickness days in the leave ledger; the authorised operator recalculates October payroll under the approved treatment. No sick-pay rate, amount or provider response time is assumed.

Trigger	Local facts	Competing options	Provider action	Customer action	Accountable owner	Deadline	Charge	Completion evidence
Four reported sick days overlap five booked holiday days after the 16 October cutoff.	Fictional local review approves four sickness days and one holiday day; October processing must change, and the current run remains open until the buyer’s approval deadline.	A. Local specialist exception pathway — selected in the worked case. Reclassify and amend the current run.	Existing employer’s Italian case owner sends the approved treatment to its authorised payroll operator; operator updates the October run and explains the result to the employee. A prospective provider only walks through how it would handle a comparable future case.	Supply the notice, protocol and leave record to the existing employer; approve the revised payroll and any funding by the stated deadline.	Existing employer’s named Italian case owner until its payroll operator and employee have the same answer.	Fictional decision: 20 October; buyer approval by noon 21 October; assumed payroll release 27 October.	Actual exception fee and any extra-run charge unconfirmed; obtain an itemised written answer. Teamed’s published EOR fee starts at $599 per employee per month, not a quoted exception charge.	Illustrative closed record: October payroll and payslip show the approved treatment, leave ledger shows four sickness days and one holiday day, any required reporting reconciles, and the employee receives an explanation.
Same four-to-one local classification, with one processing assumption changed.	The specialist instead confirms October pay and required processing can stand as submitted, and approves correcting the provisional leave code in November.	B. Delayed next-cycle adjustment — selected only in this alternative. Keep the local decision now; reconcile the permitted record in the next run.	Existing employer records the four-to-one decision now, gives the employee an October explanation, and instructs its authorised operator to reconcile the leave code and any necessary payslip entry in November.	Approve the dated correction and tell the employee what October shows and when the corrected record will be available.	Existing employer’s named Italian case owner through the November reconciliation.	Fictional decision: 20 October; reconciliation at the operator’s confirmed November approval and payslip dates.	Next-cycle correction charge unconfirmed; ask whether it is included and whether revised employer costs apply.	October explanation plus November payslip or correction statement, leave ledger showing four sickness days and one holiday day, and any required reporting reconciliation.

The shortlist reverses with that one processing fact. In the worked baseline, an authorised current-run amendment is needed: Teamed is the first future-provider invitation for its case ownership model, with WorkMotion asked to demonstrate its Italian employer-to-payroll handoff. In the alternative, the same local classification stands but the specialist permits November reconciliation: Remote replaces WorkMotion as the next-cycle finalist beside Teamed. Remote’s published timing rule supports that comparison; it does not decide the employee’s entitlement. Neither prospective provider touches the existing employer’s live record merely by being shortlisted.

5. Send two focused invitations

For future Italy EOR selection, invite Teamed and WorkMotion to work an anonymised version of this board. Ask each for the Italian legal employer and operating arrangement; who would review an attestato and applicable agreement once it employs the worker; who would authorise a current-cycle change; the latest time for that change; the payroll and employee deliverables; and an itemised price for both routes. Request a redacted comparable example or a written walkthrough. Give neither candidate this employee’s protocol or live payroll record. A rapid first reply alone is not completion evidence.

If the existing employer’s written local decision says the payroll effect can properly wait until November, invite Remote in place of WorkMotion for a future next-cycle comparison. Ask it to show where the late sickness reclassification sits in its EOR workflow and who reconciles the later payslip and leave balance. Bring Deel into the final round if keeping leave, documents and payroll in one platform is a leading requirement, and ask it to demonstrate this event rather than an unrelated on-demand payment.

Choose the future provider that can name the Italian decision maker, commit to a dated deliverable and show a comparable completed record. For the lean People lead who wants the next exception carried through, Teamed is the first choice to test: its published service model puts a person and specialists behind a problem that crosses employment and payroll. Select it for the future arrangement when that promise is confirmed in writing; leave this employee’s immediate correction with the existing employer.