Trial balance with closing transactions analysis [BETA]

The extension prints a trial balance that separates the effect of closing transactions from the rest of the accounting. For each account it shows the unadjusted balance, the adjustments and the adjusted balance side by side on the same row.

Prerequisites

To use this extension you must:

• download and install Banana Accounting Plus.
• use a double-entry accounting file.

Beta version

The extension is currently released as a beta version. This means that some details may change without prior notice.

Install the extension

To install the extension:

• Open Banana Accounting Plus.
• Menu Extensions > Manage Extensions
• Select Universal as country.
• Select Online > Productivity.
• From the extensions list select Trial balance with closing transactions analysis.
• Click Install to install the extension.
• Click Close to close the window.

Create the report

To creare the report:

1. Open an accounting file.
2. From the Extensions menu select Trial balance with closing transactions analysis.
3. In Settings dialogue complete the options then click OK to create the report.

The texts of the settings dialog and column headers in the printout are fixed and are in the same language as the Banana file (defined from the menu File > File and accounting properties > Other > Current language). The languages that can be used are Italian, French, German and English.

The report always covers the whole accounting period of the file, from the opening date to the closing date set in the file properties.

On first use, the Doc codes field is empty: the codes must be entered because they depend on each accounting's conventions. If the report is run without them, a warning appears and the adjustment columns stay at zero.

Settings dialogue

Run the extension from the menu Extensions > Trial balance with closing transactions analysis.
The extension Settings dialogue will open. From here you can choose some parameters to print the report.

Transactions filter:

• Closing transactions indentification method
  Choose one of the following methods to filter the closing transactions:
  • Codes in the Doc column
    If closing transactions are identified by specific codes in the Doc column of the Transactions table, enter the code or multiple codes separated by ; (e.g. "CHIU" or "CHIU;ABC;XXX"). The Doc value must exactly match one of the specified codes (case-sensitive).
  • Text in the Description column
    If closing transactions are identified by specific text in the Description column of the Transactions table, enter that text.
  • Custom JavaScript function
    If you want to use a different method to identify closing transactions, you can use a custom JavaScript function. For example, the following function identifies closing transactions by searching for the text "Closing transaction" in the Notes column:
    function(row) { var d = row.value("Notes"); return d ? d.indexOf("Closing transaction") >= 0 : false; }

Report:

• Show closing transactions details
  Adds at the end, for each account with closing transactions, the list of the individual transactions.
• Split by BClass
  Groups the accounts into Assets, Liabilities, Revenues and Expenses, with a header and a total for each section.
• Show zero amounts (0.00)
  When off, zero amounts are left empty (except in the grand total).
• Show negative amounts in red
  Shows negative amounts in red, as in Banana's tables.
• Print cost centers and segments
  Adds the cost center and segment sections, if the chart of accounts contains them.
• Show columns
  Select the columns to display in the report.
  • Account
    The account number.
  • Description
    The description of the account.
  • Opening
    The opening balance of the account.
  • Unadjusted – Debit / Credit
    The movements of the year without the closing transactions of the account.
  • Unadjusted – Balance
    The balance before the closing transactions, opening included, of the account.
  • Adjustments – Debit / Credit
    The movements of the closing transactions only of the account.
  • Adjustments – Movement
    The total amount of the account's closing transactions (Debit − Credit).
  • Adjusted – Debit / Credit
    The account's total movements for the year.
  • Adjusted – Balance
    The account's final balance, after all transactions.
  • Var. % balance
    The account's percentage change of the balance caused by the closing transactions.
  • Last posting date
    The date of the last transaction on the account

Layout:

• Print in landscape orientation
  Print the report in landscape orientation.

The report

The report starts with the title, the company header (defined in the file properties) and the accounting period. Then follow the main table, the optional cost center and segment sections and, if requested, the closing transactions details.

Main table

The table lists all accounts with a BClass, in the order Assets, Liabilities, Revenues and Expenses, and ends with the Grand total. The amounts are grouped into three blocks:

• Unadjusted
  Movements and balance before closing transactions.
• Adjustments
  Movements of the closing transactions.
• Adjusted
  Total movements and final balance after the closing transactions.

For every account the following always holds:

Unadjusted balance + Adjustmenst movement = Adjusted balance

In a balanced accounting, the balances in the grand total are 0.00.

Percentage change

The Var. % balance column shows how much the closing transactions moved the balance, relative to the unadjusted balance in absolute value:

Var. % = (Adjusted balance - Unadjusted balance)  /  |Unadjusted balance| * 100

A positive value means a shift towards Debit, a negative one towards Credit, for any account type. n.m. (not meaningful) is shown instead of the number when the unadjusted balance is below 1.00 in absolute value or when the change exceeds ±1,000 %. If the account has no closing transactions, the cell stays empty.

Closing transactions details

With the option on, the end of the report contains a table for each account affected by closing transactions, with Date, Doc, Description, Contra account, Debit and Credit of each transaction and the total. It shows which transactions produced the movement reported in the main table.

Custom JavaScript function

The custom function lets you define rules that Doc codes or Description text cannot cover, for example by combining several columns. Banana calls it for each journal row of the account: if it returns true the row is a closing entry, otherwise it is not.

Writing rules:

• write the function on a single line and without a name after function;
• it receives row, the journal row, as argument; values are read with row.value("ColumnName");
• use the internal column names (XML names), not the visible headers;
• it must explicitly return true or false;

Example 1 - text in the Notes. Treats as closing transactions the rows whose Notes column contains YE:
function(row) { var n = row.value("Notes"); return n ? n.indexOf("YE") >= 0 : false; }

Example 2 – several conditions. Treats as closing transactions only the rows with Doc CHIU and Closing in the description:
function(row) { var d = row.value("Description"); return row.value("Doc") === "CHIU" && d ? d.indexOf("Closing") >= 0 : false; }

Warning messages

Warnings appear in Banana and the report is still generated, but without closing transactions.

• "Codes in the Doc column" method selected, but no code was entered. No entry was considered a closing entry.
  • The codes field is empty or contains only ; and spaces.
• "Text in the Description column" method selected, but no text was entered. No entry was considered a closing entry.
  • The text field is empty or contains only spaces.
• The custom function to identify closing entries is empty or invalid. No entry was considered a closing entry.
  • The field is empty, contains a syntax error or does not define a function.