System Integration Consultant, Italy

Which connections an Italian ERP has to get right

The integration inventory for an Italian company usually shows two kinds of links. Some are mandatory in practice, because invoices, preservation and bank collections cannot run without them. Others are operational, and their absence shows up as re-keying and reconciliation work.

For each line I note the provider, the contract owner, how errors are noticed today and who fixes them. In Italian companies it is common for one person in administration to be the only one who knows how a given upload works. The inventory makes that dependency visible and turns it into a documented flow. My ERP integration page explains the general method.

The SdI channel, notifications and supplier invoices

Sending an invoice file is the easy part. The integration has to handle what comes back and what arrives unannounced.

• Outgoing invoices are generated by the ERP with the recipient code or PEC address from the customer record, then passed to the channel. The design states which document types and series go through which route, including invoices to public administration where your advisor confirms different rules apply.
• Notifications such as delivery, failed delivery and rejection must be read back into the ERP against the original document, so administration sees the status without logging in elsewhere.
• Rejections follow a defined correction path that keeps numbering intact, with an alert to a named person.
• Received invoices are imported from the channel, matched to the supplier by VAT number, and checked against purchase orders and goods receipts before posting.

Where the ERP uses an intermediary, I check what the intermediary actually returns, how quickly, and through which interface, because that determines how much of this can be automated. Where invoices pass through a PEC mailbox instead, the design says who reads it and how files reach the ERP. Whether a particular treatment is correct for tax purposes is for your commercialista; the integration makes sure the system behaves as they describe. The Italian ERP business analyst page shows how these rules become requirements.

Ri.Ba., SEPA and bank statements through remote banking

Italian collections still lean heavily on bank receipt collections, alongside SEPA direct debits and transfers. Each method creates a cycle the ERP has to follow from start to finish.

• Presentation: the ERP builds the collection file from due installments and sends it through the remote banking channel your bank provides.
• Outcomes: paid and unpaid results come back as files. Paid items close; unpaid ones reopen with the bank charges posted and a task for the credit controller.
• Supplier payments: SEPA transfer files are produced from an approved payment proposal, with supplier bank details changed only through an approval step.
• Statements: daily statement files are imported and matched, so cash in the ERP agrees with the bank each morning.

Banks differ in which formats and channels they support, and some companies use several banks with different arrangements. I plan a test exchange with each one, including an unpaid collection and a returned transfer, before go-live. The design also covers where each bank's credentials live and who can trigger a file, because payment flows deserve tighter access than any other interface. Your bank's own specifications and your commercialista's posting rules are the reference; my job is a design that follows both and can be tested. The Odoo Accounting page for Italy shows one platform's take on these flows.

Payroll, logistics, outside workshops and online sales

Payroll. Italian payroll is often prepared by an external labor consultant or a payroll service. The ERP needs a journal by account and cost center, delivered in a consistent file, plus a way to reconcile it against the payroll summary. I agree the mapping of pay elements with finance and the consultant and define how corrections are handled in later periods.

Logistics. When a third-party warehouse handles storage or shipping, the ERP sends shipment orders and receives confirmations, tracking and stock movements. Transport documents must be consistent between the two systems, so I specify which system numbers them and how differences are flagged.

Outside workshops. Manufacturers sending material to subcontractors for processing need the ERP to know what is held where. Movements out and back are linked to the subcontracting order, and where the workshop can exchange files or use a portal, I design that flow too.

Online sales. Marketplace and webshop orders bring customer data, payments settled net of fees and returns. The mapping covers tax codes, shipping charges, refunds and how each settlement is split into gross sales, fees and payouts. For retail outlets, I check with your advisor how daily receipt totals from shop tills should reach the ledger. Businesses in ecommerce and manufacturing usually carry most of these flows at once.

Choosing the method, testing and running it after go-live

For each flow I set the practical routes side by side: a native module in the ERP, a connector from the software house or an intermediary, a middleware platform, a custom API service or scheduled files. The comparison weighs reliability, cost drivers, who supports the link and how upgrades affect it. A connector that only one small firm maintains may be acceptable, but the contract should say what happens if that firm changes its product.

Testing uses real documents from your business: an invoice to a customer with a recipient code, one with only a PEC address, a credit note, a rejected file, a supplier invoice that does not match its order, an unpaid collection, a payroll correction and a marketplace refund. Administration ties the results back across systems before anyone signs, and the switchover plan states which channel switches on, which switches off and how documents in transit are handled.

After go-live, an alert reaches a named person whenever an invoice is rejected, a notification is missing or a bank file fails. A runbook explains how to reprocess safely. The work is remote, with visits by arrangement. The sales side of these flows is on my CRM consultant page for Italy, and the wider ERP view is on my ERP consultant page for Italy.