Updated voucher

This table contains one row for each line in a bundle of vouchers that has been updated.

PropertyValueDescription
DatabaseCompanyThis table is in the company databases.
SQL nameUpdVoThe table name in the database.
API identifierupdatedVoucherThe API identifier used in GraphQL.
Table no.49The table number in the data model.

The following fields exist in this table:

Account statement trans. no.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainNo.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameAcStmtTrNoThe database field name.
API identifieraccountStatementTransactionNoThe API identifier used in GraphQL.
Number18966 
Table 1. Table relations
To tablePurposeFrom columnsTo columnsComments
Account statement transactionAccountStatementTransaction
  • Account statement trans. no.

Accounting document no.

The accounting document no refers to Accounting document table.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainNo.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameInAcDocNoThe database field name.
API identifierincomingAccountingDocumentNoThe API identifier used in GraphQL.
Number17923 
Table 2. Table relations
To tablePurposeFrom columnsTo columnsComments
Accounting documentIncomingAccountingDocument
  • Accounting document no.

Accounting rule no.

Accounting rule no. coming from Accounting rule criteria table.

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.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainNo.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameAcRuleNoThe database field name.
API identifieraccountingRuleNoThe API identifier used in GraphQL.
Number19019 
Table 3. Table relations
To tablePurposeFrom columnsTo columnsComments
Accounting rule criteriaAccountingRuleCriteria
  • Accounting rule no.

Accrual accounting end year/period

The date on which the accrual accounting of the Voucher is to end.

To be used if accrual accounting is to be executed when updating the voucher.
Note:
There are other alternatives for accrual accounting:
  • Using the Accrual accounting processing.
  • Using the Period key field.
By default the Debit account field will be subject to accrual accounting. If the Per. Credit field is checked, the Credit account field will be subject to accrual accounting. Set off account for the accrued periods is given in the Per. Debit acc. and the Per. Credit acc. fields in the Company information table. The field must be used in combination with the Accrual accounting start year/period field.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainYear/Per.Integer
SQL namePEnYrPrThe database field name.
API identifieraccrualAccountingEndYearAndPeriodThe API identifier used in GraphQL.
Number11995 

Accrual accounting start year/period

The date on which the accrual accounting of the Voucher is to start.

To be used if accrual accounting is to be executed when updating the voucher.
Note:
There are other alternatives for accrual accounting:
  • Using the Accrual accounting processing.
  • Using the Period key field.
By default the Debit account field will be subject to accrual accounting. If the Per. Credit field is checked, the Credit account field will be subject to accrual accounting. Set off account for the accrued periods is given in the Per. Debit acc. and the Per. Credit acc. fields in the Company information table. The field must be used in combination with the Accrual accounting end year/period field.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainYear/Per.Integer
SQL namePStYrPrThe database field name.
API identifieraccrualAccountingStartYearAndPeriodThe API identifier used in GraphQL.
Number11994 

Additional text

A supplementary description of the voucher.

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.
Note:
When importing incoming payments from Visma.net AutoPay, an internal reference is stored in this field. This reference is used by Business NXT to find the correct payment when running the View payment details processing.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainTextText (200)
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameTxt2The database field name.
API identifieradditionalTextThe API identifier used in GraphQL.
Number5817 

Amount

The amount of the current voucher.

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

Note:
If the Debit turnover cl. or Credit turnover cl. used is 6, 12, or 19, the amount entered shall match the amount on the invoice, which is excl. VAT.

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.

A bank voucher consists of a total amount of NOK 10,000, which you should credit to general ledger account 1920 Bank and debit three suppliers: NOK 2,000 from supplier account 50000, NOK 3,000 from supplier account 50025 and NOK 5,000 from supplier account 50016. You must then post the voucher over four voucher lines, with the voucher producing an overall difference of zero. All you need to enter are the account numbers and the amounts. In the other fields you can enter + to repeat the previous line. + in the final Amount field generates the difference in the batch.

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

A look-up in this column opens the calculator.

PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainAmountDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameAmThe database field name.
API identifieramountDomesticThe API identifier used in GraphQL.
Number999 

Amount excl. VAT

The amount excl. VAT of the voucher.

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.

A look-up in this column opens the calculator.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameAmExVATThe database field name.
API identifieramountExclusiveVatDomesticThe API identifier used in GraphQL.
Number8521 

Amount excl. VAT in currency

The amount excl. VAT in currency of the voucher

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.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameCurAmExVatThe database field name.
API identifieramountExclusiveVatInCurrencyThe API identifier used in GraphQL.
Number18160 

Amount in currency

The amount in currency of the voucher.

When you update the Currency no. field (or a currency is suggested), the Exchange rate is retrieved from the:
  1. The Sales rate field in the Currency rate table where the From date equals or is less than the Voucher date on the Voucher line.
  2. The Sales rate field from the Currency table.
The cursor moves to the next field. You can always return to the Exchange rate field and change the Exchange rate for the record.

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.

Note:
If you enter an amount in this field before first selecting a value in the Currency no. field, the default currency number will be retrieved from the Currency no. field in the Company information table, and the Exchange rate and Amount fields will be calculated. It is not possible to update a batch where there are voucher lines with values in the Amount in currency field but without Currency no.
A look-up in this column opens the calculator.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameCurAmThe database field name.
API identifieramountInCurrencyThe API identifier used in GraphQL.
Number998 

Amount in currency 2

The amount in currency 2 of the voucher.

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.

A look-up in this column opens the calculator.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameCurAm2The database field name.
API identifieramountInCurrency2The API identifier used in GraphQL.
Number14361 

Amount in EURO

The Amount field converted to EURO.

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.

If the standard currency, defined in the Company information table is defined as Currency type 0 or 1, please read the field help for the Currency table for explanation of how the amount in Euro is calculated.
Note:
The column is a calculated column, not stored in the database, which means that Amount in EURO in all tables where it exists will be updated if the Euro exchange rate in Currency table is changed.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Source columnAmount in currencyEuro
Write AccessNoneYou are not allowed to modify the value in this field.
Memory fieldYesThe value in this field is only displayed in the program, it is not stored in the database.
API identifieramountInEuroThe API identifier used in GraphQL.
Number7767 

Approval token

Token for payment pre-approved in Visma.net AutoPay.

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.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainApproval tokenText (40)
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameApTkThe database field name.
API identifierapprovalTokenThe API identifier used in GraphQL.
Number18563 

Approval workflow handle

Reference to a workflow in Visma.net Approval.

Used in Visma.net AutoPay for viewing of invoices.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainApproval workflow handleText (36)
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameApWfHThe database field name.
API identifierapprovalWorkflowHandleThe API identifier used in GraphQL.
Number18820 

Auth. responsible

If you are entering an incoming invoice that shall be authorised, the employee number of the authorisation official must be entered here.

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

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainEmpl. no.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameAttThe database field name.
API identifierapprovalOfficialThe API identifier used in GraphQL.
Number1014 
Table 4. Table relations
To tablePurposeFrom columnsTo columnsComments
AssociateApprovalOfficial
  • Auth. responsible

AutoPay log seq. no.

Reference to the Identifier column in Visma.net AutoPay log table, where the actual incoming payment file is stored.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainNo.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameApLSeqNoThe database field name.
API identifierautopayLogEntryNoThe API identifier used in GraphQL.
Number19628 

AutoPay payment reference

Reference to an incoming payment imported from Visma.net AutoPay.

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

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAutoPay payment referenceText (100)
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameApPmtRefThe database field name.
API identifierautopayPaymentReferenceThe API identifier used in GraphQL.
Number18213 

Bank account

This field overrides the bank account from the Associate table when creating a payment from an incoming invoice.

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.

Note:
The value in the Bank account field can be validated according to different rules and to disable this validation you have to set some option in the Country processing field in the Country table. The Country no. field from the debit or credit supplier/customer will be used so if there are no supplier or customer entered the control is disabled.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainBank accountText (35)
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameBankGThe database field name.
API identifierbankAccountThe API identifier used in GraphQL.
Number5818 

Bank account line no.

The reference to the Bank account table.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainNo.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameBankAcLnThe database field name.
API identifierbankAccountLineNoThe API identifier used in GraphQL.
Number11465 

Bank amount

The amount on the bank voucher relating to a deposit from the customer or a payment to the supplier.

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.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
SQL nameBankAmThe database field name.
API identifierbankAmountDomesticThe API identifier used in GraphQL.
Number12360 

Bank no.

A unique number identifying the bank in the Bank table.

The field has no function in electronic funds transfer.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainBank no.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameBankConThe database field name.
API identifierbankNoThe API identifier used in GraphQL.
Number11464 
Table 5. Table relations
To tablePurposeFrom columnsTo columnsComments
BankBank
  • Bank no.

Bank reference

The bank's reference for the transaction.

Applicable for GL bank account transactions. Automatically filled out when importing incoming payments and settlements for outgoing payments from Visma.net AutoPay, but can also be manually entered in the Voucher table.
Note:
If a transaction group in the incoming payments file from Visma.net AutoPay contain several payment lines, the bank reference will not be filled out on the GL bank account row.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainBank referenceText (30)
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameBankRefThe database field name.
API identifierbankReferenceThe API identifier used in GraphQL.
Number18779 

Batch no.

The batch to which the Voucher belongs.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainBatch no.Integer
Primary keyYesVoucher jour. no., Batch no., Line no.
SQL nameBndNoThe database field name.
API identifierbatchNoThe API identifier used in GraphQL.
Number983 
Table 6. Table relations
To tablePurposeFrom columnsTo columnsComments
Updated batchUpdatedBatch
  • Voucher jour. no.
  • Batch no.
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.
Updated voucherVoucher
  • Voucher jour. no.
  • Batch no.
  • Voucher no.
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.

Cap. asset no.

Filled out automatically when a Capital asset no is entered in the Debit account or Credit account fields.

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.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainCap. asset no.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL namePropNoThe database field name.
API identifiercapitalAssetNoThe API identifier used in GraphQL.
Number5775 
Table 7. Table relations
To tablePurposeFrom columnsTo columnsComments
Capital assetCapitalAsset
  • Cap. asset no.

Capital asset proc.

The type of processing for the capital asset.

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.

Note:
Entering a valid value in this field is mandatory, when a voucher line is entered, where the debit account or credit account contains a capital asset no. If not, the voucher line will not be possible to update. On capital asset transactions, therefore the field will always contain a valid value.
The capital asset processing determines which fields in the Capital asset balance table that will be updated and is essential to achieve correct depreciations.
A look-up in this field gives you the following list of possible values:
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
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainCapital asset proc.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL namePropPrcThe database field name.
API identifiercapitalAssetProcessingThe API identifier used in GraphQL.
Number5418 

Cash amount

The domestic cash amount of the current voucher.

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.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameCshAmThe database field name.
API identifiercashAmountDomesticThe API identifier used in GraphQL.
Number6239 

Cash amount in currency

The cash amount in currency of the voucher line.

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.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameCshCurAmThe database field name.
API identifiercashAmountInCurrencyThe API identifier used in GraphQL.
Number6238 

Cash amount in EURO

The Cash amount in currency value converted into EURO.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Source columnCash amount in currencyEuro
Write AccessNoneYou are not allowed to modify the value in this field.
Memory fieldYesThe value in this field is only displayed in the program, it is not stored in the database.
API identifiercashAmountInEuroThe API identifier used in GraphQL.
Number7822 

Cash due date

The cash due date.

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.

Note:
Only the Voucher date and NO OTHER DATE on the voucher determines the Cash due date

The date is validated using the regional settings in Windows.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainDateInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameCshDueDtThe database field name.
API identifiercashDueDateThe API identifier used in GraphQL.
Number6237 

CID code

The CID code for the voucher.

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.

Note:
The value in the CID code field can be validated according to different rules. The validation can be disabled by settings in the Country processing field in the Country table. The country no. from the debit or credit supplier/customer will be used, so if there are no supplier or customer entered in the Debit account and Credit account fields the control is disabled.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainCID codeText (30)
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameCIDThe database field name.
API identifiercidThe API identifier used in GraphQL.
Number1019 

Client processing

The field is used to manage vouchers related to client accounts.

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.

A look-up in this field gives you the following list of possible values:
1 - Outlay
2 - Client responsibility 1
3 - Client responsibility 2
4 - Client responsibility 3
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainClient processingInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameClPrcThe database field name.
API identifierclientProcessingThe API identifier used in GraphQL.
Number8436 

Cost amount

Non-deductible input VAT.

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.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameCstAmThe database field name.
API identifiercostAmountDomesticThe API identifier used in GraphQL.
Number9004 

Country no.

Used for OSS VAT handling.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainCountry no.Integer
SQL nameCtryThe database field name.
API identifiercountryNoThe API identifier used in GraphQL.
Number17540 
Table 8. Table relations
To tablePurposeFrom columnsTo columnsComments
CountryCountry
  • Country no.

Credit account

The credit account no.

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.

Note:
If you enter the number of a customer whose credit is suspended, a message appears in brackets after the customer name in the Status bar. You may still enter and update vouchers for the customer. If, however, you attempt to post vouchers to a suspended general ledger account, customer or supplier or capital asset, you are prevented from doing so and an error message will be displayed.

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.

When you enter Debit account or Credit account on the voucher, the corresponding value is entered in the Debit account type or Credit account type field as appropriate. If you delete the contents of the Debit account or Credit account fields, the contents of the Debit account type or Credit account type fields are also deleted.
Note:
If the field for Debit account or Credit account contains an account number that you want to replace with an account number for a different type of account, you must first delete the value in the field before you enter the new account number.

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.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainAccount no.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameCrAcNoThe database field name.
API identifiercreditAccountNoThe API identifier used in GraphQL.
Number994 
Table 9. Table relations
To tablePurposeFrom columnsTo columnsComments
AssociateCreditCustomer
  • Credit account
AssociateCreditSupplier
  • Credit account
General ledger accountCreditGeneralLedgerAccount
  • Credit account
Capital assetCreditCapitalAsset
  • Credit account

Credit account type

Indicates whether the Debit account or Credit account field refers to a customer, a supplier, a capital asset or a general ledger account.

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.

A look-up in this field gives you the following list of possible values:
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.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAccount typeInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameCrAcClThe database field name.
API identifiercreditAccountTypeThe API identifier used in GraphQL.
Number993 

Credit auto. st.

If you have posted vouchers to a general ledger account for which Auto. entry processing are defined, you can call up a status field for the automatic posting process.

Note:
If you for a general ledger account have checked the 1 - Expand on voucher lines field under Auto. entry processing in the General ledger account table, you can in this field turn off the automatic function by deleting the status before you enter amounts.

A look-up in this field gives you the following list of possible values:
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.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAut. entry statusInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameCrAutStThe database field name.
API identifiercreditAutomaticStatusThe API identifier used in GraphQL.
Number3683 

Credit VAT code

Determines whether Business NXT calculates input or output VAT for the voucher.

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.

Note:
You must ensure that the Credit VAT code corresponds to the turnover class on the voucher. Otherwise you might get an inconsistency in the tax statement. In the standard data sets, delivered with the installation, a standard set of VAT codes with corresponding turnover classes will be included.

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.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainVAT codeInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameCrTxCdThe database field name.
API identifiercreditTaxCodeThe API identifier used in GraphQL.
Number995 
Table 10. Table relations
To tablePurposeFrom columnsTo columnsComments
VAT codeCreditTaxCode
  • Credit VAT code

Credit VAT code paym. variance

This field is no longer in use. Be aware the field may be removed in later versions.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainVAT codeInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameCrTxCdPThe database field name.
API identifiercreditTaxCodePaymentVarianceThe API identifier used in GraphQL.
Number11077 
Table 11. Table relations
To tablePurposeFrom columnsTo columnsComments
VAT codeCreditTaxCodePaymentVariance
  • Credit VAT code paym. variance

Credit turnover cl.

Form the basis for printing tax statements.

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.

Note:
However, if there is a customer or supplier ledger account in the same voucher as a General ledger account and an area has been defined for export for the associate, the turnover class for export sales/purchases is used for updates. This also applies if the General ledger account has a Turnover class for taxable sales/purchases. No VAT is posted on these transactions and the tax statement is therefore correct in relation to accumulated figures for non-taxable sales/purchases. If you have to post a purchase/expense to a customer (often an employee with a customer number) and want, for example, to enter the code 2 Received VAT with inv. tax, you must override the turnover class for the ledger entry and not the General ledger account, or post the Voucher to two separate lines. If you have entered tax codes with turnover class you avoid this problem. It is therefore important that you enter the correct values in the VAT code table, so that you avoid tax errors when reporting.
Note:
If you use tax code on a general ledger for which you have not defined any turnover class, and a customer or supplier is entered in the voucher, the customers/suppliers area is used to produce the correct Turnover class for the General ledger transaction.
Note:
In order for the VAT amount field to be calculated when you fill in the Amount in the voucher, the turnover class must be entered.

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.

A look-up in this field gives you the following list of possible values:
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
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainTurnover classInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameCrTrnClThe database field name.
API identifiercreditTurnoverClassThe API identifier used in GraphQL.
Number6894 

Credit turnover cl. paym. variance

This field is no longer in use. Be aware the field may be removed in later versions.

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.

A look-up in this field gives you the following list of possible values:
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
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainTurnover classInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameCrTrnClPThe database field name.
API identifiercreditTurnoverClassPaymentVarianceThe API identifier used in GraphQL.
Number11078 

Cross reference

The cross reference when matching payment voucher against open customer / supplier entries.

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.

Note:
As these are just temporary entries in the Cross reference table until saved, so there are restrictions on completion of included fields from underlying tables. When searching or refreshing these fields will be blanked. It is not possible to search in these rows either before you have clicked Save.
Note:
It is not allowed to select multiple rows in the Open customer entry table for matching an incoming payment, if any of them are transferred to Visma AutoCollect for follow-up (i.e. the entry has a value in the Debt collection ID field). A warning will in this case be given.

PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainDoc. no.Text (40)
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameAgRefThe database field name.
API identifiercrossReferenceThe API identifier used in GraphQL.
Number1009 

Currency no.

A currency for the voucher.

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.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainCurrency no.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameCurThe database field name.
API identifiercurrencyNoThe API identifier used in GraphQL.
Number996 
Table 12. Table relations
To tablePurposeFrom columnsTo columnsComments
CurrencyCurrency
  • Currency no.

Currency no. 2

A currency number two for the voucher.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainCurrency no.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameCur2The database field name.
API identifiercurrencyNo2The API identifier used in GraphQL.
Number14359 
Table 13. Table relations
To tablePurposeFrom columnsTo columnsComments
CurrencyCurrency2
  • Currency no. 2

Cust. no.

The customer number the voucher applies to.

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

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainCust. no.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameCustThe database field name.
API identifiercustomerNoThe API identifier used in GraphQL.
Number1016 
Table 14. Table relations
To tablePurposeFrom columnsTo columnsComments
AssociateCustomer
  • Cust. no.

Date 1

This field is used by some bank reconciliation systems to assign a date to processed transactions.

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.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainDateInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameDt1The database field name.
API identifierdate1The API identifier used in GraphQL.
Number11258 

Date 2

This field is used by some bank reconciliation systems to assign a date to processed transactions.

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.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainDateInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameDt2The database field name.
API identifierdate2The API identifier used in GraphQL.
Number11259 

Debit account

The debit account no.

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.

Note:
If you enter the number of a customer whose credit is suspended, a message appears in brackets after the customer name in the Status bar. You may still enter and update vouchers for the customer. If, however, you attempt to post vouchers to a suspended general ledger account, customer or supplier or capital asset, you are prevented from doing so and an error message will be displayed.

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.

When you enter Debit account or Credit account on the voucher, the corresponding value is entered in the Debit account type or Credit account type field as appropriate. If you delete the contents of the Debit account or Credit account fields, the contents of the Debit account type or Credit account type fields are also deleted.
Note:
If the field for Debit account or Credit account contains an account number that you want to replace with an account number for a different type of account, you must first delete the value in the field before you enter the new account number.

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.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainAccount no.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameDbAcNoThe database field name.
API identifierdebitAccountNoThe API identifier used in GraphQL.
Number991 
Table 15. Table relations
To tablePurposeFrom columnsTo columnsComments
AssociateDebitCustomer
  • Debit account
AssociateDebitSupplier
  • Debit account
General ledger accountDebitGeneralLedgerAccount
  • Debit account
Capital assetDebitCapitalAsset
  • Debit account

Debit account type

The account type indicates whether the account number refers to a customer, a supplier, a capital asset or a general ledger account.

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.

A look-up in this field gives you the following list of possible values:
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.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAccount typeInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameDbAcClThe database field name.
API identifierdebitAccountTypeThe API identifier used in GraphQL.
Number990 

Debit auto. st.

If you have posted vouchers to a general ledger account for which Auto. entry processing are defined, you can call up a status field for the automatic posting process.

Note:
If you for a general ledger account have checked the 1 - Expand on voucher lines field under Auto. entry processing in the General ledger account table, you can in this field turn off the automatic function by deleting the status before you enter amounts.

A look-up in this field gives you the following list of possible values:
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.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAut. entry statusInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameDbAutStThe database field name.
API identifierdebitAutomaticStatusThe API identifier used in GraphQL.
Number3682 

Debit turnover cl.

Form the basis for printing tax statements.

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.

Note:
However, if there is a customer or supplier ledger account in the same voucher as a General ledger account and an area has been defined for export for the associate, the turnover class for export sales/purchases is used for updates. This also applies if the General ledger account has a Turnover class for taxable sales/purchases. No VAT is posted on these transactions and the tax statement is therefore correct in relation to accumulated figures for non-taxable sales/purchases. If you have to post a purchase/expense to a customer (often an employee with a customer number) and want, for example, to enter the code 2 Received VAT with inv. tax, you must override the turnover class for the ledger entry and not the General ledger account, or post the Voucher to two separate lines. If you have entered tax codes with turnover class you avoid this problem. It is therefore important that you enter the correct values in the VAT code table, so that you avoid tax errors when reporting.
Note:
If you use tax code on a general ledger for which you have not defined any turnover class, and a customer or supplier is entered in the voucher, the customers/suppliers area is used to produce the correct Turnover class for the General ledger transaction.
Note:
In order for the VAT amount field to be calculated when you fill in the Amount in the voucher, the turnover class must be entered.

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.

A look-up in this field gives you the following list of possible values:
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
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainTurnover classInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameDbTrnClThe database field name.
API identifierdebitTurnoverClassThe API identifier used in GraphQL.
Number6891 

Debit turnover cl. paym. variance

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.

A look-up in this field gives you the following list of possible values:
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
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainTurnover classInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameDbTrnClPThe database field name.
API identifierdebitTurnoverClassPaymentVarianceThe API identifier used in GraphQL.
Number11076 

Debit VAT code

The Debit VAT code field determines whether Business NXT calculates input or output VAT and/or investment tax for the voucher.

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.

Note:
You must ensure that the Debit VAT code corresponds to the turnover class by which the general ledger accounts are defined. Otherwise you might have a difference in the tax statement.

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.

Note:
When importing batches this field should always be filled in for general ledger accounts together with the Debit turnover cl. field, unless the account plan is set up with turnover class; otherwise the tax statement could be incorrect.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainVAT codeInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameDbTxCdThe database field name.
API identifierdebitTaxCodeThe API identifier used in GraphQL.
Number992 
Table 16. Table relations
To tablePurposeFrom columnsTo columnsComments
VAT codeDebitTaxCode
  • Debit VAT code

Debit VAT code paym. variance

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainVAT codeInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameDbTxCdPThe database field name.
API identifierdebitTaxCodePaymentVarianceThe API identifier used in GraphQL.
Number11075 
Table 17. Table relations
To tablePurposeFrom columnsTo columnsComments
VAT codeDebitTaxCodePaymentVariance
  • Debit VAT code paym. variance

Debt collection amount

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameDColAmThe database field name.
API identifierdebtCollectionAmountDomesticThe API identifier used in GraphQL.
Number18873 

Debt collection ID

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainGUIDText (40)
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameDColIdThe database field name.
API identifierdebtCollectIdThe API identifier used in GraphQL.
Number18994 

Debt collection response status

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainTextText (200)
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameDColRStThe database field name.
API identifierdebtCollectionResponseStatusThe API identifier used in GraphQL.
Number18874 

Debt collection sent date

The date is validated using the regional settings in Windows.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainDateInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameDColSDtThe database field name.
API identifierdebtCollectionSentDateThe API identifier used in GraphQL.
Number18871 

Debt collection sent time

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainTimeInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameDColSTmThe database field name.
API identifierdebtCollectionSentTimeThe API identifier used in GraphQL.
Number18872 

Delivery associate no.

Is filled in on supplier ledger vouchers produced on the basis of orders.

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

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAssociate no.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameDelActNoThe database field name.
API identifierdeliveryAssociateNoThe API identifier used in GraphQL.
Number8898 
Table 18. Table relations
To tablePurposeFrom columnsTo columnsComments
AssociateDeliveryAssociate
  • Delivery associate no.

Difference

Shows the difference between the Bank amount field and the certain entries.

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.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
Memory fieldYesThe value in this field is only displayed in the program, it is not stored in the database.
API identifierdifferenceThe API identifier used in GraphQL.
Number12359 

Distribution key

The Amount, Amount in currency and Quantity fields in the voucher can be distributed proportionally between one or more organisational units by referring to a predefined distribution key.

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 %.

Note:
Distribution will by default not be performed for ledger entries. If you want to have this function, you must enable the parameter Generate distribution lines on Cust/Supp. trans in the Accounting processing dialog box in the Company information table.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainDistribution keyInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameDstGrThe database field name.
API identifierdistributionKeyNoThe API identifier used in GraphQL.
Number2234 
Table 19. Table relations
To tablePurposeFrom columnsTo columnsComments
Distribution keyDistributionKey
  • Distribution key

Document product no.

Incoming document product identification processed from Accounting document table.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainDocument product no.Text (40)
SQL nameDocProdNoThe database field name.
API identifierdocumentProductNoThe API identifier used in GraphQL.
Number19689 

Document quantity

Incoming document line quantity processed from Accounting document table.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainQuantityDecimal
SQL nameDocQtyThe database field name.
API identifierdocumentQuantityThe API identifier used in GraphQL.
Number19725 

Document VAT rate

Incoming document VAT rate (on invoice/credit note) processed from Accounting document table

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainPercentDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameDocVatRtThe database field name.
API identifierdocumentVatRateThe API identifier used in GraphQL.
Number19084 

Due date

The due date is crucial for the routines associated with reminders, interest computation and payment suggestions.

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.

PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainDateInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameDueDtThe database field name.
API identifierdueDateThe API identifier used in GraphQL.
Number1007 

EFT bank fee code

Used in connection with electronic funds transfer.

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.

EFT bank fee texts for different languages can be defined in the Text table. These texts has text type 130.
Note:
If you double-click or press * in this field, you can look up a EFT bank fee in the Text table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainEFT bank feeInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameEFT2The database field name.
API identifiereftBankFeeCodeThe API identifier used in GraphQL.
Number6645 

EFT currency code

Used in connection with electronic funds transfer.

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.

Note:
For incoming payments imported from Visma.net AutoPay and Visma AutoPay, will AutoPay's internal reference ID for the payment be stored in this field.

EFT Currency code texts for different languages can be defined in the Text table. These texts has text type 129.
Note:
If you double-click or press * in this field, you can look up a EFT Currency code in the Text table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainEFT Currency codeInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameEFT1The database field name.
API identifiereftCurrencyCodeThe API identifier used in GraphQL.
Number6644 

EFT decl. code

Used in connection with electronic funds transfer.

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.

EFT declaration code texts for different languages can be defined in the Text table. These texts has text type 131.
Note:
If you double-click or press * in this field, you can look up a EFT declaration code in the Text table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainEFT declaration codeInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameEFT3The database field name.
API identifiereftDeclarationCodeThe API identifier used in GraphQL.
Number6646 

EFT form type

The form type for Danish payment formats, or for other payment formats which must state the form type in the payment file.

For Danish payment formats, you can use:
  • 1 = giro transfer with notification without payment ID
  • 4 = giro transfer without notification with payment ID
  • 15 = giro transfer with notification and payment ID
  • 71 = money order without notification with payment ID
  • 73 = money order with notification without payment ID
  • 75 = money order with notification and payment ID
Note:
Run the Mandatory text types processing from the Company information table, and set the text type EFT form type to mandatory. This will prevent you from entering an incorrect code.
EFT form type texts for different languages can be defined in the Text table. These texts has text type 203.
Note:
If you double-click or press * in this field, you can look up a EFT form type in the Text table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainEFT form typeInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameEftFrmTpThe database field name.
API identifiereftFormTypeThe API identifier used in GraphQL.
Number15469 

EFT paym. method

Used in connection with electronic funds transfer.

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.

EFT payment method texts for different languages can be defined in the Text table. These texts has text type 132.
Note:
If you double-click or press * in this field, you can look up a EFT payment method in the Text table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainEFT payment methodInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameEFT4The database field name.
API identifiereftPaymentMethodThe API identifier used in GraphQL.
Number6647 

Empl. no.

An employee number.

An employee number can be entered. This will be copied to transaction tables when updating the voucher if a follow-up of transactions pr employee is needed.
Note:
  • For follow-up of open supplier entries for authorisation, it is recommended to use the Auth. responsible field.
  • For follow-up on accounting reports it is recommended to establish an organisational unit for employees

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

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainEmpl. no.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameEmpThe database field name.
API identifieremployeeNoThe API identifier used in GraphQL.
Number1017 
Table 20. Table relations
To tablePurposeFrom columnsTo columnsComments
AssociateEmployee
  • Empl. no.

Error message

Shows whether any errors were found during updating.

For example, whether an account was used that does not exist in the account plan, or whether a mandatory organisational unit is missing. It is not possible to update vouchers that contain errors, and this field is therefore rarely updated. The field is updated, for example, when data has been exchanged interactively with other systems, in which case Business NXT controls are not started before the update.

The field can also be updated when the installation does not have a licence for accounting. This is because installations that do not have a licence for accounting always use direct updating from the order module.

A look-up opens the dialog box where you can see the following check boxes and options:
Illegal value date
Unknown organisational unit 1
Unknown organisational unit 2
Unknown organisational unit 3
Unknown organisational unit 4
Unknown organisational unit 5
Unknown organisational unit 6
Unknown debit account, Cust. no., Account no. or Cap. asset no.
Unknown credit account, Cust. no., Account no. or Cap. asset no.
Unknown debit VAT code or VAT code
Unknown credit VAT code or VAT code
Unknown debit VAT rate
Unknown credit VAT rate
Unknown debit investment tax
Unknown credit investment tax
Unknown debit payment terms
Unknown credit payment terms
Unknown distribution key
Illegal debit turnover cl. or Turnover class
Illegal credit turnover cl. or Turnover class
Missing credit turnover cl. or Turnover class
The grace period for the debit has exceeded
The grace period for the credit has exceeded
Unknown organisational unit 7
Unknown organisational unit 8
Unknown organisational unit 9
Unknown organisational unit 10
Unknown organisational unit 11
Unknown organisational unit 12
Missing accounting period
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainError messageInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameErrThe database field name.
API identifiererrorMessageThe API identifier used in GraphQL.
Number1020 

Exchange rate

The exchange rate for currency.

When you enter a currency no. (or Business NXT suggests a currency), the exchange rate is retrieved from either of the following tables with the following priority:
  1. Currency rate, Sales rate from the line that matches the vouchers Voucher date
  2. Currency, Sales rate
The suggested or manually entered Exchange rate can be overridden.

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.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainExchange rateDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameExRtThe database field name.
API identifierexchangeRateThe API identifier used in GraphQL.
Number997 

Exchange rate 2

The exchange rate for currency 2.

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.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainExchange rateDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameExRt2The database field name.
API identifierexchangeRate2The API identifier used in GraphQL.
Number14360 

Exempt

A code that controls if the voucher should be exempt from reminders and/or interest computation.

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.

A look-up in this field gives you the following list of possible values:
1 - No reminders/payment
2 - No interest
3 - No reminders or interest
4 - No debt collection
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainExemptInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameExcThe database field name.
API identifierexemptThe API identifier used in GraphQL.
Number1012 

Exempt from auto entry

If the field is checked, the voucher is not accumulated in the fields for automatic entry movements in the General ledger account table.

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.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainBooleanInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameExAutThe database field name.
API identifierexemptFromAutomaticEntryThe API identifier used in GraphQL.
Number5800 

External reference 1

Used by some bank reconciliation systems to show processed transactions.

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.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainString of length 20Text (20)
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameExtRef1The database field name.
API identifierexternalReference1The API identifier used in GraphQL.
Number11256 

External reference 2

Used by some bank reconciliation systems to show processed transactions.

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.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainString of length 20Text (20)
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameExtRef2The database field name.
API identifierexternalReference2The API identifier used in GraphQL.
Number11257 

External reference 3

Used by some bank reconciliation systems to show processed transactions.

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.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainString of length 20Text (20)
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameExtRef3The database field name.
API identifierexternalReference3The API identifier used in GraphQL.
Number12800 

Fixed amount

An amount which Business NXT may not use when calculating cash discounts.

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.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameFixAmThe database field name.
API identifierfixedAmountDomesticThe API identifier used in GraphQL.
Number6236 

Fixed amount in currency

An amount in currency which Business NXT may not use when calculating cash discounts.

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

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameFixCurAmThe database field name.
API identifierfixedAmountInCurrencyThe API identifier used in GraphQL.
Number6235 

Fixed amount in EURO

Shows the amount in EURO which Business NXT may not use when calculating cash discounts.

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

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Source columnFixed amount in currencyEuro
Write AccessNoneYou are not allowed to modify the value in this field.
Memory fieldYesThe value in this field is only displayed in the program, it is not stored in the database.
API identifierfixedAmountInEuroThe API identifier used in GraphQL.
Number7821 

Free 1

Additional numeric information about the voucher.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainQuantityDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameFree1The database field name.
API identifierfree1The API identifier used in GraphQL.
Number9181 

Free 2

Additional numeric information about the voucher.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainQuantityDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameFree2The database field name.
API identifierfree2The API identifier used in GraphQL.
Number9182 

Free 3

Additional numeric information about the voucher.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainQuantityDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameFree3The database field name.
API identifierfree3The API identifier used in GraphQL.
Number9183 

Free 4

Additional numeric information about the voucher.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainQuantityDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameFree4The database field name.
API identifierfree4The API identifier used in GraphQL.
Number9184 

Giro no. check sum

When you use a bank giro number, Business NXT checks, via BIG, that the check sum stated agrees with the giro number on the same line.

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.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainNo.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameGiroChSmThe database field name.
API identifiergiroNoCheckSumThe API identifier used in GraphQL.
Number10500 

Incm. doc. no.

Reference to the corresponding Document comment table entry.

This field is used for order match functionality.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainNo.Integer
SQL nameInDocNoThe database field name.
API identifierincomingDocumentNoThe API identifier used in GraphQL.
Number17922 
Table 21. Table relations
To tablePurposeFrom columnsTo columnsComments
Incoming documentIncomingDocument
  • Incm. doc. no.

Interest free amount

An amount which is exempt from interest calculation in the default currency.

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.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameFreeAmThe database field name.
API identifierinterestFreeAmountDomesticThe API identifier used in GraphQL.
Number11863 

Interest free amount in currency

An amount which is exempt from interest calculation in the current currency.

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.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameFreeCurAThe database field name.
API identifierinterestFreeAmountInCurrencyThe API identifier used in GraphQL.
Number11864 

Interest free amount in EURO

An amount which is exempt from interest calculation converted to EURO.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Source columnInterest free amount in currencyEuro
Write AccessNoneYou are not allowed to modify the value in this field.
Memory fieldYesThe value in this field is only displayed in the program, it is not stored in the database.
API identifierinterestFreeAmountInEuroThe API identifier used in GraphQL.
Number11862 

Interest rate

An interest rate for customer entries.

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.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainPercentDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameIntRtThe database field name.
API identifierinterestRateThe API identifier used in GraphQL.
Number1010 

Invoice no.

The invoice number.

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.

Vouchers automatically produced from purchase orders and sales orders will automatically get the field filled out with the same no as the voucher which will be fetched from the Voucher series that has been defined as Invoice series/Product purchase voucher series in the Company information table.
Note:
Another field; -Reference- is crucial to perform matching of invoices and payments and inherits the value from the Invoice no., if not manually entered. Therefore, it is strongly advised to be careful to avoid erroneous values in the Invoice no. field.
When entering payment vouchers, a look-up containing open entries matching the customer or supplier no entered in the Credit account or Debit account field can be performed in the Invoice no. field. By highlighting one or more invoice(s) in the look-up, and press <Ctrl>+<Enter> the Amount will automatically be updated and the Cross reference table will be populated with cross references to the highlighted open entries.
Note:
When the look-up is performed from the Invoice no. field, the open entries paid must be highlighted to be able to update the Amount field and the Cross reference table. If it is requested be able to update the amount from the look-up, without highlighting and populating the Cross reference table, the look-up shall be performed from the Cross reference field instead.

PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainDoc. no.Text (40)
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameInvoNoThe database field name.
API identifierinvoiceNoThe API identifier used in GraphQL.
Number1006 

Line no.

Each line in the table is given a consecutive number in the order in which they are entered.

Note:
The Line no. does not change when inserting new lines between existing ones. The Sort seq. no. specifies the order of the lines and is affected when new lines are inserted between existing lines.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainNo.Integer
Primary keyYesVoucher jour. no., Batch no., Line no.
SQL nameLnNoThe database field name.
API identifierlineNoThe API identifier used in GraphQL.
Number984 

Memo file name

If you link a memo to the voucher, this field will refer a file name.

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.

Note:
It is important that you save the file on a server and in a folder that is available to all users, otherwise users who try to open the memo will receive an error message.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainMemo file nameText (260)
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameNoteNmThe database field name.
API identifiermemoFileNameThe API identifier used in GraphQL.
Number4364 

Memo no.

Link to the memo for the entry.

The actual memo is stored in the Memo table.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainMemo no.Integer
SQL nameMemoNoThe database field name.
API identifiermemoNoThe API identifier used in GraphQL.
Number19246 
Table 22. Table relations
To tablePurposeFrom columnsTo columnsComments
MemoMemo
  • Memo no.

No. of periods

This field is no longer in use. Be aware the field may be removed in later versions.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainNo.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
Memory fieldYesThe value in this field is only displayed in the program, it is not stored in the database.
API identifiernoOfPeriodsThe API identifier used in GraphQL.
Number12165 

Order no.

Order no on vouchers produced from order processing or order no for recharge of manually posted outlays.

The order number is filled in on vouchers generated from order processing.
Note:
  • To get the order no filled out on the non-customer/supplier ledger voucher from processed orders with transaction type 1 - Sales, 2 - Hire,3 - Loan or 6 - Purchase, the option GL trans. per invoice (Recommended) in Company information must be enabled.
  • To get the order no filled out on the vouchers from processed orders with another transaction type than mentioned above, the option GL trans. per order, when posting from product trans. in Company information must be enabled.

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.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainOrder no.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameTaskThe database field name.
API identifierorderNoThe API identifier used in GraphQL.
Number1015 
Table 23. Table relations
To tablePurposeFrom columnsTo columnsComments
OrderOrder
  • Order no.

Organisational unit 1

The field is used to specify organisational unit.

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.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainOrganisational unit no.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameR1The database field name.
API identifierorgUnit1The API identifier used in GraphQL.
Number1000 
Table 24. Table relations
To tablePurposeFrom columnsTo columnsComments
Organisational unit 1OrgUnit1
  • Organisational unit 1

Organisational unit 2

The field is used to specify organisational unit.

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.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainOrganisational unit no.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameR2The database field name.
API identifierorgUnit2The API identifier used in GraphQL.
Number1001 
Table 25. Table relations
To tablePurposeFrom columnsTo columnsComments
Organisational unit 2OrgUnit2
  • Organisational unit 2

Organisational unit 3

The field is used to specify organisational unit.

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.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainOrganisational unit no.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameR3The database field name.
API identifierorgUnit3The API identifier used in GraphQL.
Number1002 
Table 26. Table relations
To tablePurposeFrom columnsTo columnsComments
Organisational unit 3OrgUnit3
  • Organisational unit 3

Organisational unit 4

The field is used to specify organisational unit.

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.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainOrganisational unit no.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameR4The database field name.
API identifierorgUnit4The API identifier used in GraphQL.
Number1003 
Table 27. Table relations
To tablePurposeFrom columnsTo columnsComments
Organisational unit 4OrgUnit4
  • Organisational unit 4

Organisational unit 5

The field is used to specify organisational unit.

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.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainOrganisational unit no.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameR5The database field name.
API identifierorgUnit5The API identifier used in GraphQL.
Number1004 
Table 28. Table relations
To tablePurposeFrom columnsTo columnsComments
Organisational unit 5OrgUnit5
  • Organisational unit 5

Organisational unit 6

The field is used to specify organisational unit.

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.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainOrganisational unit no.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameR6The database field name.
API identifierorgUnit6The API identifier used in GraphQL.
Number1005 
Table 29. Table relations
To tablePurposeFrom columnsTo columnsComments
Organisational unit 6OrgUnit6
  • Organisational unit 6

Organisational unit 7

The field is used to specify organisational unit.

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.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainLong alphanumeric organisational unit no.Text (40)
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameR7The database field name.
API identifierorgUnit7The API identifier used in GraphQL.
Number9498 
Table 30. Table relations
To tablePurposeFrom columnsTo columnsComments
Organisational unit 7OrgUnit7
  • Organisational unit 7

Organisational unit 8

The field is used to specify organisational unit.

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.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainShort alphanumeric organisational unit no.Text (10)
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameR8The database field name.
API identifierorgUnit8The API identifier used in GraphQL.
Number9499 
Table 31. Table relations
To tablePurposeFrom columnsTo columnsComments
Organisational unit 8OrgUnit8
  • Organisational unit 8

Organisational unit 9

The field is used to specify organisational unit.

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.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainShort alphanumeric organisational unit no.Text (10)
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameR9The database field name.
API identifierorgUnit9The API identifier used in GraphQL.
Number9500 
Table 32. Table relations
To tablePurposeFrom columnsTo columnsComments
Organisational unit 9OrgUnit9
  • Organisational unit 9

Organisational unit 10

The field is used to specify organisational unit.

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.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainShort alphanumeric organisational unit no.Text (10)
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameR10The database field name.
API identifierorgUnit10The API identifier used in GraphQL.
Number9501 
Table 33. Table relations
To tablePurposeFrom columnsTo columnsComments
Organisational unit 10OrgUnit10
  • Organisational unit 10

Organisational unit 11

The field is used to specify organisational unit.

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.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainShort alphanumeric organisational unit no.Text (10)
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameR11The database field name.
API identifierorgUnit11The API identifier used in GraphQL.
Number9502 
Table 34. Table relations
To tablePurposeFrom columnsTo columnsComments
Organisational unit 11OrgUnit11
  • Organisational unit 11

Organisational unit 12

The field is used to specify organisational unit.

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.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainShort alphanumeric organisational unit no.Text (10)
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameR12The database field name.
API identifierorgUnit12The API identifier used in GraphQL.
Number9503 
Table 35. Table relations
To tablePurposeFrom columnsTo columnsComments
Organisational unit 12OrgUnit12
  • Organisational unit 12

Original voucher no.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainVoucher no.Integer
SQL nameOrVoNoThe database field name.
API identifieroriginalVoucherNoThe API identifier used in GraphQL.
Number18629 

OSS VAT term

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainPeriodInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameEsTxTrmThe database field name.
API identifierossTaxTermThe API identifier used in GraphQL.
Number17566 
Table 36. Table relations
To tablePurposeFrom columnsTo columnsComments
OSS VAT periodOssTaxTerm
  • VAT year
  • OSS VAT term
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.

Part payment

The amount to match (obsolete functionality).

Note:
The functionality for which this field is meant to be used is obsolete.

If invoices are payed only partly, it is strongly recommended to use a Voucher type with the option Copy open entries on lookup enabled and enter the part payments in the joined Cross reference table instead. This will give the user a better overview of the matched part payments.

(You can use this field if you do not want to match the whole amount for an entry. When you update your vouchers, the Part payment field is included in the open entries.

This is because the Part payment field forms the basis when you match the entry. The part payment amount is reduced when you match the entry, the entry matching is completed with the part payment amount is zero.

In Open supplier entry table the fields are also used for payment suggestions.)

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL namePrtAmThe database field name.
API identifierpartPaymentDomesticThe API identifier used in GraphQL.
Number7992 

Part payment in currency

An amount in currency to match.

Note:
The functionality for which this field is meant to be used is obsolete.

If invoices are payed only partly, it is strongly recommended to use a Voucher type with the option Copy open entries on lookup enabled and enter the part payments in the joined Cross reference table instead. This will give the user a better overview of the matched part payments

When you enter the part payment amount in the current currency, Business NXT suggests the part payment amount in the default currency, and vice versa.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL namePrtCurAmThe database field name.
API identifierpartPaymentInCurrencyThe API identifier used in GraphQL.
Number7967 

Part payment in EURO

An amount in EURO to match.

This field is not contained in the database, but displays the Part payment in currency field converted to EURO.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Source columnPart payment in currencyEuro
Write AccessNoneYou are not allowed to modify the value in this field.
Memory fieldYesThe value in this field is only displayed in the program, it is not stored in the database.
API identifierpartPaymentInEuroThe API identifier used in GraphQL.
Number7991 

Payment element index

Reference to the relevant <Payment> element in the incoming payment file.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainNo.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL namePayIdxThe database field name.
API identifierpaymentIndexThe API identifier used in GraphQL.
Number19629 

Payment line element index

Reference to the relevant <PaymentLine> element in the incoming payment file.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainNo.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL namePayLnIdxThe database field name.
API identifierpaymentLineIndexThe API identifier used in GraphQL.
Number19630 

Payment method

The payment method.

The field is used to control the automatic posting that is executed when a voucher concerning customer or supplier transactions is updated. The Payment method is defined in the Payment method table. The field is to be used mainly for vouchers reflecting cash sales / purchases and for voucher generated by POS.

Payment method texts for different languages can be defined in the Text table. These texts has text type 7.
Note:
If you double-click or press * in this field, you can look up a Payment method in the Text table.
Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainPayment methodInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL namePmtMtThe database field name.
API identifierpaymentMethodThe API identifier used in GraphQL.
Number10557 
Table 37. Table relations
To tablePurposeFrom columnsTo columnsComments
Payment methodPaymentMethod
  • Payment method

Payment supplier no.

Supplier used as the payee when creating payment suggestions.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainSup. no.Integer
Write AccessSystem supervisor userOnly users who are marked as System supervisor in the User table are allowed to modify the value in this field.
SQL nameRmtSupThe database field name.
API identifierremittanceSupplierNoThe API identifier used in GraphQL.
Number17878 
Table 38. Table relations
To tablePurposeFrom columnsTo columnsComments
AssociateRemittanceSupplier
  • Payment supplier no.

Payment terms

The payment terms.

When you enter invoices for either customers or suppliers, the Payment terms field is suggested on the basis of what is in the Associate table for the relevant customer or supplier. Also the due date and cash due date are suggested on the basis of the payment terms.

The Payment terms forms together with the Voucher date field the basis for calculation of the Due date and Cash due date fields.

If the payment terms are to be retrieved for the customer or supplier in connection with opposite entry, you must check the Use payment terms on credit notes field under Accounting processing in the Company information table.

Payment terms texts for different languages can be defined in the Text table. These texts has text type 6.
Note:
If you double-click or press * in this field, you can look up a Payment terms in the Text table.
Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainPayment termsInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL namePmtTrmThe database field name.
API identifierpaymentTermsThe API identifier used in GraphQL.
Number4945 
Table 39. Table relations
To tablePurposeFrom columnsTo columnsComments
Payment termPaymentTerms
  • Payment terms

Per. Credit

Make the Credit account field subject to accrual accounting.

When the field is selected, the Credit account field will be subject to accrual accounting instead of the Debit account field that is default subject to accrual accounting. The field is to be used only in combination with Accrual accounting start year/period and Accrual accounting end year/period or in combination with Period key on the Voucher record.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainBooleanInteger
Write AccessNoneYou are not allowed to modify the value in this field.
Memory fieldYesThe value in this field is only displayed in the program, it is not stored in the database.
API identifieraccrualCreditThe API identifier used in GraphQL.
Number11993 

Period

The accounting period to use.

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

Note:
You do not need to complete the Year, Period, VAT year and VAT term fields for the voucher unless the voucher is to be posted for an accounting period or VAT period that is different from the rest of the batch. To make it easier to reconcile, we recommend that you use the Value date field instead.

The period, year, VAT year and VAT period 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 period for the voucher to be updated. Even if a company is not liable to pay tax, at least one VAT period must be defined to cover the entire financial year. The suspension date can be updated whenever a VAT statement is approved, which means that vouchers cannot be posted for periods that have been 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.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainPeriodInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameAcPrThe database field name.
API identifierperiodThe API identifier used in GraphQL.
Number4505 
Table 40. Table relations
To tablePurposeFrom columnsTo columnsComments
Accounting periodAccountingPeriod
  • Year
  • Period
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.

Period batch no.

The period batch number and the value is retrieved from the batch head.

The period batch number is included in all entries that are produced when updating. On normal transactions, the value is taken from the batch head unless it is given on the voucher.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainNo.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL namePrBtThe database field name.
API identifierperiodBatchNoThe API identifier used in GraphQL.
Number10559 

Period key

A distribution key for accrual accounting.

If the voucher shall be splitted and amounts distributed over several accounting periods, a Period key can be used if the processing Accrual accounting is unwanted by the user.

The processing Accrual accounting will create and expand a new voucher for each accrued period, which might give the user a less good overview of the vouchers, while the use of a Period key will expand the accrual accounting during the update.

The period keys are defined in the Period key table.

The Period line table will not be regarded when using the field Period key on the voucher line, only the No. of periods field in the Period key table.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainPeriod keyInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL namePrKThe database field name.
API identifierperiodKeyNoThe API identifier used in GraphQL.
Number15526 
Table 41. Table relations
To tablePurposeFrom columnsTo columnsComments
Period keyPeriodKey
  • Period key

Picture file name

If, for example, you want to scan in or link to a picture of one of your vouchers, you can enter the file name for the picture in this field.

The value in the field is transferred from the voucher lines to updated vouchers and on to the transactions and open entries. If you use the Design/Add/Visualise menu item, the contents in this field is used.

Tip:
Double-clicking or pressing * in this box opens the picture. If the box is empty, a dialog box for selecting a picture file will open.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainPicture file nameText (260)
Write AccessNoneYou are not allowed to modify the value in this field.
SQL namePictNoThe database field name.
API identifierpictureFileNameThe API identifier used in GraphQL.
Number9179 

Pre-approved

Pre-approved for payment in Visma.net AutoPay.

The transaction has been approved for payment in Visma.net Approval. Approval of the payment in Visma.net AutoPay should not be required. This value can be removed, but not be set.

PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainBooleanInteger
Write AccessNoneYou are not allowed to modify the value in this field.
Memory fieldYesThe value in this field is only displayed in the program, it is not stored in the database.
API identifierpreapprovedThe API identifier used in GraphQL.
Number18575 

Previous voucher no.

When you fill in this field in a voucher line and you have checked the Authorisation box in the batch to which the voucher is joined, the General ledger transaction with this voucher number are reversed.

This only applies to transactions that are not automatically generated. Business NXT rejects voucher numbers for which there are no general ledger transactions.

The following fields are filled in in the voucher line:

  • The fields for debit/credit account number are filled in reversed.
  • The Amount field is filled in with the amount excluding VAT.
  • The Currency no., Exchange rate, Amount in currency and Quantity fields and organisational units are copied from the arrival voucher. If the currency is the same as the default currency, the currency amount is set as equal to the amount in default currency.
  • The Order no. field from the Open supplier entry is filled in.

At the same time, Business NXT displays the Open supplier entry in a separate Open supplier entry page element that has to be joined to the Voucher table. The following fields in this window are filled in:

  • The Att. voucher no. field in the supplier entry is set as equal to the Voucher no. field on the voucher line, if the Voucher no. in the entry is the same as the Previous voucher no. in the voucher line.
  • The Auth. date 1 field is set to the current date in the Open supplier entry table.
  • When the Priority field is filled in in the voucher line, this value is copied to the supplier entry.

Business NXT prevents authorisation of the same transaction several times. When you authorise a general ledger transaction, Business NXT checks the Authorised option in the dialog box for the Trans. status field.

If you delete or overwrite the Previous voucher no. field or delete the entire voucher line, this check is removed. If there is no value in the Voucher no. field when Previous voucher no. is filled in, the value in the Previous voucher no. field is copied to the Voucher no. field. If the contents of the Previous voucher no. field are deleted, the contents of the Voucher no. field are also deleted.

The previous voucher number is copied to subsequent voucher lines with the same voucher number.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainVoucher no.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL namePrevVoNoThe database field name.
API identifierpreviousVoucherNoThe API identifier used in GraphQL.
Number6260 

Priority

Group incoming and outgoing invoices according to priority, e.g. to select invoices for payment suggestions.

The different voucher types can be assigned a fixed priority in the Voucher type table. The priority specified for the voucher type will be suggested in the voucher line. The Priority field is included in the Open supplier entry table when the vouchers are updated, and the value can be overridden. If you choose to use the Priority field as a status indicator, the vouchers may pass through a number of different stages before the entry is settled.

If you double click or enter * in the field, you bring up the Payment priority dialog box with all the priorities that have been entered for default language, if any texts have been defined in terms of priority. This could be:

  • 1. Payment priority 1
  • 2. Payment priority 2
  • 8. For authorisation
  • 9. Do not remit

You can start using the Priority field after Business NXT has been in use a while, if you find that you need more opportunities to select invoice vouchers.

The cursor pauses in the Priority field when you enter customer and supplier account and you have enabled authorisation in the batch head.

Payment priority texts for different languages can be defined in the Text table. These texts has text type 67.
Note:
If you double-click or press * in this field, you can look up a Payment priority in the Text table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainPayment priorityInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL namePriThe database field name.
API identifierpriorityThe API identifier used in GraphQL.
Number1011 

Product no.

The product number for an invoice.

If both Order no. and Product no. fields are filled in in the voucher, a new order line will be added to the order when you update the batch. This is provided you have the value 1 - Update order in the Update order field in the Voucher type table.

The Quantity field on the Order line will when updating be set as equal to the value in the Quantity field on the Voucher row, or to 1 if no quantity has been entered on the voucher. Cust. no., Sup. no. and Empl. no. are copied from the voucher table to the new order line. The information in the order head in the order lines is updated as during ordinary order entry. When order lines are added on the basis of vouchers, the posted amount excl VAT is transferred to the order lines and divided by the Quantity to calculate the Price and Price (dom.) on the Order line. If the product is exempt from warehousing, the same amount is also set as the Cost price and Cost price (dom.) on the order line. This is particularly useful for further invoicing of expenses in connection with projects and assignments. The incoming invoice is entered once only, and is re-invoiced directly.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainProduct no.Text (40)
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameActThe database field name.
API identifierproductNoThe API identifier used in GraphQL.
Number1018 
Table 42. Table relations
To tablePurposeFrom columnsTo columnsComments
ProductProduct
  • Product no.
Search productSearchProduct
  • Product no.

Quantity

A quantity for the voucher.

The cursor only pauses in the Quantity field if you have checked the Enter quantity box in the General ledger account table for the Debit account or Credit account in the voucher. Even if the cursor skips the field, you can of course use the arrow keys to return to the field and enter a quantity.

You do not define the type of unit of the quantity, and all the quantities entered are added together in the General ledger balance for the account. You should therefore only use one quantity unit per account to produce a meaningful balance (so that you do not add up boxes and metres). This means that there must be a separate sales account for each unit for which you want a balance.

You must not post the Quantity field with a preceding sign. A volume posted to a credit account number is interpreted as a negative quantity. It is up to you to decide whether to use the quantity term as a PL or balance sheet figure.

If you include quantities both in invoices and on payment, the quantity balance for the ledger number will be zero. As with the amount and currency amount fields, the quantity balances for General ledger account and customers/suppliers are totalled. You can print the quantity balances in account statements and balance lists. The quantity is regarded as turnover, and is reset at the start of a new financial year unless you have posted the quantity to an organisational unit class defined with an accumulated result.

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 Quantity field cannot be printed on profit and loss reports and balance sheet reports.

See also the description for Product no.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainQuantityDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameQtyThe database field name.
API identifierquantityThe API identifier used in GraphQL.
Number1013 

Realisation journal no.

Reflects the Realisation journal from realisation of orders.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainJournal no.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameRealJNoThe database field name.
API identifierrealisationJournalNoThe API identifier used in GraphQL.
Number15276 
Table 43. Table relations
To tablePurposeFrom columnsTo columnsComments
Realisation journalRealisationJournal
  • Realisation journal no.
Realisation journal lineRealisationJournalLine
  • Realisation journal no.
  • Realisation journal line no.
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.

Reference

The reference for matching.

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.

If the Reference field is not filled in, it will be copied from the Invoice no. field when updating the voucher. If this field is not filled in either, it will in turn be copied from the Voucher no. field.

The field will update the Reference field in the Open customer entry and Open supplier entry tables from vouchers containing customer / supplier invoices. This field will be used to match the open entries against Cross reference entered on payment vouchers.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainDoc. no.Text (40)
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameRefThe database field name.
API identifierreferenceThe API identifier used in GraphQL.
Number1008 

Scan doc. no.

The ID of the scanned document.

Is used in connection with Visma Document Center.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainNo.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL namePLDNoThe database field name.
API identifierscanDocumentNoThe API identifier used in GraphQL.
Number11199 

Scan status

The status of the scanned document.

Is used in connection with Visma Document Center.

A look-up in this field gives you the following list of possible values:
1 - Scanned document
2 - Document on flow
4 - Document finished
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainScan statusInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL namePLDFlowThe database field name.
API identifierscanStatusThe API identifier used in GraphQL.
Number11200 

Structured element index

Reference to the relevant <Structured> element within the <PaymentLine> element in the incoming payment file.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainNo.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameStrElIdxThe database field name.
API identifierstructuredElementIndexThe API identifier used in GraphQL.
Number19631 

Sup. no.

The supplier number the voucher applies to.

The field is filled out automatically if the Debit account or the Credit account is filled out with a supplier no (2 - Supplier)

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainSup. no.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameSupThe database field name.
API identifiersupplierNoThe API identifier used in GraphQL.
Number4946 
Table 44. Table relations
To tablePurposeFrom columnsTo columnsComments
AssociateSupplier
  • Sup. no.

Text

A text for the voucher.

Business NXT retrieves the voucher text from the Voucher type table, which is filled in when you enter a voucher type. If you have checked the Enter text box for the voucher type, the cursor pauses in the Text field in the Voucher table to allow you to change the text if necessary. This is useful for invoice vouchers, for example, if you want to enter the invoice number in the voucher text. You can call up the voucher text in all transaction lists. Even if the cursor does not pause on a field, you can return to the field using the arrow keys and edit the voucher text.

PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainTextText (200)
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameTxtThe database field name.
API identifiertextThe API identifier used in GraphQL.
Number989 

Total credit

The sum of credit amounts.

The value is updated with a negative value from the Bank amount field and with values from positive entries which have a cross in the Payment reg. field in the linked Cross reference table.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameSmCrThe database field name.
API identifiersumCreditDomesticThe API identifier used in GraphQL.
Number12358 

Total debit

The sum of debit amounts.

The value is updated with a positive value from the Bank amount field and with values from negative entries which have a cross in the Payment reg. field in the linked Cross reference table.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameSmDbThe database field name.
API identifiersumDebitDomesticThe API identifier used in GraphQL.
Number12357 

Trans. status

The status of the transaction.

A look-up opens the dialog box where you can see the following check boxes and options:

Overwritten

Amount excl. VAT
When you complete the Amount excl. VAT field in the Voucher table, this check box is selected.
VAT amount
This field is checked if you have overridden the VAT amount in the voucher line.
Org. unit
If organisational units are overridden in the General ledger transaction table, Business NXT defines a value here that indicates that the organisational unit has been corrected after updating.

Debt collector

Transferred to debt collector
This field applies only to open customer entries and customer transactions. Business NXT updates the field when you run the Transfer to debt collection processing.
Returned from debt collector
This field applies only to open customer entries and customer transactions. Business NXT updates the field when you run the Return from debt collection processing.
Added during debt collection
This field applies only to open customer entries and customer transactions. Business NXT updates the field when you run the List debt collection related transactions processing.

Duration

Permanent
All regular transactions.
Temporary
Business NXT uses this field in connection with reversal of transactions.
Reversing
Business NXT uses this field in connection with reversal of transactions.

Accounting rule

Created by an accounting rule
The option is automatically enabled when a voucher line is created by an accounting rule.
The field is greyed out in the following tables:
  • Customer transaction
  • Supplier transaction
  • General ledger transaction
  • Capital asset transaction
  • Open customer entry
  • Open supplier entry
Do not apply accounting rule

Per.

Per. Debit acc.
Per. Credit acc.

____

Do not create open entries
Business NXT does not produce open entries for the voucher line. This field overrides the Matching method parameter in the Company information table and Matching method cust./Matching method sup. in the Associate table. You can use this parameter, for example, when converting from other systems in which you want to refer to earlier transactions. You can also increase the speed when updating a batch if you define this flag for vouchers that you know are fully matched.
The field is greyed out in the following tables:
  • Customer transaction
  • Supplier transaction
  • General ledger transaction
  • Capital asset transaction
  • Open customer entry
  • Open supplier entry
Ref. Entry Free of interest
This comes from the order module and will exempt this entry and the cross-reference from interest computation in connection with updating.
Ref. Entry Free of reminder fee
If you in the Order table have selected the Ref. Entry Free of interest check box in Order options, this check box is selected. When you update the batch the post and the cross-references are exempted from interest calculation.
Credit note
Business NXT checks for credit note if the transaction is a credit entry for a customer or a debit entry for a supplier. Business NXT assumes that you have checked the Affects turn./purch. box in the Voucher type table for the relevant voucher type.

This field is used for customer transactions and supplier transactions, and is therefore greyed out in the voucher line.

Authorised
This field is checked if you have authorised a general ledger transaction. You can also check the field manually if the transaction has already been authorised.
Factoring performed
You only use this check box for open customer entries, and it is therefore greyed out in the voucher lines.
Period flow processed
Business NXT will select this field when you execute the Automatic entries processing in the General ledger account table.
Paid
Business NXT will select this field when you transfer the open entry to payment lines. You cannot select the field manually.

Business NXT inserts a cross in this field when you save a cross reference line which has a cross in the Payment reg. field. When you delete a voucher line, transaction status Paid is deleted if you press Delete in the cross reference line or the voucher line, and not in the batch head.

Partly paid in AutoPay
Automatically set when an open customer/supplier entry is updated as a partial payment, i.e. when an approver has overridden the payment amount in Visma.net AutoPay.
Cancelled/Rejected payment
This check box is selected when a payment line is cancelled or rejected. The Paid and Payment no. fields are then deleted, so that you can create payment for the entry once more. This requires that the parameter Set to "Cancelled" for payments not transferred in the EFT processing field of the Bank partner table has been checked.
Prepayment
This check box is selected when OCR transactions are imported containing advance payment. The routine enters the order number in the voucher line. This requires that you have selected the parameter Prepayment in Payment processing in the Company information or Factoring company tables.
Accept transactions with amount 0
If you select this field in a voucher line, transactions are produced even if both the amount and quantity are 0 (zero) in the voucher line.

In these voucher lines and updated voucher lines, 0 (zero) is shown instead of a blank Amount field (in default currency).

The Accept transactions with amount 0 field are greyed out when you open the dialog box in the Trans. status field from tables other than the Voucher table.

Direct debit from order
When posting invoices from the order system, Business NXT checks whether the customer has a direct debiting agreement, and whether the voucher date is within the applicable from and to dates for this. If so, the flag from Direct debit from order is placed in the Trans. status field in the voucher line. If this amount exceeds a maximum amount specified by the customer, the Exceeded max amount flag is inserted.
Exceeded max amount
When posting invoices from the order system, Business NXT checks whether the customer has a direct debiting agreement, and whether the voucher date is within the applicable from and to dates for this. If so, the flag from Direct debit from order is placed in the Trans. status field in the voucher line. If this amount exceeds a maximum amount specified by the customer, the Exceeded max amount flag is inserted.
Do not update exchange rate from voucher date
The voucher line’s exchange rate from the Currency rate or Currency rate 2 table will not be updated when you change the voucher date.
Debt collection voucher lines already expanded
Value date overridden
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainTrans. statusInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameTransStThe database field name.
API identifiertransactionStatusThe API identifier used in GraphQL.
Number6271 

Unit

A unit for the voucher.

The field refers to the Unit table and can be used to define the unit if a quantity has been entered in the Quantity field.

Unit texts for different languages can be defined in the Text table. These texts has text type 16.
Note:
If you double-click or press * in this field, you can look up a Unit in the Text table.
Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainUnitInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameUnThe database field name.
API identifierunitThe API identifier used in GraphQL.
Number10558 
Table 45. Table relations
To tablePurposeFrom columnsTo columnsComments
UnitUnit
  • Unit

Value date

The value date.

The Value date field completes the Period, Year, VAT year and VAT term 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 period and VAT year to the correct periods and years manually.

Note:
You do not need to complete the Value date field in the voucher unless the voucher is to be posted for an accounting period or VAT period that is different from what is entered in the batch. If the Value date field is left blank in the voucher, the Value date field defined for the batch is used.

Value date is a date field, which you must enter in the format as 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 previous voucher. If you enter + in the field, the system copies the date from the batch. The cursor moves to the next field which means you do not have to press Enter.

The date is validated using the regional settings in Windows.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainDateInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameValDtThe database field name.
API identifiervalueDateThe API identifier used in GraphQL.
Number987 

VAT amount

The VAT amount.

When you complete the Amount field in a voucher line, where a Debit VAT code or a Credit VAT code exists, Business NXT calculates the VAT amount and suggests it in the VAT amount field. If you make a change in the Amount field, the VAT amount will be recalculated.

You can override the value in the VAT amount field if it differs from the invoice or other document you are posting. If this field is empty, for example after importing data, the VAT amount will be calculated when the batch is updated.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameVatAmThe database field name.
API identifiervatAmountDomesticThe API identifier used in GraphQL.
Number6234 

VAT amount in currency

The VAT amount in currency of the voucher.

When you fill in the Amount in currency field in a voucher line, where a Debit VAT code or a Credit VAT code exists, Business NXT calculates the VAT amount and suggests it in the VAT amount in currency field. If you make a change in the Amount in currency field, the VAT amount will be recalculated.

You can override the value in the VAT amount in currency field if it differs from the invoice or other document you are posting. If this field is empty, for example after importing data, the VAT amount will be calculated when the batch is updated.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameCurVatAmThe database field name.
API identifiervatAmountInCurrencyThe API identifier used in GraphQL.
Number18159 

VAT term

The VAT period to use.

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

Note:
You do not need to complete the Year, Period, VAT year and VAT term fields for the voucher unless the voucher is to be posted for an accounting period or VAT period that is different from the rest of the batch. To make it easier to reconcile, we recommend that you use the Value date field instead.

The Year, Period, 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 period for the batch to be updated. Even if a company is not liable to pay tax, at least one VAT period must be defined to cover the entire financial year. The suspension date is 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.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainPeriodInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameTxTrmThe database field name.
API identifiertaxTermThe API identifier used in GraphQL.
Number4507 
Table 46. Table relations
To tablePurposeFrom columnsTo columnsComments
VAT periodTaxTerm
  • VAT year
  • VAT term
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.

VAT year

The VAT year to use.

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

Note:
You do not need to complete the Year, Period, VAT year and VAT term fields for the voucher unless the voucher is to be posted for an accounting period or VAT period that is different from the rest of the batch. To make it easier to reconcile, we recommend that you use the Value date field instead.

The Year, Period, 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 period for the batch to be updated. Even if a company is not liable to pay tax, at least one VAT period must be defined to cover the entire financial year. The suspension date is 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.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainYearInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameTxYrThe database field name.
API identifiertaxYearThe API identifier used in GraphQL.
Number4506 
Table 47. Table relations
To tablePurposeFrom columnsTo columnsComments
VAT periodTaxTerm
  • VAT year
  • VAT term
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.
OSS VAT periodOssTaxTerm
  • VAT year
  • OSS VAT term
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.

Visma ID

The ID of the scanned document.

Is used in connection with Visma Document Center.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainNo.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameWfIdThe database field name.
API identifiervismaIdThe API identifier used in GraphQL.
Number11198 

Voucher date

The actual date of the voucher, e.g. the invoice date.

This date is used for automatic calculation of the due date for customer and supplier entries.
Note:
The voucher date does not relate to Accounting period or VAT period
Note:
If the due date is entered manually or the voucher date is the same as the value date of the batch, Business NXT sets the voucher date as equal to the value date when the batch is updated. In such instances you do not therefore have to enter the voucher date manually.

The Voucher date field is a date field, which you enter in the format as defined in the regional settings in Windows. You only need to enter the date and month number for dates in the same year as the Value date of the batch. A check is performed to ensure the date entered is valid. A warning or an error message is given if the voucher date is further away from the current date than the number of days as defined in the No. of days +/- warning or No. of days +/- rejection fields in the Company information table.

If you enter + in this field, the Value date defined for the batch is entered. If you enter / in the field, the Voucher date from the previous voucher line is repeated. The cursor moves to the next field which means you do not have to press Enter.

Updating of currency in amount

Updating of currency in amount requires you to have selected the Update exchange rate from voucher date field in the Voucher type processing field in the Voucher type table.

You have various currencies (ISO codes) in the Currency table. There is a sales rate for each currency here. In the Exchange rate table, you can enter several sales rates for one currency with a different from date.

It is also possible with daily automatically update of the Exchange rate table, if you have integration with Visma.net AutoPay.

If currency USD has a sales rate of 7 in the Currency table and the following in the Currency rate table:
  • From date = 01/02/2018 and Sales rate = 7.5
  • From date = 01/04/2018 and Sales rate = 8

When you have entered a voucher with a voucher date of 01.01.2018, the exchange rate will be 7 and the amount will be NOK 700.

If you enter a voucher with a voucher date of 01.02.2018, the exchange rate will be 7.5 and the amount will be NOK 750.

If you enter a voucher a with a voucher date of 01.04.2018, the exchange rate will be 8 and the amount will be NOK 800.

If you change the voucher date to 01.01.2018, the exchange rate will change to 7 and the amount will become NOK 700.

The date is validated using the regional settings in Windows.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainDateInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameVoDtThe database field name.
API identifiervoucherDateThe API identifier used in GraphQL.
Number986 
Table 48. Table relations
To tablePurposeFrom columnsTo columnsComments
Supplier transactionSupplierTransaction_VoucherNoAndDate
  • Voucher no.
  • Voucher date
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.
Open supplier entryOpenSupplierEntry_VoucherNoAndDate
  • Voucher no.
  • Voucher date
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.
VoucherVoucher_VoucherNoAndDate
  • Voucher no.
  • Voucher date
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.
Updated voucherUpdatedVoucher_VoucherNoAndDate
  • Voucher no.
  • Voucher date
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.
Customer transactionCustomerTransaction_VoucherNoAndDate
  • Voucher no.
  • Voucher date
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.
Open customer entryOpenCustomerEntry_VoucherNoAndDate
  • Voucher no.
  • Voucher date
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.
Capital asset transactionCapitalAssetTransaction_VoucherNoAndDate
  • Voucher no.
  • Voucher date
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.
General ledger transactionGeneralLedgerTransaction_VoucherNoAndDate
  • Voucher no.
  • Voucher date
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.
Accounting transactionAccountingTransaction_VoucherNoAndDate
  • Voucher no.
  • Voucher date
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.

Voucher group 1

Grouping value for sorting or selecting vouchers.

You define the codes you want to use and what they should represent. You can also change the description/column heading for the fields. You can define valid values for these fields in the Text table.

Voucher group 1 texts for different languages can be defined in the Text table. These texts has text type 163.
Note:
If you double-click or press * in this field, you can look up a Voucher group 1 in the Text table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainVoucher group 1Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameVoGr1The database field name.
API identifiervoucherGroup1The API identifier used in GraphQL.
Number6152 

Voucher group 2

Grouping value for sorting or selecting vouchers.

You define the codes you want to use and what they should represent. You can also change the description/column heading for the fields. You can define valid values for these fields in the Text table.

Voucher group 2 texts for different languages can be defined in the Text table. These texts has text type 164.
Note:
If you double-click or press * in this field, you can look up a Voucher group 2 in the Text table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainVoucher group 2Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameVoGr2The database field name.
API identifiervoucherGroup2The API identifier used in GraphQL.
Number6153 

Voucher jour. no.

The voucher journal number.

Is stamped on voucher lines that are created with the Create new batch processing in the Updated batch table or the Create new voucher processing in the Updated voucher table.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainJournal no.Integer
Primary keyYesVoucher jour. no., Batch no., Line no.
SQL nameJNoThe database field name.
API identifiervoucherJournalNoThe API identifier used in GraphQL.
Number982 
Table 49. Table relations
To tablePurposeFrom columnsTo columnsComments
Updated batchUpdatedBatch
  • Voucher jour. no.
  • Batch no.
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.
Updated voucherVoucher
  • Voucher jour. no.
  • Batch no.
  • Voucher no.
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.
Realisation journalRealisationJournalVoucherJournalNo
  • Voucher jour. no.

Voucher no.

A unique number identifying the voucher line.

This number identifies the vouchers from the time they are entered in the update tables and in the transaction and open entry tables.

If a voucher series has been specified for the batch, you can enter + in the Voucher no. field in the first row of the voucher for a new batch. The next voucher number for the current voucher series will then be retrieved from the Voucher series table. At the same time the counter is incremented by one. If you are not using voucher series, you must know the starting voucher number.

Note:
Business NXT does not check whether the voucher number entered has been used before unless you have selected voucher number control 2 - Check that voucher no. has not been used before or 3 - Check both voucher series and numbers from the dialog box for the Voucher no. control field in the Company information table. Such a control places a heavy demand on resources. Business NXT only controls against voucher numbers in the table Updated voucher. Voucher numbers in batches that have not been updated are therefore not controlled.

After you have entered the first voucher line of the batch, you can enter + in the Voucher no. field to obtain the next voucher number. If the voucher is not balanced, i.e. if the same amounts have not been posted to credit and debit accounts, entering + in the Voucher no. field will produce the same voucher number as the line above. The cursor moves to the next field in the table.

If you delete a voucher in the batch, the voucher number is not suggested again. Unless you enter the deleted voucher number manually, there will therefore be a gap in the number series.

If you delete the voucher number in the last voucher, the Next voucher no. field in the Voucher series table is reset, and when you enter + in the Voucher no. field the next time you bring up the voucher number that you deleted.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainVoucher no.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameVoNoThe database field name.
API identifiervoucherNoThe API identifier used in GraphQL.
Number985 
Table 50. Table relations
To tablePurposeFrom columnsTo columnsComments
Updated voucherVoucher
  • Voucher jour. no.
  • Batch no.
  • Voucher no.
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.
Supplier transactionSupplierTransaction_VoucherNo
  • Voucher no.
Supplier transactionSupplierTransaction_VoucherNoAndDate
  • Voucher no.
  • Voucher date
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.
Open supplier entryOpenSupplierEntry_VoucherNo
  • Voucher no.
Open supplier entryOpenSupplierEntry_VoucherNoAndDate
  • Voucher no.
  • Voucher date
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.
VoucherVoucher_VoucherNo
  • Voucher no.
VoucherVoucher_VoucherNoAndDate
  • Voucher no.
  • Voucher date
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.
Updated voucherUpdatedVoucher_VoucherNo
  • Voucher no.
Updated voucherUpdatedVoucher_VoucherNoAndDate
  • Voucher no.
  • Voucher date
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.
Customer transactionCustomerTransaction_VoucherNo
  • Voucher no.
Customer transactionCustomerTransaction_VoucherNoAndDate
  • Voucher no.
  • Voucher date
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.
Open customer entryOpenCustomerEntry_VoucherNo
  • Voucher no.
Open customer entryOpenCustomerEntry_VoucherNoAndDate
  • Voucher no.
  • Voucher date
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.
Capital asset transactionCapitalAssetTransaction_VoucherNo
  • Voucher no.
Capital asset transactionCapitalAssetTransaction_VoucherNoAndDate
  • Voucher no.
  • Voucher date
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.
General ledger transactionGeneralLedgerTransaction_VoucherNo
  • Voucher no.
General ledger transactionGeneralLedgerTransaction_VoucherNoAndDate
  • Voucher no.
  • Voucher date
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.
Accounting transactionAccountingTransaction_VoucherNo
  • Voucher no.
Accounting transactionAccountingTransaction_VoucherNoAndDate
  • Voucher no.
  • Voucher date
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.

Voucher processing

Options for processing of vouchers.

A look-up opens the dialog box where you can see the following check boxes and options:
Locked
Enabling this option restricts manual editing of fields in a voucher line. This function is specifically designed for Swedish companies working with pre-registration.
When running the Update supplier transactions processing in the Batch table, the Locked option will be automatically set on voucher lines in the Voucher table, if the following conditions are met:
  • The voucher line contains the general ledger account specified in the Interim cost account field in the Company information table
  • Pre-registration for incoming invoices is selected for Workflow processing in the Company information table

This function restricts manual editing of fields in the affected voucher lines while allowing all processing activities to continue operating without regards to this setting. You can also enable and disable the Locked option manually in the Voucher processing field.

Ledger adjustment
Proposed accounting rule
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainVoucher processingInteger
SQL nameVoProThe database field name.
API identifiervoucherProcessingThe API identifier used in GraphQL.
Number20578 

Voucher type

The voucher type controls several aspects of how the voucher is processed, both before and during update.

The voucher type determines the voucher text to be posted with the voucher, and how the voucher is processed. The voucher type determines whether the cursor pauses in the Text field and Currency fields, whether the amount posted for customers and suppliers is included in accumulated turnover/purchases, and whether any tax codes are ignored. Even if the cursor does not pause in a field when you press the Enter or Tab keys, you can still return to the field using the arrow keys or the mouse.

Note:
Entering the correct voucher type is most important when posting invoices and credit notes as well as vouchers concerning currency corrections.

Invoices/credit notes are not included in the total turnover/purchases in the customers/suppliers balance tables if you post them to a voucher type for which you have not checked the Affects turn./purch. box in the Voucher type table. In the Voucher type table supplied with the standard table structure -xxxfirm.txt-, this field is checked for voucher types 11 to 15 (outgoing invoices/credit note), and voucher types 21 to 25 (incoming invoices/credit note). In order to reverse an updated voucher using these voucher types, the same voucher type must also be used for the correction voucher to ensure that the turnover/purchases are correct. Receipts must not be included in total turnover/total purchases, and must therefore be posted using a voucher types other than invoices.

If a voucher series has been defined for the batch, entering + in the Voucher type field causes the Voucher type to be linked to the voucher series. Entering / in the field causes the Voucher type from the previous voucher line to be copied. The cursor moves to the next field which means you do not have to press Enter.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainVoucher typeInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameVoTpThe database field name.
API identifiervoucherTypeThe API identifier used in GraphQL.
Number988 
Table 51. Table relations
To tablePurposeFrom columnsTo columnsComments
Voucher typeVoucherType
  • Voucher type

W/off variance cash discount

The W/off variance cash discount.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL namePmVaAmCDThe database field name.
API identifierwriteOffVarianceCashDiscountDomesticThe API identifier used in GraphQL.
Number11067 

W/off variance cash discount in currency

The W/off variance cash discount in currency.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
Memory fieldYesThe value in this field is only displayed in the program, it is not stored in the database.
API identifierwriteOffVarianceCashDiscountInCurrencyThe API identifier used in GraphQL.
Number11065 

W/off variance cash discount in EURO

The W/off variance cash discount in EURO.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Source columnW/off variance cash discount in currencyEuro
Write AccessNoneYou are not allowed to modify the value in this field.
Memory fieldYesThe value in this field is only displayed in the program, it is not stored in the database.
API identifierwriteOffVarianceCashDiscountInEuroThe API identifier used in GraphQL.
Number11066 

W/off variance misc.

The W/off variance misc.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL namePmVaAmThe database field name.
API identifierwriteOffVarianceMiscDomesticThe API identifier used in GraphQL.
Number11070 

W/off variance misc. in currency

The W/off variance misc. in currency.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
SQL namePmVaCAmThe database field name.
API identifierwriteOffVarianceMiscInCurrencyThe API identifier used in GraphQL.
Number11068 

W/off variance misc. in EURO

The W/off variance misc. in EURO.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Source columnW/off variance misc. in currencyEuro
Write AccessNoneYou are not allowed to modify the value in this field.
Memory fieldYesThe value in this field is only displayed in the program, it is not stored in the database.
API identifierwriteOffVarianceMiscInEuroThe API identifier used in GraphQL.
Number11069 

W/off variance total

The W/off variance total.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
Memory fieldYesThe value in this field is only displayed in the program, it is not stored in the database.
API identifierwriteOffVarianceTotalDomesticThe API identifier used in GraphQL.
Number11064 

W/off variance total in currency

The W/off variance total in currency.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Write AccessNoneYou are not allowed to modify the value in this field.
Memory fieldYesThe value in this field is only displayed in the program, it is not stored in the database.
API identifierwriteOffVarianceTotalInCurrencyThe API identifier used in GraphQL.
Number11062 

W/off variance total in EURO

The W/off variance total in EURO.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAmountDecimal
Source columnW/off variance total in currencyEuro
Write AccessNoneYou are not allowed to modify the value in this field.
Memory fieldYesThe value in this field is only displayed in the program, it is not stored in the database.
API identifierwriteOffVarianceTotalInEuroThe API identifier used in GraphQL.
Number11063 

Web page

If, for example, you want to link a special web page to one of your vouchers, you can enter the address here.

You can, for example, use the field to link to scanned documents which are a copy of the voucher so that you can later perform look-ups from the transactions in order to see the voucher electronically. The value in the field is transferred from the voucher lines to updated vouchers and on to the transactions and open entries.

Double-click or press * to open the web page in your web browser.

Alternatively the field can be used to refer to documents or other files. Double-click or press * in the empty field to open the Select file dialog box.

On the Design tab, in the Insert group, you can click on Web page to visualise the document or web page on the screen.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainWeb pageText (260)
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameWebPgThe database field name.
API identifierwebPageThe API identifier used in GraphQL.
Number9180 

Year

The accounting year to use.

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

Note:
You do not need to complete the Year, Period, VAT year and VAT term fields for the voucher unless the voucher is to be posted for an accounting period or VAT term that is different from the rest of the batch. To make it easier to reconcile, we recommend that you use the Value date instead.

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 for the batch to be updated. Even if a company is not liable to pay tax, at least one VAT period must be defined to cover the entire financial year. The suspension date is 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.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainYearInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameAcYrThe database field name.
API identifieryearThe API identifier used in GraphQL.
Number4504 
Table 52. Table relations
To tablePurposeFrom columnsTo columnsComments
Accounting periodAccountingPeriod
  • Year
  • Period
This is a combined foreign key. Making a lookup in one of the fields may also fill in value in the others.

Control columns

Control columns include information about who has changed the record last and when, and which process that is currently editing the record.

Changed by provenance

The provenance for the record change.

A look-up in this field gives you the following list of possible values:

0 - None

1 - UI

10 - External API

20 - GAiA

21 - AI Connect

100 - Internal service

101 - Task automation

102 - AutoInvoice download

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainProvenanceInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameChPvnThe database field name.
API identifierchangedByProvenanceThe API identifier used in GraphQL.
NumberA unique column number. 

Changed by user

The name of the user that changed the record.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainUser nameText (24)
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameChUsrThe database field name.
API identifierchangedByUserThe API identifier used in GraphQL.
NumberA unique column number. 

Changed date

The date when the record was changed.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainDateInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameChDtThe database field name.
API identifierchangedDateThe API identifier used in GraphQL.
NumberA unique column number. 

Changed time

The time when the record was changed.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainTimeInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameChTmThe database field name.
API identifierchangedTimeThe API identifier used in GraphQL.
NumberA unique column number. 

Changed time stamp

The date and time when the record was changed.

The field is updated with the UTC time.

This value can be used by external systems to replicate changed data. The column is indexed. 

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainDate/timeDateTime
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameChTsThe database field name.
API identifierchangedTimestampThe API identifier used in GraphQL.
NumberA unique column number. 

Created by provenance

The provenance for the record creation.

A look-up in this field gives you the following list of possible values:

0 - None

1 - UI

10 - External API

20 - GAiA

21 - AI Connect

100 - Internal service

101 - Task automation

102 - AutoInvoice download

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainProvenanceInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameCrePvnThe database field name.
API identifiercreatedByProvenanceThe API identifier used in GraphQL.
NumberA unique column number. 

Created by user

The name of the user that created the record.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainUser nameText (24)
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameCreUsrThe database field name.
API identifiercreatedByUserThe API identifier used in GraphQL.
NumberA unique column number. 

Created date

The date when the record was created.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainDateInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameCreDtThe database field name.
API identifiercreatedDateThe API identifier used in GraphQL.
NumberA unique column number. 

Created time

The time when the record was created.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainTimeInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameCreTmThe database field name.
API identifiercreatedTimeThe API identifier used in GraphQL.
NumberA unique column number. 

Created time stamp

The date and time when the record was created.

The field is updated with the UTC time.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainDate/timeDateTime
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameCreTsThe database field name.
API identifiercreatedTimestampThe API identifier used in GraphQL.
NumberA unique column number. 

Edit status

The current status of the record.

A look-up in this field gives you the following list of possible values:

0 - Unchanged: The record is read, but not changed.

1 - Inserted: The record is new.

2 - Changed: The record is changed.

3 - Deleted: The record is deleted.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainEdit statusInteger
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameLckStThe database field name.
API identifiereditStatusThe API identifier used in GraphQL.
NumberA unique column number. 

Process no

The Process no. from the Active company process table which is currently using or has control of this record.

Note:
If you double-click or press * in this field, you can look up a value in the related table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainProcess no.Integer
Write AccessNoneYou are not allowed to modify the value in this field.
SQL nameChPrcThe database field name.
API identifierlockedByProcessNoThe API identifier used in GraphQL.
NumberA unique column number. 
Table 53. Table relations
To table Purpose From columns To columns Comments
Active company process CompanyProcess Process no. Process no.