One ledger. Many auditors can read it.
Every hour in a Tymr report traces back to a source event — a Jira transition, a GitHub commit, a calendar block, a ServiceNow incident, an agent run. The compliance pack is a downstream view of the same ledger that powers capacity and project cost — not a separate workflow, not a quarterly scramble.
The frameworks covered
Three regulatory regimes, one ledger underneath. Each artifact ships with a methodology PDF and a workpaper-ready CSV.
IRC §41 + §174 / SR&ED
Per-worker, per-project qualifying hours with the four-part test applied per activity bucket, contemporaneously, and cited back to source events. Federal + state estimates with base-period rules accounted for. Canadian SR&ED supported.
Workers don't fill surveys. Controllers spot-check edge cases.ASC 350-40 / IAS 38
Application-development stage cleanly separated from preliminary project stage and post-implementation. Journal-entry ready, with the ITGC walkthrough your auditor expects, plus the amortization schedule (5-year for internal use, 15-year for non-US R&E).
Capitalize vs. expense, project-by-project, live.DCAA labor allowability
Per-employee daily time records, supervisor approvals, manual adjustments logged, indirect-vs-direct labor split. Built around the floor-check rules DCAA actually applies — not a generic timesheet bolted onto a federal program.
Tamper-evident audit log, hash-chainable.The four files in every pack
Every compliance engagement ships the same four deliverables — sized to drop into the file your accountant, tax firm, or DCAA representative already uses.
R&D credit estimate
Per-worker, per-project qualifying hours with a federal + state credit estimate measured against last year's claim. Where the lift is, where the risk is.
PDF · 6–8 pagesCapitalization pack
Hours that belong on the balance sheet, cleanly split from day-to-day expense work. Journal-entry ready, with the ITGC walkthrough your auditor wants.
PDF · journal-entry readyWorkpaper-ready CSV
Worker, project, hours, period, classification, evidence link — in the column shape your tax firm or accountant already uses. Paste, don't rename.
CSV · standard schemaMethodology PDF
Two pages, plain English. Where the data came from, how each hour gets classified, how a human handles ambiguity — the document a tax partner or DCAA auditor defends.
PDF · 2 pagesHow an engagement runs
One scope. Files at the end. No worker surveys, no quarterly spreadsheets, no re-platforming.
Hook up the tools
OAuth into your calendar, Jira, GitHub, ServiceNow, Workday. Scope the group. Pull last year's claim, if applicable, so we have a benchmark.
Run continuously
Every event auto-classified into the right framework: qualifying / capitalized / expensed / direct / indirect. Your controller reviews edge cases in about thirty minutes a week.
Hand off the pack
Four files delivered. We walk your tax firm, auditor, or DCAA representative through them on a single call. Preparer signs off on the methodology.
Roll wider
Standardize across the org, or scope quarter by quarter. The ledger underneath stays the same — only the framework view changes.
Working with your existing partners
Tymr is not a tax firm and not a return preparer. We sit underneath your existing study and produce the time evidence your firm has to collect anyway — just cleaner, captured as the work happens, and tied back to source events.
The time-evidence layer your study already requires
Per-worker, per-project hours with the right framework tags, captured as the work happens. Every hour cites a Jira transition, a GitHub commit, a calendar block, an agent run, or a ServiceNow incident. Exports as CSV into your firm's existing workpaper template.
Not a tax firm. Not a return preparer. Not a study.
We don't file returns. We don't touch the credit study. We don't share or cap your firm's fees. We don't build a direct tax relationship with the client — your firm stays the advisor of record.
R&D boutiques
Your analysts skip the time-survey grind on software and tech-services clients. Your firm keeps the engagement and the fee. The study is defensible without the April scramble.
Workpaper-compatible CSV out of the boxNational firm software practices
Tymr underneath a Big-4 / national-firm R&D practice or software-vertical team. We produce the contemporaneous evidence; your firm signs the workpapers and the methodology PDF.
No re-platforming required for the clientIn-house tax / DCAA leads
For organizations with internal tax or contract-compliance leads, Tymr is the time substrate — with the four files delivered to your team instead of an external partner.
Direct delivery, same filesWhy the substantiation holds up
The credit math is the easy part. The hard part — and the reason most organizations under-claim, get haircut, or fail an audit — is substantiation: proving the work actually qualified, with contemporaneous evidence tied to specific projects and workers.
Every hour in a Tymr workpaper traces back to a source event — time-stamped and immutable, with hash-chainable corrections expressed as new events that reference the original. When your tax firm prepares the credit, when your auditor walks the cap-ex schedule, or when DCAA looks at your floor checks, the evidence is already on file.