Manage transactions /visma-net-erp/help/general-ledger/manage-transactions section Transactions posted to General ledger are organised into batches that can be created manually or generated automatically by the system when documents are released in other Visma Net workspaces. 2026-02-19T17:09:06+01:00 # Manage transactions Transactions posted to General ledger are organised into batches that can be created manually or generated automatically by the system when documents are released in other Visma Net workspaces. Transactions posted to General ledger are organised into batches that can be created manually or generated automatically by the system when documents are released in other Visma Net workspaces. Each batch can contain one transaction or multiple transactions. A transaction, in turn, can contain at least two journal entries, for which the account and debit and credit amount is specified. This topic describes how to work with batches in the General ledger workspace, and how to create, release, and post batches in this workspace. It also describes how to automate the entry of transactions that are repeated regularly (recurring transactions), and how to create adjusting transactions that are reversed at the beginning of the next period (auto-reversing transactions). General ledger batches /visma-net-erp/help/general-ledger/manage-transactions/general-ledger-batches section 2026-02-19T17:09:06+01:00 # General ledger batches About general ledger batches /visma-net-erp/help/general-ledger/manage-transactions/general-ledger-batches/about-general-ledger-batches page Transactions posted to General ledger, whether manually entered or system-generated, are organised in batches. 2026-02-19T17:09:06+01:00 # About general ledger batches Transactions posted to General ledger, whether manually entered or system-generated, are organised in batches. Transactions posted to General ledger, whether manually entered or system-generated, are organised in batches. Because of the potential for errors, we recommend that manual entries to the General ledger be kept to a minimum. This topic focuses on the use of manually entered general ledger batches. ## Manually entered batch All transactions in one general ledger batch must use the same currency (but not necessarily the base currency). They also must be posted to the same ledger and the same period. A General ledger batch must include at least two transactions. For each transaction, you should specify all of the following by using the [Journal transactions (GL301000)](/visma-net-erp/help/general-ledger/general-ledger-windows/journal-transactions-gl301000/) window: + Account + Subaccount (if subaccounts are enabled in your system) + Debit or credit amount The total credit and debit amounts of transactions in a batch must be equal; otherwise, the batch cannot be processed further. CAUTION: No transactions can be entered for the **Year-to-date net income** account. When you first save a batch, its batch number is automatically generated in accordance with the numbering sequence assigned to General ledger batches in the [General ledger preferences (GL102000)](/visma-net-erp/help/general-ledger/general-ledger-windows/general-ledger-preferences-gl102000/) window. ## Batch status The batch status reflects its current state and defines what processing can be applied to it. See below for a description of the batch statuses.
Status Description
On hold

A batch with On hold status cannot be released or posted.

You can give a batch this status by selecting the Hold check box in the Journal transactions (GL301000) window. The On hold status is usually assigned to a newly created batch if further editing is planned.

Also, if after being edited, a batch becomes out of balance, it can be saved as On hold. If a batch that’s on hold has total debits equal to total credits, you can change its status to Balanced once you clear the Hold check box.

To have the On hold status assigned by default to all batches on their entry, select the Hold batches on entry check box in the General ledger preferences (GL102000) window.

Balanced

The Balanced status indicates that the batch’s debit total equals its credit total and the batch can be released or posted. You can modify or delete a balanced batch, but you can save changes only if the batch’s credit and debit totals remain equal.

To have the Balanced status assigned by default to all entered batches, clear the Hold batches on entry check box in the General ledger preferences (GL102000) window.

Scheduled

The Scheduled status indicates that the batch was attached to a schedule. A scheduled batch is used as a template for generating similar general ledger preferences batches with dates calculated according to the schedule settings. The batch can be scheduled if its status is Balanced. A batch with a Scheduled status can be modified, but it can be saved only if its debit and credit totals are equal.

The status of a batch will change to Void if the batch is deleted from the schedule. A scheduled batch can be fully deleted only if the schedule was never executed and no ordinary general ledger preferences batches were generated in accordance with it.

Unposted A batch with the Unposted status is a balanced batch that was released but not yet posted (used to update general ledger preferences account balances). You cannot edit or delete such a batch.
Posted The Posted status indicates that the transactions of the batch were posted or were used for updating appropriate general ledger preferences account balances. A posted batch cannot be modified or deleted; it is available only for viewing.
Void The Void status indicates that this batch was cancelled, for example, because it was removed from the schedule before the schedule was completed. However, the voided batch cannot be deleted because it is needed for auditing.
## Control total amount of a batch In Visma Net, each batch has a control total, which is specified in the [Journal transactions (GL301000)](/visma-net-erp/help/general-ledger/general-ledger-windows/journal-transactions-gl301000/) window. For a balanced batch, the control total is equal to both its credit total and its debit total. If these totals differ, the batch cannot be released and posted. You use the **Validate batch control totals on entry** check box in the [General ledger preferences (GL102000)](/visma-net-erp/help/general-ledger/general-ledger-windows/general-ledger-preferences-gl102000/) window to enforce validation of batch control totals as follows: + If this check box is selected, each time you add a transaction (by using the [Journal transactions (GL301000)](/visma-net-erp/help/general-ledger/general-ledger-windows/journal-transactions-gl301000/) window) during initial entry of the batch or later editing, the system updates the **Total credits** and **Total debits** and highlights in red the **Control total**. To save the batch with the **Balanced** status, in the **Control total** field, you must enter the control total amount, which is equal to both total credits and total debits. If you cannot make the batch balanced, change its status to **On hold** by selecting the **Hold** check box and clicking **Save**. An **On hold** batch doesn't need to have valid control totals. + If the **Validate batch control totals on entry** check box is cleared, the **Control total** field isn't shown in the [Journal transactions (GL301000)](/visma-net-erp/help/general-ledger/general-ledger-windows/journal-transactions-gl301000/) window. The system checks the batch totals only when you click **Save**, and if the totals are not equal, an error message appears. Unbalanced batches may be saved as drafts with the **On hold** status. ## Batch processing Once the batch status changes to **Balanced**, the batch may be processed further. You can apply the **Release** action in the [Journal transactions (GL301000)](/visma-net-erp/help/general-ledger/general-ledger-windows/journal-transactions-gl301000/) window after you have finished editing the batch, or you can use the [Release transactions (GL501000)](/visma-net-erp/help/general-ledger/general-ledger-windows/release-transactions-gl501000/) window. After you release the batch, it gets the **Unposted** status and cannot be modified. You can instead configure the system to immediately post batches on their release. To do this, use the **Automatically post on release** option, located in the [General ledger preferences (GL102000)](/visma-net-erp/help/general-ledger/general-ledger-windows/general-ledger-preferences-gl102000/) window. You can post released batches (those with the **Unposted** status) only by using the [Post transactions (GL502000)](/visma-net-erp/help/general-ledger/general-ledger-windows/post-transactions-gl502000/) window. You can post all the batches listed or only those you select. The system initiates the posting process in the background so that you can continue with data entry or other tasks. When the system has finished posting the batches to general ledger, it automatically updates the status of the batches to **Posted**. ## Batch audit trail To facilitate batch tracking, you can attach scanned images of supporting documents to a batch and to each line of the batch. Once transactions are posted to the database, you cannot delete them because they're needed for auditing purposes. The only way to correct errors while keeping a full audit trail is to create another batch that contains reversing or adjusting journal entries for the original batch. + [Create a batch](/visma-net-erp/help/general-ledger/manage-transactions/general-ledger-batches/create-a-batch/) [Release a batch](/visma-net-erp/help/general-ledger/manage-transactions/general-ledger-batches/release-a-batch/) [Release multiple batches](/visma-net-erp/help/general-ledger/manage-transactions/general-ledger-batches/release-multiple-batches/) [Post batches](/visma-net-erp/help/general-ledger/manage-transactions/general-ledger-batches/post-batches/) [Find and view a particular batch](/visma-net-erp/help/general-ledger/manage-transactions/general-ledger-batches/find-and-view-a-particular-batch/)
Create a batch /visma-net-erp/help/general-ledger/manage-transactions/general-ledger-batches/create-a-batch section 2026-02-19T17:09:06+01:00 # Create a batch 1. Go to the > [Journal transactions (GL301000)](/visma-net-erp/help/general-ledger/general-ledger-windows/journal-transactions-gl301000/) window. 1. Click ![icon-add](/media/visma-net-erp/icon-add.png). 1. In the top part, perform the following steps: 1. In the **Module** field, select **General ledger** because a new batch can be created only for the General ledger workspace. 1. In the **Transaction date** field, specify the transaction date for the batch. All journal transactions that you will add to this batch will have the transaction date specified here. 1. In the **Post period** field, specify the financial period to which the transactions should be posted. 1. Optional: In the **Description** field, enter the brief description of the transaction. 1. In the **Branch** field, specify the branch to which the transactions belong. 1. In the **Ledger** field, specify the ledger to post the transactions. By default, the posting ledger specified for the branch in the [Inter-branch account mapping (GL101010)](/visma-net-erp/help/general-ledger/general-ledger-windows/inter-branch-account-mapping-gl101010/) window is selected in this field. 1. In the **Currency** field, select the currency used for all journal transactions of the batch. By default, the base currency defined for all branches in the [Branches (CS102000)](/visma-net-erp/help/organisation-structure/organisation-structure-windows/branches-cs102000/) window is specified. 1. Optional: Select the **Auto-reversing** check box, if the batch contains the adjusting period-end transactions that should be automatically reversed at the beginning of the next period. 1. In the table toolbar, click ![icon-add](/media/visma-net-erp/icon-add.png) and enter journal entry parameters in the following way: 1. In the **Branch** field, select the branch whose balance will be updated by the journal entry. By default, the branch that you have specified in the top part is specified. 1. In the **Account** field, select the account to be updated by the entry. 1. Optional: In the **Ref. number** column, specify a value that meets your internal requirements. For example: The reference number of the document for which this batch was generated. 1. Optional: In the **Quantity** field, specify the quantity of items associated with the transaction, if relevant. 1. Optional: In the **UoM** field, specify the unit of measure for items associated with the transaction, if relevant. 1. In the **Debit amount** field, specify the debit amount of the journal entry (if any). 1. In the **Credit amount** field, specify the credit amount of the journal entry (if any). > [!NOTE] > A single entry contains either a debit amount or a credit amount. 1. Optional: In the **Transaction description** field, enter the description that will help you or other users identify the journal entry. > [!NOTE] > Perform these steps for each journal entry to be added in the batch. 1. Optional: Attach scanned images of the supporting documents or their electronic versions to this batch. 1. To save the batch with the **On hold** status make sure, that the **Hold** check box is selected. 1. To save the batch with the **Balanced** status, do one of the following: + If the **Control total** field is shown in the window, enter the amount that equals the debit total or credit total. + If the **Control total** field is not displayed in the window, make sure the debit total equals the credit total. 1. Click ![icon-save](/media/visma-net-erp/icon-save.png). Parent topic: Related reference [Journal transactions](/visma-net-erp/help/general-ledger/general-ledger-windows/journal-transactions-gl301000/)

Related pages

Tasks

Release a batch /visma-net-erp/help/general-ledger/manage-transactions/general-ledger-batches/release-a-batch page 2026-02-19T17:09:06+01:00 # Release a batch 1. Go to the [Journal transactions (GL301000)](/visma-net-erp/help/general-ledger/general-ledger-windows/journal-transactions-gl301000/) window. Open the batch that you want to release; see: [Find and view a particular batch](/visma-net-erp/help/general-ledger/manage-transactions/general-ledger-batches/find-and-view-a-particular-batch/) if necessary. 1. Optional: If the batch has the **On hold** status, clear the **Hold** check box and type in the control total if applicable. This changes the status to **Balanced**. 1. Once the batch has a status of **Balanced**, click **Release**. This changes the status of the batch to **Unposted** or **Posted**, depending on whether the **Automatically post on release** check box in the [General ledger preferences (GL102000)](/visma-net-erp/help/general-ledger/general-ledger-windows/general-ledger-preferences-gl102000/) window is selected. Release multiple batches /visma-net-erp/help/general-ledger/manage-transactions/general-ledger-batches/release-multiple-batches page 2026-02-19T17:09:06+01:00 # Release multiple batches 1. Go to the [Release transactions (PM501000)](/visma-net-erp/help/project-accounting/project-accounting-windows/release-transactions-pm501000/) window. Batches with the **Balanced** status are listed here. You can set up a filter to display only specific batches on the list. 1. Do one of the following: + Select the batches for release by selecting the check boxes next to the batches. If you plan to release most of the listed batches, instead select the check box in the column header (to select all check boxes on the page), and clear the check boxes preceding batches you don't want to release. + Click **Release**. + Click **Release all** to release all the listed batches. The release operation changes the status of batches to **Unposted** or **Posted**, depending on whether the **Automatically post on release** check box is selected in the [General ledger preferences (GL102000)](/visma-net-erp/help/general-ledger/general-ledger-windows/general-ledger-preferences-gl102000/) window. Post batches /visma-net-erp/help/general-ledger/manage-transactions/general-ledger-batches/post-batches page 2026-02-19T17:09:06+01:00 # Post batches 1. Go to the [Post transactions (GL502000)](/visma-net-erp/help/general-ledger/general-ledger-windows/post-transactions-gl502000/) window. You can set up a filter to display only specific batches on the list. 1. Do one of the following actions, each of which changes the status of applicable batches to **Posted**: + Select the batches in the list (by selecting the unlabelled check boxes next to the batches) and click **Post**. + Click **Post all**. Find and view a particular batch /visma-net-erp/help/general-ledger/manage-transactions/general-ledger-batches/find-and-view-a-particular-batch section 2026-02-19T17:09:06+01:00 # Find and view a particular batch ## Find a batch by using the [Journal transactions (GL301000)](/visma-net-erp/help/general-ledger/general-ledger-windows/journal-transactions-gl301000/) window 1. Go to the [Journal transactions (GL301000)](/visma-net-erp/help/general-ledger/general-ledger-windows/journal-transactions-gl301000/) window. 1. In the **Batch no.** field, click ![icon-select](/media/visma-net-erp/icon-select.jpg). 1. To locate the batch, do one of the following: + Click the **Batch no.** column heading, or any other column heading, to arrange the items in ascending or descending order of the values. Navigate between pages to locate the specific batch. + Click the column heading for any column where a search may be helpful, and then type a string in the search box at the bottom left of the lookup window. As you type, the system filters the listed batches to display only those containing the text in the selected column. + Create a filter to find the batch by its details. To do this, click the **Add filter** icon in the **Filter** field at the top right of the lookup window, and specify a condition based on the batch details. 1. When you find the batch, double-click anywhere in the row to open that batch and view its information. ## Find a batch by using the [Unreleased transactions summary (GL61150S)](/visma-net-erp/help/general-ledger/general-ledger-reports/unreleased-transactions-summary-gl61150s/) window This window lists **On hold** batches grouped by period. 1. Go to the [Unreleased transactions summary (GL61150S)](/visma-net-erp/help/general-ledger/general-ledger-reports/unreleased-transactions-summary-gl61150s/) window. 1. Select the ledger and a financial period. 1. Click **Run report**. 1. Review the list of batches for the period. If you don not see the batch you are looking for, click **Parameters**, change the selection criteria, and run the report again. 1. To view the details of the batch you were looking for, click the batch number to navigate to the [Journal transactions (GL301000)](/visma-net-erp/help/general-ledger/general-ledger-windows/journal-transactions-gl301000/) window. Post transactions with VAT directly in general ledger /visma-net-erp/help/general-ledger/manage-transactions/general-ledger-batches/post-transactions-with-vat-directly-in-general-ledger section Normally, you can only post VAT from the Customer ledger and the Supplier ledger. 2026-02-19T17:09:06+01:00 # Post transactions with VAT directly in general ledger Normally, you can only post VAT from the Customer ledger and the Supplier ledger. In some cases, posting VAT directly in the General ledger may be necessary. To do this, activate this functionality first and after that you can create a journal transaction with VAT. ## Activating VAT entry from the General ledger 1. Go to the [Enable/disable functionalities (CS100000)](/visma-net-erp/help/common-settings/enable-or-disable-functionalites/enable-disable-functionalities-cs100000/) window. 1. Select **VAT entry from general ledger**. 1. Click ![icon-save](/media/visma-net-erp/icon-save.png). 1. Click **Enable**. ## Posting a journal transaction with VAT 1. Go to the [Journal transactions (GL301000)](/visma-net-erp/help/general-ledger/general-ledger-windows/journal-transactions-gl301000/) window. 1. Select **Create VAT transactions**. 1. Click ![icon-add](/media/visma-net-erp/icon-add.png) to add row. 1. Enter your transaction. Make sure to enter the **VAT code** on the income/expense line and **VAT ID** on the VAT line 1. Click ![icon-save](/media/visma-net-erp/icon-save.png). 1. Click **Release** to process the transaction through to the tax reports. Auto-reversing transactions /visma-net-erp/help/general-ledger/manage-transactions/auto-reversing-transactions section 2026-02-19T17:09:06+01:00 # Auto-reversing transactions About auto-reversing transactions /visma-net-erp/help/general-ledger/manage-transactions/auto-reversing-transactions/about-auto-reversing-transactions page Visma Net makes it easy to close your books at the end of a period. 2026-02-19T17:09:06+01:00 # About auto-reversing transactions Visma Net makes it easy to close your books at the end of a period. Visma Net makes it easy to close your books at the end of a period. To do so, you may need to post some adjusting transactions that should be reversed at the beginning of the next period. For example: At the period-end, the accounts maintained in foreign currencies are revalued in the base currency, and the adjusting entries are posted to the General ledger's unrealised gains and losses accounts. At the beginning of the next period, these entries should be reversed. In Visma Net, the General ledger workspace can process auto-reversing batches, which can be manually marked as such in the [Journal transactions (GL301000)](/visma-net-erp/help/general-ledger/general-ledger-windows/journal-transactions-gl301000/) window. Also, some auto-reversing batches are automatically generated. ## Reversing batches For a batch marked as auto-reversing, the system automatically creates the reversing batch according to the following rules: + All transactions are reversed—that is, a debit entry is reversed as a credit entry and vice versa. + The first day of the next financial period is set as the date of the reversing transactions. Depending on the **Generate reversing entries** option in the [General ledger preferences (GL102000)](/visma-net-erp/help/general-ledger/general-ledger-windows/general-ledger-preferences-gl102000/) window, the system can be configured to generate reversing batches at either of the following times: On post : Each reversing batch is generated once the original batch is posted. On period closing : All reversing batches are generated at once when the process of period closing has been initiated. When you view the batches in the [Journal transactions (GL301000)](/visma-net-erp/help/general-ledger/general-ledger-windows/journal-transactions-gl301000/) window, note that for the reversing batches, the **Reversing entry** check box is selected. Reverse a batch /visma-net-erp/help/general-ledger/manage-transactions/auto-reversing-transactions/reverse-a-batch section 2026-02-19T17:09:06+01:00 # Reverse a batch 1. Go to the [Journal transactions (GL301000)](/visma-net-erp/help/general-ledger/general-ledger-windows/journal-transactions-gl301000/) window. 1. Open the batch you want to reverse; see: [Find and view a particular batch](/visma-net-erp/help/general-ledger/manage-transactions/general-ledger-batches/find-and-view-a-particular-batch/) if necessary. 1. In the toolbar, on the **Actions** menu, select **Reverse batch**. This creates and opens a new batch in which credit entries become debit entries and debit entries become credit entries. 1. In the **Orig. batch number** field, note the reference number of the batch that was reversed. 1. Notice that the **Reversing entry** check box is selected, which indicates that this is a reversing batch. 1. If the **Control total** field is shown, enter the control total. 1. Make sure the **Hold** check box is cleared. 1. Click ![icon-save](/media/visma-net-erp/icon-save.png). **Parent topic:** [About auto-reversing transactions](/visma-net-erp/help/general-ledger/manage-transactions/auto-reversing-transactions/about-auto-reversing-transactions/) Recurring journal transactions /visma-net-erp/help/general-ledger/manage-transactions/recurring-journal-transactions section 2026-02-19T17:09:06+01:00 # Recurring journal transactions About recurring journal transactions /visma-net-erp/help/general-ledger/manage-transactions/recurring-journal-transactions/about-recurring-journal-transactions page Some General ledger transactions, such as loan payments, depreciation-related transactions, repeat regularly. 2026-02-19T17:09:06+01:00 # About recurring journal transactions Some General ledger transactions, such as loan payments, depreciation-related transactions, repeat regularly. Some General ledger transactions, such as loan payments, depreciation-related transactions, repeat regularly. To automate the entering of recurring transactions, you can create schedules for them in the General ledger workspace. ## Create schedules You create schedules by using the [Recurring transactions (GL203500)](/visma-net-erp/help/general-ledger/general-ledger-windows/recurring-transactions-gl203500/) window. To a schedule, you can add general ledger batches immediately (if all the required batches are already created) or later. The batches of the **Normal** type and the **Balanced** status can be scheduled only. Once a batch is assigned to a schedule, its status changes to **Scheduled**. A schedule defines how many times and how often specific General ledger transactions should be created. When creating a schedule, you can either specify a maximum number of times the schedule should be repeated, or set up an unlimited schedule executions by selecting the **No execution limit** option. For a schedule, you can select from multiple frequency options: Daily : The batches should be generated daily or every **x** days. Weekly : The batches should be generated once a week or every **x** weeks. Monthly : The batches should be generated once per month or every **x** months. By financial period : The batches should be generated only once per financial period or every **x** financial periods. If you need to schedule only one batch, in the [Journal transactions (GL301000)](/visma-net-erp/help/general-ledger/general-ledger-windows/journal-transactions-gl301000/) window, click **Add to schedule** in the window toolbar to create a new schedule for this batch. ## Attach relevant documents To make tracking of batches easier for users and to facilitate auditing, you can attach to each schedule the scanned documents or electronic versions of the documents that are the basis for the schedule you have created. To attach a file to the schedule, in the [Recurring transactions (GL203500)](/visma-net-erp/help/general-ledger/general-ledger-windows/recurring-transactions-gl203500/) window, perform these steps: 1. In the **Schedule** field, select the schedule by its ID. 1. In the window title bar, click **Files**. This opens the **Files dialog box**. 1. In the dialog box, click **Add new record** in the table title bar. This brings up the **Upload file dialog box**. 1. In the dialog box, click **Browse** to locate the file and then click **Upload** to import the file and close the dialog box. If multiple non-related batches are assigned to the same schedule, on the **Batch list** tab of the window, for each batch in the table, click the paper clip (at the beginning of the row) to attach a file or multiple files explaining why this batch is generated periodically. ## Run schedules To generate batches in accordance with the schedule, you run the schedule periodically by using the [Generate recurring transactions (GL504000)](/visma-net-erp/help/general-ledger/general-ledger-windows/generate-recurring-transactions-gl504000/) window. When you run a schedule, the system uses a template batch to generate similar batches. The batches generated by a schedule can differ from the template as follows: Date : The date of each batch is determined by the schedule you have configured. Reference number : A new reference number is generated for each batch in accordance with the numbering series specified in the [General ledger preferences (GL102000)](/visma-net-erp/help/general-ledger/general-ledger-windows/general-ledger-preferences-gl102000/) window. Currency rate : If a currency of a batch differs from the base currency set in the system, the system uses for conversion the currency exchange rate effective on the date of the batch creation. No matter how many times you run the schedule, batches will be generated only as required by the schedule. The system determines whether it should generate the batches depending on the current date, the schedule's start and expiration dates, the schedule type, and the date when the batches were last generated. After required batches have been generated, the system updates the **Last executed on** value. Thus, no batches will be generated ahead of time, but you can generate missing batches for past due dates by running the [Generate recurring transactions (GL504000)](/visma-net-erp/help/general-ledger/general-ledger-windows/generate-recurring-transactions-gl504000/) window for each batch that is due. For example: Suppose that you have scheduled a particular batch to be performed weekly on each Tuesday, with no execution limit. If you run the schedule every week on Wednesday, one batch will be generated each time. If you run this schedule every day, the batches will be generated only on Tuesdays. If you want to run this schedule once in a month, on the last Wednesday, you should run it four times to generate four batches. ## Further processing Batches generated as a result of running a schedule appear in the list of batches in the [Journal transactions (GL301000)](/visma-net-erp/help/general-ledger/general-ledger-windows/journal-transactions-gl301000/) window with the **Balanced** status. They can be released or posted as any other batches can. You can change the transaction amounts, if needed. When necessary corrections are made, a batch can be saved only if its status remains **Balanced**.

Related pages

Tasks

Generate recurring transactions /visma-net-erp/help/general-ledger/manage-transactions/recurring-journal-transactions/generate-recurring-transactions page 2026-02-19T17:09:06+01:00 # Generate recurring transactions ## Generate a recurring transaction 1. Go to the [Generate recurring transactions (GL504000)](/visma-net-erp/help/general-ledger/general-ledger-windows/generate-recurring-transactions-gl504000/) window. 1. In the **Execution date** field, specify the date that the system will use to filter the schedules to be loaded to the table. Those schedules whose **Next execution** date is earlier than or equal to the date specified in this field will be loaded. By default, the current business date is selected. 1. Specify the condition that the system will use to stop schedule executions by selecting one of the following option buttons: + **Stop on execution date**: the system stops running schedules on the date that you specify in the **Execution date** field. + **Stop after number of executions**: the system stops running schedules when the specified number of schedule executions have been performed. If you select this option button, specify the required number in the adjacent box. 1. In the window toolbar, click **Run** or **Run all** to process selected schedules or all listed schedules respectively. ## View the generated batches 1. Go to the [Generate recurring transactions (GL504000)](/visma-net-erp/help/general-ledger/general-ledger-windows/generate-recurring-transactions-gl504000/) window. 1. In the list of schedules, open the required schedule by clicking the link in the **Schedule ID** column. The **Recurring transactions** window as a dialog box with the selected schedule opens. 1. On the **Generated documents** tab, click the number of the batch in the **Batch number** column. 1. In the [Journal transactions (GL301000)](/visma-net-erp/help/general-ledger/general-ledger-windows/journal-transactions-gl301000/) window that opens, view the details of the batch. Work with recurring transactions /visma-net-erp/help/general-ledger/manage-transactions/recurring-journal-transactions/work-with-recurring-transactions section Here you create and maintain schedules for recurring invoices. 2026-02-19T17:09:06+01:00 # Work with recurring transactions Here you create and maintain schedules for recurring invoices. You can also view the details of active and completed schedules. ## How to create a schedule for recurring invoices 1. Go to the [Recurring transactions (GL203500)](/visma-net-erp/help/general-ledger/general-ledger-windows/recurring-transactions-gl203500/) window. 1. Click ![icon-add](/media/visma-net-erp/icon-add.png) to add a new record. The **Schedule ID** will be generated automatically upon saving. Use the **Active** check box to activate or deactivate the schedule. 1. Select a **Start date** for the schedule. 1. Continue to fill in the other fields (optional): **Expiration date**: Only active if the **Never expires** check box is deselected. **Execution limit (times)**: The maximum number of times the schedule can be executed. Only active if the **No limit** check box is deselected. **Description**: Enter a description for the schedule. The **Next execution** field is a read-only field that will display the next execution date for the schedule. 1. In the **Schedule type** section you decide how often you want to generate invoices. Select the schedule type and enter the parameters in the corresponding section on the right hand side. 1. In the **Document list** tab click ![icon-add](/media/visma-net-erp/icon-add.png) to assign one or more invoices to the schedule. 1. In the **Reference no.** column, click to activate the field and click ![icon-select](/media/visma-net-erp/icon-select.jpg) to select an invoice by its reference number. 1. Click ![icon-save](/media/visma-net-erp/icon-save.png). In the **Generated documents** tab you can see a list of the documents generated as a result of running this schedule. ## How to delete or edit a schedule 1. Click ![icon-select](/media/visma-net-erp/icon-select.jpg) to select a **Schedule ID** to edit or delete. 1. If you want to edit the schedule, make your changes in the fields and check boxes. 1. Click ![icon-save](/media/visma-net-erp/icon-save.png) to save your changes. 1. Click ![icon-delete](/media/visma-net-erp/icon-delete.png) if you want to delete the selected schedule and click **OK** to confirm. **Tip!** If you want to run your schedule manually, click **Run now** and the schedule will run immediately. Schedule a recurring batch /visma-net-erp/help/general-ledger/manage-transactions/recurring-journal-transactions/schedule-a-recurring-batch section If specific journal transactions must be entered periodically, you can automate this task by creating a schedule and assigning a batch or multiple batches to it. 2026-02-19T17:09:06+01:00 # Schedule a recurring batch If specific journal transactions must be entered periodically, you can automate this task by creating a schedule and assigning a batch or multiple batches to it. If specific journal transactions must be entered periodically, you can automate this task by creating a schedule and assigning a batch or multiple batches to it. When you define the schedule, you specify how often and how many times the batches should be generated. For more information on schedules, see: [About recurring journal transactions](/visma-net-erp/help/general-ledger/manage-transactions/recurring-journal-transactions/about-recurring-journal-transactions/). ## Before you proceed Create a batch (or multiple batches if they should be generated according to the same schedule) by using the [Journal transactions (GL301000)](/visma-net-erp/help/general-ledger/general-ledger-windows/journal-transactions-gl301000/) window. Save each batch with the **Balanced** status. Do not release. > [!NOTE] > If you want to generate new batches that are similar to a posted batch, copy and paste this posted batch to a new batch and make necessary edits; save with the **Balanced** status. ## Create a schedule 1. Go to the [Recurring transactions (GL203500)](/visma-net-erp/help/general-ledger/general-ledger-windows/recurring-transactions-gl203500/) window. 1. In the **Description** field, add a description of the schedule. 1. In the **Start date** field, select the start date for the schedule. By default, the current date is selected. 1. Place limitations on the schedule execution in one of the following ways: + Enter the maximum number of times it should be executed in the **Execution limit** field, or select the **No limit** check box. + In **Expiration date** field, enter the date when the schedule expires, or select the **Never expires** check box. 1. Specify how often the batches should be generated: + To generate the batches daily or every **x** days, do the following: 1. In the **Schedule type** section, select **Daily**. 1. In the **Every day(s)** field of the **Daily** section, type an integer to specify the number of days between successive batches. + To generate the batches weekly or every **x** weeks, do the following: 1. In the **Schedule type** section, select **Weekly**. 1. In the **Every week(s)** field of the **Weekly** section, type an integer to specify the number of weeks between successive batches. 1. Select the days of the week on which the batches should be generated. + To generate the batches monthly or every x months, do the following: 1. In the **Schedule type** section, select **Monthly**. 1. In the **Every month(s)** field of the **Monthly** section, enter an integer to specify the number of months between successive batches. 1. Select when the batches should be generated: either the day of the month, or the week of the month and day of the week. + To generate the invoice every **x** financial periods, do the following: 1. In the **Schedule type** section, select **By financial period**. 1. In the **Every period(s)** field, type an integer to specify the frequency of invoice generation by financial period. 1. Specify whether the invoice should be generated on the first day of the financial period, the last day of the financial period, or a specific day of the period (the day can be selected). 1. Make sure the **Active** check box is selected for the schedule. 1. Click ![icon-save](/media/visma-net-erp/icon-save.png). In the **Schedule ID** field, notice the unique ID of the schedule, which the system generated in accordance with the numbering series assigned to schedules in the [General ledger preferences (GL102000)](/visma-net-erp/help/general-ledger/general-ledger-windows/general-ledger-preferences-gl102000/) window. 1. Optional: For user reference, attach a scanned copy or electronic version of the document on which this schedule is based. For this, drag the file from the folder on your computer and drop it to the top part. ## Add batches to the schedule 1. On the **Batch list** tab, click **Add row**. 1. In the **Module** column, select **General ledger** from the list of system workspaces. 1. In the **Batch number** column, select the batch by its number. 1. Optional: To attach an electronic version of the related document or its scanned image to the scheduled batch, click a staple icon, select and upload the document. 1. Repeat Steps 1 through 4 for each batch you want to add. 1. Click ![icon-save](/media/visma-net-erp/icon-save.png). Parent topic: [About recurring journal transactions](/visma-net-erp/help/general-ledger/manage-transactions/recurring-journal-transactions/about-recurring-journal-transactions/) Reclassify and split general ledger transactions /visma-net-erp/help/general-ledger/manage-transactions/reclassify-and-split-general-ledger-transactions section 2026-02-19T17:09:06+01:00 # Reclassify and split general ledger transactions About reclassifying general ledger transactions /visma-net-erp/help/general-ledger/manage-transactions/reclassify-and-split-general-ledger-transactions/about-reclassifying-general-ledger-transactions page In Visma Net, the reclassification of a general ledger transaction means the creation of a correcting transaction to move an amount from one general ledger account to another general ledger account, from one subaccount to another subaccount, or from one company branch to another one. 2026-02-19T17:09:06+01:00 # About reclassifying general ledger transactions In Visma Net, the reclassification of a general ledger transaction means the creation of a correcting transaction to move an amount from one general ledger account to another general ledger account, from one subaccount to another subaccount, or from one company branch to another one. In Visma Net, the reclassification of a general ledger transaction means the creation of a correcting transaction to move an amount from one general ledger account to another general ledger account, from one subaccount to another subaccount, or from one company branch to another one. You can reclassify a general ledger transaction if an amount has been posted to the wrong general ledger account, subaccount, or branch by mistake. As a result of the reclassification process, the system generates a new transaction of the **Reclassification** type based on the original general ledger transaction. The **Reclassification** transaction moves the amount from the wrong general ledger account, subaccount, or branch to the required one. The following section provides an example of the reclassification process and illustrates the corresponding general ledger transactions. ## Understanding the reclassification process Suppose that you classify all your expenses by department by using a dedicated subaccount segment for each department code. By mistake, you have specified the wrong subaccount in the supplier ledger invoice, so that an amount has been posted to the expenses of the wrong department; now you need to reclassify the wrong journal entry by creating a correcting transaction, so that amount will be moved to the subaccount of the correct department. The following table shows the journal entries of the original general ledger transaction of the **Normal** type. |Account|Subaccount|Debit|Credit| |---|---|---|---| |Supplier ledger account|00-00-000|00.00|Amount| |Expense account|00-00-OPS|Amount|00.00| The following table shows the journal entries of the correcting general ledger transaction of the **Reclassification** type. |Account|Subaccount|Debit|Credit| |---|---|---|---| |Expense account|00-00-OPS|00.00|Amount| |Expense account|00-00-FIN|Amount|00.00| You can find and view transactions of the **Reclassification** type in the [Journal transactions (GL301000)](/visma-net-erp/help/general-ledger/general-ledger-windows/journal-transactions-gl301000/) window. In this window, in the **Orig. batch no.** column of the table, the reclassified journal entries contain the links to the original general ledger transactions (that is, to the batches generated for the transactions). In Visma Net, a batch is generated for each transaction created in the system. A batch can contain one transaction or multiple transactions, and each transaction consists of at least two journal entries (a debit entry and a credit entry). Through the reclassification process, you can reclassify a wrong journal entry or move an amount from the wrong account, subaccount, or branch to the correct one. The reclassification process generates the correcting transaction, which includes two journal entries. ## Understanding the splitting process The split of a general ledger transaction means the creation of a correcting transaction to move a part of the amount (of the original transaction) from one general ledger account to another general ledger account, from one subaccount to another subaccount, or from one company branch to another branch. You can split the transaction in any of these regards. As a result of the reclassification or split process, the system generates a new transaction of the Reclassification type based on the original general ledger transaction. The Reclassification transaction moves the amount or a part of the amount from the wrong general ledger account, subaccount, or branch (or more than one of these) to the required one (or ones). Related reference [Account details](/visma-net-erp/help/general-ledger/general-ledger-windows/account-details-gl404000/) [Reclassification history](/visma-net-erp/help/general-ledger/general-ledger-windows/reclassification-history-gl405000/) [Reclassify transactions](/visma-net-erp/help/general-ledger/general-ledger-windows/reclassify-transactions-gl506000/)

Related pages

Concepts

Tasks

Initiate reclassification and split /visma-net-erp/help/general-ledger/manage-transactions/reclassify-and-split-general-ledger-transactions/initiate-reclassification-and-split page You can open the Reclassify transactions (GL506000) window in one of the following ways: 2026-02-19T17:09:06+01:00 # Initiate reclassification and split You can open the Reclassify transactions (GL506000) window in one of the following ways: For more information: [Reclassify transactions (GL506000)](/visma-net-erp/help/general-ledger/general-ledger-windows/reclassify-transactions-gl506000/). + By using the [Account details (GL404000)](/visma-net-erp/help/general-ledger/general-ledger-windows/account-details-gl404000/) window. In this window, you select a general ledger account and, in the list of transactions posted to this account, the transactions that you need to reclassify. You then click **Reclassify** on the window toolbar. The [Reclassify transactions (GL506000)](/visma-net-erp/help/general-ledger/general-ledger-windows/reclassify-transactions-gl506000/) window opens with the selected transactions displayed in the table. (To reclassify all transactions posted to the selected account, you can instead click **Reclassify all** on the window toolbar.) + By using the [Journal transactions (GL301000)](/visma-net-erp/help/general-ledger/general-ledger-windows/journal-transactions-gl301000/) window. In this window, you select a required **released** general ledger batch, and in the **Actions** menu in the window toolbar, click **Reclassify**. The [Reclassify transactions (GL506000)](/visma-net-erp/help/general-ledger/general-ledger-windows/reclassify-transactions-gl506000/) window opens, displaying the transactions included in the selected general ledger batch. + Go to the [Reclassify transactions (GL506000)](/visma-net-erp/help/general-ledger/general-ledger-windows/reclassify-transactions-gl506000/) window. The [Reclassify transactions (GL506000)](/visma-net-erp/help/general-ledger/general-ledger-windows/reclassify-transactions-gl506000/) window opens with no entries in the list. To load the entries to be reclassified, you click **Load** on the window toolbar. In the **Load transactions dialog box** that opens, you specify the parameters of the transactions to be uploaded to the window. Once the transactions are uploaded, you can modify the details of each required transaction or of multiple transactions simultaneously. (For details, see the next section of this topic.) + By using the [Reclassification history (GL405000)](/visma-net-erp/help/general-ledger/general-ledger-windows/reclassification-history-gl405000/) window. In this window, you can select the last transaction of the reclassification chain, and then click **Reclassify** on the window toolbar, which opens the [Reclassify transactions (GL506000)](/visma-net-erp/help/general-ledger/general-ledger-windows/reclassify-transactions-gl506000/) window. Transactions with a control account specified in any rows cannot be reclassified, so these transactions are not transferred to the [Reclassify transactions (GL506000)](/visma-net-erp/help/general-ledger/general-ledger-windows/reclassify-transactions-gl506000/) window. **Parent topic:** [About reclassifying general ledger transactions](/visma-net-erp/help/general-ledger/manage-transactions/reclassify-and-split-general-ledger-transactions/about-reclassifying-general-ledger-transactions/)

Related pages

Concepts

Tasks

Process reclassification /visma-net-erp/help/general-ledger/manage-transactions/reclassify-and-split-general-ledger-transactions/process-reclassification page In the Reclassify transactions (GL506000) window, before you perform the reclassification process, you need to specify new details for each journal entry that you need to reclassify. 2026-02-19T17:09:06+01:00 # Process reclassification In the Reclassify transactions (GL506000) window, before you perform the reclassification process, you need to specify new details for each journal entry that you need to reclassify. For more information: [Reclassify transactions (GL506000)](/visma-net-erp/help/general-ledger/general-ledger-windows/reclassify-transactions-gl506000/). In the [Reclassify transactions (GL506000)](/visma-net-erp/help/general-ledger/general-ledger-windows/reclassify-transactions-gl506000/) window, before you perform the reclassification process, you need to specify new details for each journal entry that you need to reclassify. You can change an account, subaccount, and branch. While reclassifying a transaction, you can also edit the transaction date and the description of the reclassification transaction. If you edit the date, the new date has to be in the range of the financial period of the original transaction. You can change required parameters in each needed row manually, or perform mass changing of parameters in multiple rows. These options are described in details in the next sections of this topic. ## Modify selected transactions manually To change the required parameters manually, in each needed row, you modify any of the following boxes: To account : The transaction amount will be moved from the originally specified general ledger account ( **Account** ) to the account specified in this field. To subaccount : The transaction amount will be moved from the originally specified subaccount ( **Subaccount** ) to the subaccount specified in this field. This field is available only if the **Subaccounts** functionality is enabled in the [Enable/disable functionalities (CS100000)](/visma-net-erp/help/common-settings/enable-or-disable-functionalites/enable-disable-functionalities-cs100000/) window. To branch : The transaction will be moved to the general ledger account or subaccount of the branch specified in this field. This field is available only if the **Multi-branch support** functionality is enabled in the [Enable/disable functionalities (CS100000)](/visma-net-erp/help/common-settings/enable-or-disable-functionalites/enable-disable-functionalities-cs100000/) window. By default, these fields contain the values of the original journal entry. Once you have changed any of the default values, the entry becomes available for reclassification. To edit the date and description of a transaction, you need to enter new parameters in the **New trans. date** and **New transaction description** fields, respectively. ## Modify a group of transactions To perform mass-changing of parameters in multiple rows, on the window toolbar of the [Reclassify transactions (GL506000)](/visma-net-erp/help/general-ledger/general-ledger-windows/reclassify-transactions-gl506000/) window, click **Replace**. In the **Find and replace dialog box** that opens, specify the original and replacement transaction parameters. Then click **Replace** to close the dialog box and replace the parameters in the needed rows. To run the reclassification process, click **Process** in the window toolbar. Parent topic: [About reclassifying general ledger transactions](/visma-net-erp/help/general-ledger/manage-transactions/reclassify-and-split-general-ledger-transactions/about-reclassifying-general-ledger-transactions/) Related reference [Reclassification history](/visma-net-erp/help/general-ledger/general-ledger-windows/reclassification-history-gl405000/) [Reclassify transactions](/visma-net-erp/help/general-ledger/general-ledger-windows/reclassify-transactions-gl506000/)

Related pages

Concepts

Tasks

Process splitting /visma-net-erp/help/general-ledger/manage-transactions/reclassify-and-split-general-ledger-transactions/process-splitting page In the Reclassify transactions (GL506000) window, to process splitting of a transaction, you need to add new lines that represent the journal entries to which a part of the original journal entry amount will be split. 2026-02-19T17:09:06+01:00 # Process splitting In the Reclassify transactions (GL506000) window, to process splitting of a transaction, you need to add new lines that represent the journal entries to which a part of the original journal entry amount will be split. For more information: [Reclassify transactions (GL506000)](/visma-net-erp/help/general-ledger/general-ledger-windows/reclassify-transactions-gl506000/). A part of the amount can be transferred to another account, subaccount, or branch (or more than one of these). You first click the journal entry to be split and then click **Split** in the window toolbar. The system adds a new entry under the original one. The original entry has the icon, and each new line added during the split process has the icon. The original entry and each new entry are highlighted in bold during the process of splitting the transaction. Multiple new entries can be added to split the original entry. In each new row and in the original one, you modify the values in any of the following columns: + To account: The transaction amount will be moved from the originally specified general ledger account (Account) to the account you specify in this column. + To subaccount: The transaction amount will be moved from the originally specified subaccount (Subaccount) to the subaccount you specify in this column. + This column is available only if the **Subaccounts** functionality is enabled in the [Enable/disable functionalities (CS100000)](/visma-net-erp/help/common-settings/enable-or-disable-functionalites/enable-disable-functionalities-cs100000/) window. + To branch: The transaction amount will be moved from the originally specified branch to the general ledger account or subaccount of the branch you specify in this column. This column is available only if the **Multi-branch support** functionality is enabled in the [Enable/disable functionalities (CS100000)](/visma-net-erp/help/common-settings/enable-or-disable-functionalites/enable-disable-functionalities-cs100000/) window. By default, these columns contain the values of the original journal entry. For new lines of the splitting group, these columns contain values of the original journal entry even if you have changed any of these values of the original entry. For each new entry, in the **New amount** column, you specify the amount to be transferred from the original entry to a new one. For the original entry, in this column, the system calculates the remaining amount based on the new amounts of new entries. The total amount of new entries cannot be more than the amount of the original entry. Negative values can be specified in the **New amount** column for the new entries. The negative amounts are highlighted in red and increase the amount of the original entry. To edit the date and description of a transaction, you need to enter new parameters in the **New tran. date** and **New transaction description** fields, respectively. If you edit the date, the new date has to be within the financial period of the original transaction. The transaction is ready for splitting if the check box is selected in the **Selected** column for the original entry and all the related new entries. The systems selects this check box for each new entry when you have changed a value in the **To account**, **To subaccount**, or **To branch** column and have specified the amount to be moved to the new entry in the **New amount** columns. The systems selects this check box for the original entry when you have changed a value in the **To account**, **To subaccount**, or **To branch** column or the amount has been adjusted according to the changes made for amounts of the new lines. Split general ledger transactions /visma-net-erp/help/general-ledger/manage-transactions/reclassify-and-split-general-ledger-transactions/split-general-ledger-transactions page 2026-02-19T17:09:06+01:00 # Split general ledger transactions 1. Open the [Reclassify transactions (GL506000)](/visma-net-erp/help/general-ledger/general-ledger-windows/reclassify-transactions-gl506000/) window: 1. In the window toolbar, click **Load**. 1. In the **Load transactions** dialog box, which the system has opened, specify the needed selection criteria to help you find the required general ledger transactions, and click **Load** (to add new transactions meeting the specified criteria to the list of existing transactions, if any) or **Reload** (to remove any existing transactions listed in the window and load new transactions that match the specified criteria) to upload these transactions to the window. 1. Split an amount of each necessary journal entry by doing the following: 1. In the table, click the journal entry to be split. 1. In the window toolbar, click **Split**. 1. In the new line, in the **To account**, **To subaccount**, and **To branch** column, specify the account, subaccount (if applicable), and branch (if applicable), respectively, to which the amount will be transferred. 1. In the **New amount** column, specify the amount that will be transferred from the original journal entry to the new one. 1. If an amount of the original journal entry has to be split to one more line, repeat the three previous substeps. 1. Click **Process** in the window toolbar to initiate the process of splitting the transaction. Once the process has completed successfully, the **Reclass. batch number** column appears with the number of the corresponding split batch. You can now release the split batch in the [Release transactions (GL501000)](/visma-net-erp/help/general-ledger/general-ledger-windows/release-transactions-gl501000/) window. You can also reclassify the original entry. The following parameters can be reclassified: the account (To account), the subaccount (To subaccount), and the branch (To branch). For the original line, in the **New amount** column, the system displays the remaining amount of the entry that can be split. For each new line (that is added when you click **Split** ), in the **New amount** column, you specify the amount to be transferred from the original entry to a new one. For the new entries, both positive and negative values can be specified in this column. Positive amounts will decrease the amount of the original entry. Negative amounts, which are highlighted in red, will increase the amount of the original entry. While splitting a journal entry, you can also edit the date and description of the transactions ( **New tran. date** and **New transaction description** ). If you edit the date, the new date has to be within the financial period of the original transaction. In the same reclassification batch, the system includes journal entries that have the same transaction period and currency specified. A separate reclassification batch is generated for each journal entry that has a different transaction period or currency. The batch will be released automatically if the **Automatically release reclassification batches** check box is selected in the [General ledger preferences (GL102000)](/visma-net-erp/help/general-ledger/general-ledger-windows/general-ledger-preferences-gl102000/) window. About viewing and managing reclassification transactions /visma-net-erp/help/general-ledger/manage-transactions/reclassify-and-split-general-ledger-transactions/about-viewing-and-managing-reclassification-transactions page In the Account details (GL404000) window, you can view the list of transactions posted to a selected general ledger account within the specified period. 2026-02-19T17:09:06+01:00 # About viewing and managing reclassification transactions In the Account details (GL404000) window, you can view the list of transactions posted to a selected general ledger account within the specified period. For more information: [Account details (GL404000)](/visma-net-erp/help/general-ledger/general-ledger-windows/account-details-gl404000/). In the [Account details (GL404000)](/visma-net-erp/help/general-ledger/general-ledger-windows/account-details-gl404000/) window, you can view the list of transactions posted to a selected general ledger account within the specified period. By default, the system does not show the entries that were reclassified. To include in the list of entries the journal entries that have been reclassified, select the **Include reclassified** check box in the top part. In the **Reclass. batch number** column, each of the reclassified entries has a link to the appropriate **Reclassification** transaction. You can also view a list of transactions that includes the reclassified journal entries by preparing the transactions for account or transactions for period report with the **Include reclassified** check box selected. Read more in [About Transactions for account](/visma-net-erp/help/general-ledger/general-ledger-reports/transactions-for-account-gl633500/). ## Editing 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)](/visma-net-erp/help/general-ledger/general-ledger-windows/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)](/visma-net-erp/help/general-ledger/general-ledger-windows/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)](/visma-net-erp/help/general-ledger/general-ledger-windows/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. ## Reversing a reclassification batch You can reverse the general ledger transactions that were generated by the reclassification process. To reverse these transactions, in the [Journal transactions (GL301000)](/visma-net-erp/help/general-ledger/general-ledger-windows/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)](/visma-net-erp/help/general-ledger/general-ledger-windows/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. ## Viewing the history of reclassification transactions 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)](/visma-net-erp/help/general-ledger/general-ledger-windows/reclassification-history-gl405000/) window. You can open this window by clicking the **Reclassification history** button in the [Account details (GL404000)](/visma-net-erp/help/general-ledger/general-ledger-windows/account-details-gl404000/) window for the selected transaction (if it has been reclassified), or in the [Journal transactions (GL301000)](/visma-net-erp/help/general-ledger/general-ledger-windows/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)](/visma-net-erp/help/general-ledger/general-ledger-windows/reclassification-history-gl405000/) window by clicking **Reclassify** in the window toolbar. ## Knowing which transactions cannot be reclassified 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)](/visma-net-erp/help/general-ledger/general-ledger-windows/import-consolidation-data-gl509000/) window. For details, see: [General ledger consolidation - overview](/visma-net-erp/help/general-ledger/manage-consolidations/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)](/visma-net-erp/help/general-ledger/general-ledger-windows/run-allocations-gl504500/) window. For details, see: [About allocation rules](/visma-net-erp/help/general-ledger/manage-allocations/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. > [!NOTE] > You can reclassify the general ledger transactions in which the non-project code is specified. Parent topic: [About reclassifying general ledger transactions](/visma-net-erp/help/general-ledger/manage-transactions/reclassify-and-split-general-ledger-transactions/about-reclassifying-general-ledger-transactions/)

Related pages

Concepts

Tasks

Reclassify general ledger transactions /visma-net-erp/help/general-ledger/manage-transactions/reclassify-and-split-general-ledger-transactions/reclassify-general-ledger-transactions page You can begin working with the Reclassify transactions (GL506000) window in the following ways: 2026-02-19T17:09:06+01:00 # Reclassify general ledger transactions You can begin working with the Reclassify transactions (GL506000) window in the following ways: For more information: [Reclassify transactions (GL506000)](/visma-net-erp/help/general-ledger/general-ledger-windows/reclassify-transactions-gl506000/). + By using the [Account details (GL404000)](/visma-net-erp/help/general-ledger/general-ledger-windows/account-details-gl404000/) window, in which you select transactions to be reclassified and click **Reclassify** (or **Reclassify all** ) in the window toolbar. + By using the [Journal transactions (GL301000)](/visma-net-erp/help/general-ledger/general-ledger-windows/journal-transactions-gl301000/) window, in which you select a required general ledger batch and then click **Reclassify** in the **Actions** menu in the window toolbar. + By navigating to it directly. 1. If the system has brought up the [Reclassify transactions (GL506000)](/visma-net-erp/help/general-ledger/general-ledger-windows/reclassify-transactions-gl506000/) window via the [Account details (GL404000)](/visma-net-erp/help/general-ledger/general-ledger-windows/account-details-gl404000/) window, or the [Journal transactions (GL301000)](/visma-net-erp/help/general-ledger/general-ledger-windows/journal-transactions-gl301000/) window and transactions are listed in the table, skip Steps 2 and 3 and proceed to Step 4. 1. Click **Load** in the window toolbar. 1. In the **Load transactions dialog box** that opens, specify the needed selection parameters to help you find the required general ledger transactions, and click **Load** or **Reload** to upload them to the window. When you click **Load**, new transactions will be added to the list of existing transactions (if any); when you click **Reload**, new transactions will overwrite any transactions listed on the window. 1. Reclassify transactions in one of the following ways: 1. Enter new parameters for multiple transactions at once by clicking **Replace** on the window toolbar and specifying new parameters in the **Find and replace dialog box** that opens. In the **Find** section, specify the original parameters of the transactions that should be reclassified; in the **Replace with** section, specify reclassification parameters. Click **Replace**. 1. Enter new parameters for one transaction or multiple selected transactions manually in each required row. The following parameters can be reclassified: the account ( **To account** ), the subaccount ( **To subaccount** ), or the branch ( **To branch** ). While reclassifying a journal entry, you can also edit the date and description of the transactions ( **New trans. date** and **New transaction description** ). 1. Click **Process** in the window toolbar to initiate the reclassification process. Once the process is completed successfully, The **Reclass. batch number** column appears with the number of the corresponding reclassification batch. The system includes journal entries, which have the same transaction period or the currency specified, in the same reclassification batch. A separate reclassification batch is generated for each journal entry that has a different transaction period or currency. 1. In the [Reclassify transactions (GL506000)](/visma-net-erp/help/general-ledger/general-ledger-windows/reclassify-transactions-gl506000/) window, release the batch. The batch will be released automatically if the **Automatically release reclassification batches** check box is selected in the [General ledger preferences (GL102000)](/visma-net-erp/help/general-ledger/general-ledger-windows/general-ledger-preferences-gl102000/) window. Related reference [Reclassification history](/visma-net-erp/help/general-ledger/general-ledger-windows/reclassification-history-gl405000/)

Related pages

Concepts

About VAT entries from the general ledger /visma-net-erp/help/general-ledger/manage-transactions/about-vat-entries-from-the-general-ledger page In Visma Net, you can configure automatic VAT calculation in documents that you create in the system. 2026-02-19T17:09:06+01:00 # About VAT entries from the general ledger In Visma Net, you can configure automatic VAT calculation in documents that you create in the system. In Visma Net, you can configure automatic VAT calculation in documents that you create in the system. With automatic VAT calculation, tax and taxable amounts are computed automatically on each invoice or invoice created in the system workspaces (such as Customer ledger or Supplier ledger). Once a document is created and released, the system automatically creates the appropriate general ledger transactions containing VAT-related journal entries. In Visma Net, you can also create tax-related transactions manually in the General ledger workspace. These transactions update the balances of the general ledger accounts specified for each journal entry of the transaction. Manual creating of VAT-related transactions is available only if the **VAT entry from general ledger module** functionality is enabled in the [Enable/disable functionalities (CS100000)](/visma-net-erp/help/common-settings/enable-or-disable-functionalites/enable-disable-functionalities-cs100000/) window. ## Manual creation of a VAT-related journal transaction You should use the [Journal transactions (GL301000)](/visma-net-erp/help/general-ledger/general-ledger-windows/journal-transactions-gl301000/)window to create a VAT-related journal transaction in the General ledger workspace. In this window, you need to select the **Create VAT transactions** check box so that the additional **VAT ID** and **VAT category** columns appear in the table. Each VAT-related transaction should contain at least three journal entries: + A journal entry that represents the document amount. (This amount can be recorded, for example, to the supplier ledger account.) + A journal entry that represents the VAT amount. (This amount can be recorded, for example, to the VAT payable account defined for a VAT.) + A journal entry that represents the taxable amount. (This amount can be recorded, for example, to any expense or income account, depending on the VAT type.) While creating a journal transaction, you need to specify the following information for each journal entry you add: Account : The general ledger account that should be updated with the amount you enter in this line. Subaccount : The appropriate subaccount (if any). Ref. number : The number of the internal or external document to which the transaction is related. VAT-related information will be posted to the appropriate VAT report only if you specify this reference number. Otherwise (if the **Ref. number** column is empty), VAT and taxable amounts will not be reflected in the VAT report. All journal entries of the journal transaction that relate to the same document should have the same document number in the Ref. number column. Debit amount : or **Credit amount**: The amount that should debit or credit the specified general ledger account (and subaccount, if applicable). A single journal entry should contain only a debit amount or credit amount. VAT ID : The VAT to be used to calculate VAT amount. The system enters the tax automatically if you have specified an account assigned to a particular VAT on the **General ledger accounts** tab in the [VAT (TX205000)](/visma-net-erp/help/vat/vat-windows/vat-tx205000/) window. VAT category : The VAT category based on which the taxable amount is calculated. The system enters the tax category automatically if you have selected an account (expense, income, or inventory) that is associated with a particular VAT category in the [Chart of accounts (GL202500)](/visma-net-erp/help/general-ledger/general-ledger-windows/chart-of-accounts-gl202500/) window. In a transaction, the total credit amount ( **Credit total** in the top part) of all journal entries must be equal to total debit amount ( **Debit total** ) of all journal entries. ## VAT amount calculation When you create a journal entry in the [Journal transactions (GL301000)](/visma-net-erp/help/general-ledger/general-ledger-windows/journal-transactions-gl301000/) windoww, the system calculates the tax amount according to the VAT associated with the general ledger account (and subaccount, if applicable) that you specify in the **Account** (and **Subaccount**, if any) column. When you specify the account (subaccount), the system automatically enters the tax associated with this account (subaccount) in the **VAT ID** column and uses it for calculating the VAT amount for the entry. The account (and subaccount. if any) associated with the tax has been specified in the **VAT payable account** (and **Subaccount** ) or **VAT claimable account** (and **Subaccount** ) field (depending on the VAT type) on the **General ledger accounts** tab in the [VAT (TX205000)](/visma-net-erp/help/vat/vat-windows/vat-tx205000/) window during configuration of a tax in the system. While you are adding a journal entry, you can overwrite the default **VAT ID** value. ## Taxable amount calculation The system calculates the taxable amount according to the VAT category specified for the journal entry in the **VAT category** column in the [Journal transactions (GL301000)](/visma-net-erp/help/general-ledger/general-ledger-windows/journal-transactions-gl301000/)window. Once you have selected an account in the **Account** column, the system automatically enters the VAT category associated with the general ledger account. The associated VAT category is the one that is assigned to the selected general ledger account in the **VAT category** column in the [Chart of accounts (GL202500)](/visma-net-erp/help/general-ledger/general-ledger-windows/chart-of-accounts-gl202500/) window. If no VAT category is specified for the general ledger account you select in the **Account** column, no VAT-related transaction can be created. ## Batch release On release of the journal transaction (a batch) that you have created, the general ledger accounts specified in each journal entry will be updated with the appropriate amounts. The tax-related amounts will be reflected in the appropriate tax report only if the number of the document related to the journal transaction is specified for each journal entry in the **Ref. number** column. About rules for balancing inter-branch transactions /visma-net-erp/help/general-ledger/manage-transactions/about-rules-for-balancing-inter-branch-transactions page When an organisation consists of multiple legal entities (branches), it often has transactions that occur between these branches. 2026-02-19T17:09:06+01:00 # About rules for balancing inter-branch transactions When an organisation consists of multiple legal entities (branches), it often has transactions that occur between these branches. When an organisation consists of multiple legal entities (branches), it often has transactions that occur between these branches. The branches of the same organisation may regularly purchase stock items for other branches, transfer goods, or redistribute funds among branches in the organisation. Inter-branch transactions, if they are not properly processed and eliminated, can result in overestimation of the organisation's financial position. Visma Net supports automatic generation of inter-branch transactions if the **Inter-branch transactions** functionality is activated. ## Types of inter-branch transactions An inter-branch transaction occurs when one branch of an organisation is involved in a transaction with another branch of the same organisation. Branches engaging in transactions with one another debit and credit each other as they would if there were no corporate relationship between them. Transactions between branches of an entity can take multiple windows and can occur between any branches of the entity. The transactions are processed differently depending on whether both branches are legal entities (or are units of different legal entities). There are two basic types of inter-branch transactions: 1. If transactions occur between branches that are legal entities themselves or are subordinate branches of different legal entities, they should be balanced in each branch involved so that the accounts of each legal entity will be in balance. 1. If transactions occur between a consolidation branch and its subordinate branch, these transactions do not always require balancing within each branch. However, it may happen that some inter-branch transactions require elimination before reporting. In Visma Net, an inter-branch transaction is considered a transaction of the first type if the following criteria are met: + The branches involved in the transaction post their records to different ledgers. + The branches use the same ledger, and for the ledger, the **Branch accounting** check box is selected in the [Ledgers (GL201500)](/visma-net-erp/help/general-ledger/general-ledger-windows/ledgers-gl201500/) window. Inter-branch transactions of the first type should be balanced in such a way that each branch can file reports separately. ## An example of inter-branch transaction balancing In Visma Net, the rules for balancing inter-branch transactions define offset accounts to be used for particular branches involved, depending on the accounts used in the original transactions. Let's create balancing rules based on the following example: Consider a retailing organisation with several autonomous branches (Model 2). To use volume discounts, Branch 1 purchases goods for itself and other branches and then transfers the purchased inventory to other branches. For example, Branch 1 moves some of the purchased inventory from its asset account 12000 to Branch 2's asset account 12100 and records the following journal entries. |Branch|Account|Debit|Credit| |---|---|---|---| |Branch 1|12000|0.0|€ 3867.49| |Branch 2|12100|€ 3867.49|0.0| To balance these transactions for each branch, we should add one complementary transaction for each original transaction, as shown below. |Branch|Account|Debit|Credit| |---|---|---|---| |Branch 1|12000|0.0|€ 3867.49| |Branch 1|XXXX (Receivables from Branch 2)|€ 3867.49|0.0| |Branch 2|12100|€ 3867.49|0.0| |Branch 2|YYYY (Payables to Branch 1)|0.0|€ 3867.49| In this example, **XXXX** and **YYYY** are offset accounts that should be defined by the balancing rules. **XXXX** is an account used by Branch 1 to record the amounts receivable from Branch 2, and **YYYY** is an account used by Branch 2 to record the amounts payable to Branch 1. Using specially created offset (inter-branch) accounts helps you efficiently identify inter-branch transactions, view that they are in balance, and eliminate them when you close an accounting period. Failure to eliminate inter-branch transactions when preparing the consolidated financial statements results in overstated financial results and can lead to legal consequences. ## Rules for transaction balancing In Visma Net, you can create account mapping by using the [Inter-branch account mapping (GL101010)](/visma-net-erp/help/general-ledger/general-ledger-windows/inter-branch-account-mapping-gl101010/)window. For each branch, specify a range of accounts that might be involved in inter-branch transactions. In each branch, specify offset (inter-branch) accounts for amounts to be paid to other branches (Payables to Branch 1, Payables to Branch 3, and so forth) and for amounts to be received from other branches (Receivables from Branch 1, Receivables from Branch 2, and so forth). The following terminology is used in the [Inter-branch account mapping (GL101010)](/visma-net-erp/help/general-ledger/general-ledger-windows/inter-branch-account-mapping-gl101010/)window: An **originating** branch is always the branch specified in the top part (header) of the document to be balanced, and each of the branches specified in the document lines are the **destination** branches. For each branch selected in the top part of the [Inter-branch account mapping (GL101010)](/visma-net-erp/help/general-ledger/general-ledger-windows/inter-branch-account-mapping-gl101010/) window, use the **Transaction in the originating branch** tab to specify the offset accounts to be used for specific ranges of accounts in each of the other branches. Then, if an inter-branch transaction refers to an account in one of the specified ranges in any destination branch, the system will generate a new balancing transaction in the originating branch for the respective offset account. You can use the **Transaction in the destination branch** tab to specify the offset accounts to be used for generating balancing transactions in other branches if the inter-branch transactions refers to accounts within specific account ranges in the destination branches. To better understand how to use the [Inter-branch account mapping (GL101010)](/visma-net-erp/help/general-ledger/general-ledger-windows/inter-branch-account-mapping-gl101010/)window, consider the following example: There are three branches in an organisation. If you select **Branch 1** in the top part of the window, on the **Transaction in the originating branch** tab, for Branch 1 you can specify the following offset accounts: **Receivables from branch 2**, **Receivables from branch 3**. For the above example, by using the **Transaction in the destination branch** tab, you can specify the following offset accounts: + For branch 2: **Payables to Branch 1** + For branch 3: **Payables to Branch 1** Successively selecting Branch 2 and Branch 3 in the top part of the window, you can specify the inter-branch accounts for all possible inter-branch transactions. ## Using the rules The system will apply the balancing rules to the inter-branch transactions once the following conditions are met: + The transaction accounts match the account range specified by rules for inter-branch transactions. + The transaction's header and the details refer to different branches. Complementary transactions are generated when the original transactions are posted. About foreign currency transactions /visma-net-erp/help/general-ledger/manage-transactions/about-foreign-currency-transactions page You can use the General ledger workspace to record batches of journal entries in foreign currencies. 2026-02-19T17:09:06+01:00 # About foreign currency transactions You can use the General ledger workspace to record batches of journal entries in foreign currencies. You can use the General ledger workspace to record batches of journal entries in foreign currencies. All the transactions in one batch must use the same currency, but not necessarily the base currency. If at least one of the accounts used in a batch is denominated to a specific currency, only this currency can be used as a batch currency. The default exchange rate type is defined for all the foreign currencies in the [Currency management preferences (CM101000)](/visma-net-erp/help/currency-management/currency-management-windows/currency-management-preferences-cm101000/) window. Exchange rates for all rate types are maintained in the system with their history. ## Rounding gains and losses Once you enter your journal transactions with debit and credit amounts in the foreign currency, the system automatically converts the amounts into the base currency based on the default or the specified exchange rate. The base currency generally has fewer decimal places than the exchange rate, which has six decimal places. Thus, the debit and credit amounts calculated in the base currency may differ by a very small amount, causing the batch to not balance. In this case, the difference is recorded to one of the accounts specified for each currency, **Rounding gain** account or **Rounding loss** account, and the corresponding transaction is automatically added to the batch. ### Related concepts [About denominated accounts](/visma-net-erp/help/general-ledger/manage-accounts/about-denominated-accounts/) ### Related reference [Journal transactions](/visma-net-erp/help/general-ledger/general-ledger-windows/journal-transactions-gl301000/)