The R&D tax credit for software companies

The Section 41 credit rewards developing or improving a product through a process of experimentation grounded in the hard sciences. For software, the hard science is computer science, and the experimentation is the everyday work of trying an approach, measuring it, and refining or discarding it.

A team building a new search ranking system, a faster data pipeline, or a novel sync algorithm is resolving technical uncertainty: at the outset, the right design is not known. That uncertainty, worked through iteratively, is the heart of a qualifying activity.

Qualifying work includes new features with real technical risk, performance and scalability engineering, new architectures, and algorithm development. The common thread is uncertainty about whether or how the result could be achieved.

Routine work does not qualify: cosmetic interface changes, content updates, configuration, and bug fixes that apply known solutions. A credible claim carves these out rather than sweeping them in, which is also what protects the qualifying work on exam.

The largest qualified research expense is usually wages for the engineers doing the work, for the portion of their time spent on qualifying activities. Contract developers count too, at 65% of what you paid them, and cloud or compute used for development can count as well.

R&D Binder ties each expense back to the business component it supported and the four-part-test evidence behind it, which is what Form 6765 Section G now asks for.

• What is a qualified research activity?
• What is a business component?
• The Section 41 four-part test
• R&D tax credit for startups

• 26 U.S.C. § 41, credit for increasing research activities - Cornell Law School, Legal Information Institute
• Treas. Reg. § 1.41-4, qualified research and the four-part test - Cornell Law School, Legal Information Institute
• IRS, Instructions for Form 6765 - Internal Revenue Service