I've been researching this for another issue. Anyhow, expensing R&D is a perennial political issue. Logically, if you're creating an income-producing asset, then you have to depreciate it over its useful life. The theory is sound, but of course politicians can mess with it, as they do. But I thought the "useful life" of software was 3 years. No?
You usually want to incentivize R&D, messing with that simple theory is the standard. Anyway, even that 3 years common knowledge number is biased into long-lived code. Do you spend work time putting out fires? Do you write code that is immediately discovered to be wrong so you have to take more time and fix it? Those 3 years are only for software that already passed through all of that. (Anyway, I don't have any inte…
I don't have a dog in this fight either. Does "maintenance" on an amortized asset have to be amortized as well? Don't know.