Batch

The field is populated when running the Process document processing in the Accounting document table.

When checked you must also unhide the field Previous voucher no. in the Voucher table. If you enter a Previous voucher no. on the vouchers, Business NXT will retrieve the entry for the previous voucher and enter it against this voucher to reset the previous posting, so that you can post it on the definite account.

Can be entered manually. Next free Batch no. will be given by entering +, although omissions in the number series resulting from any deleted batches are not suggested. When you update the batch the Batch no. is released so that you can re-use numbers if you wish unless the Updated batch has a "x" in the Keep field.

Copy description to new lines

Selecting this, Business NXT copies the text in the Description field in the batch head to the Text field in new voucher lines instead of suggesting the text field from the Voucher type table.

Exclude VAT when checking amount difference

The debit-/ credit difference will be calculated from the column Amount excl. VAT in the Voucher table.

Locked

If selected, the Batch is locked for editing. No changes can be done in the Batch and its Voucher lines.

Tentative - Do not assign voucher numbers

If selected, no Voucher no. will be set for the voucher lines. The Tentative field in the Batch table will visualise this selection. Selection can be removed manually, either by clearing the value in the Tentative field, or via the Assign voucher numbers processing.

Pre-registration

This option is used by Visma Business Workflow. It is automatically set when Pre-registration for incoming invoices has been enabled in Workflow processing field in Company information table and batch has been created by Process document in Accounting document table.

In Approval

Reversal

The value is calculated continuously when you fill in, change or delete amounts or the debit/credit account number in the vouchers.

The amount is meant to be filled in manually from the bank account statement, to be compared to the Calculated CB bank.

The difference between this field and Total credit field appears in the Control diff. field.

You can enter a manually calculated check sum in this field to ensure that you have entered all the vouchers in the batch. This enables you to check that the sum Total debit/Total credit (see below) is equal to the Check sum before you update the batch. Alternatively, you can use the field as an information field for other users, for example, to record why the batch has not yet been updated.

If you decide to use the field for a particular piece of information, the lead text/column heading can be given a more appropriate designation, e.g. Check sum or Information.

You can enter a manually calculated Check sum in the field to ensure that you have entered all the vouchers in the batch. This enables you to check that the Total debit/Total credit fields are equal to the Check sum before you update the batch. Alternatively, you can use the field as an information field for other users, for example to record why the batch has not yet been updated.

If you decide to use the field for a particular piece of information, the lead text/column heading can be given a more appropriate designation, e.g. Check sum or Information.

This field is an information field, which is updated whenever you enter, change or delete an amount or an account number on the Vouchers.

The field has the same function as the Difference field but in the current currency. See the explanation under the Difference field.

This field is an information field, which is updated whenever you enter, change or delete an amount or an account number on the Vouchers.

The field has the same function as the Difference field but in the current currency 2. See the explanation under the Difference field.

If you want to use the function with calculated OB, Motion and CB on bank vouchers, even in the Currency account, you enter the Currency no. in this field. Then only entries to the bank account in the vouchers with this Currency no. will be accumulated in the batch head.

Will be suggested on the vouchers (if the column is empty) when Debit account / Credit account fields are entered.

An information field, which is updated whenever you enter, change or delete an amount or an account number on the vouchers.

A negative difference means that a higher total amount has been posted to the Credit account than to the Debit account. If the Debit/credit control field is selected in the Company information table, you are not allowed to update batches containing a difference. There is no control to determine whether the Batch contains a difference when it is saved, because the batch is regarded as a draft until it is updated.

If a group voucher from the bank or Post Office is entered extending over several vouchers, it is a good idea to check that there are no differences in the Voucher (a Voucher can easily be overlooked).

This field is an information field, which is updated whenever you enter, change or delete an amount or an account number on the Vouchers.

The field has the same function as the Difference field but with amounts excl. VAT. See the explanation under the Difference field.

The account no. for the bank account that you want to follow in the entered vouchers by using the OB bank, CB bank, Calculated CB bank and Calculated movem. bank fields.

The Voucher no. and date are retained, which means that if you need to update the batch more than once, you should change these fields if necessary before the next update. The box is checked if any value other than 0 and blank is entered.

In the case of fixed, periodic vouchers such as rental and other fixed expenditure, you can create permanent batches, where you only update Voucher no. and date before updating. The Suspended field should also be checked for such periodically batches to make sure they are not updated by mistake. In order to avoid involuntary double updates of batches, a safer, recommended alternative is to create new batches of batches that have already been updated. To do this, select the Create new batch processing in the Updated batch table.

The following Voucher processings are prevented from running when Batch is Locked:

The following Voucher commands are prevented from running when Batch is Locked:

Reference fields appear in the Batch window corresponding to the organisational unit classes you have defined in the Company information table. The fields might be called for example Department, Project or Object. You have one field per organisational unit, so that you can run the same Batch for both a department and a project, for example.

You enter the organisational units for which to run the batch. The organisational units are suggested in the vouchers when you post general ledger accounts for which you have not entered a permanent organisational unit, and only if the option of suggesting the organisational unit class is enabled. In the case of accounts for which permanent organisational units have been defined, these will continue to be suggested in preference to the organisational unit defined in the batch. You can change the organisational unit in each vouchers by returning to the Organisational unit field.

When an organisational unit is entered in the Batch head or the vouchers, other organisational units that you have entered for this organisational unit, are suggested.

Organisational units fields can be used freely according to company needs to split accounting, sales and purchases into organisational units. The most common types are department, project and campaign. It is also possible to limit the organisational units a user should see by limiting the organisational units in the Limitation groups, User limitation groups and Limitations. The field appear with the name assigned to it in the Company information table.

Reference fields appear in the Batch window corresponding to the organisational unit classes you have defined in the Company information table. The fields might be called for example Department, Project or Object. You have one field per organisational unit, so that you can run the same Batch for both a department and a project, for example.

You enter the organisational units for which to run the batch. The organisational units are suggested in the vouchers when you post general ledger accounts for which you have not entered a permanent organisational unit, and only if the option of suggesting the organisational unit class is enabled. In the case of accounts for which permanent organisational units have been defined, these will continue to be suggested in preference to the organisational unit defined in the batch. You can change the organisational unit in each vouchers by returning to the Organisational unit field.

When an organisational unit is entered in the Batch head or the vouchers, other organisational units that you have entered for this organisational unit, are suggested.

Organisational units fields can be used freely according to company needs to split accounting, sales and purchases into organisational units. The most common types are department, project and campaign. It is also possible to limit the organisational units a user should see by limiting the organisational units in the Limitation groups, User limitation groups and Limitations. The field appear with the name assigned to it in the Company information table.

Reference fields appear in the Batch window corresponding to the organisational unit classes you have defined in the Company information table. The fields might be called for example Department, Project or Object. You have one field per organisational unit, so that you can run the same Batch for both a department and a project, for example.

You enter the organisational units for which to run the batch. The organisational units are suggested in the vouchers when you post general ledger accounts for which you have not entered a permanent organisational unit, and only if the option of suggesting the organisational unit class is enabled. In the case of accounts for which permanent organisational units have been defined, these will continue to be suggested in preference to the organisational unit defined in the batch. You can change the organisational unit in each vouchers by returning to the Organisational unit field.

When an organisational unit is entered in the Batch head or the vouchers, other organisational units that you have entered for this organisational unit, are suggested.

Organisational units fields can be used freely according to company needs to split accounting, sales and purchases into organisational units. The most common types are department, project and campaign. It is also possible to limit the organisational units a user should see by limiting the organisational units in the Limitation groups, User limitation groups and Limitations. The field appear with the name assigned to it in the Company information table.

Reference fields appear in the Batch window corresponding to the organisational unit classes you have defined in the Company information table. The fields might be called for example Department, Project or Object. You have one field per organisational unit, so that you can run the same Batch for both a department and a project, for example.

You enter the organisational units for which to run the batch. The organisational units are suggested in the vouchers when you post general ledger accounts for which you have not entered a permanent organisational unit, and only if the option of suggesting the organisational unit class is enabled. In the case of accounts for which permanent organisational units have been defined, these will continue to be suggested in preference to the organisational unit defined in the batch. You can change the organisational unit in each vouchers by returning to the Organisational unit field.

When an organisational unit is entered in the Batch head or the vouchers, other organisational units that you have entered for this organisational unit, are suggested.

Organisational units fields can be used freely according to company needs to split accounting, sales and purchases into organisational units. The most common types are department, project and campaign. It is also possible to limit the organisational units a user should see by limiting the organisational units in the Limitation groups, User limitation groups and Limitations. The field appear with the name assigned to it in the Company information table.

Reference fields appear in the Batch window corresponding to the organisational unit classes you have defined in the Company information table. The fields might be called for example Department, Project or Object. You have one field per organisational unit, so that you can run the same Batch for both a department and a project, for example.

You enter the organisational units for which to run the batch. The organisational units are suggested in the vouchers when you post general ledger accounts for which you have not entered a permanent organisational unit, and only if the option of suggesting the organisational unit class is enabled. In the case of accounts for which permanent organisational units have been defined, these will continue to be suggested in preference to the organisational unit defined in the batch. You can change the organisational unit in each vouchers by returning to the Organisational unit field.

When an organisational unit is entered in the Batch head or the vouchers, other organisational units that you have entered for this organisational unit, are suggested.

Organisational units fields can be used freely according to company needs to split accounting, sales and purchases into organisational units. The most common types are department, project and campaign. It is also possible to limit the organisational units a user should see by limiting the organisational units in the Limitation groups, User limitation groups and Limitations. The field appear with the name assigned to it in the Company information table.

Reference fields appear in the Batch window corresponding to the organisational unit classes you have defined in the Company information table. The fields might be called for example Department, Project or Object. You have one field per organisational unit, so that you can run the same Batch for both a department and a project, for example.

You enter the organisational units for which to run the batch. The organisational units are suggested in the vouchers when you post general ledger accounts for which you have not entered a permanent organisational unit, and only if the option of suggesting the organisational unit class is enabled. In the case of accounts for which permanent organisational units have been defined, these will continue to be suggested in preference to the organisational unit defined in the batch. You can change the organisational unit in each vouchers by returning to the Organisational unit field.

When an organisational unit is entered in the Batch head or the vouchers, other organisational units that you have entered for this organisational unit, are suggested.

Organisational units fields can be used freely according to company needs to split accounting, sales and purchases into organisational units. The most common types are department, project and campaign. It is also possible to limit the organisational units a user should see by limiting the organisational units in the Limitation groups, User limitation groups and Limitations. The field appear with the name assigned to it in the Company information table.

Reference fields appear in the Batch window corresponding to the organisational unit classes you have defined in the Company information table. The fields might be called for example Department, Project or Object. You have one field per organisational unit, so that you can run the same Batch for both a department and a project, for example.

You enter the organisational units for which to run the batch. The organisational units are suggested in the vouchers when you post general ledger accounts for which you have not entered a permanent organisational unit, and only if the option of suggesting the organisational unit class is enabled. In the case of accounts for which permanent organisational units have been defined, these will continue to be suggested in preference to the organisational unit defined in the batch. You can change the organisational unit in each vouchers by returning to the Organisational unit field.

When an organisational unit is entered in the Batch head or the vouchers, other organisational units that you have entered for this organisational unit, are suggested.

The field appear with the name assigned to it in the Company information table.

Reference fields appear in the Batch window corresponding to the organisational unit classes you have defined in the Company information table. The fields might be called for example Department, Project or Object. You have one field per organisational unit, so that you can run the same Batch for both a department and a project, for example.

You enter the organisational units for which to run the batch. The organisational units are suggested in the vouchers when you post general ledger accounts for which you have not entered a permanent organisational unit, and only if the option of suggesting the organisational unit class is enabled. In the case of accounts for which permanent organisational units have been defined, these will continue to be suggested in preference to the organisational unit defined in the batch. You can change the organisational unit in each vouchers by returning to the Organisational unit field.

When an organisational unit is entered in the Batch head or the vouchers, other organisational units that you have entered for this organisational unit, are suggested.

The field appear with the name assigned to it in the Company information table.

Reference fields appear in the Batch window corresponding to the organisational unit classes you have defined in the Company information table. The fields might be called for example Department, Project or Object. You have one field per organisational unit, so that you can run the same Batch for both a department and a project, for example.

You enter the organisational units for which to run the batch. The organisational units are suggested in the vouchers when you post general ledger accounts for which you have not entered a permanent organisational unit, and only if the option of suggesting the organisational unit class is enabled. In the case of accounts for which permanent organisational units have been defined, these will continue to be suggested in preference to the organisational unit defined in the batch. You can change the organisational unit in each vouchers by returning to the Organisational unit field.

When an organisational unit is entered in the Batch head or the vouchers, other organisational units that you have entered for this organisational unit, are suggested.

The field appear with the name assigned to it in the Company information table.

Reference fields appear in the Batch window corresponding to the organisational unit classes you have defined in the Company information table. The fields might be called for example Department, Project or Object. You have one field per organisational unit, so that you can run the same Batch for both a department and a project, for example.

You enter the organisational units for which to run the batch. The organisational units are suggested in the vouchers when you post general ledger accounts for which you have not entered a permanent organisational unit, and only if the option of suggesting the organisational unit class is enabled. In the case of accounts for which permanent organisational units have been defined, these will continue to be suggested in preference to the organisational unit defined in the batch. You can change the organisational unit in each vouchers by returning to the Organisational unit field.

When an organisational unit is entered in the Batch head or the vouchers, other organisational units that you have entered for this organisational unit, are suggested.

The field appear with the name assigned to it in the Company information table.

Reference fields appear in the Batch window corresponding to the organisational unit classes you have defined in the Company information table. The fields might be called for example Department, Project or Object. You have one field per organisational unit, so that you can run the same Batch for both a department and a project, for example.

You enter the organisational units for which to run the batch. The organisational units are suggested in the vouchers when you post general ledger accounts for which you have not entered a permanent organisational unit, and only if the option of suggesting the organisational unit class is enabled. In the case of accounts for which permanent organisational units have been defined, these will continue to be suggested in preference to the organisational unit defined in the batch. You can change the organisational unit in each vouchers by returning to the Organisational unit field.

When an organisational unit is entered in the Batch head or the vouchers, other organisational units that you have entered for this organisational unit, are suggested.

The field appear with the name assigned to it in the Company information table.

Reference fields appear in the Batch window corresponding to the organisational unit classes you have defined in the Company information table. The fields might be called for example Department, Project or Object. You have one field per organisational unit, so that you can run the same Batch for both a department and a project, for example.

You enter the organisational units for which to run the batch. The organisational units are suggested in the vouchers when you post general ledger accounts for which you have not entered a permanent organisational unit, and only if the option of suggesting the organisational unit class is enabled. In the case of accounts for which permanent organisational units have been defined, these will continue to be suggested in preference to the organisational unit defined in the batch. You can change the organisational unit in each vouchers by returning to the Organisational unit field.

When an organisational unit is entered in the Batch head or the vouchers, other organisational units that you have entered for this organisational unit, are suggested.

The field appear with the name assigned to it in the Company information table.

The Origin and Original run no. fields in the Batch table are only information fields.

The first field indicates whether the batch was entered manually or it was generated in an automatic routine. The latter case applies, for example, to payment transfer, interest computation, reminders, closing VAT period, OCR payments, etc.

The other field indicates the run number allocated to the batch in question. The run number will only be filled out from relevant processes, e.g. invoicing (Order journal no) and VAT reports (VAT report no)

These fields are uneditable.

1 - Manually entered

2 - Automatically generated

13 - Automatic entry

3 - VAT report

41 - OSS VAT report

10 - Direct debiting

4 - Reminder

5 - Interest note

8 - OCR payment

21 - Write off payments

6 - Giro payment

7 - Direct payment

11 - Depreciation on capital assets

9 - Order processing

23 - Incoming invoice

12 - Import

Normal text import.

14 - Previous batch

15 - Compressing transactions

16 - Posting of costs

18 - Internal invoicing

17 - Differences

When you update a batch with this origin code debit/credit control is not carried out.

19 - EDI invoice import

20 - Payroll

22 - Visma Business Services

24 - Activate Capital asset

25 - Calculate client interest

26 - Document Center temporary batch

27 - Document Center finished batch

28 - Debt collector

29 - Split invoice

30 - Currency correction

31 - External application

If this origin code is used, this value can be used by other applications that use BIG or SQL and create batches.

32 - Cash order document

33 - Sell or scrap capital asset

34 - Initializing capital asset

35 - EDI read dirdeb vouchers

37 - Accrual accounting

38 - Order processing with picking after invoicing

39 - Picked after invoicing

40 - Correction of costs

42 - Accounting document

Batch was created from Accounting document table.

43 - Order match pre-registration

44 - Self billing invoice

45 - Split batch, supplier transactions

Batch was created by Update supplier transactions processing for supplier transactions only.

46 - Split batch, cost transactions

Batch was created by Update supplier transactions processing for cost and capital transactions to be adjusted after payment.

47 - Account statement vouchers

Batch was created by Create voucher processing in the Account statement transaction table.

48 - WebFaktura

49 - Central

The Origin and Original run no. fields in the Batch table are only information fields.

The first field indicates whether the batch was entered manually or it was generated in an automatic routine. The latter case applies, for example, to payment transfer, interest computation, reminders, closing VAT period, OCR payments, etc.

The other field indicates the run number allocated to the batch in question. The run number will only be filled out from relevant processes, e.g. invoicing (Order journal no) and VAT reports (VAT report no)

These fields are uneditable.

The Year and Period fields are the accounting year and period for which the batch is updated. The VAT year and VAT period fields are the VAT period and VAT year for which the batch is updated. If you complete the Value date field, Business NXT suggests the Year, Period, VAT year and VAT period within which the Value date falls. You can override the Period, Year, VAT year and VAT term fields yourself. If the Value date is not filled in, Business NXT sets it to the last date in the relevant period.

Example If accounting period 13 is used for year-end transactions, the end date for accounting periods 12 and 13 will be the same, i.e. 31.12. This means that if you post vouchers in period 13 and enter 31.12 in the Value date field, the value 12 is entered in the Period field. The value 13 must therefore override the Period field, to ensure that Business NXT updates the batch in the correct period.

The period, year, VAT year and VAT term must be later than the Suspension date in the dialog box for the Move suspension date processing in the Company information table, and must fall within a defined accounting period and VAT term to update the batch. Even if a company is not liable to pay tax, at least one VAT term must be defined to cover the entire accounting year.

The suspension date can be updated whenever a VAT statement is approved, which means that vouchers cannot be posted for periods that have finished. You can enter vouchers for the next accounting year before you have finished the current year, provided that the periods for the next year have been defined in the Accounting period and VAT period tables.

If you type + in one of the fields, the system enters the next period that has not been opened.

The no will show the original Batch no. for batches with the origin 14 - Previous batch.

Will be filled out only on batches with the origin 14 - Previous batch

The Reversal VAT period, Reversal VAT year, Reversal period and Reversal year fields are filled in when you enter the reversal date.

The Reversal VAT period, Reversal VAT year, Reversal period and Reversal year fields are filled in when you enter the reversal date.

The Reversal VAT period, Reversal VAT year, Reversal period and Reversal year fields are filled in when you enter the reversal date.

The Reversal VAT period, Reversal VAT year, Reversal period and Reversal year fields are filled in when you enter the reversal date.

The Reversal VAT period, Reversal VAT year, Reversal period and Reversal year fields are filled in when you enter the reversal date.

Has the same function as the Total credit field, but in the relevant currency 2.

The field is updated each time you enter, change or delete an amount or account number in the Voucher table. You can also use the Sum curr. 2 debit and Sum curr. 2 credit fields to check against a manually calculated Check sum to ensure that all vouchers have been entered correctly. You then total the vouchers in the batch manually before you start posting them. The Check sum may be entered in the Description field (see previous section).

The field is uneditable.

Has the same function as the Total debit field, but in the current currency 2.

This field is updated each time you enter, change or delete an amount or account number in the Voucher table. You can also use the Sum curr. 2 debit and Sum curr. 2 credit fields to check against a manually calculated Check sum to ensure that all vouchers have been entered correctly. You then total the vouchers in the batch manually before you start posting them. You can enter the Check sum in the Description field.

The field is uneditable.

Has the same function as the Total credit field, but in the current currency.

The field is updated every time you enter, change or delete an amount or an account number in the Voucher table. You can also use the Sum curr. debit and Sum curr. credit fields to check against a manually calculated Check sum to ensure that all vouchers have been entered correctly. You then total the vouchers in the batch manually before you start posting them. The Check sum may be entered in the Description field (see previous section).

The field is uneditable.

Has the same function as the Total debit field, but in the current currency.

The field is updated every time you enter, change or delete an amount or an account number in the Voucher table. You can also use the Sum curr. debit and Sum curr. credit fields to check against a manually calculated Check sum to ensure that all vouchers have been entered correctly. You then total the vouchers in the batch manually before you start posting them. You can enter the Check sum in the Description field.

The field is uneditable.

The box is checked if any value other than 0 and blank is entered.

You should use this field if you close a Batch without completing Voucher entry, to prevent another user updating the batch by mistake. You can enter a comment in the Description field to explain why the batch must not be updated yet. If you try to update a suspended Batch, an error message will be displayed in the status bar and in a dialog and the update process will not be started.

This field is a visualisation of the Tentative - Do not assign voucher numbers flag in the Batch processing field. Used in import from Visma Business Workflow of incoming invoices that are still in the approval flow.

The field is updated every time you enter, change or delete an amount or a credit account number in the Voucher window. You can also use the Total debit and Total credit fields to check against a manually calculated Check sum to ensure that all vouchers have been entered correctly. In that case You total the vouchers in the batch manually before you start posting them. The Check sum may for example be entered in the Description field (see previous section).

The field is uneditable.

The field is updated every time you enter, change or delete an amount or an account number in the Voucher window. You can also use the Total Debit excl. VAT and Total Credit excl. VAT fields to check against a manually calculated Check sum to ensure that all vouchers have been entered correctly. You then total the vouchers in the Batch manually before you start posting them. The Check sum may be entered in the Description field (see previous section).

The field is uneditable.

The field is updated every time you enter, change or delete an amount or an account number in the Voucher window. You can also use the Total debit and Total credit fields to check against a manually calculated Check sum to ensure that all vouchers have been entered correctly. You then total the vouchers in the batch manually before you start posting them. You can enter the Check sum in the Description field.

The field is uneditable.

The field is updated every time you enter, change or delete an amount or an account number in the Voucher window. You can also use the Total Debit excl. VAT and Total Credit excl. VAT fields to check against a manually calculated Check sum to ensure that all vouchers have been entered correctly. You then total the vouchers in the batch manually before you start posting them. You can enter the Check sum in the Description field.

The field is uneditable.

The Value date field completes the Period, Year, VAT period and VAT year fields. These are the fields that determine the periods and years for which the vouchers are posted. You should therefore ensure that the current date falls within the accounting period for which you want the voucher to be updated. If it does not, you must remember to enter the accounting period, accounting year, VAT term and VAT year to the correct Period and Year manually.

If you type / in the field, the system copies the date from the previous batch. The field pointer moves to the next field which means you do not have to press Enter.

The date is validated using the regional settings in Windows.

The Year and Period fields are the accounting year and period for which the batch is updated. The VAT year and VAT period fields are the VAT period and VAT year for which the batch is updated. If you complete the Value date field, Business NXT suggests the Year, Period, VAT year and VAT period within which the Value date falls. You can override the Period, Year, VAT year and VAT term fields yourself. If the Value date is not filled in, Business NXT sets it to the last date in the relevant period.

Example If accounting period 13 is used for year-end transactions, the end date for accounting periods 12 and 13 will be the same, i.e. 31.12. This means that if you post vouchers in period 13 and enter 31.12 in the Value date field, the value 12 is entered in the Period field. The value 13 must therefore override the Period field, to ensure that Business NXT updates the batch in the correct period.

The period, year, VAT year and VAT term must be later than the Suspension date in the dialog box for the Move suspension date processing in the Company information table, and must fall within a defined accounting period and VAT term to update the batch. Even if a company is not liable to pay tax, at least one VAT term must be defined to cover the entire accounting year.

The suspension date can be updated whenever a VAT statement is approved, which means that vouchers cannot be posted for periods that have finished. You can enter vouchers for the next accounting year before you have finished the current year, provided that the periods for the next year have been defined in the Accounting period and VAT period tables.

If you type + in one of the fields, the system enters the next period that has not been opened.

The Year and Period fields are the accounting year and period for which the batch is updated. The VAT year and VAT period fields are the VAT period and VAT year for which the batch is updated. If you complete the Value date field, Business NXT suggests the Year, Period, VAT year and VAT period within which the Value date falls. You can override the Period, Year, VAT year and VAT term fields yourself. If the Value date is not filled in, Business NXT sets it to the last date in the relevant period.

Example If accounting period 13 is used for year-end transactions, the end date for accounting periods 12 and 13 will be the same, i.e. 31.12. This means that if you post vouchers in period 13 and enter 31.12 in the Value date field, the value 12 is entered in the Period field. The value 13 must therefore override the Period field, to ensure that Business NXT updates the batch in the correct period.

The period, year, VAT year and VAT term must be later than the Suspension date in the dialog box for the Move suspension date processing in the Company information table, and must fall within a defined accounting period and VAT term to update the batch. Even if a company is not liable to pay tax, at least one VAT term must be defined to cover the entire accounting year.

The suspension date can be updated whenever a VAT statement is approved, which means that vouchers cannot be posted for periods that have finished. You can enter vouchers for the next accounting year before you have finished the current year, provided that the periods for the next year have been defined in the Accounting period and VAT period tables.

If you type + in one of the fields, the system enters the next period that has not been opened.

You define the Voucher reversal date on which you wish to reverse the batch if necessary. If you enter + in this field, the first day of the next accounting period is entered. The Reversal VAT period, Reversal VAT year, Reversal period and Reversal year fields are filled in when you enter the reversal date.

If these fields are filled in when you update the batch, Business NXT updates the batch again after regular updating with the reversal date as the Value date, reversal year and period as the accounting year and period, Reversal VAT year and term as the VAT year and term, in the batch and in all vouchers, and with the values in the debit and credit fields reversed.

The reversal date is used as the Voucher date.

The transactions in the two rounds of updating are labelled in the Trans. status field with flags for temporary and reversal respectively. The flags are visualised with radio buttons in the Duration group in the look-up dialog box for this field. Regular transactions have a selection in the Permanent radio button. The fields are carried to the table of Updated batch (and if necessary back again using the Create new batch processing).

The tables with Updated batch, vouchers and cross-references are updated in the final round, and the rows in the tables with batches, vouchers and cross-references are deleted.

The date is validated using the regional settings in Windows.

If you specify a Voucher series for the batch, you can type + in the Voucher no. and Voucher type fields in the Voucher window. This causes Business NXT to suggest the next voucher no. in the specified Voucher series and the Voucher type defined for the Voucher series. This assumes that you have defined separate Voucher series for the major types of vouchers. You can change or even delete the Voucher series specified for the batch several times when entering vouchers in a batch. Changing the Voucher series only affects new vouchers.

Example If you specify the Voucher series for outgoing invoices for a Batch and then enter all the outgoing invoices, you can change the Voucher series for bank vouchers in the Batch window afterwards. The suggested number in the next vouchers of the Voucher window will relate to the bank vouchers series.

If the Voucher series is reserved, either because Business NXT is currently updating vouchers for another user or because another user has reserved the series, the following message will be shown: The voucher series is in use. If voucher number control is being used and an abnormal interruption occurs during Voucher entry, the voucher series in use will remain reserved until the system supervisor releases the lock.

If you prefer to register the vouchers unsorted, you can skip the Voucher series no. field in the batch. However, you must then keep track of the first free voucher no. yourself, because Business NXT only keeps track of voucher no. within the various voucher series defined in the Voucher series table.

You can also receive a message if the Voucher series is suspended. All Voucher series used by Business NXT in automated routines are blocked from manual use.

Workflow document ID is assigned when sending the document for approval. The identifier can be used to find the document for example in Visma.net Approval.

The Year and Period fields are the accounting year and period for which the batch is updated. The VAT year and VAT period fields are the VAT period and VAT year for which the batch is updated. If you complete the Value date field, Business NXT suggests the Year, Period, VAT year and VAT period within which the Value date falls. You can override the Period, Year, VAT year and VAT term fields yourself. If the Value date is not filled in, Business NXT sets it to the last date in the relevant period.

Example If accounting period 13 is used for year-end transactions, the end date for accounting periods 12 and 13 will be the same, i.e. 31.12. This means that if you post vouchers in period 13 and enter 31.12 in the Value date field, the value 12 is entered in the Period field. The value 13 must therefore override the Period field, to ensure that Business NXT updates the batch in the correct period.

The period, year, VAT year and VAT term must be later than the Suspension date in the dialog box for the Move suspension date processing in the Company information table, and must fall within a defined accounting period and VAT term to update the batch. Even if a company is not liable to pay tax, at least one VAT term must be defined to cover the entire accounting year.

The suspension date can be updated whenever a VAT statement is approved, which means that vouchers cannot be posted for periods that have finished. You can enter vouchers for the next accounting year before you have finished the current year, provided that the periods for the next year have been defined in the Accounting period and VAT period tables.

If you type + in one of the fields, the system enters the next period that has not been opened.