ERP Selection Consultant, Italy

Should the current software house simply supply the next ERP?

In Italy the relationship with a software house often runs deep. It knows your processes, it set up the electronic invoicing, and switching feels risky. Staying can be sensible, but the decision deserves the same scrutiny as any alternative.

I start by reviewing what the incumbent proposes: whether it is an upgrade of the same product or a migration to a newer platform in their range, what data and customizations carry over, how the licensing model changes and how the product would support plans such as a new foreign entity or more advanced production planning. Then the incumbent goes into the shortlist and runs the same scripted demos as everyone else.

This often clarifies things in both directions. Sometimes the incumbent's offer looks strong once compared fairly, and the selection simply gives the owners confidence to proceed. Sometimes it reveals that a family business has outgrown a system built around a single company and a single founder's way of working. Either way, the choice is documented.

Family firms in a generational handover benefit in particular, because the selection forces decisions previously held by one person to be written down. That ties into the process work described on my Italian ERP business analyst page.

What Italian companies put on the shortlist

The shortlist depends on the size and complexity of the business more than on brand. For Italian companies the candidates I typically consider look like this:

For each candidate the key question in Italy is how the electronic invoice cycle is delivered: natively, through a connector app, or through an external intermediary. Each route has a different cost, support contact and upgrade risk, and the answer may vary by edition or partner. The same applies to bank receipt collections and statutory registers. A candidate that fails an essential requirement leaves the list at this point, and the file notes why. For a broader view of how I work with Italian businesses, see my ERP consultant page for Italy.

Making each demo run the electronic invoice cycle

Every vendor will say it supports Italian e-invoicing. A demo has to show what that means in practice. I script a sequence using your own customers and items:

1. Issue a domestic invoice to a customer identified by a recipient code, and a second to a customer receiving through a PEC mailbox.
2. Show the transmission status and the delivery notification once the exchange system returns it.
3. Simulate a rejection, correct the invoice and resend it, keeping numbering intact.
4. Receive a supplier invoice from the exchange system, match it to a purchase order and goods receipt, and post it.
5. Issue a credit note and an invoice to a foreign customer, and show how the cross-border reporting is handled.
6. Show where invoices and notifications are sent for digital preservation and how they can be found later.

Further scenarios cover bank receipt collections, agent commissions, material sent to outside workshops and stamp duty on exempt invoices where your advisor says it applies. Your process owners score each step as standard, configuration, connector or custom work. Tax treatment itself is confirmed by your commercialista; the demo tests whether the system behaves as they describe. My ERP evaluation page explains the scoring method.

Comparing proposals from Italian partners

Italian partner proposals often differ less in their headline figure than in what sits outside it. To compare them, I break each one into the same lines and record what is included, assumed or left to you:

• Licenses or subscriptions and how they grow with users or companies.
• The e-invoicing connector or intermediary service, and who supports it.
• Digital preservation: included, a separate contract or left to the commercialista.
• Italian print layouts, document numbering and statutory registers.
• Data migration from the current system, including open items and collection schedules.
• Training, support terms and response times.

Typical gaps include migration limited to master data, preservation not mentioned at all, and a connector priced as included for the first period only. Each gap becomes a written clarification question, and answers feed the scoring sheet. I also ask each partner for named team members and for references with companies of similar size and sector, then hold those calls with a structured question list.

If proposals are already on your desk and you only want them checked, my vendor proposal review handles that as a standalone piece of work, and ERP RFP consulting covers a formal tender.

GDPR, hosting and the contract before you sign

An ERP holds employee, customer and supplier data, so GDPR questions belong in the selection rather than after it. I send every shortlisted vendor and partner the same short questionnaire: where production and backup data are hosted, which subprocessors can access it, how support access is controlled, how a data processing agreement is put in place and how all data can be exported if you leave. Your lawyer or data protection advisor reviews the answers; I make sure the questions are asked while they can still influence the choice.

The contract review then checks that the statement of work names the scenarios that were demonstrated, that acceptance is tied to them, and that change requests follow an agreed process. Contracts are often in Italian, so your lawyer reviews the legal wording while I compare the scope against the selection record.

The work runs remotely in English, with sessions in the hours that overlap between Italy and India and written notes after each one. A meeting in person can be arranged if the owners want one. You keep the requirement list, demo scripts, scores, proposal comparison and recommendation. When delivery starts, the same documents support my ERP implementation oversight in Italy. Everything else I offer Italian companies is on the Italy overview.