R&D Binder

Short answer. A business component is the product, process, computer software, technique, formula, or invention that a company develops or improves and holds for sale, lease, license, or use in its own business. It is the unit the Section 41 four-part test is applied to.

The six kinds of business component

Section 41(d)(2)(B) lists six kinds. For a software company most components are computer software; build pipelines and internal tooling are often a process.

  • Product. Something you sell or license to customers.
  • Process. A method you use to produce or deliver, including build, deployment, and data pipelines.
  • Computer software. The most common kind for SaaS: the services, APIs, algorithms, and the systems behind them.
  • Technique. A specific method you developed to solve a technical problem.
  • Formula. A defined calculation or model built on a technical method, such as a scoring or matching model.
  • Invention. Something novel you built, whether or not it is patented.

Why the boundary decides the credit

The four-part test runs against each component separately, so where you draw the line changes what qualifies.

A business component has to be named with a boundary an auditor can see. 'The platform' is the whole company; an examiner will ask which part, which version, which team, and if the answer is everything, the claim fails on the first question.

The substantially-all rule is measured per component. At least 80 percent of the effort recorded against a component has to be experimentation, under Treas. Reg. 1.41-4(a)(8). Bundle a tightly experimental service together with months of routine deployment work and the combined component can drop under the threshold and fall out in full. Scope it to the experimental work and it stays in.

So the component is not a label added at the end. It is the unit the whole credit is built on, and naming it well is the difference between a schedule that reads as real and one that reads as reverse-engineered.

How the binder names components

Naming components by hand across a year of commits is where most documentation goes vague.

R&D Binder clusters your commit history into candidate components and names each one with a version range, a scope, and an owner, so the boundary is observable rather than asserted.

Each named component carries straight onto Form 6765 Section G, which asks for a Business Component Name and a Business Component Type per claim. The name on the schedule is the same name the four-part test was scored against.

A business component is the unit; these cover the test it has to pass and the costs it carries:

Sources

Every claim on this page traces to a primary authority. Each source below is independent and verifiable.

Get documentation built to survive an exam

R&D Binder clusters your commit history into candidate business components and names each one with a version range, scope, and owner, ready for Form 6765 Section G.

Estimate your credit See the sample binder