Jira Cloud · Runs on Atlassian · Zero egress · Rovo agent
Software Capitalization and R&D Time for Jira Cloud
CapRadar turns Jira work data into a CapEx and OpEx split and an R&D time record. Explainable rules, capitalization phases per epic, a queue for what is left to classify, approvals and a period lock. Every locked period becomes a hash-signed snapshot that your auditor can verify offline, and your cost rates never leave Atlassian.
Built on Atlassian Forge and distributed through Atlassian Marketplace. Works with or without timesheets.
Rules by space, category, epic, work type, label, component, custom field or JQL, inherited from initiative to worklog. Each result records why: the rule and version, or the override, plus phase, method and policy version.
Three methods inside Jira: attributed native worklogs, hours per work item and epic on Tempo sites, and timesheet-free allocation from Jira work item data with a calibration report.
Effective-dated phases per epic or initiative, including the ASU 2025-06 funding authorization date and the significant development uncertainty flag, with an evidence note.
A “To classify” queue with bulk actions, pre-close checks, review and approval with separation of duties, then lock and sign. Later changes become visible adjustments; a signed period stays final.
SHA-256 hashed snapshots chained period to period, a CSV pack with a manifest, and an auditor PDF pack with methodology, approvals and a reproducible random sample.
An R&D flag and category independent of CapEx treatment, and report layouts for common R&D relief regimes, each labelled for review by your advisor.
Role and person rates, effective-dated, imported by CSV (including the MarginRadar rate export), with blended rate fallback. Rates are visible to finance roles only.
Period, space and epic reports, per-person reports where attributed, an amortization schedule, plan versus actual, journal entry files and a one-page board pack.
A finance workspace in Jira, a capitalization panel on work items, a space page for engineering managers and a dashboard gadget.
Classify, review, approve and lock with attestation. Export the auditor pack and the journal file from the locked snapshot.
Engineering managers set phases and classify their own spaces. They see hours, and never rates or per-person cost.
Auditors read locked periods, exports and the audit trail, and verify any signed file offline with standard tools.
CapRadar supports your accounting and tax process and collects evidence for it. It does not give accounting, tax or legal advice. Every capitalization or tax decision (what to capitalize, from when, at what rate) stays with you, your auditor and your advisors.
CapRadar makes no calls outside Atlassian. No email, Slack or webhooks. Notifications stay in the in-app inbox.
Classifications, rates, policies, periods and snapshots live in Atlassian Forge hosted storage, following the data residency of your Jira site.
CapRadar reads Jira and stores its results in its own storage. Exports are generated in your browser.
The CapRadar agent in Rovo answers from CapRadar data computed inside Forge. It always states whether a period is a draft or approved and locked, names the measurement method and explains the configured policy.
MarginRadar shows cost, burn rate and margin from worklogs, and its rate export feeds CapRadar. AccessRadar and ConfigRadar bring the same signed evidence pattern to access reviews and configuration changes. CapRadar applies it to the capitalization close.
