Voucher

It is possible to manually select an accounting rule on the voucher line.

Values on the voucher line will be filled from the accounting rule. It is possible to discard changes from the rule, and then roll back to the previously saved state.

It is possible to change what rule is applied by selecting another rule.

When accounting rule is selected manually, any rule can be selected and no validation is done against Accounting rule criteria.

An extra text to describe the voucher and its content can be entered in this field

If you have entered a macro in Additional text definition field in the Voucher type table, the field is filled in during manual Voucher registration. It will also be filled in in connection with:

• Updating Voucher lines.
• Batches generated by other subsystems.
• Batches that have been imported.

If you use tax codes to post taxes during voucher updates, you must enter the gross amount, i.e. the amount inclusive of any VAT in this field, since the Amount excl. VAT and the VAT amount will be calculated from the gross amount

If you want to post the same amounts to the Debit account and Credit account, you can enter both accounts in the same voucher line with the same amount. If a group voucher is being entered, e.g. from the bank or Post Office, and the amount is to be divided between several general ledger accounts, the voucher must be entered over several lines. If you enter + in the Amount field, the difference between the Total debit and the Total credit fields in the batch will be suggested. If the difference is 0, the amount from the voucher line above will be copied, as when entering / in the field. The cursor moves to the next field, which means that you do not have to press Enter.

Accrual accounting

If you have a Voucher type record where the Accrual accounting field is selected or where the reference to the General ledger account table from the Debit account/Credit account field have Accrual accounting selected. Then a flag is placed in the Voucher to tell you that the accrual accounting dialog box will appear when you enter something in the Amount or Amount in currency field.

See also: Accrual accounting

Expanding automatic entries

If you select 1 - Expand on voucher lines in the Auto. entry processing field for the General ledger account table or in the Automatic entry table the automatic entries will be expanded in the entry window. The automatic entries appear when you enter values in the Amount field or in the Amount in currency field.

See also: Expand automatic entries

The Amount excl. VAT check box in the Trans. status field is selected to show you that you have value in the Amount excl. VAT field. You can see this in the dialog box that appears when you double-click or press * in the Trans. status field. If you complete the Amount field afterwards, the check box is cleared.

If you complete this field, the Amount field is calculated and then the VAT amount field will be calculated.

If you override the VAT amount, the Amount excl. VAT field is recalculated if the flag in the Trans. status is not set, otherwise the value in the Amount field is recalculated.

If you update the Debit VAT code/Credit VAT code fields, the program will not recalculate the VAT amount or Amount fields, unless the Amount excl. VAT is re-entered.

When you fill this field, the Amount in currency field is calculated and then the VAT amount in currency field will be calculated.

If you update the Debit VAT code/Credit VAT code fields, the program will not recalculate the VAT amount in currency or Amount in currency fields, unless the Amount excl. VAT in currency is re-typed.

If Enter currency field is selected for the Voucher type that is used, the cursor pauses in the Currency no. field and the Amount in currency field and skips the Amount field. The Amount field is calculated as soon as the Amount in currency field is entered, or if the Currency no., Exchange rate or Amount in currency fields are updated.

If you update the Amount field, the Amount in currency field is calculated immediately and the Exchange rate remains unchanged. However, if you want the Exchange rate field to be updated when you update the Amount in currency field or the Amount field, you must select the Calculate cur. rate field in the Voucher type table.

In the same way as the Amount field, the Amount in currency field is added up for general ledger accounts, customers and suppliers, and you can print out these on account statements and balance lists. The balance tables only store the balance for the currency defined for the particular general ledger account, as well as the balance in the domestic currency.

If the domestic amount is entered, the balance for the customer is not accumulated in the foreign currency when the voucher line is updated, even if the Currency no. is entered for the customer. Similarly, if no currency is defined for the sales account in the General ledger account table, no general ledger balance will be calculated in foreign currency.

If you enter + in the Amount in currency field the cursor skips to the next field without entering a value. It is then easier for you to load the outstanding amount when using currency, and you also avoid differences.

Amount in currency without VAT.

The Amount in currency fields for General ledger transactions and Capital asset transactions is calculated on the basis of the amount posted, i.e. after the deduction of VAT. The amount is reduced by the same percentage as the Posted amount in relation to the Entered amount.

If you change the value in the Exchange rate 2 field or the Amount field in the base currency in a voucher line, these values will be used as a basis for calculating the Amount in currency 2 field. If you override the Amount in currency 2 field then the Exchange rate 2 field is recalculated, unless you leave the field blank or the Amount in the base currency is not entered.

The amount in base currency is:

• Amount in currency, if you have selected the Calculate "Amount in currency 2" from "Currency amount" check box in the Accounting processing field in the Company information table, and the Amount in currency field is filled in on the Voucher line.

and if not the base currency is:

• Amount

Amount in currency 2 without VAT.

Amount in currency 2 for General ledger transaction and Capital asset transaction is calculated on the basis of the Amount posted, i.e. after the deduction of VAT. The amount is reduced by the same percentage as the Posted amount in relation to the Entered amount.

If the standard currency, given in the Company information table is defined as Currency type 2 or 3 in the Currency table, the Amount in EURO will be calculated with the exchange rate given for Euro in Sales rate field in the Currency table.

The transaction has been approved for payment in Visma.net Approval. When this token follows the payment, approval of the payment in Visma.net AutoPay should not be required.

Used in Visma.net AutoPay for viewing of invoices.

The Empl. no. is a unique number identifying one specific Employee.

Details about the payment can be seen using the View payment details processing.

When you transfer Customer transactions and Supplier transactions to the Payment line table, this bank account for the transactions will override the Bank account field from the Associate table. You can later override or delete the Bank account in the Payment line table.

The field is to be filled out manually with the amount from a bank statement and is used to reconciliate the amount when it is filled out by accumulating amounts from the Cross reference table.

The field has no function in electronic funds transfer.

If you have selected the Repeat info. check box in the Voucher type table, the value in this field is copied to the subsequent voucher line that have the same voucher no.

It is mandatory to fill out the field if the Debit account type field or the Credit account type field have the value 4 (Capital asset account) otherwise it will not be possible to update the Batch record

The field can be suggested on the basis of the Voucher type field in the Voucher table.

1 - Acquisition

To be used on records concerning the main acquisition of capital assets. E.g. cars, or buildings.

2 - Addition

To be used on records concerning additions. The definition of an "addition" is e.g. winter tyres for a car or marquises on a building. Additions can be given a lifetime, that differs from the main acquisition.

3 - Revaluation

To be used on records meant to adjust the total value of a capital asset. An example when a revaluation can be performed is when a very old real estate has a much higher market value, than the book value.

Note:

Revaluation shall NOT be performed when a capital asset has a lower value than expected due to under-usage, in this case the lifetime, and consequently the periodic depreciations, shall be adjusted instead.

Note:

Revaluation of capital assets is in most countries surrounded by legal restrictions and shall be performed only after accurate consideration.

4 - Devaluation

To be used on records meant to adjust the total value of a capital asset. An example when a devaluation can be performed is when the value of a real estate falls under the book value due to a financial crisis or another extraordinary occurrence.

Note:

Devaluation shall NOT be performed when a capital asset has a higher value than expected due to over-usage, in this case the lifetime, and consequently the periodic depreciations, shall be adjusted instead.

Note:

Devaluation of capital assets might be surrounded by legal restrictions in your country and shall be performed only after accurate consideration.

5 - Sale

To be used on records concerning sales of capital assets.

6 - Discarded

To be used on records concerning discard of capital assets.

7 - (Not in use)

Not in use.

8 - Back transfer

Resets depreciation when capital assets are sold or discarded.

9 - Depreciation on investment

10 - Depreciation on addition

11 - Depreciation on revaluation

12 - Depreciation on devaluation

When you complete the Amount field in a voucher line, the cash amount is displayed in the Cash amount and Cash amount in currency fields. You can override the value in these fields. If you only enter the Cash amount, the value in the Amount field is assigned the same value as the one in the Cash amount field. This is done when posting invoices, i.e. debiting customers or crediting suppliers. The calculated amount is dependent on settings in the Cash discount processing in the Company information table. Depending on settings in the Accounting processing in the Company information table, it might also be calculated on payment vouchers.

When you complete the Amount field in a voucher line, the cash amount is displayed in the Cash amount and Cash amount in currency fields. You can override the value in these fields. If you only enter the Cash amount, the value in the Amount field is assigned the same value as the one in the Cash amount field. This is done when posting invoices, i.e. debiting customers or crediting suppliers. The calculated amount is dependent on settings in the Cash discount processing in the Company information table. Depending on settings in the Accounting processing in the Company information table, it might also be calculated on payment vouchers.

The Cash due date is derived from Payment terms and the Voucher date field. If no Payment terms have been specified, the Cash due date field will be empty, and the Due date field is calculated on the basis of the Voucher date + 30 days. The Cash due date field is also empty if no credit days or months are specified for the Payment terms.

If the Cash due date field is empty when the Voucher is updated, it is assigned the same value as the Due date of the transactions.

The date is validated using the regional settings in Windows.

On incoming invoices you can enter a CID code (customer identification code) for use in the context of automatic funds transfers.

If the supplier uses giros with its own CID field, it is strongly recommended to quote the CID code when transferring payment. The CID code is normally made up of the invoice number, customer number and/or the due date.

For outgoing invoices from the order module, this field will be filled in with the CID code of the printed invoice.

The field shall only be used in combination with a Debit account or Credit account concerning customers and is to be used in businesses where one possesses and manage cash on a clients account, eg law firms.

1 - Outlay

2 - Client responsibility 1

3 - Client responsibility 2

4 - Client responsibility 3

The value is derived from the VAT amount and an eventual Cost % given in the VAT code table for the Debit VAT code or Credit VAT code given on the voucher.

The Cost amount will only be filled out on voucher lines with a Turnover class that produces both input and output VAT. It will not be filled out on voucher lines with a Turnover class that produces only input vat, for these voucher lines, the Cost amount will be calculated when updating the voucher.

Business NXT differentiates between general ledger accounts, capital asset accounts and customer / supplier ledger accounts on the basis of the account number ranges defined in the Account no. series table, or via the associated Account type field. When you enter an account number, the name of the customer, supplier, general ledger account or capital asset appears in the Status bar. This enables you to check that you have entered the correct number. You can decide whether to post a voucher on a single line containing both the debit account and credit account, or to use separate voucher lines for the debit and credit entries.

If you enter + in one of the fields for Debit account or Credit account and you have already filled in the Cust. no. or Sup. no. field, a cross-account is suggested. You define the cross-account for each individual customer and supplier in the Associate table. If a customer no. or a supplier no. is entered as debit account or credit account the cross account will be filled out automatically if given in the Associate table.

If you enter an account number in this field and it falls within the number series for customers, suppliers or capital assets, and then perform a look-up in the field, you call up a list of customers, suppliers or capital assets that have been entered.

You can edit the look-up window as a normal page element if you want to change the details for an existing customer, supplier, general ledger account or capital asset. The same applies if you want to create new ones. This requires that the look-up window has not been stored in the layout as non-editable.

When you enter a general ledger account number, the currency no., tax code and/or organisational unit will be suggested. When you enter a capital asset number, the tax code will be suggested if you have entered this for the capital asset. When you enter a customer / supplier number, the Currency no. field will be suggested if you have entered this for the customer or the supplier. If the Debit account and Credit account specify different codes, the account entered first is suggested. If you delete or change an account number once it is entered, the corresponding tax code field is deleted or changed accordingly.

When you enter a customer number or a supplier number in the Debit account or the Credit account field then the Cust. no. field or the Sup. no. field is updated with the same value. The same applies when you enter an Order no.

The customer number or supplier number is also included in the General ledger transaction record for sales/purchases.

If the value in the Debit account or the Credit account field is deleted, the values in the organisational units fields from that voucher are removed as well.

If you adhere to the account ranges defined in the Account no. series table, it is a good idea to hide the Debit account type and Credit account type fields. In this case, all account numbers are unique, and the account type is derived from the account number. The account type codes are defined permanently by the system.

1 - Customer

The account number refer to a customer.

2 - Supplier

The account number refer to a supplier.

3 - General ledger account

The account number refer to a general ledger account.

4 - Capital asset

The account number refer to a capital asset.

1 - Unexpanded automatic entry head

An automatic entry is defined for the general ledger account, but it is not expanded. You can expand it by selecting the processing Expand automatic entries in the Voucher table.

2 - Expanded automatic entry head

The voucher line has been expanded in one or more automatic entry lines, either automatically or using the processing Expand automatic entries.

3 - Automatic entry line

The voucher line is an automatic entry line defined for the relevant general ledger account in the Automatic entry table.

If a Turnover class has been entered for a Voucher type record, this turnover class is suggested when you enter a value in the Voucher type field on the Voucher line. The value in the Credit turnover cl. field is not overwritten when you fill in the Debit account or the Credit account field.

If Turnover class has not been entered on the Voucher type record, the Credit turnover cl. field is suggested when the following is entered in the Debit account or Credit account fields:

• a customer no. or supplier no., and VAT code cust. or VAT code sup. field and area have been entered for the customer/supplier.
• a number and turnover class has been entered for the general ledger account.

If you enter a value both in the Debit account and the Credit account field, the turnover class for the relevant general ledger account is used.

The General ledger transaction are entered for the turnover class, and form the basis for printing tax statements.

On vouchers with general ledger entries for sales and purchases that are generated on the basis of orders, the turnover class is defined on the basis of the Transaction type, Trade area and Service type fields.

1 - Taxable sales

Is used for sales of taxable products. I.e. when

• the Transaction type is 1 - Sales or 2 - Hire
• the Trade area is 0 - Taxable domestic according to VAT- and accounting inf./VAT code

2 - Non-taxable domestic sales

Is used for sales of non-taxable products. I.e. when

• the Transaction type is 1 - Sales or 2 - Hire
• the Trade area is 1 - Non-taxable domestic

10 - Transfer of goods to EU countries

Used when

• the Transaction type is 1 - Sales or 2 - Hire
• the Trade area is 4 - Subsidiary in another EU country
• Service type1 - Services is not selected

5 - Sale of goods to EU countries

Used when

• the Transaction type is 1 - Sales or 2 - Hire
• the Trade area is 2 - Within other EU country
• Service type1 - Services is not selected

3 - Sale of goods outside EU/Abroad

Used when

• the Transaction type is 1 - Sales or 2 - Hire
• the Trade area is 3 - Outside EU/Abroad
• Service type1 - Services is not selected

9 - Sale of services abroad

Used when

• the Transaction type is 1 - Sales or 2 - Hire
• the Trade area is 2 - Within other EU country, 3 - Outside EU/Abroad or 4 - Subsidiary in another EU country
• Service type1 - Services is selected

13 - Non-taxable sales

16 - Sales outside tax area

18 - Sales, taxable for purchaser

20 - Agent sales to third party

22 - Sales of services to EU countries

26 - Rent income voluntary

27 - OSS union scheme services

28 - OSS union scheme goods

29 - OSS import scheme

4 - Taxable purchases

Is used for purchases of taxable products. I.e. when

• the Transaction type is 6 - Purchase
• the Trade area is 0 - Taxable domestic according to VAT- and accounting inf./VAT code

7 - Non-taxable domestic purchases

Is used for purchases of non-taxable products. I.e. when

• the Transaction type is 6 - Purchase
• the Trade area is 1 - Non-taxable domestic

15 - Domestic purchases with reversed VAT deduction

11 - Transfer of goods between other EU countries

Used when

• the Transaction type is 6 - Purchase
• the Trade area is 5 - Transfer between other EU countries
• Service type1 - Services is not selected

6 - Purchase of goods from EU countries

Used when

• the Transaction type is 6 - Purchase
• the Trade area is 2 - Within other EU country
• Service type1 - Services is not selected

8 - Purchase of goods outside EU/Abroad

Used when

• the Transaction type is 6 - Purchase
• the Trade area is 3 - Outside EU/Abroad
• Service type1 - Services is not selected

12 - Purchase of services abroad

Used when

• the Transaction type is 6 - Purchase
• the Trade area is 2 - Within other EU country or 5 - Transfer between other EU countries
• Service type1 - Services is selected

14 - Non-taxable purchases

17 - Purchase outside tax area

19 - Purchase, taxable by purchaser

21 - Purchase of services from EU countries

23 - Domestic purchase of services

24 - Taxable product consumption

25 - Domestic purchases with reversed VAT liability

Tax computation is performed when the vouchers are updated. You enter the gross amounts in the vouchers. Business NXT subtracts any VAT and posts it to the specified tax accounts. You can neglect entering a value in the Credit VAT code field and post the taxes manually to the tax account on a separate voucher if you wish. This is however not recommended, since you will not be able to use the standard VAT report form distributed with the program.

If you enter vouchers for a general ledger account or capital asset account with a defined VAT code, this VAT code is suggested. The cursor will move to the next field. You can return to the Credit VAT code field and change the code even if the cursor does not pause there.

If you enter a value in the Cust. no. or Sup. no. field, the customers/suppliers tax code will be suggested. This applies if you have selected Suggest VAT code in the Customer options field and in the Supplier options field respectively in the Associate table.

Exception 1 If you have selected Enter VAT code in the General ledger account table for the Account no. for which you are posting the voucher, the cursor will always pause in the Credit VAT code field.

Exception 2 If you have selected Ignore VAT code in the Voucher type table for the Voucher type used to post the voucher then the Credit VAT code is not suggested, even if one is defined for the General ledger account.

If there is no Turnover class on the General ledger account, it will be retrieved from the VAT code.

If you delete the value in the Credit VAT code field, the VAT amount will be removed in the voucher. This does not apply if you have overridden the VAT amount.

The Reference field on open customer / supplier entries will be matched against the Cross reference on payment vouchers if 4 - Entered references is chosen as the Matching method in the Company information table.

Normally the voucher is filled in with Customer no or a Supplier no in the Credit account or Debit account field. If a Cross reference thereafter is entered that matches the Reference on an open entry for the entered Customer no or Supplier no, the Outstanding amount and Outstanding amount in currency fields from the Open customer entry/Open supplier entry tables will be copied to the Amount and Amount in currency fields. If the vouchers Voucher date is within the open entries Cash due date, the Rest cash amount and Rest cash amount in currency will update the Amount and Amount in currency fields.

A look-up can be performed to get an overview over the open entries. If <Ctrl>+<Enter> is pressed, the Outstanding amount in currency and Outstanding amount in currency fields from the focused open entry will be copied into the voucher line. (Or the Rest cash amount and Rest cash amount in currency fields if the Voucher date falls within the Cash due date. The Reference will be copied to the voucher line`s Cross reference field.

If the open entry in the look-up is highlighted, and <Ctrl>+<Enter> is pressed only the amounts will be copied and the Cross reference will be reflected on a new line in the Cross reference table instead of in the Cross reference field.

If more than one open entry in the look-up is highlighted, and <Ctrl>+<Enter> is pressed, the sum of the open entries will be copied to the amount fields and all the open entries Cross reference will be reflected on new lines in the Cross reference table.

If a voucher type with the option Copy voucher no. to order line has been used on the voucher and a look-up is performed, the open entries related to the customer no / supplier no entered as Credit account or Debit account will be copied to the Cross reference. In the Cross reference table, the field Payment reg. can be ticked, to distribute the invoice amount to the Amount and the Amount in currency fields in the voucher. A part payment can also be registered in the Part payment or Part payment in currency field in the Cross reference table, this will only distribute the part payment amount to the Amount and the Amount in currency fields in the Voucher table.

If no Customer no or Supplier no is entered as Credit account or Debit account on the voucher and a value is entered in the Cross reference field, a search for an open entry with a matching reference will be performed, where the Open customer entry will be searched prior to the Open supplier entry. If a match is found, the amount will be filled in from the open entry and the Customer no / supplier no will be filled in as Credit account or Debit account.

When you enter an account number, a Currency no. with its associated Calculate rate is suggested if one is defined for the general ledger account, customer, supplier or capital asset in question. If a voucher is posted to two accounts with references to different currency codes, the currency is determined by the account entered first. The cursor can be forced to stop in the field by the option Enter currency in the Voucher type.

When you enter vouchers in the currency defined for the account, a separate currency balance is maintained in the Customer balance, Supplier balance or General ledger balance tables after updating the voucher.

The field is filled out automatically if a customer no is used in the Debit account or the Credit account field.

If the field is already filled in, the value is overwritten by the bank reconciliation system. If bank reconciliation is not in use the field can be used manually, or an external application can use the field via BIG.

The date is validated using the regional settings in Windows.

If the field is already filled in, the value is overwritten by the bank reconciliation system. If bank reconciliation is not in use the field can be used manually, or an external application can use the field via BIG.

The date is validated using the regional settings in Windows.

Business NXT differentiates between general ledger accounts, capital asset accounts and customer / supplier ledger accounts on the basis of the account number ranges defined in the Account no. series table, or via the associated Account type field. When you enter an account number, the name of the customer, supplier, general ledger account or capital asset appears in the Status bar. This enables you to check that you have entered the correct number. You can decide whether to post a voucher on a single line containing both the debit account and credit account, or to use separate voucher lines for the debit and credit entries.

If you enter + in one of the fields for Debit account or Credit account and you have already filled in the Cust. no. or Sup. no. field, a cross-account is suggested. You define the cross-account for each individual customer and supplier in the Associate table. If a customer no. or a supplier no. is entered as debit account or credit account the cross account will be filled out automatically if given in the Associate table.

If you enter an account number in this field and it falls within the number series for customers, suppliers or capital assets, and then perform a look-up in the field, you call up a list of customers, suppliers or capital assets that have been entered.

You can edit the look-up window as a normal page element if you want to change the details for an existing customer, supplier, general ledger account or capital asset. The same applies if you want to create new ones. This requires that the look-up window has not been stored in the layout as non-editable.

When you enter a general ledger account number, the currency no., tax code and/or organisational unit will be suggested. When you enter a capital asset number, the tax code will be suggested if you have entered this for the capital asset. When you enter a customer / supplier number, the Currency no. field will be suggested if you have entered this for the customer or the supplier. If the Debit account and Credit account specify different codes, the account entered first is suggested. If you delete or change an account number once it is entered, the corresponding tax code field is deleted or changed accordingly.

When you enter a customer number or a supplier number in the Debit account or the Credit account field then the Cust. no. field or the Sup. no. field is updated with the same value. The same applies when you enter an Order no.

The customer number or supplier number is also included in the General ledger transaction record for sales/purchases.

If the value in the Debit account or the Credit account field is deleted, the values in the organisational units fields from that voucher are removed as well.

If you adhere to the account ranges defined in the Account no. series table, it is a good idea to hide the Debit account type and Credit account type fields. In this case, all account numbers are unique, and the Debit account type is derived from the account number.

1 - Customer

The account number refer to a customer.

2 - Supplier

The account number refer to a supplier.

3 - General ledger account

The account number refer to a general ledger account.

4 - Capital asset

The account number refer to a capital asset.

1 - Unexpanded automatic entry head

An automatic entry is defined for the general ledger account, but it is not expanded. You can expand it by selecting the processing Expand automatic entries in the Voucher table.

2 - Expanded automatic entry head

The voucher line has been expanded in one or more automatic entry lines, either automatically or using the processing Expand automatic entries.

3 - Automatic entry line

The voucher line is an automatic entry line defined for the relevant general ledger account in the Automatic entry table.

If a Turnover class has been entered for a Voucher type record, this turnover class is suggested when you enter a value in the Voucher type field on the Voucher line. The value in the Credit turnover cl. field is not overwritten when you fill in the Debit account or the Credit account field.

If Turnover class has not been entered on the Voucher type record, the Credit turnover cl. field is suggested when the following is entered in the Debit account or Credit account fields:

• a customer no. or supplier no., and VAT code cust. or VAT code sup. field and area have been entered for the customer/supplier.
• a number and turnover class has been entered for the general ledger account.

If you enter a value both in the Debit account and the Credit account field, the turnover class for the relevant general ledger account is used.

The General ledger transaction are entered for the turnover class, and form the basis for printing tax statements.

On vouchers with general ledger entries for sales and purchases that are generated on the basis of orders, the turnover class is defined on the basis of the Transaction type, Trade area and Service type fields.

1 - Taxable sales

Is used for sales of taxable products. I.e. when

• the Transaction type is 1 - Sales or 2 - Hire
• the Trade area is 0 - Taxable domestic according to VAT- and accounting inf./VAT code

2 - Non-taxable domestic sales

Is used for sales of non-taxable products. I.e. when

• the Transaction type is 1 - Sales or 2 - Hire
• the Trade area is 1 - Non-taxable domestic

10 - Transfer of goods to EU countries

Used when

• the Transaction type is 1 - Sales or 2 - Hire
• the Trade area is 4 - Subsidiary in another EU country
• Service type1 - Services is not selected

5 - Sale of goods to EU countries

Used when

• the Transaction type is 1 - Sales or 2 - Hire
• the Trade area is 2 - Within other EU country
• Service type1 - Services is not selected

3 - Sale of goods outside EU/Abroad

Used when

• the Transaction type is 1 - Sales or 2 - Hire
• the Trade area is 3 - Outside EU/Abroad
• Service type1 - Services is not selected

9 - Sale of services abroad

Used when

• the Transaction type is 1 - Sales or 2 - Hire
• the Trade area is 2 - Within other EU country, 3 - Outside EU/Abroad or 4 - Subsidiary in another EU country
• Service type1 - Services is selected

13 - Non-taxable sales

16 - Sales outside tax area

18 - Sales, taxable for purchaser

20 - Agent sales to third party

22 - Sales of services to EU countries

26 - Rent income voluntary

27 - OSS union scheme services

28 - OSS union scheme goods

29 - OSS import scheme

4 - Taxable purchases

Is used for purchases of taxable products. I.e. when

• the Transaction type is 6 - Purchase
• the Trade area is 0 - Taxable domestic according to VAT- and accounting inf./VAT code

7 - Non-taxable domestic purchases

Is used for purchases of non-taxable products. I.e. when

• the Transaction type is 6 - Purchase
• the Trade area is 1 - Non-taxable domestic

15 - Domestic purchases with reversed VAT deduction

11 - Transfer of goods between other EU countries

Used when

• the Transaction type is 6 - Purchase
• the Trade area is 5 - Transfer between other EU countries
• Service type1 - Services is not selected

6 - Purchase of goods from EU countries

Used when

• the Transaction type is 6 - Purchase
• the Trade area is 2 - Within other EU country
• Service type1 - Services is not selected

8 - Purchase of goods outside EU/Abroad

Used when

• the Transaction type is 6 - Purchase
• the Trade area is 3 - Outside EU/Abroad
• Service type1 - Services is not selected

12 - Purchase of services abroad

Used when

• the Transaction type is 6 - Purchase
• the Trade area is 2 - Within other EU country or 5 - Transfer between other EU countries
• Service type1 - Services is selected

14 - Non-taxable purchases

17 - Purchase outside tax area

19 - Purchase, taxable by purchaser

21 - Purchase of services from EU countries

23 - Domestic purchase of services

24 - Taxable product consumption

25 - Domestic purchases with reversed VAT liability

Tax computation is performed when the vouchers are updated. You enter the gross amounts in the vouchers. Business NXT subtracts any VAT and posts it to the specified tax accounts. In the case of investment tax, Business NXT calculates both the tax basis and the tax itself, and posts them to the specified general ledger account. You can set the Debit VAT code field to 0 and post the taxes manually to the tax account if you wish.

If you enter vouchers for a general ledger account or capital asset account with a defined VAT code, this VAT code is suggested. The cursor will move to the next field. You can return to the Debit VAT code field and change the code even if the cursor does not pause there.

If you enter a customer no. or supplier no., the customers/suppliers tax code will be suggested. This applies if you have selected Suggest VAT code in the Customer options field and in the Supplier options field respectively in the Associate table.

Exception 1 If you have selected Enter VAT code in the General ledger account table for the account no. for which you are posting the voucher, the cursor will always pause in the Debit VAT code field.

Exception 2 If you have selected Ignore VAT code in the Voucher type table for the voucher type used to post the voucher, the Debit VAT code field is not suggested, even if one is defined for the general ledger account.

A general ledger account that is taxable (defined as Turnover class 1 - Taxable sales or 4 - Taxable purchases) must have a Debit VAT code that calculates output or input VAT. The turnover class determines the general ledger accounts to be added up in the total taxable purchases and sales for the tax statement. These figures will not correspond with the taxes posted if vouchers have been posted with a debit VAT code that does not correspond to the turnover class.

If there is no turnover class in the general ledger account, it will be retrieved from the VAT code table.

If you delete the VAT code, the VAT amount will be removed in the voucher. This does not apply if you have overridden the VAT amount.

The date is validated using the regional settings in Windows.

The value in this field is transferred to Updated voucher, Open supplier entry and Supplier transaction tables when voucher lines are updated.

Shows the difference between the Bank amount field and the total of the entries which have a cross in the Payment reg. field in the linked Cross reference table. This functionality is to be used only when entering payment vouchers and only when using a voucher type with the option Copy open entries on lookup.

The distribution key can combine a number of organisational units.

If a voucher is entered for two general ledger accounts with different distribution key, the distribution key is determined by the general ledger account entered first. If an organisational unit is defined in the same voucher line (see previous field), the distribution key only applies to any other organisational unit classes. A distribution key does not need to add up to 100 %.

The date is suggested on the basis of the Voucher date and Payment terms fields. In the case of payments and credit notes with no due date defined, Business NXT sets the Due date field equal to the Voucher date field. The due date for credit notes is normally set as the same as the due date for the invoice to prevent interest computation.

You can override the Due date field in the voucher line, or after the voucher has been updated, in the Open customer entry and Open supplier entry tables.

The Due date field is a date field, which you must enter in the format defined in the regional settings in Windows. You only need to enter the dates and month number for dates in the current year. A check is performed to ensure the date entered is valid.

If you enter + in the field, the system copies the date from the Voucher date. If you enter / in the field, the system copies the date from the last voucher. The cursor moves to the next field which means you do not have to press Enter.

If no payment terms is given on the voucher, the value from the Standard payment terms. field in the Company information table will be used.

The date is validated using the regional settings in Windows.

You define valid values and related texts in the Text table. The values are included in open supplier entries and transactions and then to payment lines in connection with payment suggestions. You can enter help and valid values in the Text table. This text can be made mandatory in the function Mandatory text types in the Company information table. The field is not overwritten by the value in the corresponding field in the Associate table if it is filled in, but retains the original value. The field is in use for Swedish payment formats.

You define valid values and related texts in the Text table. The values are included in open supplier entries and transactions and then to payment lines in connection with payment suggestions. You can enter help and valid values in the Text table. This text can be made mandatory in the function Mandatory text types in the Company information table. The field is not overwritten by the value in the corresponding field in the Associate table if it is filled in, but retains the original value. The field is in use for Swedish payment formats.

You define valid values and related texts in the Declaration code table. The values are included in open supplier entries and transactions and then to payment lines in connection with payment suggestions. This text can be made mandatory in the function Mandatory text types in the Company information table.

You define valid values and related texts in the Text table. The values are included in open supplier entries and transactions and then to payment lines in connection with payment suggestions. You can enter help and valid values in the Text table. This text can be made mandatory in the function Mandatory text types in the Company information table. The field is in use for Swedish payment formats.

The Empl. no. is a unique number identifying one specific Employee.

If Enter currency is checked for the voucher type used, the cursor pauses in the Currency no. and Amount in currency fields and skips the (domestic currency) Amount field. The value in the Amount field is calculated as soon as the Amount in currency field is entered, or if the Currency no., Exchange rate or Amount in currency fields are changed. If the Amount field is changed, the Amount in currency is amended accordingly, with the rate remaining unchanged. However, if you want the Exchange rate field to change when you change the Amount in currency or Amount, you must check the Calculate cur. rate field in the Voucher type table.

In the same way as amounts in the domestic currency, the foreign currency amounts are added up for general ledger accounts, customers and suppliers, and you can print out these on account statements and balance lists. Business NXT only stores the balance in the balance tables for the currency code defined for the particular account, as well as the balance in the domestic currency.

If the amount is entered in the domestic currency, the balance for the customer is not accumulated in the foreign currency when the voucher is updated, even if the Currency no. is entered for the customer. Similarly, if no currency no. is defined for the sales account in the General ledger account, no general ledger balance will be calculated in foreign currency.

When you enter a value in the Currency no. 2 field in the voucher line, Exchange rate 2 is suggested from the Currency rate 2 table. If you have selected the Update exchange rate from voucher date field under Voucher type processing in the Voucher type field and change the value in the Voucher date, Value date and Currency no. fields in the voucher line, Exchange rate 2 is retrieved from the first row that has From date >= Voucher date. If the voucher date is not entered in the voucher line, the Value date field is used. If the Value date field in the voucher line is not entered, the Value date field in the batch head or the current date is used.

In the Associate table you can specify that one or more customers/suppliers are exempt from reminders and/or interest computation/payment suggestions. These settings can be changed for each invoice voucher by entering a code in the Exempt field. You can exempt an invoice from reminders, payment suggestions and/or interest computation, even after a voucher has been updated, in the Open customer entry and Open supplier entry tables.

All of the codes are relevant for outgoing invoices. Only code 1 - No reminders/payment is relevant for incoming invoices. This exempts the invoice from payment suggestions. You can also use this code to enter an incoming invoice that you know has already been paid, to avoid paying twice.

1 - No reminders/payment

2 - No interest

3 - No reminders or interest

4 - No debt collection

This check box is suggested when you enter the Voucher type field in the voucher. Vouchers with a check from expanding automatic entries on the manual entry of vouchers are also exempted.

If the field is already filled in, the value is overwritten by the bank reconciliation system. The field is updated from vouchers. If bank reconciliation is not in use the field can be used manually.

If the field is already filled in, the value is overwritten by the bank reconciliation system. The field is updated from vouchers. If bank reconciliation is not in use the field can be used manually.

If the field is already filled in, the value is overwritten by the bank reconciliation system. The field is updated from vouchers. If bank reconciliation is not in use the field can be used manually.

This could be for example freight and customs. If you have entered the current currency in the field, Business NXT suggests the field in the default currency, provided that the exchange rate is in the voucher. The Fixed amount in EURO field displays the value in the Fixed amount in currency field converted into EURO.

See explanation of the field in the text under Fixed amount field.

See explanation of the field in the text under Fixed amount field.

The field is transferred from the Voucher table to the Updated voucher, Supplier transaction and Open supplier entry tables. The field is subsequently transferred from Open supplier entry to the Payment line table.

When you generate new batches on the basis of updated batches/vouchers, the field is also transferred back from updated batches to vouchers.

This field is used for order match functionality.

The field is to be used only on voucher with customer invoices. In case of late payment and interest invoicing, this amount will be deducted from the invoice amount before interest calculation.

The field is to be used only on vouchers with customer invoices. In case of late payment and interest invoicing, this amount will be deducted from the invoice amount before interest calculation.

The cursor only pauses in the Interest rate field when a customer account number is entered in the voucher. The interest rate specified for the customer in the Associate table is suggested. If the customer's Interest rate field is blank, the default interest rate for the customer's country number, as defined in the Country table, is suggested. If you want to apply another interest rate to an outgoing invoice, you can enter it in this field. You will then be able to use different interest rates when printing out interest notes for a single customer.

This field is intended for decimal figures. The field will only accept figures, full stops and commas. The decimal separator will be the one you have defined in Windows for each workstation.

The Invoice no. field is crucial on vouchers regarding customer invoices or supplier invoices. If it is not filled in manually, it will be updated with the same value as the Voucher no. field when the voucher is updated. The Invoice no. field will also be copied to the Reference field, when the voucher is updated, unless the Reference field has been filled in manually.

If you do not specify a file name yourself, a file name will be suggested.

On the Editing menu, click Memo to create a new memo or to view the existing memo. The memo file name is saved in this text box.

Double-click or press * to open the Select file dialog box to manually select a memo file.

The actual memo is stored in the Memo table.

If both Order no. and Product no. fields are filled in in a line, you can make Business NXT update the order with a new order line when you update the batch. This assumes that you use a Voucher type which has the value 1 - Update order in the Update order field and that a product number is entered in the Product no. field.

If the Order no. field has been filled in and you are using a Voucher type which has the value 2 - Update prepayment status in the Update order field, the specified order will be updated so that the barred advance order is released for further processing. A test will be performed to determine whether the amount on the voucher line is as large or larger in order for the order to be released. The voucher number will be transferred to the order's Invoice reference so that the invoice for this order will be matched against this payment.

When the Order no. field is entered in the Voucher table you can link to the Order line table to see the order lines on receipt of invoice/authorisation.

It keeps flags for fields that are lacking mandatory values, in accordance with the selections made in the fields for Organisational unit processing in the General ledger account table. (This forms the basis of the red question marks in the fields.)

The field can also be processed further in BIG for example. Further processing of the field has not been implemented.

It is not possible to edit in this field.

Organisational unit 1

Organisational unit 2

Organisational unit 3

Organisational unit 4

Organisational unit 5

Organisational unit 6

Organisational unit 7

Organisational unit 8

Organisational unit 9

Organisational unit 10

Organisational unit 11

Organisational unit 12

The Voucher window includes one field for each organisational unit class defined in the Company information table. These fields may for example be named "Department" or "Project", and refer to the relevant organisational unit tables. You can therefore post the same voucher for both a department and a project, for example.

If you distribute vouchers by organisational unit, you can print separate reports for one or more organisational units without dividing them between different general ledger accounts. If you create hierarchies of organisational units, for example to divide a project into a main project and a sub-project, you can produce detailed reports on two levels. You choose you own subtotal level and the information/selection to be included. For example, you can print PL and balance sheet reports, balance lists and account statements for one or more organisational units.

Business NXT suggests the organisational unit where a permanent link is defined to the relevant general ledger account. If the general ledger account indicates that the organisational unit class should be entered, the organisational unit defined for the batch is suggested. If you enter a voucher for two general ledger accounts with different organisational units, the organisational unit is determined by the account entered first. If you enter an organisational unit, this will be used in preference to any distribution key for the same organisational unit class.

When you enter a customer/supplier number in the fields for debit/credit when entering a voucher, the organisational unit is retrieved from the Associate table.

The cursor only pauses in the organisational unit field if you have selected the Organisational unit processing box for the Debit account or Credit account. Even if the cursor skips the organisational unit field in a voucher line, you can always use the arrow keys to return to the field and edit it. When you enter an organisational unit number, the name of the organisational unit is displayed in the Status bar, so that you can check that you have entered the right number.

If neither debit account or credit account is entered with the value 1-3 in Organisational unit processing, you will be warned and you will not be able to enter an organisational unit in the voucher.

You will also receive messages if you use incorrect combinations of accounts and organisational units which you have defined in the Combination group, User combination group and Combination matrix tables.

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.

The Voucher window includes one field for each organisational unit class defined in the Company information table. These fields may for example be named "Department" or "Project", and refer to the relevant organisational unit tables. You can therefore post the same voucher for both a department and a project, for example.

If you distribute vouchers by organisational unit, you can print separate reports for one or more organisational units without dividing them between different general ledger accounts. If you create hierarchies of organisational units, for example to divide a project into a main project and a sub-project, you can produce detailed reports on two levels. You choose you own subtotal level and the information/selection to be included. For example, you can print PL and balance sheet reports, balance lists and account statements for one or more organisational units.

Business NXT suggests the organisational unit where a permanent link is defined to the relevant general ledger account. If the general ledger account indicates that the organisational unit class should be entered, the organisational unit defined for the batch is suggested. If you enter a voucher for two general ledger accounts with different organisational units, the organisational unit is determined by the account entered first. If you enter an organisational unit, this will be used in preference to any distribution key for the same organisational unit class.

When you enter a customer/supplier number in the fields for debit/credit when entering a voucher, the organisational unit is retrieved from the Associate table.

The cursor only pauses in the organisational unit field if you have selected the Organisational unit processing box for the Debit account or Credit account. Even if the cursor skips the organisational unit field in a voucher line, you can always use the arrow keys to return to the field and edit it. When you enter an organisational unit number, the name of the organisational unit is displayed in the Status bar, so that you can check that you have entered the right number.

If neither debit account or credit account is entered with the value 1-3 in Organisational unit processing, you will be warned and you will not be able to enter an organisational unit in the voucher.

You will also receive messages if you use incorrect combinations of accounts and organisational units which you have defined in the Combination group, User combination group and Combination matrix tables.

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.

The Voucher window includes one field for each organisational unit class defined in the Company information table. These fields may for example be named "Department" or "Project", and refer to the relevant organisational unit tables. You can therefore post the same voucher for both a department and a project, for example.

If you distribute vouchers by organisational unit, you can print separate reports for one or more organisational units without dividing them between different general ledger accounts. If you create hierarchies of organisational units, for example to divide a project into a main project and a sub-project, you can produce detailed reports on two levels. You choose you own subtotal level and the information/selection to be included. For example, you can print PL and balance sheet reports, balance lists and account statements for one or more organisational units.

Business NXT suggests the organisational unit where a permanent link is defined to the relevant general ledger account. If the general ledger account indicates that the organisational unit class should be entered, the organisational unit defined for the batch is suggested. If you enter a voucher for two general ledger accounts with different organisational units, the organisational unit is determined by the account entered first. If you enter an organisational unit, this will be used in preference to any distribution key for the same organisational unit class.

When you enter a customer/supplier number in the fields for debit/credit when entering a voucher, the organisational unit is retrieved from the Associate table.

The cursor only pauses in the organisational unit field if you have selected the Organisational unit processing box for the Debit account or Credit account. Even if the cursor skips the organisational unit field in a voucher line, you can always use the arrow keys to return to the field and edit it. When you enter an organisational unit number, the name of the organisational unit is displayed in the Status bar, so that you can check that you have entered the right number.

If neither debit account or credit account is entered with the value 1-3 in Organisational unit processing, you will be warned and you will not be able to enter an organisational unit in the voucher.

You will also receive messages if you use incorrect combinations of accounts and organisational units which you have defined in the Combination group, User combination group and Combination matrix tables.

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.

The Voucher window includes one field for each organisational unit class defined in the Company information table. These fields may for example be named "Department" or "Project", and refer to the relevant organisational unit tables. You can therefore post the same voucher for both a department and a project, for example.

If you distribute vouchers by organisational unit, you can print separate reports for one or more organisational units without dividing them between different general ledger accounts. If you create hierarchies of organisational units, for example to divide a project into a main project and a sub-project, you can produce detailed reports on two levels. You choose you own subtotal level and the information/selection to be included. For example, you can print PL and balance sheet reports, balance lists and account statements for one or more organisational units.

Business NXT suggests the organisational unit where a permanent link is defined to the relevant general ledger account. If the general ledger account indicates that the organisational unit class should be entered, the organisational unit defined for the batch is suggested. If you enter a voucher for two general ledger accounts with different organisational units, the organisational unit is determined by the account entered first. If you enter an organisational unit, this will be used in preference to any distribution key for the same organisational unit class.

When you enter a customer/supplier number in the fields for debit/credit when entering a voucher, the organisational unit is retrieved from the Associate table.

The cursor only pauses in the organisational unit field if you have selected the Organisational unit processing box for the Debit account or Credit account. Even if the cursor skips the organisational unit field in a voucher line, you can always use the arrow keys to return to the field and edit it. When you enter an organisational unit number, the name of the organisational unit is displayed in the Status bar, so that you can check that you have entered the right number.

If neither debit account or credit account is entered with the value 1-3 in Organisational unit processing, you will be warned and you will not be able to enter an organisational unit in the voucher.

You will also receive messages if you use incorrect combinations of accounts and organisational units which you have defined in the Combination group, User combination group and Combination matrix tables.

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.

The Voucher window includes one field for each organisational unit class defined in the Company information table. These fields may for example be named "Department" or "Project", and refer to the relevant organisational unit tables. You can therefore post the same voucher for both a department and a project, for example.

If you distribute vouchers by organisational unit, you can print separate reports for one or more organisational units without dividing them between different general ledger accounts. If you create hierarchies of organisational units, for example to divide a project into a main project and a sub-project, you can produce detailed reports on two levels. You choose you own subtotal level and the information/selection to be included. For example, you can print PL and balance sheet reports, balance lists and account statements for one or more organisational units.

Business NXT suggests the organisational unit where a permanent link is defined to the relevant general ledger account. If the general ledger account indicates that the organisational unit class should be entered, the organisational unit defined for the batch is suggested. If you enter a voucher for two general ledger accounts with different organisational units, the organisational unit is determined by the account entered first. If you enter an organisational unit, this will be used in preference to any distribution key for the same organisational unit class.

When you enter a customer/supplier number in the fields for debit/credit when entering a voucher, the organisational unit is retrieved from the Associate table.

The cursor only pauses in the organisational unit field if you have selected the Organisational unit processing box for the Debit account or Credit account. Even if the cursor skips the organisational unit field in a voucher line, you can always use the arrow keys to return to the field and edit it. When you enter an organisational unit number, the name of the organisational unit is displayed in the Status bar, so that you can check that you have entered the right number.

If neither debit account or credit account is entered with the value 1-3 in Organisational unit processing, you will be warned and you will not be able to enter an organisational unit in the voucher.

You will also receive messages if you use incorrect combinations of accounts and organisational units which you have defined in the Combination group, User combination group and Combination matrix tables.

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.

The Voucher window includes one field for each organisational unit class defined in the Company information table. These fields may for example be named "Department" or "Project", and refer to the relevant organisational unit tables. You can therefore post the same voucher for both a department and a project, for example.

If you distribute vouchers by organisational unit, you can print separate reports for one or more organisational units without dividing them between different general ledger accounts. If you create hierarchies of organisational units, for example to divide a project into a main project and a sub-project, you can produce detailed reports on two levels. You choose you own subtotal level and the information/selection to be included. For example, you can print PL and balance sheet reports, balance lists and account statements for one or more organisational units.

Business NXT suggests the organisational unit where a permanent link is defined to the relevant general ledger account. If the general ledger account indicates that the organisational unit class should be entered, the organisational unit defined for the batch is suggested. If you enter a voucher for two general ledger accounts with different organisational units, the organisational unit is determined by the account entered first. If you enter an organisational unit, this will be used in preference to any distribution key for the same organisational unit class.

When you enter a customer/supplier number in the fields for debit/credit when entering a voucher, the organisational unit is retrieved from the Associate table.

The cursor only pauses in the organisational unit field if you have selected the Organisational unit processing box for the Debit account or Credit account. Even if the cursor skips the organisational unit field in a voucher line, you can always use the arrow keys to return to the field and edit it. When you enter an organisational unit number, the name of the organisational unit is displayed in the Status bar, so that you can check that you have entered the right number.

If neither debit account or credit account is entered with the value 1-3 in Organisational unit processing, you will be warned and you will not be able to enter an organisational unit in the voucher.

You will also receive messages if you use incorrect combinations of accounts and organisational units which you have defined in the Combination group, User combination group and Combination matrix tables.

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.

The Voucher window includes one field for each organisational unit class defined in the Company information table. These fields may for example be named "Department" or "Project", and refer to the relevant organisational unit tables. You can therefore post the same voucher for both a department and a project, for example.

If you distribute vouchers by organisational unit, you can print separate reports for one or more organisational units without dividing them between different general ledger accounts. If you create hierarchies of organisational units, for example to divide a project into a main project and a sub-project, you can produce detailed reports on two levels. You choose you own subtotal level and the information/selection to be included. For example, you can print PL and balance sheet reports, balance lists and account statements for one or more organisational units.

Business NXT suggests the organisational unit where a permanent link is defined to the relevant general ledger account. If the general ledger account indicates that the organisational unit class should be entered, the organisational unit defined for the batch is suggested. If you enter a voucher for two general ledger accounts with different organisational units, the organisational unit is determined by the account entered first. If you enter an organisational unit, this will be used in preference to any distribution key for the same organisational unit class.

When you enter a customer/supplier number in the fields for debit/credit when entering a voucher, the organisational unit is retrieved from the Associate table.

The cursor only pauses in the organisational unit field if you have selected the Organisational unit processing box for the Debit account or Credit account. Even if the cursor skips the organisational unit field in a voucher line, you can always use the arrow keys to return to the field and edit it. When you enter an organisational unit number, the name of the organisational unit is displayed in the Status bar, so that you can check that you have entered the right number.

If neither debit account or credit account is entered with the value 1-3 in Organisational unit processing, you will be warned and you will not be able to enter an organisational unit in the voucher.

You will also receive messages if you use incorrect combinations of accounts and organisational units which you have defined in the Combination group, User combination group and Combination matrix tables.

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

The Voucher window includes one field for each organisational unit class defined in the Company information table. These fields may for example be named "Department" or "Project", and refer to the relevant organisational unit tables. You can therefore post the same voucher for both a department and a project, for example.

If you distribute vouchers by organisational unit, you can print separate reports for one or more organisational units without dividing them between different general ledger accounts. If you create hierarchies of organisational units, for example to divide a project into a main project and a sub-project, you can produce detailed reports on two levels. You choose you own subtotal level and the information/selection to be included. For example, you can print PL and balance sheet reports, balance lists and account statements for one or more organisational units.

Business NXT suggests the organisational unit where a permanent link is defined to the relevant general ledger account. If the general ledger account indicates that the organisational unit class should be entered, the organisational unit defined for the batch is suggested. If you enter a voucher for two general ledger accounts with different organisational units, the organisational unit is determined by the account entered first. If you enter an organisational unit, this will be used in preference to any distribution key for the same organisational unit class.

When you enter a customer/supplier number in the fields for debit/credit when entering a voucher, the organisational unit is retrieved from the Associate table.

The cursor only pauses in the organisational unit field if you have selected the Organisational unit processing box for the Debit account or Credit account. Even if the cursor skips the organisational unit field in a voucher line, you can always use the arrow keys to return to the field and edit it. When you enter an organisational unit number, the name of the organisational unit is displayed in the Status bar, so that you can check that you have entered the right number.

If neither debit account or credit account is entered with the value 1-3 in Organisational unit processing, you will be warned and you will not be able to enter an organisational unit in the voucher.

You will also receive messages if you use incorrect combinations of accounts and organisational units which you have defined in the Combination group, User combination group and Combination matrix tables.

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

The Voucher window includes one field for each organisational unit class defined in the Company information table. These fields may for example be named "Department" or "Project", and refer to the relevant organisational unit tables. You can therefore post the same voucher for both a department and a project, for example.

If you distribute vouchers by organisational unit, you can print separate reports for one or more organisational units without dividing them between different general ledger accounts. If you create hierarchies of organisational units, for example to divide a project into a main project and a sub-project, you can produce detailed reports on two levels. You choose you own subtotal level and the information/selection to be included. For example, you can print PL and balance sheet reports, balance lists and account statements for one or more organisational units.

Business NXT suggests the organisational unit where a permanent link is defined to the relevant general ledger account. If the general ledger account indicates that the organisational unit class should be entered, the organisational unit defined for the batch is suggested. If you enter a voucher for two general ledger accounts with different organisational units, the organisational unit is determined by the account entered first. If you enter an organisational unit, this will be used in preference to any distribution key for the same organisational unit class.

When you enter a customer/supplier number in the fields for debit/credit when entering a voucher, the organisational unit is retrieved from the Associate table.

The cursor only pauses in the organisational unit field if you have selected the Organisational unit processing box for the Debit account or Credit account. Even if the cursor skips the organisational unit field in a voucher line, you can always use the arrow keys to return to the field and edit it. When you enter an organisational unit number, the name of the organisational unit is displayed in the Status bar, so that you can check that you have entered the right number.

If neither debit account or credit account is entered with the value 1-3 in Organisational unit processing, you will be warned and you will not be able to enter an organisational unit in the voucher.

You will also receive messages if you use incorrect combinations of accounts and organisational units which you have defined in the Combination group, User combination group and Combination matrix tables.

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

The Voucher window includes one field for each organisational unit class defined in the Company information table. These fields may for example be named "Department" or "Project", and refer to the relevant organisational unit tables. You can therefore post the same voucher for both a department and a project, for example.

If you distribute vouchers by organisational unit, you can print separate reports for one or more organisational units without dividing them between different general ledger accounts. If you create hierarchies of organisational units, for example to divide a project into a main project and a sub-project, you can produce detailed reports on two levels. You choose you own subtotal level and the information/selection to be included. For example, you can print PL and balance sheet reports, balance lists and account statements for one or more organisational units.

Business NXT suggests the organisational unit where a permanent link is defined to the relevant general ledger account. If the general ledger account indicates that the organisational unit class should be entered, the organisational unit defined for the batch is suggested. If you enter a voucher for two general ledger accounts with different organisational units, the organisational unit is determined by the account entered first. If you enter an organisational unit, this will be used in preference to any distribution key for the same organisational unit class.

When you enter a customer/supplier number in the fields for debit/credit when entering a voucher, the organisational unit is retrieved from the Associate table.

The cursor only pauses in the organisational unit field if you have selected the Organisational unit processing box for the Debit account or Credit account. Even if the cursor skips the organisational unit field in a voucher line, you can always use the arrow keys to return to the field and edit it. When you enter an organisational unit number, the name of the organisational unit is displayed in the Status bar, so that you can check that you have entered the right number.

If neither debit account or credit account is entered with the value 1-3 in Organisational unit processing, you will be warned and you will not be able to enter an organisational unit in the voucher.

You will also receive messages if you use incorrect combinations of accounts and organisational units which you have defined in the Combination group, User combination group and Combination matrix tables.

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