> 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/trial-balance/import-chart-of-accounts.md).

# Import a chart of accounts

Upload a spreadsheet of asset, liability, equity and revenue accounts to build or update the chart of accounts on your trial balance.

The **Import Chart of Accounts** page adds your chart of accounts from a spreadsheet. Owners, Super Admins and Managers open it from the Trial Balance page (**Trial Balance** in the sidebar).

{% hint style="info" %}
If your production uses a chart of accounts, **Trial Balance** is in the sidebar. If your company also uses chart of accounts import, the **Import a chart of accounts** link shows at the top of that page.
{% endhint %}

## Prepare your file

Select **sample-chart-of-accounts.xlsx** in the note at the top of the page to download the template. Or email your chart of accounts to the address in that note, and RollCredits can upload it for you.

Leave Expense accounts out: a file with any can't be read. Importing a budget adds them, so [import your budget](/budget-and-cost-report/import-budget.md) first if you haven't.

The file must follow these rules:

* It's an .xlsx file with one sheet, or a .csv file.
* The first row holds the headings `Section Code`, `Section`, `Section Type`, `Subsection Code`, `Subsection`, `Subsection Type`, `Code`, `Category` and `Category Type`, spelled exactly like this.
* Every row has a `Section Code`, `Section` and `Section Type`, so leave no blank rows. Repeat a section's code and name on each row that belongs to it.
* Types are `ASSET`, `LIABILITY`, `EQUITY` or `REVENUE`, in capitals. Subsection and category types match the section's type.
* A category needs a subsection on the same row. A subsection or category with a blank code, name or type is left out.

{% hint style="warning" %}
The template spells its last heading `Category type`. Change it to `Category Type`, with a capital T, or your categories aren't imported.
{% endhint %}

## Import the file

1. On **Trial Balance**, select **Import a chart of accounts**.
2. Drag your file into **Chart of Accounts file**, or select the box and choose it.
3. Once the file is read, select **Next**.
4. Check the accounts found, shown as code, name and type under their parents. To start over, select **Back** and choose the file again.
5. Select **Import**, or **Overwrite** if the production already has accounts.

You see **Successfully imported trial balance** and return to Trial Balance.

If the file can't be read, **Next** stays greyed out and a message under the field says so. Check it against the rules above, or write to the address in that message.

## Overwrite existing accounts

If the production already has accounts, the review step warns that the import will overwrite them. When you select **Overwrite**:

* Only accounts whose type appears in your file can change. Expense accounts from your budget aren't touched.
* Accounts with the same code under the same parent are kept and take the name from the file.
* Other accounts of those types are deleted, unless coded transactions or escrow employees use them. Those are kept, along with the accounts above them, and the success message says how many.


---

# 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/trial-balance/import-chart-of-accounts.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.