Associate
The Associate table contains one row for each customer, supplier, employee or other person/organisation the company is in contact with.
| Property | Value | Description |
|---|---|---|
| Database | Company | This table is in the company databases. |
| SQL name | Actor | The table name in the database. |
| API identifier | associate | The API identifier used in GraphQL. |
| Table no. | 152 | The table number in the data model. |
The following fields exist in this table:
Account set cust.
Account set used on sales orders.
Used together with VAT and accounting group to get the correct VAT and accounting information on orders. The value in the Account set cust. field is suggested when you enter orders for the customer. The VAT and accounting group field and the Account set field in the Order line table define the tax processing.
If you do not enter a value in the Account set cust. field, the default Default account set in the Company information table is used.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Account set | Integer |
| SQL name | CAcSet | The database field name. |
| API identifier | accountSetForCustomer | The API identifier used in GraphQL. |
| Number | 4064 |
Account set sup.
Account set used on purchase orders.
Used together with VAT and accounting group to get the correct VAT and accounting information on orders. The value in the Account set sup. field is suggested when you enter orders for the supplier. The VAT and accounting group field and the Account set field in the Order line table define the tax processing.
If you do not enter a value in the Account set sup. field, the default account set in the Company information table is used.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Account set | Integer |
| SQL name | SAcSet | The database field name. |
| API identifier | accountSetForSupplier | The API identifier used in GraphQL. |
| Number | 4371 |
Accounting cost
Definition for the accounting cost string used in electronic invoicing.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Accounting cost | Text (250) |
| SQL name | AcCost | The database field name. |
| API identifier | accountingCost | The API identifier used in GraphQL. |
| Number | 17743 |
Address line 1
The street address, PO Box address, c/o address and/or attention.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Address line | Text (60) |
| SQL name | Ad1 | The database field name. |
| API identifier | addressLine1 | The API identifier used in GraphQL. |
| Number | 4030 |
Address line 2
The street address, PO Box address, c/o address and/or attention.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Address line | Text (60) |
| SQL name | Ad2 | The database field name. |
| API identifier | addressLine2 | The API identifier used in GraphQL. |
| Number | 4031 |
Address line 3
The street address, PO Box address, c/o address and/or attention.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Address line | Text (60) |
| SQL name | Ad3 | The database field name. |
| API identifier | addressLine3 | The API identifier used in GraphQL. |
| Number | 4032 |
Address line 4
The street address, PO Box address, c/o address and/or attention.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Address line | Text (60) |
| SQL name | Ad4 | The database field name. |
| API identifier | addressLine4 | The API identifier used in GraphQL. |
| Number | 4033 |
Adm. time
The number of days from identifying an order requirement until the order is sent to the supplier, or the time which is required for internal approvals before goods can be delivered.
The value is used to calculate the total lead time.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Days | Integer |
| SQL name | AdmTm | The database field name. |
| API identifier | administrationTime | The API identifier used in GraphQL. |
| Number | 6323 |
Appointment flow balance
The balance of all open appointments for the associate, i.e. all appointments which are not yet transferred to an order.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Amount | Decimal |
| SQL name | AgrChBal | The database field name. |
| API identifier | appointmentFlowBalance | The API identifier used in GraphQL. |
| Number | 12793 |
Associate no.
A unique number identifying the associate.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Associate no. | Integer |
| Primary key | Yes | Associate no. |
| SQL name | ActNo | The database field name. |
| API identifier | associateNo | The API identifier used in GraphQL. |
| Number | 4028 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Participant | Participant |
| ||
| Associate reference | AssociateReference |
| ||
| Associate role | AssociateRole |
|
Associate processing
Settings defining the behaviour of the associate.
Selection
- Exclude
- When set, the corresponding row in the Associate table will no longer be displayed in the drop-down list of related lookups. The purpose of this flag is to allow the external employees to be distinguished from internal users.
Bank account
- Do not read bank account when creating payments
- The accounts for payments are not read from the external system.
Organisation no.
- Do not read organisation no. during input
- When reading an incoming e-document in the Visma XML format, a lookup is done on the Organisation no. to try to find the correct customer/supplier no. in the internal system. If you have several associates with the same Organisation no., you can block out the once you do not want to have associated with the organisation no. If all associate have option Do not read organisation no. during input selected in the Associate table, a second lookup will be done on the EAN location code.
- VAT registered
- The associate is in the VAT register. Will be updated automatically if qualified, when running the Update directly from Visma Bizweb processing.
Visma Bizweb
- Exclude from mass update
- When selected, the associate will be excluded from update when running the Update directly from Visma Bizweb processing.
EAN Location usage
- Customer
- When writing an e-document and check box Use EAN Location Code is selected in the EDI processing
field in the Company information table, the
EAN loc. code field for the customer (EANLocCd) can be found by adding the
customer no. to the customer number tag of the associate. If XML Compliant format is selected in the EDI processing
field in the Company information table, the
Ord_CustNo tag will be used, if the XML Compliant format is not selected it will be the Ord.CustNo tag.
If EAN location code cannot be obtained an error message will be added to the EDI error message table.
- Customer is blocked
- When reading an incoming e-document in the Visma XML format, a lookup is done on the EAN loc. code field to try to find the correct customer no. in the internal system. If you have several associates with the same EAN location code, you can block out the once you do not want to have associated with the EAN location code. However, you will always try to first do a lookup on the Organisation no. field to try to find the corresponding internal customer no. If you instead want to use the EAN loc. code field, you can block the reading of the Organisation no. field by selecting Do not read organisation no. during input in the associate processing dialog.
- Invoice customer
- When writing an e-document and check box Use EAN Location Code is selected in the EDI processing field in the Company information table, the EAN loc. code field for the associate being invoiced EANInvoNo can be found by adding the customer no. to the invoice customer number tag of the associate. If XML Compliant format is selected in the EDI processing field in the Company information table, the Ord_InvoCust tag will be used, if the XML Compliant format is not selected it will be the Ord.InvoCust tag.
- Invoice customer is blocked
- When reading an incoming e-document in the Visma XML format, a lookup is done on the EAN loc. code field to try to find the correct invoice customer no. in the internal system. If you have several associates with the same EAN location code, you can block out the once you do not want to have associated with the EAN location code. However, you will always try to first do a lookup on the Organisation no. field to try to find the corresponding internal invoice customer no. If you instead want to use the EAN loc. code field, you can block the reading of the Organisation no. field by selecting Do not read organisation no. during input in the associate processing dialog.
- Deliver to associate
- When writing an e-document and check box Use EAN Location Code is selected in the EDI processing field in the Company information table, the EAN loc. code field for the associate being delivered to EANDelAct can be found by adding the customer no. to the deliver customer number tag of the associate. If XML Compliant format is selected in the EDI processing field in the Company information table, the Ord_DelActNo tag will be used, if the XML Compliant format is not selected it will be the Ord.DelActNo tag.
- Delivery to associate is blocked
- When reading an incoming e-document in the Visma XML format, a lookup is done on the EAN loc. code field to try to find the correct Delivery associate no. If you have serveral associates with the same EAN location code, you can block out the once you do not want to have associated with the EAN location code. However, you will always try to first do a lookup on the Organisation no. field to try to find the corresponding internal Delivery associate no. If you instead want to use the EAN loc. code field, you can block the reading of the Organisation no. field by selecting Do not read organisation no. during input in the associate processing dialog.
- Supplier
- When writing an e-document and check box Use EAN Location Code is selected in the EDI processing field in the Company information table, the EAN loc. code field for the supplier (EANSupNo) can be found by adding the supplier no. to the supplier number tag of the associate. If XML Compliant format is selected in the EDI processing field in the Company information table, the Ord_SupNo tag will be used, if the XML Compliant format is not selected it will be the Ord_SupNo tag.
- Supplier is blocked
- When reading an incoming e-document in the Visma XML format, a lookup is done on the EAN loc. code field to try to find the correct supplier no. in the internal system. If you have several associates with the same EAN location code, you can block out the once you do not want to have associated with the EAN location code. However, you will always try to first do a lookup on the Organisation no. field to try to find the corresponding internal supplier no. If you instead want to use the EAN loc. code field, you can block the reading of the Organisation no. field by selecting Do not read organisation no. during input in the associate processing dialog.
- Send to associate
- When writing an e-document and check box Use EAN Location Code is selected in the EDI processing field in the Company information table, the EAN loc. code field for the associate being sendt to EANShpNo can be found by adding the associate no. to the sendt associate number tag of the associate. If XML Compliant format is selected in the EDI processing field in the Company information table, the Ord_ShpActNo tag will be used, if the XML Compliant format is not selected it will be the Ord.ShpActNo tag.
- Send to associate is blocked
- When reading an incoming e-document in the Visma XML format, a lookup is done on the EAN loc. code field to try to find the correct ship to associate no. If you have several associates with the same EAN location code, you can block out the once you do not want to have associated with the EAN location code. However, you will always try to first do a lookup on the Organisation no. field to try to find the corresponding internal ship to associate no. If you instead want to use the EAN loc. code field, you can block the reading of the Organisation no. field by selecting Do not read organisation no. during input in the associate processing dialog.
- Liaison associate
- This check box is currently not in use.
- Liaison associate is blocked
- This check box is currently not in use.
- Liaison associate 2
- This check box is currently not in use.
- Liaison associate 2 is blocked
- This check box is currently not in use.
AutoInvoice
- Do not use EAN for PartyIdentification
- EAN loc. code field content will not be used for AutoInvoice PartyIdentification.
- Specify operator code when sending invoice
- When set, the value in AutoInvoice operator no. is
used for routing when invoices are sent through Visma.net AutoInvoice. In most cases, it is not recommended or necessary to specify an operator code for
invoice, unless there are conflicting routes available in AutoInvoice (meaning it is
possible to deliver through more than one external access point) and an override is
required.Note:This setting is not required for B2C invoicing with operator code.
- Exclude e-invoice as route when sending invoice
- When set, electronic route will be disregarded when AutoInvoice attempt to deliver the invoice. Meaning that even if the customer is able to receive invoices electronically, the invoice will be delivered as e-mail or printed.
- Exclude EU goods stat. no. when sending invoice
- When set, value in the EU goods stat. no. field will not be included in the XML invoice.
External processing
- No access to delete
- The row can not be deleted, even if there are no transactions linked
to the row. This check box is intended for use when another program has imported the
data and you want to prevent the row being deleted by mistake.Note:There are no restrictions on who can select or deselect this check box.
- Inactive in external system
- The associate is inactive in the external system.
- Exclude from Visma Mobile
- The associate is excluded from Visma Mobile Sales Order.
- Exclude from Visma On Demand
- The associate is excluded from Visma On Demand.
- Exclude from Master Data Management
- Created automatically
- This setting is automatically selected when new associate is created from an incoming document.
Document center
- Document processor
- The value must be updated from Visma Document Center.
- Document manager
- The value must be updated from Visma Document Center.
- Accountant
- The value must be updated from Visma Document Center.
- E-mail warning
- The value must be updated from Visma Document Center.
External user
- User in Time Ease
- The associate is a Visma TimeEase user. If check box is selected, an x will be shown in the TimeEase user field in the Associate table.
- User in Zpider
- The associate is a Zpider user.
- User in External system 3
- The associate is a User in External system 3 user.
- User in External system 4
- The associate is a User in External system 4 user.
AutoInvoice payment means
- Use default for all
- The payment information is selected from the customer's location: Domestic customers get Bank account and/or Postal giro, international customers get IBAN. This is the standard behaviour, used for all customers where nothing else is selected.
- Use domestic for all
- When selected, Bank account and/or Postal giro is used as payment information on all invoices to this customer, also when the customer is international. Use this for customers abroad that cannot handle IBAN. If no bank account is found for the company, the invoice will not be transferred to AutoInvoice.
- Use IBAN for all
- When selected, IBAN is used as payment information on all invoices to this customer, also when the customer is domestic. Use this for domestic customers that require IBAN for payment. If no IBAN is found for the company, the invoice will not be transferred to AutoInvoice.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Associate processing | Integer |
| SQL name | ActPro | The database field name. |
| API identifier | associateProcessing | The API identifier used in GraphQL. |
| Number | 8474 |
Associate processing 2
Settings defining the behaviour of the associate.
Selection
- Exclude
- When set, the corresponding row in the Associate table will no longer be displayed in the drop-down list of related lookups. The purpose of this flag is to allow the external employees to be distinguished from internal users.
Bank account
- Do not read bank account when creating payments
- The accounts for payments are not read from the external system.
Organisation no.
- Do not read organisation no. during input
- When reading an incoming e-document in the Visma XML format, a lookup is done on the Organisation no. to try to find the correct customer/supplier no. in the internal system. If you have several associates with the same Organisation no., you can block out the once you do not want to have associated with the organisation no. If all associate have option Do not read organisation no. during input selected in the Associate table, a second lookup will be done on the EAN location code.
- VAT registered
- The associate is in the VAT register. Will be updated automatically if qualified, when running the Update directly from Visma Bizweb processing.
Visma Bizweb
- Exclude from mass update
- When selected, the associate will be excluded from update when running the Update directly from Visma Bizweb processing.
EAN Location usage
- Customer
- When writing an e-document and check box Use EAN Location Code is selected in the EDI processing
field in the Company information table, the
EAN loc. code field for the customer (EANLocCd) can be found by adding the
customer no. to the customer number tag of the associate. If XML Compliant format is selected in the EDI processing
field in the Company information table, the
Ord_CustNo tag will be used, if the XML Compliant format is not selected it will be the Ord.CustNo tag.
If EAN location code cannot be obtained an error message will be added to the EDI error message table.
- Customer is blocked
- When reading an incoming e-document in the Visma XML format, a lookup is done on the EAN loc. code field to try to find the correct customer no. in the internal system. If you have several associates with the same EAN location code, you can block out the once you do not want to have associated with the EAN location code. However, you will always try to first do a lookup on the Organisation no. field to try to find the corresponding internal customer no. If you instead want to use the EAN loc. code field, you can block the reading of the Organisation no. field by selecting Do not read organisation no. during input in the associate processing dialog.
- Invoice customer
- When writing an e-document and check box Use EAN Location Code is selected in the EDI processing field in the Company information table, the EAN loc. code field for the associate being invoiced EANInvoNo can be found by adding the customer no. to the invoice customer number tag of the associate. If XML Compliant format is selected in the EDI processing field in the Company information table, the Ord_InvoCust tag will be used, if the XML Compliant format is not selected it will be the Ord.InvoCust tag.
- Invoice customer is blocked
- When reading an incoming e-document in the Visma XML format, a lookup is done on the EAN loc. code field to try to find the correct invoice customer no. in the internal system. If you have several associates with the same EAN location code, you can block out the once you do not want to have associated with the EAN location code. However, you will always try to first do a lookup on the Organisation no. field to try to find the corresponding internal invoice customer no. If you instead want to use the EAN loc. code field, you can block the reading of the Organisation no. field by selecting Do not read organisation no. during input in the associate processing dialog.
- Deliver to associate
- When writing an e-document and check box Use EAN Location Code is selected in the EDI processing field in the Company information table, the EAN loc. code field for the associate being delivered to EANDelAct can be found by adding the customer no. to the deliver customer number tag of the associate. If XML Compliant format is selected in the EDI processing field in the Company information table, the Ord_DelActNo tag will be used, if the XML Compliant format is not selected it will be the Ord.DelActNo tag.
- Delivery to associate is blocked
- When reading an incoming e-document in the Visma XML format, a lookup is done on the EAN loc. code field to try to find the correct Delivery associate no. If you have serveral associates with the same EAN location code, you can block out the once you do not want to have associated with the EAN location code. However, you will always try to first do a lookup on the Organisation no. field to try to find the corresponding internal Delivery associate no. If you instead want to use the EAN loc. code field, you can block the reading of the Organisation no. field by selecting Do not read organisation no. during input in the associate processing dialog.
- Supplier
- When writing an e-document and check box Use EAN Location Code is selected in the EDI processing field in the Company information table, the EAN loc. code field for the supplier (EANSupNo) can be found by adding the supplier no. to the supplier number tag of the associate. If XML Compliant format is selected in the EDI processing field in the Company information table, the Ord_SupNo tag will be used, if the XML Compliant format is not selected it will be the Ord_SupNo tag.
- Supplier is blocked
- When reading an incoming e-document in the Visma XML format, a lookup is done on the EAN loc. code field to try to find the correct supplier no. in the internal system. If you have several associates with the same EAN location code, you can block out the once you do not want to have associated with the EAN location code. However, you will always try to first do a lookup on the Organisation no. field to try to find the corresponding internal supplier no. If you instead want to use the EAN loc. code field, you can block the reading of the Organisation no. field by selecting Do not read organisation no. during input in the associate processing dialog.
- Send to associate
- When writing an e-document and check box Use EAN Location Code is selected in the EDI processing field in the Company information table, the EAN loc. code field for the associate being sendt to EANShpNo can be found by adding the associate no. to the sendt associate number tag of the associate. If XML Compliant format is selected in the EDI processing field in the Company information table, the Ord_ShpActNo tag will be used, if the XML Compliant format is not selected it will be the Ord.ShpActNo tag.
- Send to associate is blocked
- When reading an incoming e-document in the Visma XML format, a lookup is done on the EAN loc. code field to try to find the correct ship to associate no. If you have several associates with the same EAN location code, you can block out the once you do not want to have associated with the EAN location code. However, you will always try to first do a lookup on the Organisation no. field to try to find the corresponding internal ship to associate no. If you instead want to use the EAN loc. code field, you can block the reading of the Organisation no. field by selecting Do not read organisation no. during input in the associate processing dialog.
- Liaison associate
- This check box is currently not in use.
- Liaison associate is blocked
- This check box is currently not in use.
- Liaison associate 2
- This check box is currently not in use.
- Liaison associate 2 is blocked
- This check box is currently not in use.
AutoInvoice
- Do not use EAN for PartyIdentification
- EAN loc. code field content will not be used for AutoInvoice PartyIdentification.
- Specify operator code when sending invoice
- When set, the value in AutoInvoice operator no. is
used for routing when invoices are sent through Visma.net AutoInvoice. In most cases, it is not recommended or necessary to specify an operator code for
invoice, unless there are conflicting routes available in AutoInvoice (meaning it is
possible to deliver through more than one external access point) and an override is
required.Note:This setting is not required for B2C invoicing with operator code.
- Exclude e-invoice as route when sending invoice
- When set, electronic route will be disregarded when AutoInvoice attempt to deliver the invoice. Meaning that even if the customer is able to receive invoices electronically, the invoice will be delivered as e-mail or printed.
- Exclude EU goods stat. no. when sending invoice
- When set, value in the EU goods stat. no. field will not be included in the XML invoice.
External processing
- No access to delete
- The row can not be deleted, even if there are no transactions linked
to the row. This check box is intended for use when another program has imported the
data and you want to prevent the row being deleted by mistake.Note:There are no restrictions on who can select or deselect this check box.
- Inactive in external system
- The associate is inactive in the external system.
- Exclude from Visma Mobile
- The associate is excluded from Visma Mobile Sales Order.
- Exclude from Visma On Demand
- The associate is excluded from Visma On Demand.
- Exclude from Master Data Management
- Created automatically
- This setting is automatically selected when new associate is created from an incoming document.
Document center
- Document processor
- The value must be updated from Visma Document Center.
- Document manager
- The value must be updated from Visma Document Center.
- Accountant
- The value must be updated from Visma Document Center.
- E-mail warning
- The value must be updated from Visma Document Center.
External user
- User in Time Ease
- The associate is a Visma TimeEase user. If check box is selected, an x will be shown in the TimeEase user field in the Associate table.
- User in Zpider
- The associate is a Zpider user.
- User in External system 3
- The associate is a User in External system 3 user.
- User in External system 4
- The associate is a User in External system 4 user.
AutoInvoice payment means
- Use default for all
- The payment information is selected from the customer's location: Domestic customers get Bank account and/or Postal giro, international customers get IBAN. This is the standard behaviour, used for all customers where nothing else is selected.
- Use domestic for all
- When selected, Bank account and/or Postal giro is used as payment information on all invoices to this customer, also when the customer is international. Use this for customers abroad that cannot handle IBAN. If no bank account is found for the company, the invoice will not be transferred to AutoInvoice.
- Use IBAN for all
- When selected, IBAN is used as payment information on all invoices to this customer, also when the customer is domestic. Use this for domestic customers that require IBAN for payment. If no IBAN is found for the company, the invoice will not be transferred to AutoInvoice.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Associate processing 2 | Integer |
| SQL name | ActPro2 | The database field name. |
| API identifier | associateProcessing2 | The API identifier used in GraphQL. |
| Number | 18499 |
Associate template
The associate you will use as a template for this associate.
When you enter an associate in this field, the values from that associate is copied to the current associate. Fields that are already filled in are not overridden.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Associate 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 | associateTemplate | The API identifier used in GraphQL. |
| Number | 8728 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Associate | AssociateTemplate |
|
Attestation amount limit
The field is intended to be used by third party products.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Amount | Decimal |
| SQL name | AttAmLmt | The database field name. |
| API identifier | attestationAmountLimit | The API identifier used in GraphQL. |
| Number | 12674 |
Auth. responsible
The authorisation official for vouchers.
The authorisation official is suggested when you enter vouchers for the supplier.
The Empl. no. is a unique number identifying one specific Employee.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Empl. no. | Integer |
| SQL name | Att | The database field name. |
| API identifier | approvalOfficial | The API identifier used in GraphQL. |
| Number | 4496 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Associate | ApprovalOfficial |
|
AutoInvoice e-mail address
E-mail address used for routing messages from AutoInvoice to the customer.
If set, AutoInvoice e-mail address will be used when sending to AutoInvoice. If empty, E-mail address will be selected.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | E-mail address | Text (60) |
| SQL name | AuMailAd | The database field name. |
| API identifier | autoInvoiceEmailAddress | The API identifier used in GraphQL. |
| Number | 16622 |
AutoInvoice endpoint ID
Must contain the receiver ID used for electronic delivery through Visma.net AutoInvoice, numeric characters only. This excludes the scheme (the value before and including colon). The exception is when the receiver ID is identical to Organisation no., in which case no value should be put in this field.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | AutoInvoice endpoint ID | Text (40) |
| SQL name | AiEpId | The database field name. |
| API identifier | autoInvoiceEndpointId | The API identifier used in GraphQL. |
| Number | 18048 |
AutoInvoice endpoint scheme
Definition of what type of value has been set in AutoInvoice Endpoint ID, and if not set, AutoInvoice Endpoint ID will not be used. Value must be the scheme code from the Electronic Address Scheme (EAS).
| Scheme code | Registry |
|---|---|
| 0002 | System Information et Repertoire des Entreprise et des Etablissements: SIRENE |
| 0007 | SE organisationsnummer |
| 0009 | SIRET-CODE |
| 0216 | FI OVT - LY-tunnus |
| 0060 | D-U-N-S Number |
| 0088 | EAN Location Code |
| 0096 | Danish Chamber of Commerce scheme |
| 0097 | FTI - Ediforum Italia |
| 0106 | Association of Chambers of Commerce and Industry in the Netherlands Scheme |
| 0130 | Directorates of the European Commission |
| 0135 | SIA Object Identifiers |
| 0142 | SECETI Object Identifiers |
| 0151 | Australian Business Number (ABN) Scheme |
| 0183 | Swiss Unique Business Identification Number (UIDB) |
| 0184 | DIGSTORG |
| 0190 | Dutch Originator's Identification Number |
| 0191 | Centre of Registers and Information Systems of the Ministry of Justice |
| 0192 | Enhetsregisteret ved Brønnøysundregistrene |
| 0193 | UBL.BE party identifier |
| 0195 | Singapore UEN identifier |
| 0196 | Kennitala - Iceland legal id for individuals and legal entities |
| 0198 | ERSTORG |
| 0199 | Global legal entity identifier (GLEIF) |
| 0200 | Legal entity code (Lithuania) |
| 0201 | Codice Univoco Unità Organizzativa iPA |
| 0202 | Indirizzo di Posta Elettronica Certificata |
| 0204 | Leitweg-ID |
| 9901 | Danish Ministry of the Interior and Health |
| 9906 | Ufficio responsabile gestione partite IVA |
| 9907 | TAX Authority |
| 9910 | Hungary VAT number |
| 9913 | Business Registers Network |
| 9914 | Österreichische Umsatzsteuer-Identifikationsnummer |
| 9915 | Österreichisches Verwaltungs bzw. Organisationskennzeichen |
| 9918 | SOCIETY FOR WORLDWIDE INTERBANK FINANCIAL, TELECOMMUNICATION S.W.I.F.T |
| 9919 | Kennziffer des Unternehmensregisters |
| 9920 | Agencia Española de Administración Tributaria |
| 9922 | Andorra VAT number |
| 9923 | Albania VAT number |
| 9924 | Bosnia and Herzegovina VAT number |
| 9925 | Belgium VAT number |
| 9926 | Bulgaria VAT number |
| 9927 | Switzerland VAT number |
| 9928 | Cyprus VAT number |
| 9929 | Czech Republic VAT number |
| 9930 | Germany VAT number |
| 9931 | Estonia VAT number |
| 9932 | United Kingdom VAT number |
| 9933 | Greece VAT number |
| 9934 | Croatia VAT number |
| 9935 | Ireland VAT number |
| 9936 | Liechtenstein VAT number |
| 9937 | Lithuania VAT number |
| 9938 | Luxemburg VAT number |
| 9939 | Latvia VAT number |
| 9940 | Monaco VAT number |
| 9941 | Montenegro VAT number |
| 9942 | Macedonia, the former Yugoslav Republic of VAT number |
| 9943 | Malta VAT number |
| 9944 | Netherlands VAT number |
| 9945 | Poland VAT number |
| 9946 | Portugal VAT number |
| 9947 | Romania VAT number |
| 9948 | Serbia VAT number |
| 9949 | Slovenia VAT number |
| 9950 | Slovakia VAT number |
| 9951 | San Marino VAT number |
| 9952 | Turkey VAT number |
| 9953 | Holy See (Vatican City State) VAT number |
| 9955 | Swedish VAT number |
| 9956 | Belgian Crossroad Bank of Enterprises |
| 9957 | French VAT number |
| 9958 | German Leitweg ID |
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | AutoInvoice endpoint scheme | Text (10) |
| SQL name | AiEpSc | The database field name. |
| API identifier | autoInvoiceEndpointScheme | The API identifier used in GraphQL. |
| Number | 18049 |
AutoInvoice operator no.
Defines electronic route via AutoInvoice
The field has a lookup to the AutoInvoice operator table.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | No. | Integer |
| SQL name | AuInOpNo | The database field name. |
| API identifier | autoInvoiceOperatorNo | The API identifier used in GraphQL. |
| Number | 16499 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| AutoInvoice operator | AutoInvoiceOperator |
|
Bank account
The bank account number used when you print completed bank giro forms in connection with reminders, interest notes and payments, or if you use Electronic Funds Transfer.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Bank account | Text (35) |
| SQL name | BGiro | The database field name. |
| API identifier | bankAccount | The API identifier used in GraphQL. |
| Number | 4084 |
Bank branch
The bank branch number used in connection with electronic funds transfer. The field must contain details about clearing code, bank code, BLZ, etc., obtained from the supplier.
The field is used for payments using the Telepay format. In some cases, the SWIFT code is also sent, as determined by the receiving bank/country. Your bank or supplier will tell you if you need to include this field. Used by Visma.net AutoPay as Fedwire information on payments to USA.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Bank account | Text (35) |
| SQL name | Branch | The database field name. |
| API identifier | bankBranch | The API identifier used in GraphQL. |
| Number | 5072 |
Bank no.
The associate's bank. This value is not in use for payments.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Bank no. | Integer |
| SQL name | BankCon | The database field name. |
| API identifier | bankNo | The API identifier used in GraphQL. |
| Number | 10507 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Bank | Bank |
|
Bank partner no.
The bank partner used to define what is remitted to a bank partner.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | No. | Integer |
| SQL name | BPartNo | The database field name. |
| API identifier | bankPartnerNo | The API identifier used in GraphQL. |
| Number | 12934 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Bank partner | BankPartner |
|
Buyer
The buyer for the supplier.
The Empl. no. is a unique number identifying one specific Employee.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Empl. no. | Integer |
| SQL name | Buyer | The database field name. |
| API identifier | buyer | The API identifier used in GraphQL. |
| Number | 4051 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Associate | Buyer |
|
Change time in ms
The time when changes were made in milliseconds.
Used in the integration between Zpider and Business NXT. With this field, the changes you make in Business NXT are updated in Zpider immediately.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | No. | Integer |
| Write Access | None | You are not allowed to modify the value in this field. |
| SQL name | ChTmms | The database field name. |
| API identifier | changeTimeInMs | The API identifier used in GraphQL. |
| Number | 14514 |
Changed externally
The field is intended to be used by third party products.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Date/time | Decimal |
| SQL name | ChExt | The database field name. |
| API identifier | changedExternally | The API identifier used in GraphQL. |
| Number | 6416 |
Client responsible account 1
The account for the customer used to accumulate client funds.
You can also define that for ranges of customer numbers in the Account no. series table. If the field is blank, account references in the Company information table are used.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | ClReAcNo | The database field name. |
| API identifier | clientResponsibleAccountNo1 | The API identifier used in GraphQL. |
| Number | 8438 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | ClientResponsibleAccount1 |
|
Client responsible account 2
The account for the customer used to accumulate client funds.
You can also define that for ranges of customer numbers in the Account no. series table. If the field is blank, account references in the Company information table are used.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | ClBaAcNo | The database field name. |
| API identifier | clientResponsibleAccountNo2 | The API identifier used in GraphQL. |
| Number | 8439 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | ClientResponsibleAccount2 |
|
Client responsible account 3
The account for the customer used to accumulate client funds.
You can also define that for ranges of customer numbers in the Account no. series table. If the field is blank, account references in the Company information table are used.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | Cl3AcNo | The database field name. |
| API identifier | clientResponsibleAccountNo3 | The API identifier used in GraphQL. |
| Number | 12260 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | ClientResponsibleAccount3 |
|
Contact for
The contact for an entry in the Associate table.
There is no limit to the number of contacts an associate can have. You can join the Associate table to itself using this field to view all contacts for an associate.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Associate no. | Integer |
| SQL name | LiaAct | The database field name. |
| API identifier | contactFor | The API identifier used in GraphQL. |
| Number | 4049 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Associate | ContactFor |
|
Contracting, buyer's reference
Defines which XML field is used as buyer's reference for the Contracting Works integration when invoice/credit note is processed from Accounting document table.
- 1 - Buyer reference
- 2 - Order reference
- 3 - Sales order ID
- 4 - Invoice document reference
- 5 - Despatch document reference
- 6 - Receipt document reference
- 7 - Originator document reference
- 8 - Contract document reference
- 9 - Additional document reference
- 10 - Project reference
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Contracting, buyer's reference | Integer |
| SQL name | CtrBuyRef | The database field name. |
| API identifier | contractingBuyersReference | The API identifier used in GraphQL. |
| Number | 19687 |
Country no.
The country of the associate. It is only relevant if the associate's country is different from the default country.
You define default country in the Company information table. The Country no. field is used to enter the country number that applies to the associate.
When the country number is entered, values get updated in the Language no. and Currency no. fields if you have entered this information for the relevant country in the Country table. The values can be changed if required. The country number determines, amongst other things, the parameters to be used for invoicing, reminders and calculation of interest. The field appears in two sets in the order head, and is suggested based of the customer/supplier and the recipient. If required, the country can also be edited out in forms as a part of the address, by retrieving the name of the country (or nationality code) from the Country table.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Country no. | Integer |
| SQL name | Ctry | The database field name. |
| API identifier | countryNo | The API identifier used in GraphQL. |
| Number | 4036 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Country | Country |
|
Credit card reservation addition %
A percentage, setting the upper limit for credit card reservations.
The field is intended to be used by third party products.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Percent | Decimal |
| SQL name | CardAddP | The database field name. |
| API identifier | creditCardReservationAddition | The API identifier used in GraphQL. |
| Number | 15915 |
Credit evaluation
Information about the credit worthiness of the customer.
The value is copied to the Customer document table when you create open entry lists.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Name | Text (80) |
| SQL name | CrEval | The database field name. |
| API identifier | creditEvaluation | The API identifier used in GraphQL. |
| Number | 4061 |
Credit limit
The amount that the customer (invoice recipient) is allowed to owe the company.
- The credit limit is exceeded by the total orders plus d/c ledger balance for the customer.
- The customer has overdue invoices with a total outstanding amount that is bigger than the setting in the credit limit field.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Amount | Decimal |
| SQL name | CrLmt | The database field name. |
| API identifier | creditLimit | The API identifier used in GraphQL. |
| Number | 4059 |
Credit note credit days
Used in payment mediation assumes that there is a check for allowed negative payments in the Accounting processing field in the Company information table.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | No. | Integer |
| SQL name | CNtDy | The database field name. |
| API identifier | creditNoteDueDays | The API identifier used in GraphQL. |
| Number | 11444 |
Credit suspension
If you have to suspend a customer's credit, e.g. if they are in breach of their payment obligations, you check the Credit suspension box.
The customer has its credit suspended when you approve reminders for the country in question.
Entering orders
If you have suspended the customer's credit Business NXT will not let you enter orders for the customer, and you have to cancel the credit suspension before you can enter new orders. You can, however, always enter credit notes (as long as you have checked Credit note in the order head before entering the customer number). Control takes place on the basis of the invoice recipient, whether the invoice issuer's customer number is filled in directly or indirectly via the customer number. If you cancel the credit suspension for a customer and the Set credit suspension on open customer orders? check box is selected under the Accounting processing dialog in the Company information table, Business NXT removes the credit suspension for all orders entered for the customer.
Voucher registration
When you run vouchers for a customer whose credit is suspended, you receive a message stating that the customer's credit is suspended, but Business NXT does not block this as the transaction has of course already taken place.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Boolean | Integer |
| SQL name | CrSusp | The database field name. |
| API identifier | creditDenied | The API identifier used in GraphQL. |
| Number | 4060 |
CRM ID
Used by the integration with Sales Office and Super Office when synchronising data with Business NXT.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | No. | Integer |
| SQL name | SOLink | The database field name. |
| API identifier | crmId | The API identifier used in GraphQL. |
| Number | 8422 |
Cross-account no. cust.
The account that will be suggested as the cross-account for the customer in the voucher line.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | AgAcNo | The database field name. |
| API identifier | crossAccountNoForCustomer | The API identifier used in GraphQL. |
| Number | 4498 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | CrossGeneralLedgerAccountForCustomer |
|
Cross-account no. sup.
The account that will be suggested as the cross-account for the supplier in the voucher line.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | SAgAcNo | The database field name. |
| API identifier | crossAccountNoForSupplier | The API identifier used in GraphQL. |
| Number | 4789 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | CrossGeneralLedgerAccountForSupplier |
|
Currency no.
The currency no for the customer or supplier.
| 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 | 4076 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Currency | Currency |
|
Currency no. 2
| 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 | 14300 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Currency | Currency2 |
|
Cust. no.
A unique number identifying the customer.
You should place the customer number within the range for account type 1 (customers). You define this range in the Account no. series table. This enables you to avoid entering the account type when entering vouchers.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Cust. no. | Integer |
| SQL name | CustNo | The database field name. |
| API identifier | customerNo | The API identifier used in GraphQL. |
| Number | 4045 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Customer current balance | CustomerCurrentBalance |
|
Customer options
Settings defining the behaviour of the customer.
Order
- Gross orders
- The same check box will be selected in the Order options dialog box, based on the buyer (customer number).
- Reserve on save
- The same check box will be selected in the Order options dialog box, based on the buyer (customer number).
- Reserve within lead time
- The same check box will be selected in the Order options dialog box, based on the buyer (customer number).
- Batch invoice
- When this customer is set as the invoice recipient on an order the order will be suggested to be included in a batch invoice. See Order options domain.
- Justify exchange rate
- The same check box will be selected in the Order options dialog box, based on the buyer (customer number).
- Exempt from invoice fee
- The same check box will be selected in the Order options dialog box, based on the invoice recipient (the invoice's customer number).
- Accept changes manually
- The same check box will be selected in the Order options dialog box, based on the buyer (customer number).
- Send confirmations automatically
- The customer is sent confirmations for orders received by EDI.
- Include all lines on delivery notes
- All order lines are included on delivery notes, not only those with the order line status that they are ready for printing on delivery notes.
- Pick complete orders
- The same check box will be selected in the Order options dialog box, based on the buyer (customer number).
- Invoice no. from 'Label'
- The same check box will be selected in the Order options dialog box, based on the invoice recipient (the invoice's customer number).
- Withdrawal from client bank account
- The same check box will be selected in the Order options dialog box, based on the buyer (customer number).
- Post client funds
- The same check box will be selected in the Order options dialog box, based on the buyer (customer number).
- Use client responsibility 2
- The same check box will be selected in the Order options dialog box, based on the buyer (customer number).
- Use client responsibility 3
- The same check box will be selected in the Order options dialog box, based on the buyer (customer number).
- Prepayment
- You block the order from being processed at a higher status level than the order confirmation. In order for the order to be processed, you must enter a payment against this order in the voucher entry.
- Do not move confirmed delivery date to earlier
- The confirmed delivery date will not be changed for allocated orders
which are to be delivered after the confirmed date. Orders with an earlier date get an
updated confirmed delivery date with a confirmed date from the purchase production
order when the Confirmed and Sent processings are used.
For loose allocations, future orders will not be reserved if this field has not been
selected:
- Reserve by confirmed / sent under Reservation processing in the Company information table
- Reserve against all orders in the dialog box for the Confirmed and Sent processings. A check is suggested when Reserve by confirmed / sent in Reservation processing in the Company information table is selected.
- as standard for all orders in the Calculate delivery date field in the Company information table
- at each individual order in the Order options field in the Order table
- Use original exchange rate on credit notes
- Use buyer's item ID to find the product
- When selected, processing incoming orders will try to identify the product based on the customer's product ID in the XML, first searching Product customer field Customer's product no. followed by Product no. in Product. If not found, the default product search is run.
Accounting
- Suggest VAT code
- The VAT code and the Turnover class -derived from the Trade area- for the customer is suggested when you register vouchers.
- Reminder suggested
- No reminders
- The customer is exempted from reminders. This can also be done automatically after approval of the last reminder for the country in question, using the After last reminder field in the Country table.
- No debt collection
- No functionality has been implemented in this field. You can process them further in an external application such as BIG if required.
- Private person
- The customer is treated as a private customer. This is relevant for
the interest rate that is used and whether compound interest is calculated. See the
description of the Country
table.
Invoicing: When set, the customer will be identified as consumer when invoicing to Visma.net AutoInvoice. This means that if the route is available, the invoice may be sent electronically to the customer's bank for processing. If not available, the invoice will either be sent by e-mail or be printed and sent by mail.
- No interest
- The customer is exempted from interest computation. This can also be done automatically after approval of the last reminder for the country in question, using the After last reminder field in the Country table.
- Foreign payment
- You are making a payment transfer to a customer abroad.
- No payment
- The supplier is not to receive payment.
- Use Postgiro for payments - Swedish
- This field is used by some EFT systems for Swedish payments. Postgiro is also used with other formats, so you must leave this field unchecked if you are using bank formats other than Swedish ones.
- Suspended on voucher
- You will not be able to post the voucher lines directly on the customer. You will see the message "Customer xxxxxxx is suspended from direct posting" in the status bar.
Debt collection
- To debt collection
- This check box is selected when you have run the final reminder and checked the Set debt collection flag after last letter field under Accounting processing in the Company information table, and the customer is sent to debt collection.
- Transferred to debt collection
- This check box is selected when the customer is sent to debt collection. All vouchers that are registered after the customer has been sent to debt collection are registered as being subject to debt collection and can be sent in a change list to the debt collection company. This applies in particular to payments that have been sent to debt collection.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Customer options | Integer |
| SQL name | CustPref | The database field name. |
| API identifier | customerPreferences1 | The API identifier used in GraphQL. |
| Number | 5733 |
Customer options 2
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Customer options 2 | Integer |
| SQL name | CustPre2 | The database field name. |
| API identifier | customerPreferences2 | The API identifier used in GraphQL. |
| Number | 14828 |
Customer price gr. 1
Set equal prices and discounts/additions to a Customer price group.
Customers can be assigned to one or more customer price groups in the Associate table. Valid customer price groups are defined in the Text table.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Customer price group 1 | Integer |
| SQL name | CustPrGr | The database field name. |
| API identifier | customerPriceGroup1 | The API identifier used in GraphQL. |
| Number | 4077 |
Customer price gr. 2
Set equal prices and discounts/additions to a Customer price group.
Customers can be assigned to one or more customer price groups in the Associate table. Valid customer price groups are defined in the Text table.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Customer price group 2 | Integer |
| SQL name | CustPrG2 | The database field name. |
| API identifier | customerPriceGroup2 | The API identifier used in GraphQL. |
| Number | 3078 |
Customer price gr. 3
Set equal prices and discounts/additions to a Customer price group.
Customers can be assigned to one or more customer price groups in the Associate table. Valid customer price groups are defined in the Text table.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Customer price group 3 | Integer |
| SQL name | CustPrG3 | The database field name. |
| API identifier | customerPriceGroup3 | The API identifier used in GraphQL. |
| Number | 8669 |
Date of birth
The date of birth for the customer.
Used as an optional invoice receiver lookup criteria by the AutoInvoice integration when sending consumer invoices.
The date is validated using the regional settings in Windows.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Date | Integer |
| SQL name | BirthDt | The database field name. |
| API identifier | birthDate | The API identifier used in GraphQL. |
| Number | 19542 |
Delivery method cust.
The delivery method for the customer.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Delivery method | Integer |
| SQL name | CDelMt | The database field name. |
| API identifier | deliveryMethodForCustomer | The API identifier used in GraphQL. |
| Number | 4074 |
Delivery method sup.
The delivery method used by the supplier.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Delivery method | Integer |
| SQL name | SDelMt | The database field name. |
| API identifier | deliveryMethodForSupplier | The API identifier used in GraphQL. |
| Number | 4373 |
Delivery note interval
The minimum number of days between each time the customer is included when delivery notes are printed.
If you do not define an interval, the customer will be included in each new printout.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Days | Integer |
| SQL name | DelIntv | The database field name. |
| API identifier | deliveryNoteInterval | The API identifier used in GraphQL. |
| Number | 6386 |
Delivery priority
The delivery priority of the customer.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Delivery priority | Integer |
| SQL name | DelPri | The database field name. |
| API identifier | deliveryPriority | The API identifier used in GraphQL. |
| Number | 4073 |
Delivery terms cust.
The delivery term for the customer.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Delivery terms | Integer |
| SQL name | CDelTrm | The database field name. |
| API identifier | deliveryTermsForCustomer | The API identifier used in GraphQL. |
| Number | 4075 |
Delivery terms sup.
The delivery term for the supplier.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Delivery terms | Integer |
| SQL name | SDelTrm | The database field name. |
| API identifier | deliveryTermsForSupplier | The API identifier used in GraphQL. |
| Number | 4374 |
Direct deb. from date
Set to the current date when the Direct deb. status field is filled out.
Information field internally in Business NXT.
The date is validated using the regional settings in Windows.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Date | Integer |
| SQL name | DebFrDt | The database field name. |
| API identifier | directDebitingFromDate | The API identifier used in GraphQL. |
| Number | 4088 |
Direct deb. status
Determines if Direct Debit is used for the customer.
Assigned value 2 or 3 for Direct Debit. Can be done manually, or when importing customer agreements from Visma.net AutoPay.
- 1 - Process inquiry
- For customers wishing to enter into an agreement on direct debiting.
- 2 - Agreement w/o notification
- In the direct debiting dialog box, which you call up via the processing for direct debiting, there is an option to create new direct debitors. This will send an inquiry to the bank for approval of the associates with direct debiting status 1 and simultaneously change the status to 2.
- 3 - Agreement with notification
- The debitor is accepted by the bank.
- 4 - Rejected
- The debitor is rejected by the bank.
- 5 - e-Invoice
- 6 - B2B direct e-mail
- 7 - e-Invoice and AvtaleGiro
- 8 - e-Invoice and Vipps
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Direct deb. status | Integer |
| SQL name | DirDeb | The database field name. |
| API identifier | directDebitingStatus | The API identifier used in GraphQL. |
| Number | 5508 |
Direct deb. to date
Set to the current date when importing terminated Direct Debit customer agreements from Visma.net AutoPay.
Information field internally in Business NXT.
The date is validated using the regional settings in Windows.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Date | Integer |
| SQL name | DebToDt | The database field name. |
| API identifier | directDebitingToDate | The API identifier used in GraphQL. |
| Number | 4089 |
Direct debit message
Message to customer.
Extra message regarding Direct Debit claim, used for messages sent from the bank to the customer. Comes in addition to the standard message given.
| 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 | DebMess | The database field name. |
| API identifier | directDebitMessage | The API identifier used in GraphQL. |
| Number | 17759 |
District
Can be used for groupings.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | District | Integer |
| SQL name | Distr | The database field name. |
| API identifier | district | The API identifier used in GraphQL. |
| Number | 4108 |
Document delivery method 1
How documents are to be sent.
The method is suggested in the order head for the associate.
Order documents
The dialog box contains boxes for each of the relevant document types, that you can check to define required delivery methods. You can send the same document in several different ways by selecting several delivery methods. No documents are sent unless you select at least one of the delivery methods. There is a block against removing all selections in invoices; at least one of the delivery methods must be selected. Print previews of the documents works regardless of which delivery methods have been selected.
Accounting documents
You can send interest notes and reminders as fax and e-mail attachments in the same way as the order documents.
- Printout
- Printout (print to PDF) is the default value for all documents, so you only need to go into the dialog box if you want a different delivery method for any of the documents. You can define default values for this field via the Edit/Entry rules menu item. If the delivery method field is empty, Printout is still selected for all documents in the dialog box.
- You can send all order documents via e-mail. A valid e-mail address needs to
be entered for the associate. There is no validation in place on value in the
e-mail address field.
The name added to the Subject field of the e-mail is taken from the Text table, in the language in which the order/accounting document is entered. Otherwise, the text is obtained from the active language.
- EDI
- The EDI options are not available for delivery notes and production
orders.
EDI documents will only work if you also define the relevant document type in EDI messages.
- AutoInvoice
- AutoInvoice documents will only work if you have set up Visma AutoInvoice in the Visma AutoInvoice portal and in Business NXT.
In addition to the document types with the associated delivery methods described above, there are some additional settings.
EDI Settings
Media type
- E-media
Postage type
- 1. class mail
- 2. class mail
____
- Stop before sending e-mail
- Used to prevent immediate transmission by e-mail. This means you can edit the e-mail before it is sent to the contact.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Document delivery method 1 | Integer |
| SQL name | DocSMt | The database field name. |
| API identifier | documentDeliveryMethod1 | The API identifier used in GraphQL. |
| Number | 6385 |
Document delivery method 2
How documents are to be sent.
The method is suggested in the order head for the associate.
Order documents
The dialog box contains boxes for each of the relevant document types, that you can check to define required delivery methods. You can send the same document in several different ways by selecting several delivery methods. No documents are sent unless you select at least one of the delivery methods. There is a block against removing all selections in invoices; at least one of the delivery methods must be selected. Print previews of the documents works regardless of which delivery methods have been selected.
Accounting documents
You can send interest notes and reminders as fax and e-mail attachments in the same way as the order documents.
- Printout
- Printout (print to PDF) is the default value for all documents, so you only need to go into the dialog box if you want a different delivery method for any of the documents. You can define default values for this field via the Edit/Entry rules menu item. If the delivery method field is empty, Printout is still selected for all documents in the dialog box.
- You can send all order documents via e-mail. A valid e-mail address needs to
be entered for the associate. There is no validation in place on value in the
e-mail address field.
The name added to the Subject field of the e-mail is taken from the Text table, in the language in which the order/accounting document is entered. Otherwise, the text is obtained from the active language.
- EDI
- The EDI options are not available for delivery notes and production
orders.
EDI documents will only work if you also define the relevant document type in EDI messages.
- AutoInvoice
- AutoInvoice documents will only work if you have set up Visma AutoInvoice in the Visma AutoInvoice portal and in Business NXT.
In addition to the document types with the associated delivery methods described above, there are some additional settings.
EDI Settings
Media type
- E-media
Postage type
- 1. class mail
- 2. class mail
____
- Stop before sending e-mail
- Used to prevent immediate transmission by e-mail. This means you can edit the e-mail before it is sent to the contact.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Document delivery method 2 | Integer |
| SQL name | AcDocSMt | The database field name. |
| API identifier | documentDeliveryMethod2 | The API identifier used in GraphQL. |
| Number | 8305 |
EAN loc. code
The GLN/GS1 number for the associate.
The GLN/GS1 number is a numbering system developed to identify the legal entities involved in a transaction. Legal entities might be buyers, sellers, banks, hauliers, etc. You can also use the code to identify geographical locations in company addresses, departments, warehouse locations, loading bay doors, etc.
The allocation procedures guarantee that the location number is unique everywhere in the world. The number consists of a total of 18 digits. The structure can vary between member states.
If you have checked the Use EAN Location Code field under EDI processing field in the Company information table, a lookup is performed in this field during EDI import. It is important that two associates do not have the same GLN/GS1 number, as the lookup during EDI import would then lead to errors. If a company has administration and warehouse in different places, the company must have several GLN/GS1 numbers.
You can upload the field to the EDI export file.
An EAN/GTIN item number has either 8 or 13 digits. The 8-digit version is used for small packages. EAN/GTIN codes with 13 digits are unique all over the world, and the 2 or 3 first digits identify the country where the code was assigned.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | EAN code | Text (40) |
| SQL name | EANLocCd | The database field name. |
| API identifier | eanLocationCode | The API identifier used in GraphQL. |
| Number | 7561 |
eBusiness processing
This field is no longer in use. Be aware the field may be removed in later versions.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | eBusiness processing | Integer |
| SQL name | eProc | The database field name. |
| API identifier | ebusinessProcessing | The API identifier used in GraphQL. |
| Number | 11446 |
EFT bank fee code
The default EFT VAT code for the associate.
The value in the field is copied to the Voucher table. If there is a customer/supplier with both debit and credit, it is the credit customer that is copied over to the Voucher table.
The EFT VAT code for the supplier is used to set up the processing of bank fees when performing a electronic funds transfer. The following values are valid:
| Value | Explanation |
|---|---|
| 0 | "SHAR" - the sender takes the fee from their bank, the payment receiver takes from their |
| 1 | "DEBT" - the sender takes all the bank fees for the payment |
| 4 | "CRED" - the receiver takes all the bank fees for the payment |
The value in the EFT bank fee code field will be copied from the associate to the voucher lines and then transferred to open supplier entries. When you generate a payment proposal, the value will be transferred to the Foreign cost field in the Payment line table and taken into account in connection with payments. If the payment line has the value "0. Default" in the EFT bank fee code field and Bank Partner has a value from 1-4 in the Std. EFT bank fee code field, the value of bank partner will apply.
Visma.net AutoPay and Visma AutoPay will copy the Text field from Text table into Foreign cost field in Payment line table. If text does not exist, or Numeric cost codes is selected in EFT processing, the numeric value from EFT bank fee code will be copied instead.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | EFT bank fee | Integer |
| SQL name | EFT2 | The database field name. |
| API identifier | eftBankFeeCode | The API identifier used in GraphQL. |
| Number | 13768 |
EFT currency code
The default EFT currency code for the associate.
The value in the field is copied to the Voucher table. If there is a customer/supplier with both debit and credit, it is the credit customer that is copied over to the Voucher table.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | EFT Currency code | Integer |
| SQL name | EFT1 | The database field name. |
| API identifier | eftCurrencyCode | The API identifier used in GraphQL. |
| Number | 13767 |
EFT decl. code
For payment abroad, this field is used to enter the declaration code in accordance with national rules.
The declaration code you enter in this field becomes the default for the associate. The value in the field is copied to the Voucher table. If there is a customer/supplier with both debit and credit, it is the credit customer that is copied over to the Voucher table.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | EFT declaration code | Integer |
| SQL name | EFT3 | The database field name. |
| API identifier | eftDeclarationCode | The API identifier used in GraphQL. |
| Number | 13769 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Declaration code | DeclarationCode |
|
EFT form type
The form type for Electronic Funds Transfer.
- 1 = giro transfer with notification without payment ID
- 4 = giro transfer without notification with payment ID
- 15 = giro transfer with notification and payment ID
- 71 = money order without notification with payment ID
- 73 = money order with notification without payment ID
- 75 = money order with notification and payment ID
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | EFT form type | Integer |
| SQL name | EftFrmTp | The database field name. |
| API identifier | eftFormType | The API identifier used in GraphQL. |
| Number | 15462 |
EFT paym. method
The default EFT payment method for the associate.
The value in the field is copied to the Voucher table. If there is a customer/supplier with both debit and credit, it is the credit customer that is copied over to the Voucher table.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | EFT payment method | Integer |
| SQL name | EFT4 | The database field name. |
| API identifier | eftPaymentMethod | The API identifier used in GraphQL. |
| Number | 13770 |
EFT separator
The separator you want to use for batch payments.
The field is processed in some EFT systems on payments and after OCR scanning.
In direct remittances and OCR data scanning, you can specify the separator used in batch transactions for each supplier/customer.
When data is exported via the EFT system for batch invoices, the value in this field is used as the separator between invoice numbers.
If you enter one character, this character is used to separate the invoice numbers. If you enter two characters, each invoice number is placed between the two characters. If you enter three characters, each invoice number is placed between the first and last character and the middle character is used as a separator between the invoices.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | EFT separator | Text (3) |
| SQL name | EftSep | The database field name. |
| API identifier | eftSeparator | The API identifier used in GraphQL. |
| Number | 13018 |
E-mail address
The e-mail address of the associate.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | E-mail address | Text (60) |
| SQL name | MailAd | The database field name. |
| API identifier | emailAddress | The API identifier used in GraphQL. |
| Number | 4039 |
E-mail template group
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | E-mail template group | Integer |
| SQL name | EmailTmplGr | The database field name. |
| API identifier | emailTemplateGroup | The API identifier used in GraphQL. |
| Number | 17615 |
Empl. no.
A unique number identifying the employee.
Employee roles
- Employees can have various roles in different tables, such as:
- Official for a customer, an order, an organisational unit (department manager, project manager), a product, a delivery alternative, a warehouse, a resource or a capital asset.
- Seller responsible for a customer or a sales order.
- Buyer of a supplier or a purchase order, a product, a delivery alternative or a capital asset.
- Authorisation official for a supplier or an open supplier entry (incoming invoice).
- Participant in an order or a voucher (e.g. work undertaken).
The Empl. no. is a unique number identifying one specific Employee.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Empl. no. | Integer |
| SQL name | EmpNo | The database field name. |
| API identifier | employeeNo | The API identifier used in GraphQL. |
| Number | 4047 |
Employee price gr.
The price group for the employee.
The employee price group is suggested in the order head and order lines on the basis of the employee number.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Employee price group | Integer |
| SQL name | EmpPrGr | The database field name. |
| API identifier | employeePriceGroup | The API identifier used in GraphQL. |
| Number | 4198 |
Encryption Key
The encryption key for the associate.
Encryption keys can be imported through EDI documents. The encryption key is not used for any functionality inside Business NXT.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Encryption Key | Text (20) |
| SQL name | CryptK | The database field name. |
| API identifier | encryptionKey | The API identifier used in GraphQL. |
| Number | 8455 |
Exempt from sp. tax
If you use special tax you can exempt orders from it.
- 1 - No special tax
- No special tax
- 2 - Only specification on invoice
- Only specification on invoice
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Exempt from sp. tax | Integer |
| SQL name | ExSpc | The database field name. |
| API identifier | exemptFromSpecialTax | The API identifier used in GraphQL. |
| Number | 4067 |
Expense account
Accumulated expenses in a specific account for each customer or range of customers (defined in the Account no. series table).
If you do not enter a value here the account references from the Company information table will be used.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | OlAcNo | The database field name. |
| API identifier | outlayAccountNo | The API identifier used in GraphQL. |
| Number | 8437 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | OutlayAccount |
|
External export grouping
A group to which the associate belongs.
This is used by Zpider.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | External: Export grouping | Integer |
| SQL name | ExtExpGr | The database field name. |
| API identifier | externalExportGrouping | The API identifier used in GraphQL. |
| Number | 13712 |
External ID
An external id for the associate used by external applications.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | External ID | Text (156) |
| SQL name | ExtID | The database field name. |
| API identifier | externalId | The API identifier used in GraphQL. |
| Number | 6415 |
Fact. company no./CID-def.
The factoring company, if you are using more than one factoring company or if you have a large number of customers abroad.
This is used for printing invoices and OCR scanning payments.
If you have a large number of customers abroad, you create payment accounts abroad for the customers in the relevant countries, and you define the CID code in this field according to the national requirements.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Factoring no. | Integer |
| SQL name | FCNo | The database field name. |
| API identifier | factoringCompanyNo | The API identifier used in GraphQL. |
| Number | 12232 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Factoring company | FactoringCompany |
|
Factoring no.
The customer's factoring number indicating that factoring will be used for this associate.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Organisation no. | Text (24) |
| SQL name | FactNo | The database field name. |
| API identifier | factoringNo | The API identifier used in GraphQL. |
| Number | 4081 |
Fax
The fax number.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Phone | Text (20) |
| SQL name | Fax | The database field name. |
| API identifier | fax1 | The API identifier used in GraphQL. |
| Number | 4044 |
Fax 2
The second fax number.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Phone | Text (20) |
| SQL name | Fax2 | The database field name. |
| API identifier | fax2 | The API identifier used in GraphQL. |
| Number | 6126 |
Flow group
Used to define a supplier's predefined flow group.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | No. | Integer |
| SQL name | FlGr | The database field name. |
| API identifier | flowGroup | The API identifier used in GraphQL. |
| Number | 12673 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Flow group | FlowGroup |
|
Form ID
You can use the form id to join the customer with a form.
Suggested when you enter orders for the customer. You can only use the field in XML and EDI outlays directly from the customer.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | No. | Integer |
| SQL name | FormId | The database field name. |
| API identifier | formId | The API identifier used in GraphQL. |
| Number | 13771 |
From date
Can be used for two different reasons. The date when a customer relationship began or when an employee started in the company.
In the Created date field you bring up the date on which you created the associate.
The date is validated using the regional settings in Windows.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Date | Integer |
| SQL name | FrDt | The database field name. |
| API identifier | fromDate | The API identifier used in GraphQL. |
| Number | 4124 |
Giro no. check sum
When you use a bank giro number, there is a check via BIG, that the giro no check sum matches with the giro number on the same line.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | No. | Integer |
| SQL name | GiroChSm | The database field name. |
| API identifier | giroNoCheckSum | The API identifier used in GraphQL. |
| Number | 10495 |
Giro type
Defines information available on the giro used for payment.
When using Visma.net AutoPay for outgoing payments, different codes can be entered here for Danish suppliers to decide which payment form to be used.
- 04 - Danish Inpayment Form type 04
- 71 - Danish Inpayment Form type 71
- 73 - Danish Inpayment Form type 73
- 75 - Danish Inpayment Form type 75
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Bank giro type | Integer |
| SQL name | GiroTp | The database field name. |
| API identifier | giroType | The API identifier used in GraphQL. |
| Number | 17730 |
GL account cust.
The general ledger account the customer is allocated to.
If the field is blank, the Customer account field in the Company information table will be used. It is also possible to enter general ledger account numbers for ranges of customer numbers in the Account no. series table.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | CustAcNo | The database field name. |
| API identifier | generalLedgerAccountNoForCustomer | The API identifier used in GraphQL. |
| Number | 4062 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | GeneralLedgerAccountForCustomer |
|
GL account sup.
The general ledger account the supplier is allocated to.
If the field is blank, the Supplier account field in the Company information table will be used. It is also possible to enter general ledger account numbers for ranges of supplier numbers in the Account no. series table.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | SupAcNo | The database field name. |
| API identifier | generalLedgerAccountNoForSupplier | The API identifier used in GraphQL. |
| Number | 4063 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | GeneralLedgerAccountForSupplier |
|
Gr. 1
A group to which the associate belongs.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Associate grouping 1 | Integer |
| SQL name | Gr | The database field name. |
| API identifier | group1 | The API identifier used in GraphQL. |
| Number | 4112 |
Gr. 2
A group to which the associate belongs.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Associate grouping 2 | Integer |
| SQL name | Gr2 | The database field name. |
| API identifier | group2 | The API identifier used in GraphQL. |
| Number | 4113 |
Gr. 3
A group to which the associate belongs.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Associate grouping 3 | Integer |
| SQL name | Gr3 | The database field name. |
| API identifier | group3 | The API identifier used in GraphQL. |
| Number | 4114 |
Gr. 4
A group to which the associate belongs.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Associate grouping 4 | Integer |
| SQL name | Gr4 | The database field name. |
| API identifier | group4 | The API identifier used in GraphQL. |
| Number | 4115 |
Gr. 5
A group to which the associate belongs.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Associate grouping 5 | Integer |
| SQL name | Gr5 | The database field name. |
| API identifier | group5 | The API identifier used in GraphQL. |
| Number | 4116 |
Gr. 6
A group to which the associate belongs.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Associate grouping 6 | Integer |
| SQL name | Gr6 | The database field name. |
| API identifier | group6 | The API identifier used in GraphQL. |
| Number | 4117 |
Gr. 7
A group to which the associate belongs.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Associate grouping 7 | Integer |
| SQL name | Gr7 | The database field name. |
| API identifier | group7 | The API identifier used in GraphQL. |
| Number | 5998 |
Gr. 8
A group to which the associate belongs.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Associate grouping 8 | Integer |
| SQL name | Gr8 | The database field name. |
| API identifier | group8 | The API identifier used in GraphQL. |
| Number | 5999 |
Gr. 9
A group to which the associate belongs.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Associate grouping 9 | Integer |
| SQL name | Gr9 | The database field name. |
| API identifier | group9 | The API identifier used in GraphQL. |
| Number | 6000 |
Gr. 10
A group to which the associate belongs.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Associate grouping 10 | Integer |
| SQL name | Gr10 | The database field name. |
| API identifier | group10 | The API identifier used in GraphQL. |
| Number | 6001 |
Gr. 11
A group to which the associate belongs.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Associate grouping 11 | Integer |
| SQL name | Gr11 | The database field name. |
| API identifier | group11 | The API identifier used in GraphQL. |
| Number | 6002 |
Gr. 12
A group to which the associate belongs.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Associate grouping 12 | Integer |
| SQL name | Gr12 | The database field name. |
| API identifier | group12 | The API identifier used in GraphQL. |
| Number | 6003 |
IBAN
The company's IBAN account number.
Then you must also complete the Bank branch or Swift code fields. Which fields you complete depends on the IBAN requirements in the receiver's country, which you can find out from the bank or your supplier.
IBAN (International Bank Account Number) is an international standard for account numbers, which you use in connection with payments to and from abroad. On payment suggestions for foreign suppliers, is the priority order for which account number to use: IBAN, Bank account and Postal giro, the first one completed will be used (unless an account number exists on the open entry).
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Bank account | Text (35) |
| SQL name | IBAN | The database field name. |
| API identifier | iban | The API identifier used in GraphQL. |
| Number | 17729 |
Incoming invoice deviation tolerance %
Allowed deviation tolerance in % for supplier invoices.
This field offers the possibility to specify for each supplier the allowed deviation tolerance in % (based on the invoice amount) between the supplier invoice amount and the original purchase order amount in Business NXT. Only values between 0 and 100 are permitted. If the flag Do not tolerate any deviation is enabled then the order match processing will disregard the value in this field and then unless no deviation in amount exists the order line will be flagged as outside deviation tolerance.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Percent | Decimal |
| SQL name | IIDvTlP | The database field name. |
| API identifier | incomingInvoiceDeviationTolerancePercent | The API identifier used in GraphQL. |
| Number | 17969 |
Incoming invoice deviation tolerance amount
Allowed deviation tolerance amount for supplier invoices.
This field offers the possibility to specify for each supplier the allowed deviation tolerance amount between the supplier invoice amount and the original purchase order amount in Business NXT. If the flag Do not tolerate any deviation is enabled then the order match processing will disregard the value in this field and then unless no deviation in amount exists the order line will be flagged as outside deviation tolerance.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Amount | Decimal |
| SQL name | IIDvTlAm | The database field name. |
| API identifier | incomingInvoiceDeviationToleranceAmount | The API identifier used in GraphQL. |
| Number | 17970 |
Inf. 1
Additional associate 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 | 4118 |
Inf. 2
Additional associate 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 | 4119 |
Inf. 3
Additional associate 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 | 4120 |
Inf. 4
Additional associate 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 | 4121 |
Inf. 5
Additional associate 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 | 4122 |
Inf. 6
Additional associate 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 | 4123 |
Inf. 7
Additional associate 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 | 6085 |
Inf. 8
Additional associate 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 | 6086 |
Inf. category
A group to which the associate belongs.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Information category | Integer |
| SQL name | InfCat | The database field name. |
| API identifier | informationCategory | The API identifier used in GraphQL. |
| Number | 4106 |
Interest fee
The interest fee which is used for the customer.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Amount | Decimal |
| SQL name | IntFee | The database field name. |
| API identifier | interestFee | The API identifier used in GraphQL. |
| Number | 16421 |
Interest rate
The interest rate used for the customer.
You can override the interest rate in individual entries. If none is specified the interest rates defined in the Country table will be used.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Percent | Decimal |
| SQL name | IntRt | The database field name. |
| API identifier | interestRate | The API identifier used in GraphQL. |
| Number | 4096 |
Interest rate group
A group to which the associate belongs.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Interest rate group | Integer |
| SQL name | IntGr | The database field name. |
| API identifier | interestRateGroup | The API identifier used in GraphQL. |
| Number | 11217 |
Invoice customer no.
The customer paying the invoice, if it is different from the buyer/receiver of the goods or services.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Cust. no. | Integer |
| SQL name | InvoCust | The database field name. |
| API identifier | invoiceCustomerNo | The API identifier used in GraphQL. |
| Number | 4080 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Associate | InvoiceCustomer |
|
Invoice note text no.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Invoice note | Integer |
| SQL name | InvNtTxtNo | The database field name. |
| API identifier | invoiceNoteTextNo | The API identifier used in GraphQL. |
| Number | 19609 |
Language no.
The language, if it is different from the default language defined in the Company information table.
The language determines which texts are printed in documents that are sent to the customer/supplier.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Language no. | Integer |
| SQL name | Lang | The database field name. |
| API identifier | languageNo | The API identifier used in GraphQL. |
| Number | 4037 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Language | Language |
|
Last delivery note date
The date when the last delivery note was sent to the customer.
The date is validated using the regional settings in Windows.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Date | Integer |
| SQL name | LstDelDt | The database field name. |
| API identifier | lastDeliveryNoteDate | The API identifier used in GraphQL. |
| Number | 6387 |
Last reminder date
The date when the last reminder was sent to the customer.
The date is validated using the regional settings in Windows.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Date | Integer |
| SQL name | LstRemDt | The database field name. |
| API identifier | lastReminderDate | The API identifier used in GraphQL. |
| Number | 4092 |
Lead time
The number of days the supplier needs to delivery the product.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Days | Integer |
| SQL name | DelTm | The database field name. |
| API identifier | leadTime | The API identifier used in GraphQL. |
| Number | 6324 |
Main associate
The main associate to which an associate belongs.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Associate no. | Integer |
| SQL name | MainAct | The database field name. |
| API identifier | mainAssociateNo | The API identifier used in GraphQL. |
| Number | 6476 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Associate | MainAssociate |
|
Matching method cust.
The matching method used for the customer.
Regardless of which of the 4 methods you select, you can match entries manually by going into the Open customer entries or Open supplier entries table, selecting the entries to match and selecting one of the processings for matching entries. In methods 2, 3 and 4 Business NXT will also try to match entries during voucher updates.
The matching method can also be overridden for individual customers/suppliers. 5 means the same as if the field were not filled in, except in the Associate table, where a blank field means that the matching method under Company information is to apply.
- 1 - Manual
- You must select 1 if Business NXT is to keep open customer and supplier entries. But if you do not want automatic matching by date, amount or references during updating of vouchers, matching must take place via the processings for matching, in the tables of open customer and supplier entries.
- 2 - Ascending date
- If you select 2, an attempt will be made to match entries against the oldest entry/entries for the relevant customer or supplier. Matching continues until there is no outstanding amount for the entry, or there is nothing more to match against (in which case the outstanding amount is returned to the open entries table). If several entries share the same date, they are matched in ascending order of journal and version number, i.e. in the order in which the transactions were generated/the vouchers were entered.
- 3 - Same amount
- 3 means that matching will take place against the oldest entry with the same amount. If there is no entry with the identical amount and the opposite sign, the entry is not matched when it is updated.
- 4 - Entered references
- 4 means that the entries must match entries that were selected explicitly during voucher entry. Such references are specified in the cross-reference field in the voucher line or in the Cross-references table, which you can choose to join to the voucher lines. From these fields you can also look up open entries, move to a specified row, select several and press Ctrl + Return. It is not necessary for customer number or supplier number to be entered in the voucher line. If no account type is specified, Business NXT will first of all look up in open customer entries, and then, if the cross-reference is specified, in open supplier entries, to complete the customer number or supplier number for debit or credit in the voucher line. Business NXT also enters the currency number, exchange rate and amount in current currency and default currency in the voucher line, if the amount is not already specified, and deducts any cash discount.
- 5 - Do not keep open entries
- Even if you normally wish to retain open entries, you may not want to do this for Sundry customers, for example, and you can then select matching method 5 for such customers.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Matching method | Integer |
| SQL name | CustMaMt | The database field name. |
| API identifier | matchingMethodForCustomer | The API identifier used in GraphQL. |
| Number | 4598 |
Matching method sup.
The matching method used for the supplier.
Regardless of which of the 4 methods you select, you can match entries manually by going into the Open customer entries or Open supplier entries table, selecting the entries to match and selecting one of the processings for matching entries. In methods 2, 3 and 4 Business NXT will also try to match entries during voucher updates.
The matching method can also be overridden for individual customers/suppliers. 5 means the same as if the field were not filled in, except in the Associate table, where a blank field means that the matching method under Company information is to apply.
- 1 - Manual
- You must select 1 if Business NXT is to keep open customer and supplier entries. But if you do not want automatic matching by date, amount or references during updating of vouchers, matching must take place via the processings for matching, in the tables of open customer and supplier entries.
- 2 - Ascending date
- If you select 2, an attempt will be made to match entries against the oldest entry/entries for the relevant customer or supplier. Matching continues until there is no outstanding amount for the entry, or there is nothing more to match against (in which case the outstanding amount is returned to the open entries table). If several entries share the same date, they are matched in ascending order of journal and version number, i.e. in the order in which the transactions were generated/the vouchers were entered.
- 3 - Same amount
- 3 means that matching will take place against the oldest entry with the same amount. If there is no entry with the identical amount and the opposite sign, the entry is not matched when it is updated.
- 4 - Entered references
- 4 means that the entries must match entries that were selected explicitly during voucher entry. Such references are specified in the cross-reference field in the voucher line or in the Cross-references table, which you can choose to join to the voucher lines. From these fields you can also look up open entries, move to a specified row, select several and press Ctrl + Return. It is not necessary for customer number or supplier number to be entered in the voucher line. If no account type is specified, Business NXT will first of all look up in open customer entries, and then, if the cross-reference is specified, in open supplier entries, to complete the customer number or supplier number for debit or credit in the voucher line. Business NXT also enters the currency number, exchange rate and amount in current currency and default currency in the voucher line, if the amount is not already specified, and deducts any cash discount.
- 5 - Do not keep open entries
- Even if you normally wish to retain open entries, you may not want to do this for Sundry customers, for example, and you can then select matching method 5 for such customers.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Matching method | Integer |
| SQL name | SupMaMt | The database field name. |
| API identifier | matchingMethodForSupplier | The API identifier used in GraphQL. |
| Number | 4599 |
Max direct debit. amount
The maximum direct debit amount for each entry.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Amount | Decimal |
| SQL name | MaxDebAm | The database field name. |
| API identifier | maxDirectDebitingAmount | The API identifier used in GraphQL. |
| Number | 5509 |
Max. % of credit overdue
The percentage that will be used as a basis for testing for unpaid, overdue invoices.
The test is performed for orders if the associated field has a value greater than 0.
- In the customer ledger there must be no overdue invoices with a total amount outstanding greater than the percentage multiplied by the customer’s (i.e. the invoice recipient’s) credit limit, and
- none of the overdue invoices may be older than the number of days stated.
It overrides the corresponding fields under Company information.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | No. | Integer |
| SQL name | MaxDueP | The database field name. |
| API identifier | maxPercentOfCreditOverdue | The API identifier used in GraphQL. |
| Number | 8229 |
Max. days overdue
The number of days that will be used on the credit control check for overdue invoices.
It is used for the warning or block on the credit control setting in the Company information table. It overrides corresponding fields under Company information.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Days | Integer |
| SQL name | MaxDueDy | The database field name. |
| API identifier | maxDaysOverdue | The API identifier used in GraphQL. |
| Number | 8230 |
Max. no. of reminders
The number of reminders to send before the transactions will be included in the debt collection/change list.
When you send a reminder to a customer you define the reminder number and the reminder text. When you reach a number of reminders that you have specified in the field for the maximum number of reminders, the final reminder for the country is used. If you have not specified a maximum number of reminders all reminders will be written.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Number of reminders | Integer |
| SQL name | MaxRems | The database field name. |
| API identifier | maxNoOfReminders | The API identifier used in GraphQL. |
| Number | 4091 |
Memo file name
The file name for the Memo attached to the associate.
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 | NoteNm | The database field name. |
| API identifier | memoFileName | The API identifier used in GraphQL. |
| Number | 4236 |
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 | 19202 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Memo | Memo |
|
Mobile phone
The mobile phone number.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Phone | Text (20) |
| SQL name | MobPh | The database field name. |
| API identifier | mobilePhone | The API identifier used in GraphQL. |
| Number | 4042 |
Name
The name of the associate.
| 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 | 4029 |
New customer no.
The new customer no for an existing customer.
You can highlight/select the associates with a value in New customer no. and execute the menu item Change customer/supplier number. The Change Customer no./Supplier no. processing updates all foreign keys containing the Cust. no. field in all tables which refer to them. Business NXT also deals with instances where two numerical keys exchange values.
The old number is saved in the Previously customer no. field. If you change to the same customer number in several rows in the Associate table via the New customer no. field and save, the Cust. no. field must be greyed out in all rows except the first one.
If you use common tables for Associate, General ledger account or Product, you cannot use the function for changing number. This function only processes transactions in the active company and not in the other companies using the same table. We therefore recommend regulating access to the field so it is not visible to some Access groups.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Cust. no. | Integer |
| SQL name | NwCNo | The database field name. |
| API identifier | newCustomerNo | The API identifier used in GraphQL. |
| Number | 7364 |
New supplier no.
The new supplier no for an existing supplier.
You can highlight/select the associates with a value in New supplier no. and execute the Change Customer no./Supplier no. processing. The processing Change Customer no./Supplier no. updates all foreign keys containing the Sup. no. field in all tables which refer to them. Business NXT also deals with instances where two numerical keys exchange values.
The old number is saved in the Previously supplier no. field.
If you use common tables for Associate, General ledger account or Product, you cannot use the function for changing number. This function only processes transactions in the active company and not in the other companies using the same table. We therefore recommend regulating access to the field so it is not visible to some Access groups.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Sup. no. | Integer |
| SQL name | NwSNo | The database field name. |
| API identifier | newSupplierNo | The API identifier used in GraphQL. |
| Number | 7365 |
No. of employees
The number of employees at the associate.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | No. | Integer |
| SQL name | NoOfEmp | The database field name. |
| API identifier | noOfEmployees | The API identifier used in GraphQL. |
| Number | 4110 |
No. of reminders sent
How many times you have issued reminders for the entry that has had the most reminders. This could be higher than the letter number.
This field is obsolete. No. of reminders is given per invoice in the Open customer entry and Customer transaction tables.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Number of reminders | Integer |
| SQL name | LstRemNo | The database field name. |
| API identifier | noOfRemindersSent | The API identifier used in GraphQL. |
| Number | 4093 |
Normal time discrep.
Used in the time registration module to generate a time schedule balance, and will calculate a deduction in relation to the time schedule group's normal time as a %.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Percent | Decimal |
| SQL name | NrmTDisc | The database field name. |
| API identifier | normalTimeDiscrepance | The API identifier used in GraphQL. |
| Number | 12365 |
Organisation no.
The company's organisation number in the national registry.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Organisation no. | Text (24) |
| SQL name | BsNo | The database field name. |
| API identifier | companyNo | The API identifier used in GraphQL. |
| Number | 4109 |
Organisational unit 1
The department, project, etc. the associate is linked to.
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 | R1 | The database field name. |
| API identifier | orgUnit1 | The API identifier used in GraphQL. |
| Number | 4053 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 1 | OrgUnit1 |
|
Organisational unit 2
The department, project, etc. the associate is linked to.
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 | R2 | The database field name. |
| API identifier | orgUnit2 | The API identifier used in GraphQL. |
| Number | 4054 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 2 | OrgUnit2 |
|
Organisational unit 3
The department, project, etc. the associate is linked to.
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 | R3 | The database field name. |
| API identifier | orgUnit3 | The API identifier used in GraphQL. |
| Number | 4055 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 3 | OrgUnit3 |
|
Organisational unit 4
The department, project, etc. the associate is linked to.
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 | R4 | The database field name. |
| API identifier | orgUnit4 | The API identifier used in GraphQL. |
| Number | 4056 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 4 | OrgUnit4 |
|
Organisational unit 5
The department, project, etc. the associate is linked to.
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 | R5 | The database field name. |
| API identifier | orgUnit5 | The API identifier used in GraphQL. |
| Number | 4057 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 5 | OrgUnit5 |
|
Organisational unit 6
The department, project, etc. the associate is linked to.
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 | R6 | The database field name. |
| API identifier | orgUnit6 | The API identifier used in GraphQL. |
| Number | 4058 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 6 | OrgUnit6 |
|
Organisational unit 7
The department, project, etc. the associate is linked to.
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 | R7 | The database field name. |
| API identifier | orgUnit7 | The API identifier used in GraphQL. |
| Number | 9486 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 7 | OrgUnit7 |
|
Organisational unit 8
The department, project, etc. the associate is linked to.
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 | R8 | The database field name. |
| API identifier | orgUnit8 | The API identifier used in GraphQL. |
| Number | 9487 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 8 | OrgUnit8 |
|
Organisational unit 9
The department, project, etc. the associate is linked to.
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 | R9 | The database field name. |
| API identifier | orgUnit9 | The API identifier used in GraphQL. |
| Number | 9488 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 9 | OrgUnit9 |
|
Organisational unit 10
The department, project, etc. the associate is linked to.
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 | R10 | The database field name. |
| API identifier | orgUnit10 | The API identifier used in GraphQL. |
| Number | 9489 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 10 | OrgUnit10 |
|
Organisational unit 11
The department, project, etc. the associate is linked to.
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 | R11 | The database field name. |
| API identifier | orgUnit11 | The API identifier used in GraphQL. |
| Number | 9490 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 11 | OrgUnit11 |
|
Organisational unit 12
The department, project, etc. the associate is linked to.
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 | R12 | The database field name. |
| API identifier | orgUnit12 | The API identifier used in GraphQL. |
| Number | 9491 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Organisational unit 12 | OrgUnit12 |
|
Our cust./sup. no.
Your customer number with the supplier or your supplier number with the customer.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Organisation no. | Text (24) |
| SQL name | OurCNo | The database field name. |
| API identifier | ourCustomerOrSupplierNo | The API identifier used in GraphQL. |
| Number | 4105 |
Pager
The pager number.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Phone | Text (20) |
| SQL name | Pers | The database field name. |
| API identifier | pager | The API identifier used in GraphQL. |
| Number | 4043 |
Payment method cust.
The payment method for the customer.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Payment method | Integer |
| SQL name | CPmtMt | The database field name. |
| API identifier | paymentMethodForCustomer | The API identifier used in GraphQL. |
| Number | 4083 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Payment method | PaymentMethodForCustomer |
|
Payment method sup.
The payment method for the supplier.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Payment method | Integer |
| SQL name | SPmtMt | The database field name. |
| API identifier | paymentMethodForSupplier | The API identifier used in GraphQL. |
| Number | 4376 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Payment method | PaymentMethodForSupplier |
|
Payment priority
In the Payment priority field you can enter your own priority codes, which you can choose to sort or select by in connection with payment suggestions.
The value you enter here is suggested when you run vouchers for the supplier, and is carried forward to open customer and supplier entries and transactions. The priority can also be suggested from the voucher type.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Payment priority | Integer |
| SQL name | RmtPri | The database field name. |
| API identifier | remittancePriority | The API identifier used in GraphQL. |
| Number | 4497 |
Payment supplier no.
You only need to complete this field if payment is to be made to someone other than the supplier.
Suggested when you enter orders for the supplier.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Sup. no. | Integer |
| SQL name | RmtSup | The database field name. |
| API identifier | remittanceSupplierNo | The API identifier used in GraphQL. |
| Number | 4098 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Associate | RemittanceSupplier |
|
Payment terms cust.
The payment term for the customer.
These fields are suggested when you enter orders, and in voucher lines when you debit customers. The payment terms fields refer to the Payment term table, where you have defined how many days/months of credit the customer is granted, including cash discounts if appropriate.
If you have not registered the customer's payment terms, the Standard payment terms. are retrieved from the Company information table in connection with the new entry of orders and the EDI import of orders.
Calculate due date
The payment terms are the basis of your calculation of due dates in invoices and voucher lines. You can override the due date in orders and voucher lines, or later in the open entries. If no other payment terms are defined, any Standard payment terms. defined under Company information will be applied to calculate due dates. If no payment terms are defined, the terms used will be cash on invoicing and 30 days net in the voucher lines.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Payment terms | Integer |
| SQL name | CPmtTrm | The database field name. |
| API identifier | paymentTermsForCustomer | The API identifier used in GraphQL. |
| Number | 4082 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Payment term | PaymentTermsForCustomer |
|
Payment terms sup.
The payment term for the supplier.
These fields are suggested when you enter purchase orders, and in voucher lines when you credit suppliers. The payment terms fields refer to the Payment term table, where you have defined how many days/months of credit you are granted by the supplier, including cash discounts if appropriate.
If you have not registered the customer's payment terms, the Standard payment terms. are retrieved from the Company information table in connection with the new entry of orders and the EDI import of orders.
Calculate due date
The payment terms are the basis of your calculation of due dates in invoices and voucher lines. You can override the due date in orders and voucher lines, or later in the open entries. If no other payment terms are defined, any Standard payment terms. defined under Company information will be applied to calculate due dates. If no payment terms are defined, the terms used will be cash on invoicing and 30 days net in the voucher lines.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Payment terms | Integer |
| SQL name | SPmtTrm | The database field name. |
| API identifier | paymentTermsForSupplier | The API identifier used in GraphQL. |
| Number | 4375 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Payment term | PaymentTermsForSupplier |
|
Person ID
A person's birthday or a another ID that identifies person.
The value of the field is updated from the dialog Payment when doing cash orders, when you create new customers and when you fill out Personal ID
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Person ID | Text (24) |
| SQL name | PerID | The database field name. |
| API identifier | personId | The API identifier used in GraphQL. |
| Number | 16218 |
Phone
The phone number.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Phone | Text (20) |
| SQL name | Phone | The database field name. |
| API identifier | phone | The API identifier used in GraphQL. |
| Number | 4040 |
Picture file name
A link to the picture file for the associate.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Picture file name | Text (260) |
| SQL name | PictFNm | The database field name. |
| API identifier | pictureFileName | The API identifier used in GraphQL. |
| Number | 8551 |
Post code
The post code.
If you enter a Post code that exists in the Postal address table, the Postal area field is filled in and the cursor jumps to the next field. If the Post code does not exist you will see a warning in the Status bar and the cursor will then stop in the Postal area field so you can type in the Postal area manually.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Post code | Text (40) |
| SQL name | PNo | The database field name. |
| API identifier | postCode | The API identifier used in GraphQL. |
| Number | 4034 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Postal address | PostalAddress |
|
Postal area
The postal area.
If you enter a postcode that exists in the Postal address table, Business NXT fills in the Postal area field and the cursor jumps to the next field.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Address line | Text (60) |
| SQL name | PArea | The database field name. |
| API identifier | postalArea | The API identifier used in GraphQL. |
| Number | 4035 |
Postal giro
The postal giro number of the associate.
This is relevant if you want to print completed postal giro forms in connection with reminders, interest notes and payments, or if you use electronic funds transfer. You can restrict payments to associates for whom at least one of the Bank account or Postal giro fields is completed. To do this you must select the Payment if giro no. option in the Payment processing field in the Company information table.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Bank account | Text (35) |
| SQL name | PGiro | The database field name. |
| API identifier | postalGiro | The API identifier used in GraphQL. |
| Number | 4085 |
Previously customer no.
When you change a customer number the old number is saved in this field.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Cust. no. | Integer |
| SQL name | OldCNo | The database field name. |
| API identifier | previouslyCustomerNo | The API identifier used in GraphQL. |
| Number | 7189 |
Previously supplier no.
When you change a supplier number the old number is saved in this field.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Sup. no. | Integer |
| SQL name | OldSNo | The database field name. |
| API identifier | previouslySupplierNo | The API identifier used in GraphQL. |
| Number | 7190 |
Price from supplier no.
The values you enter in the Price from supplier no. and Sales price addition % fields enable Business NXT to calculate sales prices for specific customers or specific orders as purchase prices from a given supplier plus a possible % addition.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Sup. no. | Integer |
| SQL name | PrSup | The database field name. |
| API identifier | priceFromSupplierNo | The API identifier used in GraphQL. |
| Number | 5722 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Associate | PriceFromSupplier |
|
Private person
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Boolean | Integer |
| Memory field | Yes | The value in this field is only displayed in the program, it is not stored in the database. |
| API identifier | privatePerson | The API identifier used in GraphQL. |
| Number | 18986 |
Private phone
The private phone number.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Phone | Text (20) |
| SQL name | PrivPh | The database field name. |
| API identifier | privatePhone | The API identifier used in GraphQL. |
| Number | 4041 |
Production time
The time it takes to produce a product.
The production time is used to calculate the total delivery time. Suggested when you enter the Sup. no. in the Delivery alternative table or the Normal supplier field in the Stock balance table.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Days | Integer |
| SQL name | ProdTm | The database field name. |
| API identifier | productionTime | The API identifier used in GraphQL. |
| Number | 11595 |
Reminder fee
The reminder fee for the customer.
The reminder fee in the currency according to the Country no. of the customer in the Associate table. If the Country no. field in the Associate table is blank, the default Country no. in the Company information table is used.
You can use the Reminder fee field in the Associate table to override the value in the Reminder fee field in the Reminder table in order to obtain the reminder fee in the customer's currency. If you use this option, the same reminder fee is used in all reminders.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Amount | Decimal |
| SQL name | Fee | The database field name. |
| API identifier | reminderFee | The API identifier used in GraphQL. |
| Number | 13867 |
Reminder printing date
The date when the last reminder got printed for the customer.
The date is validated using the regional settings in Windows.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Date | Integer |
| SQL name | RemPrDt | The database field name. |
| API identifier | reminderPrintingDate | The API identifier used in GraphQL. |
| Number | 11003 |
Responsible
The official for the associate.
The Empl. no. is a unique number identifying one specific Employee.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Empl. no. | Integer |
| SQL name | Rsp | The database field name. |
| API identifier | official | The API identifier used in GraphQL. |
| Number | 4052 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Associate | Official |
|
Sales price addition %
The percentage by which you want the sales price to increase.
The values you enter in the Price from supplier no. and Sales price addition % fields are suggested in the order head. Sales prices for specific customers or specific orders are calculated as purchase prices from a given supplier plus an addition. At the same time the cost price is set equal to the purchase price.
Sales prices can also be calculated on the basis of other prices via the sales price basis and sales price addition fields in the Price- and discount matrix table.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Percent | Decimal |
| SQL name | SPrAdd | The database field name. |
| API identifier | salesPriceAddition | The API identifier used in GraphQL. |
| Number | 5723 |
Sector
A group to which the associate belongs.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Trade | Integer |
| SQL name | Trade | The database field name. |
| API identifier | sector | The API identifier used in GraphQL. |
| Number | 4107 |
Seller
The seller who is responsible for the customer.
The Empl. no. is a unique number identifying one specific Employee.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Empl. no. | Integer |
| SQL name | Seller | The database field name. |
| API identifier | seller | The API identifier used in GraphQL. |
| Number | 4050 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Associate | Seller |
|
Send in to associate no.
To whom the products are to be delivered from the supplier.
Only used for Transaction type 6 - Purchase. This field is suggested when you enter orders for the supplier.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Associate no. | Integer |
| SQL name | DelFrAct | The database field name. |
| API identifier | sendInToAssociateNo | The API identifier used in GraphQL. |
| Number | 4333 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Associate | SendInToAssociate |
|
Send to associate no.
To whom the products are to be delivered if it is someone other than the customer.
Only used for transaction type 1 - Sales, transaction type 2 - Hire and transaction type 3 - Loan. Suggested when you enter orders for the customer/supplier.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Associate no. | Integer |
| SQL name | DelToAct | The database field name. |
| API identifier | sendToAssociateNo | The API identifier used in GraphQL. |
| Number | 4071 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Associate | SendToAssociate |
|
Ship to associate no.
Who is to receive the goods if this associate differs from the content of the fields for send to associate, customer, send in to associate, date and us.
Suggested when you enter orders for the customer/supplier (final delivery address or collection centre).
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Associate no. | Integer |
| SQL name | ShpActNo | The database field name. |
| API identifier | shipToAssociateNo | The API identifier used in GraphQL. |
| Number | 12802 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Associate | ShipToAssociate |
|
Short name
Used to sort the associates in a particular order or to make selections on groups of associates.
Business NXT suggests the contents in the field when you enter a value in the Name field.
Example
If you enter the customer AS Ole Hansen in the Name field, this customer is sorted under A in an alphabetical list of names. To sort the customer under the letter H instead, you enter Hansen, Ole AS in the Short name field. For an alphabetical list of your customers, sort using the Short name field instead of the Name field.| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Name | Text (80) |
| SQL name | Shrt | The database field name. |
| API identifier | shortName | The API identifier used in GraphQL. |
| Number | 4038 |
SMS-provider
The SMS provider.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | SMS-provider | Integer |
| SQL name | SmsProv | The database field name. |
| API identifier | smsProvider | The API identifier used in GraphQL. |
| Number | 11466 |
Source no.
States from where you have obtained information on the associate.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Source no. | Integer |
| SQL name | SrcNo | The database field name. |
| API identifier | sourceNo | The API identifier used in GraphQL. |
| Number | 4126 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Source | Source |
|
Sup. no.
A unique number identifying the supplier.
You should place the supplier number within the range for account type 2 (suppliers). You define this range in the Account no. series table. This enables you to avoid entering the account type when entering vouchers.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Sup. no. | Integer |
| SQL name | SupNo | The database field name. |
| API identifier | supplierNo | The API identifier used in GraphQL. |
| Number | 4046 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Supplier current balance | SupplierCurrentBalance |
|
Supplier no. series
When set on a supplier template, this value will be used to select the supplier series when creating a new supplier from incoming documents.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Account number series no. | Integer |
| SQL name | SupSr | The database field name. |
| API identifier | supplierNoSeries | The API identifier used in GraphQL. |
| Number | 19672 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Account no. series | SupplierNoSeries |
|
Supplier options
Settings defining the behaviour of the supplier.
Order
- Gross orders
- The same check box will be selected in the order preference dialog box, based on the supplier. See the description of the Order table.
- Price refund agreement
- Order: If a supplier wishes to refund price reductions relating to
stock levels, you check Price refund agreement.
- Business NXT will then log such price refunds in the Price refund table.
- You can print refund requests for suppliers.
- When the supplier approves the refund request relevant tables are updated, cf. the Price refund confirmed processing in the Price refund table.
- Produces CID code
- This selection is suggested in the order options dialog box on the basis of the payee's supplier number, and determines whether Business NXT includes the CID code in vouchers produced on receipt of invoices. The CID code consists of supplier number and invoice number preceded by zeros and a Modulus 10 check digit. The number of digits in the supplier number and invoice number elements is determined by the CID cust./suppl. chars. and CID ref. no. digits fields under Company information. Other properties for the CID codes can be defined in the dialog box for the Payment processing field under Company information. If the CID codes are to be calculated differently for a supplier, you can add them to the vouchers before the batch is updated.
- Prepayment
- You can suspend an order from being processed by checking the Prepayment box. In order for the order to be processed, a payment must be entered against this order in the voucher entries.
- Do not copy from payment supplier
- When making payment to the supplier number of an order, the following
fields are called up in the Associate table:
- Payment terms sup.
- Payment method sup.
- Delivery terms sup.
- Payment supplier no.
- Currency no.
- Cost currency no.
- Justify exchange rate
Accounting
- Suggest VAT code
- The supplier's VAT code and Turnover class -derived from the Trade area- will be suggested when you enter a voucher.
- Suspended on voucher
- You will not be able to post the voucher lines directly on the supplier. You will receive the message "Supplier xxxxxxx is suspended from direct posting" in the status bar.
- Obligatory CID for defined voucher types
- Select this field if this supplier is to have a mandatory CID code on
the voucher line when you register voucher types with a corresponding selection in the
Voucher type processing/Obligatory CID from supplier field on the voucher line. When you register a voucher type by selecting the
Obligatory CID from supplier field under Voucher type processing
on the voucher line, Business NXT will check whether you have selected the Obligatory CID for defined voucher types field. If Obligatory CID for defined voucher types is selected, the CID code field in the voucher
line is marked with a red ? if the field is not filled in. You
will not be able to execute the processing Update batch for the voucher
if the CID code is
marked with a red ?. Note:This check is not present in the Receive invoice dialog box in the Order table, but the voucher will be given a red ? in the CID code field.
- Self-employed supplier
- When selected, supplier is flagged as a self-employed supplier (with no fixed place of business). This is used as a selection criteria for the self-employed supplier report.
- Author of intellectual property
- When selected, supplier is marked as a author of intellectual property. This is used as a selection criteria for the reporting of intellectual properties to Altinn.
- Combine incoming invoice lines
Payment suggestion
- Foreign payment
- If you are to make a payment to a foreign country, you select
Foreign payment.Note:For Swedish remittance; this setting should not be selected if the foreign supplier has a Swedish bankgirot account.
- No payment
- You can exempt a supplier from payment suggestions by selecting No payment.
- Intracompany payment
- When selected, payments to the supplier are marked as intracompany payments. Can be used if the bank offer lower or free charges for this kind of transactions. Used when sending payments through Visma.net AutoPay.
- Treat foreign payment as domestic
- This selection applies to electronic payment methods in Denmark to Nordea, where you can transfer payments from Denmark to Norway, Sweden, Finland, Germany, Great Britain and the USA, and they will be processed as domestic payments in each country. When you select this option for a supplier, regardless of whether it is a domestic/foreign payment, the payment transaction type will be changed to 43. For domestic it is changed from 14 to 43, and for foreign from 106 to 43. Z Data can process the transactions in a simple way.
- Use Postgiro for payments - Swedish
- This field is used by some EFT systems for Swedish payment transfers. Postgiro is also used with other formats, so you must leave this field unchecked if you are using bank formats other than Swedish.
- Tax department
- When selected, payments uploaded to Visma.net AutoPay for this supplier will be marked as payment of tax (will have "TAXS" in the <Purpose> tag in the VOP file).
Cost addition distribution
- From order line
- Amount
- Amount will be the basis of the cost addition distribution for a purchase order for this supplier. The value will be transferred to the Order options field in the Order table.
- Net weight
- Net weight will be the basis of the cost addition distribution for a purchase order for this supplier. The value will be transferred to the Order options field in the Order table.
- Gross weight
- Gross weight will be the basis of the cost addition distribution for a purchase order for this supplier. The value will be transferred to the Order options field in the Order table.
- Volume
- Volume will be the basis of the cost addition distribution for a purchase order for this supplier. The value will be transferred to the Order options field in the Order table.
- Quantity
- Quantity will be the basis of the cost addition distribution for a purchase order for this supplier. The value will be transferred to the Order options field in the Order table.
External processing
- Invoice matching against ordering
- All scanned invoices for this supplier must be matched against orders in the order system. This field has no function in Business NXT, but is used for integration with Visma Workflow.
- Created automatically
- This setting is automatically enabled when new supplier is created from Accounting document table. If enabled and Suspend flow on automatically created suppliers is also enabled in Accounting processing field in Company information table, batches created from Accounting document table will be set as Suspended in Batch table if any of the supplier have this setting.
- Is a template
- When selected, the associate will be displayed as a template in Visma Document Center.Note:This option is not copied when filling the Associate template field in the Associate table.
Order Match
- No automatic invoice receive if freight
- If enabled then the automatic invoice receive of an order matched invoice is not performed in case the incoming invoice contains at least one freight charge. This flag is checked by the order match processing only if it is simultaneously enabled the Order match automatic invoice receive flag from Order processing 2 field in Company information table.
- No automatic invoice receive if additional fees
- If enabled then the automatic invoice receive of an order matched invoice is not performed in case the incoming invoice contains a fee charge or rounding amount. This flag is checked by the order match processing only if it is simultaneously enabled the Order match automatic invoice receive flag from Order processing 2 field in Company information table.
- Do not run automatic order match
- This option is currently not in use.
- Order match on totals
- Enables automatic order matching on order header level for incoming supplier invoices. When enabled, invoices imported with a matching purchase order number are validated against the purchase order total net amounts and processed through the Order match on totals workflow.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Supplier options | Integer |
| SQL name | SupPref | The database field name. |
| API identifier | supplierPreferences1 | The API identifier used in GraphQL. |
| Number | 5734 |
Supplier options 2
Settings defining the behaviour of the supplier.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Supplier options 2 | Integer |
| SQL name | SupPre2 | The database field name. |
| API identifier | supplierPreferences2 | The API identifier used in GraphQL. |
| Number | 19605 |
Swift address 1
The SWIFT address for the supplier.
Normally you type the name of the bank in the Swift address 1 field and the rest of the address in the SWIFT address 2-4 fields.
- SWIFT
- SWIFT (Society for Worldwide Interbank Financial Telecommunication) acts as a register of addresses for the international banking network. It is used in connection with electronic funds transfer to identify the issuing bank of the payee's bank for foreign payments.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Address line | Text (60) |
| SQL name | SwftAd1 | The database field name. |
| API identifier | swiftAddress1 | The API identifier used in GraphQL. |
| Number | 4101 |
Swift address 2
The SWIFT address for the supplier.
Normally you type the name of the bank in the Swift address 1 field and the rest of the address in the SWIFT address 2-4 fields.
- SWIFT
- SWIFT (Society for Worldwide Interbank Financial Telecommunication) acts as a register of addresses for the international banking network. It is used in connection with electronic funds transfer to identify the issuing bank of the payee's bank for foreign payments.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Address line | Text (60) |
| SQL name | SwftAd2 | The database field name. |
| API identifier | swiftAddress2 | The API identifier used in GraphQL. |
| Number | 4102 |
Swift address 3
The SWIFT address for the supplier.
Normally you type the name of the bank in the Swift address 1 field and the rest of the address in the SWIFT address 2-4 fields.
- SWIFT
- SWIFT (Society for Worldwide Interbank Financial Telecommunication) acts as a register of addresses for the international banking network. It is used in connection with electronic funds transfer to identify the issuing bank of the payee's bank for foreign payments.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Address line | Text (60) |
| SQL name | SwftAd3 | The database field name. |
| API identifier | swiftAddress3 | The API identifier used in GraphQL. |
| Number | 4103 |
Swift address 4
The SWIFT address for the supplier.
Normally you type the name of the bank in the Swift address 1 field and the rest of the address in the SWIFT address 2-4 fields.
- SWIFT
- SWIFT (Society for Worldwide Interbank Financial Telecommunication) acts as a register of addresses for the international banking network. It is used in connection with electronic funds transfer to identify the issuing bank of the payee's bank for foreign payments.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Address line | Text (60) |
| SQL name | SwftAd4 | The database field name. |
| API identifier | swiftAddress4 | The API identifier used in GraphQL. |
| Number | 4104 |
Swift code
The SWIFT code for the supplier.
The SWIFT code (BIC code) is a unique code used on foreign payments to identify the bank.
The SWIFT code consists of 8-11 characters (such as "DNBANOKKXXX") and is made up of 4 parts; an abbreviation for the bank's name (4 characters), the ISO country code (2 characters), the city code (2 characters) and an optional branch code (3 characters, "XXX" = head office).
In addition you have the SWIFT address 1-4 fields.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Swift code | Text (11) |
| SQL name | SwftCd | The database field name. |
| API identifier | swiftCode | The API identifier used in GraphQL. |
| Number | 4100 |
Time schedule group no.
The time schedule group for the employee.
The time schedule group no is used in the time registration module to generate the employee's time schedule balance.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Time schedule group no. | Integer |
| SQL name | TSGrNo | The database field name. |
| API identifier | timeScheduleGroupNo | The API identifier used in GraphQL. |
| Number | 12366 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Time schedule group | TimeScheduleGroup |
|
Time Zone
The timezone used by external applications.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Time Zone | Integer |
| SQL name | TmZn | The database field name. |
| API identifier | timeZone | The API identifier used in GraphQL. |
| Number | 12223 |
TimeEase user
Visualises the User in Time Ease option under the Associate processing field. An x is shown, if the user is enabled for User in Time Ease.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Boolean | Integer |
| Memory field | Yes | The value in this field is only displayed in the program, it is not stored in the database. |
| API identifier | timeSystemUser | The API identifier used in GraphQL. |
| Number | 8481 |
Title
The professional title for a private individual.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Name | Text (80) |
| SQL name | Title | The database field name. |
| API identifier | title | The API identifier used in GraphQL. |
| Number | 4048 |
To date
You can use this field to state when a customer relationship ended or when an employee left the company.
The date is validated using the regional settings in Windows.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Date | Integer |
| SQL name | ToDt | The database field name. |
| API identifier | toDate | The API identifier used in GraphQL. |
| Number | 4125 |
Ton rate
The ton rate.
Ton rates are defined in the Transport agreement table. It contains four Ton rate fields.
- 1 - Ton rate 1
- 2 - Ton rate 2
- 3 - Ton rate 3
- 4 - Ton rate 4
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Ton rate | Integer |
| SQL name | TonRt | The database field name. |
| API identifier | tonRate | The API identifier used in GraphQL. |
| Number | 9123 |
Total disc. % cust.
This percentage value is suggested as the total discount on customer orders.
If you want to use additions instead of discounts then you have to enter a negative value into the field.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Percent | Decimal |
| SQL name | CustTotD | The database field name. |
| API identifier | totalDiscountPercentForCustomer | The API identifier used in GraphQL. |
| Number | 4078 |
Total disc. % sup.
This percentage value is suggested as the total discount on supplier orders.
If you want to use additions instead of discounts then you have to enter a negative value into the field.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Percent | Decimal |
| SQL name | SupTotD | The database field name. |
| API identifier | totalDiscountPercentForSupplier | The API identifier used in GraphQL. |
| Number | 4334 |
Total lead time
The total delivery time is calculated on the basis of the values in the Adm. time + Lead time + Transport time + Production time fields.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Days | Integer |
| Write Access | None | You are not allowed to modify the value in this field. |
| Memory field | Yes | The value in this field is only displayed in the program, it is not stored in the database. |
| API identifier | totalLeadTime | The API identifier used in GraphQL. |
| Number | 6326 |
Trade area
Defines the trade area for the associate. It is suggested in the orders, and specifies whether the customer/supplier is located within the country, in another EU country or outside the EU/abroad.
When this field has been filled in (with a value other than 0) this means that VAT will not be calculated on orders. 0 appears blank. The area code determines which of the account references for taxable, non-taxable domestic, EU and export/import are to be used in connection with sales, discounts, additions, special taxes and purchases in the Tax- and accounting inf. table, and invoice fees in the Currency table. If the product is not taxable and the associate is domestic, the account references for non-taxable are used regardless. This is an exception from the rule that the VAT follows the product. For example, the VAT rules of a country may require VAT to be invoiced to the customer if the product goes to another EU country but the invoice stays in the same country. If the Delivery associate number has Trade area 2, 4 or 5 in the Associate table, but Trade area 0 is within the trade area of the order, the system does not overwrite the value. Otherwise, the value in Delivery associate number overwrites the values from the Invoice customer number field.
The Order processing 2 field contains the parameter Do not overwrite trade area and EU VAT with local VAT, which you should use in combination with the Trade area and VAT codes from delivery associate number option. When you have set these parameters, Business NXT will calculate the VAT from the Delivery associate number when invoicing.
The area codes apply to both customers and suppliers, unless otherwise stated.
The area code forms the basis when Business NXT selects the turnover class of the vouchers.
- 0 - Taxable domestic according to VAT- and accounting inf./VAT code
- 1 - Non-taxable domestic
- 2 - Within other EU country
- only relevant if the company is located in an EU country
- 3 - Outside EU/Abroad
- applies to all other foreign associates
- 4 - Subsidiary in another EU country
- only relevant for customers, only relevant if the company is located in an EU country, treated in the same way as 2 in respect of account references
- 5 - Transfer between other EU countries
- only relevant for suppliers, only relevant if the company is located in an EU country, treated in the same way as 2 in respect of account references
- 6 - Consuming of products
- 7 - Reversed domestic tax
- 8 - Rent income voluntary
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Trade area | Integer |
| SQL name | ExVat | The database field name. |
| API identifier | tradeArea | The API identifier used in GraphQL. |
| Number | 4066 |
Transp. agr. no.
The supplier's transport agreement number.
The transport agreement number will be copied to the same field on the order lines.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Transp. agr. no. | Integer |
| SQL name | TspAgrNo | The database field name. |
| API identifier | transportAgreementNo | The API identifier used in GraphQL. |
| Number | 9064 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Transport agreement | TransportAgreement |
|
Transport time
The number of days it takes to transport the goods from the supplier.
The field will be suggested when you enter the supplier number in the Delivery alternative table and Normal supplier in the Stock balance table.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Days | Integer |
| SQL name | TanspTm | The database field name. |
| API identifier | transportTime | The API identifier used in GraphQL. |
| Number | 6325 |
Turnover
The annual turnover.
This is only used for information purposes.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Amount | Decimal |
| SQL name | Turn | The database field name. |
| API identifier | turnover | The API identifier used in GraphQL. |
| Number | 4111 |
User in Zpider
Visualises the User in Zpider option under the Associate processing field. An x is shown, if the user is enabled for User in Zpider.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Boolean | Integer |
| Memory field | Yes | The value in this field is only displayed in the program, it is not stored in the database. |
| API identifier | userInZpider | The API identifier used in GraphQL. |
| Number | 12850 |
User name
The user name which is associated with the associate.
The User table contains valid user names. You must be registered as an associate with the logged on user name in this field in order to be able to register appointments, create documents or integrate with Visma Document Center.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | User name | Text (24) |
| SQL name | Usr | The database field name. |
| API identifier | userName | The API identifier used in GraphQL. |
| Number | 4199 |
VAT code cust.
The VAT code for the customer.
If you have made the appropriate selection in the customer options dialog box, it will also be suggested when you enter a voucher. Any VAT code in the order head, or one that is overridden in the order lines, will take precedence over the VAT code in the VAT- and accounting information table, unless you have checked the Override order box there. You do not have to enter any VAT code for customers unless the same one is always used. For example in industries where the tax calculation is performed by customer rather than product. This is true, for example, of publishers, who must include VAT in the net amount for sales to booksellers regardless of whether the product is taxable or non-taxable, while sales to regular customers are only subject to VAT if the product is taxable according to the normal rules. For domestic customers that are non-taxable, you can choose to enter a VAT code without a VAT number (or using tax rate 0). You can always use 1 - Non-taxable domestic in the Trade area field to exempt domestic customers from tax calculations.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | VAT code | Integer |
| SQL name | CVatNo | The database field name. |
| API identifier | taxCodeForCustomer | The API identifier used in GraphQL. |
| Number | 4065 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| VAT code | TaxCodeForCustomer |
|
VAT code sup.
The VAT code for the supplier.
Suggested when you enter orders for the supplier (payee). If you have made the appropriate selection in the supplier preferences dialog box, it will also be suggested when you enter a voucher. Any VAT code in the order head or that has been overridden in the order lines, will take precedence over the VAT code in the VAT- and accounting information table, unless you have checked the Override order box there. You do not have to enter any VAT code for suppliers unless the same one is always used.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | VAT code | Integer |
| SQL name | SVatNo | The database field name. |
| API identifier | taxCodeForSupplier | The API identifier used in GraphQL. |
| Number | 4718 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| VAT code | TaxCodeForSupplier |
|
VAT reg. no.
VAT registration number for the company.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Organisation no. | Text (24) |
| SQL name | EUTaxNo | The database field name. |
| API identifier | euVatRegistrationNo | The API identifier used in GraphQL. |
| Number | 4492 |
VAT registered
Selected if the VAT registered check box in the dialog for the Associate processing field has been selected.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Boolean | Integer |
| Memory field | Yes | The value in this field is only displayed in the program, it is not stored in the database. |
| API identifier | vatRegistered | The API identifier used in GraphQL. |
| Number | 18397 |
Visit post code
The visiting post code.
When you enter a visiting postcode, the appropriate visiting postcode area is completed. If the postcode is not defined in the Postal address table, a warning is issued in the status bar.
If you enter a Post code that exists in the Postal address table, the Postal area field is filled in and the cursor jumps to the next field. If the Post code does not exist you will see a warning in the Status bar and the cursor will then stop in the Postal area field so you can type in the Postal area manually.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Post code | Text (40) |
| SQL name | ViPNo | The database field name. |
| API identifier | visitPostCode | The API identifier used in GraphQL. |
| Number | 10561 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Postal address | VisitPostalAddress |
|
Visit postal area
The visiting postal area.
When you enter a visiting postcode, the appropriate visiting postcode area is completed. If the postcode is not defined in the Postal address table, a warning is issued in the status bar.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Address line | Text (60) |
| SQL name | ViPArea | The database field name. |
| API identifier | visitPostalArea | The API identifier used in GraphQL. |
| Number | 10562 |
Warehouse no. cust.
The warehouse from where the products are to be taken from for a specific customer.
Suggested when you enter orders on the basis of the recipient for sales/hire/loan.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Warehouse no. | Integer |
| SQL name | CStc | The database field name. |
| API identifier | warehouseNoForCustomer | The API identifier used in GraphQL. |
| Number | 4072 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Warehouse | WarehouseForCustomer |
|
Warehouse no. sup.
The warehouse the products are to be delivered to.
Suggested when you enter orders on the basis of the supplier or recipient for purchases
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Warehouse no. | Integer |
| SQL name | SStc | The database field name. |
| API identifier | warehouseNoForSupplier | The API identifier used in GraphQL. |
| Number | 4372 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Warehouse | WarehouseForSupplier |
|
Web page 1
The address of a web page for the associate.
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 | IntAd1 | The database field name. |
| API identifier | webPage1 | The API identifier used in GraphQL. |
| Number | 6601 |
Web page 2
The address of a web page for the associate.
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 | IntAd2 | The database field name. |
| API identifier | webPage2 | The API identifier used in GraphQL. |
| Number | 6602 |
Your ref.
The customer's/supplier's reference.
The reference is suggested on orders for the customer/supplier.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Reference | Text (60) |
| SQL name | YrRef | The database field name. |
| API identifier | yourReference | The API identifier used in GraphQL. |
| Number | 6125 |
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. |