Automatic entry
This table defines entries to be made as a result of entries on specific accounts.
Depending on the value in the Auto. entry processing field in the General ledger account table, the Automatic entry table can be used in different situations:
- When expanding automatic entries on lines in the Voucher table, either automatically, when filling in the amount, or manually, using the Expand automatic entries processing
- Periodically, using the Automatic entries processing in the General ledger account or Automatic entry table
| Property | Value | Description |
|---|---|---|
| Database | Company | This table is in the company databases. |
| SQL name | Aut | The table name in the database. |
| API identifier | automaticEntry | The API identifier used in GraphQL. |
| Table no. | 66 | The table number in the data model. |
The following fields exist in this table:
Account no.
Enter which general ledger account you want to link an automatic entry to. This field will not be available if you have joined the Automatic entry table with the General ledger account table, because you can only see the automatic entries applicable for the account highlighted in the main subwindow.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | AcNo | The database field name. |
| API identifier | accountNo | The API identifier used in GraphQL. |
| Number | 1511 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | GeneralLedgerAccount |
|
Amount
If you want an automatic entry to relate to a fixed amount, you can enter the amount in this field. When the automatic entry is expanded the amount will automatically be copied to the voucher line.
If you use VAT codes to post taxes during voucher updates, you must enter the gross amount, i.e. the amount inclusive of any VAT.
If you want to post the same amounts to the debit account and credit account, you can enter both accounts in the same automatic entry line with the same amount. Otherwise, the automatic entry must be spread over several lines.
If you enter / in the Amount field, the amount from the row above will automatically be copied. The field pointer moves to the next field, which means that you do not have to press Return. This field is intended for decimal figures. The field will only accept figures, full stops and commas.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Amount | Decimal |
| SQL name | Am | The database field name. |
| API identifier | amountDomestic | The API identifier used in GraphQL. |
| Number | 1516 |
Auto. entry processing
Defining of how to process automatic entries.
- 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 | No | This field is not visible by default in the table display. |
| Domain | Auto. entry processing | Integer |
| SQL name | ExpAut | The database field name. |
| API identifier | automaticEntriesProcessing | The API identifier used in GraphQL. |
| Number | 15426 |
Credit account
Enter which account you want to post automatic credit entries to. You can enter automatic entries for customer, supplier and general ledger accounts.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | CrAcNo | The database field name. |
| API identifier | creditAccountNo | The API identifier used in GraphQL. |
| Number | 1514 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Associate | CreditCustomer |
| ||
| Associate | CreditSupplier |
| ||
| General ledger account | CreditGeneralLedgerAccount |
| ||
| Capital asset | CreditCapitalAsset |
|
Credit account type
The account type indicates whether the account numbers entered refer to a customer no., a supplier no. or a general ledger account.
If you adhere to the account ranges defined in the Account no. series table, it is a good idea to hide the debit account type / credit account type. In this case, all account numbers are unique, and the account type is derived from the account number.
- 1 - Customer
- The account number refer to a customer.
- 2 - Supplier
- The account number refer to a supplier.
- 3 - General ledger account
- The account number refer to a general ledger account.
- 4 - Capital asset
- The account number refer to a capital asset.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Account type | Integer |
| SQL name | CrAcCl | The database field name. |
| API identifier | creditAccountType | The API identifier used in GraphQL. |
| Number | 3687 |
Credit VAT code
If you want a specific VAT code to be applied to the current automatic entry, you can enter the code here for each credit account.
This may override any VAT code defined for the account in the General ledger account table, if you have selected 2 - Copy from voucher line in the VAT code processing field.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | VAT code | Integer |
| SQL name | CrTxCd | The database field name. |
| API identifier | creditTaxCode | The API identifier used in GraphQL. |
| Number | 3688 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| VAT code | CreditTaxCode |
|
Debit account
Enter which account you want to post automatic debit entries to. You can enter automatic entries for customer, supplier and general ledger accounts.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | DbAcNo | The database field name. |
| API identifier | debitAccountNo | The API identifier used in GraphQL. |
| Number | 1513 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Associate | DebitCustomer |
| ||
| Associate | DebitSupplier |
| ||
| General ledger account | DebitGeneralLedgerAccount |
| ||
| Capital asset | DebitCapitalAsset |
|
Debit account type
The account type indicates whether the account numbers entered refer to a customer no., a supplier no. or a general ledger account.
If you adhere to the account ranges defined in the Account no. series table, it is a good idea to hide the debit account type / credit account type. In this case, all account numbers are unique, and the account type is derived from the account number.
- 1 - Customer
- The account number refer to a customer.
- 2 - Supplier
- The account number refer to a supplier.
- 3 - General ledger account
- The account number refer to a general ledger account.
- 4 - Capital asset
- The account number refer to a capital asset.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Account type | Integer |
| SQL name | DbAcCl | The database field name. |
| API identifier | debitAccountType | The API identifier used in GraphQL. |
| Number | 3685 |
Debit VAT code
If you want a specific VAT code to be applied to the current automatic entry, you can enter the code here for each debit account.
This may override any VAT code defined for the account in the General ledger account table, if you have selected 2 - Copy from voucher line in the VAT code processing field.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | VAT code | Integer |
| SQL name | DbTxCd | The database field name. |
| API identifier | debitTaxCode | The API identifier used in GraphQL. |
| Number | 3686 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| VAT code | DebitTaxCode |
|
Except
You have the option of preventing automatic entries from being distributed among organisational units, even if organisational units or distribution key have been defined for the voucher.
- Organisational unit 1
- The dialog box contains a list of which organisational units are
selected, enclosed in brackets.
- Select one or more organisational units and click +/- to remove the brackets and the organisational units from the automatic entry line.
- Select one or more organisational units and click +/- to add the brackets and the organisational units to the automatic entry line.
- Organisational unit 2
- See Organisational unit 1.
- Organisational unit 3
- See Organisational unit 1.
- Organisational unit 4
- See Organisational unit 1.
- Organisational unit 5
- See Organisational unit 1.
- Organisational unit 6
- See Organisational unit 1.
- Organisational unit 7
- See Organisational unit 1.
- Organisational unit 8
- See Organisational unit 1.
- Organisational unit 9
- See Organisational unit 1.
- Organisational unit 10
- See Organisational unit 1.
- Organisational unit 11
- See Organisational unit 1.
- Organisational unit 12
- See Organisational unit 1.
- Distribution key
- No distribution key may be stated for the voucher line.
- Look only on account no. to trigger automatic entries
The customer wants to run automatic entries with processing on voucher line, therefore there is no Auto. entry processing entered in the General ledger account table. Automatic entries will be triggered from G/L account only.
Unselect this check box if you want automatic entries to be triggered based on combination of G/L account and org unit.
- Corporate company no.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Except | Integer |
| SQL name | Exc | The database field name. |
| API identifier | except | The API identifier used in GraphQL. |
| Number | 3684 |
Line no.
Each line in the table is given a consecutive number in the order in which they are entered.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | No. | Integer |
| Primary key | Yes | Line no. |
| SQL name | LnNo | The database field name. |
| API identifier | lineNo | The API identifier used in GraphQL. |
| Number | 1512 |
Must be blank
The automatic entry will only apply to entries where no organisational unit has been filled in.
Organisational units that are not entered in the automatic entry line will otherwise be valid, regardless of the value in the voucher line.
- Organisational unit 1
- The dialog box contains a list of which organisational units are
selected, enclosed in brackets.
- Select one or more organisational units and click +/- to remove the brackets and the organisational units from the automatic entry line.
- Select one or more organisational units and click +/- to add the brackets and the organisational units to the automatic entry line.
- Organisational unit 2
- See Organisational unit 1.
- Organisational unit 3
- See Organisational unit 1.
- Organisational unit 4
- See Organisational unit 1.
- Organisational unit 5
- See Organisational unit 1.
- Organisational unit 6
- See Organisational unit 1.
- Organisational unit 7
- See Organisational unit 1.
- Organisational unit 8
- See Organisational unit 1.
- Organisational unit 9
- See Organisational unit 1.
- Organisational unit 10
- See Organisational unit 1.
- Organisational unit 11
- See Organisational unit 1.
- Organisational unit 12
- See Organisational unit 1.
- Distribution key
- No distribution key may be stated for the voucher line.
- Look only on account no. to trigger automatic entries
The customer wants to run automatic entries with processing on voucher line, therefore there is no Auto. entry processing entered in the General ledger account table. Automatic entries will be triggered from G/L account only.
Unselect this check box if you want automatic entries to be triggered based on combination of G/L account and org unit.
- Corporate company no.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Except | Integer |
| SQL name | Blank | The database field name. |
| API identifier | mustBeBlank | The API identifier used in GraphQL. |
| Number | 5059 |
Organisational unit 1
You can also limit the automatic entry to certain combinations of organisational unit classes for the specified account number. If the organisational unit fields are empty, the automatic entries apply to all organisational units unless you have selected that some organisational units must be blank in the Must be blank field.
In the automatic entries window there is a field for each organisational unit class that you have created in the Company information table. These fields may for example be named Department or Project, and refer to the relevant organisational unit tables.
Organisational units fields can be used freely according to company needs to split accounting, sales and purchases into organisational units. The most common types are department, project and campaign. It is also possible to limit the organisational units a user should see by limiting the organisational units in the Limitation groups, User limitation groups and Limitations. The field appear with the name assigned to it in the Company information table.
| 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 | 5053 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 1 | OrgUnit1 |
|
Organisational unit 2
You can also limit the automatic entry to certain combinations of organisational unit classes for the specified account number. If the organisational unit fields are empty, the automatic entries apply to all organisational units unless you have selected that some organisational units must be blank in the Must be blank field.
In the automatic entries window there is a field for each organisational unit class that you have created in the Company information table. These fields may for example be named Department or Project, and refer to the relevant organisational unit tables.
Organisational units fields can be used freely according to company needs to split accounting, sales and purchases into organisational units. The most common types are department, project and campaign. It is also possible to limit the organisational units a user should see by limiting the organisational units in the Limitation groups, User limitation groups and Limitations. The field appear with the name assigned to it in the Company information table.
| 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 | 5054 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 2 | OrgUnit2 |
|
Organisational unit 3
You can also limit the automatic entry to certain combinations of organisational unit classes for the specified account number. If the organisational unit fields are empty, the automatic entries apply to all organisational units unless you have selected that some organisational units must be blank in the Must be blank field.
In the automatic entries window there is a field for each organisational unit class that you have created in the Company information table. These fields may for example be named Department or Project, and refer to the relevant organisational unit tables.
Organisational units fields can be used freely according to company needs to split accounting, sales and purchases into organisational units. The most common types are department, project and campaign. It is also possible to limit the organisational units a user should see by limiting the organisational units in the Limitation groups, User limitation groups and Limitations. The field appear with the name assigned to it in the Company information table.
| 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 | 5055 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 3 | OrgUnit3 |
|
Organisational unit 4
You can also limit the automatic entry to certain combinations of organisational unit classes for the specified account number. If the organisational unit fields are empty, the automatic entries apply to all organisational units unless you have selected that some organisational units must be blank in the Must be blank field.
In the automatic entries window there is a field for each organisational unit class that you have created in the Company information table. These fields may for example be named Department or Project, and refer to the relevant organisational unit tables.
Organisational units fields can be used freely according to company needs to split accounting, sales and purchases into organisational units. The most common types are department, project and campaign. It is also possible to limit the organisational units a user should see by limiting the organisational units in the Limitation groups, User limitation groups and Limitations. The field appear with the name assigned to it in the Company information table.
| 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 | 5056 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 4 | OrgUnit4 |
|
Organisational unit 5
You can also limit the automatic entry to certain combinations of organisational unit classes for the specified account number. If the organisational unit fields are empty, the automatic entries apply to all organisational units unless you have selected that some organisational units must be blank in the Must be blank field.
In the automatic entries window there is a field for each organisational unit class that you have created in the Company information table. These fields may for example be named Department or Project, and refer to the relevant organisational unit tables.
Organisational units fields can be used freely according to company needs to split accounting, sales and purchases into organisational units. The most common types are department, project and campaign. It is also possible to limit the organisational units a user should see by limiting the organisational units in the Limitation groups, User limitation groups and Limitations. The field appear with the name assigned to it in the Company information table.
| 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 | 5057 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 5 | OrgUnit5 |
|
Organisational unit 6
You can also limit the automatic entry to certain combinations of organisational unit classes for the specified account number. If the organisational unit fields are empty, the automatic entries apply to all organisational units unless you have selected that some organisational units must be blank in the Must be blank field.
In the automatic entries window there is a field for each organisational unit class that you have created in the Company information table. These fields may for example be named Department or Project, and refer to the relevant organisational unit tables.
Organisational units fields can be used freely according to company needs to split accounting, sales and purchases into organisational units. The most common types are department, project and campaign. It is also possible to limit the organisational units a user should see by limiting the organisational units in the Limitation groups, User limitation groups and Limitations. The field appear with the name assigned to it in the Company information table.
| 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 | 5058 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 6 | OrgUnit6 |
|
Organisational unit 7
You can also limit the automatic entry to certain combinations of organisational unit classes for the specified account number. If the organisational unit fields are empty, the automatic entries apply to all organisational units unless you have selected that some organisational units must be blank in the Must be blank field.
In the automatic entries window there is a field for each organisational unit class that you have created in the Company information table. These fields may for example be named Department or Project, and refer to the relevant organisational unit tables.
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 | 9558 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 7 | OrgUnit7 |
|
Organisational unit 8
You can also limit the automatic entry to certain combinations of organisational unit classes for the specified account number. If the organisational unit fields are empty, the automatic entries apply to all organisational units unless you have selected that some organisational units must be blank in the Must be blank field.
In the automatic entries window there is a field for each organisational unit class that you have created in the Company information table. These fields may for example be named Department or Project, and refer to the relevant organisational unit tables.
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 | 9559 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 8 | OrgUnit8 |
|
Organisational unit 9
You can also limit the automatic entry to certain combinations of organisational unit classes for the specified account number. If the organisational unit fields are empty, the automatic entries apply to all organisational units unless you have selected that some organisational units must be blank in the Must be blank field.
In the automatic entries window there is a field for each organisational unit class that you have created in the Company information table. These fields may for example be named Department or Project, and refer to the relevant organisational unit tables.
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 | 9560 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 9 | OrgUnit9 |
|
Organisational unit 10
You can also limit the automatic entry to certain combinations of organisational unit classes for the specified account number. If the organisational unit fields are empty, the automatic entries apply to all organisational units unless you have selected that some organisational units must be blank in the Must be blank field.
In the automatic entries window there is a field for each organisational unit class that you have created in the Company information table. These fields may for example be named Department or Project, and refer to the relevant organisational unit tables.
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 | 9561 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 10 | OrgUnit10 |
|
Organisational unit 11
You can also limit the automatic entry to certain combinations of organisational unit classes for the specified account number. If the organisational unit fields are empty, the automatic entries apply to all organisational units unless you have selected that some organisational units must be blank in the Must be blank field.
In the automatic entries window there is a field for each organisational unit class that you have created in the Company information table. These fields may for example be named Department or Project, and refer to the relevant organisational unit tables.
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 | 9562 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 11 | OrgUnit11 |
|
Organisational unit 12
You can also limit the automatic entry to certain combinations of organisational unit classes for the specified account number. If the organisational unit fields are empty, the automatic entries apply to all organisational units unless you have selected that some organisational units must be blank in the Must be blank field.
In the automatic entries window there is a field for each organisational unit class that you have created in the Company information table. These fields may for example be named Department or Project, and refer to the relevant organisational unit tables.
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 | 9563 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 12 | OrgUnit12 |
|
R1 Aut
Use these fields to perform the automatic entry from an organisational unit and to an organisational unit.
Example
If you want the automatic entry to be performed on general ledger account 7010 for vouchers with a department from 200 to 400, this is what you do:
- Enter general ledger account 7010 in the Account no. field.
- Enter the value 1 - Expand on voucher lines in the Auto. entry processing field.
- Enter the value 200 in the Organisational unit 1 field (Department).
- Enter the value 400 in the R1 Aut field (to Department).
Result: You perform the automatic entry for all vouchers with account 7010 and with a value from 200 to 400 in the Organisational unit 1 field (Department).
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 | No | This field is not visible by default in the table display. |
| Domain | Organisational unit no. | Integer |
| SQL name | SelR1 | The database field name. |
| API identifier | orgUnit1Automatic | The API identifier used in GraphQL. |
| Number | 12153 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 1 | SelectOrgUnit1 |
|
R2 Aut
Use these fields to perform the automatic entry from an organisational unit and to an organisational unit.
Example
If you want the automatic entry to be performed on general ledger account 7010 for vouchers with a department from 200 to 400, this is what you do:
- Enter general ledger account 7010 in the Account no. field.
- Enter the value 1 - Expand on voucher lines in the Auto. entry processing field.
- Enter the value 200 in the Organisational unit 1 field (Department).
- Enter the value 400 in the R1 Aut field (to Department).
Result: You perform the automatic entry for all vouchers with account 7010 and with a value from 200 to 400 in the Organisational unit 1 field (Department).
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 | No | This field is not visible by default in the table display. |
| Domain | Organisational unit no. | Integer |
| SQL name | SelR2 | The database field name. |
| API identifier | orgUnit2Automatic | The API identifier used in GraphQL. |
| Number | 12154 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 2 | SelectOrgUnit2 |
|
R3 Aut
Use these fields to perform the automatic entry from an organisational unit and to an organisational unit.
Example
If you want the automatic entry to be performed on general ledger account 7010 for vouchers with a department from 200 to 400, this is what you do:
- Enter general ledger account 7010 in the Account no. field.
- Enter the value 1 - Expand on voucher lines in the Auto. entry processing field.
- Enter the value 200 in the Organisational unit 1 field (Department).
- Enter the value 400 in the R1 Aut field (to Department).
Result: You perform the automatic entry for all vouchers with account 7010 and with a value from 200 to 400 in the Organisational unit 1 field (Department).
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 | No | This field is not visible by default in the table display. |
| Domain | Organisational unit no. | Integer |
| SQL name | SelR3 | The database field name. |
| API identifier | orgUnit3Automatic | The API identifier used in GraphQL. |
| Number | 12155 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 3 | SelectOrgUnit3 |
|
R4 Aut
Use these fields to perform the automatic entry from an organisational unit and to an organisational unit.
Example
If you want the automatic entry to be performed on general ledger account 7010 for vouchers with a department from 200 to 400, this is what you do:
- Enter general ledger account 7010 in the Account no. field.
- Enter the value 1 - Expand on voucher lines in the Auto. entry processing field.
- Enter the value 200 in the Organisational unit 1 field (Department).
- Enter the value 400 in the R1 Aut field (to Department).
Result: You perform the automatic entry for all vouchers with account 7010 and with a value from 200 to 400 in the Organisational unit 1 field (Department).
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 | No | This field is not visible by default in the table display. |
| Domain | Organisational unit no. | Integer |
| SQL name | SelR4 | The database field name. |
| API identifier | orgUnit4Automatic | The API identifier used in GraphQL. |
| Number | 12156 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 4 | SelectOrgUnit4 |
|
R5 Aut
Use these fields to perform the automatic entry from an organisational unit and to an organisational unit.
Example
If you want the automatic entry to be performed on general ledger account 7010 for vouchers with a department from 200 to 400, this is what you do:
- Enter general ledger account 7010 in the Account no. field.
- Enter the value 1 - Expand on voucher lines in the Auto. entry processing field.
- Enter the value 200 in the Organisational unit 1 field (Department).
- Enter the value 400 in the R1 Aut field (to Department).
Result: You perform the automatic entry for all vouchers with account 7010 and with a value from 200 to 400 in the Organisational unit 1 field (Department).
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 | No | This field is not visible by default in the table display. |
| Domain | Organisational unit no. | Integer |
| SQL name | SelR5 | The database field name. |
| API identifier | orgUnit5Automatic | The API identifier used in GraphQL. |
| Number | 12157 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 5 | SelectOrgUnit5 |
|
R6 Aut
Use these fields to perform the automatic entry from an organisational unit and to an organisational unit.
Example
If you want the automatic entry to be performed on general ledger account 7010 for vouchers with a department from 200 to 400, this is what you do:
- Enter general ledger account 7010 in the Account no. field.
- Enter the value 1 - Expand on voucher lines in the Auto. entry processing field.
- Enter the value 200 in the Organisational unit 1 field (Department).
- Enter the value 400 in the R1 Aut field (to Department).
Result: You perform the automatic entry for all vouchers with account 7010 and with a value from 200 to 400 in the Organisational unit 1 field (Department).
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 | No | This field is not visible by default in the table display. |
| Domain | Organisational unit no. | Integer |
| SQL name | SelR6 | The database field name. |
| API identifier | orgUnit6Automatic | The API identifier used in GraphQL. |
| Number | 12158 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 6 | SelectOrgUnit6 |
|
R7 Aut
Use these fields to perform the automatic entry from an organisational unit and to an organisational unit.
Example
If you want the automatic entry to be performed on general ledger account 7010 for vouchers with a department from 200 to 400, this is what you do:
- Enter general ledger account 7010 in the Account no. field.
- Enter the value 1 - Expand on voucher lines in the Auto. entry processing field.
- Enter the value 200 in the Organisational unit 1 field (Department).
- Enter the value 400 in the R1 Aut field (to Department).
Result: You perform the automatic entry for all vouchers with account 7010 and with a value from 200 to 400 in the Organisational unit 1 field (Department).
The field appear with the name assigned to it in the Company information table.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Long alphanumeric organisational unit no. | Text (40) |
| SQL name | SelR7 | The database field name. |
| API identifier | orgUnit7Automatic | The API identifier used in GraphQL. |
| Number | 12159 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 7 | SelectOrgUnit7 |
|
R8 Aut
Use these fields to perform the automatic entry from an organisational unit and to an organisational unit.
Example
If you want the automatic entry to be performed on general ledger account 7010 for vouchers with a department from 200 to 400, this is what you do:
- Enter general ledger account 7010 in the Account no. field.
- Enter the value 1 - Expand on voucher lines in the Auto. entry processing field.
- Enter the value 200 in the Organisational unit 1 field (Department).
- Enter the value 400 in the R1 Aut field (to Department).
Result: You perform the automatic entry for all vouchers with account 7010 and with a value from 200 to 400 in the Organisational unit 1 field (Department).
The field appear with the name assigned to it in the Company information table.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Short alphanumeric organisational unit no. | Text (10) |
| SQL name | SelR8 | The database field name. |
| API identifier | orgUnit8Automatic | The API identifier used in GraphQL. |
| Number | 12160 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 8 | SelectOrgUnit8 |
|
R9 Aut
Use these fields to perform the automatic entry from an organisational unit and to an organisational unit.
Example
If you want the automatic entry to be performed on general ledger account 7010 for vouchers with a department from 200 to 400, this is what you do:
- Enter general ledger account 7010 in the Account no. field.
- Enter the value 1 - Expand on voucher lines in the Auto. entry processing field.
- Enter the value 200 in the Organisational unit 1 field (Department).
- Enter the value 400 in the R1 Aut field (to Department).
Result: You perform the automatic entry for all vouchers with account 7010 and with a value from 200 to 400 in the Organisational unit 1 field (Department).
The field appear with the name assigned to it in the Company information table.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Short alphanumeric organisational unit no. | Text (10) |
| SQL name | SelR9 | The database field name. |
| API identifier | orgUnit9Automatic | The API identifier used in GraphQL. |
| Number | 12161 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 9 | SelectOrgUnit9 |
|
R10 Aut
Use these fields to perform the automatic entry from an organisational unit and to an organisational unit.
Example
If you want the automatic entry to be performed on general ledger account 7010 for vouchers with a department from 200 to 400, this is what you do:
- Enter general ledger account 7010 in the Account no. field.
- Enter the value 1 - Expand on voucher lines in the Auto. entry processing field.
- Enter the value 200 in the Organisational unit 1 field (Department).
- Enter the value 400 in the R1 Aut field (to Department).
Result: You perform the automatic entry for all vouchers with account 7010 and with a value from 200 to 400 in the Organisational unit 1 field (Department).
The field appear with the name assigned to it in the Company information table.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Short alphanumeric organisational unit no. | Text (10) |
| SQL name | SelR10 | The database field name. |
| API identifier | orgUnit10Automatic | The API identifier used in GraphQL. |
| Number | 12162 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 10 | SelectOrgUnit10 |
|
R11 Aut
Use these fields to perform the automatic entry from an organisational unit and to an organisational unit.
Example
If you want the automatic entry to be performed on general ledger account 7010 for vouchers with a department from 200 to 400, this is what you do:
- Enter general ledger account 7010 in the Account no. field.
- Enter the value 1 - Expand on voucher lines in the Auto. entry processing field.
- Enter the value 200 in the Organisational unit 1 field (Department).
- Enter the value 400 in the R1 Aut field (to Department).
Result: You perform the automatic entry for all vouchers with account 7010 and with a value from 200 to 400 in the Organisational unit 1 field (Department).
The field appear with the name assigned to it in the Company information table.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Short alphanumeric organisational unit no. | Text (10) |
| SQL name | SelR11 | The database field name. |
| API identifier | orgUnit11Automatic | The API identifier used in GraphQL. |
| Number | 12163 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 11 | SelectOrgUnit11 |
|
R12 Aut
Use these fields to perform the automatic entry from an organisational unit and to an organisational unit.
Example
If you want the automatic entry to be performed on general ledger account 7010 for vouchers with a department from 200 to 400, this is what you do:
- Enter general ledger account 7010 in the Account no. field.
- Enter the value 1 - Expand on voucher lines in the Auto. entry processing field.
- Enter the value 200 in the Organisational unit 1 field (Department).
- Enter the value 400 in the R1 Aut field (to Department).
Result: You perform the automatic entry for all vouchers with account 7010 and with a value from 200 to 400 in the Organisational unit 1 field (Department).
The field appear with the name assigned to it in the Company information table.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Short alphanumeric organisational unit no. | Text (10) |
| SQL name | SelR12 | The database field name. |
| API identifier | orgUnit12Automatic | The API identifier used in GraphQL. |
| Number | 12164 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 12 | SelectOrgUnit12 |
|
Share
Specify a fixed share of the voucher amount to be posted to the account (s) defined.
The amount will be calculated when the automatic entry is expanded. This field is intended for decimal figures. The field will only accept figures, full stops and commas. The decimal separator will be the one you have defined in Windows for each workstation.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Percent | Decimal |
| SQL name | Shr | The database field name. |
| API identifier | share | The API identifier used in GraphQL. |
| Number | 1515 |
Sort seq. no.
The order of the lines.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Sort seq. no. | Integer |
| Write Access | None | You are not allowed to modify the value in this field. |
| SQL name | Srt | The database field name. |
| API identifier | sortSequenceNo | The API identifier used in GraphQL. |
| Number | 2449 |
VAT code processing
How VAT codes should be processed.
- 0 - Copy from account
Used if the VAT code has not been filled in.
Debit and credit VAT code is copied from the account to the new voucher lines.
- 1 - Overwritten on automatic entry line
- The fields for debit and credit VAT code are copied from the automatic entry line to the new voucher lines that it has inserted.
- 2 - Copy from voucher line
- The debit or credit VAT code from the voucher line the automatic entries are expanded from are used.
- 3 - Deduct VAT
- The share in the automatic entry line is calculated as the amount in the main voucher line minus the value in the field for VAT amount.
- 4 - Use d/c VAT code as a criterion to expand automatic entry
- The automatic entries will be expanded based on the VAT code entry.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | VAT code processing | Integer |
| SQL name | TxCdProc | The database field name. |
| API identifier | taxCodeProcessing | The API identifier used in GraphQL. |
| Number | 6192 |
Control columns
Control columns include information about who has changed the record last and when, and which process that is currently editing the record.
Changed by provenance
The provenance for the record change.
A look-up in this field gives you the following list of possible values:
0 - None
1 - UI
10 - External API
20 - GAiA
21 - AI Connect
100 - Internal service
101 - Task automation
102 - AutoInvoice download
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Provenance | Integer |
| Write Access | None | You are not allowed to modify the value in this field. |
| SQL name | ChPvn | The database field name. |
| API identifier | changedByProvenance | The API identifier used in GraphQL. |
| Number | A unique column number. |
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 provenance
The provenance for the record creation.
A look-up in this field gives you the following list of possible values:
0 - None
1 - UI
10 - External API
20 - GAiA
21 - AI Connect
100 - Internal service
101 - Task automation
102 - AutoInvoice download
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Provenance | Integer |
| Write Access | None | You are not allowed to modify the value in this field. |
| SQL name | CrePvn | The database field name. |
| API identifier | createdByProvenance | 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. |