> For the complete documentation index, see [llms.txt](https://help.swarmia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.swarmia.com/features/capitalize-software-development-costs.md).

# Software capitalization

Use developer activity data from Swarmia to generate capitalization reports and blend with cost data.

{% embed url="<https://www.youtube.com/watch?v=yw5JW-tZrZU>" %}

Accounting and engineering rarely meet, but in modern software development organizations, that sometimes becomes a must. When software development costs are treated as long-term assets, it's essential to accurately connect effort with specific projects.

<figure><img src="https://2772466312-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMa8uBmGhQgR7MTPq9yh7%2Fuploads%2Fgit-blob-809cd8255fed70b8724812397680bd4fdb13a87c%2FCapex.png?alt=media" alt=""><figcaption><p>How software capitalization works in Swarmia</p></figcaption></figure>

Swarmia helps organizations track and report on capitalizable software development costs with precision:

* We connect data from your Git and issue tracker to accurately understand how developers allocate their time. Data accuracy is ensured because your developers regularly view and verify their activity in Swarmia.
* You can define custom rules to match what work qualifies as capitalizable
* Your finance team can export monthly or yearly software capitalization reports

### Using Swarmia

<figure><img src="https://2772466312-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMa8uBmGhQgR7MTPq9yh7%2Fuploads%2Fgit-blob-e84c2f2a04d6b60254a875ff11dabd5b8eebeed2%2Fcapex-frontpage.png?alt=media" alt="Swarmia - Software capitalization"><figcaption><p>Reports on software capitalization based on your Swarmia data.</p></figcaption></figure>

Swarmia automatically generates monthly reports based on developer activity, issue hierarchy, and capitalization rules. You can manually generate data and override the previous snapshot for the given month.

{% hint style="info" %}
Software capitalization is available to [organization admins](https://help.swarmia.com/settings/organization/managing-users-and-roles.md).
{% endhint %}

### Setting up your categorization

You can categorize issues manually, set issue filters to categorize them automatically, or combine both approaches. AI suggestions can help you review your categorization.

{% hint style="info" %}
Remember that only work linked to issues can be capitalized. If much of your organization's effort involves unlinked pull requests, consider creating issues and linking them to enable capitalization.
{% endhint %}

#### Manual categorization

Manual categorization works well if you capitalize a small number of large projects annually. These projects are easily identified in the [**work tab**](https://app.swarmia.com/capitalization/work) and marked "Capitalizable." When you categorize issues manually, you'll see a small hand icon next to the category.

<figure><img src="https://2772466312-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMa8uBmGhQgR7MTPq9yh7%2Fuploads%2Fgit-blob-3e95e4c2386af77ced433b74a01078a1f76b5ebd%2FScreenshot%202025-06-16%20at%2012.53.38.png?alt=media" alt=""><figcaption><p>The work tab shows all issues for the year grouped by the highest level.</p></figcaption></figure>

#### Automatic categorization

Automatic categorization works best if you already have clear categories in your issue tracker and want to transfer them to Swarmia. On the [**setup tab**](https://app.swarmia.com/capitalization/setup), you'll find a section called "Rules for software capitalization," where you can configure filters to identify capitalizable work.

<figure><img src="https://2772466312-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMa8uBmGhQgR7MTPq9yh7%2Fuploads%2Fgit-blob-6ecf81b2bd3fda9c945e6d060ce472d9c60aa22e%2FScreenshot%202025-06-16%20at%2012.54.23.png?alt=media" alt=""><figcaption><p>A typical way of doing automatic categorization is via a Jira custom field connected to capitalizable initiatives or epics.</p></figcaption></figure>

#### AI suggestions

AI suggestions help you identify work that may need a closer look, whether you categorize work manually or use rules. Swarmia considers the issue's title, type, labels, and description and suggests whether the work is capitalizable (CapEx) or not capitalizable (OpEx). Suggestions don't change categories until you apply them.

To enable suggestions, select **Suggest categories automatically** when setting up software capitalization, or enable **AI suggestions** on the [setup tab](https://app.swarmia.com/capitalization/setup). By default, suggestions are limited to issues without a parent issue. Under **Advanced options**, you can change which issues receive suggestions and customize the suggestion prompt to reflect your accounting policy.

When you save changes to enabled AI suggestion settings, choose **Save only** to keep existing suggestions for matching issues without generating suggestions for existing work immediately. Choose **Save and refresh** to generate suggestions for matching issues updated this year. Refreshing uses your AI quota. Suggestions for issues outside the filter are removed with either option, but categories you've already applied are kept. Prompt changes apply to suggestions started after you save.

### Reviewing your capitalizable work

Review your capitalization data before exporting:

The [**work tab**](https://app.swarmia.com/capitalization/work) allows you to examine issues and see how much of each is marked as capitalizable. The issues are grouped at the highest level, which means the capitalization percentage represents how much of the work grouped underneath is capitalizable.

If you've set automatic categorization rules and see a lower-than-expected capitalization percentage, it is likely because child items do not match your rules.

With AI suggestions enabled, the work tab's **Suggestion** column shows the suggested category. Hover over it to see the reasoning, and use the checkmark to apply a suggestion that differs from the current category. The **Worth a second look** summary highlights capitalized effort the AI considers non-capitalizable (**Risk**) and non-capitalized effort it considers capitalizable (**Potential**). Select either to filter the work table for review.

The [**inbox tab**](https://app.swarmia.com/capitalization/inbox) lists uncategorized top-level issues with effort in the selected year. Suggestions are preselected when available. Review the reasoning, choose CapEx or OpEx, and use the checkmark to apply the category. You can also use **Apply all** to apply the selected categories on the current page.

The [**employees tab**](https://app.swarmia.com/capitalization/employees) shows employees and their respective capitalization percentages. This means how much of their total accumulated effort is directed towards capitalizable issues. This view also shows excluded days (time offs and inactive days), which lower an employee's accumulated effort. You can find more on this topic in [the effort article](https://help.swarmia.com/definitions/developer-effort-ftes.md).

### Building reports

Once you've categorized work (either manually or automatically), reports will automatically be generated and delivered to the [**reports tab**](https://app.swarmia.com/capitalization/reports). In this view, you'll find monthly and yearly exports. The exports are split into employees (yearly) and capitalization (yearly/monthly) files.

You can use these files as raw data or alternatively, compile them into a capitalization report using our reporting template. To use the reporting template, copy it by clicking the "Copy reporting template" button on the reports tab and follow the instructions inside.

### **Frequently asked questions**

**Q: Can the work be aggregated by a specific Jira issue type in the software capitalization report?**

**A:** It's not possible right now, but we're going to add support for this in the future. Currently, the work is aggregated by the highest-level issue that we can find from your Jira issue hierarchy. However, you can already see the FTE values for any of your issues from Swarmia's UI.

**Q: Can I capitalize unlinked pull requests?**

**A:** No. Software capitalization only accounts for work linked to issues. We require each line item in your capitalization report to have proper documentation in the form of an issue. If you have significant effort in unlinked pull requests, consider creating issues and linking them to enable capitalization.

**Q: What's the optional "additional info" field in software capitalization settings?**

**A:** It is an extra column in the work export that provides more context about the capitalizable project (e.g., the reason for capitalization, and the capitalization date).

Concretely, it's a field in your Jira issues, e.g. a label or a custom field, that's pulled to the capitalizable work export as a separate column. It can be used for custom reporting purposes if you don't prefer to use software capitalization reporting template.

**Q: Can I convert the software capitalization reporting template to a .xlsx file?**

**A:** It's not possible right now as some of the formulas used in the Google Sheet reporting template are not available on Microsoft Excel. We're planning to build a reporting template for Excel in the future.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.swarmia.com/features/capitalize-software-development-costs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
