Business Process Consultant, Italy

Why Italian processes stall between departments

In many Italian companies each department works well on its own. Sales knows its customers and agents, the warehouse knows its shelves, administration knows the invoices. The trouble sits in the handoffs. A price agreed by an agent never reaches the order. A delivery note leaves with the goods but the invoice waits until month-end, and nobody checks whether quantities changed. A supplier invoice arrives through the exchange system before the goods do, and the person who could match it is on the road.

Owner-led firms add a second pattern: decisions that flow through one person. Purchases, discounts, credit for a slow payer and even small supplier changes wait for the owner's yes. That keeps control, but it also creates a queue that grows with the business.

I start by following real documents through the company rather than asking how things are supposed to work. A recent order, its delivery note, the invoice, the collection and the posting in the books tell a precise story. In online workshops I draw that story as a swimlane map, with every wait, re-entry and workaround marked. The method behind this is on my ERP process mapping page, and it works whether or not a new system is planned.

SdI notifications and delivery notes as process steps

Electronic invoicing in Italy runs through the national exchange system, and every invoice produces responses: a delivery receipt, a rejection, or a notice that the file could not be delivered and is available in the recipient's reserved area. Systems display these messages, but a process decides what happens next.

In the order-to-cash design I agree with you:

• Who checks the status of outgoing invoices, and how often.
• What happens after a rejection: who corrects the data, how the corrected invoice is reissued and who confirms acceptance, all within the timing your commercialista advises.
• How customers are told when delivery failed and the invoice sits in their reserved area.
• Which master data, such as the recipient code or PEC address, must be confirmed before the first invoice to a new customer.

Delivery notes deserve the same attention. Where goods ship with a delivery note and invoices follow later, the process needs a clear point where someone checks that every delivery note has been invoiced, and that returns and price changes were applied. I mark that control on the map with its owner. Timing rules are your commercialista's to state; the map simply guarantees a step exists that applies them.

Ri.Ba. collections, unpaid returns and the agent

Bank receipt collections remain part of how many Italian companies get paid, and the process around them is longer than it looks. I map it from the moment payment terms are agreed with the customer to the day the money is safely in the bank:

1. Payment terms and bank details captured on the customer record.
2. Due dates planned from the invoice and grouped for presentation.
3. Presentation to the bank, and the posting when credit arrives.
4. Unpaid returns received, recorded and charged back where agreed.
5. Sales, the agent and the customer informed, with a decision on whether to present again, agree a new date or move to a reminder.
6. Agent commissions adjusted if they depend on actual payment.

The weak points are usually the final steps. An unpaid return is booked correctly, but the agent keeps selling to the same customer, or the commission statement goes out unchanged. Clear owners and a short rule for each case fix much of this without any software.

The same map covers SEPA direct debits and bank transfers, so administration works from one view of how each customer pays. Credit decisions, such as blocking further orders, stay with a named person and follow limits management sets.

Supplier invoices, preservation and approval limits

On the purchasing side, Italian companies receive supplier invoices as structured files through the exchange system, often before the goods are checked in. The procure-to-pay map has to answer what happens in that gap. Who matches the invoice to the order and the receipt? What happens if quantities differ or the price is wrong? Since an invoice cannot simply be sent back the way paper once was, the process needs a route for asking the supplier for a credit note and tracking it until it arrives.

Digital preservation belongs on the same map. Invoices and other documents must be preserved under the applicable rules, often through a provider or with the commercialista's help. In many firms nobody actually checks that every file reached preservation. I add that check as a periodic step with an owner, and leave the legal requirements to your advisor.

Approval limits complete this part. I help you write a simple matrix: who may order, approve an invoice difference or authorize a payment, by amount and area, with the owner keeping the decisions that genuinely matter. Approval design in more depth is on my approval workflows page, and the requirement side is covered by my Italian ERP business analyst work.

The commercialista, the labor consultant and the software question

Most Italian companies rely on outside advisors: a commercialista for tax and statutory books, a labor consultant for payroll. The record-to-report and hire-to-pay maps show exactly what flows to and from them. Which reconciliations does administration finish first? Which reports does the commercialista expect for the periodic VAT settlement? How do hires, leavers, absences and overtime reach the labor consultant, and how does the payroll journal come back into the books? When these handoffs are written down, they stop depending on phone calls in the last days of the month.

Personal data travels through these flows, especially in hire to pay. I mark on each map which personal details pass to which advisor, giving your privacy counsel a concrete basis for a GDPR review. The legal conclusions are theirs to draw.

Only then does software return to the conversation. Sometimes the current gestionale can support the agreed process with better setup. Sometimes a new system is needed, and the maps become the brief described on my ERP consultant page for Italy. Repetitive steps the maps uncover lead into my Italian business automation work. Everything I offer Italian firms is listed on the Italy overview.