> For the complete documentation index, see [llms.txt](https://kb.bevica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bevica.com/bevica-select/opening-balances-inventory/bevica_select_-_trial_balance_opening_balances_template.md).

# Trial Balance Opening Balances Template

### Before you start

* Understanding the Configuration Worksheet: [Configuration Worksheet](/bevica-select/bevica_select_training/bevica_select_-_excel_template_data_migration.md#configuration-worksheet).
* Understanding Excel templates: [Excel Template Data Migration](/bevica-select/bevica_select_training/bevica_select_-_excel_template_data_migration.md#excel-template-data-migration).
* Understanding how financial opening balance imports work: [Bevica Select - Finance Data Migration Overview](/bevica-select/opening-balances-inventory/bevica_select_-_finance_data_migration_overview.md).

### Map G/L accounts

You will need to map the G/L Account number from your old system to the relevant G/L Account number in Bevica. In addition to this, you will need to switch the following accounts to be the migration control account (in the ZZ99XX range):

* Sales Ledger Control Account - do not post to 2310, post to ZZ9910 instead
* Purchase Ledger Control Account - do not post to 5410, post to ZZ9920 instead
* Bank Control Accounts - do not post to accounts in the 2900..2990 range if they are linked to a bank account, post to ZZ9930 instead
* Stock Control Account - do not post to 2120, post to ZZ9950 instead

Once the TB has been loaded in, accounts ZZ9910 to ZZ9950 should all equal zero. If any have a balance, then the entries brought over as part of the SL, PL, Stock, or Bank data migration didn't equal the total of the ledger control accounts in your old system.

### VAT amounts

If you are going live part way through a VAT quarter and have opening input and output VAT values on your trial balance, post these values to the VAT input and output accounts in Bevica. Note that you will need to switch on Direct Posting for the journal to post. Remember to switch it back after the journal has been posted.

For more information see [Opening VAT Balances](/bevica-select/opening-balances-inventory/opening_vat_balances_and_initial_vat_return.md)

### Create a manual journal

If you would prefer to create the opening trial balance journal manually rather than importing a template, navigate to the General Journal and open the ZZ-DM journal batch. Populate the columns listed below except for:

* `Journal Template Name`
* `Journal Batch Name`
* `Line No.`

### Template

The template is a pre-formatted spreadsheet with the fields you need to create your opening trial balance transactions within Bevica.

You will need a list of opening balances per G/L Account from your old finance system. This may be one value per G/L Account or the balance may be broken down by Dimension combinations.

The template has the following fields:

<table data-header-hidden="false" data-header-sticky><thead><tr><th width="170">Field ID / Field Name</th><th width="155">Related Table</th><th width="143">FieldType</th><th>Note</th></tr></thead><tbody><tr><td>1 <code>Journal Template Name</code></td><td>(82) Gen. Journal Template</td><td>Code 20 (Mandatory)</td><td>Enter GENERAL</td></tr><tr><td>51 <code>Journal Batch Name</code></td><td>(232) Gen. Journal Batch</td><td>Code 20 (Mandatory)</td><td>Enter ZZ-DM</td></tr><tr><td>2 <code>Line No.</code></td><td></td><td>Integer (Mandatory)</td><td>Must be a unique number per line. Line numbers normally start with 10000 and increment by 10000, for example 10000, 20000, 30000.</td></tr><tr><td>5 <code>Posting Date</code></td><td></td><td>Date (Mandatory)</td><td>Set all Posting Dates to the date before go-live. For example, if you are going live 01/01/22 then you should have all posting dates set to 31/12/21.</td></tr><tr><td>76 <code>Document Date</code></td><td></td><td>Date (Mandatory)</td><td>Set this to be the same as the Posting Date.</td></tr><tr><td>6 <code>Document Type</code></td><td></td><td>Option (Leave Blank)</td><td>Leave this blank.</td></tr><tr><td>7 <code>Document No.</code></td><td></td><td>Code 20 (Mandatory)</td><td>The whole journal should have the same document number, for example OPENBAL.</td></tr><tr><td>77 <code>External Document No.</code></td><td></td><td>Code 35 (Optional)</td><td>Populate this if you have another reference to bring across</td></tr><tr><td>3 <code>Account Type</code></td><td></td><td>Option (Mandatory)</td><td>Enter G/L Account</td></tr><tr><td>4 <code>Account No.</code></td><td>(15) G/L Account</td><td>Code 20 (Mandatory)</td><td>The G/L Account in Bevica. Any value entered here must already exist in its related table.</td></tr><tr><td>8 <code>Description</code></td><td></td><td>Text 100 (Mandatory)</td><td>Enter a relevant description.</td></tr><tr><td>13 <code>Amount</code></td><td></td><td>Decimal (Mandatory)</td><td>Enter the Amount.</td></tr><tr><td>11 <code>Bal. Account Type</code></td><td></td><td>Option (Mandatory)</td><td>Enter G/L Account</td></tr><tr><td>63 <code>Bal. Account No.</code></td><td>(15) G/L Account</td><td>Code 20 (Mandatory)</td><td>Enter ZZ9940</td></tr><tr><td>Dimensions</td><td></td><td>(Optional)</td><td>Enter the relevant dimensions. Any value entered here must already exist in its related table.</td></tr></tbody></table>

### Upload the journal

Once the template has been applied, navigate to the General Journal **ZZ-DM** batch and check that the journal holds the same information as the data migration template used.

* Ensure all columns you have imported data into are visible (with the exception of Journal Template Name, Journal Batch Name, and Line No.).
* Have all the lines been imported?
* Select a number of lines at random. Are they all correct and the values both correct?
* Export the journal lines to Excel and make sure the details look correct, including dates and values.
* Select **Post/Print** then **Preview Posting**. Check the entries that will be posted look correct.

### Post the journal

Before posting any opening balances, it is a good idea to copy the company as a backup, so you have a point to return to if there are problems once the **General Journal** has been posted. See [Bevica Select - Creating new Bevica companies](/bevica-select/bevica-select-data-migration/bevica_select_-_creating_new_bevica_companies.md) for information on how to do this.

### Reconcile

Once posted, the entries need to be reconciled with the values from your old system. The following should be checked:

* Balance on G/L Accounts. Check that the figures on your old system and Bevica match. On the Chart of Accounts page, set a Date Filter to be the Posting Date of the journal imported. You will see the Balance field which will be the total for each G/L Account.
* Check the data migration control accounts in the ZZ9910 to ZZ9950 range equal 0.

Another trusted user, rather than the person who created and posted the opening balance, should perform these checks. They should do this using their own data source from your previous system and not rely on the migration files you used in case there were errors on those.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://kb.bevica.com/bevica-select/opening-balances-inventory/bevica_select_-_trial_balance_opening_balances_template.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.