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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account group | Text (60) |
| SQL name | AcGr | The database field name. |
| API identifier | accountGroup | The API identifier used in GraphQL. |
| Number | 1483 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Account group | AccountGroup |
|
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.
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account no. | Integer |
| Primary key | Yes | Account no. |
| SQL name | AcNo | The database field name. |
| API identifier | accountNo | The API identifier used in GraphQL. |
| Number | 1480 |
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.
There are no restrictions on who can select or deselect this field.
- Specify transactions from external system
- Do not show in accrual accounting dialog
- No access to delete
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Account processing | Integer |
| SQL name | AcProc | The database field name. |
| API identifier | accountProcessing | The API identifier used in GraphQL. |
| Number | 14902 |
Account subtype
The account subtype that will be used for reporting purposes.
- 1 - Asset
- 2 - Cost
- 3 - Debt
- 4 - Income
- 5 - Unknown
- 6 - Internal
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Account subtype | Integer |
| SQL name | AcSubTp | The database field name. |
| API identifier | accountSubType | The API identifier used in GraphQL. |
| Number | 18480 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Account no. | Integer |
| Memory field | Yes | The value in this field is only displayed in the program, it is not stored in the database. |
| API identifier | templateAccountNo | The API identifier used in GraphQL. |
| Number | 8748 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | AccountTemplate |
|
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Boolean | Integer |
| SQL name | Per | The database field name. |
| API identifier | accrualAccounting | The API identifier used in GraphQL. |
| Number | 6266 |
Auto.entry processing
How to process Automatic entry.
- 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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Auto.entry processing | Integer |
| SQL name | ExpAut | The database field name. |
| API identifier | automaticEntryProcessing | The API identifier used in GraphQL. |
| Number | 3679 |
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
- 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.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Balance processing | Integer |
| SQL name | BalProc | The database field name. |
| API identifier | balanceProcessing | The API identifier used in GraphQL. |
| Number | 14376 |
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.
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Currency no. | Integer |
| SQL name | Cur | The database field name. |
| API identifier | currencyNo | The API identifier used in GraphQL. |
| Number | 1490 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Currency | Currency |
|
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Currency no. | Integer |
| SQL name | Cur2 | The database field name. |
| API identifier | currencyNo2 | The API identifier used in GraphQL. |
| Number | 14314 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Currency | Currency2 |
|
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 %.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Distribution key | Integer |
| SQL name | DstGr | The database field name. |
| API identifier | distributionKeyNo | The API identifier used in GraphQL. |
| Number | 1503 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Distribution key | DistributionKey |
|
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Boolean | Integer |
| SQL name | InpQty | The database field name. |
| API identifier | enterQuantity | The API identifier used in GraphQL. |
| Number | 2223 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Boolean | Integer |
| SQL name | InpTxCd | The database field name. |
| API identifier | enterTaxCode | The API identifier used in GraphQL. |
| Number | 1487 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Exchange rate | Decimal |
| SQL name | ExRt | The database field name. |
| API identifier | exchangeRate | The API identifier used in GraphQL. |
| Number | 14313 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Exchange rate | Decimal |
| SQL name | ExRt2 | The database field name. |
| API identifier | exchangeRate2 | The API identifier used in GraphQL. |
| Number | 14315 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | General ledger account grouping 1 | Integer |
| SQL name | Gr | The database field name. |
| API identifier | group1 | The API identifier used in GraphQL. |
| Number | 4321 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | General ledger account grouping 2 | Integer |
| SQL name | Gr2 | The database field name. |
| API identifier | group2 | The API identifier used in GraphQL. |
| Number | 4322 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | General ledger account grouping 3 | Integer |
| SQL name | Gr3 | The database field name. |
| API identifier | group3 | The API identifier used in GraphQL. |
| Number | 4323 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | General ledger account grouping 4 | Integer |
| SQL name | Gr4 | The database field name. |
| API identifier | group4 | The API identifier used in GraphQL. |
| Number | 4324 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | General ledger account grouping 5 | Integer |
| SQL name | Gr5 | The database field name. |
| API identifier | group5 | The API identifier used in GraphQL. |
| Number | 4325 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | General ledger account grouping 6 | Integer |
| SQL name | Gr6 | The database field name. |
| API identifier | group6 | The API identifier used in GraphQL. |
| Number | 4326 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | General ledger account grouping 7 | Integer |
| SQL name | Gr7 | The database field name. |
| API identifier | group7 | The API identifier used in GraphQL. |
| Number | 6049 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | General ledger account grouping 8 | Integer |
| SQL name | Gr8 | The database field name. |
| API identifier | group8 | The API identifier used in GraphQL. |
| Number | 6050 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | General ledger account grouping 9 | Integer |
| SQL name | Gr9 | The database field name. |
| API identifier | group9 | The API identifier used in GraphQL. |
| Number | 6051 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | General ledger account grouping 10 | Integer |
| SQL name | Gr10 | The database field name. |
| API identifier | group10 | The API identifier used in GraphQL. |
| Number | 6052 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | General ledger account grouping 11 | Integer |
| SQL name | Gr11 | The database field name. |
| API identifier | group11 | The API identifier used in GraphQL. |
| Number | 6053 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | General ledger account grouping 12 | Integer |
| SQL name | Gr12 | The database field name. |
| API identifier | group12 | The API identifier used in GraphQL. |
| Number | 6054 |
Grouping category
Alternative to using SAF-T account ID for grouping accounts.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | String of length 40 | Text (40) |
| SQL name | GrCat | The database field name. |
| API identifier | groupingCategory | The API identifier used in GraphQL. |
| Number | 18481 |
Grouping code
Alternative to using SAF-T account ID for grouping accounts.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | String of length 40 | Text (40) |
| SQL name | GrCd | The database field name. |
| API identifier | groupingCode | The API identifier used in GraphQL. |
| Number | 18482 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Boolean | Integer |
| SQL name | Trn | The database field name. |
| API identifier | includeInTurnover | The API identifier used in GraphQL. |
| Number | 1488 |
Inf. 1
Additional account information.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Inf. @ | Text (40) |
| SQL name | Inf | The database field name. |
| API identifier | information1 | The API identifier used in GraphQL. |
| Number | 3529 |
Inf. 2
Additional account information.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Inf. @ | Text (40) |
| SQL name | Inf2 | The database field name. |
| API identifier | information2 | The API identifier used in GraphQL. |
| Number | 3530 |
Inf. 3
Additional account information.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Inf. @ | Text (40) |
| SQL name | Inf3 | The database field name. |
| API identifier | information3 | The API identifier used in GraphQL. |
| Number | 3531 |
Inf. 4
Additional account information.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Inf. @ | Text (40) |
| SQL name | Inf4 | The database field name. |
| API identifier | information4 | The API identifier used in GraphQL. |
| Number | 3532 |
Inf. 5
Additional account information.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Inf. @ | Text (40) |
| SQL name | Inf5 | The database field name. |
| API identifier | information5 | The API identifier used in GraphQL. |
| Number | 3533 |
Inf. 6
Additional account information.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Inf. @ | Text (40) |
| SQL name | Inf6 | The database field name. |
| API identifier | information6 | The API identifier used in GraphQL. |
| Number | 3534 |
Inf. 7
Additional account information.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Inf. @ | Text (40) |
| SQL name | Inf7 | The database field name. |
| API identifier | information7 | The API identifier used in GraphQL. |
| Number | 6089 |
Inf. 8
Additional account information.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Inf. @ | Text (40) |
| SQL name | Inf8 | The database field name. |
| API identifier | information8 | The API identifier used in GraphQL. |
| Number | 6090 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Memo file name | Text (260) |
| SQL name | MemoFNm | The database field name. |
| API identifier | memoFileName | The API identifier used in GraphQL. |
| Number | 10477 |
Memo no.
Link to the memo for the entry.
The actual memo is stored in the Memo table.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Memo no. | Integer |
| SQL name | MemoNo | The database field name. |
| API identifier | memoNo | The API identifier used in GraphQL. |
| Number | 19211 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Memo | Memo |
|
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Name | Text (80) |
| SQL name | Nm | The database field name. |
| API identifier | name | The API identifier used in GraphQL. |
| Number | 1482 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Name | Text (80) |
| SQL name | Nm2 | The database field name. |
| API identifier | name2 | The API identifier used in GraphQL. |
| Number | 14221 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | NwAcNo | The database field name. |
| API identifier | newAccountNo | The API identifier used in GraphQL. |
| Number | 6612 |
Old account no.
If you have changed an account number, the old account number will be stored here.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | OldAcNo | The database field name. |
| API identifier | oldAccountNo | The API identifier used in GraphQL. |
| Number | 6613 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Organisational unit no. | Integer |
| SQL name | R1 | The database field name. |
| API identifier | orgUnit1 | The API identifier used in GraphQL. |
| Number | 1491 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 1 | OrgUnit1 |
|
Organisational unit 1 processing
The processing used for the organisational unit.
- 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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Input status | Integer |
| SQL name | InpR1 | The database field name. |
| API identifier | orgUnit1Processing | The API identifier used in GraphQL. |
| Number | 1497 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Organisational unit no. | Integer |
| SQL name | R2 | The database field name. |
| API identifier | orgUnit2 | The API identifier used in GraphQL. |
| Number | 1492 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 2 | OrgUnit2 |
|
Organisational unit 2 processing
The processing used for the organisational unit.
- 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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Input status | Integer |
| SQL name | InpR2 | The database field name. |
| API identifier | orgUnit2Processing | The API identifier used in GraphQL. |
| Number | 1498 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Organisational unit no. | Integer |
| SQL name | R3 | The database field name. |
| API identifier | orgUnit3 | The API identifier used in GraphQL. |
| Number | 1493 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 3 | OrgUnit3 |
|
Organisational unit 3 processing
The processing used for the organisational unit.
- 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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Input status | Integer |
| SQL name | InpR3 | The database field name. |
| API identifier | orgUnit3Processing | The API identifier used in GraphQL. |
| Number | 1499 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Organisational unit no. | Integer |
| SQL name | R4 | The database field name. |
| API identifier | orgUnit4 | The API identifier used in GraphQL. |
| Number | 1494 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 4 | OrgUnit4 |
|
Organisational unit 4 processing
The processing used for the organisational unit.
- 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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Input status | Integer |
| SQL name | InpR4 | The database field name. |
| API identifier | orgUnit4Processing | The API identifier used in GraphQL. |
| Number | 1500 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Organisational unit no. | Integer |
| SQL name | R5 | The database field name. |
| API identifier | orgUnit5 | The API identifier used in GraphQL. |
| Number | 1495 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 5 | OrgUnit5 |
|
Organisational unit 5 processing
The processing used for the organisational unit.
- 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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Input status | Integer |
| SQL name | InpR5 | The database field name. |
| API identifier | orgUnit5Processing | The API identifier used in GraphQL. |
| Number | 1501 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Organisational unit no. | Integer |
| SQL name | R6 | The database field name. |
| API identifier | orgUnit6 | The API identifier used in GraphQL. |
| Number | 1496 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 6 | OrgUnit6 |
|
Organisational unit 6 processing
The processing used for the organisational unit.
- 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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Input status | Integer |
| SQL name | InpR6 | The database field name. |
| API identifier | orgUnit6Processing | The API identifier used in GraphQL. |
| Number | 1502 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Long alphanumeric organisational unit no. | Text (40) |
| SQL name | R7 | The database field name. |
| API identifier | orgUnit7 | The API identifier used in GraphQL. |
| Number | 9552 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 7 | OrgUnit7 |
|
Organisational unit 7 processing
The processing used for the organisational unit.
- 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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Input status | Integer |
| SQL name | InpR7 | The database field name. |
| API identifier | orgUnit7Processing | The API identifier used in GraphQL. |
| Number | 9648 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Short alphanumeric organisational unit no. | Text (10) |
| SQL name | R8 | The database field name. |
| API identifier | orgUnit8 | The API identifier used in GraphQL. |
| Number | 9553 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 8 | OrgUnit8 |
|
Organisational unit 8 processing
The processing used for the organisational unit.
- 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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Input status | Integer |
| SQL name | InpR8 | The database field name. |
| API identifier | orgUnit8Processing | The API identifier used in GraphQL. |
| Number | 9649 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Short alphanumeric organisational unit no. | Text (10) |
| SQL name | R9 | The database field name. |
| API identifier | orgUnit9 | The API identifier used in GraphQL. |
| Number | 9554 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 9 | OrgUnit9 |
|
Organisational unit 9 processing
The processing used for the organisational unit.
- 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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Input status | Integer |
| SQL name | InpR9 | The database field name. |
| API identifier | orgUnit9Processing | The API identifier used in GraphQL. |
| Number | 9650 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Short alphanumeric organisational unit no. | Text (10) |
| SQL name | R10 | The database field name. |
| API identifier | orgUnit10 | The API identifier used in GraphQL. |
| Number | 9555 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 10 | OrgUnit10 |
|
Organisational unit 10 processing
The processing used for the organisational unit.
- 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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Input status | Integer |
| SQL name | InpR10 | The database field name. |
| API identifier | orgUnit10Processing | The API identifier used in GraphQL. |
| Number | 9651 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Short alphanumeric organisational unit no. | Text (10) |
| SQL name | R11 | The database field name. |
| API identifier | orgUnit11 | The API identifier used in GraphQL. |
| Number | 9556 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 11 | OrgUnit11 |
|
Organisational unit 11 processing
The processing used for the organisational unit.
- 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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Input status | Integer |
| SQL name | InpR11 | The database field name. |
| API identifier | orgUnit11Processing | The API identifier used in GraphQL. |
| Number | 9652 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Short alphanumeric organisational unit no. | Text (10) |
| SQL name | R12 | The database field name. |
| API identifier | orgUnit12 | The API identifier used in GraphQL. |
| Number | 9557 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 12 | OrgUnit12 |
|
Organisational unit 12 processing
The processing used for the organisational unit.
- 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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Input status | Integer |
| SQL name | InpR12 | The database field name. |
| API identifier | orgUnit12Processing | The API identifier used in GraphQL. |
| Number | 9653 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Product no. | Text (40) |
| SQL name | ProdNo | The database field name. |
| API identifier | productNo | The API identifier used in GraphQL. |
| Number | 5736 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Product | Product |
| ||
| Search product | SearchProduct |
|
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.
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Boolean | Integer |
| SQL name | Res | The database field name. |
| API identifier | profitAndLossAccount | The API identifier used in GraphQL. |
| Number | 1484 |
Report code
Used for groupings or additional information.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | String of length 1 | Text (1) |
| SQL name | RepCd | The database field name. |
| API identifier | reportCode | The API identifier used in GraphQL. |
| Number | 5587 |
Report group
Used for groupings or additional information.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | No. | Integer |
| SQL name | RepGr | The database field name. |
| API identifier | reportGroup | The API identifier used in GraphQL. |
| Number | 5455 |
SAF-T account ID
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | String of length 4 | Text (4) |
| SQL name | SfAcId | The database field name. |
| API identifier | saftAccountId | The API identifier used in GraphQL. |
| Number | 14222 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Short name | Text (24) |
| SQL name | AcCode | The database field name. |
| API identifier | shortName | The API identifier used in GraphQL. |
| Number | 1481 |
Standard account status
The status after suggesting a mapping with the Set standard accounts processing.
- 1 - Exact match
- 2 - Group match
- 3 - Confirmed
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Standard account status | Integer |
| SQL name | StdAcSt | The database field name. |
| API identifier | standardAccountStatus | The API identifier used in GraphQL. |
| Number | 18479 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Boolean | Integer |
| SQL name | Susp | The database field name. |
| API identifier | suspended | The API identifier used in GraphQL. |
| Number | 1489 |
Turnover class
The type of turnover used for the general ledger account.
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.
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.
- 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
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Turnover class | Integer |
| SQL name | TxCl | The database field name. |
| API identifier | turnoverClass | The API identifier used in GraphQL. |
| Number | 1485 |
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.
If you imported the standard table structure during setup, the most common VAT code will have been entered in this table.
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | VAT code | Integer |
| SQL name | TxCd | The database field name. |
| API identifier | taxCode | The API identifier used in GraphQL. |
| Number | 1486 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| VAT code | TaxCode |
|
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.
- 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.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | VAT control | Integer |
| SQL name | TxCtrl | The database field name. |
| API identifier | taxControl | The API identifier used in GraphQL. |
| Number | 6898 |
VAT specification
- 1 - Adjustments
- 2 - Losses on claims
- 3 - Reversal of input value added tax
- 4 - Withdrawals
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | VAT specification | Integer |
| SQL name | TxSpec | The database field name. |
| API identifier | taxSpecification | The API identifier used in GraphQL. |
| Number | 19105 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Web page | Text (260) |
| SQL name | WebPg | The database field name. |
| API identifier | webPage | The API identifier used in GraphQL. |
| Number | 8729 |
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.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | User name | Text (24) |
| Write Access | None | You are not allowed to modify the value in this field. |
| SQL name | ChUsr | The database field name. |
| API identifier | changedByUser | The API identifier used in GraphQL. |
| Number | A unique column number. |
Changed date
The date when the record was changed.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Date | Integer |
| Write Access | None | You are not allowed to modify the value in this field. |
| SQL name | ChDt | The database field name. |
| API identifier | changedDate | The API identifier used in GraphQL. |
| Number | A unique column number. |
Changed time
The time when the record was changed.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Time | Integer |
| Write Access | None | You are not allowed to modify the value in this field. |
| SQL name | ChTm | The database field name. |
| API identifier | changedTime | The API identifier used in GraphQL. |
| Number | A 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.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Date/time | DateTime |
| Write Access | None | You are not allowed to modify the value in this field. |
| SQL name | ChTs | The database field name. |
| API identifier | changedTimestamp | The API identifier used in GraphQL. |
| Number | A unique column number. |
Created by user
The name of the user that created the record.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | User name | Text (24) |
| Write Access | None | You are not allowed to modify the value in this field. |
| SQL name | CreUsr | The database field name. |
| API identifier | createdByUser | The API identifier used in GraphQL. |
| Number | A unique column number. |
Created date
The date when the record was created.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Date | Integer |
| Write Access | None | You are not allowed to modify the value in this field. |
| SQL name | CreDt | The database field name. |
| API identifier | createdDate | The API identifier used in GraphQL. |
| Number | A unique column number. |
Created time
The time when the record was created.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Time | Integer |
| Write Access | None | You are not allowed to modify the value in this field. |
| SQL name | CreTm | The database field name. |
| API identifier | createdTime | The API identifier used in GraphQL. |
| Number | A unique column number. |
Created time stamp
The date and time when the record was created.
The field is updated with the UTC time.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Date/time | DateTime |
| Write Access | None | You are not allowed to modify the value in this field. |
| SQL name | CreTs | The database field name. |
| API identifier | createdTimestamp | The API identifier used in GraphQL. |
| Number | A 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.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Edit status | Integer |
| Write Access | None | You are not allowed to modify the value in this field. |
| SQL name | LckSt | The database field name. |
| API identifier | editStatus | The API identifier used in GraphQL. |
| Number | A unique column number. |
Process no
The Process no. from the Active company process table which is currently using or has control of this record.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Process no. | Integer |
| Write Access | None | You are not allowed to modify the value in this field. |
| SQL name | ChPrc | The database field name. |
| API identifier | lockedByProcessNo | The API identifier used in GraphQL. |
| Number | A unique column number. |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Active company process | CompanyProcess | Process no. | Process no. |