What should an outsourced R&D study include?
A useful R&D tax credit study connects the client's technical activities to the expenses and calculation reported for a particular tax year. A polished narrative is only one part of that file. The activity and expense requirements are distinct (IRC §41(d) and §41(b)). The reviewer also needs the expense sources, allocation reasoning, historical inputs, method analysis, and open issues.
Before referring a client, agree on the entities, years, states, projects, and preparation responsibilities. Ask which schedules will be delivered and who will confirm technical facts. An engagement for calculation and documentation preparation should not leave either firm assuming that the other handles return filing, elections, or examination representation.
Paribus prepares R&D tax credit studies and supporting claim packages for businesses and their advisors. Tell us about your client and the help they need before sharing confidential records.
Make information requests easier for your client.
Identify one accounting contact and a technical contact who understands how the development work was performed. The accountant can explain the entity structure, filing calendar, and financial records. The technical contact can identify uncertainties, alternatives, testing, and the point at which development ended.
A staged request is often more productive than sending a large generic checklist. Start with a project inventory and available records, then ask targeted follow-up questions. Route overlapping requests through an agreed contact so the client does not receive different versions of the same question.
Decide whether the CPA will join technical discussions and review draft schedules. Record changes and outstanding questions in one place. This makes it easier to distinguish information awaiting confirmation from a conclusion ready for tax review.
What should the supporting workpapers include?
- A business-component inventory and factual activity descriptions.
- Qualified expense schedules tied to payroll and accounting sources.
- Explanations of excluded costs and allocation methods.
- Calculation inputs, historical data, and method considerations.
- Separate state schedules where included in the scope.
- A list of unresolved facts and return-level decisions for your team.
For example, a wage total should lead to the employees, periods, activities, and source records behind it. A reviewer should not have to reverse-engineer a percentage from the final credit. The study review checklist offers a practical way to assess that connection.
What to ask before choosing a study provider.
Ask how the preparer distinguishes qualifying experimentation from routine work and how conflicting evidence is handled. A discussion focused only on a projected refund can overlook the work necessary to support it. Ask how the preparation changes when records are incomplete or a project includes both development and production.
Clarify pricing, timing, access to working schedules, record retention, and responsibilities after delivery. We discuss the delivery format, filing calendar, and services your client needs with your firm before the engagement begins. If your client needs examination assistance or representation, discuss those services separately.
For a prior-year engagement, flag amendment deadlines and earlier elections before work begins. For a current-year engagement, consider Form 6765 business-component reporting while organizing the records.
Tell us where your client needs help.
On the first call, tell us about your client’s industry, development work, tax years, and business structure. You do not need a credit estimate or a complete study to discuss preparation. Avoid sending payroll or tax returns through the website form.
Tell us whether you need a first activity review, calculations based on existing records, state preparation, or help organizing supporting documentation. We can discuss what the file should contain and how it will fit your review process. Call Paribus to talk through your client's R&D work.