Monthly F24 payment checklist for payroll in Italy

The F24 is the form Italian employers use to pay payroll taxes and social contributions in a single transfer. For a global EOR or payroll platform, it is the step where a correct payslip becomes a compliant payment. If it is late or wrong, the employer faces penalties and the employee’s record is affected.

This checklist sets out what gets paid, by when, and with what evidence. Use it as a control sheet for each payroll cycle.

What gets paid  

The F24 normally groups several lines. Confirm each one against the closed payroll.

• Withholding tax on employee income, taken from the gross pay.
• Regional and municipal surcharges on income tax, where they apply to the employee.
• Social security contributions owed to the national institute, split between the employer share and the employee share.
• Other contributions that depend on the contract and the collective agreement applied.

Each line carries a tax code and a reference period. The code tells the authority what the money is for. The period tells it which month the money covers. A correct amount with the wrong code or period is a common cause of misallocated payments.

By when  

The due date is set by law for each type of payment. Do not hard-code a date from memory. Take it from a verified source and store it with the date you checked it. Calendars shift when a due date falls on a weekend or holiday, so build the date from a rule, not from last year’s spreadsheet.

Work backwards from the due date. Payroll must be closed early enough to leave time for review, funding and submission. Your internal cut-off should sit well before the legal deadline, so that one late input does not push the payment past it.

Pre-payment checklist  

Run these checks before any money moves.

1. Payroll is closed and no further changes are open for the period.
2. Totals on the F24 match the payroll register line by line.
3. Tax codes and reference periods are correct for every line.
4. Employer and employee contribution shares reconcile to the gross pay.
5. Any credits or offsets are documented and approved before they are applied.
6. The paying entity and its tax identifier are correct.
7. Funds are available in the paying account.
8. A second person has reviewed the form.

The second review matters. The person who prepared the form tends to see what they expect to see.

Payment and submission  

F24 forms are submitted through channels the authority accepts, usually online banking or the tax authority’s own services. Submission is not the same as settlement. Check that the payment was accepted and that the debit actually cleared.

If you pay on behalf of a client entity, make sure the entity’s own identifiers are on the form. Paying under the wrong identifier creates a reconciliation problem that can take weeks to untangle.

Evidence to keep  

An auditor, a client or the authority may ask you to prove the payment. Keep these items together for each period.

• The final F24 as submitted.
• The receipt issued by the bank or the authority’s service.
• The bank statement line showing the debit.
• The payroll register the amounts were drawn from.
• A reconciliation note linking the register totals to the form totals.
• The name of the preparer and the reviewer, with the time of each sign-off.
• The source and check date for the due date rule you applied.

Store the evidence under the employer, the period and the payment type. A folder per month with clear names is enough. The test is simple: could someone who was not involved find the proof in a few minutes?

After payment  

Close the loop. Compare the amount paid with the amount due. Record any difference and its cause. If a correction is needed, file it through the proper procedure and keep the new receipt next to the original.

Also feed the result back into payroll. Employee records should show that contributions for the period were paid. A gap between payroll status and payment status is an early sign of a process fault.

Common failure points  

• Wrong tax code or reference period on an otherwise correct amount.
• Payroll changed after the form was prepared.
• Due date taken from an outdated calendar.
• Credits applied without documentation.
• Receipt saved in a personal inbox instead of the shared record.
• Payment made under the wrong entity.

Most of these are process faults, not knowledge faults. They are fixed by a fixed sequence, a second reviewer and a shared evidence folder.

For platform operations teams  

If your platform runs payroll across countries, treat the F24 as a defined event with inputs, an owner, a due date and an evidence pack. Expose its status to your own customers. They want to know that the payment was made, not only that the payslip was issued.

Partnership teams that want to connect payment status and evidence to their own systems can request the data-exchange specification.