Your R&D credit, calculated end to end.

Every number on the return ties back to a ticket, a person, and a defensible interpretation of §41.

Book a demo See the worked example

A return for every stakeholder. From your engineers to the IRS.

  • Engineering

    Traditional method

    Surveys and interviews 18 months later.

    People forget, re-org and leave.

    With Neo.Tax

    Eliminate almost all surveys and interviews.

    Red Ventures got back 300 to 800 interview hours.

  • IRS

    Traditional method

    Agrees engineers can't remember.

    Wants records made at the time.

    With Neo.Tax

    A calculation from records made at the time.

    Every number traced to the ticket, hour, and token behind it.

  • Tax

    Traditional method

    A painful process made worse by Section G.

    Provision first and the actual later.

    With Neo.Tax

    A more rigorous study in far less time.

    Refresh the data monthly or quarterly so the provision tracks the return.

  • CFO

    Traditional method

    A FIN 48 reserve and questions about the credit.

    "How are we using AI?"

    With Neo.Tax

    Better-supported credits and a lower FIN 48 reserve.

    An answer to "How are we using AI?"

See the full comparison

Review the study in the app. Projects, wage QREs and the credit calculation.

  1. 1Projects found in tickets
  2. 2Eligibility with the reasoning
  3. 3The details the study needs

Four steps from the ticket to the return.

1 / 4

Business components, identified from real work.

Built from your team's tickets and pull requests. No year-end survey.

ProjectsFY2025
Business components5 projects · 3,115 tickets
  • Payments ledger service
    Platform · 38 people
    1,318 tickets
  • Fraud model v3
    Risk ML · 21 people
    731 tickets
  • Mobile onboarding
    Growth · 26 people
    612 tickets
  • Support agent
    CX · 12 people
    280 tickets
  • Admin tooling
    IT · 9 people
    174 tickets
Auto-clustered from Jira and GitHub.
2 / 4

The four-part test, applied uniformly.

Every project gets IRS §41's four-part test. Same evidence gives the same answer.

QualificationFY2025
Project1234
  • Payments ledger service
  • Fraud model v3
  • Mobile onboarding
  • Support agent
  • Admin toolingExcluded···
  1. 1 Technical in nature
  2. 2 Qualified purpose
  3. 3 Technical uncertainty
  4. 4 Experimentation
3 / 4

Allocation tied to actual work.

Effort comes from ticket data. Never from job titles or self-reports.

AllocationFY2025
ProjectEffortQREs
  • Payments ledger service
    $6.4M
  • Fraud model v3
    $4.9M
  • Mobile onboarding
    $1.9M
  • Support agent
    $1.7M
  • Admin tooling
    $0
  • Qualified research expenses$14.9M
4 / 4

Form 6765, Section G, reproducible from the exports.

Auditors rebuild every percentage from one export with a pivot table.

Form 6765FY2025
Form 6765 Section GTax year 2025
Business componentTotal
  • 1Payments ledger service6,399,300
  • 2Fraud model v34,882,800
  • 3Mobile onboarding1,929,000
  • 4Support agent1,691,600
  • Total qualified research14,902,700
1traces to 1,318 tickets in PAY and LEDG and 38 people in payroll.

Follow one engineer. From tickets to an R&D share.

Jason Smith
Software Engineer · FY 2024
R&D Allocation
95%
Raw timestamps Active days

His active days on qualified projects set his R&D share at 95%.

Projects worked in FY 2024
  • Hardware Enhancements 327 tickets / PRs Yes
  • Billing System Overhaul 12 tickets / PRs Yes
  • Platform Security & Feature Development 1 ticket / PR Yes
3 other projects Not qualified

Each ticket is matched to a project. Each project is tested against the four-part test.

Tax leaders get their time back.

Read customer stories
“Filing this first year took at least 50% less time.”
Karin Barratt VP of Tax, Octane
“Neo.Tax significantly reduced the number of interviews we conducted and helped us eliminate a major cost with an external advisor.”
Sean Cannizzaro VP, Head of Tax Operations, Thomson Reuters
“Our CFO loved how unbelievable the ROI was. This is the only AI we've used that actually worked.”
Raymond Salort VP & Director of Taxes, Red Ventures

Questions auditors ask first.

How can I verify the calculation?
All steps are transparent. Task-level efforts are visible in the Ticketing view, and project-level allocations can be reproduced from exports. The R&D percentage is the sum of qualified project percentages.
What about people with very different ticket volumes?
Normalization accounts for ticket volume and size. Someone with many small tickets and someone with a few large feature tickets receive allocations driven by worked effort, not ticket count.
What about different job titles?
The base model treats qualified technical work consistently based on task complexity and timing. Role-based adjustments can be layered on later if needed.
What if our Jira data is messy?
Every company's is, and Neo.Tax is built for it. It reads the trail people leave as they work: tickets and commits with their timestamps and change logs. Manual tags count where you have them, and the trail counts most.

AI for Enterprise R&D. See how it works for your teams.

Book a demo