ERPNext Accounting in Italy

A chart of accounts the commercialista can read

ERPNext lets you load a chart of accounts from a template or build one by hand. Whether a maintained Italian template exists for your version, and how close it sits to the piano dei conti your accountant works with, needs a direct answer from Frappe or the partner, never an assumption. I treat the chart as a design document, not a file to import and forget.

The design covers four things:

• Statutory grouping: account groups arranged so the commercialista can map them to the balance sheet and income statement layout they prepare in their own software.
• Management detail: product lines, plants or sales channels handled through cost centers and accounting dimensions, avoiding a growing list of ledger accounts.
• Default accounts: item groups, customers, suppliers and stock pointed at the right accounts, so users rarely pick one by hand.
• Several companies: where an owner holds an operating company beside a property or holding company, each gets its own chart and fiscal setup in one installation, with intercompany documents agreed in advance.

This step ends with a mapping table signed off by the advisor: every ERPNext account against the statutory line it feeds. That table pays for itself at year end, when nobody has to guess where a balance belongs. General finance features are described on the ERPNext Accounting page.

IVA templates, nature codes and the registers

ERPNext expresses tax through templates attached to selling and buying documents, per-item overrides and tax categories. In Italy that toolkit must express more than a rate. Exempt, excluded and non-taxable operations each carry a nature code in the electronic invoice file, domestic reverse charge applies in certain sectors, and invoices to public bodies may fall under split payment. Which of these apply to you is your advisor's decision.

I turn the advisor's list into a template matrix:

• One template per rate and per special case, named so users recognize it at a glance.
• The nature code and legal reference wording the invoice must show, stored where the Italian app or intermediary reads them.
• Tax categories that switch templates automatically for EU customers, exports and reverse charge suppliers.
• Purchase-side handling for EU acquisitions, where your advisor specifies the self-invoice document required.

The registers are the harder part. ERPNext produces a general ledger and tax reports, but Italian sales and purchase IVA registers and the periodic settlement follow layouts your commercialista knows from Italian software. I check whether your version or an Italian app produces them; if not, we agree an export the advisor imports. Separate invoice sections, the sezionali, are modeled with naming series and tested for gaps and duplicates.

Invoices through the SdI: what the ledger has to know

The ERPNext in Italy page sets out the transmission options: an Italian app, an external service or an Italian package beside ERPNext. On the accounting side the question is narrower. Once a sales invoice is submitted in ERPNext, how does the ledger learn what happened to its file?

Whatever route you choose, I agree the same ledger rules with the app maintainer or intermediary:

1. Each invoice carries a transmission status finance can filter on: sent, delivered, rejected or awaiting outcome.
2. A rejected file leads to a correction the advisor approves, either an amended document or a credit note and reissue, never a quiet edit of a submitted invoice.
3. Supplier files received through the intermediary become draft purchase invoices, with duplicate checks on supplier and number.
4. Receipts and files are kept by the preservation service your advisor approves, with a reference stored on the ERPNext document.

I then run a full cycle in staging, including an invoice designed to be rejected. If the app or intermediary cannot meet these rules on your version, I say so plainly. Confirm current behavior with Frappe, the app publisher or the partner shortly before go-live, because Italian technical specifications change and apps follow at their own pace.

Italian banks, CBI files and foreign currency

The ERPNext bank reconciliation tool works on statements imported from files or received through a bank integration. Italian banks commonly exchange data in CBI layouts, and whether your version reads those directly, needs a community app or needs a small conversion step is a point for the partner to confirm. I collect sample files from each bank early, because this detail decides how much manual matching finance keeps.

Collections get their own test plan:

• Ri.Ba.: producing the presentation file, recording the effect on customer balances, posting the bank credit and reversing an unpaid item.
• SEPA direct debits and transfers: mandate details held on the customer and payment files your bank accepts.
• Supplier payments: payment entries grouped the way treasury actually releases them.

Exporters billing in US dollars, Swiss francs or pounds need foreign currency receivable accounts, an exchange gain and loss account and a periodic revaluation the advisor agrees with. ERPNext handles currency well at document level; the real work is agreeing which rate source and timing the books follow. If sister companies trade with each other, intercompany invoices and balances are tested in the same round. The multi-currency page covers the general method.

Who maintains the Italian layer, and when ERPNext is the wrong ledger

ERPNext is released under the GPL license with no per-user software fee, but the Italian layer around it needs an owner. You can run on Frappe Cloud, self-host with a European provider or use a partner's hosting; each choice changes who applies upgrades and who retests the Italian app afterward. I write that down with names, not job titles.

The upgrade discipline I recommend:

• Every upgrade rehearsed on a copy of production, then checked against a closed period: same registers, same settlement, same balances.
• No upgrade scheduled close to an IVA deadline your advisor flags.
• Custom code held in a separate app with its own repository, so the core stays upgradable.
• A named support contact for the Italian app, whether a community maintainer or a paid partner, with expectations agreed in writing.

ERPNext Accounting is the wrong choice when the commercialista keeps the full ledger in Italian software and will not move, when nobody can own the Italian app, or when a parent group already runs another ERP. ERPNext can then run operations and pass summaries to the advisor, or a platform with a vendor-maintained localization, such as Odoo Accounting in Italy, may suit better. I hold no Frappe partnership and resell neither hosting nor support. The Italy ERP consultant page explains how remote delivery works.