Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Look up section 162 vs 174 treatment and the distinction between "new companies" vs "carrying on a trade". It's far from unambiguous and as long as you have a defensible position you absolutely are entitled to push the envelope.

Is implementing a specification a REE "in the experimental or laboratory sense"? I'd say it's not, and I don't have to explain my position unless I'm audited.

https://www.law.cornell.edu/cfr/text/26/1.174-2



It looks like the CFR (at least here) hasn't been updated to match the corresponding USC: https://www.law.cornell.edu/uscode/text/26/174

See c(3). Any software development is unambiguously R&D.


Section 174 intro: "In general in the case of a taxpayer’s specified research or experimental expenditures for any taxable year".

Note limiting phrase.

Section 174 later: "For purposes of this section, the term “specified research or experimental expenditures” means, with respect to any taxable year, research or experimental expenditures which are paid or incurred by the taxpayer during such taxable year in connection with the taxpayer’s trade or business."

Note the "in connection with the taxpayer's trade or business" and look up the definition of that phrasing versus "carrying on" business and compare to Section 162. (e.g., Snow v. Commissioner of Internal Revenue, 416 U.S. 500 (1974), Cantor v. Commissioner of Internal Revenue, 998 F.2d 1514 (1993), Scoggins v. Commissioner of Internal Revenue, 46 F.3d 950 (1995))

Section 174 later: "For purposes of this section, any amount paid or incurred in connection with the development of any software shall be treated as a research or experimental expenditure."

Note the limiting phrase.

Ultimately we need guidance from the Service but the above are (possibly aggressive) readings some CPAs are taking.


You don't specify which expenses, the USC does in the next subsection (if you got to specify it it would be "specified by the taxpayer". "For purposes of this section" is in the same section.

Stranger things have happened but I don't see how someone can defensibly argue that software dev doesn't have to be ammortized.


> See c(3). Any software development is unambiguously R&D.

"For purposes of this section" to me means you don't have to justify software development as R&E if you define that software development work as R&E.

Being pedantic, but it's R&E not R&D.


Except the purpose of the section is to say that R&E has to be amortized. So it seems pretty clear to me that software development costs have to be amortized.


Exactly. I don't see how anyone can read this and tell the IRS with a straight face that their software dev doesn't need to be ammortized.


According to Bloomberg [1], for ongoing business expenses, it doesn’t. For startup costs, it does need to if you want these RD credits.

[1] https://news.bloombergtax.com/tax-insights-and-commentary/ch...

It is ambiguous even if you disagree with Bloomberg.


Not one mention of "software" in that article. It's clearly written in a general context where this may be true. They don't mention c(3) at all:

"For purposes of this section, any amount paid or incurred in connection with the development of any software shall be treated as a research or experimental expenditure."




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: