Which ATECO code should I choose when starting a software agency in Italy? Tax and invoicing processes

Your accountant's recommendation of 62.01.00 is standard and accurate. There is no legal issue with having multiple codes; you can easily add 62.02 (consulting) and 58.29 (software publishing) as secondary codes alongside your primary one. The only thing you need to watch out for is ensuring your primary code represents the bulk of your day-to-day operations.

I set up under forfettario with code 62.01.00 in Turin last year. On a turnover of 38,000 EUR with the 67% coefficient, my taxable base came out to roughly 25,460 EUR. Gestione Separata contributions hover around 26%, and with the 5% income tax rate for the first five years, the overall system is very predictable.

If there are two of you, run the numbers carefully to see whether opening two separate forfettario setups makes more sense than starting an srls. With an SRLS, you lose the INPS flexibility of the ATECO code, and your fixed accounting and balance-sheet filing costs climb to around 3,000 EUR a year.

There are three things you need to clarify with your commercialista during registration: 1) Whether the primary activity is registered as a freelance profession or an artisan/commercial business, 2) The intended invoice weighting for secondary codes, and 3) Whether you'll need to submit a SCIA when you transition to selling pre-built products.

we faced a similar dilemma in Rome but we initially put the consulting code as primary and then some corporate clients startted demanding certifications for invoicing. once we switched back to 62.01.00, everything went smoothly; it's by far the cleanest path for agency work.

we have both 62.01 and 62.02 active but i mean just make sure the invoice desscription matches the code and you're good, nobody checks the line item details anyway but the inps side is super critical make sure u don't get stuck with fixed contributions.

edit: typed from phone, sorry for typos.

Are you planning to sell the pre-built cloud tool as a subscription hosted directly on your own infrastructure, or deploy it onto the client's servers? That distinction could trigger the commercial register requirement down the line.

Let me share what happened to me; it might be useful. When you try to change everything at once nothing settles.

If you post the result here, it will help others too.

Just a heads-up. Processes without records never improve, because you don't know what to fix.

Hasty decisions become decisions you have to fix six months later.

There's a part I don't understand. Any unwritten clause becomes a point of disagreement later, as both sides remember it differently.

Thanks, this was very helpful.

Exactly like that. In legacy systems, the most expensive thing is unknown dependencies.

I'm also curious if anyone does it differently.

I was thinking the same thing. Every "we'll look at it later" in a meeting means unbilled work.

Just because everyone does it doesn't mean it's right. I'm also curious if anyone does it differently.

I went through the same thing two years ago. When we decide without measuring, we always end up in the same place.

When making a decision, first look at what data you have on hand. Hope this helps.

There are three things to check when doing this. Hasty decisions become decisions you have to fix six months later.

If you get three different answers on a topic, the question was asked wrong. Proven by experience.

Following.

I'd appreciate it if you shared the outcome. Implementing a change request process doesn't slow things down, it speeds them up.

If you post the result here, it will help others too.

Saved. Hasty decisions become decisions you have to fix six months later.