If the restaurant buys e.g. a fancy oven or a delivery truck, it can't expense 100% of that cost in year 1, it has to spread that cost over the lifetime of the oven or truck.
Labor that operates the business day-to-day would be an expense, labor that creates a capital asset is more complicated.
I happen to think most employee time in software dev is more on the day-to-day operation side, and should be expensed, but I can see an argument that some should (or could) be amortized.
> If the restaurant buys e.g. a fancy oven or a delivery truck, it can't expense 100% of that cost in year 1, it has to spread that cost over the lifetime of the oven or truck.
The difference of course is that you'll have a truck or oven that can be sold. If you could count the full value in the first year then you could sell and buy one each year to reduce your taxes without actually changing anything.
Thus if we want to go that route for software the salary of the R&D employees should be counted against the value of the software they created (As in, the value were it to be sold wholesale to another company). The time spent by the employees is not an asset, once you pay the employees for their time it's gone even if they generated nothing of value. The actual value is that of the software, but that's obviously not easily assigned a value.
It's a lot easier to get financing for a tangible asset like an oven or a delivery truck, which mitigates the cash flow issue.
Sure, you can only deduct a certain percentage of the asset's value as an expense each year, but your cash expenditures to pay for it are also spread over a multi year period.
Labor that operates the business day-to-day would be an expense, labor that creates a capital asset is more complicated.
I happen to think most employee time in software dev is more on the day-to-day operation side, and should be expensed, but I can see an argument that some should (or could) be amortized.