About viewing and managing reclassification transactions

You can edit general ledger transactions that were generated by the reclassification process.
After editing, the number of the reclassification batch remains unchanged.

To perform editing, in the Journal transactions (GL301000) window, you need to select a batch of the Reclassification type with the Balanced or On hold status, and click Edit in the window toolbar. The Reclassify transactions (GL506000) window opens, displaying all journal entries included in the batch.
On this window, in the Reclass. batch number column, the number of the batch that you edit is shown.

You can edit the following details of each displayed journal entry: the branch (To branch), the account (To account), the subaccount (To subaccount), the transaction date (New trans. date), and the description of the transaction (New transaction description).
The following rules apply to the editing process:

• If you edit an account in one of the journal entries of the batch, the new account that you specify must have the same default currency as the default currency of the batch.
• If you change the transaction date for all journal entries of the batch, the date of the original batch will be changed after you finish editing the transactions.

While editing, you can add new journal entries (rows) to the list of journal entries in the Reclassify transactions (GL506000) window.
You add new journal entry (or multiple entries) by clicking Load in the window toolbar.
In the Load transactions dialog box, you specify the criteria to load the required journal entries.
For these journal entries, if you specify a post period or currency that differs from the period or currency of the original general ledger transaction, then when you process the transaction, the system generates a new reclassification transaction (with a new identification number) that includes these journal entries.

You can also delete journal entries (rows) from the list of journal entries when you edit a transaction, so that after you run the process, the reclassification transaction will not contain deleted journal entries.

You can reverse the general ledger transactions that were generated by the reclassification process.
To reverse these transactions, in the Journal transactions (GL301000) window, you need to select a released general ledger batch of the Reclassification type, and click Actions - Reverse batch on the window toolbar.
The Reclassify transactions (GL506000) window opens, which already contains the data that reverses the original batch.
In this window, you can edit the required details in the journal entries that are displayed.
When you click Process, the new Reclassification batch is generated.

You can view the history of reclassifications for a selected general ledger transaction that has been reclassified.
The reclassification history is represented as a list of transactions generated by the reclassification process, starting with the original general ledger transaction.
You can view the reclassification history for a transaction in the Reclassification history (GL405000) window.
You can open this window by clicking the Reclassification history button in the Account details (GL404000) window for the selected transaction (if it has been reclassified), or in the Journal transactions (GL301000) window for a selected transaction of the Reclassification type in the general ledger batch.

You can reclassify only the last transaction in the list of transactions in the Reclassification history (GL405000) window by clicking Reclassify in the window toolbar.

The following transactions cannot be reclassified:

• A journal entry of a transaction in which a control account is specified.
  (A control account is a general ledger account that accumulates the summary information of a subsidiary ledger.
  The details of the control account balance are contained in a subledger, so the balance of the control account should match the total of the related subsidiary ledger.)
• General ledger transactions generated in the General ledger workspace when consolidation data has been imported in the Import consolidation data (GL509000) window.
  For details, see: General ledger consolidation overview.
• General ledger transactions generated in the General ledger workspace by a user invoking the run allocations process in the Run allocations (GL504500) window.
  For details, see: About allocation rules.
• All general ledger transactions generated in the Currency management workspace.
• If the Project management functionality is enabled in Visma Net, the general ledger transactions related to any project.
  
  You can reclassify the general ledger transactions in which the non-project code is specified.