Italian chart of account

Rational

We don’t have a chart of account for Italy right now, I want to reify this.

Proposal

Creating a basic chart of account based on the model described in the Art. 2424(balance sheet) and Art. 2425(income statement).
From this model i can derive all the chart of account for different type of companies (the other articles describe in legalese witch account can be dropped for each type of company)

I need a help from the tax code template, if you have some sources please post it below.

Implementation

Tax codes are used to report the amount of each tax a company has paid/received during period to the tax authorities. On tryton are used to sum base (untaxes) and tax amounts of all acounting moves.

So you need to know:

  • Which taxes are yoused on your country
  • How this taxes are reported to the tax authorities.

Total n00b on the tax side, so sorry if i ask this:

  • I think i need to take a subset of the taxes (like just Value Added Tax, property tax, social security) and not all (like tax for alcohol/tobacco production).
  • Should i add the tax for community services (like waste management)?
  • Should i add the tax on document filing (usually this are 16€ stamps you buy in stores)
  • What about “de minimis regime”(regime dei minimi) invoices where there is no VAT, but you use a 2€ stamp?
  • what about the “professional register”(albo dei professionisti) rate (usually 4%) for self employed people, should i add this or leave it.

I can to a professional accountant in case of some doubt.

Another point,
The tax name are a bit contextual, for example:

  1. partecipazioni in: (shares in)
    a) imprese controllate (controlled company)
    b) imprese collegate (connected company)

Should i add the full name in each account (eg. “participazioni in imprese controllate” [shares in conttrolled company]) or leave it as is?
I ask it because sometimes different father account shares the child account name, and on tryton is a bit difficult to distinguish two account with the same name.

We normally add the taxes that are collected by companies which means:Value Added Tax, Import and Export taxes (you should create a tax rule for them) and so one.

Does company have the possibility to substract this taxes from the tax they collected? You should add them if the answer is yes.

As far as this is included on the invoice (this is the case in Spain) you should add them and ad a tax rule to be set on the self employed parties. If you want an example this is called Retencion taxes in Spanish Chart of Account.

I think you should use taxes and account as defined by tax authority always using the full name. This is the way that most accountants will find them.

P.S: If there is a code defined you should also set them on templates as most accountants will refer to accounts by it’s code.

We implemented some time ago an italian chart of account for a customer. It is on 5.0, please feel free to use it.
Some points should be reviewed:

1 Like

This is a huge help, thank you very much.

Hi
I’m a chartered accountant in Italy and have some experience with tryton, odoo and so on (there should be my translation there).
I’ve just seen the discussion, I have some simple remark.

  1. Here in Italy we have NO mandatory CoA, simply some accountant want to harmonize account with mandatory FS. So I do not see any point to use a long default CoA that’s not useful for anyone. Then I would avoid slashes or points in the account codes.

  2. Similarly for VAT it’s true it’s complicated but really I do not see the point of using such a mess of rates. We have a normal tax rate (22%), some exemptions, some limited deductions, INTRA and international transactions.

So I would struggle to keep SIMPLE the model, and evaluate the goal of the efforts.
If you need some help feel free to contact me.

Marco

I’ll just implement just art 2424 and 2425 and nothing more, i can create different type of chart for different entity type (micro, medium and big company) as the law suggest.

for now I’ll steer away the CoA for really big entities (I’m talking about the XBRL one)… it just add more sub-account.

I was thinking to implement:

  • varius VAT/IVA rates (22% and 10%)
  • undeductable VAT/IVA (in different percentages)
  • “ritenuta d’acconto” a.k.a. pay the taxes for me wold ya (4%)

If you can compile a small list of most used taxes a PMI would encounter, different from the one above it will help me.

P.S: @marco … i think we met before :slight_smile: (OpenDesignConference)

Another question:
The stock flag (account type), what does it means in the tryton context?
It should be for Account that hold the value of deprecable items?
Accounts that represent the value of goods in inventory?
Accounts that represent shares of another company?

Found something, bust still i have no clue Issue 4990: Merge account type and account kind - Tryton issue tracker

THsi post suggest that is for inventory items: Stock Account in French plan

But still unsure

It is for account that will be defined on product category to manage perpetual stock accounting. They are three accounts to define: Stock, IN and OUT.

@wifasoi My advice was to compile a simpler set than 2424 2425 that are made for FS and NOT for accounting. The law suggests NO CoA. As you said the law prescribes different FS, not accounts.
About VAT I would be pleased to help you, would you prefer to share the list here or to keep contact directly? Would you send me a model I compile?
Feel free to contact me when you want.

@wifasoi tryton like odoo/openerp and other erp systems was designed to work with both perpetual and discontinued inventory. In Italy it’s very rare to use perpetual so my advice is to encode the stock accounts all with a similar code in order to see them close.
In the case in the future you use perpetual you will change/configure such accounts and journals.

There is not overload by setting proper flags on the template chart as it will not prevent non-perpetual stock accounting.
In contrary if you do not set them in the template, users will have to “personalize” the account type which makes them harder to keep it up to date.