Identify which side of the contract you are on.
A business that hires an outside developer needs to examine whether its payments meet the contract research requirements. A firm doing development for a customer needs to examine whether its own research is excluded as funded. The same agreement can matter to both businesses, but their analyses are not interchangeable.
Begin by identifying the taxpayer claiming the credit, the work performed, and the parties' obligations. An invoice labeled engineering or R&D provides only a starting point. The activity must also meet the research requirements, and the expense must satisfy the relevant inclusion rules.
When your business hires a researcher.
Review the agreement in place for the services, the nature and location of the research, payment obligations, and your rights in its results. Contract research expenses are addressed in IRC §41(b)(3) and Treas. Reg. §1.41-2(e). The potentially includible amount is not automatically the full invoice.
Ask the vendor to distinguish research work from implementation, training, maintenance, or other services when the available records allow that distinction. Preserve the statement of work, amendments, invoices, and evidence of the actual services. A combined invoice should not become an unexplained single figure in the study.
If a contractor subcontracts work, clarify where and by whom it was performed. Discuss advance payments and work spanning multiple tax years with the preparation team rather than assuming the invoice date resolves timing.
When your customer pays your business.
For the research performer, the funded-research analysis examines payment risk and substantial rights in the research (IRC §41(d)(4)(H); Treas. Reg. §1.41-4(c)(9) and §1.41-4A(d)). Retaining rights by itself does not resolve the payment question, and taking financial risk does not by itself resolve the rights question.
A fixed-price label is not a complete answer. Review acceptance provisions, warranties, termination rights, change orders, and the circumstances in which payment is owed. The actual contractual obligations matter more than a sales description of the engagement.
Bring the complete agreement rather than a selected intellectual-property paragraph. Related documents may change the meaning of that paragraph or explain how the project was carried out.
Match contract terms to the work performed.
Imagine an engineering firm developing a customer-specific assembly. It models alternatives, builds test versions, and revises the design. Those facts may warrant an activity review, but they do not establish which party can include which costs.
A study should connect the technical record to the relevant agreement and cost schedule. Identify which project phases each contract covers, whether amendments changed the obligations, and how payments relate to the work. Separate an unresolved contract question from a supported expense conclusion.
- Collect signed agreements and incorporated terms.
- Match statements of work and amendments to projects.
- Identify payment and acceptance provisions.
- Document rights and restrictions on use of results.
- Reconcile costs to the services and tax year reviewed.
Discuss the agreement before estimating a credit.
Paribus Advisors helps evaluate research activities and expenses as part of study preparation. Flag customer-funded work early so contract issues can be discussed with your accountant and, where needed, legal counsel.
Call with a high-level description of the arrangement. Avoid uploading contracts through the public contact form; agree on a document-sharing process after the initial discussion. For firms providing technical services, our engineering firm guide also explains how to organize project evidence.