General ledger account

This table contains one row for each general ledger account.

The following fields exist in this table:

Account group

The Account group where the account belongs to.

There is no restriction on the number of general ledger Account group. These are entered in the Account group table. You can edit out each Account group on the Profit and loss account and balance sheet as a totals line.

If you imported the standard table structure during setup, Account group will have been set up in accordance with Norwegian Standard 4102 for private companies and public limited companies. The system also suggests a Profit and loss account and balance sheet report that uses these Account group.

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 groupText (60)
SQL nameAcGrThe database field name.
API identifieraccountGroupThe API identifier used in GraphQL.
Number1483 
Table 1. Table relations
To tablePurposeFrom columnsTo columnsComments
Account groupAccountGroup
  • Account group

Account no.

A unique number identifying General ledger account.

The Account no. is used as a reference in all tables that refer to the General ledger account. It also applies for voucher entries and budgeting, to ensure the relevant General ledger account is used. The Norwegian Standard uses four-digit account numbers.

If you want the Account no. to be made up of a minimum number of digits, enter the number in the Digits in account no. w/0 field in the Company information table. If you enter a new General ledger account with fewer digits than the number you specified in this field, Visma Business adds the relevant number of zeros in front of the digit to meet the criterion. You can still enter Account no. with more digits than the number you specified in the Digits in account no. w/0 field.

Note:
This does not affect existing account numbers that consist of more digits.

If you define a number series for General ledger account numbers in the Account no. series tables, the Account no. will be suggested accordingly. If you follow the number series, the Account no. will be a unique account reference, and you can hide the Account type field in the Voucher entry window.

Note:
If you press + in this field, the next available number is suggested. Gaps in the number series resulting from any deleted rows are not suggested. If you enter an existing number you will receive an error message. The number cannot be changed once it is entered.
PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainAccount no.Integer
Primary keyYesAccount no.
SQL nameAcNoThe database field name.
API identifieraccountNoThe API identifier used in GraphQL.
Number1480 

Account processing

The "Specify transactions from external application" selection box in the dialog box below the Account processing field is not processed by Visma Business, but by external systems.

External processing

If you have selected the "You are not authorised to delete data" field, you will not be able to delete the row in Visma Business, even if there are no transactions linked to the row. This field is intended for use when another program has imported the data and you want to prevent the row being deleted by mistake.

Note:

There are no restrictions on who can select or deselect this field.

A look-up opens the dialog box where you can see the following check boxes and options:
Specify transactions from external system
Do not show in accrual accounting dialog
No access to delete
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAccount processingInteger
SQL nameAcProcThe database field name.
API identifieraccountProcessingThe API identifier used in GraphQL.
Number14902 

Account subtype

The account subtype that will be used for reporting purposes.

A look-up in this field gives you the following list of possible values:
1 - Asset
2 - Cost
3 - Debt
4 - Income
5 - Unknown
6 - Internal
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAccount subtypeInteger
SQL nameAcSubTpThe database field name.
API identifieraccountSubTypeThe API identifier used in GraphQL.
Number18480 

Account template

You can use the accounts template to create new General ledger account with the same setting/values.

If you want to create a new General ledger account with the same properties as one you know from before, you can enter the new account number, account name and then the value of the one you want to use as a template. All the values from this General ledger account will then be entered, apart from the fields that you filled in yourself.

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.
DomainAccount no.Integer
Memory fieldYesThe value in this field is only displayed in the program, it is not stored in the database.
API identifiertemplateAccountNoThe API identifier used in GraphQL.
Number8748 
Table 2. Table relations
To tablePurposeFrom columnsTo columnsComments
General ledger accountAccountTemplate
  • Account template

Accrual accounting

Select this field if you want to display the Accrual accounting dialog box when you enter amounts in the voucher lines. You will find the corresponding field in the Voucher type table, so that you can select automatic accrual accounting based on both Account no. and Voucher type.

PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainBooleanInteger
SQL namePerThe database field name.
API identifieraccrualAccountingThe API identifier used in GraphQL.
Number6266 

Auto.entry processing

How to process Automatic entry.

A look-up in this field gives you the following list of possible values:
1 - Expand on voucher lines
If you want the system to display automatic entries defined for the account concerned during voucher entry. The automatic entries are expanded when you complete the amount field on the voucher line. You can also use the processing Expand automatic entries in the voucher table to expand automatic entries.
2 - Calculate from period flows
The automatic entries will be calculated on the basis of the account movements within specified periods.
Note:
Automatic entries routine only works if Auto.entry processing2 - Calculate from period flows is set from General ledger account table, and not from Automatic entry table.

It is possible to verify that Auto.entry processing has been performed on General ledger account level for a certain period. For Auto.entry processing2 - Calculate from period flows, General ledger balance table : Sum debit aut. flow and Sum credit aut. flow columns have to be verified. If the columns are empty, the Auto.entry processing2 - Calculate from period flows has been run. If they contain amounts, it means that Auto.entry processing 2 has to be performed on General ledger account again.

3 - Calc. from period flows on org. units also
The automatic entries will be calculated on the basis of the account movements within specified periods and on individual org. units.
Note:
Automatic entries routine only works if Auto.entry processing3 - Calc. from period flows on org. units also is set from General ledger account table, and not from Automatic entry table.

It is possible to verify that Auto.entry processing has been performed on General ledger account level for a certain period. If the Auto.entry processing3 - Calc. from period flows on org. units also has been run, it will update Trans. status field: Period flow processed in General ledger transaction table.

PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainAuto.entry processingInteger
SQL nameExpAutThe database field name.
API identifierautomaticEntryProcessingThe API identifier used in GraphQL.
Number3679 

Balance processing

How to process the balances.

When the option Create all balance periods is ticked and the processing Regenerate general ledger account balances is executed, records for each Accounting period in Year containing General ledger transaction will be created in the General ledger balance

A look-up opens the dialog box where you can see the following check boxes and options:
Create all balance periods
One record per month is generated in the General ledger balance table when you are running the Create acc balances for all periods processing in the Accounting period table.

If the check box is not selected then only one record is created for the whole year.

Note:
You need to select the Create all balance periods check box in the Balance processing field in the General ledger account table as well. Otherwise the settings in the organisational unit table will not be taken into consideration when balances are created.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainBalance processingInteger
SQL nameBalProcThe database field name.
API identifierbalanceProcessingThe API identifier used in GraphQL.
Number14376 

Currency no.

You can setup General ledger account with a particular currency.

The Currency no. and rate are suggested during each Voucher entry for the account concerned. If a voucher is posted to two accounts with different currency numbers, the account entered first determines the Currency no. This applies whether the Voucher relates to customers, suppliers or the General ledger account. The Currency no. field is particularly relevant to foreign balance sheet accounts, e.g. deposits in foreign banks. There must be a separate account for each currency to obtain the correct balance in the currency.

Note:
You can change the Currency no. of individual voucher lines by returning to the Currency no. field, but the General ledger balance will only be generated in the currency specified for the General ledger account (as well as in the domestic currency) during updating.

If you imported the standard table structure during the setup, the most common currencies will exist in the Currency table. If you want to change an existing Currency no. or create a new one, you can do so in the help window as in a normal Currencies window.

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.
DomainCurrency no.Integer
SQL nameCurThe database field name.
API identifiercurrencyNoThe API identifier used in GraphQL.
Number1490 
Table 3. Table relations
To tablePurposeFrom columnsTo columnsComments
CurrencyCurrency
  • Currency no.

Currency no. 2

The currency 2 which will be used in the voucher lines.

The currency number will be suggested in the voucher lines if the field is not already completed.

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
SQL nameCur2The database field name.
API identifiercurrencyNo2The API identifier used in GraphQL.
Number14314 
Table 4. Table relations
To tablePurposeFrom columnsTo columnsComments
CurrencyCurrency2
  • Currency no. 2

Distribution key

A predefined Distribution key can be used to distribute the entries to the General ledger account between one or more organisational units on the basis of a percentage. A Distribution key may combine several different organisational unit classes. You can use the Distribution key during Voucher entry.

If a voucher is entered for two General ledger account with different Distribution key, the Distribution key is determined by the General ledger account entered first. 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 defaultYesThis field is visible by default in the table display.
DomainDistribution keyInteger
SQL nameDstGrThe database field name.
API identifierdistributionKeyNoThe API identifier used in GraphQL.
Number1503 
Table 5. Table relations
To tablePurposeFrom columnsTo columnsComments
Distribution keyDistributionKey
  • Distribution key

Enter quantity

If you want to enter quantities for the Account, you can select this field to specify that the cursor should pause in the Quantity field during Voucher entry. This can be relevant for sales accounts, for example.

Even if you leave this field unselected, you can move the cursor back to the field and enter the quantity in vouchers for the Account.
Note:
Different types of units are not supported. All the quantities entered are added in a balance in the General ledger balance (in the same way as amounts). You should therefore keep to one quantity to obtain a meaningful balance.

PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainBooleanInteger
SQL nameInpQtyThe database field name.
API identifierenterQuantityThe API identifier used in GraphQL.
Number2223 

Enter VAT code

If you want to enter VAT code, you can select this field to specify that the cursor should pause in the VAT code field during voucher entry for this account. This makes it easy to change the VAT code, even if you have defined a default VAT code for the account (see the previous field).

If you leave Enter VAT code unselected, you still have the option of changing the VAT code during Voucher entry.

Note:
If the Ignore VAT code field is selected for the Voucher type used in posting the voucher, the system skips the VAT code field even if you have specified that it should pause there. In the Voucher type table supplied with the standard table structure, this only applies to the balance and foreign currency balance Voucher type (types 29 and 30). These Voucher type are used for entering opening balances.

PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainBooleanInteger
SQL nameInpTxCdThe database field name.
API identifierenterTaxCodeThe API identifier used in GraphQL.
Number1487 

Exchange rate

The exchange rate for the currency, used in vouchers when you enter the general ledger account.

The value will be suggested in the Voucher lines when you register the Debit account or Credit account number.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainExchange rateDecimal
SQL nameExRtThe database field name.
API identifierexchangeRateThe API identifier used in GraphQL.
Number14313 

Exchange rate 2

The exchange rate for the currency 2, used in vouchers when you enter the general ledger account.

The value will be suggested in the Voucher lines when you register the Debit account or Credit account number.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainExchange rateDecimal
SQL nameExRt2The database field name.
API identifierexchangeRate2The API identifier used in GraphQL.
Number14315 

Gr. 1

A group to which the account belongs.

Groups are used for selections or sorting General ledger account. We recommend that you change the names of the group fields you want to use to more descriptive names, and keep the rest of the fields hidden.

For those who use Visma Portal, Gr. 12 is used to define which accounts Visma Business is to display for Sales, Purchases, Receipts and Payments.

General ledger account grouping 1 texts for different languages can be defined in the Text table. These texts has text type 30.
Note:
If you double-click or press * in this field, you can look up a General ledger account grouping 1 in the Text table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainGeneral ledger account grouping 1Integer
SQL nameGrThe database field name.
API identifiergroup1The API identifier used in GraphQL.
Number4321 

Gr. 2

A group to which the account belongs.

Groups are used for selections or sorting General ledger account. We recommend that you change the names of the group fields you want to use to more descriptive names, and keep the rest of the fields hidden.

For those who use Visma Portal, Gr. 12 is used to define which accounts Visma Business is to display for Sales, Purchases, Receipts and Payments.

General ledger account grouping 2 texts for different languages can be defined in the Text table. These texts has text type 31.
Note:
If you double-click or press * in this field, you can look up a General ledger account grouping 2 in the Text table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainGeneral ledger account grouping 2Integer
SQL nameGr2The database field name.
API identifiergroup2The API identifier used in GraphQL.
Number4322 

Gr. 3

A group to which the account belongs.

Groups are used for selections or sorting General ledger account. We recommend that you change the names of the group fields you want to use to more descriptive names, and keep the rest of the fields hidden.

For those who use Visma Portal, Gr. 12 is used to define which accounts Visma Business is to display for Sales, Purchases, Receipts and Payments.

General ledger account grouping 3 texts for different languages can be defined in the Text table. These texts has text type 32.
Note:
If you double-click or press * in this field, you can look up a General ledger account grouping 3 in the Text table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainGeneral ledger account grouping 3Integer
SQL nameGr3The database field name.
API identifiergroup3The API identifier used in GraphQL.
Number4323 

Gr. 4

A group to which the account belongs.

Groups are used for selections or sorting General ledger account. We recommend that you change the names of the group fields you want to use to more descriptive names, and keep the rest of the fields hidden.

For those who use Visma Portal, Gr. 12 is used to define which accounts Visma Business is to display for Sales, Purchases, Receipts and Payments.

General ledger account grouping 4 texts for different languages can be defined in the Text table. These texts has text type 33.
Note:
If you double-click or press * in this field, you can look up a General ledger account grouping 4 in the Text table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainGeneral ledger account grouping 4Integer
SQL nameGr4The database field name.
API identifiergroup4The API identifier used in GraphQL.
Number4324 

Gr. 5

A group to which the account belongs.

Groups are used for selections or sorting General ledger account. We recommend that you change the names of the group fields you want to use to more descriptive names, and keep the rest of the fields hidden.

For those who use Visma Portal, Gr. 12 is used to define which accounts Visma Business is to display for Sales, Purchases, Receipts and Payments.

General ledger account grouping 5 texts for different languages can be defined in the Text table. These texts has text type 34.
Note:
If you double-click or press * in this field, you can look up a General ledger account grouping 5 in the Text table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainGeneral ledger account grouping 5Integer
SQL nameGr5The database field name.
API identifiergroup5The API identifier used in GraphQL.
Number4325 

Gr. 6

A group to which the account belongs.

Groups are used for selections or sorting General ledger account. We recommend that you change the names of the group fields you want to use to more descriptive names, and keep the rest of the fields hidden.

For those who use Visma Portal, Gr. 12 is used to define which accounts Visma Business is to display for Sales, Purchases, Receipts and Payments.

General ledger account grouping 6 texts for different languages can be defined in the Text table. These texts has text type 35.
Note:
If you double-click or press * in this field, you can look up a General ledger account grouping 6 in the Text table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainGeneral ledger account grouping 6Integer
SQL nameGr6The database field name.
API identifiergroup6The API identifier used in GraphQL.
Number4326 

Gr. 7

A group to which the account belongs.

Groups are used for selections or sorting General ledger account. We recommend that you change the names of the group fields you want to use to more descriptive names, and keep the rest of the fields hidden.

For those who use Visma Portal, Gr. 12 is used to define which accounts Visma Business is to display for Sales, Purchases, Receipts and Payments.

General ledger account grouping 7 texts for different languages can be defined in the Text table. These texts has text type 80.
Note:
If you double-click or press * in this field, you can look up a General ledger account grouping 7 in the Text table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainGeneral ledger account grouping 7Integer
SQL nameGr7The database field name.
API identifiergroup7The API identifier used in GraphQL.
Number6049 

Gr. 8

A group to which the account belongs.

Groups are used for selections or sorting General ledger account. We recommend that you change the names of the group fields you want to use to more descriptive names, and keep the rest of the fields hidden.

For those who use Visma Portal, Gr. 12 is used to define which accounts Visma Business is to display for Sales, Purchases, Receipts and Payments.

General ledger account grouping 8 texts for different languages can be defined in the Text table. These texts has text type 81.
Note:
If you double-click or press * in this field, you can look up a General ledger account grouping 8 in the Text table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainGeneral ledger account grouping 8Integer
SQL nameGr8The database field name.
API identifiergroup8The API identifier used in GraphQL.
Number6050 

Gr. 9

A group to which the account belongs.

Groups are used for selections or sorting General ledger account. We recommend that you change the names of the group fields you want to use to more descriptive names, and keep the rest of the fields hidden.

For those who use Visma Portal, Gr. 12 is used to define which accounts Visma Business is to display for Sales, Purchases, Receipts and Payments.

General ledger account grouping 9 texts for different languages can be defined in the Text table. These texts has text type 82.
Note:
If you double-click or press * in this field, you can look up a General ledger account grouping 9 in the Text table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainGeneral ledger account grouping 9Integer
SQL nameGr9The database field name.
API identifiergroup9The API identifier used in GraphQL.
Number6051 

Gr. 10

A group to which the account belongs.

Groups are used for selections or sorting General ledger account. We recommend that you change the names of the group fields you want to use to more descriptive names, and keep the rest of the fields hidden.

For those who use Visma Portal, Gr. 12 is used to define which accounts Visma Business is to display for Sales, Purchases, Receipts and Payments.

General ledger account grouping 10 texts for different languages can be defined in the Text table. These texts has text type 83.
Note:
If you double-click or press * in this field, you can look up a General ledger account grouping 10 in the Text table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainGeneral ledger account grouping 10Integer
SQL nameGr10The database field name.
API identifiergroup10The API identifier used in GraphQL.
Number6052 

Gr. 11

A group to which the account belongs.

Groups are used for selections or sorting General ledger account. We recommend that you change the names of the group fields you want to use to more descriptive names, and keep the rest of the fields hidden.

For those who use Visma Portal, Gr. 12 is used to define which accounts Visma Business is to display for Sales, Purchases, Receipts and Payments.

General ledger account grouping 11 texts for different languages can be defined in the Text table. These texts has text type 84.
Note:
If you double-click or press * in this field, you can look up a General ledger account grouping 11 in the Text table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainGeneral ledger account grouping 11Integer
SQL nameGr11The database field name.
API identifiergroup11The API identifier used in GraphQL.
Number6053 

Gr. 12

A group to which the account belongs.

Groups are used for selections or sorting General ledger account. We recommend that you change the names of the group fields you want to use to more descriptive names, and keep the rest of the fields hidden.

For those who use Visma Portal, Gr. 12 is used to define which accounts Visma Business is to display for Sales, Purchases, Receipts and Payments.

General ledger account grouping 12 texts for different languages can be defined in the Text table. These texts has text type 85.
Note:
If you double-click or press * in this field, you can look up a General ledger account grouping 12 in the Text table.
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainGeneral ledger account grouping 12Integer
SQL nameGr12The database field name.
API identifiergroup12The API identifier used in GraphQL.
Number6054 

Grouping category

Alternative to using SAF-T account ID for grouping accounts.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainString of length 40Text (40)
SQL nameGrCatThe database field name.
API identifiergroupingCategoryThe API identifier used in GraphQL.
Number18481 

Grouping code

Alternative to using SAF-T account ID for grouping accounts.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainString of length 40Text (40)
SQL nameGrCdThe database field name.
API identifiergroupingCodeThe API identifier used in GraphQL.
Number18482 

Include in turnover

Select this field if you want the balance of the account to be included in the turnover. This usually applies to all sales and discount accounts. In the General ledger account table supplied with the standard table structure, these are the accounts in the 3000 series), whereas other revenue such as fees, rental and commission are not usually included in the turnover.

All entries posted to accounts with this field selected will be considered as 100 % turnover. You can print out on the PL report the percentage share of the turnover relating to each expenditure and revenue account.

Note:
This field is only used when generating a PL report, and can therefore be changed as required at any time.

PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainBooleanInteger
SQL nameTrnThe database field name.
API identifierincludeInTurnoverThe API identifier used in GraphQL.
Number1488 

Inf. 1

Additional account information.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainInf. @Text (40)
SQL nameInfThe database field name.
API identifierinformation1The API identifier used in GraphQL.
Number3529 

Inf. 2

Additional account information.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainInf. @Text (40)
SQL nameInf2The database field name.
API identifierinformation2The API identifier used in GraphQL.
Number3530 

Inf. 3

Additional account information.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainInf. @Text (40)
SQL nameInf3The database field name.
API identifierinformation3The API identifier used in GraphQL.
Number3531 

Inf. 4

Additional account information.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainInf. @Text (40)
SQL nameInf4The database field name.
API identifierinformation4The API identifier used in GraphQL.
Number3532 

Inf. 5

Additional account information.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainInf. @Text (40)
SQL nameInf5The database field name.
API identifierinformation5The API identifier used in GraphQL.
Number3533 

Inf. 6

Additional account information.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainInf. @Text (40)
SQL nameInf6The database field name.
API identifierinformation6The API identifier used in GraphQL.
Number3534 

Inf. 7

Additional account information.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainInf. @Text (40)
SQL nameInf7The database field name.
API identifierinformation7The API identifier used in GraphQL.
Number6089 

Inf. 8

Additional account information.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainInf. @Text (40)
SQL nameInf8The database field name.
API identifierinformation8The API identifier used in GraphQL.
Number6090 

Memo file name

The file name for the Memo attached to General ledger account.

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)
SQL nameMemoFNmThe database field name.
API identifiermemoFileNameThe API identifier used in GraphQL.
Number10477 

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 defaultNoThis field is not visible by default in the table display.
DomainMemo no.Integer
SQL nameMemoNoThe database field name.
API identifiermemoNoThe API identifier used in GraphQL.
Number19211 
Table 6. Table relations
To tablePurposeFrom columnsTo columnsComments
MemoMemo
  • Memo no.

Name

The name of General ledger account.

The account name is displayed in the status bar when references to the account are made during voucher entry and budgeting to help you check that you are referring to the right account. The account name is also displayed when you include a reference to the Account no. in the Company information, Currency, Voucher type, VAT rate, Automatic entry and Associate tables.

The account name can be included in lists and reports such as account listings and balance lists, as well as specific Profit and loss account and balance sheet reports.

PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainNameText (80)
SQL nameNmThe database field name.
API identifiernameThe API identifier used in GraphQL.
Number1482 

Name 2

A different name for the account, for example the account name in another language.

If you select "Use name 2" in the "PL/Balance" print dialog box, the "Name 2" field is printed on the Profit and loss account and balance sheet reports with account specification.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainNameText (80)
SQL nameNm2The database field name.
API identifiername2The API identifier used in GraphQL.
Number14221 

New account no.

If you want to change the Account no., you can enter the New account no. here

The new account no is used in combination with the processing Change account no.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAccount no.Integer
SQL nameNwAcNoThe database field name.
API identifiernewAccountNoThe API identifier used in GraphQL.
Number6612 

Old account no.

If you have changed an account number, the old account number will be stored here.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainAccount no.Integer
SQL nameOldAcNoThe database field name.
API identifieroldAccountNoThe API identifier used in GraphQL.
Number6613 

Organisational unit 1

Used to indicate the organisational unit to which the vouchers for the General ledger account are normally posted.

The organisational unit will be suggested whenever a Voucher is entered for this general ledger account. If a Voucher is entered for two general ledger accounts with different organisational units, the account entered first determines the organisational unit to be used. The suggested value can be overridden in the Voucher table.

There is one field for each organisational unit class defined, allowing the same Voucher to be posted to more than only one organisational unit.

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 defaultYesThis field is visible by default in the table display.
DomainOrganisational unit no.Integer
SQL nameR1The database field name.
API identifierorgUnit1The API identifier used in GraphQL.
Number1491 
Table 7. Table relations
To tablePurposeFrom columnsTo columnsComments
Organisational unit 1OrgUnit1
  • Organisational unit 1

Organisational unit 1 processing

The processing used for the organisational unit.

Note:
If the field is left blank, the organisational unit is not included in the transactions relating to the active account. If neither the debit nor the credit account is valid for processing of the organisational unit, Business NXT displays a message during voucher entry.
Note:
If obligatory organisational units have not been entered before you update, you will be given an error status for the transactions and a report stating the number of transactions containing errors.
A look-up in this field gives you the following list of possible values:
0 - Not allowed - blocked
1 - In use
Business NXT copies information about the organisational units from the general ledger account, if a value has been entered here.
2 - Stop
The cursor pauses in the organisational unit field when posting to the general ledger account concerned.
3 - Mandatory
The cursor pauses in the organisational unit field when posting to the general ledger account concerned. Business NXT will display a red question mark in compulsory organisational unit fields which have not yet been filled in for the voucher line.
PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainInput statusInteger
SQL nameInpR1The database field name.
API identifierorgUnit1ProcessingThe API identifier used in GraphQL.
Number1497 

Organisational unit 2

Used to indicate the organisational unit to which the vouchers for the General ledger account are normally posted.

The organisational unit will be suggested whenever a Voucher is entered for this general ledger account. If a Voucher is entered for two general ledger accounts with different organisational units, the account entered first determines the organisational unit to be used. The suggested value can be overridden in the Voucher table.

There is one field for each organisational unit class defined, allowing the same Voucher to be posted to more than only one organisational unit.

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 defaultYesThis field is visible by default in the table display.
DomainOrganisational unit no.Integer
SQL nameR2The database field name.
API identifierorgUnit2The API identifier used in GraphQL.
Number1492 
Table 8. Table relations
To tablePurposeFrom columnsTo columnsComments
Organisational unit 2OrgUnit2
  • Organisational unit 2

Organisational unit 2 processing

The processing used for the organisational unit.

Note:
If the field is left blank, the organisational unit is not included in the transactions relating to the active account. If neither the debit nor the credit account is valid for processing of the organisational unit, Business NXT displays a message during voucher entry.
Note:
If obligatory organisational units have not been entered before you update, you will be given an error status for the transactions and a report stating the number of transactions containing errors.
A look-up in this field gives you the following list of possible values:
0 - Not allowed - blocked
1 - In use
Business NXT copies information about the organisational units from the general ledger account, if a value has been entered here.
2 - Stop
The cursor pauses in the organisational unit field when posting to the general ledger account concerned.
3 - Mandatory
The cursor pauses in the organisational unit field when posting to the general ledger account concerned. Business NXT will display a red question mark in compulsory organisational unit fields which have not yet been filled in for the voucher line.
PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainInput statusInteger
SQL nameInpR2The database field name.
API identifierorgUnit2ProcessingThe API identifier used in GraphQL.
Number1498 

Organisational unit 3

Used to indicate the organisational unit to which the vouchers for the General ledger account are normally posted.

The organisational unit will be suggested whenever a Voucher is entered for this general ledger account. If a Voucher is entered for two general ledger accounts with different organisational units, the account entered first determines the organisational unit to be used. The suggested value can be overridden in the Voucher table.

There is one field for each organisational unit class defined, allowing the same Voucher to be posted to more than only one organisational unit.

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 defaultYesThis field is visible by default in the table display.
DomainOrganisational unit no.Integer
SQL nameR3The database field name.
API identifierorgUnit3The API identifier used in GraphQL.
Number1493 
Table 9. Table relations
To tablePurposeFrom columnsTo columnsComments
Organisational unit 3OrgUnit3
  • Organisational unit 3

Organisational unit 3 processing

The processing used for the organisational unit.

Note:
If the field is left blank, the organisational unit is not included in the transactions relating to the active account. If neither the debit nor the credit account is valid for processing of the organisational unit, Business NXT displays a message during voucher entry.
Note:
If obligatory organisational units have not been entered before you update, you will be given an error status for the transactions and a report stating the number of transactions containing errors.
A look-up in this field gives you the following list of possible values:
0 - Not allowed - blocked
1 - In use
Business NXT copies information about the organisational units from the general ledger account, if a value has been entered here.
2 - Stop
The cursor pauses in the organisational unit field when posting to the general ledger account concerned.
3 - Mandatory
The cursor pauses in the organisational unit field when posting to the general ledger account concerned. Business NXT will display a red question mark in compulsory organisational unit fields which have not yet been filled in for the voucher line.
PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainInput statusInteger
SQL nameInpR3The database field name.
API identifierorgUnit3ProcessingThe API identifier used in GraphQL.
Number1499 

Organisational unit 4

Used to indicate the organisational unit to which the vouchers for the General ledger account are normally posted.

The organisational unit will be suggested whenever a Voucher is entered for this general ledger account. If a Voucher is entered for two general ledger accounts with different organisational units, the account entered first determines the organisational unit to be used. The suggested value can be overridden in the Voucher table.

There is one field for each organisational unit class defined, allowing the same Voucher to be posted to more than only one organisational unit.

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 defaultYesThis field is visible by default in the table display.
DomainOrganisational unit no.Integer
SQL nameR4The database field name.
API identifierorgUnit4The API identifier used in GraphQL.
Number1494 
Table 10. Table relations
To tablePurposeFrom columnsTo columnsComments
Organisational unit 4OrgUnit4
  • Organisational unit 4

Organisational unit 4 processing

The processing used for the organisational unit.

Note:
If the field is left blank, the organisational unit is not included in the transactions relating to the active account. If neither the debit nor the credit account is valid for processing of the organisational unit, Business NXT displays a message during voucher entry.
Note:
If obligatory organisational units have not been entered before you update, you will be given an error status for the transactions and a report stating the number of transactions containing errors.
A look-up in this field gives you the following list of possible values:
0 - Not allowed - blocked
1 - In use
Business NXT copies information about the organisational units from the general ledger account, if a value has been entered here.
2 - Stop
The cursor pauses in the organisational unit field when posting to the general ledger account concerned.
3 - Mandatory
The cursor pauses in the organisational unit field when posting to the general ledger account concerned. Business NXT will display a red question mark in compulsory organisational unit fields which have not yet been filled in for the voucher line.
PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainInput statusInteger
SQL nameInpR4The database field name.
API identifierorgUnit4ProcessingThe API identifier used in GraphQL.
Number1500 

Organisational unit 5

Used to indicate the organisational unit to which the vouchers for the General ledger account are normally posted.

The organisational unit will be suggested whenever a Voucher is entered for this general ledger account. If a Voucher is entered for two general ledger accounts with different organisational units, the account entered first determines the organisational unit to be used. The suggested value can be overridden in the Voucher table.

There is one field for each organisational unit class defined, allowing the same Voucher to be posted to more than only one organisational unit.

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 defaultYesThis field is visible by default in the table display.
DomainOrganisational unit no.Integer
SQL nameR5The database field name.
API identifierorgUnit5The API identifier used in GraphQL.
Number1495 
Table 11. Table relations
To tablePurposeFrom columnsTo columnsComments
Organisational unit 5OrgUnit5
  • Organisational unit 5

Organisational unit 5 processing

The processing used for the organisational unit.

Note:
If the field is left blank, the organisational unit is not included in the transactions relating to the active account. If neither the debit nor the credit account is valid for processing of the organisational unit, Business NXT displays a message during voucher entry.
Note:
If obligatory organisational units have not been entered before you update, you will be given an error status for the transactions and a report stating the number of transactions containing errors.
A look-up in this field gives you the following list of possible values:
0 - Not allowed - blocked
1 - In use
Business NXT copies information about the organisational units from the general ledger account, if a value has been entered here.
2 - Stop
The cursor pauses in the organisational unit field when posting to the general ledger account concerned.
3 - Mandatory
The cursor pauses in the organisational unit field when posting to the general ledger account concerned. Business NXT will display a red question mark in compulsory organisational unit fields which have not yet been filled in for the voucher line.
PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainInput statusInteger
SQL nameInpR5The database field name.
API identifierorgUnit5ProcessingThe API identifier used in GraphQL.
Number1501 

Organisational unit 6

Used to indicate the organisational unit to which the vouchers for the General ledger account are normally posted.

The organisational unit will be suggested whenever a Voucher is entered for this general ledger account. If a Voucher is entered for two general ledger accounts with different organisational units, the account entered first determines the organisational unit to be used. The suggested value can be overridden in the Voucher table.

There is one field for each organisational unit class defined, allowing the same Voucher to be posted to more than only one organisational unit.

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 defaultYesThis field is visible by default in the table display.
DomainOrganisational unit no.Integer
SQL nameR6The database field name.
API identifierorgUnit6The API identifier used in GraphQL.
Number1496 
Table 12. Table relations
To tablePurposeFrom columnsTo columnsComments
Organisational unit 6OrgUnit6
  • Organisational unit 6

Organisational unit 6 processing

The processing used for the organisational unit.

Note:
If the field is left blank, the organisational unit is not included in the transactions relating to the active account. If neither the debit nor the credit account is valid for processing of the organisational unit, Business NXT displays a message during voucher entry.
Note:
If obligatory organisational units have not been entered before you update, you will be given an error status for the transactions and a report stating the number of transactions containing errors.
A look-up in this field gives you the following list of possible values:
0 - Not allowed - blocked
1 - In use
Business NXT copies information about the organisational units from the general ledger account, if a value has been entered here.
2 - Stop
The cursor pauses in the organisational unit field when posting to the general ledger account concerned.
3 - Mandatory
The cursor pauses in the organisational unit field when posting to the general ledger account concerned. Business NXT will display a red question mark in compulsory organisational unit fields which have not yet been filled in for the voucher line.
PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainInput statusInteger
SQL nameInpR6The database field name.
API identifierorgUnit6ProcessingThe API identifier used in GraphQL.
Number1502 

Organisational unit 7

Used to indicate the organisational unit to which the vouchers for the General ledger account are normally posted.

The organisational unit will be suggested whenever a Voucher is entered for this general ledger account. If a Voucher is entered for two general ledger accounts with different organisational units, the account entered first determines the organisational unit to be used. The suggested value can be overridden in the Voucher table.

There is one field for each organisational unit class defined, allowing the same Voucher to be posted to more than only one organisational unit.

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 defaultYesThis field is visible by default in the table display.
DomainLong alphanumeric organisational unit no.Text (40)
SQL nameR7The database field name.
API identifierorgUnit7The API identifier used in GraphQL.
Number9552 
Table 13. Table relations
To tablePurposeFrom columnsTo columnsComments
Organisational unit 7OrgUnit7
  • Organisational unit 7

Organisational unit 7 processing

The processing used for the organisational unit.

Note:
If the field is left blank, the organisational unit is not included in the transactions relating to the active account. If neither the debit nor the credit account is valid for processing of the organisational unit, Business NXT displays a message during voucher entry.
Note:
If obligatory organisational units have not been entered before you update, you will be given an error status for the transactions and a report stating the number of transactions containing errors.
A look-up in this field gives you the following list of possible values:
0 - Not allowed - blocked
1 - In use
Business NXT copies information about the organisational units from the general ledger account, if a value has been entered here.
2 - Stop
The cursor pauses in the organisational unit field when posting to the general ledger account concerned.
3 - Mandatory
The cursor pauses in the organisational unit field when posting to the general ledger account concerned. Business NXT will display a red question mark in compulsory organisational unit fields which have not yet been filled in for the voucher line.
PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainInput statusInteger
SQL nameInpR7The database field name.
API identifierorgUnit7ProcessingThe API identifier used in GraphQL.
Number9648 

Organisational unit 8

Used to indicate the organisational unit to which the vouchers for the General ledger account are normally posted.

The organisational unit will be suggested whenever a Voucher is entered for this general ledger account. If a Voucher is entered for two general ledger accounts with different organisational units, the account entered first determines the organisational unit to be used. The suggested value can be overridden in the Voucher table.

There is one field for each organisational unit class defined, allowing the same Voucher to be posted to more than only one organisational unit.

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 defaultYesThis field is visible by default in the table display.
DomainShort alphanumeric organisational unit no.Text (10)
SQL nameR8The database field name.
API identifierorgUnit8The API identifier used in GraphQL.
Number9553 
Table 14. Table relations
To tablePurposeFrom columnsTo columnsComments
Organisational unit 8OrgUnit8
  • Organisational unit 8

Organisational unit 8 processing

The processing used for the organisational unit.

Note:
If the field is left blank, the organisational unit is not included in the transactions relating to the active account. If neither the debit nor the credit account is valid for processing of the organisational unit, Business NXT displays a message during voucher entry.
Note:
If obligatory organisational units have not been entered before you update, you will be given an error status for the transactions and a report stating the number of transactions containing errors.
A look-up in this field gives you the following list of possible values:
0 - Not allowed - blocked
1 - In use
Business NXT copies information about the organisational units from the general ledger account, if a value has been entered here.
2 - Stop
The cursor pauses in the organisational unit field when posting to the general ledger account concerned.
3 - Mandatory
The cursor pauses in the organisational unit field when posting to the general ledger account concerned. Business NXT will display a red question mark in compulsory organisational unit fields which have not yet been filled in for the voucher line.
PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainInput statusInteger
SQL nameInpR8The database field name.
API identifierorgUnit8ProcessingThe API identifier used in GraphQL.
Number9649 

Organisational unit 9

Used to indicate the organisational unit to which the vouchers for the General ledger account are normally posted.

The organisational unit will be suggested whenever a Voucher is entered for this general ledger account. If a Voucher is entered for two general ledger accounts with different organisational units, the account entered first determines the organisational unit to be used. The suggested value can be overridden in the Voucher table.

There is one field for each organisational unit class defined, allowing the same Voucher to be posted to more than only one organisational unit.

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 defaultYesThis field is visible by default in the table display.
DomainShort alphanumeric organisational unit no.Text (10)
SQL nameR9The database field name.
API identifierorgUnit9The API identifier used in GraphQL.
Number9554 
Table 15. Table relations
To tablePurposeFrom columnsTo columnsComments
Organisational unit 9OrgUnit9
  • Organisational unit 9

Organisational unit 9 processing

The processing used for the organisational unit.

Note:
If the field is left blank, the organisational unit is not included in the transactions relating to the active account. If neither the debit nor the credit account is valid for processing of the organisational unit, Business NXT displays a message during voucher entry.
Note:
If obligatory organisational units have not been entered before you update, you will be given an error status for the transactions and a report stating the number of transactions containing errors.
A look-up in this field gives you the following list of possible values:
0 - Not allowed - blocked
1 - In use
Business NXT copies information about the organisational units from the general ledger account, if a value has been entered here.
2 - Stop
The cursor pauses in the organisational unit field when posting to the general ledger account concerned.
3 - Mandatory
The cursor pauses in the organisational unit field when posting to the general ledger account concerned. Business NXT will display a red question mark in compulsory organisational unit fields which have not yet been filled in for the voucher line.
PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainInput statusInteger
SQL nameInpR9The database field name.
API identifierorgUnit9ProcessingThe API identifier used in GraphQL.
Number9650 

Organisational unit 10

Used to indicate the organisational unit to which the vouchers for the General ledger account are normally posted.

The organisational unit will be suggested whenever a Voucher is entered for this general ledger account. If a Voucher is entered for two general ledger accounts with different organisational units, the account entered first determines the organisational unit to be used. The suggested value can be overridden in the Voucher table.

There is one field for each organisational unit class defined, allowing the same Voucher to be posted to more than only one organisational unit.

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 defaultYesThis field is visible by default in the table display.
DomainShort alphanumeric organisational unit no.Text (10)
SQL nameR10The database field name.
API identifierorgUnit10The API identifier used in GraphQL.
Number9555 
Table 16. Table relations
To tablePurposeFrom columnsTo columnsComments
Organisational unit 10OrgUnit10
  • Organisational unit 10

Organisational unit 10 processing

The processing used for the organisational unit.

Note:
If the field is left blank, the organisational unit is not included in the transactions relating to the active account. If neither the debit nor the credit account is valid for processing of the organisational unit, Business NXT displays a message during voucher entry.
Note:
If obligatory organisational units have not been entered before you update, you will be given an error status for the transactions and a report stating the number of transactions containing errors.
A look-up in this field gives you the following list of possible values:
0 - Not allowed - blocked
1 - In use
Business NXT copies information about the organisational units from the general ledger account, if a value has been entered here.
2 - Stop
The cursor pauses in the organisational unit field when posting to the general ledger account concerned.
3 - Mandatory
The cursor pauses in the organisational unit field when posting to the general ledger account concerned. Business NXT will display a red question mark in compulsory organisational unit fields which have not yet been filled in for the voucher line.
PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainInput statusInteger
SQL nameInpR10The database field name.
API identifierorgUnit10ProcessingThe API identifier used in GraphQL.
Number9651 

Organisational unit 11

Used to indicate the organisational unit to which the vouchers for the General ledger account are normally posted.

The organisational unit will be suggested whenever a Voucher is entered for this general ledger account. If a Voucher is entered for two general ledger accounts with different organisational units, the account entered first determines the organisational unit to be used. The suggested value can be overridden in the Voucher table.

There is one field for each organisational unit class defined, allowing the same Voucher to be posted to more than only one organisational unit.

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 defaultYesThis field is visible by default in the table display.
DomainShort alphanumeric organisational unit no.Text (10)
SQL nameR11The database field name.
API identifierorgUnit11The API identifier used in GraphQL.
Number9556 
Table 17. Table relations
To tablePurposeFrom columnsTo columnsComments
Organisational unit 11OrgUnit11
  • Organisational unit 11

Organisational unit 11 processing

The processing used for the organisational unit.

Note:
If the field is left blank, the organisational unit is not included in the transactions relating to the active account. If neither the debit nor the credit account is valid for processing of the organisational unit, Business NXT displays a message during voucher entry.
Note:
If obligatory organisational units have not been entered before you update, you will be given an error status for the transactions and a report stating the number of transactions containing errors.
A look-up in this field gives you the following list of possible values:
0 - Not allowed - blocked
1 - In use
Business NXT copies information about the organisational units from the general ledger account, if a value has been entered here.
2 - Stop
The cursor pauses in the organisational unit field when posting to the general ledger account concerned.
3 - Mandatory
The cursor pauses in the organisational unit field when posting to the general ledger account concerned. Business NXT will display a red question mark in compulsory organisational unit fields which have not yet been filled in for the voucher line.
PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainInput statusInteger
SQL nameInpR11The database field name.
API identifierorgUnit11ProcessingThe API identifier used in GraphQL.
Number9652 

Organisational unit 12

Used to indicate the organisational unit to which the vouchers for the General ledger account are normally posted.

The organisational unit will be suggested whenever a Voucher is entered for this general ledger account. If a Voucher is entered for two general ledger accounts with different organisational units, the account entered first determines the organisational unit to be used. The suggested value can be overridden in the Voucher table.

There is one field for each organisational unit class defined, allowing the same Voucher to be posted to more than only one organisational unit.

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 defaultYesThis field is visible by default in the table display.
DomainShort alphanumeric organisational unit no.Text (10)
SQL nameR12The database field name.
API identifierorgUnit12The API identifier used in GraphQL.
Number9557 
Table 18. Table relations
To tablePurposeFrom columnsTo columnsComments
Organisational unit 12OrgUnit12
  • Organisational unit 12

Organisational unit 12 processing

The processing used for the organisational unit.

Note:
If the field is left blank, the organisational unit is not included in the transactions relating to the active account. If neither the debit nor the credit account is valid for processing of the organisational unit, Business NXT displays a message during voucher entry.
Note:
If obligatory organisational units have not been entered before you update, you will be given an error status for the transactions and a report stating the number of transactions containing errors.
A look-up in this field gives you the following list of possible values:
0 - Not allowed - blocked
1 - In use
Business NXT copies information about the organisational units from the general ledger account, if a value has been entered here.
2 - Stop
The cursor pauses in the organisational unit field when posting to the general ledger account concerned.
3 - Mandatory
The cursor pauses in the organisational unit field when posting to the general ledger account concerned. Business NXT will display a red question mark in compulsory organisational unit fields which have not yet been filled in for the voucher line.
PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainInput statusInteger
SQL nameInpR12The database field name.
API identifierorgUnit12ProcessingThe API identifier used in GraphQL.
Number9653 

Product no.

If a product number is entered on the General ledger account, it will be suggested in the voucher line when a Debit account or Credit account is entered.

A product no is required on a voucher line if you want to create an order from 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.
DomainProduct no.Text (40)
SQL nameProdNoThe database field name.
API identifierproductNoThe API identifier used in GraphQL.
Number5736 
Table 19. Table relations
To tablePurposeFrom columnsTo columnsComments
ProductProduct
  • Product no.
Search productSearchProduct
  • Product no.

Profit and loss account

Select this field if the account is used as a profit and loss account. Leave it blank for balance sheet accounts.

Note:
It is important that the Profit and loss account field is filled in correctly before Visma Business is taken into use.

Visma Business checks this field during each voucher update for the account, and updates the balance differently depending on whether the voucher is posted to a Profit and loss account and balance sheet account. Changes to the field do not have any retroactive effect, and can result in errors in the balance tables. The balance of PL accounts is set to zero in the first Accounting period of a new financial year, unless the Voucher is posted for a organisational unit defined to produce an accumulated result. In the case of balance sheet accounts, the balance is carried forward to the new financial year.

Note:
If you have made a mistake in this field and performed updates, you can change the value in the field and select Processing/Regenerate account balances from the menu bar in the Company information table. Only the system supervisor can use this menu item. This action can be time-consuming.

PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainBooleanInteger
SQL nameResThe database field name.
API identifierprofitAndLossAccountThe API identifier used in GraphQL.
Number1484 

Report code

Used for groupings or additional information.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainString of length 1Text (1)
SQL nameRepCdThe database field name.
API identifierreportCodeThe API identifier used in GraphQL.
Number5587 

Report group

Used for groupings or additional information.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainNo.Integer
SQL nameRepGrThe database field name.
API identifierreportGroupThe API identifier used in GraphQL.
Number5455 

SAF-T account ID

PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainString of length 4Text (4)
SQL nameSfAcIdThe database field name.
API identifiersaftAccountIdThe API identifier used in GraphQL.
Number14222 

Short name

Used to sort the general ledger accounts in a particular order or to make selections on groups of general ledger accounts.

If you choose to use the Short name field, you should complete it for all general ledger accounts otherwise the sorting won't be consistent.

Example

If you have given account 3010 the name Taxable Sales, as it is to appear in reports, the account is put under T when the accounts are sorted by name. To sort the account under S you can enter the short name Sales, Taxable and leave the name unchanged. Then, to obtain an alphabetical list, sort by the Short name column instead of the Name column.

Example

The General ledger account can be grouped into various types, such as Sales, Purchases and Bank. Sorting the table by the Short name field provides a clear summary of the General ledger account of each type, or else you can choose only to display the sales account, for example.

PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainShort nameText (24)
SQL nameAcCodeThe database field name.
API identifiershortNameThe API identifier used in GraphQL.
Number1481 

Standard account status

The status after suggesting a mapping with the Set standard accounts processing.

A look-up in this field gives you the following list of possible values:
1 - Exact match
2 - Group match
3 - Confirmed
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainStandard account statusInteger
SQL nameStdAcStThe database field name.
API identifierstandardAccountStatusThe API identifier used in GraphQL.
Number18479 

Suspended

If you want to disable the option of posting vouchers directly to an account, you can select this field. The message "account is suspended for direct entry" is displayed if you enter the account number during Voucher entry.

We recommend that you suspend all account that you post via ledger. This makes sure that the ledger entries in the general ledger are posted via ledgers, thereby also reducing the risk of differences between the ledger and the general ledger. In the General ledger account table supplied with the standard table structure, this option is selected in the General ledger account for customers and suppliers (account numbers 1500 and 2410). These are only posted in the context of automated transactions.

PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainBooleanInteger
SQL nameSuspThe database field name.
API identifiersuspendedThe API identifier used in GraphQL.
Number1489 

Turnover class

The type of turnover used for the general ledger account.

Note:
Turnover classes 5, 6, 9, 10, 11 and 12 must not be used by non-EU countries as they produce entries for the EU VAT account and would thus render the VAT statement incorrect.

You use turnover class 4, taxable purchases, for accounts for taxable purchases and taxable acquisitions that can be capitalised (i.e. most capital asset accounts). This also applies for General ledger account that you use for both taxable and non-taxable cost allocation. If you do not use a VAT code, no VAT amount will be calculated, even if turnover class 4 is defined for the account.

Note:
It is very important that this field is correctly filled in before Visma Business is taken into use.

Incomplete or incorrect entries may lead to differences in the VAT statement. If the field is changed once vouchers have been updated, Visma Business applies no retroactive effect to the change. Vouchers updated for General ledger account with an incorrect turnover class must be corrected manually using correction vouchers. Unless all the accounts relating to statement purchases/sales have been defined with the correct VAT class, the summary of taxable sales and purchases for the period in the VAT statement will not be the same as the taxes automatically posted to the VAT accounts.

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 defaultYesThis field is visible by default in the table display.
DomainTurnover classInteger
SQL nameTxClThe database field name.
API identifierturnoverClassThe API identifier used in GraphQL.
Number1485 

VAT code

Specify the VAT code normally used for the General ledger account.

This VAT code is suggested whenever a Voucher is entered for this general ledger account. The VAT code determines the type of VAT and the VAT rate to apply to the voucher.

Note:
If the Ignore VAT code field is selected for the Voucher type used in posting the voucher, no suggestion for the VAT code will be made, even if one is defined for the account. In the Voucher type table supplied with the standard table structure, this only applies to the balance and foreign currency balance Voucher type (types 29 and 30). These Voucher type are used for entering opening balances.

If you imported the standard table structure during setup, the most common VAT code will have been entered in this table.

Note:
The VAT code must correspond with the account's Turnover class, otherwise there will be a difference in the VAT statement.

A General ledger account which is taxable (i.e. turnover class 1 or 4), MUST have a VAT code which calculates received or paid VAT respectively. The VAT class determines which accounts are added up in the total taxable purchases and sales for the VAT statement. These figures will not agree with the automatically posted taxes if vouchers have been posted with a VAT code that does NOT correspond to the VAT class.

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
SQL nameTxCdThe database field name.
API identifiertaxCodeThe API identifier used in GraphQL.
Number1486 
Table 20. Table relations
To tablePurposeFrom columnsTo columnsComments
VAT codeTaxCode
  • VAT code

VAT control

Select which turnover classes will be available to the General ledger account.

The VAT control in the General ledger account table is performed when you complete the Turnover class or VAT control fields. You must enter values in both fields. It does not matter which field you complete first.

The VAT control in the voucher line table is performed when you complete the Debit account, Credit account and their associated Turnover class fields. When you update vouchers, an error status will be assigned to transactions that have turnover classes that are incompatible with the value in the VAT control field in the General ledger account table.

If you have not filled in the VAT control you can use all the turnover classes.

A look-up in this field gives you the following list of possible values:
1 - No VAT
You use the value (1) for accounts that are not subject to VAT, for example salaries and wages (account number 5010 in the standard account plan). Business NXT rejects attempts to enter turnover classes 1 or 4.
2 - Sale only
Value (2) is allocated to accounts that only apply to sales. Business NXT rejects attempts to enter turnover classes 4, 7, 11, 6, 8 or 12.
3 - Purchase only
Value (3) is allocated to accounts that only apply to purchases. Business NXT rejects attempts to enter turnover classes 1, 2, 10, 5, 3 or 9.
PropertyValueDescription
Visible by defaultYesThis field is visible by default in the table display.
DomainVAT controlInteger
SQL nameTxCtrlThe database field name.
API identifiertaxControlThe API identifier used in GraphQL.
Number6898 

VAT specification

A look-up in this field gives you the following list of possible values:
1 - Adjustments
2 - Losses on claims
3 - Reversal of input value added tax
4 - Withdrawals
PropertyValueDescription
Visible by defaultNoThis field is not visible by default in the table display.
DomainVAT specificationInteger
SQL nameTxSpecThe database field name.
API identifiertaxSpecificationThe API identifier used in GraphQL.
Number19105 

Web page

Enter a reference to a document, e.g. in Word or Excel, or a home page on the Internet. Visma Business can use visualisation to display this page together with this account in Visma Business.

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)
SQL nameWebPgThe database field name.
API identifierwebPageThe API identifier used in GraphQL.
Number8729 

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 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 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 21. Table relations
To table Purpose From columns To columns Comments
Active company process CompanyProcess Process no. Process no.