> For the complete documentation index, see [llms.txt](https://knowledge.rollcredits.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.rollcredits.io/company/custom-fields.md).
# Set up custom fields
Add your own fields to transactions and to their category or account lines, for every production in your company.
Use the Custom Fields page to add your own fields to transactions. Open it from **Company > Custom Fields** in the sidebar, which shows it to Owners, Super Admins and Managers.
Custom fields belong to the company, so every production in it uses the same fields. The page has two tabs, and each one has its own list of fields:
* **Transactions**: fields for a whole transaction. They appear as columns in the transactions table and in the transaction's side panel.
* **Transaction Categories**: fields for each category line you code a transaction to.
Each tab lists its fields with their **Name** and **Type**. To fill fields in on transactions, see [Find and edit transactions in the table](/transactions/transactions/find-and-edit.md), [Review and edit a transaction](/transactions/transactions/edit-a-transaction.md) and [Code transactions](/transactions/transactions/code-transactions.md).
{% hint style="info" %}
If your production uses a chart of accounts, the second tab is called **Transaction Accounts**, and its fields are on each account line.
{% endhint %}
{% hint style="info" %}
If RollCredits payroll is turned on for your production, Text and Dropdown fields on the **Transaction Categories** or **Transaction Accounts** tab show a **Payroll** badge next to their name. Pointing at it shows **This field is available to use on payroll timesheets**. When you create or edit a field on that tab, a note at the top of the window says **For payroll fields, use the available column types: Text, Dropdown.** To give an employee a default value for these fields, see [Add and edit payroll employees](/payroll/setup/employees.md).
{% endhint %}
## Create a custom field
1. Select the tab the field belongs on.
2. Select **Create Custom Field**.
3. Enter a **Name**.
4. Choose a **Type**: **Text**, **Number**, **Money**, **Dropdown**, **Date**, **Percentage**, **Checkbox** or **Formula**. A new field starts as **Text**.
5. For a **Dropdown** or **Formula** field, set up its options or its formula, as described below.
6. Select **Confirm**. To close without saving, select **Cancel**.
Each name can be used only once on a tab. Names that differ only in capital letters, or in spaces at the start or end, count as the same. If the name is taken, you see **A field with this name already exists.** and **Confirm** stays greyed out.
### Add dropdown options
When the type is **Dropdown**, an **Options** list appears with one empty box.
1. Type the first option.
2. Select **Add Option** and type the next one. Repeat for each option.
3. To take an option out, select **Remove** next to it.
A dropdown always keeps at least one box, so **Remove** is greyed out when only one is left. Empty boxes are dropped when you save.
### Build a formula
A Formula field works out its own value by adding and subtracting amounts on the same transaction or line. Nobody can type in it. It shows as a column in tables, but not among the fields in the transaction's side panel.
When the type is **Formula**, a **Formula** list appears with one item that adds **Amount**.
1. On each item, choose **+** or **-**, then choose **Amount** or one of the tab's Money fields.
2. Select **Add Item** to add another item.
3. To take an item out, select **Remove** next to it.
A formula always keeps at least one item, so **Remove** is greyed out when only one is left.
On the **Transactions** tab, **Amount** is the transaction's amount. On the **Transaction Categories** or **Transaction Accounts** tab, it's the line's amount. A formula can use only Money fields from its own tab, so create those first. A Money field left empty counts as zero.
## Use a field for tax incentives
Text and Dropdown fields on the **Transaction Categories** or **Transaction Accounts** tab can feed the Tax Incentives page.
1. Create or edit a Text or Dropdown field on that tab.
2. Tick **Enable for Tax Incentives Aggregation?**.
3. Select **Confirm**.
**Company > Tax Incentives** then totals the lines of the production you have open by each value of that field. Only Owners and Super Admins can open that page. See [Track tax incentives](/company/tax-incentives.md).
## Edit a custom field
1. Select the **...** menu at the end of the field's row.
2. Select **Edit**.
3. Change the **Name**, the dropdown options, the formula or the tax incentives checkbox.
4. Select **Confirm**.
You can't change a field's **Type** after it's created. Renaming a field keeps the values already entered in it.
{% hint style="warning" %}
You can't remove or rename a dropdown option while it's chosen anywhere in the company. If you try, you see **Failed to update custom column** and none of your changes in that window are saved. You can still add new options.
{% endhint %}
## Delete a custom field
1. Select the **...** menu at the end of the field's row.
2. Select **Delete**.
3. In **Remove Custom Field**, select **Confirm**.
{% hint style="danger" %}
Deleting a custom field can't be undone.
{% endhint %}
**Delete** is greyed out while the field is in use, and pointing at it shows **Field is in use and cannot be deleted. Remove its references first.** A field is in use when:
* A value has been saved for it anywhere in the company, such as on a transaction, a category or account line, or a payroll timesheet. Clearing the value later doesn't change this.
* A Formula field on the same tab uses it.
* It's mapped to a class for accounting sync. See [Map accounts for accounting sync](/accounting-sync/configure.md).
---
# 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://knowledge.rollcredits.io/company/custom-fields.md?ask=&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.
