Skip to main content
iVentureTeam
Odoo HR & Payroll

Odoo Payroll Italy: Busta Paga Options, Limits and When to Outsource

Odoo payroll in Italy: why Odoo 20 has no Italian payroll localization, what busta paga modules cover, and when to keep a consulente del lavoro.

Siddharth JambukiyaSiddharth JambukiyaOdoo Techno-Functional Consultant
November 14, 202611 min read4 views
Odoo Payroll Italy: Busta Paga Options, Limits and When to Outsource cover

Most guides on Odoo payroll assume your country has a localization. Italy does not, and that changes the whole plan. Our Odoo consulting services start with that gap, so you choose a payroll route before you configure anything.

Related service: Odoo implementation services — HR, payroll and attendance configured for your local rules.

This guide is for HR managers, CFOs and owners of Italian firms, or groups with Italian staff, on Odoo. For the general setup steps, see our Odoo payroll setup guide for Odoo 19 and 20.

Does Odoo have an Italian payroll localization?

No, Odoo does not ship an Italian payroll localization in Odoo 19 or Odoo 20. The Payroll app works in Italy, but only as a generic rules engine with no Italian salary rules.

The Odoo payroll localizations list for Odoo 20 shows 25 countries. Eight are in Europe: Belgium, Lithuania, Luxembourg, the Netherlands, Poland, Romania, Slovakia and Switzerland. Italy is not on it.

That matters because a localization ships the salary structures, contribution rates, tax rules and statutory reports. Without one, every rule on an Italian payslip must come from a module, from your own salary rules, or from an outside payroll engine.

Users in other unsupported countries hit the same wall. On the Odoo forum, one user asked whether they can add a payroll localization for a country missing from the list, and the replies only pointed to generic payroll tutorials.

What does the Odoo Italian localization cover?

The Odoo Italian localization is an accounting and tax package, not a payroll package. It is mature for invoicing and VAT, which is why many buyers assume payroll is included.

The Odoo Italy fiscal localization documentation lists eight modules installed with the Italian localization. The table shows what each area does and what it means for payroll.

AreaWhat Odoo covers in ItalyPayroll impact
Accounting (l10n_it)Italian chart of accounts and taxesPayroll journals post here
E-invoicing (l10n_it_edi)FatturaPA XML sent through SdINone
Declaration of IntentDichiarazione di Intento for exportersNone
Point of SaleItalian fiscal printer linkNone
Accounting reportsItalian VAT and tax reportsNo payroll filings
Ri.Ba. and DDTBank receipts and transport documentsNone
PayrollNot coveredNeeds a module or external provider

The accounting side is ready for payroll entries, but nothing standard computes INPS, IRPEF or TFR. For more on e-invoice formats across Europe, see our guide to Odoo e-invoice formats compared.

Why is Italy payroll hard to run inside any ERP?

Italy payroll is hard because several rule sources overlap and change every year, not because the math is complex. Each one must be correct on every payslip.

  • Collective agreements: each CCNL sets minimum pay, seniority steps, extra monthly payments and overtime rates. A CNEL report found 626 agreements, 72.4% of those filed, cover only a tiny share of workers.
  • Contributions: INPS and INAIL rates depend on sector, job grade, company size and temporary reliefs.
  • Income tax: IRPEF uses three brackets in 2026, 23%, 33% and 43%, plus deductions and regional and municipal surcharges.
  • TFR: severance accrues monthly and is revalued each year.
  • Filings: withholdings are paid by F24 by the 16th of the next month, and UniEmens is due by the last day of the next month.
  • Year end: the Certificazione Unica goes to employees and the tax agency by 16 March.

Every budget law can move brackets, deductions and the tax wedge. That is why Italian payroll software behaves more like a service than a product: someone must update it for you.

Odoo busta paga modules: what l10n_it_busta_paga and others cover

Third-party Odoo busta paga modules now exist for Odoo 18, 19 and 20, and they claim most of the statutory calculations. Treat their claims as a starting point to test, not as proof of compliance.

The table compares the options we found on the Odoo Apps Store and in the OCA Italian repository.

OptionOdoo editionListed scopePrice shown
Italy Payroll Busta Paga (l10n_it_busta_paga)Community, versions 18 to 20INPS, IRPEF, surcharges, TFR, payslip, LUL export, F24 summaryUS$229.43
Italy Payroll for Enterprise (l10n_italy_hr_payroll)Enterprise, versions 19 and 20Adds UniEmens XML, CU file, sickness and maternityUS$750.00
OCA l10n_it_hr_payroll_documentCommunity, version 16Sends payslips, matches staff by fiscal codeFree (AGPL-3)

The l10n_it_busta_paga listing says it computes the 9.19% employee INPS share, IRPEF at 23%, 33% and 43%, and the EUR 1,200 trattamento integrativo. It says every rate is editable, so you can update figures without code changes.

The Enterprise app goes further. Its listing claims official MEF surcharge tables for all 21 regions and about 7,900 municipalities, plus a UniEmens XML validated against the INPS schema.

What none of them can promise is your CCNL. Both listings handle national rules, but contract-specific minimums, steps and overtime rates are still yours to configure and maintain.

Which route fits: build, buy a module or outsource?

Odoo payroll Italy: Which payroll route fits your company?

Most Italian companies on Odoo should outsource payroll calculation and keep HR data in Odoo; a module fits only firms with simple contracts and in-house payroll skills. Building your own rules rarely pays off.

RouteBest forMain riskWho updates the rules
Build salary rules yourselfVery few staff, one CCNLYou own every legal changeYour team
Third-party busta paga moduleOne or two CCNLs, in-house payroll clerkVendor stops updating; upgrade costModule vendor plus you
Outsource to a consulente del lavoroMost SMEs, several CCNLsManual data handoffThe consultant
External payroll engine plus connectorMid-size firms wanting automationConnector upkeep at each Odoo versionThe payroll provider

Ask one question first: who is liable if a payslip is wrong? In practice, Italian employers hand that work to a consultant or a payroll bureau, and a generic rules engine does not change that.

Our post on Odoo localization gaps shows how to score gaps like this one before you sign a project.

What should stay in Odoo when Italy payroll is outsourced?

Keep every input that feeds the payslip in Odoo, so your consultant receives clean data once a month. This is where Odoo HR saves the most time in Italy.

  • Employees: codice fiscale, IBAN, job grade, CCNL and level, hire date and contract type.
  • Contracts: gross pay, working schedule, part-time percentage and contract versions over time.
  • Attendance: check-ins from a kiosk, badge or the mobile app, with extra hours approved by managers.
  • Time off: ferie, permessi, sickness and other leave, with approvals and balances.
  • Expenses: reimbursements that end up on the payslip.
  • Documents: payslip PDFs returned by the consultant, stored on each employee record.

Payroll files hold sensitive personal data, so restrict access by role. Our Odoo GDPR compliance checklist covers access rights and data processing terms.

How do you connect Odoo to your consulente del lavoro each month?

Agree a fixed monthly cycle: Odoo closes the inputs, the consultant computes pay, and Odoo receives payslips and the cost entry. Odoo 20 makes the first step easier.

Our Odoo 20 payroll release notes show that the separate provider export tools were replaced by one Export Time Entries action on employees. It exports a month of time entries for the selected staff in one common file.

  1. Lock the month: approve all attendance, overtime and leave before your cut-off date.
  2. Export time entries: in Odoo 20, select employees, then Actions, Export Time Entries, and pick the month.
  3. Add changes: send hires, leavers, pay changes and expense claims with the export.
  4. Consultant computes: the consultant runs the busta paga, F24, UniEmens and Libro Unico del Lavoro entries.
  5. Load payslips: attach the PDFs to each employee record, or publish them on the employee portal.
  6. Post the cost: import the consultant's salary summary as a journal entry with wages, contributions, withholdings and TFR.
  7. Pay staff: create the salary payments in Odoo and reconcile them against the bank.

For automated links between Odoo and a payroll provider, our Odoo integration services build and maintain the connector.

How do you test an Odoo payroll module for Italy?

Test any Italian payroll module with a parallel run against your current payslips before you trust it. Compare net pay and every statutory line, not just totals.

  1. Pick a sample: full-time, part-time, a new hire, a leaver, someone on sick leave and one high earner.
  2. Run two months in parallel: compute payslips in Odoo next to your current payroll.
  3. Compare line by line: gross pay, INPS, IRPEF, surcharges, TFR and net pay.
  4. Check the outputs: F24 summary, LUL export and UniEmens file, if the module claims them.
  5. Test December: run the year-end conguaglio on a test database before real year end.
  6. Ask about upgrades: confirm the vendor's update cycle for each budget law and each Odoo version.

If the gaps are small and the vendor updates quickly, a module can work. If you find gaps on CCNL rules, keep the consultant and use Odoo for inputs.

What does Odoo payroll for Italy cost?

Odoo payroll cost in Italy has three parts: Odoo licenses, any third-party module, and implementation or consultant fees. The licenses are the smallest part for most firms.

Under Odoo's subscription terms, an active employee record not linked to an active user counts as a Light User. The Odoo pricing page lists Light Users at EUR 7.90 per employee in Europe, so staff who never log in cost less than full users.

The two module listings show US$229.43 and US$750.00 as one-time Apps Store prices. Budget for testing and re-testing them at each Odoo upgrade.

Our published Odoo implementation cost ranges run from $3k to $9k for small projects, $9k to $27k for mid-size and $27k to $150k+ for large ones. Treat them as indicative.

For a number on your own scope, try the Odoo project estimate tool.

Odoo payroll Italy by industry

Your sector's CCNL and shift patterns decide the payroll route more than headcount does. The table shows common Italian patterns.

IndustryPain or cost driverOdoo approachHow iVentureTeam helps
Manufacturing (metalworking)Shifts, night work, overtime ratesKiosk attendance, extra hours approvalMap shift data to the consultant's pay codes
Retail and hospitalityPart-time staff, Sunday and holiday workVariable schedules, time off typesSet rotas and clean monthly exports
ConstructionSite crews, Cassa Edile rulesAttendance by site or projectTag hours by site for the consultant
Professional servicesTimesheets, travel, expensesTimesheets and Expenses in one placeLink time to projects and reimbursements
Foreign groups with Italian staffFew staff, local rules unknown at HQOdoo HR at group levelConnect Odoo to a local payroll provider

How iVentureTeam helps with Odoo payroll in Italy

Odoo HR in Italy? Price it first

iVentureTeam helps Italian companies pick the right payroll route and makes Odoo the clean source of HR data behind it. We have delivered 150+ ERP projects across 35+ countries with 40+ Odoo specialists, led by a consultant with 13+ years in Odoo.

  • Route check: compare a module, your own rules and an outsourced consultant against your CCNLs and headcount.
  • HR setup: employees, contracts, schedules, attendance and time off configured for Italian leave types.
  • Module testing: parallel runs of any busta paga module against your current payslips.
  • Consultant handoff: monthly exports, payslip storage and journal entries for payroll cost.
  • Connectors: links to external payroll engines through our Odoo consulting services and integration team.

Time data to payroll case study: Enabl Health

Enabl Health is not an Italian company, but it solved the same upstream problem: turning raw time data into correctly rated pay and billing lines. That is the step Italian payroll depends on.

The Australian health-tech firm tracked hours with manual start and stop times, and rates differed for weekdays, weekends and holidays. That mirrors the Sunday, holiday and overtime rates in many Italian CCNLs.

We cleaned data across sales, timesheets, invoices, payslips and users. We then automated timesheet classification by day type, added start and stop timers, and extended Odoo's Timesheet, Payroll and Portal layers.

The project ran on Odoo.sh with staging and production branches over 10 weeks plus ongoing support. Read the Enabl Health timesheet and billing case study.

The bottom line on Odoo payroll for Italy

Use Odoo for Italian HR, attendance and leave, and keep payroll calculation with a consulente del lavoro unless a tested module covers your CCNL. That split is the safest route today.

Odoo 20 adds no Italian payroll localization, but its single time entry export makes the monthly handoff cleaner. Test any busta paga module with a parallel run, and plan who updates the rules each year.

Ready to plan your Italian payroll route in Odoo?

Book an Italy payroll review

Get a clear answer on module, consultant or connector before you configure anything. Talk to us about Odoo payroll in Italy, call +91-90235-15208, or email business@iventureteam.com.

Frequently Asked Questions

Does Odoo support Italian payroll?

+

Not natively. Odoo 19 and Odoo 20 have no Italian payroll localization. The Payroll app works as a generic rules engine, so Italian payslips need a third-party module, your own salary rules, or an external payroll provider.

What is l10n_it_busta_paga?

+

It is a third-party Odoo Apps Store module for Odoo 18, 19 and 20 Community. Its listing claims INPS, IRPEF, surcharges, TFR, payslips, a Libro Unico export and an F24 summary. Test it in parallel before going live.

Does the Odoo Italian localization include payroll?

+

No. The Odoo Italian localization covers accounting, VAT, FatturaPA e-invoicing through SdI, the Declaration of Intent, the fiscal printer, Ri.Ba. and DDT. Payroll is outside its scope.

Can Odoo replace my consulente del lavoro?

+

For most Italian companies, no. The consultant tracks CCNL changes, computes pay and files F24, UniEmens and the CU. Odoo works best as the clean source of employee, attendance and leave data they need.

How do I send attendance data from Odoo to my payroll provider?

+

In Odoo 20, select employees and use Actions, Export Time Entries to export one month in a common file. Add hires, leavers and pay changes, then send it to your consultant or payroll engine.

Which countries in Europe have Odoo payroll localizations?

+

The Odoo 20 list includes Belgium, Lithuania, Luxembourg, the Netherlands, Poland, Romania, Slovakia and Switzerland. Italy, France, Germany and Spain are not on the list.

How much does Odoo cost for Italian employees who do not log in?

+

Under Odoo's subscription terms, an active employee record not linked to an active user counts as a Light User, listed at EUR 7.90 per employee in Europe. Full users cost more.

Can Odoo post payroll costs if payroll is outsourced?

+

Yes. Import the consultant's monthly salary summary as a journal entry for wages, contributions, withholdings and TFR, then create salary payments and reconcile them against the bank in Odoo Accounting.

Free payroll setup review

Setting up payroll in Odoo?

Tell us your headcount and pay rules. We set up salary rules, statutory files and leave in Odoo, and show what needs a custom module.

Free, with no obligation. A senior consultant replies within 12 business hours.

We use cookies to improve your experience

Essential cookies make the site work, and we use analytics to improve it. Choose “Only necessary” to turn analytics off. See our cookie policy.