ERP Implementation Consultant, Italy

What goes wrong in Italian ERP projects

Italian implementations tend to run into the same set of problems, and most of them are visible well before go-live if someone on the client side is looking:

• The e-invoicing channel treated as a technical detail. The connector is configured late, recipient codes in the customer master are incomplete, and the first rejected invoices appear on go-live day.
• Knowledge held by one person. In owner-led firms, pricing rules, agent agreements and credit decisions live in someone's head. If they are not captured in design sessions, the system is configured on guesses.
• Customizations carried over by habit. Reports and screens built for the old package get recreated without asking whether they are still needed.
• Advisors brought in too late. The commercialista sees the new registers only when the first VAT settlement is due, and the labor consultant learns about the new journal format at month end.
• Testing squeezed. Configuration runs late and UAT becomes a short demonstration rather than a real test.

None of these require a large team to prevent. They need someone on the company's side who tracks open points, insists on seeing results rather than status reports and gets each question to the person entitled to answer it. For context on the requirements behind the project, see my ERP selection work in Italy.

How I oversee the partner from the company's side

A capable Italian partner brings product knowledge, localization and developers. What they cannot bring is authority to make your business decisions, and that is where projects lose time. I fill that gap from the client side.

The rhythm is simple: a weekly working session with the partner's project manager, a steering meeting with the owners or managing director at an agreed interval, and shared logs for decisions, risks and change requests. Before each design workshop I prepare the questions your process owners must answer; afterwards I confirm the decisions in writing and ask the right person to sign off.

When the partner proposes a workaround, I ask what it will cost your office staff in extra steps once the partner has left. When a new request arrives, it goes into the change log with its business reason and the partner's estimate, and the owners decide whether it enters the current scope or a later phase. That keeps the budget conversation honest without turning the relationship adversarial.

On partner-led projects I do not configure the system or take over the partner's delivery responsibility. I make sure what they deliver matches what the company agreed. My ERP implementation service describes the wider approach, and part-time leadership is covered under fractional ERP lead.

Migrating from Italian packages and spreadsheets

Many Italian companies starting an ERP project are leaving a package from a domestic software house, such as TeamSystem or Zucchetti, or an older product their supplier no longer develops, usually supported by spreadsheets for production, pricing or agents. The migration plan has to reflect how that data is held and who on your side can verify it.

I review the mapping templates and trial loads with your staff, focusing on what will break first if it is wrong:

• Customer records with VAT numbers, tax codes, recipient codes or PEC addresses, and payment terms.
• Open receivables with their collection schedules, so bank receipt collections due after go-live are not lost or duplicated.
• Open payables and supplier bank details.
• Agent assignments and commission bases for orders still open.
• Opening balances agreed to the legacy trial balance, and stock values agreed to the last count.

A trial migration counts as passed only when the person who owns that data has compared totals and signed them off. Where figures disagree, the correction happens in the source file or the mapping rules, not by editing records in the new ERP. Historic electronic invoices stay in the preservation archive where they were stored. See my ERP data migration page for the full approach.

Testing the e-invoice channel and the period close

Acceptance testing in Italy has to cover the documents that travel outside the company, because that is where problems become visible to customers and the tax agency. Together with the heads of sales, purchasing, production and accounts, I draft scenario scripts, and every Italian project includes:

• An order to cash cycle ending in an electronic invoice, its transmission, the delivery notification and the customer payment, including a bank receipt collection.
• A deliberately rejected invoice, corrected and resent without breaking the numbering.
• A supplier invoice arriving through the exchange system, matched to an order and receipt, then approved and paid.
• Material sent to an outside workshop and returned as finished goods, with costs captured.
• A credit note, an export invoice and the related cross-border reporting.
• A period close producing the registers and reports your commercialista uses for the VAT settlement.

The partner arranges the test channel for electronic invoices; I make sure the scripts use realistic data and that the commercialista reviews the results. Defects go into one log, triaged with the partner into real defects, training needs and new requests. UAT ends when agreed sign-off criteria are met. My ERP testing and UAT page explains the method.

Cutover, payroll handoff and hypercare in Italy

Cutover in Italy has a few moving parts that deserve their own owner. Invoices sent from the old system may still receive notifications after the switch, so someone must watch that channel until it goes quiet. The address where supplier invoices are delivered has to move to the new system in a controlled way, and numbering must continue without gaps or duplicates. The timing is agreed with the commercialista, who will prefer that one VAT settlement is not divided between two systems.

Payroll usually stays with your labor consultant. Before go-live I make sure the payroll journal arrives in a format the ERP can import, with agreed accounts and cost centers, a named person to post it and a reconciliation step each month.

From the first morning on the new system, key users meet briefly each day to review a single list of problems, and anything that stops invoicing, shipping or collections goes to the top. Issues are classified as training, data, configuration or process, and configuration faults go to the partner. Support steps down to normal levels only once the first close is done and the conditions we set beforehand are satisfied. I run it remotely, with your key users helping colleagues on site; a visit can be arranged if the owners want one. Italian training guides are prepared by your team or the partner. More on how I work with Italian companies is on the Italy overview and my Italian ERP consultant page.