Trial balance configuration

Trial balance configuration

The trial balance feeds the module's Origin balances. It is loaded via Process, using the [Accounts] Trial Balance model (described in the article "Process-based deployment"). This article explains the structure the trial balance needs to have in order to be read correctly.

Where the data comes from

Process is Dattos' data preparation workflow builder. For this reason, the trial balance can come from any source: a file, an API, or a database from any system. What matters is that, throughout the preparation flow within Dattos, the data is delivered in the standard columns described below. This is what ensures it is read correctly by the module, regardless of the source.

The standard structure

The trial balance follows the standard TrialBalance structure and must have only one load per reference month. When the company has more than one trial balance (by business or by different ERP), they are unified into this same structure throughout the flow, before loading.

The 7 required columns

By the end of the preparation flow, the trial balance must have these seven columns, all required:

• BusinessCode: the code of the business unit or headquarters, the same as in the Businesses tab of the company and account records.

• EnterpriseCode: the code of the company or branch.

• AccountNumber: the account number.

• StartingBalanceAmount: the opening balance of the account in the period.

• DebitAmount: the debit movement.

• CreditAmount: the credit movement, reported with a negative value.

• EndingBalanceAmount: the closing balance of the account in the period.

After loading

After running the trial balance process, check in Account Analysis whether the balances have been updated. For testing, use a month the company will actually use later, so you do not leave open statuses in earlier periods.

Where to go next

• Process-based deployment.

• Customer reports and logo.