Company information
The Company information table contains information about the company and company-wide options.
| Property | Value | Description |
|---|---|---|
| Database | Company | This table is in the company databases. |
| SQL name | FrmData | The table name in the database. |
| API identifier | companyInformation | The API identifier used in GraphQL. |
| Table no. | 26 | The table number in the data model. |
The following fields exist in this table:
1. accounting month
If you have a financial year which does not follow the calendar year, you enter the first month of the financial year (1 -12) in this field.
When depreciating capital assets Business NXT will then be able to calculate the correct dates for depreciation based on the number of instances of depreciation per annum. Business NXT will also take this into account when dates are suggested in the Accounting period table using the + key (or the Edit/Suggest value menu item).
- 1 - January
- 2 - February
- 3 - March
- 4 - April
- 5 - May
- 6 - June
- 7 - July
- 8 - August
- 9 - September
- 10 - October
- 11 - November
- 12 - December
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Month | Integer |
| SQL name | FstAcMth | The database field name. |
| API identifier | firstAccountingMonthNo | The API identifier used in GraphQL. |
| Number | 5795 |
Account no. format
Display format for general ledger accounts.
If for example you have a five-digit account plan, you can format the presentation of account numbers for both screens and printouts. You then enter "#" which represents the digits, and you enter spaces, full stops or other characters between the digits. Then for example ### ## the account number with a space between the third and fourth digits is displayed.
This field replaces previous formatting, which is done in registry under the ACCOUNT_NO_FORMAT string.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | String of length 20 | Text (20) |
| SQL name | AcNoFmt | The database field name. |
| API identifier | accountNoFormat | The API identifier used in GraphQL. |
| Number | 14893 |
Accountant's e-mail address
The e-mail address of the accountant.
This is in addition to the E-mail address field, which is reserved for the e-mail address of the company.
| 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 | AcMailAd | The database field name. |
| API identifier | accountantsEmailAddress | The API identifier used in GraphQL. |
| Number | 14805 |
Accountant's name
The name of the accountant.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Name | Text (80) |
| SQL name | AcNm | The database field name. |
| API identifier | accountantsName | The API identifier used in GraphQL. |
| Number | 14806 |
Accounting cost
Definition for the accounting cost string used in electronic invoicing.
May contain text or macros to export data related to the specific order line, like product no, account, organisational unit. Used when sending purchase orders through AutoInvoice. See Extended mapping information for more information.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is 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 | 17742 |
Accounting instances
Determines when batches are to be produced.
- Accounting: Determines whether a batch shall be created or not for the processing described.
- Direct update: Determines whether the batch shall be directly updated or not. For processings where an approval dialog appears before the batch is created, this option will check the direct option in the approval dialog.
- No changes: Will prevent the user from unchecking the
direct update in an approval dialog.Note:Invoicing sales cash order cannot be excluded for legal reasonsNote:Cost on production when finishing will create posting on the Product in work account when finishing a order line on a production order with Transaction type = 5 - Further processing. This option is meant to be used together with the option Cost on production when approval which will reverse the posting on the Product in work account and create a posting on the Production warehouse account. These two options shall NOT be used together with the option Post temp. stock value on production which will create a preliminary posting when finishing the structure head on a production order, which will be reversed when performing invoice receival.
Logistics
- Invoicing sales/hire
- Vouchers will be created for invoicing.
- Invoicing sales cash order
- Vouchers will be created for invoicing of cash order.
- Post temp. stock value on sales
- Vouchers will be created for accounting temporary stock values on sales.
- Cost/stock/discard on hire
- Vouchers will be created for cost or stock discard on hire.
- Cost/stock/discard on loan
- Vouchers will be created for cost or stock discard on loan.
- Cost on adjustment/internal issue
- Vouchers will be created for cost on loss.
- Cost on further processing
- Vouchers will be created for cost on further processing.
- Invoice received
- Vouchers will be created
for invoice received.
If receipt of invoice is to be posted, a dialog box will appear in connection with the use of the Received invoice processing in the order head or when saving changes which include receipt of invoice. See the chapter on accounting in the system specification for logistics.
- Post temp. stock value on purchase
- Vouchers will be created for accounting temporary stock value on purchase.
- Cost on production when approval
- Vouchers will be created for cost on production when approving.
- Cost on production when finishing
- Vouchers will be created for cost on production when finishing.
- Post temp. stock value on production
- Vouchers will be created when finishing the structure head on a production order.
- Stock transfer
- Vouchers will be created for stock transfer.
- Correction stock balance
- Vouchers will be created for correcting stock balances.
- Automatic cost correction
- Vouchers will be created for automatic cost correction, under the condition that the option Invoice received has been selected.
- Internal invoicing
- Vouchers will be created for internal invoicing.
- Post temp. stock value
- Vouchers will be created for accounting temporary stock value when running the Post temporary stock value processing directly from the Product transaction table.
- Post costs
- Vouchers will be created for accounting costs when running the Post cost processing directly from the Product transaction table.
Finance
- Interest calculation
- Vouchers will be created for interest calculation.
- Reminder/interest fee
- Vouchers will be created for reminders and interest fee.
- Payment giro
- Vouchers will be created for payments.
- VAT control
- Vouchers will be created for tax settlement.
- OSS VAT control
- Vouchers will be created when printing a OSS VAT report.
- Activate capital asset
- Vouchers will be created for activating capital assets.
- Interest suggestion
- Vouchers will be created for interest suggestion.
- Accounting document
- If the Direct update checkbox for Accounting document is selected, batches will be updated automatically if they don't have errors. It is not possible to change the checkbox values for Accounting (always performed) and No changes.
Miscellaneous
- Direct update from Visma Business Services
- If selected, direct update will be the option used when calling from Visma Business Services.
- System admin. can change
- If selected, only the system administrator can update directly if the
No changes option is selected for the following instances -
even if the user has access to the Accounting:
- Invoicing sales/hire
- Invoicing sales cash order
- Interest calculation
- Reminder/interest fee
- Invoice received
- Payment giro
- VAT control
- Post costs
- Post temp. stock value
- Internal invoicing
- Activate capital asset
- Interest suggestion
- Stock consistency control on postings
- When the parameter is set, the table VAT and accounting group will be used to make sure there is consistency in posting of order lines where stock handling has been changed.
- Set value date on cost correction = invoice value date
- When set, cost correction will be posted with value date using the purchase invoice value date instead of the invoice date.
Post VAT
- Via VAT codes
- If selected, VAT amounts are posted via VAT codes when voucher lines
are produced in connection with invoicing and receipt of invoice.
The advantage of accounting via VAT codes is that sales and purchase transactions will contain complete information on which taxes have been calculated. Both gross amounts (amounts entered) and net amounts (amounts posted) will be calculated. It will be therefore be easier to produce informative reports.
VAT codes will be included even if the VAT rate is 0 (zero).
- Directly to VAT accounts
- If selected, VAT amounts are posted directly to VAT accounts when
voucher lines are produced in connection with invoicing and receipt of
invoice.Note:This parameter shall not be used if the company is subject to VAT that shall be posted on both debit and credit, e.g. purchase from the EU, purchase from countries outside EU and domestic purchase with reversed VAT.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Accounting instances | Integer |
| SQL name | Acc | The database field name. |
| API identifier | accountingInstances1 | The API identifier used in GraphQL. |
| Number | 6138 |
Accounting instances 2
Determines when batches are to be produced.
- Accounting: Determines whether a batch shall be created or not for the processing described.
- Direct update: Determines whether the batch shall be directly updated or not. For processings where an approval dialog appears before the batch is created, this option will check the direct option in the approval dialog.
- No changes: Will prevent the user from unchecking the
direct update in an approval dialog.Note:Invoicing sales cash order cannot be excluded for legal reasonsNote:Cost on production when finishing will create posting on the Product in work account when finishing a order line on a production order with Transaction type = 5 - Further processing. This option is meant to be used together with the option Cost on production when approval which will reverse the posting on the Product in work account and create a posting on the Production warehouse account. These two options shall NOT be used together with the option Post temp. stock value on production which will create a preliminary posting when finishing the structure head on a production order, which will be reversed when performing invoice receival.
Logistics
- Invoicing sales/hire
- Vouchers will be created for invoicing.
- Invoicing sales cash order
- Vouchers will be created for invoicing of cash order.
- Post temp. stock value on sales
- Vouchers will be created for accounting temporary stock values on sales.
- Cost/stock/discard on hire
- Vouchers will be created for cost or stock discard on hire.
- Cost/stock/discard on loan
- Vouchers will be created for cost or stock discard on loan.
- Cost on adjustment/internal issue
- Vouchers will be created for cost on loss.
- Cost on further processing
- Vouchers will be created for cost on further processing.
- Invoice received
- Vouchers will be created
for invoice received.
If receipt of invoice is to be posted, a dialog box will appear in connection with the use of the Received invoice processing in the order head or when saving changes which include receipt of invoice. See the chapter on accounting in the system specification for logistics.
- Post temp. stock value on purchase
- Vouchers will be created for accounting temporary stock value on purchase.
- Cost on production when approval
- Vouchers will be created for cost on production when approving.
- Cost on production when finishing
- Vouchers will be created for cost on production when finishing.
- Post temp. stock value on production
- Vouchers will be created when finishing the structure head on a production order.
- Stock transfer
- Vouchers will be created for stock transfer.
- Correction stock balance
- Vouchers will be created for correcting stock balances.
- Automatic cost correction
- Vouchers will be created for automatic cost correction, under the condition that the option Invoice received has been selected.
- Internal invoicing
- Vouchers will be created for internal invoicing.
- Post temp. stock value
- Vouchers will be created for accounting temporary stock value when running the Post temporary stock value processing directly from the Product transaction table.
- Post costs
- Vouchers will be created for accounting costs when running the Post cost processing directly from the Product transaction table.
Finance
- Interest calculation
- Vouchers will be created for interest calculation.
- Reminder/interest fee
- Vouchers will be created for reminders and interest fee.
- Payment giro
- Vouchers will be created for payments.
- VAT control
- Vouchers will be created for tax settlement.
- OSS VAT control
- Vouchers will be created when printing a OSS VAT report.
- Activate capital asset
- Vouchers will be created for activating capital assets.
- Interest suggestion
- Vouchers will be created for interest suggestion.
- Accounting document
- If the Direct update checkbox for Accounting document is selected, batches will be updated automatically if they don't have errors. It is not possible to change the checkbox values for Accounting (always performed) and No changes.
Miscellaneous
- Direct update from Visma Business Services
- If selected, direct update will be the option used when calling from Visma Business Services.
- System admin. can change
- If selected, only the system administrator can update directly if the
No changes option is selected for the following instances -
even if the user has access to the Accounting:
- Invoicing sales/hire
- Invoicing sales cash order
- Interest calculation
- Reminder/interest fee
- Invoice received
- Payment giro
- VAT control
- Post costs
- Post temp. stock value
- Internal invoicing
- Activate capital asset
- Interest suggestion
- Stock consistency control on postings
- When the parameter is set, the table VAT and accounting group will be used to make sure there is consistency in posting of order lines where stock handling has been changed.
- Set value date on cost correction = invoice value date
- When set, cost correction will be posted with value date using the purchase invoice value date instead of the invoice date.
Post VAT
- Via VAT codes
- If selected, VAT amounts are posted via VAT codes when voucher lines
are produced in connection with invoicing and receipt of invoice.
The advantage of accounting via VAT codes is that sales and purchase transactions will contain complete information on which taxes have been calculated. Both gross amounts (amounts entered) and net amounts (amounts posted) will be calculated. It will be therefore be easier to produce informative reports.
VAT codes will be included even if the VAT rate is 0 (zero).
- Directly to VAT accounts
- If selected, VAT amounts are posted directly to VAT accounts when
voucher lines are produced in connection with invoicing and receipt of
invoice.Note:This parameter shall not be used if the company is subject to VAT that shall be posted on both debit and credit, e.g. purchase from the EU, purchase from countries outside EU and domestic purchase with reversed VAT.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Accounting instances 2 | Integer |
| SQL name | Acc2 | The database field name. |
| API identifier | accountingInstances2 | The API identifier used in GraphQL. |
| Number | 16316 |
Accounting instances 3
Determines when batches are to be produced.
- Accounting: Determines whether a batch shall be created or not for the processing described.
- Direct update: Determines whether the batch shall be directly updated or not. For processings where an approval dialog appears before the batch is created, this option will check the direct option in the approval dialog.
- No changes: Will prevent the user from unchecking the
direct update in an approval dialog.Note:Invoicing sales cash order cannot be excluded for legal reasonsNote:Cost on production when finishing will create posting on the Product in work account when finishing a order line on a production order with Transaction type = 5 - Further processing. This option is meant to be used together with the option Cost on production when approval which will reverse the posting on the Product in work account and create a posting on the Production warehouse account. These two options shall NOT be used together with the option Post temp. stock value on production which will create a preliminary posting when finishing the structure head on a production order, which will be reversed when performing invoice receival.
Logistics
- Invoicing sales/hire
- Vouchers will be created for invoicing.
- Invoicing sales cash order
- Vouchers will be created for invoicing of cash order.
- Post temp. stock value on sales
- Vouchers will be created for accounting temporary stock values on sales.
- Cost/stock/discard on hire
- Vouchers will be created for cost or stock discard on hire.
- Cost/stock/discard on loan
- Vouchers will be created for cost or stock discard on loan.
- Cost on adjustment/internal issue
- Vouchers will be created for cost on loss.
- Cost on further processing
- Vouchers will be created for cost on further processing.
- Invoice received
- Vouchers will be created
for invoice received.
If receipt of invoice is to be posted, a dialog box will appear in connection with the use of the Received invoice processing in the order head or when saving changes which include receipt of invoice. See the chapter on accounting in the system specification for logistics.
- Post temp. stock value on purchase
- Vouchers will be created for accounting temporary stock value on purchase.
- Cost on production when approval
- Vouchers will be created for cost on production when approving.
- Cost on production when finishing
- Vouchers will be created for cost on production when finishing.
- Post temp. stock value on production
- Vouchers will be created when finishing the structure head on a production order.
- Stock transfer
- Vouchers will be created for stock transfer.
- Correction stock balance
- Vouchers will be created for correcting stock balances.
- Automatic cost correction
- Vouchers will be created for automatic cost correction, under the condition that the option Invoice received has been selected.
- Internal invoicing
- Vouchers will be created for internal invoicing.
- Post temp. stock value
- Vouchers will be created for accounting temporary stock value when running the Post temporary stock value processing directly from the Product transaction table.
- Post costs
- Vouchers will be created for accounting costs when running the Post cost processing directly from the Product transaction table.
Finance
- Interest calculation
- Vouchers will be created for interest calculation.
- Reminder/interest fee
- Vouchers will be created for reminders and interest fee.
- Payment giro
- Vouchers will be created for payments.
- VAT control
- Vouchers will be created for tax settlement.
- OSS VAT control
- Vouchers will be created when printing a OSS VAT report.
- Activate capital asset
- Vouchers will be created for activating capital assets.
- Interest suggestion
- Vouchers will be created for interest suggestion.
- Accounting document
- If the Direct update checkbox for Accounting document is selected, batches will be updated automatically if they don't have errors. It is not possible to change the checkbox values for Accounting (always performed) and No changes.
Miscellaneous
- Direct update from Visma Business Services
- If selected, direct update will be the option used when calling from Visma Business Services.
- System admin. can change
- If selected, only the system administrator can update directly if the
No changes option is selected for the following instances -
even if the user has access to the Accounting:
- Invoicing sales/hire
- Invoicing sales cash order
- Interest calculation
- Reminder/interest fee
- Invoice received
- Payment giro
- VAT control
- Post costs
- Post temp. stock value
- Internal invoicing
- Activate capital asset
- Interest suggestion
- Stock consistency control on postings
- When the parameter is set, the table VAT and accounting group will be used to make sure there is consistency in posting of order lines where stock handling has been changed.
- Set value date on cost correction = invoice value date
- When set, cost correction will be posted with value date using the purchase invoice value date instead of the invoice date.
Post VAT
- Via VAT codes
- If selected, VAT amounts are posted via VAT codes when voucher lines
are produced in connection with invoicing and receipt of invoice.
The advantage of accounting via VAT codes is that sales and purchase transactions will contain complete information on which taxes have been calculated. Both gross amounts (amounts entered) and net amounts (amounts posted) will be calculated. It will be therefore be easier to produce informative reports.
VAT codes will be included even if the VAT rate is 0 (zero).
- Directly to VAT accounts
- If selected, VAT amounts are posted directly to VAT accounts when
voucher lines are produced in connection with invoicing and receipt of
invoice.Note:This parameter shall not be used if the company is subject to VAT that shall be posted on both debit and credit, e.g. purchase from the EU, purchase from countries outside EU and domestic purchase with reversed VAT.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Accounting instances 3 | Integer |
| SQL name | Acc3 | The database field name. |
| API identifier | accountingInstances3 | The API identifier used in GraphQL. |
| Number | 16317 |
Accounting processing
Rules for accounting in the system.
Account no. control
- Use account series on customer numbers
- Account number series for customer numbers are checked during voucher registration. You must then also enter the series in the Account no. series table.
- Use account series on supplier numbers
- Account number series for supplier numbers are checked during voucher registration. You must then also enter the series in the Account no. series table.
- Use account series on capital assets no.
- Account number series for capital assets are checked during voucher registration. You must then also enter the series in the Account no. series table.
- Do not allow overlapping account series
- Account series will be monitored while entering them, to make sure they do not overlap. Business NXT tests for customer/supplier/general ledger. Capital asset, employee, and resource are tested separately.
Printouts
- Use original due date for interest calculation
- The original due date based on the terms of payment for the invoice are used to calculate interest. The customer then pays interest from the original due date, even if the due date has been moved.
- Customer account statement as form
- A separate form will be used for customer account statements. You must use form type 10.
- Override last reminder to printer
Database
- Show only periods with account balance
- Balance lines with 0 (zero) will not appear in the General ledger balance tables. If not selected, they will appear, but only on screen. They are not stored in the database.
- Free info 1 is a view
- The Free information 1 table is marked as a database view. This will ensure that registering a new customer/supplier number in the Associate table, a new account number in the General ledger account table or a new product number in the Product table will not try to update the Free information 1.
- Free info 2 is a view
- The Free information 2 table is marked as a database view. This will ensure that registering a new customer/supplier number in the Associate table, a new account number in the General ledger account table or a new product number in the Product table will not try to update the Free information 2.
- Free info 3 is a view
- The Free information 3 table is marked as a database view. This will ensure that registering a new customer/supplier number in the Associate table, a new account number in the General ledger account table or a new product number in the Product table will not try to update the Free information 3.
Entry rules
- Org unit from open entry
- The organisational units are imported from the open entry (the invoice transaction) to the counter entry (payment transaction) on the entries that are selected in the Payment reg. field from the Cross reference table. If you select the Payment reg. field for several entries, and they have different organisational units, respective organisational units will be blanked out. The Cross reference field on the voucher line is updated with Cross reference from the Cross reference table, when you select just one entry. If you select several entries the field will be blanked out, if the field can be used in such cases.
- Allow change of invoice no. on open entries
- The Invoice no. field in the Open customer entry and Open supplier entry tables are editable.
Voucher update
- Generate distribution lines on Cust/Supp. trans
- Cost distribution for customer and supplier transactions is performed in addition to general ledger and capital assets transactions.
- Check turnover class and area on voucher line
- The presence of turnover class and area on voucher lines with VAT code is checked during voucher updating. It is thus not possible to enter a VAT code on a voucher line without turnover class and area also being present in the VAT code.
- Debit/credit control within period and batch
- Debit/credit controls within the period and within the same batch will be performed. Any difference is displayed by means of an error message referring to period and differential amount.
- Write off rest amount instead of payment variance
- The value in the Outstanding amount field is used instead of Acc. w/off variance amount when you run the Write off payments processing.
- Write off negative rest amounts
- Write off of both positive and negative entries in the customer ledger is possible. There is a joint entry in the cross-account for all positive and negative write-offs.
- Run write off after voucher update
- The outstanding amount is written off when you update the batch.
- Write error log file on update
- The Update even on error check box is enabled. The error messages when updating batches are written in a log
file. The log file is located in the Programs Files directory under
\VISMA\Business\Log, with file name Batch-x-yyyymmdd-ddmm.
If not selected, the error messages are shown in a dialog box. The dialog box appears unless you have disabled it in BIG.
If you combine this option with the Update even on error option the batch will be updated, regardless of whether it contains errors or not. The Write error log file on update and Update even on error options can be used without BIG, but BIG allows you to disable the error message dialog box.
- Update even on error
- If the Write error log file on update is also selected, the batch is updated regardless of whether they contain errors or not.
- Control per voucher
- It will be checked that every single voucher is zero before updating a manually entered batch, and a message will be generated if a voucher is not zero. This and any subsequent batches in the run will then remain, not updated. The batches can then be corrected and the update is run once more. This process requires that all voucher lines with the same voucher number arrive together.
- Caching on batch validation
- The customer, supplier and organisation unit records will be cached
when validating and updating batches. If you have large batches and few customers,
suppliers and organisation units this will improve the performance.
However, if you have a large number of customers, suppliers or organisation units you should not select this check box.
- Suspend flow on automatically created suppliers
- When enabled, batches created from Accounting document table are set as suspended in Batch table if any of the suppliers in the batch have the setting Created automatically enabled in Supplier options field.
- Check if supplier is VAT-registered
- When enabled, the validation will be executed in the Update batch processing.
The purpose of this validation is to avoid posting of supplier invoices including VAT if the supplier is not in the VAT register. The validation will check if the option VAT registered is set for the supplier in the Associate processing dialog. Only when that option is enabled it will be possible to post vouchers with a VAT code having VAT rate more than 0.
The validation will only be executed on voucher lines having Debit account type or Credit account type = 2 - Supplier.
- Always inherit voucher no./type on accrual lines
- When enabled, no validation will be done on the Period voucher series field in Company information table, and the Voucher no., Voucher type and Text will be coming from the original voucher. If the setting if OFF and Period voucher series is set in Company information, that one is used when creating the accrual lines, as per now.
- Postpone updating of accounting balances
- When enabled, balances will not be updated while running the Update batch processing in the Batch table. You can update the excluded balances separately by running the Update accounting balances processing in the Company information afterwards.
- Always split accrued amount in intended number of fractions
- When enabled, the accrual accounting is split according to the originally intended number of postings. This setting can be used when updating vouchers where the Accrual accounting start year/period is before the suspension date.
- Automatically move the value date to an open period
- When this feature is enabled, the Value date of applicable
documents is automatically moved to the first open accounting period. This occurs
during the Update batch or Update supplier transactions
processing. This automation applies to incoming documents with the origins:
- 42 - Accounting document
- 45 - Split batch, supplier transactions
- 46 - Split batch, cost transactions
Currency
- Fixed "Currency 2"
- The Currency no. 2 field cannot be overridden anywhere other than in the Company information table. If not selected, you can override the Currency no. 2 field in the Associate, General ledger account, Capital asset, Organisational unit 1-Organisational unit 12, Batch and Voucher tables. It is not possible to change the value in the Currency no. 2 field in the Updated batch and Updated voucher tables. If the access group for the user has functional access to Change Currency 2 on transactions, you can also change the Currency no. 2 field in the Customer transaction, Supplier transaction, General ledger transaction, Open customer entry and Open supplier entry tables.
- Fixed "Currency rate 2"
- The value in the Exchange rate 2 field cannot be overridden in the General ledger account, Capital asset and Voucher tables. It is not possible to change the value in the Exchange rate 2 field in the Updated voucher table. If the access group for the user has functional access to Change Currency 2 on transactions, the field can also be changed in the Customer transaction, Supplier transaction, General ledger transaction, Open customer entry and Open supplier entry tables.
- Calculate "Amount in currency 2" from "Currency amount"
- The Amount in currency 2 field is calculated on the basis of the Amount in currency field. You cannot change the Exchange rate 2 field in the Open customer entry, Open supplier entry, Customer transaction, Supplier transaction and Capital asset transaction tables if the Amount (Posted amount in General ledger transaction table) field is 0.00. If this option is selected, the Exchange rate 2 field cannot be edited if Amount in currency is 0.00. This prevents you from accidentally changing the Currency no. 2 field when the basis for the calculation for Amount in currency 2 is 0.00. Correction transactions for only Amount in currency 2 will then also be changed and it will not be possible to get the original value back.
- Mandatory currency 2 when updating vouchers
- The Currency no. 2, Exchange rate 2 and Amount in currency 2 fields must have a value to have the voucher be updated.
Client interest
- Set entry free of interest on suspended cases
- The transactions for cases that are suspended are set to no interest when posting client interest.
- Post client interest by client voucher
- The client bank account is assigned each transaction and not an accumulated amount for each account/currency occurrence. This can be used to post all organisational units from the case to the cross-account. The option must be selected if posting as in previous versions is wanted.
- Split GL transactions when booking client interest
- General ledger, cross-client and cross-account are split into more
detail and processed differently for each posting type.
- The general ledger entry for banks is split into General ledger account, Case number and Client management, and corresponds to Client interest transactions.
- If you use Cross-client, this is split into Cross-client and Client management.
- Cross-account for cross-client is split into Cross-account, Cross-client and Client management.
Payment
- Allow negative payments
- Amounts with a negative sign in front of them will also be processed.
This option is also present under EFT processing field in the Bank partner table. By
using the selection in EFT processing field in the Bank partner table, you
can set different processing for each bank partner.Note:For negative payments you are meant to transfer larger amounts of credit notes than invoices. This is selected when it is permitted to send this to the bank for monitoring, so that with the next invoice the bank reduces the payment amount with the remaining credit note value. This is only used when sending payments to Swedish banks.
- No debit balance when creating payments
- It is checked that the payment does not create a debit balance for a supplier. The transfer of transactions to suggested payments that create a debit balance for the supplier is not accepted. A check is made against payment rows with Paym. line status1 - Estimate, 2 - Transferred, 3 - Receipt, 5 - Settled and the closing balance for the supplier. Payment transactions that have not yet been posted are also processed. A check is made against the balance for the supplier in the Supplier balance table.
- Use payment terms on credit notes
- Payment terms on credit notes will be calculated.Note:The Use payment terms on credit notes and No estimated pay date on credit notes options are mutually exclusive, which means that you can only use one of them at a time.
- No estimated pay date on credit notes
- Entries with credit notes will not be given a payment date.Note:The Use payment terms on credit notes and No estimated pay date on credit notes options are mutually exclusive, which means that you can only use one of them at a time.
- Set debt collection flag after last letter
- The entries that you have run that last reminder for are sent to debt collection.
- Only transactions due for debt collection
- Only the positive transactions that have the same number in the
No. of reminders sent field in the Customer transaction
table and the Max. no. of reminders field in the Associate table are
sent to debt collection. Other payments for the customer are not transferred to debt
collection. If the Only transactions due for debt collection option is selected, the After last reminder field in the Country table has no
function, because no more reminders will be sent after the first one reaches the
maximum number of reminders.
If not selected, negative transactions (credit notes and payments) which have not been reminded and which have the value Added during debt collection in the Trans. status field are transferred to the change list for debt collection. These entries can be exempted from the change list by selecting 4 - No debt collection in the Exempt field in voucher registration. The entries will then be transferred to Customer transaction table with the value 2 - Exempt from debt recovery in the No reminders field. You can also change the value in the No reminders field in the Customer transaction and Open customer entry tables before you send the change file for debt collection.
Capital assets
- No deprec. < 1/2 month
- Depreciation will not be calculated for less than half a month, i.e. when purchasing a capital asset on or after the 16th of the month.
- Depreciate on specified date
- Depreciation will be performed on the date specified in the
depreciation dialog box (i.e. running the Depreciation
processing in the Capital asset table),
instead of on the calculated dates.Note:This option shall be used ONLY if the accounting periods defined in the Accounting period table do not last from the first to the last date in the months (=calendar months). E.g. when following British accounting rules, that uses four-week accounting periods.Tip:Write-off with four-week periods will be correct if you create 13 periods for each accounting year and you have selected this option.
Order
- Mandatory invoice no./date in dialog
- The OK button in the Received invoice processing dialog box in the Order table will not be available if the Invoice no. and Invoice date fields for incoming invoices have not been filled out. If the Invoice no. and Invoice date fields are not filled in when the Received invoice processing is run, the Invoice date field for the product transactions is updated with the current date, which cannot be used for anything. If you then manually correct the Invoice no. and Voucher date fields in the automatically generated batch, there will be a difference between the accounts and stock.
- Set credit suspension on open customer orders?
- The entry of additional order lines and printing of pick lists for already entered orders for customers whose credit has been suspended will be stopped. In addition to this option, you must also set Credit suspension - On picking to Block in the dialog box for the Credit control field. If you remove the credit suspension for the customer in the Associate table, the credit suspension on all orders entered for the customer will be removed.
- Post 0-amount invoices on vouchers
- A ledger transaction will be created during invoicing, even if the amount on the invoice is 0 (zero). The voucher line created at 0 (zero) invoicing automatically has the Accept transactions with amount 0 option in the Trans. status field selected. If you have selected the Voucher must have amount field in the Company information table, and you still want to post an invoice with a 0 (zero) amount, you can manually check the Accept transactions with amount 0 field in the voucher line. This selection overrides the selection in the Voucher must have amount field by updating vouchers with customer ledger transactions with a value of 0. If the override is to work on manually entered supplier ledger transactions, Accept transactions with amount 0 in the Trans. status field on the voucher line must be selected. On batches with origin code 30 - Currency correction no validation check is made whether the amount in currency is filled in, even if the currency number is specified.
- Order h. info. to d/c ledger
- The organisational units in the Order table will be included in voucher lines which produced for customers and suppliers. The general ledger entries for profit accounts (sales and product costs) are, nevertheless, split for all organisational units involved, whether they come from the Order, Product or the VAT- and accounting information table or are overridden in the order lines.
- GL trans. per invoice (Recommended)
- Note:Separate general ledger transactions will be produced per invoice instead of accumulating them for all invoices which are posted at the same time, and give all voucher lines for an invoice the same voucher number (i.e. the voucher lines with general ledger entries for an invoice are given the same voucher number as the voucher line with accounts receivable and payable entries). This applies to both incoming and outgoing invoices. The order number, customer number/supplier number, employee number and invoice number are included in general ledger transactions for sales/purchases.To meet requirements for SAF-T reporting, this option must always be ticked. When upgrading from versions older than 15.10, this option will be ticked automatically during the upgrade.
If not selected, general ledger entries in the batch will be given the next free voucher number (and voucher type) from the voucher and document series for sales or product purchases. If you select the GL trans. per invoice (Recommended) option and run the Post cost processing in the Product transaction table, the voucher lines are split per invoice number.
- GL trans. per order, when posting from product trans.
- General ledger transactions created during accumulation of cost from product transaction are grouped per order number.
- Sales org. units as stock responsible
- Product cost, freight and duty will be credited to the selling
organisational units in the VAT- and accounting information and the corresponding fields in the Order and Order line tables to
show that the selling organisational units are also supplying. If not selected, the
organisational units specified as suppliers in the VAT- and accounting information will be used.
Which organisational units posting of sales, discounts, additions, debit product cost, freight and duty are performed to is determined by the fields for the selling organisational units in the VAT- and accounting information table and the corresponding fields in the Order and Order line tables.
- Sup. as credit cost
- When posting a product cost, the supplier will be used as the
cross-account (credit account number). Also, a voucher line will be produced for each
order number (except for batch invoices). Supplier numbers are used in order of
priority:
- Payment supplier no. in the order line,
- Payment supplier no. in the order head,
- Supplier number in the order line and
- Supplier number in the order head.
- Due date based on finishing
- The Due date in Order document will be calculated on the basis of the finishing date instead of the invoice date.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Accounting processing | Integer |
| SQL name | AccPro | The database field name. |
| API identifier | accountingProcessing1 | The API identifier used in GraphQL. |
| Number | 8602 |
Accounting processing 2
Rules for accounting in the system.
Account no. control
- Use account series on customer numbers
- Account number series for customer numbers are checked during voucher registration. You must then also enter the series in the Account no. series table.
- Use account series on supplier numbers
- Account number series for supplier numbers are checked during voucher registration. You must then also enter the series in the Account no. series table.
- Use account series on capital assets no.
- Account number series for capital assets are checked during voucher registration. You must then also enter the series in the Account no. series table.
- Do not allow overlapping account series
- Account series will be monitored while entering them, to make sure they do not overlap. Business NXT tests for customer/supplier/general ledger. Capital asset, employee, and resource are tested separately.
Printouts
- Use original due date for interest calculation
- The original due date based on the terms of payment for the invoice are used to calculate interest. The customer then pays interest from the original due date, even if the due date has been moved.
- Customer account statement as form
- A separate form will be used for customer account statements. You must use form type 10.
- Override last reminder to printer
Database
- Show only periods with account balance
- Balance lines with 0 (zero) will not appear in the General ledger balance tables. If not selected, they will appear, but only on screen. They are not stored in the database.
- Free info 1 is a view
- The Free information 1 table is marked as a database view. This will ensure that registering a new customer/supplier number in the Associate table, a new account number in the General ledger account table or a new product number in the Product table will not try to update the Free information 1.
- Free info 2 is a view
- The Free information 2 table is marked as a database view. This will ensure that registering a new customer/supplier number in the Associate table, a new account number in the General ledger account table or a new product number in the Product table will not try to update the Free information 2.
- Free info 3 is a view
- The Free information 3 table is marked as a database view. This will ensure that registering a new customer/supplier number in the Associate table, a new account number in the General ledger account table or a new product number in the Product table will not try to update the Free information 3.
Entry rules
- Org unit from open entry
- The organisational units are imported from the open entry (the invoice transaction) to the counter entry (payment transaction) on the entries that are selected in the Payment reg. field from the Cross reference table. If you select the Payment reg. field for several entries, and they have different organisational units, respective organisational units will be blanked out. The Cross reference field on the voucher line is updated with Cross reference from the Cross reference table, when you select just one entry. If you select several entries the field will be blanked out, if the field can be used in such cases.
- Allow change of invoice no. on open entries
- The Invoice no. field in the Open customer entry and Open supplier entry tables are editable.
Voucher update
- Generate distribution lines on Cust/Supp. trans
- Cost distribution for customer and supplier transactions is performed in addition to general ledger and capital assets transactions.
- Check turnover class and area on voucher line
- The presence of turnover class and area on voucher lines with VAT code is checked during voucher updating. It is thus not possible to enter a VAT code on a voucher line without turnover class and area also being present in the VAT code.
- Debit/credit control within period and batch
- Debit/credit controls within the period and within the same batch will be performed. Any difference is displayed by means of an error message referring to period and differential amount.
- Write off rest amount instead of payment variance
- The value in the Outstanding amount field is used instead of Acc. w/off variance amount when you run the Write off payments processing.
- Write off negative rest amounts
- Write off of both positive and negative entries in the customer ledger is possible. There is a joint entry in the cross-account for all positive and negative write-offs.
- Run write off after voucher update
- The outstanding amount is written off when you update the batch.
- Write error log file on update
- The Update even on error check box is enabled. The error messages when updating batches are written in a log
file. The log file is located in the Programs Files directory under
\VISMA\Business\Log, with file name Batch-x-yyyymmdd-ddmm.
If not selected, the error messages are shown in a dialog box. The dialog box appears unless you have disabled it in BIG.
If you combine this option with the Update even on error option the batch will be updated, regardless of whether it contains errors or not. The Write error log file on update and Update even on error options can be used without BIG, but BIG allows you to disable the error message dialog box.
- Update even on error
- If the Write error log file on update is also selected, the batch is updated regardless of whether they contain errors or not.
- Control per voucher
- It will be checked that every single voucher is zero before updating a manually entered batch, and a message will be generated if a voucher is not zero. This and any subsequent batches in the run will then remain, not updated. The batches can then be corrected and the update is run once more. This process requires that all voucher lines with the same voucher number arrive together.
- Caching on batch validation
- The customer, supplier and organisation unit records will be cached
when validating and updating batches. If you have large batches and few customers,
suppliers and organisation units this will improve the performance.
However, if you have a large number of customers, suppliers or organisation units you should not select this check box.
- Suspend flow on automatically created suppliers
- When enabled, batches created from Accounting document table are set as suspended in Batch table if any of the suppliers in the batch have the setting Created automatically enabled in Supplier options field.
- Check if supplier is VAT-registered
- When enabled, the validation will be executed in the Update batch processing.
The purpose of this validation is to avoid posting of supplier invoices including VAT if the supplier is not in the VAT register. The validation will check if the option VAT registered is set for the supplier in the Associate processing dialog. Only when that option is enabled it will be possible to post vouchers with a VAT code having VAT rate more than 0.
The validation will only be executed on voucher lines having Debit account type or Credit account type = 2 - Supplier.
- Always inherit voucher no./type on accrual lines
- When enabled, no validation will be done on the Period voucher series field in Company information table, and the Voucher no., Voucher type and Text will be coming from the original voucher. If the setting if OFF and Period voucher series is set in Company information, that one is used when creating the accrual lines, as per now.
- Postpone updating of accounting balances
- When enabled, balances will not be updated while running the Update batch processing in the Batch table. You can update the excluded balances separately by running the Update accounting balances processing in the Company information afterwards.
- Always split accrued amount in intended number of fractions
- When enabled, the accrual accounting is split according to the originally intended number of postings. This setting can be used when updating vouchers where the Accrual accounting start year/period is before the suspension date.
- Automatically move the value date to an open period
- When this feature is enabled, the Value date of applicable
documents is automatically moved to the first open accounting period. This occurs
during the Update batch or Update supplier transactions
processing. This automation applies to incoming documents with the origins:
- 42 - Accounting document
- 45 - Split batch, supplier transactions
- 46 - Split batch, cost transactions
Currency
- Fixed "Currency 2"
- The Currency no. 2 field cannot be overridden anywhere other than in the Company information table. If not selected, you can override the Currency no. 2 field in the Associate, General ledger account, Capital asset, Organisational unit 1-Organisational unit 12, Batch and Voucher tables. It is not possible to change the value in the Currency no. 2 field in the Updated batch and Updated voucher tables. If the access group for the user has functional access to Change Currency 2 on transactions, you can also change the Currency no. 2 field in the Customer transaction, Supplier transaction, General ledger transaction, Open customer entry and Open supplier entry tables.
- Fixed "Currency rate 2"
- The value in the Exchange rate 2 field cannot be overridden in the General ledger account, Capital asset and Voucher tables. It is not possible to change the value in the Exchange rate 2 field in the Updated voucher table. If the access group for the user has functional access to Change Currency 2 on transactions, the field can also be changed in the Customer transaction, Supplier transaction, General ledger transaction, Open customer entry and Open supplier entry tables.
- Calculate "Amount in currency 2" from "Currency amount"
- The Amount in currency 2 field is calculated on the basis of the Amount in currency field. You cannot change the Exchange rate 2 field in the Open customer entry, Open supplier entry, Customer transaction, Supplier transaction and Capital asset transaction tables if the Amount (Posted amount in General ledger transaction table) field is 0.00. If this option is selected, the Exchange rate 2 field cannot be edited if Amount in currency is 0.00. This prevents you from accidentally changing the Currency no. 2 field when the basis for the calculation for Amount in currency 2 is 0.00. Correction transactions for only Amount in currency 2 will then also be changed and it will not be possible to get the original value back.
- Mandatory currency 2 when updating vouchers
- The Currency no. 2, Exchange rate 2 and Amount in currency 2 fields must have a value to have the voucher be updated.
Client interest
- Set entry free of interest on suspended cases
- The transactions for cases that are suspended are set to no interest when posting client interest.
- Post client interest by client voucher
- The client bank account is assigned each transaction and not an accumulated amount for each account/currency occurrence. This can be used to post all organisational units from the case to the cross-account. The option must be selected if posting as in previous versions is wanted.
- Split GL transactions when booking client interest
- General ledger, cross-client and cross-account are split into more
detail and processed differently for each posting type.
- The general ledger entry for banks is split into General ledger account, Case number and Client management, and corresponds to Client interest transactions.
- If you use Cross-client, this is split into Cross-client and Client management.
- Cross-account for cross-client is split into Cross-account, Cross-client and Client management.
Payment
- Allow negative payments
- Amounts with a negative sign in front of them will also be processed.
This option is also present under EFT processing field in the Bank partner table. By
using the selection in EFT processing field in the Bank partner table, you
can set different processing for each bank partner.Note:For negative payments you are meant to transfer larger amounts of credit notes than invoices. This is selected when it is permitted to send this to the bank for monitoring, so that with the next invoice the bank reduces the payment amount with the remaining credit note value. This is only used when sending payments to Swedish banks.
- No debit balance when creating payments
- It is checked that the payment does not create a debit balance for a supplier. The transfer of transactions to suggested payments that create a debit balance for the supplier is not accepted. A check is made against payment rows with Paym. line status1 - Estimate, 2 - Transferred, 3 - Receipt, 5 - Settled and the closing balance for the supplier. Payment transactions that have not yet been posted are also processed. A check is made against the balance for the supplier in the Supplier balance table.
- Use payment terms on credit notes
- Payment terms on credit notes will be calculated.Note:The Use payment terms on credit notes and No estimated pay date on credit notes options are mutually exclusive, which means that you can only use one of them at a time.
- No estimated pay date on credit notes
- Entries with credit notes will not be given a payment date.Note:The Use payment terms on credit notes and No estimated pay date on credit notes options are mutually exclusive, which means that you can only use one of them at a time.
- Set debt collection flag after last letter
- The entries that you have run that last reminder for are sent to debt collection.
- Only transactions due for debt collection
- Only the positive transactions that have the same number in the
No. of reminders sent field in the Customer transaction
table and the Max. no. of reminders field in the Associate table are
sent to debt collection. Other payments for the customer are not transferred to debt
collection. If the Only transactions due for debt collection option is selected, the After last reminder field in the Country table has no
function, because no more reminders will be sent after the first one reaches the
maximum number of reminders.
If not selected, negative transactions (credit notes and payments) which have not been reminded and which have the value Added during debt collection in the Trans. status field are transferred to the change list for debt collection. These entries can be exempted from the change list by selecting 4 - No debt collection in the Exempt field in voucher registration. The entries will then be transferred to Customer transaction table with the value 2 - Exempt from debt recovery in the No reminders field. You can also change the value in the No reminders field in the Customer transaction and Open customer entry tables before you send the change file for debt collection.
Capital assets
- No deprec. < 1/2 month
- Depreciation will not be calculated for less than half a month, i.e. when purchasing a capital asset on or after the 16th of the month.
- Depreciate on specified date
- Depreciation will be performed on the date specified in the
depreciation dialog box (i.e. running the Depreciation
processing in the Capital asset table),
instead of on the calculated dates.Note:This option shall be used ONLY if the accounting periods defined in the Accounting period table do not last from the first to the last date in the months (=calendar months). E.g. when following British accounting rules, that uses four-week accounting periods.Tip:Write-off with four-week periods will be correct if you create 13 periods for each accounting year and you have selected this option.
Order
- Mandatory invoice no./date in dialog
- The OK button in the Received invoice processing dialog box in the Order table will not be available if the Invoice no. and Invoice date fields for incoming invoices have not been filled out. If the Invoice no. and Invoice date fields are not filled in when the Received invoice processing is run, the Invoice date field for the product transactions is updated with the current date, which cannot be used for anything. If you then manually correct the Invoice no. and Voucher date fields in the automatically generated batch, there will be a difference between the accounts and stock.
- Set credit suspension on open customer orders?
- The entry of additional order lines and printing of pick lists for already entered orders for customers whose credit has been suspended will be stopped. In addition to this option, you must also set Credit suspension - On picking to Block in the dialog box for the Credit control field. If you remove the credit suspension for the customer in the Associate table, the credit suspension on all orders entered for the customer will be removed.
- Post 0-amount invoices on vouchers
- A ledger transaction will be created during invoicing, even if the amount on the invoice is 0 (zero). The voucher line created at 0 (zero) invoicing automatically has the Accept transactions with amount 0 option in the Trans. status field selected. If you have selected the Voucher must have amount field in the Company information table, and you still want to post an invoice with a 0 (zero) amount, you can manually check the Accept transactions with amount 0 field in the voucher line. This selection overrides the selection in the Voucher must have amount field by updating vouchers with customer ledger transactions with a value of 0. If the override is to work on manually entered supplier ledger transactions, Accept transactions with amount 0 in the Trans. status field on the voucher line must be selected. On batches with origin code 30 - Currency correction no validation check is made whether the amount in currency is filled in, even if the currency number is specified.
- Order h. info. to d/c ledger
- The organisational units in the Order table will be included in voucher lines which produced for customers and suppliers. The general ledger entries for profit accounts (sales and product costs) are, nevertheless, split for all organisational units involved, whether they come from the Order, Product or the VAT- and accounting information table or are overridden in the order lines.
- GL trans. per invoice (Recommended)
- Note:Separate general ledger transactions will be produced per invoice instead of accumulating them for all invoices which are posted at the same time, and give all voucher lines for an invoice the same voucher number (i.e. the voucher lines with general ledger entries for an invoice are given the same voucher number as the voucher line with accounts receivable and payable entries). This applies to both incoming and outgoing invoices. The order number, customer number/supplier number, employee number and invoice number are included in general ledger transactions for sales/purchases.To meet requirements for SAF-T reporting, this option must always be ticked. When upgrading from versions older than 15.10, this option will be ticked automatically during the upgrade.
If not selected, general ledger entries in the batch will be given the next free voucher number (and voucher type) from the voucher and document series for sales or product purchases. If you select the GL trans. per invoice (Recommended) option and run the Post cost processing in the Product transaction table, the voucher lines are split per invoice number.
- GL trans. per order, when posting from product trans.
- General ledger transactions created during accumulation of cost from product transaction are grouped per order number.
- Sales org. units as stock responsible
- Product cost, freight and duty will be credited to the selling
organisational units in the VAT- and accounting information and the corresponding fields in the Order and Order line tables to
show that the selling organisational units are also supplying. If not selected, the
organisational units specified as suppliers in the VAT- and accounting information will be used.
Which organisational units posting of sales, discounts, additions, debit product cost, freight and duty are performed to is determined by the fields for the selling organisational units in the VAT- and accounting information table and the corresponding fields in the Order and Order line tables.
- Sup. as credit cost
- When posting a product cost, the supplier will be used as the
cross-account (credit account number). Also, a voucher line will be produced for each
order number (except for batch invoices). Supplier numbers are used in order of
priority:
- Payment supplier no. in the order line,
- Payment supplier no. in the order head,
- Supplier number in the order line and
- Supplier number in the order head.
- Due date based on finishing
- The Due date in Order document will be calculated on the basis of the finishing date instead of the invoice date.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Accounting processing 2 | Integer |
| SQL name | AccPro2 | The database field name. |
| API identifier | accountingProcessing2 | The API identifier used in GraphQL. |
| Number | 12931 |
Activ. Cap. A. Series
The Voucher series to be used for activation of capital assets from orders.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | ActVoSr | The database field name. |
| API identifier | activatingCapitalAssetVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 10983 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | ActivatingCapitalAssetSeries |
|
Activity order type
The Order type is to be used when orders are generated on the basis of appointments using the processing in the Appointment table for setting up orders.
If the field is not filled in, the orders are given order type 1 - Normal order.
You can change both transaction type and order type for an order which has already been entered. Business NXT will then reverse the processing of the old transaction or order type to the extent necessary in relation to the new one.
You can combine the transaction type with one of eight different order types:
Business NXT suggests order type 1 - Normal order in the Order type field in the Order head page element when entering sales orders, loan/hire orders and purchase orders. Orders generated from the Appointment table are also allocated this order type, although you can change this in the Company information table.
When you invoice direct and cash orders and save realised orders, Business NXT reserves everything you ask for, even if it is not available. If necessary, shipments are produced with negative availability.
- 1 - Normal order
- You use this for agreed or planned future goods out/goods received. You can part-deliver an order. You must finish a Normal order before you can realise it. Orders generated from the Appointment table are given this order type, but you can change this in the Company information table. This is the only order type for which you can print an order confirmation, pick list, packing slip and consignment note.
- 2 - Direct order
- You can use direct order if you want to enter the invoicing details
directly. You cannot print a pick list for this order type. Business NXT can reserve more than what is available when entering direct orders. Note:If you do not have enough products in stock for a "Direct order" that is to be invoiced, a separate shipment is created for the negative quantity.This applies even if you have not selected the Add shipments with negative availability field, which you can find under the Processing/Processing method/Warehouse menu item in the products or the order lines. You cannot part-deliver a direct order, as it is finished when the invoice is printed.
- 3 - Cash order
- A cash order is the same as a direct order, but the invoice printout
is launched when you save the order. When an invoice is printed for a cash order, the
current date is used as the order date when VAT is calculated. When you save a cash
order a dialog box appears containing payment information. This contains information
on the order amount and a field in which you can key in the amount received. You can
see the difference in the Outstanding field. The dialog box also contains a field in
which you enter the method of payment. The accounts are updated directly via a batch
per cash order. If you do not have enough products in stock for a "Cash order" that is
to be invoiced, a separate shipment is created for the negative quantity. Note:Credit note on cash order is allowed, if user has function access to "Allow credit note on cash order".
- 4 - Realised order
- This order type is realised when saved, i.e. stock and statistics are
updated immediately. Note:You can use this order type when no order documents are used, e.g. in the event of adjustments.We recommend that this order type is not used together with transaction type 1 - Sales, as you are not able to print out or transfer to accounts.
- 5 - Quotation/Inquiry
- You can print this order type as a quotation or inquiry, but no processing is involved. If the quotation is accepted you must change the order type to 1 - Normal order, 2 - Direct order or 3 - Cash order for the order to be processed.
- 6 - Unprocessed order
- This order type corresponds to the quotation order, although you cannot print it out as a quotation. The order does not generate any processing, and you must change it to another order type before you can process it. An unprocessed order is useful for imported orders. When the import is complete you can change the order type so that it can be processed.
- 7 - Advance order
- An advance order uses the same processing method as a normal order, although Business NXT does not check stock availability during order entry or whether the credit limit has been/will be exceeded.
- 8 - Budget order
- If you select this order type it means that the order lines will not be processed, in the same way as for Unprocessed orders.
- 9 - Credit card order
- Note:You cannot use order type 9 - Credit card order with manual entry. It must be imported via the EDI clock.Note:You cannot enter this order type manually. You must import it using the EDI clock. This order type is intended for Internet trading programs such as Zpider, and is dependent on Zpider being installed with communication to the card company. Upon invoicing, the reserved amount is activated at the card company, with the effect that the amount is transferred from the card company. If you delete or edit order type 9 - Credit card order, the reserved amount is cancelled at the card company. It is not possible to increase the amount of such an order over and above what is specified for Invoice customer no. in the Credit card reservation addition % field. A credit card order must be finished before it can be invoiced. Order type 9 - Credit card order also requires that the Invoice reference, Currency no., Contract amount and Invoice customer no. fields are filled in for the order. The following fields are locked for editing in a credit card order:If you change a credit card order to a different order type you cannot reset it to a credit card order, and the amount is cancelled at the card company.
- Invoice customer no.
- Invoice reference
- Masked card no.
- Contract amount
- Contract amount (dom.)
- Currency no.
- Card company
Note:It is not possible to edit such an order unless you have selected "Allow change to credit card order" for the access group under the processing "Function access/Misc.". An increase in the amount is not approved over and above the credit card reservation addition rate, even at this access level.When you copy such an order type, all you have to do is check the box for the credit note to show that it contains order type "9. Credit card order" and a credit is sent to the card company. A credit card order may only be credited once.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Order type | Integer |
| SQL name | AgrOrdTp | The database field name. |
| API identifier | activityOrderType | The API identifier used in GraphQL. |
| Number | 6514 |
Additional fees and rounding product
Product used for order match.
The field refers to the Product table, from which the order match processing will retrieve the Process no. when creating order line(s) for the fee charges or rounding amount that exist(s) in the incoming XML invoice. Both Product no. freight 4 and Additional fees and rounding product field in Company information table need to be filled in simultaneously in order for an incoming invoice which contains fees and/or freight charges to be successfully order matched.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Product no. | Text (40) |
| SQL name | OnAcProd | The database field name. |
| API identifier | additionalFeesCostsRoundingOMProduct | The API identifier used in GraphQL. |
| Number | 8586 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Product | AdditionalFeesCostsRoundingOMProduct |
| ||
| Search product | AdditionalFeesCostsRoundingOMSearchProduct |
|
Address line 1
The company’s Address line 1 to Address line 4. The standard forms are edited so that Address line 1 and Address line 2 are printed.
| 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 | 491 |
Address line 2
The company’s Address line 1 to Address line 4. The standard forms are edited so that Address line 1 and Address line 2 are printed.
| 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 | 492 |
Address line 3
The company’s Address line 1 to Address line 4. The standard forms are edited so that Address line 1 and Address line 2 are printed.
| 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 | 3789 |
Address line 4
The company’s Address line 1 to Address line 4. The standard forms are edited so that Address line 1 and Address line 2 are printed.
| 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 | 3790 |
Amount limit for cash purchase
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Amount | Decimal |
| SQL name | OffAmLmt | The database field name. |
| API identifier | officialCashAmountLimit | The API identifier used in GraphQL. |
| Number | 16217 |
Auto. entries series
The Voucher series to be used for vouchers produced by the Automatic entries processing in the General ledger account table.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | AutEVoSr | The database field name. |
| API identifier | automaticEntryVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 5808 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | AutomaticEntriesSeries |
|
Auto. gen. trans series
The Voucher series to be used for automatically generated transactions for customers, suppliers, capital assets, cash discounts, input and output VAT, investment tax and the basis for investment tax.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | AutVoSr | The database field name. |
| API identifier | automaticallyGeneratedTransactionVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 1968 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | AutomaticallyGeneratedTransactionSeries |
|
Auto. gen. trans. proc.
Alternative processing methods for automatically generated transactions.
- value date,
- overridden accounting year and period, tax year and term,
- debit/credit and
- (for Germany) sign
- 1 - Accumulate per organisational unit combination
- If selected, automatically generated transactions will also be totalled per combination of organisational units. To include the organisational units in the transactions, you must also have filled in the status field for the organisational units in the general ledger accounts. The organisational units have the cash discount transactions for the invoice transaction.
- 2 - Generate continuously (Recommended)
- If selected, automatically generated transactions are generated continuously per debit and credit in voucher lines, select value 2. The transactions then have the same voucher number, organisational unit number, employee number, customer number, supplier number, order number, product number and invoice number as the voucher line. Cross-account no. and type are set equal to the account number for the transaction from which they are generated, for example customer number for general ledger entries for customers, and sales account for VAT transactions. This is recommended for full cross-traceability between transaction tables.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Auto. gen. trans. proc. | Integer |
| SQL name | AutTr | The database field name. |
| API identifier | automaticallyGeneratedTransactionProcessing | The API identifier used in GraphQL. |
| Number | 4776 |
AutoInvoice company UUID
The Visma AutoInvoice company UUID, that you can find on the Visma AutoInvoice portal.
The value is used to identify the company in the Visma AutoInvoice portal when sending invoices.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | GUID | Text (40) |
| SQL name | MavCompId | The database field name. |
| API identifier | autoInvoiceCompanyUUID | The API identifier used in GraphQL. |
| Number | 16452 |
AutoInvoice contract unit
Defines what organisation unit is used as Contract reference in AutoInvoice documents.
When set, Business NXT will look for the chosen organisation unit type on the order when sending purchase order or invoice to Visma AutoInvoice and adds the name of the unit to the XML.
- 1 - Organisational unit class 1
- 2 - Organisational unit class 2
- 3 - Organisational unit class 3
- 4 - Organisational unit class 4
- 5 - Organisational unit class 5
- 6 - Organisational unit class 6
- 7 - Organisational unit class 7
- 8 - Organisational unit class 8
- 9 - Organisational unit class 9
- 10 - Organisational unit class 10
- 11 - Organisational unit class 11
- 12 - Organisational unit class 12
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Org. unit class no. | Integer |
| SQL name | AiCtrUn | The database field name. |
| API identifier | autoInvoiceContractUnit | The API identifier used in GraphQL. |
| Number | 18958 |
AutoInvoice customer contract unit
Defines what organisation unit is used as Customer contract reference in AutoInvoice documents.
When set, Business NXT will look for the chosen organisation unit type on the customer when sending product catalogue to Visma AutoInvoice and adds the name of the unit to the XML.
- 1 - Organisational unit class 1
- 2 - Organisational unit class 2
- 3 - Organisational unit class 3
- 4 - Organisational unit class 4
- 5 - Organisational unit class 5
- 6 - Organisational unit class 6
- 7 - Organisational unit class 7
- 8 - Organisational unit class 8
- 9 - Organisational unit class 9
- 10 - Organisational unit class 10
- 11 - Organisational unit class 11
- 12 - Organisational unit class 12
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Org. unit class no. | Integer |
| SQL name | AiCusCtrUn | The database field name. |
| API identifier | autoInvoiceCustomerContractUnit | The API identifier used in GraphQL. |
| Number | 18959 |
AutoInvoice default user API key
Visma AutoInvoice default user ID, which will be used as fallback if no user ID is specified on a user-level.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Secured GUID | Text (80) |
| SQL name | MavDefKey | The database field name. |
| API identifier | autoInvoiceDefaultUserAPIKey | The API identifier used in GraphQL. |
| Number | 16453 |
AutoInvoice endpoint ID
Must contain the sender electronic address used for Visma.net AutoInvoice, unless the electronic address is identical to Organisation no. If so, 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 | 18050 |
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 | 18051 |
AutoInvoice mapping file
The path to the mapping file created with Visma.net AutoInvoice mapping tool.
The path to the mapping file created with Visma.net AutoInvoice mapping tool, if configured per company. Default path is \Plugins. File content overrides default mapping for Visma.net AutoInvoice. The Visma.net AutoInvoice mapping tool isn't used in Business NXT.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Data filename | Text (260) |
| SQL name | AiMapFNm | The database field name. |
| API identifier | autoinvoiceMappingFileName | The API identifier used in GraphQL. |
| Number | 17915 |
AutoInvoice processing
Common
- Printout if "AutoInvoice e-mail address" field is blank
- When selected, the invoice will be sent to printout from AutoInvoice when the AutoInvoice e-mail address field on the customer is blank and electronic delivery is not available.
- Do not show a message when transfer is successful
- When selected, no message box will appear on screen when sending documents to AutoInvoice succeeds. Failed delivery will still be displayed.
- Process incoming documents automatically
- When selected, Download incoming document will trigger processing of documents and creation of new customers.
- Not VAT registered
- When selected, VAT reg. no. is not required for sending to AutoInvoice. All relevant e-documents (invoices and
orders) will be sent to AutoInvoice with the sender company identified as "Not VAT
registered". All tax codes in the document will be identified as "Not subject to VAT"
.Note:If a document with VAT is sent while this setting is on, the document will be considered invalid and will fail when run through validation.
- Do not include document PDF when sending
- When sending to AutoInvoice, a PDF copy of the document is by default
included in the delivery. When selected, the XML is sent without the PDF image
included. Assigned order attachments are always included in the XML, whether the
option is selected or not. The option is relevant for order, invoice and interest
note.Note:This option gives a significant performance improvement.
Product catalogue
- Create new suppliers from incoming document automatically
- When selected, Business NXT will automatically run the Create customer or supplier from XML processing with default options if it is unable to find a supplier during the running of the Process document processing for product catalog.
- Keep Incoming product data when processed
- When selected, the processed row is kept in the table. Default handling is that the row is deleted when the Status field is updated to 6 - Processed.
- Create product if not found when updating product data
- When selected, running the product lookup with Action = 2 - Update and the product does not exist in the database, the value of the Action field is changed to 1 - Add, the value in the Product no. field is copied to the New product no. field and the Status field is set to 2 - Ready for update. When running the Process product data processing, a new product will be created.
- Update product if found when attempting to add new
- When selected, if running the product lookup with Action = 1 - Add and the product is identified as existing in the database, the value of the Action field is changed to 2 - Update, the value in New product no. field is copied to the Product no. field and the Status field is set to 2 - Ready for update. When running the Process product data processing, the product identified in the Product no. field will be created.
- Add new price row when updating
- When selected, a new row is added in the Price- and discount matrix table instead of replacing the existing row when processing product data with Action = 2 - Update.
- Delete product if possible
- When selected, any product with Action = 3 - Delete that is possible to delete will be deleted. Products that cannot be deleted will be set as Suspended, which is the default handling.
- Process product automatically when ready for update
- When selected, running the Lookup and suggest product no. processing will trigger the running of Process product data processing, if the value of the Status field has changed to 2 - Ready for update.
- Update only supplier related product data
- When selected, only the Delivery alternative and Price- and discount matrix tables are
updated. Note:Only in use when updating existing products.
Order
- Create new customers from incoming document automatically
- When selected, Business NXT will automatically run the Create customer or supplier from XML processing with default options if it is unable to find a customer (or invoice customer) during the running of the Process document processing for order.
- Copy contact e-mail to invoice customer AutoInvoice e-mail address
- When selected, the e-mail address for the customer contact in the incoming order is copied to the invoice customer's AutoInvoice e-mail address when a new customer is created using Create customer or supplier from XML.
Despatch advice
- Create order document for despatch advice
- When selected, Business NXT will override the setting for packing slip in Document copies
and create data in the Order document tables for the
document type, so that despatch advice can be sent.Note:If Packing slip is already selected in Document copies, order documents will be created as before.
- Do not save serial numbers into the Serial number table
- When selected, if updating the Reservation table is not possible, the alternative of updating the Serial no. table will not be used.
- Finish reservation when serial number is added
- When selected, reservations will be finished when serial numbers are updated from incoming despatch advice, if the order line processing method Count number from serial no. is set on the order line.
Invoice
- Override invoice document delivery with AutoInvoice
- When selected, all new sales orders will have only AutoInvoice as document delivery method for invoice. The parameter does not influence document delivery method on existing orders.
- Do not send CID to AutoInvoice
- When selected, no CID will be sent to AutoInvoice.
- Hide product no. from invoice lines
- When selected, Product no. and EAN item no. are not included in the invoice XML content sent to AutoInvoice.
- Use legacy format for invoicing
- When selected, Business NXT sends invoices using Visma XML instead of the default format, and with pre-existing functionality.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | AutoInvoice processing | Integer |
| SQL name | AiPro | The database field name. |
| API identifier | autoInvoiceProcessing | The API identifier used in GraphQL. |
| Number | 17663 |
AutoInvoice project unit
Defines what organisation unit is used as Project reference in AutoInvoice invoices.
When set, Business NXT will look for the chosen organisation unit type on the order when sending invoice to Visma AutoInvoice and adds the name of the unit to the XML.
- 1 - Organisational unit class 1
- 2 - Organisational unit class 2
- 3 - Organisational unit class 3
- 4 - Organisational unit class 4
- 5 - Organisational unit class 5
- 6 - Organisational unit class 6
- 7 - Organisational unit class 7
- 8 - Organisational unit class 8
- 9 - Organisational unit class 9
- 10 - Organisational unit class 10
- 11 - Organisational unit class 11
- 12 - Organisational unit class 12
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Org. unit class no. | Integer |
| SQL name | AiProUn | The database field name. |
| API identifier | autoInvoiceProjectUnit | The API identifier used in GraphQL. |
| Number | 18960 |
AutoReport processing
- Send to AutoReport
- Default value for Printing VAT reports in the VAT control printing dialog. Can be set on or off by default. Value can always be changed from the printing dialog for each printing.
- Process VAT payment messages automatically
- When selected, payment messages from Altinn via Visma.net AutoReport will be processed automatically and a payment batch will be created in batch table with the defined VAT control supplier and VAT control account from Company information table.
- Automatic batch update of VAT payment messages
- When selected, the batch based on the Altinn payment information will be updated automatically.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | AutoReport processing | Integer |
| SQL name | ARProc | The database field name. |
| API identifier | autoReportProcessing | The API identifier used in GraphQL. |
| Number | 18215 |
B/S to PL exchg. var. a/c gr.
The Account group to use for posting Agio.
- the difference in profit as a consequence of different PL and B/S exchange rates (= total posted to PL accounts * (1 / PL exchange rate -1 / B/S exchange rate), and
- the difference between the total debit and credit as a consequence of rounding (= total posted to all accounts, including (1), with a reversed sign),
- realised, comparison 1 and 2, budget 1 and 2,
- OB, movement and CB,
- total debit, total credit, net, net debit and net credit,
The account group might have, for example, Other equity as the Aggregated account group.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account group | Text (60) |
| SQL name | AgioAcGr | The database field name. |
| API identifier | agioAccountGroup | The API identifier used in GraphQL. |
| Number | 6902 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Account group | AgioAccountGroup |
|
Bank account
The bank account number for the company, which you can choose to edit out on giros and other printouts.
You can override the individual customers in the GL account field in the Bank account table, if the Client responsibility bank account on giro/accounting flag is set under the Bank account processing field.
The values can be returned with the macro functions @ClientresponsibilityGeneralledgeraccount() and @ClientresponsibilityBankaccount() on order document forms.
This field is also used for electronic funds transfer, if the currency or bank partner does not have a value for this. You can also use this field for the IBAN bank account number, but there is a separate field for adding in IBAN bank account numbers. You must also complete the Bank branch or Swift code fields, which are included on the form if you wish to make a payment to a foreign country. Which fields you complete depends on the IBAN requirements in the sender's country. You can contact your bank for more details.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is 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 | 496 |
Bank no.
The referenced Bank for the company.
If no other bank is selected, this value is used. See the documentation for electronic funds transfer.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is 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 | 6226 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Bank | Bank |
|
Calculate delivery date
Options related to calculation of delivery dates.
Process actions
- Do not enter required delivery date when entering data
- If selected, the Required delivery date field in the Order table will not be filled in when new orders are created. Nor will the order lines be given a value in the Required delivery date field when the order head is blanked.
- Do not enter confirmed delivery date when entering data
- If selected, the Confirmed delivery date field in the Order table will not be filled in when new orders are created. Nor will the order lines be given a value in the Confirmed delivery date field when the order head is blanked.
- Do not update time fields
- If selected, this field, the value in the Adm. time, Lead time, Transport time, Production time, Assemble time and Disassemble time fields will be taken from the stock balance in the sales order when new order lines are inserted.
- Do not move confirmed delivery date to earlier on order
- If selected, 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.
- customers in the Customer options field in the Associate table.
- each individual order in the Order options field in the Order table.
- Overwrite non blank delivery dates
- Not in use.
- Update order head with dates from order lines
- If selected, the Required delivery date, Confirmed delivery date, Original confirmed delivery date, Sent date and
Arrival/departure date fields on the order head are updated with the first date from the order lines with
the earliest date.Note:Selecting this option overrides corresponding selections in the Customer options fields in the Associate and Order options field in the Order table.Note:The Original confirmed delivery date field is only set if this field is empty.Note:These dates have consequences for new order lines that are added, and will be suggested again as before.
- Use latest instead of earliest date
- If selected, the latest date is used from order lines instead of earliest. The option is only available when the Update order head with dates from order lines is selected.
- Update empty order line delivery date if sales order delivery date is entered
- If selected, empty order line delivery dates (Required delivery date or Confirmed delivery date) are updated when delivery date is entered on the sales order, if the order delivery date is also empty. Once the date is set, delivery date behaviour is the same as before.
Calculated at
- Filling in desired delivery date and quantity
- If selected, the confirmed delivery date on the sales order lines is
recalculated when the required delivery date and quantity have been filled in.Note:In order for the delivery dates to be calculated, you must have selected either this option or the Saving inserted/changed order lines option.
- Saving inserted/changed order lines
- If selected, the confirmed delivery date on the sales order lines is recalculated in connection with inserted and altered order lines.
- Using the "Resave" command
- If selected, the confirmed delivery date on the sales order lines is recalculated when the Resave processing is executed.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Calculate delivery date | Integer |
| SQL name | RecCfDt | The database field name. |
| API identifier | calculationOfDeliveryDates | The API identifier used in GraphQL. |
| Number | 6532 |
Capital asset deprec. series
The voucher series you enter in this field will be used for vouchers that are produced by the "Write-off" processing in the Capital asset table.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | WOVoSr | The database field name. |
| API identifier | depreciationVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 5778 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | CapitalAssetSeries |
|
Capital asset initialize voucher series
The Voucher series used for vouchers that are produced by the Initialize capital asset processing in the Capital asset table.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | PPurVoSr | The database field name. |
| API identifier | capitalAssetInitializeVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 14533 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | CapitalAssetPurchaseVoucherSeries |
|
Capital asset sales/scrap voucher series
The Voucher series used for vouchers that are produced by the Sell or scrap processing in the Capital asset table.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | PrSSVoSr | The database field name. |
| API identifier | capitalAssetSalesAndScrapVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 14532 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | CapitalAssetSalesOrScapVoucherSeries |
|
Case organisational units
The Case organisational unit that is to be used when copying to the Order no. field on the voucher line and appointments.
The default for the legal solution is 2. You must also select the Copy case no. to order no. option in the Voucher type processing field in the Voucher type table for this to work. The field is also used in client interest computation to split by case.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Organisational unit classes | Integer |
| SQL name | ClRNo | The database field name. |
| API identifier | caseOrgUnits | The API identifier used in GraphQL. |
| Number | 12269 |
Cash discount processing
Options for cash discount processing.
- 0 - VAT of amount paid
- If selected, VAT is calculated from the amount paid.
- 1 - VAT of invoiced amount
- If selected, VAT is calculated from the invoiced amount and deducted from the voucher line amount when calculating cash amounts.
- 2 - VAT of amount after cash discount
- If selected, VAT is calculated from the amount after cash discount.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Cash discount processing | Integer |
| SQL name | CshDcPro | The database field name. |
| API identifier | cashDiscountProcessing | The API identifier used in GraphQL. |
| Number | 7544 |
Cash invoice series
The Voucher series used for cash invoices.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | ChIvVoSr | The database field name. |
| API identifier | cashInvoiceVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 9266 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | CashInvoiceVoucherSeries |
|
Cash order batch processing
Options for cash order batch processing.
During cash invoicing a batch is created, and if there is an existing batch in the Batch table with the same combination, the voucher lines are added to the end of the existing batch. Using these options, you define how the batch accumulation is to be performed. If you select the Customer no., the Seller no. and the Organisational unit 1, all cash invoices printed for the same combination of these will go into the same batch.
- Join cash order batches
- Accumulate the cash invoice batches for each combination.Note:If selected, you cannot use automatic updating of the batch.
Combinations
- Value date
- If selected, accumulating is based on currency data.
- Customer no.
- If selected, accumulating is based on Cust. no.
- Invoice customer no.
- If selected, accumulating is based on Invoice customer no.
- Seller no.
- If selected, accumulating is based on Seller/buyer
- Organisational unit 1
- If selected, accumulating is based on Organisational unit 1
- Organisational unit 2
- If selected, accumulating is based on Organisational unit 2
- Organisational unit 3
- If selected, accumulating is based on Organisational unit 3
- Organisational unit 4
- If selected, accumulating is based on Organisational unit 4
- Organisational unit 5
- If selected, accumulating is based on Organisational unit 5
- Organisational unit 6
- If selected, accumulating is based on Organisational unit 6
- Organisational unit 7
- If selected, accumulating is based on Organisational unit 7
- Organisational unit 8
- If selected, accumulating is based on Organisational unit 8
- Organisational unit 9
- If selected, accumulating is based on Organisational unit 9
- Organisational unit 10
- If selected, accumulating is based on Organisational unit 10
- Organisational unit 11
- If selected, accumulating is based on Organisational unit 11
- Organisational unit 12
- If selected, accumulating is based on Organisational unit 12
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Cash order batch processing | Integer |
| SQL name | CBndProc | The database field name. |
| API identifier | cashOrderBatchProcessing | The API identifier used in GraphQL. |
| Number | 13873 |
Chain discounts
Options for chained discounts.
Getting price
- Price/discount on buyer
- The buyer (customer number) will be used instead of the invoice recipient when looking up in the price and discount matrix.
- Price refunds independent of stock
- Price rounding after discount
- Business NXT will round the price after discount to two decimals when calculating amounts in order lines. The fields for Price after discount and Price after discount (dom.) in the order lines will then also display two decimals as standard instead of floating decimals.
- Price factor for hire orders
- The order lines contain a Price factor field in which you can enter a factor by which Business NXT is to multiply the product of price and quantity when calculating line amounts. If you have checked Price factor for hire orders field , Business NXT will not multiply by the hire period when calculating line amounts and instead suggest the price factor on the basis of a table of price factors for various hire periods and only multiply by this factor.
- Cost price from the price and discount matrix if sold out
- Business NXT will use cost prices from the price and discount matrix in sales order lines instead of the physical Average cost price from the Stock balance table when the physical stock level is 0 or negative. The last FIFO cost price is retained when the stock level becomes 0 or negative. Business NXT will select the cost price for any supplier stated in the order line or in the order head. When you look up in the Stock balance table, Business NXT includes the normal supplier in the sales order line when the check is in place and the stock level is £0
Comparison date
In this field you define which date forms the basis of comparisons with the from and to dates in the Stock balance table (which states when the goods can be sold), and when referring to the Price- and discount matrix table:
- 0 - Today's date
- The current date will be used.
- 1 - Order/transaction date
- The transaction date in the order line is used, or the order date in the order head.
- 2 - Required/confirmed delivery date
- Business NXT will use the confirmed delivery date in the order line if it has been entered, possibly in the order head, or the required delivery date in the order line or the order head.
Price quantity extent
- Sales price
- Hire price
- Purchase price
- Cost price
Freight cost processing
- Ton rate 1
- Ton rate 2
- Ton rate 3
- Ton rate 4
- Cost 1
- Cost 2
- Cost 3
- Cost 4
Expenses
You check the dialog box if the freight fields from 1 - 4 in the Order table are to be calculated based on a ton rate or by cost.
- Calculate cost price addition from price after discount
- Calculate freight 1-4 based on price after discount
- Account debit/credit freight 1-4 and customs on purchase
- All freight and customs will be posted upon invoice receipt on the purchase order instead of at the time of sale. As before, the cost price of stock will increase with freight and customs, but at the time of sale this value will not be deducted; it is the cost price that will be posted.
Optimization parameters
- Consider empty/zero values for price calculations
Chain discounts
- Subtract discount 1 before discount 2
- If selected, Disc. % and Disc. amount is deducted before calculating discount 2.
- Subtract discount 1 before discount 3
- If selected, Disc. % and Disc. amount is deducted before calculating discount 3.
- Subtract discount 2 before discount 3
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 3.
- Subtract discount 1 before discount 4
- If selected, Disc. % and Disc. amount is deducted before calculating discount 4.
- Subtract discount 2 before discount 4
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 4.
- Subtract discount 3 before discount 4
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 4.
- Subtract discount 1 before discount 5
- If selected, Disc. % and Disc. amount is deducted before calculating discount 5.
- Subtract discount 2 before discount 5
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 5.
- Subtract discount 3 before discount 5
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 5.
- Subtract discount 4 before discount 5
- If selected, Disc. % 4 and Disc. amount 4 is deducted before calculating discount 5.
- Subtract discount 1 before discount 6
- If selected, Disc. % and Disc. amount is deducted before calculating discount 6.
- Subtract discount 2 before discount 6
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 6.
- Subtract discount 3 before discount 6
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 6.
- Subtract discount 4 before discount 6
- If selected, Disc. % 4 and Disc. amount 4 is deducted before calculating discount 6.
- Subtract discount 5 before discount 6
- If selected, Disc. % 5 and Disc. amount 5 is deducted before calculating discount 6.
Discount suggestion
There are two columns of check boxes. The first concerns the discount percentage, the second the discount amount. There are check boxes for each of the 5 pairs of sales discount percentages and amounts. The first pair of check boxes also concerns discount percentages and amounts for hire and purchasing.
% / Amount
- Suggest discount 1 percent
- Suggest discount 1 amount
- Suggest discount 2 percent
- Suggest discount 2 amount
- Suggest discount 3 percent
- Suggest discount 3 amount
- Suggest discount 4 percent
- Suggest discount 4 amount
- Suggest discount 5 percent
- Suggest discount 5 amount
- Search for price - discount amount
- Business NXT will deduct the discount amounts selected from the price in the row. Business NXT will otherwise search for discount amounts separately so that the discount amounts can be shown in different rows from the price and limited to other criteria. Business NXT will then select the highest possible discount amount for the criteria selected. The discount can have a maximum limit if you check the type of discount concerned in the dialog box for the field for fixed prices and discounts.
Prices/discount total field
In this field you can use as a basis totals for lines in the order with the same value in the Product price group 1 field. The Prices/disc. total field under Company information indicates the field on the order lines that is to be totalled. Looking up in this field leads to a dialog box with the following options:
(If you select "Quantity" 1, the quantity is not reduced by the value in the “Free quantity” field in the order line.)
The field is used by the Recalculate prices processing in order page elements and when correcting sales prices and discounts in sales order lines when saving price refund lines for which the refund status has been changed to 2 (Confirmed).
- 0 - (None)
- 1 - Quantity
- 2 - Quantity in base unit
- 3 - Length
- 4 - Area
- 5 - Volume
- 6 - Net weight
Customer- / Supplier- / other orders
Here you can select which criteria Business NXT is to search by in the price and discount matrix, in rows with no product number.
There are three columns of check boxes. The first relates to customer orders (sales, hire and loan), the middle one to supplier orders (purchase) and the last one to other orders (adjustments, goods consumed, production and stock transfers).
If you select as few options as possible in each column, the speed of references in the price matrix will increase, thereby also increasing the speed of order entry and the printing of price lists. When printing price lists, Business NXT starts with the selections in the customer column. Currencies includes testing in both the current currency (for sales, hire and purchase) and the cost currency.
The selections are stored in the Price/disc.-criteria 1 - Price/disc.-criteria 6 fields under Company information.
- Structure product no.
- Included in structure
- Product price group 1
- Product price group 2
- Product price group 3
- Warehouse no.
- Shipment no.
- Customer no.
- Customer price group 1
- Customer price group 2
- Customer price group 3
- Supplier no.
- Employee no.
- Employee price group
- Wage rate no.
- Order no.
- Order price group
- Post code
- Terms of delivery
- Delivery method
- Organisational unit 1
- Organisational unit 2
- Organisational unit 3
- Organisational unit 4
- Organisational unit 5
- Organisational unit 6
- Organisational unit 7
- Organisational unit 8
- Organisational unit 9
- Organisational unit 10
- Organisational unit 11
- Organisational unit 12
- Date
- Unit
- Quantity
- Price unit
- Quantity in base unit
- Length
- Area
- Volume
- Net weight
- Currency
- Gross prices
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Chain discounts | Integer |
| SQL name | ChDisc | The database field name. |
| API identifier | chainDiscounts | The API identifier used in GraphQL. |
| Number | 2470 |
Check incoming invoice no.
If you have checked this box, when you enter the invoice number in a voucher line containing a supplier number Business NXT will reject your entry if there is already a supplier transaction with the same invoice number for this supplier. The status bar displays the voucher number, voucher date and amount in default currency.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Boolean | Integer |
| SQL name | CtrlInvo | The database field name. |
| API identifier | checkIncomingInvoiceNo | The API identifier used in GraphQL. |
| Number | 6406 |
Cheque amount text
The language the @GiroAmountAsText () macro is using.
You can use this macro function in reminders, interest notes, payment giros and order documents. The giro amount is then printed as text in the language you have selected in the Cheque amount text field. You must place the @GiroAmountAsText macro in reminders, interest notes, payment giros and order documents to get the giro amount as text.
The macro provides three options:
- @GiroAmountAsText (), producing one thousand five hundred and ten 00/100
- @GiroAmountAsText (1), producing one thousand five hundred and ten Kr and 00 øre
English UK and US have a special option:
- @GiroAmountAsText (2), producing zero zero, zero one five one zero 00
Depending on the language you have selected, the currency identifier is changed when option (1) is selected:
- Norwegian, Danish and Swedish shows Kr og 00 øre
- German shows Euro und 00 cent
- English shows Pounds and 00 pence
- US English shows Dollars and 00 cents
- Lithuanian shows Lt 00 ct
- Polish shows Solvotych 00 Groszy
Russian, Finnish, Latvian and Estonian are not defined.
There is also a macro for outputting the amounts with a fixed number of printed characters and digits. @DigitsInTextBoxes (number of boxes, number of characters) This macro is an extension of the special option in @GiroAmountAsText(2) and has been created for the UK and US market, where these values must be printed on cheques and other bank documents.
Specify how many number boxes you want to print. If you do not specify values, the default number of boxes is 6 and the number of characters in each box is 10.
@DigitsITextBoxes(5,7) and with the number 1024.45
| Ten thousands | Thousands | Hundreds | Tens | Ones |
| ******* | ****ONE | ***ZERO | ****TWO | ***FOUR |
Decimal places are not shown.
In the first parameter you define the number of digits to be processed. If the number is greater, the defined number of digits is used, starting from the right. This means that digits exceeding the definition are not included.
Leading zeros are represented by asterisks (*) corresponding to the defined number of characters.
The number name is padded to the left with leading asterisks up to the defined number of characters. The minimum length is 5, which is the longest a number name can be in English. If you specify a smaller number, the system removes characters up to the last character.
We recommend that you use a fixed-width font rather than a proportion font.
- 1 - Norwegian
- 2 - Danish
- 3 - Swedish
- 9 - Finnish
- 4 - English
- 5 - German
- 6 - Polish
- 7 - Lithuanian
- 10 - Russian
- 11 - Estonian
- 12 - Latvian
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Program language no. | Integer |
| SQL name | GAmLang | The database field name. |
| API identifier | chequeAmountTextLanguageNo | The API identifier used in GraphQL. |
| Number | 6594 |
Cheque series
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | ChkVoSr | The database field name. |
| API identifier | chequeVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 9322 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | ChequeVoucherSeries |
|
CID Company no. of digits
The number of characters to be used as the company number. The field will only be used by EFT systems in order to identify the company number as part of the CID code.
You must also define the relationship between companies and general ledger accounts in the Corporation settlement account table.
Internal OCR scanning does not take account of this field.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Number of digits | Integer |
| SQL name | CIDFrm | The database field name. |
| API identifier | cidCompanyNoDigits | The API identifier used in GraphQL. |
| Number | 13031 |
CID cust./suppl. chars.
How many digits the customer/supplier part of the CID code is to consist of.
The customer/supplier part may be up to 10 digits. If the customer/supplier number is shorter, Business NXT inserts leading zeros. If it is longer, the digits are calculated from the back.
It is also possible to enter this value in the Factoring company table, so that the rules can be different for each company.
This field is also included in the Factoring company table and is activated when using Def. fact. comp./CID-code def.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Number of digits | Integer |
| SQL name | CIDCust | The database field name. |
| API identifier | cidCustomerOrSupplierNoDigits | The API identifier used in GraphQL. |
| Number | 5044 |
CID factoring chars
In this field you state how many characters are to be used from the Factoring ID field between the customer and reference number parts of the CID code which is produced with the CID code macro in order documents, reminders and interest forms.
See the description of the @CID macro in the chapter on order documents in the system specification for logistics, or the chapter on reminders and interest calculation in the system specification for accounting.
This field is also included in the Factoring company table and is activated when using Def. Factoring companies/CID code def.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Number of digits | Integer |
| SQL name | CIDFact | The database field name. |
| API identifier | cidFactoringDigits | The API identifier used in GraphQL. |
| Number | 6668 |
CID ref. no. digits
How many digits the reference number part of the CID code is to consist of.
The reference number part may be up to 9 digits. If the reference number is shorter, Business NXT inserts leading zeros. If it is longer, the digits are calculated from the back.
It is also possible to enter this value in the Factoring company table, so that the rules can be different for each company.
This field is also included in the Factoring company table and is activated when using Def. Factoring companies/CID code def.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Number of digits | Integer |
| SQL name | CIDRef | The database field name. |
| API identifier | cidReferenceNoDigits | The API identifier used in GraphQL. |
| Number | 5045 |
Client bank account
In this field you can override the individual clients in the GL account field in the Bank account table, if the Client responsibility bank account on giro/accounting flag is set under the Bank account processing field.
This field is used in Visma Lawyer, but you can also use it in other Business NXT solutions.
The values can be returned with the macro functions @ClientresponsibilityGeneralledgeraccount() and @ClientresponsibilityBankaccount() on order document forms.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | ClBaAcNo | The database field name. |
| API identifier | clientBankAccountNo | The API identifier used in GraphQL. |
| Number | 8442 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | ClientBankAccount |
|
Client interest account
This field is used in Visma Lawyer, but you can also use it in other Business NXT solutions. The cost account you want Business NXT to post interest on when you calculate client interest.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | ClIntAc | The database field name. |
| API identifier | clientInterestAccountNo | The API identifier used in GraphQL. |
| Number | 11218 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | ClientInterestAccount |
|
Client interest series
This field is used in Visma Lawyer, but you can also use it in other Business NXT solutions. The voucher series you want Business NXT to retrieve the voucher number and type from when you calculate client interest.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | ClIntVoS | The database field name. |
| API identifier | clientInterestVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 11219 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | ClientInterestSeries |
|
Client responsible account 1
The account you enter here will have client responsibility totalled, unless you have specified other accounts in the Account no. series table or for the client in the Associate table.
This will be used primarily for client funds in the legal solution.
To cover all areas of responsibility within a large legal practice, which has regular client funds, property and debt collection, three such units have been created.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is 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 | 8441 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | ClientResponsibleAccount1 |
|
Client responsible account 2
The account you enter here will have client responsibility totalled, unless you have specified other accounts in the Account no. series table or for the client in the Associate table.
This will be used primarily for client funds in the legal solution.
To cover all areas of responsibility within a large legal practice, which has regular client funds, property and debt collection, three such units have been created.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | ClRe2Ac | The database field name. |
| API identifier | clientResponsibleAccountNo2 | The API identifier used in GraphQL. |
| Number | 8666 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | ClientResponsibleAccount2 |
|
Client responsible account 3
The account you enter here will have client responsibility totalled, unless you have specified other accounts in the Account no. series table or for the client in the Associate table.
This will be used primarily for client funds in the legal solution.
To cover all areas of responsibility within a large legal practice, which has regular client funds, property and debt collection, three such units have been created.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | ClRe3Ac | The database field name. |
| API identifier | clientResponsibleAccountNo3 | The API identifier used in GraphQL. |
| Number | 12264 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | ClientResponsiblity3Account |
|
Common processing
Define rules applicable to all modules.
The options below "Unused/reserved numbers" enable you to deal with gaps in voucher series.
Unused/reserved number
- Save unused numbers
- If this field is checked, unused numbers are stored in the Unused/reserved number table.
- Reuse unused no.
- This field is greyed out if you have not checked the Save unused numbers field.
Database
- Allow asynchronous database access
- In some of Business NXT database queries, asynchronous database queries are permitted which means that several independent queries can be processed at the same time against the database.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Common processing | Integer |
| SQL name | ComPro | The database field name. |
| API identifier | commonProcessing | The API identifier used in GraphQL. |
| Number | 10802 |
Company bank account
The Company bank account field is used for entering client responsibility/bank when settling the accounts.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | OpBankAc | The database field name. |
| API identifier | companyBankAccountNo | The API identifier used in GraphQL. |
| Number | 8665 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | CompanyBankAccount |
|
Comparison date
You can select whether you want the order date/transaction date to be used instead of the current date when comparing dates in the order system. You can override the order date in the order head with the transaction date/order date in the order lines.
This applies, for example, when you are referring to the Stock balance table, where you can enter from and to dates for when the goods can be sold. The date that you select in the dialog box is compared to the from and to dates that have been entered. This also applies when referring in the Price and Discount Matrix to special campaign / seasonal prices.
Getting price
- Price/discount on buyer
- The buyer (customer number) will be used instead of the invoice recipient when looking up in the price and discount matrix.
- Price refunds independent of stock
- Price rounding after discount
- Business NXT will round the price after discount to two decimals when calculating amounts in order lines. The fields for Price after discount and Price after discount (dom.) in the order lines will then also display two decimals as standard instead of floating decimals.
- Price factor for hire orders
- The order lines contain a Price factor field in which you can enter a factor by which Business NXT is to multiply the product of price and quantity when calculating line amounts. If you have checked Price factor for hire orders field , Business NXT will not multiply by the hire period when calculating line amounts and instead suggest the price factor on the basis of a table of price factors for various hire periods and only multiply by this factor.
- Cost price from the price and discount matrix if sold out
- Business NXT will use cost prices from the price and discount matrix in sales order lines instead of the physical Average cost price from the Stock balance table when the physical stock level is 0 or negative. The last FIFO cost price is retained when the stock level becomes 0 or negative. Business NXT will select the cost price for any supplier stated in the order line or in the order head. When you look up in the Stock balance table, Business NXT includes the normal supplier in the sales order line when the check is in place and the stock level is £0
Comparison date
In this field you define which date forms the basis of comparisons with the from and to dates in the Stock balance table (which states when the goods can be sold), and when referring to the Price- and discount matrix table:
- 0 - Today's date
- The current date will be used.
- 1 - Order/transaction date
- The transaction date in the order line is used, or the order date in the order head.
- 2 - Required/confirmed delivery date
- Business NXT will use the confirmed delivery date in the order line if it has been entered, possibly in the order head, or the required delivery date in the order line or the order head.
Price quantity extent
- Sales price
- Hire price
- Purchase price
- Cost price
Freight cost processing
- Ton rate 1
- Ton rate 2
- Ton rate 3
- Ton rate 4
- Cost 1
- Cost 2
- Cost 3
- Cost 4
Expenses
You check the dialog box if the freight fields from 1 - 4 in the Order table are to be calculated based on a ton rate or by cost.
- Calculate cost price addition from price after discount
- Calculate freight 1-4 based on price after discount
- Account debit/credit freight 1-4 and customs on purchase
- All freight and customs will be posted upon invoice receipt on the purchase order instead of at the time of sale. As before, the cost price of stock will increase with freight and customs, but at the time of sale this value will not be deducted; it is the cost price that will be posted.
Optimization parameters
- Consider empty/zero values for price calculations
Chain discounts
- Subtract discount 1 before discount 2
- If selected, Disc. % and Disc. amount is deducted before calculating discount 2.
- Subtract discount 1 before discount 3
- If selected, Disc. % and Disc. amount is deducted before calculating discount 3.
- Subtract discount 2 before discount 3
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 3.
- Subtract discount 1 before discount 4
- If selected, Disc. % and Disc. amount is deducted before calculating discount 4.
- Subtract discount 2 before discount 4
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 4.
- Subtract discount 3 before discount 4
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 4.
- Subtract discount 1 before discount 5
- If selected, Disc. % and Disc. amount is deducted before calculating discount 5.
- Subtract discount 2 before discount 5
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 5.
- Subtract discount 3 before discount 5
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 5.
- Subtract discount 4 before discount 5
- If selected, Disc. % 4 and Disc. amount 4 is deducted before calculating discount 5.
- Subtract discount 1 before discount 6
- If selected, Disc. % and Disc. amount is deducted before calculating discount 6.
- Subtract discount 2 before discount 6
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 6.
- Subtract discount 3 before discount 6
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 6.
- Subtract discount 4 before discount 6
- If selected, Disc. % 4 and Disc. amount 4 is deducted before calculating discount 6.
- Subtract discount 5 before discount 6
- If selected, Disc. % 5 and Disc. amount 5 is deducted before calculating discount 6.
Discount suggestion
There are two columns of check boxes. The first concerns the discount percentage, the second the discount amount. There are check boxes for each of the 5 pairs of sales discount percentages and amounts. The first pair of check boxes also concerns discount percentages and amounts for hire and purchasing.
% / Amount
- Suggest discount 1 percent
- Suggest discount 1 amount
- Suggest discount 2 percent
- Suggest discount 2 amount
- Suggest discount 3 percent
- Suggest discount 3 amount
- Suggest discount 4 percent
- Suggest discount 4 amount
- Suggest discount 5 percent
- Suggest discount 5 amount
- Search for price - discount amount
- Business NXT will deduct the discount amounts selected from the price in the row. Business NXT will otherwise search for discount amounts separately so that the discount amounts can be shown in different rows from the price and limited to other criteria. Business NXT will then select the highest possible discount amount for the criteria selected. The discount can have a maximum limit if you check the type of discount concerned in the dialog box for the field for fixed prices and discounts.
Prices/discount total field
In this field you can use as a basis totals for lines in the order with the same value in the Product price group 1 field. The Prices/disc. total field under Company information indicates the field on the order lines that is to be totalled. Looking up in this field leads to a dialog box with the following options:
(If you select "Quantity" 1, the quantity is not reduced by the value in the “Free quantity” field in the order line.)
The field is used by the Recalculate prices processing in order page elements and when correcting sales prices and discounts in sales order lines when saving price refund lines for which the refund status has been changed to 2 (Confirmed).
- 0 - (None)
- 1 - Quantity
- 2 - Quantity in base unit
- 3 - Length
- 4 - Area
- 5 - Volume
- 6 - Net weight
Customer- / Supplier- / other orders
Here you can select which criteria Business NXT is to search by in the price and discount matrix, in rows with no product number.
There are three columns of check boxes. The first relates to customer orders (sales, hire and loan), the middle one to supplier orders (purchase) and the last one to other orders (adjustments, goods consumed, production and stock transfers).
If you select as few options as possible in each column, the speed of references in the price matrix will increase, thereby also increasing the speed of order entry and the printing of price lists. When printing price lists, Business NXT starts with the selections in the customer column. Currencies includes testing in both the current currency (for sales, hire and purchase) and the cost currency.
The selections are stored in the Price/disc.-criteria 1 - Price/disc.-criteria 6 fields under Company information.
- Structure product no.
- Included in structure
- Product price group 1
- Product price group 2
- Product price group 3
- Warehouse no.
- Shipment no.
- Customer no.
- Customer price group 1
- Customer price group 2
- Customer price group 3
- Supplier no.
- Employee no.
- Employee price group
- Wage rate no.
- Order no.
- Order price group
- Post code
- Terms of delivery
- Delivery method
- Organisational unit 1
- Organisational unit 2
- Organisational unit 3
- Organisational unit 4
- Organisational unit 5
- Organisational unit 6
- Organisational unit 7
- Organisational unit 8
- Organisational unit 9
- Organisational unit 10
- Organisational unit 11
- Organisational unit 12
- Date
- Unit
- Quantity
- Price unit
- Quantity in base unit
- Length
- Area
- Volume
- Net weight
- Currency
- Gross prices
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Comparison date | Integer |
| SQL name | OrdDtPr | The database field name. |
| API identifier | comparisonDate | The API identifier used in GraphQL. |
| Number | 4778 |
Consignment notes series
Under company information you enter references to voucher and document series for the various order documents.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | ConVoSr | The database field name. |
| API identifier | consignmentNoteVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 5984 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | ConsignmentNotesSeries |
|
Correction series
This field is used for corrections.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | CorVoSr | The database field name. |
| API identifier | correctionVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 6457 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | CorrectionSeries |
|
Country no.
Which country is to be regarded as domestic or default.
Will use parameters for this country unless a different country is stated in the Associate or Order 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 | 1985 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Country | Country |
|
Credit control
Allows you to enter quotation orders for customers with a credit suspension.
This field stores selections made in the dialog box for the processing for credit control. You can also activate the dialog box by looking up in this field.
A warning may be given, depending on the selection in the Credit control field. Any suspension takes effect only when you try to turn a quotation order into an ordinary order. It is also possible to apply a suspension when entering vouchers.
If you check the Ignore order balance in credit limit field, Business NXT excludes all non-completed orders for this customer.
If you check the Ignore appointment balance in credit limit field, Business NXT excludes the balance stored for the associate in the Appointment balance field.
Credit denied
On entry
- Ignore
- Warning
- Block
On picking
- Ignore
- Block
Voucher registration
- Ignore
- Warning
- Block
Credit limit
On entry
- Ignore
- Warning
- Block
On picking
- Ignore
- Block
Overdue invoices
On entry
- Ignore
- Warning
- Block
On picking
- Ignore
- Block
____
- Ignore order balance in credit limit
- Ignore appointment balance in credit limit
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Credit control | Integer |
| SQL name | CrCtrl | The database field name. |
| API identifier | creditControl | The API identifier used in GraphQL. |
| Number | 6367 |
Credit note series
You can enter separate voucher and document series for outgoing invoices and credit notes. The voucher and document series for invoices will be used for credit notes unless you have entered a separate voucher and document series for them and filled in the field for the next voucher number in this voucher and document series. Nevertheless, using the Voucher table and the Document link table, you will be able to specify different voucher types for invoices and credit notes so that the vouchers can have different texts depending on whether they are invoices or credit notes.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | CrNtVoSr | The database field name. |
| API identifier | creditNoteVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 3358 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | CreditNoteSeries |
|
CRM processing
Miscellaneous
- Check min. qty on resp. type
- This parameter means that the Quantity will never be lower than the minimum number on the response type, while what is allocated will change depending on when the from/to time is entered.
- Do not set appointment assoc. no. from current user
- The logged-in user is not suggested in the field for Appointment associate no.
when you enter an appointment. Note:The assignment does not apply when the Appointment table is linked to the Associate table using the Associate number – Appointment associate key.
- Calculate full time over midnight
- The Calculate full time over midnight check box is selected in the dialog box under Proc. method 8 in the Appointment table. A check is only inserted for appointments where products, resources or response types are used. You can also place a check directly in the Calculate full time over midnight field in the dialog box under Proc. method 8 in the Appointment table. If you have checked this field the time over midnight or several days with the total number of hours is calculated.
- Use "From date" as price comparison date
- Business NXT will use From date in the Price- and discount matrix table in connection with price lookups and not today's date. If From date has not been filled in, today's date will be used.
- Suggest price when pasting product/quantity
- A new lookup will be made against the price and discount matrix when
you paste a row in the Appointment table. If, for example,
you select the Appointment associate no.,
From date,
To date,
Product no.,
Quantity and
Price fields
on a row in the Appointment table, and paste the row into a blank row in the same table, a lookup will be made
against the Price- and discount matrix table, and
the Amount
and Number in quantity format fields
will be calculated.Note:If you do not use the Product no. field and "Cut"/"Paste" in activities, this field should not be selected.
Lookup behaviour
- Use table format on product lookup
- Business NXT uses table format instead of a dialog box when you perform a lookup in the Product no. field in the Appointment table.
- Use table format on liaison lookup
- Business NXT uses table format instead of a dialog box when you perform a lookup in the Contact field in the Appointment and Order tables.
- Use table format on response type lookup from participant
- Business NXT uses table format instead of a dialog box when you perform a lookup in the Resp. type field in the Participant table.
- Lookup resource from Employee no.
- Business NXT checks if there is a resource for the employee when you enter an employee number in
the appointment. If so, this value is copied to the Res. no. field of the
Appointment. You can use
this parameter if you want to link resource balances to appointments, in which case
you must specify the resource number. Note:It is important to understand that this may affect the way other appointments behave when there is more than one of them. You must therefore set the correct processing for the appointment to make sure that time balances are not affected. You do this in the Proc. method 8 field.
Account series
- Use employee account series
- Business NXT performs a check against the Account series when an employee number is assigned.
- Use resource account series
- Business NXT performs a check against the Account series when a resource number is assigned.
- Do not allow overlapping account series
- Business NXT performs a check against the Account no. series to see if they overlap.
Document handling
- Do not create appointments for documents
- Business NXT does not create appointments when you create documents. You can override these settings in the dialog box for the Create document processing in the Appointment table by selecting the Create appointment field. The Do not create appointments for documents field is selected by default.
- Use company as receiver for contact person
- The document that is created for the contact will also be linked to the associate number to which the contact belongs.
- Fax if not e-mail on mail merge
- If you select Fax if no e-mail when using e-mail to external associates, Business NXT will send a fax if an associate does not have an e-mail address. This assumes that the e-mail system supports fax transmissions. If a user is to receive a fax but the fax number is not known, the message will be sent to a printer instead if you have checked Print if no fax.
- Print if not fax with mail merge
- If you select Fax if not e-mail on mail merge when using e-mail to external associates, Business NXT will send a fax if an associate does not have an e-mail address. This assumes that the e-mail system supports fax transmissions. If a user is to receive a fax but the fax number is not known, the message will be sent to a printer instead if you have checked Print if not fax with mail merge.
- Use part of description in filename
- When running the Create document processing
from the Associate table
the file name will contain the document description.The file name will be: Part of document description - Visma Business generated file name.ExtensionNote:Only the first 40 characters of the document description will be included in the file name.
- Create folder structure using customer no. and document group no.
Transfer group appointments to order
- Get price and discount from price- discount matrix
- Prices and discounts are recalculated when you transfer appointments to orders. Consideration is also given to price criteria that are only in orders, such as order price group.
- Allow transfer without customer
- When you run the Generate order processing from the Appointment table, you transfer the appointment to an employee order. If the order has transaction type 5 - Further processing and order type 4 - Realised order, it is updated in statistics. If you have checked this field and run the Generate order processing from the Appointment table, you can also transfer appointments with different customer numbers to the same order, on the condition that the order does not have a customer number.
- Show group dialog
- The "Create order" dialog box will appear when you run the Generate order
processing in the Appointment table. You have the
following options in this dialog box:
- Groups
- Use default values from last appointment
- Demand group agreements
- By defining sorting for the appointments, multiple appointment lines are combined into one order line during transfer to order. If you select this field, a dialog box appears, from where you can run the Generate order processing from the Appointment table, indicating that sorting will be used in the transfer. You must sort the appointments at least by Currency no., Order no., Product no., and Warehouse no. before running the routine. If you do not sort the appointments, they are not transferred and Business NXT displays a corresponding message.
- Use last as default
- When you use grouping, Business NXT does not create breaks for certain fields. The values used by these fields are taken from the first line. If you check the Use last as default field, values from the last line are used instead.
Customer account set
- From invoice customer
- You can check this field to copy the account set from the invoice customer to the appointment.
- From employee
- You can check this field to copy the account set from the employee to the appointment, instead of from the invoice customer or customer.
- From customer
- You can check this field to copy the account set from the customer to the appointment, instead of from the invoice customer.
Responsible approval
- From project org. unit
- If you select official from project official, the official is taken from the organisational unit defined as the Mandatory sort organisational unit in the Company information table.
- From resource
- The official is taken from the resource number.
- From employee
- The official is taken from the employee number.
- From appointment associate
- The official is taken from the associate who is the appointment associate.
- From customer
- The official is taken from the customer number.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | CRM processing | Integer |
| SQL name | CrmPro | The database field name. |
| API identifier | crmPprocessing | The API identifier used in GraphQL. |
| Number | 9037 |
Curr. corr. voucher series
The voucher series to be used when posting currency correction amounts.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | CurCVoSr | The database field name. |
| API identifier | currencyCorrectionVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 11869 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | CurrencyCorrectionVoucherSeries |
|
Currency no.
The currency in which the accounts are to be done and in which reports to the authorities are to be submitted.
This currency applies unless a different currency is stated in, for example, the Associate table.
You can change the field with the Change default currency processing. If you try to change it directly, you are given a message that you can change it via the processing.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Currency no. | Integer |
| Write Access | None | You are not allowed to modify the value in this field. |
| SQL name | Cur | The database field name. |
| API identifier | currencyNo | The API identifier used in GraphQL. |
| Number | 1987 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Currency | Currency |
|
Currency no. 2
The value in this field is used by default in the voucher lines if the field is not already filled in and a different value is not specified in the batch head when you enter the debit/credit account number.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is 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 | 14362 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Currency | Currency2 |
|
Customer account
The general ledger account number defined in the account plan.
Customer movements are totalled in the general ledger account specified for customers (1500 in the default account plan), unless another general ledger account is specified in the Associate table or in the Account no. series table.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | CustAc | The database field name. |
| API identifier | customerAccountNo | The API identifier used in GraphQL. |
| Number | 504 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | CustomerAccount |
|
Customer no. for anonymisation
Used by the Delete customer/supplier data processing in the Associate table.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Cust. no. | Integer |
| SQL name | CustNoFAn | The database field name. |
| API identifier | customerNoForAnonymization | The API identifier used in GraphQL. |
| Number | 18502 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Associate | CustomerNoForAnonymization |
|
Customer P.E. amend days
How many days beyond the end of the period vouchers can be posted for customers.
An error message is generated when completing the fields if the number of days for the general ledger is lower than for the ledgers.
Voucher registration
When you enter the year and period or voucher reversal year and period in the batch head, either directly or indirectly via the value date/voucher reversal date, an error message is generated if the number of general ledger days is specified under company information, but the current date is more than this number of days beyond the accounting period’s to date.
When entering debit/credit account number in a voucher line, Business NXT will generate an error message if the field for the relevant account type is filled in under company information, and the current date is more than this number of days beyond the accounting period’s to date (based on the financial year and period in the voucher line, or in the batch head if they are not overridden in the voucher lines).
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Days | Integer |
| SQL name | CstDy | The database field name. |
| API identifier | customerAmendDays | The API identifier used in GraphQL. |
| Number | 8514 |
Data retention period
Used by the Delete customer/supplier data processing in the Associate table.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | No. | Integer |
| SQL name | DataRetPr | The database field name. |
| API identifier | dataRetentionPeriod | The API identifier used in GraphQL. |
| Number | 18501 |
Database transactions
Operations which you want to perform within a database transaction so that you do not risk partially updated data in the event of an abnormal operating interruption.
Business NXT will perform these operations with several small transactions, for example around each voucher line, so that data is locked for the shortest possible period of time. The problem with having large transactions is that they can produce disproportionate delays in multi-user systems unless the activities are co-ordinated so that they are performed at different times. Checks are therefore normally recommended only if there is one user or not many concurrent users or if, for example, batch updating can be started at the end of the working day.
If the transaction fails, the status bar will display 0 rows approved and a dialog box will appear to inform you that the transaction was not performed on account of deadlock or another database error. An attempt is made to cancel locks, and voucher and document series are reset if possible (i.e. unless other concurrent users have retrieved data from them in the meantime; see the section on voucher and document series).
Processings
- Updating batches
- Note:You cannot check the Updating batches field for new installations as this may produce errors in the updated journals. If you have updated from a previous version and the field is selected, the function will work as before.
- Other processings
Saving
- Saving orders
- Saving general
Printouts
- Pick list
- Approval of documents
- Approval of documents refers to order documents, delivery notes, price refund requests, reminders, interest notes, payment giros and tax statements.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Database transactions | Integer |
| SQL name | DBTrans | The database field name. |
| API identifier | databaseTransactions | The API identifier used in GraphQL. |
| Number | 5732 |
Days without payment
The days you want to be payment free.
What you check in this dialog box affects the planned payment dates for open supplier entries. You also choose in this dialog box whether you want payment dates to be moved to before or after the payment free days.
- Monday
- Tuesday
- Wednesday
- Thursday
- Friday
- Saturday
- Sunday
- Move to earlier date
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Days without payment | Integer |
| SQL name | PmtFree | The database field name. |
| API identifier | daysWithoutPayment | The API identifier used in GraphQL. |
| Number | 6739 |
Debit/credit control
Conditions that must be fulfilled before Business NXT updates a batch.
Business NXT ignores this field when you update batches with origin code 17 (Differences) and 3 (Tax statements). The latter is due to any postings to the account for the basis for investment tax.
- Total debit = Total credit
If you want to check that the total posted to debit corresponds to the total posted to credit in the batches, check the Total debit = Total credit box. This means that the Difference field must be 0. Business NXT will then refuse to update batches for which there is a difference between the totals posted to debit and credit.
It might sometimes be necessary to switch off the debit/credit control to avoid interim posting when you have batches that produce 0 in total, and you can then remove the selection temporarily.
- Check sum = Sum debit
If you check the Check sum = Total debit box, Business NXT will require that there is no difference between the check sum that you have entered in the batch head and the total posted to debit. There is a separate Control difference field in the batch head that always displays this difference, if a check sum has been defined. Batches without check sums are not affected by this selection.
- Calculated CB bank = CB bank
If you check the Calculated CB bank = CB bank box, Business NXT will not update batches where there is a difference between the closing balance that Business NXT has calculated for the account specified in the batch head and the closing balance that you have specified, i.e. the Difference CB bank field must be 0.
- Total debit currency = Total credit currency
If you want to check that the total posted to debit in currency corresponds to the total posted to credit in currency in the batches, select the "Total debit currency = Total credit currency" box. This means that the "Difference in currency" field must be 0. Business NXT will then refuse to update batches for which there is a difference between the totals posted to debit in currency and credit in currency.
It might sometimes be necessary to switch off the debit/credit control to avoid interim posting when you have batches that produce 0 in total, and you can then remove the selection temporarily.
- Total debit currency 2 = Total credit currency 2
If you want to check that the total posted to debit in currency 2 corresponds to the total posted to credit in currency 2 in the batches, select the "Total debit currency 2 = Total credit currency 2" box. This means that the "Difference in currency 2" field must be 0. Business NXT will then refuse to update batches for which there is a difference between the totals posted to debit in currency 2 and credit in currency 2.
It might sometimes be necessary to switch off the debit/credit control to avoid interim posting when you have batches that produce 0 in total, and you can then remove the selection temporarily.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Debit/credit control | Integer |
| SQL name | DbCrChk | The database field name. |
| API identifier | debitCreditControl | The API identifier used in GraphQL. |
| Number | 509 |
Deduct client responsibility 1 Product no.
The product number that is to be used when you run the Deduct client responsibility routine. If you do not enter a value, the Deviate product field is used.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Product no. | Text (40) |
| SQL name | DeCl1Pr | The database field name. |
| API identifier | deductClientResponsibility1ProductNo | The API identifier used in GraphQL. |
| Number | 12266 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Product | DeductFromClientRepsonsiblity1Product |
| ||
| Search product | DeductFromClientRepsonsiblity1SearchProduct |
|
Deduct client responsibility 2 Product no.
The product number that is to be used when you run the Deduct client responsibility routine. If you do not enter a value, the Deviate product field is used.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Product no. | Text (40) |
| SQL name | DeCl2Pr | The database field name. |
| API identifier | deductClientResponsibility2ProductNo | The API identifier used in GraphQL. |
| Number | 12267 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Product | DeductFromClientRepsonsiblity2Product |
| ||
| Search product | DeductFromClientRepsonsiblity2SearchProduct |
|
Deduct client responsibility 3 Product no.
The product number that is to be used when you run the Deduct client responsibility routine. If you do not enter a value, the Deviate product field is used.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Product no. | Text (40) |
| SQL name | DeCl3Pr | The database field name. |
| API identifier | deductClientResponsibility3ProductNo | The API identifier used in GraphQL. |
| Number | 12268 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Product | DeductFromClientRepsonsiblity3Product |
| ||
| Search product | DeductFromClientRepsonsiblity3SearchProduct |
|
Def. bank partner
Suggested as default value when creating payment suggestions.
The default value for the Bank partner field in the Create payment suggestion processing. The field is also used in the integration between Business NXT and some external EFT systems to specify which bank partner is standard.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | No. | Integer |
| SQL name | StdBPrt | The database field name. |
| API identifier | standardBankPartner | The API identifier used in GraphQL. |
| Number | 15472 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Bank partner | StandardBankPartner |
|
Def. curr. column name
In this field you state how columns with values in the default currency are to be named on the basis of the equivalent columns in the current currency or cost currency.
The name of the column with values in the current currency or cost currency is included where @ is placed. For example, @ (£) will give the column names for the default currency the suffix). If the field is not filled in, @ (dom.) is used.
This is used in tables in which the value in the default currency is subordinate to the values in the current currency or cost currency, i.e. for shipments, price refund lines, orders, order lines, reservation lines, product transactions and budget lines.
In some cases, the text forms part of a larger text. For example, the Amount, Amount (kr) and Amount in EUROS columns in the order lines all have the text Amount. Business NXT includes this text in @ (kr) itself. You can override this in the Def. curr. column name field or in @ in EUROS (from the text file for the language in question).
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Name | Text (20) |
| SQL name | DomColNm | The database field name. |
| API identifier | standardCurrencyColumnName | The API identifier used in GraphQL. |
| Number | 4920 |
Def. fact. comp./CID-code def.
In this field you enter standard factoring company which is used when printing invoices for factoring. The information is also transferred to some external EFT systems.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Factoring no. | Integer |
| SQL name | DefFCNo | The database field name. |
| API identifier | defaultFactoringCompanyNo | The API identifier used in GraphQL. |
| Number | 12226 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Factoring company | DefaultFactoringCompany |
|
Def. factoring/CID for importing
This field is used in the integration between Business NXT and some external EFT systems to specify which factoring companys and CID def. will be standard on importing OCR data.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Factoring no. | Integer |
| SQL name | StdFCNo | The database field name. |
| API identifier | defaultFactoringCompanyNoForImport | The API identifier used in GraphQL. |
| Number | 15471 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Factoring company | DefaultFactoringCompanyForImport |
|
Default account set
Which account set is to be used when nothing else is specified in the product/order line and the customer/supplier/order/order line.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account set | Integer |
| SQL name | StAcSet | The database field name. |
| API identifier | defaultAccountSet | The API identifier used in GraphQL. |
| Number | 2469 |
Default cash customer no.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Cust. no. | Integer |
| SQL name | DfChCuNo | The database field name. |
| API identifier | defaultCashCustomerNo | The API identifier used in GraphQL. |
| Number | 16216 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Associate | CashCustomer |
|
Default customer no. series
This series is used to set a Cust. no. when creating customers automatically.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account number series no. | Integer |
| SQL name | DfCstSr | The database field name. |
| API identifier | defaultCustomerNoSeriesNo | The API identifier used in GraphQL. |
| Number | 18402 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Account no. series | AccountNoSeriesCustomer |
|
Default flow group
Suggested automatically when sending a document on flow for approval.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | No. | Integer |
| SQL name | DfFlGr | The database field name. |
| API identifier | defaultFlowGroup | The API identifier used in GraphQL. |
| Number | 19686 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Flow group | FlowGroup |
|
Default supplier no. series
This series is used to set a Sup. no. when creating suppliers automatically.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account number series no. | Integer |
| SQL name | DfSupSr | The database field name. |
| API identifier | defaultSupplierNoSeriesNo | The API identifier used in GraphQL. |
| Number | 18403 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Account no. series | AccountNoSeriesSupplier |
|
Default supplier template no.
This Associate no. is suggested as default template supplier when creating a new supplier in Visma Document Center.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Associate no. | Integer |
| SQL name | DfSupTplNo | The database field name. |
| API identifier | defaultSupplierTemplateNo | The API identifier used in GraphQL. |
| Number | 18995 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Associate | DefaultSupplierTemplateNo |
|
Default VAT and accounting group
Which tax and accounting group is to be used when nothing else is specified in the product/order line and the customer/supplier/order/order line.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | VAT and accounting group | Integer |
| SQL name | StProdGr | The database field name. |
| API identifier | defaultTaxAndAccountingGroup | The API identifier used in GraphQL. |
| Number | 2468 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| VAT and accounting group | DefaultTaxAndAccGroup |
|
Default warehouse
In this field you enter which warehouse is to be used when no other warehouse is specified in orders. If this field is not filled in, 1 is used as the default warehouse.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Warehouse no. | Integer |
| SQL name | StStc | The database field name. |
| API identifier | defaultWarehouseNo | The API identifier used in GraphQL. |
| Number | 4758 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Warehouse | DefaultWarehouse |
|
Delivery address assoc. no.
You can use this field to join the Company information table and the Associate table with the key "Delivery associate no. - Associate no.".
You then have access to the fields in the Associate table from the Company information table. For example, if you want the company to have a delivery address that is different from the address registered in the Company information table, you can retrieve the Address line 1-Address line 4, Post code and Postal area fields from the Associate table. If you enter an associate number in the Delivery address assoc. no. field, this Associate no will be used as Delivery associate no. for all Order with Transaction type = 6 - Purchase unless the Sup. no. on the Order has another Send in to associate no. given in the Associate table.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Associate no. | Integer |
| SQL name | DelActNo | The database field name. |
| API identifier | deliveryAddressAssociateNo | The API identifier used in GraphQL. |
| Number | 13787 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Associate | DeliveryAddressAssociate |
|
Delivery note series
When you print delivery notes, the document number is taken from the voucher and document series for delivery notes.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | DelVoSr | The database field name. |
| API identifier | deliveryNoteVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 6391 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | DeliveryNoteSeries |
|
Digits in account no. w/0
If the general ledger account numbers have different numbers of digits, Business NXT will be able to display preceding zeros before account numbers with fewer digits than the amount specified in this field. Any account numbers with more digits will not be affected.
This is used in countries such as the USA, Germany and Poland.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Number of digits | Integer |
| SQL name | AcDig | The database field name. |
| API identifier | digitsInAccountNoWithLeadingZero | The API identifier used in GraphQL. |
| Number | 4764 |
Direct debit. giro no.
This field is not in use and will be omitted in later versions.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Bank account | Text (35) |
| SQL name | DebGiro | The database field name. |
| API identifier | directDebitingGiroNo | The API identifier used in GraphQL. |
| Number | 5709 |
Discount suggestion
This field stores the selections made in the dialog box of the Price/discount processing choices under the "Discount" tab in the "Discount suggestion" group.
Getting price
- Price/discount on buyer
- The buyer (customer number) will be used instead of the invoice recipient when looking up in the price and discount matrix.
- Price refunds independent of stock
- Price rounding after discount
- Business NXT will round the price after discount to two decimals when calculating amounts in order lines. The fields for Price after discount and Price after discount (dom.) in the order lines will then also display two decimals as standard instead of floating decimals.
- Price factor for hire orders
- The order lines contain a Price factor field in which you can enter a factor by which Business NXT is to multiply the product of price and quantity when calculating line amounts. If you have checked Price factor for hire orders field , Business NXT will not multiply by the hire period when calculating line amounts and instead suggest the price factor on the basis of a table of price factors for various hire periods and only multiply by this factor.
- Cost price from the price and discount matrix if sold out
- Business NXT will use cost prices from the price and discount matrix in sales order lines instead of the physical Average cost price from the Stock balance table when the physical stock level is 0 or negative. The last FIFO cost price is retained when the stock level becomes 0 or negative. Business NXT will select the cost price for any supplier stated in the order line or in the order head. When you look up in the Stock balance table, Business NXT includes the normal supplier in the sales order line when the check is in place and the stock level is £0
Comparison date
In this field you define which date forms the basis of comparisons with the from and to dates in the Stock balance table (which states when the goods can be sold), and when referring to the Price- and discount matrix table:
- 0 - Today's date
- The current date will be used.
- 1 - Order/transaction date
- The transaction date in the order line is used, or the order date in the order head.
- 2 - Required/confirmed delivery date
- Business NXT will use the confirmed delivery date in the order line if it has been entered, possibly in the order head, or the required delivery date in the order line or the order head.
Price quantity extent
- Sales price
- Hire price
- Purchase price
- Cost price
Freight cost processing
- Ton rate 1
- Ton rate 2
- Ton rate 3
- Ton rate 4
- Cost 1
- Cost 2
- Cost 3
- Cost 4
Expenses
You check the dialog box if the freight fields from 1 - 4 in the Order table are to be calculated based on a ton rate or by cost.
- Calculate cost price addition from price after discount
- Calculate freight 1-4 based on price after discount
- Account debit/credit freight 1-4 and customs on purchase
- All freight and customs will be posted upon invoice receipt on the purchase order instead of at the time of sale. As before, the cost price of stock will increase with freight and customs, but at the time of sale this value will not be deducted; it is the cost price that will be posted.
Optimization parameters
- Consider empty/zero values for price calculations
Chain discounts
- Subtract discount 1 before discount 2
- If selected, Disc. % and Disc. amount is deducted before calculating discount 2.
- Subtract discount 1 before discount 3
- If selected, Disc. % and Disc. amount is deducted before calculating discount 3.
- Subtract discount 2 before discount 3
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 3.
- Subtract discount 1 before discount 4
- If selected, Disc. % and Disc. amount is deducted before calculating discount 4.
- Subtract discount 2 before discount 4
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 4.
- Subtract discount 3 before discount 4
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 4.
- Subtract discount 1 before discount 5
- If selected, Disc. % and Disc. amount is deducted before calculating discount 5.
- Subtract discount 2 before discount 5
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 5.
- Subtract discount 3 before discount 5
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 5.
- Subtract discount 4 before discount 5
- If selected, Disc. % 4 and Disc. amount 4 is deducted before calculating discount 5.
- Subtract discount 1 before discount 6
- If selected, Disc. % and Disc. amount is deducted before calculating discount 6.
- Subtract discount 2 before discount 6
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 6.
- Subtract discount 3 before discount 6
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 6.
- Subtract discount 4 before discount 6
- If selected, Disc. % 4 and Disc. amount 4 is deducted before calculating discount 6.
- Subtract discount 5 before discount 6
- If selected, Disc. % 5 and Disc. amount 5 is deducted before calculating discount 6.
Discount suggestion
There are two columns of check boxes. The first concerns the discount percentage, the second the discount amount. There are check boxes for each of the 5 pairs of sales discount percentages and amounts. The first pair of check boxes also concerns discount percentages and amounts for hire and purchasing.
% / Amount
- Suggest discount 1 percent
- Suggest discount 1 amount
- Suggest discount 2 percent
- Suggest discount 2 amount
- Suggest discount 3 percent
- Suggest discount 3 amount
- Suggest discount 4 percent
- Suggest discount 4 amount
- Suggest discount 5 percent
- Suggest discount 5 amount
- Search for price - discount amount
- Business NXT will deduct the discount amounts selected from the price in the row. Business NXT will otherwise search for discount amounts separately so that the discount amounts can be shown in different rows from the price and limited to other criteria. Business NXT will then select the highest possible discount amount for the criteria selected. The discount can have a maximum limit if you check the type of discount concerned in the dialog box for the field for fixed prices and discounts.
Prices/discount total field
In this field you can use as a basis totals for lines in the order with the same value in the Product price group 1 field. The Prices/disc. total field under Company information indicates the field on the order lines that is to be totalled. Looking up in this field leads to a dialog box with the following options:
(If you select "Quantity" 1, the quantity is not reduced by the value in the “Free quantity” field in the order line.)
The field is used by the Recalculate prices processing in order page elements and when correcting sales prices and discounts in sales order lines when saving price refund lines for which the refund status has been changed to 2 (Confirmed).
- 0 - (None)
- 1 - Quantity
- 2 - Quantity in base unit
- 3 - Length
- 4 - Area
- 5 - Volume
- 6 - Net weight
Customer- / Supplier- / other orders
Here you can select which criteria Business NXT is to search by in the price and discount matrix, in rows with no product number.
There are three columns of check boxes. The first relates to customer orders (sales, hire and loan), the middle one to supplier orders (purchase) and the last one to other orders (adjustments, goods consumed, production and stock transfers).
If you select as few options as possible in each column, the speed of references in the price matrix will increase, thereby also increasing the speed of order entry and the printing of price lists. When printing price lists, Business NXT starts with the selections in the customer column. Currencies includes testing in both the current currency (for sales, hire and purchase) and the cost currency.
The selections are stored in the Price/disc.-criteria 1 - Price/disc.-criteria 6 fields under Company information.
- Structure product no.
- Included in structure
- Product price group 1
- Product price group 2
- Product price group 3
- Warehouse no.
- Shipment no.
- Customer no.
- Customer price group 1
- Customer price group 2
- Customer price group 3
- Supplier no.
- Employee no.
- Employee price group
- Wage rate no.
- Order no.
- Order price group
- Post code
- Terms of delivery
- Delivery method
- Organisational unit 1
- Organisational unit 2
- Organisational unit 3
- Organisational unit 4
- Organisational unit 5
- Organisational unit 6
- Organisational unit 7
- Organisational unit 8
- Organisational unit 9
- Organisational unit 10
- Organisational unit 11
- Organisational unit 12
- Date
- Unit
- Quantity
- Price unit
- Quantity in base unit
- Length
- Area
- Volume
- Net weight
- Currency
- Gross prices
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Discount suggestion | Integer |
| SQL name | DiscSug | The database field name. |
| API identifier | discountSuggestion | The API identifier used in GraphQL. |
| Number | 6737 |
Do not change sign when crediting
If you have checked here, Business NXT will not reverse the sign for values which are filled in in quantity fields in order lines of orders for which Credit note has been checked. This field is not in the database, but visualises a flag in the Order processing field.
| 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 | dontChangeSignWhenCrediting | The API identifier used in GraphQL. |
| Number | 8396 |
Document copies
Operations you want to run within document copies.
They are stored in the database for later printouts.
Order documents
- Invoices/credit notes
- Rows will be saved in the Order document line table using Visma EDI (invoice), normal EDI and XML.
- Consignment notes
- Packing slips
- Pick lists
- Order confirmations
- Quotations
- Purchase orders
- Inquiries
- Production orders
Customer documents
- Reminders
- Interest notes
- This field is not in use.
Invoice delivery
- Only approval - print later from document archive
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Document copies | Integer |
| SQL name | DocCp | The database field name. |
| API identifier | documentCopies | The API identifier used in GraphQL. |
| Number | 13716 |
EAN loc. code
The GLN/GS1 number of the company.
You can print the number in XML export files. If you have checked the Use EAN Location Code field under EDI processing in the Company information table, a lookup is performed in this field during EDI import. The field can have several roles, such as Customer, Invoice customer, Delivery address, Carrier, Warehouse, etc. It is important that two associates do not have the same GLN/GS1 number, as the lookup during EDI import could then produce the wrong associate. A company which has administration and warehouse in different places must have several GLN/GS1 numbers.
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 | Yes | This field is 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 | 12830 |
EDI inc. inv. series
The voucher series to be used for incoming invoices.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | EDIVoSr | The database field name. |
| API identifier | ediIncomingInvoiceVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 7065 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | EdiIncomingInvoiceSeries |
|
EDI processing
This field contains settings for import and export of the EDI files defined in the EDI message table.
- Get info. from product customer table
- The following information will be retrieved: Product no., Inf. 1, Inf. 2 and Inf. 3 from the Product customer table. This applies only to printouts.
- Check customer product (first) when importing
- You use this parameter when importing orders by EDI. If you check this, a lookup will be performed in the Product customer table and the Customer's product no. field. In the import file the customer product number will be shown in the Product number field - OrdLn.ProdNo.
- Origin country for delivery alternative
- You check here if you want to include information about Source country (Country number) from the Delivery alternative table. This applies only to printouts.
- Fetch VAT information
- Rate and VAT no. are included from the VAT rate table. Applies only to printouts.
- Use EAN Location Code
- A test is performed for the Location Code instead of associate number during EDI import.
- Use EAN Item Number
- Not implemented.
- Append to backup file
- The Backup files are not deleted when you import EDI files, but the lines that are imported are saved in the *.bak files.
- Use Customer/Supplier no. as folder
- If you check this field and export EDI files from Business NXT, for example invoicew.edi, the file is placed in a folder under "Program Files\Visma\Business\invoice.edi". This folder is named "Customer no.". If the Invoice customer no. field is different from the Cust. no. field on the order, the folder is named "Invoice customer no.".
- Do not write version information in file
- The version number is not written to the EDI file during export. The first record in the file will then be the H line with associated L lines.
- XML format in output file
- You do not need to use the Imp file for importing XML files. By taking a printout to EDI (delivery method for documents), you can see what the format will look like, so you can make adjustments to an import file of this type.
- XML format in input file
- You do not need to use the Imp file for import of EDI files. By taking a printout to EDI (delivery method for documents), you can see what the format will look like, so you can make adjustments to an import file of this type.
- XML Compliant format
- During import an XML tag must consist of a table name and field name
(SQL). Previously the separator between table name and field name was (.) a full stop.
In XML format it is not permitted to have (.) a full stop as SQL syntax. It has
therefore been replaced with an underscore (_). It is also not permitted to use
numbers that Business NXT uses for External IDs. If there is only an External ID, the tag must start with
_NNNN, where NNNN represents the external ID. You must check the XML Compliant format
field to interpret the new value.Note:The formats are:If the <ORDERS> tag in the import file includes which format is in the import file, you do not need to check the XML Compliant format field.
- <ORDERS format_xml="1.0"> for the old format with a full stop (.)
- <ORDERS format_xml="2.0"> for the new format with an underscore (_)
- Overwrite discount 1 from import file
- The Disc. % and
Disc. amount
fields in the Order line table will be
overwritten when an EDI file is imported if the value differs from 0.00. Note:The selection in the field only affects "Discount amount 1" and does not apply to ORDCHGR.
- Allow EDI collection invoice printing
- You are allowed to select both Batch invoice
in the Customer options
field, and the EDI field under Document delivery
method in the Associate table.
Note:This gives an EDI file per order with batch invoicing, and an external application must be found to combine the files.
- Unique file names
- Each order document for which an EDI file is created is given a file name, which consists of the document type and document number with the file type .edi or .xml. This prevents several users from using the same file simultaneously.
Mandatory EAN Locations
- Customer
- You use this cross to define whether the EDI location role is to be mandatory during order entry and EDI import.
- Invoice customer
- You use this cross to define whether the EDI location role is to be mandatory during order entry and EDI import.
- Deliver to associate
- You use this cross to define whether the EDI location role is to be mandatory during order entry and EDI import.
- Supplier
- You use this cross to define whether the EDI location role is to be mandatory during order entry and EDI import.
- Send to associate
- You use this cross to define whether the EDI location role is to be mandatory during order entry and EDI import.
- Liaison associate
- You use this cross to define whether the EDI location role is to be mandatory during order entry and EDI import.
- Liaison associate 2
- You use this cross to define whether the EDI location role is to be mandatory during order entry and EDI import.
- EAN Location Stock
- You use this cross to define whether the EDI location role is to be mandatory during order entry and EDI import.
- EAN item no.
- Business NXT checks whether the product has an "GTIN item no." during order entry.
- Set unprocessed if error
- The order type is set to unprocessed if the crosses in the location roles above have no "GLN/GS1 no." in the Associate table.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | EDI processing | Integer |
| SQL name | EDIProc | The database field name. |
| API identifier | ediProcessing | The API identifier used in GraphQL. |
| Number | 7047 |
EDI purchase account
The account to be used when posting incoming invoices.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | EDIAc | The database field name. |
| API identifier | ediPurchaseAccountNo | The API identifier used in GraphQL. |
| Number | 7048 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | EdiPurchaseAccount |
|
E-mail address
The company’s e-mail address.
| 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 | 3354 |
EORI number
The EORI number ("Economic Operators Registration and Identification number") is an identification number in all customs procedures when exchanging information with Customs administrations.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | String of length 20 | Text (20) |
| SQL name | EoriNo | The database field name. |
| API identifier | eoriNumber | The API identifier used in GraphQL. |
| Number | 19120 |
EURO currency no.
The exchange rate in this row is used as the basis when converting between EURO and the default currency.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Currency no. | Integer |
| SQL name | EUROCur | The database field name. |
| API identifier | euroCurrencyNo | The API identifier used in GraphQL. |
| Number | 6900 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Currency | EuroCurrency |
|
Exch. var. voucher type
The Voucher type to be used when posting agio (currency exchange rate gains/losses) for electronic funds transfer.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher type | Integer |
| SQL name | AgioVoTp | The database field name. |
| API identifier | agioVoucherType | The API identifier used in GraphQL. |
| Number | 3357 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher type | AgioVoucherType |
|
Exchange account
The Exchange account and Exchange price fields can be used in companies in which the customers finance purchases by exchanging a product or raw material, for example gold.
In the goldsmith’s trade, the Exchange price field can indicate the price per gram of gold. The exchange price is suggested in orders and is multiplied by the exchange quantities to arrive at the exchange values. The deduction from the amount which the customer (i.e. the invoice recipient, possibly a factoring company) owes remains within the account debited for exchange which you have referred to in the Exchange account field.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | ExAc | The database field name. |
| API identifier | exchangeAccountNo | The API identifier used in GraphQL. |
| Number | 4571 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | ExchangeAccount |
|
Exchange price
The Exchange account and Exchange price fields can be used in companies in which the customers finance purchases by exchanging a product or raw material, for example gold.
In the goldsmith’s trade, the Exchange price field can indicate the price per gram of gold. The exchange price is suggested in orders and is multiplied by the exchange quantities to arrive at the exchange values. The deduction from the amount which the customer (i.e. the invoice recipient, possibly a factoring company) owes remains within the account debited for exchange which you have referred to in the Exchange account field.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Price | Decimal |
| SQL name | ExPr | The database field name. |
| API identifier | exchangePrice | The API identifier used in GraphQL. |
| Number | 4570 |
Excl from Web
You can use the Excl from Web field to exempt organisational unit classes from reporting on the Web.
A lookup in the field leads to a dialog box in which you select organisational unit classes, i.e. the same as for the Must be blank and Except fields in the Automatic entry table, with the exception of the selection for Distribution key, which is not displayed.
- Organisational unit 1
- The dialog box contains a list of which organisational units are
selected, enclosed in brackets.
- Select one or more organisational units and click +/- to remove the brackets and the organisational units from the automatic entry line.
- Select one or more organisational units and click +/- to add the brackets and the organisational units to the automatic entry line.
- Organisational unit 2
- See Organisational unit 1.
- Organisational unit 3
- See Organisational unit 1.
- Organisational unit 4
- See Organisational unit 1.
- Organisational unit 5
- See Organisational unit 1.
- Organisational unit 6
- See Organisational unit 1.
- Organisational unit 7
- See Organisational unit 1.
- Organisational unit 8
- See Organisational unit 1.
- Organisational unit 9
- See Organisational unit 1.
- Organisational unit 10
- See Organisational unit 1.
- Organisational unit 11
- See Organisational unit 1.
- Organisational unit 12
- See Organisational unit 1.
- Distribution key
- No distribution key may be stated for the voucher line.
- Look only on account no. to trigger automatic entries
The customer wants to run automatic entries with processing on voucher line, therefore there is no Auto. entry processing entered in the General ledger account table. Automatic entries will be triggered from G/L account only.
Unselect this check box if you want automatic entries to be triggered based on combination of G/L account and org unit.
- Corporate company no.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Except | Integer |
| SQL name | ExWeb | The database field name. |
| API identifier | excludeFromWeb | The API identifier used in GraphQL. |
| Number | 14803 |
Exclude from approval flow
Setup for which organisational units / supplier that shall not be included in resolving the approval flow.
When left unchecked, the approval flow will be calculated from the responsible for organisational unit / supplier, combined with the Employee table relating to superiors and attestation limits.
- Organisational unit 1
- Organisational unit 2
- Organisational unit 3
- Organisational unit 4
- Organisational unit 5
- Organisational unit 6
- Organisational unit 7
- Organisational unit 8
- Organisational unit 9
- Organisational unit 10
- Organisational unit 11
- Organisational unit 12
- Supplier
- General ledger account
- Invoice reference
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Exclude from approval flow | Integer |
| SQL name | ExAppFw | The database field name. |
| API identifier | excludeFromApprovalFlow | The API identifier used in GraphQL. |
| Number | 19089 |
Exclude from Master Data Management
- Organisational unit 1
- Organisational unit 2
- Organisational unit 3
- Organisational unit 4
- Organisational unit 5
- Organisational unit 6
- Organisational unit 7
- Organisational unit 8
- Organisational unit 9
- Organisational unit 10
- Organisational unit 11
- Organisational unit 12
- Customer
- Supplier
- Contact
- General ledger account
- VAT code
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Exclude from Master Data Management | Integer |
| SQL name | VoValPro | The database field name. |
| API identifier | excludeFromMdm | The API identifier used in GraphQL. |
| Number | 8271 |
Expense account
The account you enter here will have outlay totalled, unless you have specified other accounts in the Account no. series table or for the client in the Associate table.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is 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 | 8440 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | OutlayAccount |
|
Expense voucher series
Used when posting claims from Visma.net Expense.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | ExpVoSr | The database field name. |
| API identifier | expenseVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 18203 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | ExpenseVoucherSeries |
|
Factoring CID-def.
In this field you define how the CID codes are to be built up for factoring.
When this field is filled in Business NXT's CID code is filled with leading zeros. The company number comes first in the CID code. This definition is used by the @CID macro in order documents when Factoring is checked in the order document dialog box.
You can also add this value to the field in the Factoring company table so that the rules can be different for each company.
Looking up in the field leads to a dialog box with a selection of the macro functions which apply to order documents (see the system specification for logistics) and the macro function @Modulus ().
Field length
In the same way as with the macro functions in the Form element table, you can, before the right bracket, include a vertical line (|) followed by an integer which indicates the number of characters the field is to have.
- If the number of characters is less, leading zeros are added.
- If the number of characters was less, the characters are kept from the back.
This applies regardless of whether the macro function returns numbers or text.
@Modulus ()
This macro function returns a modulus 10 check digit, or a modulus 11 check digit if 11 is entered as the parameter for the function. The check digit is calculated from that which comes earlier in the field.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Factoring CID-def. | Text (128) |
| SQL name | FactCID | The database field name. |
| API identifier | factoringCidDefinition | The API identifier used in GraphQL. |
| Number | 7548 |
Factoring customer
For factoring the factoring company is entered as a customer and you refer to this customer in the Factoring customer field.
This customer number will be used in the voucher lines for orders.
It is also possible to enter this value in the Factoring company table, so that the rules can be different for each company.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Cust. no. | Integer |
| SQL name | FactCust | The database field name. |
| API identifier | factoringCustomerNo | The API identifier used in GraphQL. |
| Number | 2474 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Associate | FactoringCustomer |
|
Factoring ID
In this field you enter the factoring ID. It is also possible to enter this value in the Factoring company table, so that the rules can be different for each company.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Factoring ID | Text (6) |
| SQL name | FactID | The database field name. |
| API identifier | factoringId | The API identifier used in GraphQL. |
| Number | 2475 |
Fax
The company’s fax number.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Phone | Text (20) |
| SQL name | Fax | The database field name. |
| API identifier | fax | The API identifier used in GraphQL. |
| Number | 495 |
Fax and e-mail processing
Processing rules for fax, e-mail and copies of documents.
File type
- PDF vector based (high performance)
- If you select this option the documents will be created in vector based PDF format. This is the most file-size efficient format.
- PDF embedded fonts
- If you select this option the documents will be created in vector based PDF format. The fonts used in the document will be embedded in the file. The file size will be bigger dependent on the different fonts used in the document.
- PDF image based
- If you select this option the documents will be created in image based PDF format. This format will, in the same way as photos, appear as intended at 100 percent but will start to lose quality if they are over-enlarged. The file size is also bigger than the vector based files.
- TIFF
- If you select this option the documents will be created in TIFF format
Make copies of
- Invoice/credit note copy
- An invoice/credit note copy will be created in the selected File type when you invoice.
The files will by default be stored under C:\Programdata, but it can be overridden to a different location in the Fax and e-mail route column in the System information table.
- Packing slip copy
- A copy of the packing slip will be created in the selected File type when you print the
packing slip.
The files will by default be stored under C:\Programdata, but it can be overridden to a different location in the Fax and e-mail route column in the System information table.
- Order confirmation copy
- An order confirmation copy will be created in the selected File type when you confirm the
order.
The files will by default be stored under C:\Programdata, but it can be overridden to a different location in the Fax and e-mail route column in the System information table.
- Quotation copy
- A copy of the quotation will be created in the selected File type when you create a
quotation.
The files will by default be stored under C:\Programdata, but it can be overridden to a different location in the Fax and e-mail route column in the System information table.
- Purchase order copy
- A copy of the purchase order will be created in the selected
File type when you
create the purchase order.
The files will by default be stored under C:\Programdata, but it can be overridden to a different location in the Fax and e-mail route column in the System information table.
- Reminder copy
- An reminder copy will be created in the selected File type when you create a
reminder.
The files will by default be stored under C:\Programdata, but it can be overridden to a different location in the Fax and e-mail route column in the System information table.
- Interest note copy
- An interest note copy will be created in the selected File type when you create an
interest note.
The files will by default be stored under C:\Programdata, but it can be overridden to a different location in the Fax and e-mail route column in the System information table.
____
- Locate copies in separate folders
- The copies are archived in separate, named directories.
- Generate customer document log
- The customer document log will be active. The log will be updated whenever you send order documents to the customer.
- Do not write on paper
- Faxes, e-mails and copies of order documents are not printed on paper.
MAPI e-mail
- Use Simple MAPI
- If you are a Lotus Notes user, you must select this if you wish to send order documents by e-mail.
- Use Bcc
- The order documents you send by e-mail are addressed in the Blind copy field instead of the To field in your e-mail system.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Fax and e-mail processing | Integer |
| SQL name | FaxMPro | The database field name. |
| API identifier | faxAndEmailProcessing1 | The API identifier used in GraphQL. |
| Number | 12932 |
Fax gateway prefix
Characters that should be added at the beginning of the fax number when you use the "Home/Print/Send e-mail" document delivery method.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Fax gateway prefix | Text (15) |
| SQL name | FaxPre | The database field name. |
| API identifier | faxGatewayPrefix | The API identifier used in GraphQL. |
| Number | 7889 |
Fax gateway suffix
Characters that should be added at the end of the fax number when you use the "Home/Print/Send e-mail" document delivery method.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Fax gateway suffix | Text (30) |
| SQL name | FaxSuf | The database field name. |
| API identifier | faxGatewaySuffix | The API identifier used in GraphQL. |
| Number | 7890 |
Fixed price deviate prod.
With fixed price invoicing you can choose to keep statistics on the difference between the revenue in the invoice plan lines and the invoiceable amounts in the other order lines, on the basis of the entered consumption of goods and services, for a product for over/under-invoicing which you specify in the Deviate prod. no. field in the order head and which is suggested from company information.
See further details in the chapter on order entry in the system specification for logistics.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Product no. | Text (40) |
| SQL name | DifProd | The database field name. |
| API identifier | fixedPriceDeviateProductNo | The API identifier used in GraphQL. |
| Number | 3053 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Product | FixedPriceDeviateProduct |
| ||
| Search product | FixedPriceDeviateSearchProduct |
|
General ledger P.E. amend days
How many days beyond the end of the period vouchers can be posted for general ledger.
An error message is generated when completing the fields if the number of days for the general ledger is lower than for the ledgers.
Voucher registration
When you enter the year and period or voucher reversal year and period in the batch head, either directly or indirectly via the value date/voucher reversal date, an error message is generated if the number of general ledger days is specified under company information, but the current date is more than this number of days beyond the accounting period’s to date.
When entering debit/credit account number in a voucher line, Business NXT will generate an error message if the field for the relevant account type is filled in under company information, and the current date is more than this number of days beyond the accounting period’s to date (based on the financial year and period in the voucher line, or in the batch head if they are not overridden in the voucher lines).
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Days | Integer |
| SQL name | GenDy | The database field name. |
| API identifier | generalLedgerAmendDays | The API identifier used in GraphQL. |
| Number | 8516 |
General note series
This voucher and document series is used as the document number for general notes.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | GenVoSr | The database field name. |
| API identifier | generalNoteVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 6971 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | GeneralNoteSeries |
|
Giro type
Defines Danish payment instructions for GIRO and FIK.
When sender and receiver are Danish, this field may be used to define payment instructions when invoicing through Visma.net AutoInvoice.
- 4 - Danish Inpayment Form type 4
- 15 - Danish Inpayment Form type 15
- 71 - Danish Inpayment Form type 71
- 75 - Danish Inpayment Form type 75
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is 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 | 16623 |
Group currency no.
If the company is part of a group which does its accounts in a currency other than that which is entered in the Currency no. field, you enter the group currency in the Group currency no. field.
Account statements, balance lists and profit and loss accounts and balance sheets can be presented in this currency.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Currency no. | Integer |
| SQL name | ConCur | The database field name. |
| API identifier | groupCurrencyNo | The API identifier used in GraphQL. |
| Number | 6901 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Currency | GroupCurrency |
|
IBAN
The company's IBAN account number.
IBAN (International Bank Account Number) is an international standard for account numbers, which you use in connection with payments to and from abroad. The IBAN account number is used when printing all documents for which you can retrieve fields from the Company information table.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Bank account | Text (35) |
| SQL name | IBAN | The database field name. |
| API identifier | ibanBic | The API identifier used in GraphQL. |
| Number | 13788 |
Incoming credit note series
The voucher series set here will be used on batches created when processing incoming credit notes. If not set, Incoming invoice series will be used.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | IncCrSr | The database field name. |
| API identifier | incomingCreditNoteVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 19606 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | IncomingCreditNoteVoucherSeries |
|
Incoming document pre-registration series
The pre-registration voucher series number.
This field is used for both the Order match pre-registration and Workflow pre-registration processes.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | OrdMaPRVoSr | The database field name. |
| API identifier | orderMatchPreRegVoucherSerieNo | The API identifier used in GraphQL. |
| Number | 17873 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | OrderMatchPreRegVoucherSeries |
|
Incoming invoice deviation tolerance %
Allowed deviation tolerance in % (based on the invoice amount) between the supplier invoice amount and the purchase order amount.
The allowed deviation tolerance in % (based on the invoice amount) between the supplier invoice amount and the purchase order amount in Business NXT. Automatic order match is performed if the deviation between both values is within the given tolerance %.
This field is used for order match functionality.
| 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 | 17817 |
Incoming invoice deviation tolerance amount
Allowed deviation tolerance amount between the supplier invoice amount and the purchase order amount.
The allowed deviation tolerance amount between the supplier invoice amount and the purchase order amount in Business NXT. Automatic order match is performed if the deviation between both values is less than the given amount.
This field is used for order match functionality.
| 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 | 17818 |
Incoming invoice series
The voucher series set here will be used on batches created when processing incoming invoices.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | IncVoSr | The database field name. |
| API identifier | incomingInvoiceVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 7187 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | IncomingInvoiceSeries |
|
Inquiry series
Under company information you enter references to voucher and document series for the various order documents.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | InqVoSr | The database field name. |
| API identifier | inquiryVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 5989 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | InquirySeries |
|
Interest days
This field states how many interest days Business NXT is to use in a year.
The interest rate is divided by this number and multiplied by the number of days between the from and to dates.
- 0 - 365/366
- Select this to use the exact number of days in the year, i.e. 365 days or 366 days for a leap year.
- 1 - 365
- Select this to use 365 days
- 2 - 360
- Select this to use 360 days (usual in Sweden)
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Interest days | Integer |
| SQL name | IntDy | The database field name. |
| API identifier | interestDays | The API identifier used in GraphQL. |
| Number | 6615 |
Interest income series
The field for interest income series is used when posting interest income.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | IntVoSr | The database field name. |
| API identifier | interestIncomeVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 2251 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | InterestIncomeSeries |
|
Interest note series
The interest note series is used as interest note number and as voucher number when posting interest notes.
Note that the value in the Voucher type field for the interest note series has a special significance. Business NXT will not calculate interest on entries for which the interest voucher type is used, unless compound interest is to be calculated for the customer (depending on the Compound interest field in the Country table and possibly the selection of Private person in the customer preference dialog box in the Associate table).
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | NoteVoSr | The database field name. |
| API identifier | interestNoteVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 2250 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | InterestNoteSeries |
|
Interest prod. no.
In this field you enter the interest product number you entered in the Product table. The interest product number is used when transferring interest on overdue payments to orders.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Product no. | Text (40) |
| SQL name | IntProd | The database field name. |
| API identifier | interestProductNo | The API identifier used in GraphQL. |
| Number | 11954 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Product | InterestProductNo |
| ||
| Search product | InterestSearchProductNo |
|
Interim cost account
This account number is used when running Update supplier transactions in the Batch table.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | IntCstAc | The database field name. |
| API identifier | interimCostAccount | The API identifier used in GraphQL. |
| Number | 18462 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | InterimCostAccount |
|
Internal invoice acc. no.
This is used by the processing for internal invoicing in the Product transaction table.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | IntInvAc | The database field name. |
| API identifier | internalInvoiceAccountNo | The API identifier used in GraphQL. |
| Number | 7213 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | InternalInvoiceAccount |
|
Internal invoice series
This field is used by the processing internal invoicing in the Product transaction table; see the system specification for logistics.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | IntInvVoS | The database field name. |
| API identifier | internalInvoiceVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 7212 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | InternalInvoiceSeries |
|
Inv. fee on credit notes
Will calculate an invoice fee on credit notes if you have filled in this field with one of the values.
- 1 - Debit
- The value causes the invoice fee to be debited (i.e. reduces the credit amount).
- 2 - Credit
- The value causes the invoice fee to be credited. (Business NXT decides on the basis of the order sum in the default currency whether it is a credit note.)
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Inv. fee on credit notes | Integer |
| SQL name | CrInvFee | The database field name. |
| API identifier | invoiceFeeOnCreditNotes | The API identifier used in GraphQL. |
| Number | 6614 |
Invoice free hire days
Weekdays for which customers are not to be invoiced for hire, for example Sundays and possibly Saturdays. These days will not be included when calculating the number of days of hire.
- Monday
- Tuesday
- Wednesday
- Thursday
- Friday
- Saturday
- Sunday
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Invoice free hire days | Integer |
| SQL name | FreeHire | The database field name. |
| API identifier | invoiceFreeHireDays | The API identifier used in GraphQL. |
| Number | 6288 |
Invoice note text no.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is 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 | 19610 |
Invoice ref. processing
Invoice reference processing.
If the field is filled in, Business NXT will, when you complete the Invoice reference field in the order head, add order lines which correspond to product transactions with this invoice reference as the invoice number.
The "Invoice ref. processing" field is also in the Order table. The value that you selected in the "Invoice ref. processing" field in the Order table overrides the value in the "Invoice ref. processing" field in the Company information table.
- 1 - Present original lines
- For 1 the signs are reversed for quantity and amount if you have checked credit note in the order head, and the first time for 2.
- 2 - Present original lines twice (-/+)
- If you have selected 2, the signs will be shown as in the original the second time, and the description fields will be shown in italics the first time (or not in italics if they were already in italics). Business NXT also inserts heading lines before each of the order line sets. The heading lines are given the texts Was and must be in the order language in the description field. The text is displayed in bold. You can override the texts in the Texts table with text type Heading texts and text numbers 7 and 8.
- 3 - Present original lines and exempt from warehousing
- 4 - Present original lines twice (-/+) and exempt from warehousing
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Invoice ref. processing | Integer |
| SQL name | InvRPro | The database field name. |
| API identifier | invoiceReferenceProcessing | The API identifier used in GraphQL. |
| Number | 8321 |
Invoice series
You can enter separate voucher and document series for outgoing invoices and credit notes.
The voucher and document series for invoices will be used for credit notes unless you have entered a separate voucher and document series for them and filled in the field for the next voucher number in this voucher and document series.
Nevertheless, using the Voucher table and the Document link table, you will be able to specify different voucher types for invoices and credit notes so that the vouchers can have different texts depending on whether they are invoices or credit notes.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | InvoVoSr | The database field name. |
| API identifier | invoiceVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 2472 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | InvoiceSeries |
|
Language no.
The language which is to be regarded as the domestic or default language.
Will use the parameter for this language unless a different language is defined in the Associate or Order table.
| 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 | 1986 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Language | Language |
|
Mandatory text types 1
These fields store choices you have made in the dialog box for the processing menu item for mandatory text types. The dialog box can also be activated by looking up in any of the fields.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Mandatory text types @ | Integer |
| SQL name | OblTxt1 | The database field name. |
| API identifier | mandatoryTextTypes1 | The API identifier used in GraphQL. |
| Number | 4794 |
Mandatory text types 2
These fields store choices you have made in the dialog box for the processing menu item for mandatory text types. The dialog box can also be activated by looking up in any of the fields.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Mandatory text types @ | Integer |
| SQL name | OblTxt2 | The database field name. |
| API identifier | mandatoryTextTypes2 | The API identifier used in GraphQL. |
| Number | 4795 |
Mandatory text types 3
These fields store choices you have made in the dialog box for the processing menu item for mandatory text types. The dialog box can also be activated by looking up in any of the fields.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Mandatory text types @ | Integer |
| SQL name | OblTxt3 | The database field name. |
| API identifier | mandatoryTextTypes3 | The API identifier used in GraphQL. |
| Number | 5708 |
Mandatory text types 4
These fields store choices you have made in the dialog box for the processing menu item for mandatory text types. The dialog box can also be activated by looking up in any of the fields.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Mandatory text types @ | Integer |
| SQL name | OblTxt4 | The database field name. |
| API identifier | mandatoryTextTypes4 | The API identifier used in GraphQL. |
| Number | 6010 |
Mandatory text types 5
These fields store choices you have made in the dialog box for the processing menu item for mandatory text types. The dialog box can also be activated by looking up in any of the fields.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Mandatory text types @ | Integer |
| SQL name | OblTxt5 | The database field name. |
| API identifier | mandatoryTextTypes5 | The API identifier used in GraphQL. |
| Number | 6011 |
Mandatory text types 6
These fields store choices you have made in the dialog box for the processing menu item for mandatory text types. The dialog box can also be activated by looking up in any of the fields.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Mandatory text types @ | Integer |
| SQL name | OblTxt6 | The database field name. |
| API identifier | mandatoryTextTypes6 | The API identifier used in GraphQL. |
| Number | 6012 |
Mandatory text types 7
These fields store choices you have made in the dialog box for the processing menu item for mandatory text types. The dialog box can also be activated by looking up in any of the fields.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Mandatory text types @ | Integer |
| SQL name | OblTxt7 | The database field name. |
| API identifier | mandatoryTextTypes7 | The API identifier used in GraphQL. |
| Number | 17588 |
Mandatory text types 8
These fields store choices you have made in the dialog box for the processing menu item for mandatory text types. The dialog box can also be activated by looking up in any of the fields.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Mandatory text types @ | Integer |
| SQL name | OblTxt8 | The database field name. |
| API identifier | mandatoryTextTypes8 | The API identifier used in GraphQL. |
| Number | 17589 |
Master org. unit flags
This field contains a dialog box in which you can select which organisational unit will be master and which organisational units will be affected by the master organisational unit.
The master organisational unit will then always overwrite values for the organisational units it will affect. It is possible to overwrite the values after the organisational units concerned have been retrieved. The master organisational unit also overwrites the organisational units concerned if they are retrieved via another organisational unit. Other organisational units are retrieved in the normal way if the field is not filled in. You must also register the master organisational unit in one of the tables R1-R12, according to the organisational unit you have selected as the master unit. You must then register the organisational units concerned in the table for the master organisational unit.
- Master org. unit 1
- Master org. unit 2
- Master org. unit 3
- Master org. unit 4
- Master org. unit 5
- Master org. unit 6
- Master org. unit 7
- Master org. unit 8
- Master org. unit 9
- Master org. unit 10
- Master org. unit 11
- Master org. unit 12
- Affects org. unit 1
- Affects org. unit 2
- Affects org. unit 3
- Affects org. unit 4
- Affects org. unit 5
- Affects org. unit 6
- Affects org. unit 7
- Affects org. unit 8
- Affects org. unit 9
- Affects org. unit 10
- Affects org. unit 11
- Affects org. unit 12
- Customer no. for the activity
- The customer number in the "Appointments" table will be suggested on the basis of the master organisational unit. The customer number will not be blanked out if the master organisational unit has not been filled in.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Master org. unit flags | Integer |
| SQL name | MstRspUF | The database field name. |
| API identifier | masterOrgUnitFlags | The API identifier used in GraphQL. |
| Number | 12368 |
Matching method
If you want Business NXT to provide an overview of open customer and supplier entries, with the facility to match entries against one another, issue reminders, calculate interest and debit or remit, you enter a value between 1 and 4 in this field to define the matching method.
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 | Yes | This field is visible by default in the table display. |
| Domain | Matching method | Integer |
| SQL name | MaMt | The database field name. |
| API identifier | matchingMethod | The API identifier used in GraphQL. |
| Number | 508 |
Max Curr. corr. %
The highest accepted currency correction amount as a percentage.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Percent | Decimal |
| SQL name | MaxCurCP | The database field name. |
| API identifier | maxCurrencyCorrectionPercent | The API identifier used in GraphQL. |
| Number | 11867 |
Max Curr. corr. am.
The highest accepted currency correction amount in the default currency.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Amount | Decimal |
| SQL name | MaxCurCA | The database field name. |
| API identifier | maxCurrencyCorrectionAmount | The API identifier used in GraphQL. |
| Number | 11868 |
Max. % of credit overdue
A percentage that will be used as a basis for testing for unpaid, overdue invoices.
You can override the value for the customers in the Associate table. 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.
The first message contains information on the customer number, percentage, total amount outstanding and credit limit. The second message contains information on the customer number, the number of invoices concerned, the stated number of days and the greatest number of days by which an invoice is overdue.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is 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 | 6368 |
Max. days overdue
A number of days that will be used as a basis for testing for unpaid/overdue invoices.
You can override the value for the customers in the Associate table. 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.
- None of the overdue invoices may be older than the number of days stated.
The first message contains information on the customer number, percentage, total amount outstanding and credit limit. The second message contains information on the customer number, the number of invoices concerned, the stated number of days and the greatest number of days by which an invoice is overdue.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is 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 | 6369 |
Maximum write off % cash discount
The maximum variance as an amount and a percentage that you will normally accept for depreciation, and which Business NXT will suggest for depreciation. Both criteria must be satisfied.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Percent | Decimal |
| SQL name | PmtVP | The database field name. |
| API identifier | maxWriteOffVariancePercentCashDiscount | The API identifier used in GraphQL. |
| Number | 8511 |
Maximum write off % misc.
This field is currently not in use.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Percent | Decimal |
| SQL name | PmtVP2 | The database field name. |
| API identifier | maxWriteOffPercentMisc | The API identifier used in GraphQL. |
| Number | 11035 |
Maximum write off amount cash discount
The maximum variance as an amount and a percentage that you will normally accept for depreciation, and which Business NXT will suggest for depreciation. Both criteria must be satisfied.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Amount | Decimal |
| SQL name | PmtVAm | The database field name. |
| API identifier | maxWriteOffVarianceAmountCashDiscount | The API identifier used in GraphQL. |
| Number | 8510 |
Maximum write off amount misc.
In this field you enter the maximum total write-off amount that you want to write off from the rest amount in the customer ledger when you use the facility for direct write-off of payment differences in connection with batch updates.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Amount | Decimal |
| SQL name | PmtVAm2 | The database field name. |
| API identifier | maxWriteOffAmountMisc | The API identifier used in GraphQL. |
| Number | 11034 |
Memo file name
In this field you can join to a memo page element, in which, for example, the accountant can write a comment for the company.
On the Editing menu, click Memo to create a new memo or to view the existing memo. The memo file name is saved in this text box.
Double-click or press * to open the Select file dialog box to manually select a memo file.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Memo file name | Text (260) |
| SQL name | MemoFNm | The database field name. |
| API identifier | memoFileName | The API identifier used in GraphQL. |
| Number | 14804 |
Memo no.
Link to the memo for the entry.
The actual memo is stored in the Memo table.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is 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 | 19248 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Memo | Memo |
|
Min. amount client interest
When you post a client interest proposal, the amount that you specified in the Min. amount client interest field is not produced.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Amount | Decimal |
| SQL name | MinCIntA | The database field name. |
| API identifier | minAmountClientInterest | The API identifier used in GraphQL. |
| Number | 13089 |
Min. margin
When saving an order, Business NXT gives a warning if the margin for the order is below the minimum limit you have stated in this field.
The warning is given in the same dialog box as any message on exceeding the credit limit.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Margin | Decimal |
| SQL name | MinMrg | The database field name. |
| API identifier | minMargin | The API identifier used in GraphQL. |
| Number | 6736 |
Miscellaneous series
Default series used when creating vouchers from misc. documents in Accounting document.
Lookup to Voucher series table. When set, the voucher series is used as default series when creating vouchers from misc. documents in Accounting document.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | MiscSr | The database field name. |
| API identifier | miscellaneousSeries | The API identifier used in GraphQL. |
| Number | 18565 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | MiscellaneousSeries |
|
Monthly VAT terms
Monthly intervals of for the tax terms.
The Monthly VAT terms control what you write in the From date/To date fields in the VAT period table, by pressing the "+" key. This means that if you write "1" in the Monthly VAT terms field, and you press the "+" key in the From date/To date fields in the VAT period table, the date field gets the values 01.01.2018 - 31.01.2018, 01.02.2018 - 28.02.2018 etc. If you write "3" in the Monthly VAT terms field, and you press the "+" key in the From date/To date fields in the VAT period table, the date fields get the values 01.01.2018 - 31.03.2018, 01.04.2018 - 30.06.2018 etc.
- 1 - Month
- 2 - 2 months
- 3 - 3 months
- 4 - 4 months
- 6 - 6 months
- 12 - 12 months
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Monthly VAT terms | Integer |
| SQL name | MTxTrm | The database field name. |
| API identifier | monthlyTaxTerms | The API identifier used in GraphQL. |
| Number | 6593 |
Next on + only
If you want to prevent users from being able to enter a number directly in the fields, you can specify the fields here.
If you have checked one or more fields, users only have to use the + key to be assigned the next available number.
- Order no.
- Customer no.
- Associate no.
- Supplier no.
- Employee no.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Next on + only | Integer |
| SQL name | NxtOrdNo | The database field name. |
| API identifier | onlyAutomaticAssignment | The API identifier used in GraphQL. |
| Number | 8187 |
No. of days +/- rejection
The number of days away from the current date before Business NXT rejects dates when you complete from/to dates, execution dates, order/transaction dates and voucher dates for appointments.
If you do not complete this field, Business NXT does not check the date you enter for appointments.
It will be natural to enter a higher number of days for rejection than for a warning. Rejection is checked first. There is no point in entering a higher number of days for a warning.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Days | Integer |
| SQL name | NoOfDyBl | The database field name. |
| API identifier | noOfDaysRejection | The API identifier used in GraphQL. |
| Number | 6738 |
No. of days +/- warning
The number of days away from the current date before Business NXT produces a warning when you complete from/to dates, execution dates, order/transaction dates and voucher dates for appointments. If you do not complete this field, Business NXT does not check the date you enter for appointments.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Days | Integer |
| SQL name | NoOfDy | The database field name. |
| API identifier | noOfDaysWarning | The API identifier used in GraphQL. |
| Number | 4520 |
Non-delivery days
Days on which Business NXT is not to suggest delivery.
When Business NXT calculates confirmed delivery dates in sales order lines and arrival/departure dates in purchase order lines, it can move them forwards to the next working day if they fall on a day which is not a working day.
In the dialog box for the field for non-delivery days you can check weekdays on which Business NXT is not to suggest delivery, for example Saturday and Sunday. You can also check whether Business NXT is to examine the Holiday table.
Moveable holidays
Looking up in the Extent field in the Holiday table leads to a dialog box in which you can, among other things, check if delivery dates are not to be suggested in the date interval in the row. This is provided that the row is not limited to a specific associate (and that both from and to dates are filled in).
- Monday
- Tuesday
- Wednesday
- Thursday
- Friday
- Saturday
- Sunday
- Holidays
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Non-delivery days | Integer |
| SQL name | DelFree | The database field name. |
| API identifier | nonDeliveryDays | The API identifier used in GraphQL. |
| Number | 6460 |
Number of approval steps
Lists how many levels of approvers to use, when approval flow is set by Business NXT.
The first line approver will always be chosen regardless of any attestation amount limits set on the approver in the Employee table, while the next levels will be set according to their set amount limits in Employee table.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | No. | Integer |
| SQL name | NoAppStp | The database field name. |
| API identifier | numberOfApprovalSteps | The API identifier used in GraphQL. |
| Number | 19086 |
Number of decimals in qty
This field is currently not in use.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Number of decimals in qty | Integer |
| SQL name | QtyDcm | The database field name. |
| API identifier | noOfDecimalsInQuantity | The API identifier used in GraphQL. |
| Number | 8501 |
OCR account bank
The general ledger account number defined in the account plan. The account number for OCR bank is used for OCR loading.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | OCRAcB | The database field name. |
| API identifier | ocrAccountNoBank | The API identifier used in GraphQL. |
| Number | 3689 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | OcrAccountBank |
|
OCR account post
The general ledger account number defined in the account plan. The account number for OCR post is used for OCR loading.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | OCRAcP | The database field name. |
| API identifier | ocrAccountNoPost | The API identifier used in GraphQL. |
| Number | 3690 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | OcrAccountPost |
|
OCR series
The voucher and document series for OCR is used when generating OCR batches.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | OCRVoSr | The database field name. |
| API identifier | ocrVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 1971 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | OcrSeries |
|
Only one shipment
This function is not supported in new installations with version 4.60, so you cannot edit the field. The field is only checked if this function has been used in previous versions.
Old function description:
You can check here if there is to be only one shipment per product number/warehouse number combination, with shipment number 1.
Business NXT then uses this shipment number regardless for both stock increases and stock reductions, and reject completion of the fields for shipment number and transferred to shipment number in the order lines and in the Reservation table with values other than 1 (deletion of the contents of the fields is still permitted.)
Business NXT will reject completion of the field with a check if there are already shipments with shipment numbers other than 1.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Boolean | Integer |
| SQL name | OneShp | The database field name. |
| API identifier | onlyOneShipment | The API identifier used in GraphQL. |
| Number | 8150 |
Order attachment processing
A lookup in the field leads to a dialog box for defining default values for the Order attachment processing field in Order attachment table. Used when adding new attachments to an order.
Attach to order documents
- Invoices/credit notes
- The attachment will be printed together with invoices/credit notes.
- Consignment notes
- The attachment will be printed together with consignment notes.
- Packing slips
- The attachment will be printed together with packing slips.
- Pick lists
- The attachment will be printed together with pick lists.
- Order confirmations
- The attachment will be printed together with order confirmations.
- Quotations
- The attachment will be printed together with quotations.
- Purchase orders
- The attachment will be printed together with purchase orders.
- Approval requests
- The attachment will be printed together with Approval request order document types.
- Inquiries
- The attachment will be printed together with inquiries.
- Production orders
- The attachment will be printed together with production orders.
- Order prints
- The attachment will be printed together with order prints.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Order attachment processing | Integer |
| SQL name | OrdAttProc | The database field name. |
| API identifier | orderAttachmentProcessing | The API identifier used in GraphQL. |
| Number | 16536 |
Order confirmation series
When printing order documents, Business NXT will assign the orders document numbers in accordance with the next voucher number in the voucher and document series for the type of document concerned.
An error message is produced if you try to print order documents without series having been stated for them.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | CfVoSr | The database field name. |
| API identifier | orderConfirmationVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 5987 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | OrderConfirmationSeries |
|
Order processing 1
Settings defining the behaviour of the orders.
Scan-document
- Copy scan document from prod to sales order
- Scan doc. no. is copied from the product to the sales order line and to the product transaction.
- Copy scan document from prod to purchase order
- Scan doc. no. is copied from the product to the sales order line and to the purchase order line. From the purchase order line it is transferred to the shipment and product transaction
- Copy scan document from prod to other orders
- Scan doc. no. is copied from the product to order lines with an order type other than sale and purchase, and from there to product transactions.
- Copy scan document from purchase to sales order
- Scan doc. no. is copied
from the shipment to the sales order line and later to the product
transaction.Note:This field is not compatible with Copy scan document from prod to sales order and Copy scan document from prod to other orders.
Firstly get account set from
- Invoice customer / Supplier
- The account set will be fetched from the invoice customer or supplier when you enter an order. This is the default option. If the account set is filled in from before, the value will not be overwritten.
- Customer
- The account set will be fetched from the customer when you enter an order.
- Stock
- The account set will be fetched from the stock when you enter an order.
- Structure
- The account set will be fetched from the structure when you enter an order.
- Employee
- The account set will be fetched from the employee when you enter an order.
- Organisational units
- The account set will be fetched from the organisation units when you enter an order.
Entry rules
- Reduplicate from order head to order lines when storing
- The Order
and Order line
tables have several fields that are identical. During order entry these fields are
copied from the order head to the order line. The values copied appear in blue on the
order lines. If you select Reduplicate from order head to order lines when storing, this means that fields that are blue on the order lines will be copied once more
from the order head when saving. This means that if you change the order head, you
also change the order line. Fields that are overridden, and that are displayed in
black, are not affected. Fields containing dates are also not duplicated.Note:Order lines with organisational units that have been transferred from the Appointment table are given a flag in the Dupl. fields 1 and Dupl. fields 2 fields, which means that the field is manually overridden and will therefore not be affected by the selection in the Reduplicate from order head to order lines when storing field.
- Trade area and VAT code from deliv. assoc. no.
- Trade area and VAT code will be imported from the associate entered in the Delivery associate no. field.
- Trade area and VAT from EU should not override local VAT
- This check box only functions together with the selection Trade area and VAT code from deliv. assoc. no. If you have checked these two fields, Business NXT will calculate the VAT from the Delivery associate no. when invoicing.
- Do not overwrite organisational units on order head
- When entering Cust. no. or Sup. no. on an order, the default result is that the organisational units are copied from the Associate, overwriting values set on the order. When Do not overwrite organisational units on order head is set, an organisational unit field that has already been set on the order will not be overwritten if the organisational unit in the Associate table is empty.
- Do not change qty when changing supplier on order line
- If you have entered a production order and changed the supplier number, the delivery number will not be re-imported from the supplier alternative. With changes of this kind, the quantity registered first on the production order will be kept.
- Set total quantity to finished quantity
- More goods than the number given on an order can be accepted.
Similarly, you can finish more than the number recorded on a sales order. The
Total quantity
is then set in the Order line table to the
quantity you entered as finished. If, in the Finish NOW field on a
sales order, you finish more than the outstanding volume in the Quantity field on the
order line, the quantity in the Incurred field is
increased correspondingly. The Inc. cost
field is correct, both on the Order line and in the Product transaction table.Note:You cannot use the Finished dialog box to finish more than the rest amount in the Quantity field, even if the parameter Set total quantity to finished quantity has been defined.
Special processing (common)
- Use Visma XML format
- The Visma XML format will be used.
- Calculate incurred cost on invoice plan
- Incurred costs will not be totalled one more time to ensure that the correct values are totalled for the order head. This is only for use in orders with an invoice plan.
- Do not print cancelled lines on order document
- The product lines will not appear on the order confirmations or purchase orders if they have been cancelled.
- One step production
- An invoice receipt for a production order is carried out even if
production is not finished. This means that the cost price is not
updated.Note:If you use production orders in the usual way, this field should not be checked.
- Customer product no.
- When selected, Business NXT will suggest customer's Product no. from the Product customer table for the Trans. information 2 field in the order lines. Both Cust. no. and Product no. must be entered for customer's Product no. to be suggested.
- Pre-registration incoming documents
- If enabled then a non-updated batch with one voucher will be created when an order matched invoice is transferred from Visma Document Center. Voucher series used will be fetched from the field Incoming document pre-registration series in the Company information table. This voucher series must have a voucher type given and the debit account from the voucher type will be used as debit account on the voucher (credit account if the invoice transferred is a credit invoice). Supplier account no will be used as cross account.
- Reverse the pre-registration for order match when rejecting invoice
- If enabled then when rejecting an order matched invoice a non-updated batch is be created that reverses the pre-registration batch that has been previously created.
- Do not tolerate any deviation
- If enabled then regardless of how small a deviation in price and amount is the order line will be flagged as outside deviation tolerance. Also, this option needs to be disabled in order for the values in the Incoming invoice deviation tolerance % and Incoming invoice deviation tolerance amount fields to be considered in the calculation of order line deviations.
- Order match automatic invoice receive
- Enables the automatic invoice receive of those order lines that have been order matched and are inside deviation tolerance. This flag and Pre-registration incoming documents cannot be simultaneously enabled.
- No partial invoice receival for order match
- If enabled then the automatic invoice receive is performed only in the
case that all the order lines of an order matched invoice are inside tolerance level.
This flag is checked by the order match processing only if it is simultaneously
enabled in the Order match automatic invoice receive flag under the Order processing 2
field in the Company information table.Note:It is normally recommended to enable this setting to avoid creating multiple vouchers for the same invoice.
- Order match on totals with order booking
- Accumulate gross weight to finished weight
- If enabled, the Order field Finished weight will be updated automatically, accumulated from Gross weight. Finished weight is used to calculate freight, based on settings under Transp. agr. processing and the Transport agreement table.
Shipments
- Do not fill up negative shipments
- Negative shipments will not be filled up first when goods are received.
- No selection on warehouse/product on shipment lookup
- A lookup in the Shipment table from the Order line table takes
into account the Product no. and Warehouse no. fields on the
order line. To prevent this, select this field. Business NXT will then display all shipments during lookups from the Order line table,
regardless of whether you have specified a product/warehouse selection or not. If you
have selected this field and perform a lookup to the Shipment table, you will copy the
values in the Product no., Shipment no. and Warehouse no. fields from
the Shipment table to the
Order line
table. If there are reservations on the shipment, you will get an error message
stating that you cannot alter "Product no.", "Shipment no." or "Warehouse no.". If
Transaction type on the order line = 1 - Sales, Business NXT will also check whether there is a quantity in the Available stock field for the
shipment. Transaction type will be checked in the following sequence:
- The order line
- Order head
- If there is "Trans. type" for both, the Order line will be selected
- Keep shipments
- Shipments are deleted when they reach 0, i.e. when the realised stock, unrealised stock increase and reserved quantity are all 0. If you check Keep shipments, Business NXT will restore shipments if required, for example in connection with crediting. Business NXT will then be able to include information from the invoice transaction. If shipments are deleted when they are no longer required, the processing time is reduced when Business NXT runs through them in FIFO order. In addition, the storage space required is reduced. If, for example, you have a few fixed shipments per product/warehouse combination and you do not need to distinguish between them over time with changing shipment numbers, there is no reason for Business NXT to spend time creating and deleting them repeatedly. They can just as well be kept. Moreover, no information will be lost if the values in all the fields in the shipments are stored. If you use invoice references in connection with crediting, the FIFO order will also be preserved.
- Insert separated shipments before
- When set, any shipments created using the Separate processing in the Shipment table, will be added before the original shipment. For example, if you use Separate to create a new shipment from shipment no 1, the separated shipment will be created as shipment no 1 and the original will be shipment no 2.
Warehouse product and direct order
As order type 2 - Direct order does not use warehouse handling (including picking, reservation, finishing), you have the option to warn or block the user if creating a direct order using a product which is not exempt from warehousing. The warning is given as a status message when the product no is entered.
- Ignore message
- No status message is displayed when the combination of order type 2 - Direct order and product with warehousing is used.
- Warning message
- A status message warning is displayed about the combination of order type 2 - Direct order and product with warehousing being used.
- Blocked
- The entered product no is removed, while a status message warning is displayed about the combination of order type 2 - Direct order and product with warehousing being used.
Stock balances
- Save finished number in stock balance table
- The Finished field in the Stock balance table will be updated with the number counted on finishing and reduced on invoicing of sales orders. By saving this value you can calculate the amount of goods you have on the shelves. To get this to work, you must create a calculated column. You create calculated columns in the Calculated column table.
- Check stock balance for counting in progress
- For stocktaking and where you have set processing method on the order line to add shipments with negative availability, you must also set the parameter to check the Stock balance table for products subject to stocktaking. You do this because if this option is not checked, Business NXT will add a negative shipment even if the product is subject to stocktaking. This parameter is implemented in order to minimise stock errors on completion of a sales order.
- No lent in Countable Qty
- The products you have for loan should be counted when the countable quantity is calculated. Products for loan are part of the physical stock and will normally be included.
- No hired products in Countable Qty
- Hired products are not included when the countable quantity is calculated. Products for hire are part of the physical stock and will normally be included.
- Use order numbers for stock take
- Product transaction from stock take is by default created without order no. When this is set, the product transaction gets an order no and will be possible to track during stock reconciliation.
- Exclude capital assets from stock on purchase orders
- The Exempt from warehousing check box in the Order line table is selected when you enter the capital asset number on the sales order line.
- Warehouse from product
- The Normal warehouse field from the products will be suggested in the order lines and thus override the warehouse number in the order head.
- Account set from warehouse on order lines
- The Account set on the Order line will be fetched from the Warehouse no. instead of from the Order table if enabled.
Serial no.
- No serial no. with credit
- The serial number is not transferred from the reservation lines/order lines to the shipments on crediting.
- Update serial no. table on purchase
- Note:Business NXT updates the Serial no. table with product numbers, warehouse numbers and shipments from the purchase order. This allows a serial number to be queried on the basis of the product, warehouse and shipment number, because all transactions using this shipment store this data in the Product transaction table.Not in use.
Price
- Always overwrite price in price- disc.matrix
- If set, making changes to the Purchase price and/or Purchase discount fields in the Price- and discount matrix table, will
update the Cost price field correspondingly, and vice versa. Updating Cost price will not take Purchase discount fields into account when
updating Purchase price however, resulting in the updated Purchase price being a copy of the Cost price set. Note:If either Purchase price or Cost price fields are empty, entering a value in the other will cause the empty field to be updated automatically, regardless of this setting.
- Sort descending on min. qty. when getting price and discount
- Price and discount rows are sorted by the minimum quantity and not the lowest price and discount. If there are several rows with the same criteria, it is the smallest quantity and the first row with reductions that applies. This also applies for "additions" (negative discounts).
- Copy cost price and date after generating order
- Cost price and date are copied directly to the current sales order when you generate a purchase order.
- Fetch price on order line created by "time to next"
- Rows produced using the Time to next field in the Order line table perform a new lookup in the Price- and discount matrix table.
- Compute average cost price on order line
- Check this box if you want to set the cost price in the order line as a weighted average of the cost prices in the reservation lines. The value is set when you reserve or change cost prices for decrease order lines in the Reservation table. This is based on the reserved quantities and cost prices when the entire quantity on the order line is reserved. This field overrides the corresponding field under Proc. method in the Product table and is valid for all products.
- Cost prices in currency
- The supplier's currency number will be suggested as the cost currency
number in purchase orders.Note:When this setting is on and any stock has been handled in other than the default currency, it is not recommended to turn it off as this will cause differences with stock values. If the setting must be turned off for some reason, this is the recommended procedure:
- Correct stock balance to 0, using order with Transaction type = 4 - Adjustment/internal issue.
- Make sure that both stock balance and accounting is 0.
- Turn off Cost prices in currency.
- Rebuild stock balance using 4 - Adjustment/internal issue to set the correct cost prices in local currency.
Visualization
- Show approval dialog for cash order
- Enabling the approval dialog for cash orders is currently not supported in Business NXT.
- No cash order dialog
- Enabling the cash order dialog is currently not supported in Business NXT.
- Warning for empty order status
- A message will be displayed if the order has been saved with order status equal to 0.
- Dialog at finishing
- The processing in the order head for finishing will lead to a dialog box in which you can choose between finishing the entire order or entering a bar code, product number or transaction information 1 and quantity. If you do not select this field the processing will finish the entire order.
- Suppress warning for stock availability
- If you enter a Quantity on an Order line that exceeds what is available in stock, a warning is displayed by default. Enabling this setting suppresses the warning.
Special processing (invoice)
- Do not change sign when crediting
- If Credit note is selected in the order header, the opposite sign is used for the values typed in the quantity fields. This will not happen if this option is used. The purpose of this option is to ease the manual typing of order lines when the credit note has many positive and only one, or few, negative order lines.
- Rounding of VAT amount on order lines
- The VAT amount will be rounding-off of per order line and not on the
total, which may result in different VAT amounts being produced, depending on whether
you calculate on the net amount in total or per order line.Note:Rounding will ALWAYS be done UP, never down. This functionality is only to be used in British markets according to British rounding regulations.
- Invoice fee only on first invoice
- An invoice fee will only be added if the order is being invoiced for the first time.
- Disable invoice no. and date in dialog
- The system does not take account of the changes made to the invoice number and date in the Invoice received dialog box.
- Only one total line for VAT
- If you run an invoice with a special tax, the VAT on the special tax appears on a separate row on the invoice. If you check this field, all VAT rows are totalled to create one row on the invoice. The last VAT code in the text is used.
- Post addition
- Additions (i.e. negative discounts) will be separated from sales and posted separately in accordance with the account references in the VAT- and accounting information table.
- Document delivery method from invoice customer
- If enabled, the Document delivery method for invoices set on the Invoice customer no. is used for the sales order. All other document delivery methods are fetched from the associate in the Cust. no. field.
- No VAT on prepayment
- This option relates to the Create prepayment line processing in the Order table, and must be used if prepayment shall not include VAT. If you check this field, the prepayment line on the order will fetch amount from Order total gross instead of Order total net. This requires using a prepayment product without VAT handling.
- Create separate orders from Visma.net Expense
- If enabled the Split processing will be automatically started on the newly created order and new separate orders will be created for each customer from the initial sales order from Visma.net Expense. If not enabled, only one sales order is created. Use Transfer processing to move lines to existing orders or use Split processing manually to create new orders for each customer.
- Update stock decrease transactions on credit note
- Credit notes are now handled the same way as purchase orders when it
comes to cost handling. Note:The cost update might decrease the performance when invoicing credit notes.
- Remember document date until layout is closed
- If enabled, the document date in the Order printout dialogue will be used for the next printout if it deviates from todays date.
Transfer to order
- Do not read order lines when transferring appointments
- This selection is used in connection with On account invoicing of orders, where the order number has been entered for the appointment, so that hours that are transferred from appointment to order are entered on the correct order. When Business NXT has been in use for a while, transfers of orders with many order lines begin to take a long time. If you select the Do not read order lines when transferring appointments field, the order will not be read in on transfer from appointments, but processing of such orders will be much faster. This means that the order head totals will not be updated before the next invoicing or before resave is implemented, but the transfer is performed correctly.
- Default Yes in transfer dialog
- When you use the Transfer processing in the Order table, order lines are transferred where the Transferred to order no. field is filled in in the Order line table. If you uncheck the options Default Yes in transfer dialog or Default No in transfer dialog, a dialog box where you must confirm the transfer Yes or No will not appear.
- Default No in transfer dialog
- When you use the Transfer processing in the Order table, order lines are transferred where the Transferred to order no. field is filled in in the Order line table. If you uncheck the options Default Yes in transfer dialog or Default No in transfer dialog, a dialog box where you must confirm the transfer Yes or No will not appear.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Order processing 1 | Integer |
| SQL name | OrdPro | The database field name. |
| API identifier | orderProcessing1 | The API identifier used in GraphQL. |
| Number | 8276 |
Order processing 2
Settings defining the behaviour of the orders.
Scan-document
- Copy scan document from prod to sales order
- Scan doc. no. is copied from the product to the sales order line and to the product transaction.
- Copy scan document from prod to purchase order
- Scan doc. no. is copied from the product to the sales order line and to the purchase order line. From the purchase order line it is transferred to the shipment and product transaction
- Copy scan document from prod to other orders
- Scan doc. no. is copied from the product to order lines with an order type other than sale and purchase, and from there to product transactions.
- Copy scan document from purchase to sales order
- Scan doc. no. is copied
from the shipment to the sales order line and later to the product
transaction.Note:This field is not compatible with Copy scan document from prod to sales order and Copy scan document from prod to other orders.
Firstly get account set from
- Invoice customer / Supplier
- The account set will be fetched from the invoice customer or supplier when you enter an order. This is the default option. If the account set is filled in from before, the value will not be overwritten.
- Customer
- The account set will be fetched from the customer when you enter an order.
- Stock
- The account set will be fetched from the stock when you enter an order.
- Structure
- The account set will be fetched from the structure when you enter an order.
- Employee
- The account set will be fetched from the employee when you enter an order.
- Organisational units
- The account set will be fetched from the organisation units when you enter an order.
Entry rules
- Reduplicate from order head to order lines when storing
- The Order
and Order line
tables have several fields that are identical. During order entry these fields are
copied from the order head to the order line. The values copied appear in blue on the
order lines. If you select Reduplicate from order head to order lines when storing, this means that fields that are blue on the order lines will be copied once more
from the order head when saving. This means that if you change the order head, you
also change the order line. Fields that are overridden, and that are displayed in
black, are not affected. Fields containing dates are also not duplicated.Note:Order lines with organisational units that have been transferred from the Appointment table are given a flag in the Dupl. fields 1 and Dupl. fields 2 fields, which means that the field is manually overridden and will therefore not be affected by the selection in the Reduplicate from order head to order lines when storing field.
- Trade area and VAT code from deliv. assoc. no.
- Trade area and VAT code will be imported from the associate entered in the Delivery associate no. field.
- Trade area and VAT from EU should not override local VAT
- This check box only functions together with the selection Trade area and VAT code from deliv. assoc. no. If you have checked these two fields, Business NXT will calculate the VAT from the Delivery associate no. when invoicing.
- Do not overwrite organisational units on order head
- When entering Cust. no. or Sup. no. on an order, the default result is that the organisational units are copied from the Associate, overwriting values set on the order. When Do not overwrite organisational units on order head is set, an organisational unit field that has already been set on the order will not be overwritten if the organisational unit in the Associate table is empty.
- Do not change qty when changing supplier on order line
- If you have entered a production order and changed the supplier number, the delivery number will not be re-imported from the supplier alternative. With changes of this kind, the quantity registered first on the production order will be kept.
- Set total quantity to finished quantity
- More goods than the number given on an order can be accepted.
Similarly, you can finish more than the number recorded on a sales order. The
Total quantity
is then set in the Order line table to the
quantity you entered as finished. If, in the Finish NOW field on a
sales order, you finish more than the outstanding volume in the Quantity field on the
order line, the quantity in the Incurred field is
increased correspondingly. The Inc. cost
field is correct, both on the Order line and in the Product transaction table.Note:You cannot use the Finished dialog box to finish more than the rest amount in the Quantity field, even if the parameter Set total quantity to finished quantity has been defined.
Special processing (common)
- Use Visma XML format
- The Visma XML format will be used.
- Calculate incurred cost on invoice plan
- Incurred costs will not be totalled one more time to ensure that the correct values are totalled for the order head. This is only for use in orders with an invoice plan.
- Do not print cancelled lines on order document
- The product lines will not appear on the order confirmations or purchase orders if they have been cancelled.
- One step production
- An invoice receipt for a production order is carried out even if
production is not finished. This means that the cost price is not
updated.Note:If you use production orders in the usual way, this field should not be checked.
- Customer product no.
- When selected, Business NXT will suggest customer's Product no. from the Product customer table for the Trans. information 2 field in the order lines. Both Cust. no. and Product no. must be entered for customer's Product no. to be suggested.
- Pre-registration incoming documents
- If enabled then a non-updated batch with one voucher will be created when an order matched invoice is transferred from Visma Document Center. Voucher series used will be fetched from the field Incoming document pre-registration series in the Company information table. This voucher series must have a voucher type given and the debit account from the voucher type will be used as debit account on the voucher (credit account if the invoice transferred is a credit invoice). Supplier account no will be used as cross account.
- Reverse the pre-registration for order match when rejecting invoice
- If enabled then when rejecting an order matched invoice a non-updated batch is be created that reverses the pre-registration batch that has been previously created.
- Do not tolerate any deviation
- If enabled then regardless of how small a deviation in price and amount is the order line will be flagged as outside deviation tolerance. Also, this option needs to be disabled in order for the values in the Incoming invoice deviation tolerance % and Incoming invoice deviation tolerance amount fields to be considered in the calculation of order line deviations.
- Order match automatic invoice receive
- Enables the automatic invoice receive of those order lines that have been order matched and are inside deviation tolerance. This flag and Pre-registration incoming documents cannot be simultaneously enabled.
- No partial invoice receival for order match
- If enabled then the automatic invoice receive is performed only in the
case that all the order lines of an order matched invoice are inside tolerance level.
This flag is checked by the order match processing only if it is simultaneously
enabled in the Order match automatic invoice receive flag under the Order processing 2
field in the Company information table.Note:It is normally recommended to enable this setting to avoid creating multiple vouchers for the same invoice.
- Order match on totals with order booking
- Accumulate gross weight to finished weight
- If enabled, the Order field Finished weight will be updated automatically, accumulated from Gross weight. Finished weight is used to calculate freight, based on settings under Transp. agr. processing and the Transport agreement table.
Shipments
- Do not fill up negative shipments
- Negative shipments will not be filled up first when goods are received.
- No selection on warehouse/product on shipment lookup
- A lookup in the Shipment table from the Order line table takes
into account the Product no. and Warehouse no. fields on the
order line. To prevent this, select this field. Business NXT will then display all shipments during lookups from the Order line table,
regardless of whether you have specified a product/warehouse selection or not. If you
have selected this field and perform a lookup to the Shipment table, you will copy the
values in the Product no., Shipment no. and Warehouse no. fields from
the Shipment table to the
Order line
table. If there are reservations on the shipment, you will get an error message
stating that you cannot alter "Product no.", "Shipment no." or "Warehouse no.". If
Transaction type on the order line = 1 - Sales, Business NXT will also check whether there is a quantity in the Available stock field for the
shipment. Transaction type will be checked in the following sequence:
- The order line
- Order head
- If there is "Trans. type" for both, the Order line will be selected
- Keep shipments
- Shipments are deleted when they reach 0, i.e. when the realised stock, unrealised stock increase and reserved quantity are all 0. If you check Keep shipments, Business NXT will restore shipments if required, for example in connection with crediting. Business NXT will then be able to include information from the invoice transaction. If shipments are deleted when they are no longer required, the processing time is reduced when Business NXT runs through them in FIFO order. In addition, the storage space required is reduced. If, for example, you have a few fixed shipments per product/warehouse combination and you do not need to distinguish between them over time with changing shipment numbers, there is no reason for Business NXT to spend time creating and deleting them repeatedly. They can just as well be kept. Moreover, no information will be lost if the values in all the fields in the shipments are stored. If you use invoice references in connection with crediting, the FIFO order will also be preserved.
- Insert separated shipments before
- When set, any shipments created using the Separate processing in the Shipment table, will be added before the original shipment. For example, if you use Separate to create a new shipment from shipment no 1, the separated shipment will be created as shipment no 1 and the original will be shipment no 2.
Warehouse product and direct order
As order type 2 - Direct order does not use warehouse handling (including picking, reservation, finishing), you have the option to warn or block the user if creating a direct order using a product which is not exempt from warehousing. The warning is given as a status message when the product no is entered.
- Ignore message
- No status message is displayed when the combination of order type 2 - Direct order and product with warehousing is used.
- Warning message
- A status message warning is displayed about the combination of order type 2 - Direct order and product with warehousing being used.
- Blocked
- The entered product no is removed, while a status message warning is displayed about the combination of order type 2 - Direct order and product with warehousing being used.
Stock balances
- Save finished number in stock balance table
- The Finished field in the Stock balance table will be updated with the number counted on finishing and reduced on invoicing of sales orders. By saving this value you can calculate the amount of goods you have on the shelves. To get this to work, you must create a calculated column. You create calculated columns in the Calculated column table.
- Check stock balance for counting in progress
- For stocktaking and where you have set processing method on the order line to add shipments with negative availability, you must also set the parameter to check the Stock balance table for products subject to stocktaking. You do this because if this option is not checked, Business NXT will add a negative shipment even if the product is subject to stocktaking. This parameter is implemented in order to minimise stock errors on completion of a sales order.
- No lent in Countable Qty
- The products you have for loan should be counted when the countable quantity is calculated. Products for loan are part of the physical stock and will normally be included.
- No hired products in Countable Qty
- Hired products are not included when the countable quantity is calculated. Products for hire are part of the physical stock and will normally be included.
- Use order numbers for stock take
- Product transaction from stock take is by default created without order no. When this is set, the product transaction gets an order no and will be possible to track during stock reconciliation.
- Exclude capital assets from stock on purchase orders
- The Exempt from warehousing check box in the Order line table is selected when you enter the capital asset number on the sales order line.
- Warehouse from product
- The Normal warehouse field from the products will be suggested in the order lines and thus override the warehouse number in the order head.
- Account set from warehouse on order lines
- The Account set on the Order line will be fetched from the Warehouse no. instead of from the Order table if enabled.
Serial no.
- No serial no. with credit
- The serial number is not transferred from the reservation lines/order lines to the shipments on crediting.
- Update serial no. table on purchase
- Note:Business NXT updates the Serial no. table with product numbers, warehouse numbers and shipments from the purchase order. This allows a serial number to be queried on the basis of the product, warehouse and shipment number, because all transactions using this shipment store this data in the Product transaction table.Not in use.
Price
- Always overwrite price in price- disc.matrix
- If set, making changes to the Purchase price and/or Purchase discount fields in the Price- and discount matrix table, will
update the Cost price field correspondingly, and vice versa. Updating Cost price will not take Purchase discount fields into account when
updating Purchase price however, resulting in the updated Purchase price being a copy of the Cost price set. Note:If either Purchase price or Cost price fields are empty, entering a value in the other will cause the empty field to be updated automatically, regardless of this setting.
- Sort descending on min. qty. when getting price and discount
- Price and discount rows are sorted by the minimum quantity and not the lowest price and discount. If there are several rows with the same criteria, it is the smallest quantity and the first row with reductions that applies. This also applies for "additions" (negative discounts).
- Copy cost price and date after generating order
- Cost price and date are copied directly to the current sales order when you generate a purchase order.
- Fetch price on order line created by "time to next"
- Rows produced using the Time to next field in the Order line table perform a new lookup in the Price- and discount matrix table.
- Compute average cost price on order line
- Check this box if you want to set the cost price in the order line as a weighted average of the cost prices in the reservation lines. The value is set when you reserve or change cost prices for decrease order lines in the Reservation table. This is based on the reserved quantities and cost prices when the entire quantity on the order line is reserved. This field overrides the corresponding field under Proc. method in the Product table and is valid for all products.
- Cost prices in currency
- The supplier's currency number will be suggested as the cost currency
number in purchase orders.Note:When this setting is on and any stock has been handled in other than the default currency, it is not recommended to turn it off as this will cause differences with stock values. If the setting must be turned off for some reason, this is the recommended procedure:
- Correct stock balance to 0, using order with Transaction type = 4 - Adjustment/internal issue.
- Make sure that both stock balance and accounting is 0.
- Turn off Cost prices in currency.
- Rebuild stock balance using 4 - Adjustment/internal issue to set the correct cost prices in local currency.
Visualization
- Show approval dialog for cash order
- Enabling the approval dialog for cash orders is currently not supported in Business NXT.
- No cash order dialog
- Enabling the cash order dialog is currently not supported in Business NXT.
- Warning for empty order status
- A message will be displayed if the order has been saved with order status equal to 0.
- Dialog at finishing
- The processing in the order head for finishing will lead to a dialog box in which you can choose between finishing the entire order or entering a bar code, product number or transaction information 1 and quantity. If you do not select this field the processing will finish the entire order.
- Suppress warning for stock availability
- If you enter a Quantity on an Order line that exceeds what is available in stock, a warning is displayed by default. Enabling this setting suppresses the warning.
Special processing (invoice)
- Do not change sign when crediting
- If Credit note is selected in the order header, the opposite sign is used for the values typed in the quantity fields. This will not happen if this option is used. The purpose of this option is to ease the manual typing of order lines when the credit note has many positive and only one, or few, negative order lines.
- Rounding of VAT amount on order lines
- The VAT amount will be rounding-off of per order line and not on the
total, which may result in different VAT amounts being produced, depending on whether
you calculate on the net amount in total or per order line.Note:Rounding will ALWAYS be done UP, never down. This functionality is only to be used in British markets according to British rounding regulations.
- Invoice fee only on first invoice
- An invoice fee will only be added if the order is being invoiced for the first time.
- Disable invoice no. and date in dialog
- The system does not take account of the changes made to the invoice number and date in the Invoice received dialog box.
- Only one total line for VAT
- If you run an invoice with a special tax, the VAT on the special tax appears on a separate row on the invoice. If you check this field, all VAT rows are totalled to create one row on the invoice. The last VAT code in the text is used.
- Post addition
- Additions (i.e. negative discounts) will be separated from sales and posted separately in accordance with the account references in the VAT- and accounting information table.
- Document delivery method from invoice customer
- If enabled, the Document delivery method for invoices set on the Invoice customer no. is used for the sales order. All other document delivery methods are fetched from the associate in the Cust. no. field.
- No VAT on prepayment
- This option relates to the Create prepayment line processing in the Order table, and must be used if prepayment shall not include VAT. If you check this field, the prepayment line on the order will fetch amount from Order total gross instead of Order total net. This requires using a prepayment product without VAT handling.
- Create separate orders from Visma.net Expense
- If enabled the Split processing will be automatically started on the newly created order and new separate orders will be created for each customer from the initial sales order from Visma.net Expense. If not enabled, only one sales order is created. Use Transfer processing to move lines to existing orders or use Split processing manually to create new orders for each customer.
- Update stock decrease transactions on credit note
- Credit notes are now handled the same way as purchase orders when it
comes to cost handling. Note:The cost update might decrease the performance when invoicing credit notes.
- Remember document date until layout is closed
- If enabled, the document date in the Order printout dialogue will be used for the next printout if it deviates from todays date.
Transfer to order
- Do not read order lines when transferring appointments
- This selection is used in connection with On account invoicing of orders, where the order number has been entered for the appointment, so that hours that are transferred from appointment to order are entered on the correct order. When Business NXT has been in use for a while, transfers of orders with many order lines begin to take a long time. If you select the Do not read order lines when transferring appointments field, the order will not be read in on transfer from appointments, but processing of such orders will be much faster. This means that the order head totals will not be updated before the next invoicing or before resave is implemented, but the transfer is performed correctly.
- Default Yes in transfer dialog
- When you use the Transfer processing in the Order table, order lines are transferred where the Transferred to order no. field is filled in in the Order line table. If you uncheck the options Default Yes in transfer dialog or Default No in transfer dialog, a dialog box where you must confirm the transfer Yes or No will not appear.
- Default No in transfer dialog
- When you use the Transfer processing in the Order table, order lines are transferred where the Transferred to order no. field is filled in in the Order line table. If you uncheck the options Default Yes in transfer dialog or Default No in transfer dialog, a dialog box where you must confirm the transfer Yes or No will not appear.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Order processing 2 | Integer |
| SQL name | OrdPro2 | The database field name. |
| API identifier | orderProcessing2 | The API identifier used in GraphQL. |
| Number | 12178 |
Order processing 3
Scan-document
- Copy scan document from prod to sales order
- Scan doc. no. is copied from the product to the sales order line and to the product transaction.
- Copy scan document from prod to purchase order
- Scan doc. no. is copied from the product to the sales order line and to the purchase order line. From the purchase order line it is transferred to the shipment and product transaction
- Copy scan document from prod to other orders
- Scan doc. no. is copied from the product to order lines with an order type other than sale and purchase, and from there to product transactions.
- Copy scan document from purchase to sales order
- Scan doc. no. is copied
from the shipment to the sales order line and later to the product
transaction.Note:This field is not compatible with Copy scan document from prod to sales order and Copy scan document from prod to other orders.
Firstly get account set from
- Invoice customer / Supplier
- The account set will be fetched from the invoice customer or supplier when you enter an order. This is the default option. If the account set is filled in from before, the value will not be overwritten.
- Customer
- The account set will be fetched from the customer when you enter an order.
- Stock
- The account set will be fetched from the stock when you enter an order.
- Structure
- The account set will be fetched from the structure when you enter an order.
- Employee
- The account set will be fetched from the employee when you enter an order.
- Organisational units
- The account set will be fetched from the organisation units when you enter an order.
Entry rules
- Reduplicate from order head to order lines when storing
- The Order
and Order line
tables have several fields that are identical. During order entry these fields are
copied from the order head to the order line. The values copied appear in blue on the
order lines. If you select Reduplicate from order head to order lines when storing, this means that fields that are blue on the order lines will be copied once more
from the order head when saving. This means that if you change the order head, you
also change the order line. Fields that are overridden, and that are displayed in
black, are not affected. Fields containing dates are also not duplicated.Note:Order lines with organisational units that have been transferred from the Appointment table are given a flag in the Dupl. fields 1 and Dupl. fields 2 fields, which means that the field is manually overridden and will therefore not be affected by the selection in the Reduplicate from order head to order lines when storing field.
- Trade area and VAT code from deliv. assoc. no.
- Trade area and VAT code will be imported from the associate entered in the Delivery associate no. field.
- Trade area and VAT from EU should not override local VAT
- This check box only functions together with the selection Trade area and VAT code from deliv. assoc. no. If you have checked these two fields, Business NXT will calculate the VAT from the Delivery associate no. when invoicing.
- Do not overwrite organisational units on order head
- When entering Cust. no. or Sup. no. on an order, the default result is that the organisational units are copied from the Associate, overwriting values set on the order. When Do not overwrite organisational units on order head is set, an organisational unit field that has already been set on the order will not be overwritten if the organisational unit in the Associate table is empty.
- Do not change qty when changing supplier on order line
- If you have entered a production order and changed the supplier number, the delivery number will not be re-imported from the supplier alternative. With changes of this kind, the quantity registered first on the production order will be kept.
- Set total quantity to finished quantity
- More goods than the number given on an order can be accepted.
Similarly, you can finish more than the number recorded on a sales order. The
Total quantity
is then set in the Order line table to the
quantity you entered as finished. If, in the Finish NOW field on a
sales order, you finish more than the outstanding volume in the Quantity field on the
order line, the quantity in the Incurred field is
increased correspondingly. The Inc. cost
field is correct, both on the Order line and in the Product transaction table.Note:You cannot use the Finished dialog box to finish more than the rest amount in the Quantity field, even if the parameter Set total quantity to finished quantity has been defined.
Special processing (common)
- Use Visma XML format
- The Visma XML format will be used.
- Calculate incurred cost on invoice plan
- Incurred costs will not be totalled one more time to ensure that the correct values are totalled for the order head. This is only for use in orders with an invoice plan.
- Do not print cancelled lines on order document
- The product lines will not appear on the order confirmations or purchase orders if they have been cancelled.
- One step production
- An invoice receipt for a production order is carried out even if
production is not finished. This means that the cost price is not
updated.Note:If you use production orders in the usual way, this field should not be checked.
- Customer product no.
- When selected, Business NXT will suggest customer's Product no. from the Product customer table for the Trans. information 2 field in the order lines. Both Cust. no. and Product no. must be entered for customer's Product no. to be suggested.
- Pre-registration incoming documents
- If enabled then a non-updated batch with one voucher will be created when an order matched invoice is transferred from Visma Document Center. Voucher series used will be fetched from the field Incoming document pre-registration series in the Company information table. This voucher series must have a voucher type given and the debit account from the voucher type will be used as debit account on the voucher (credit account if the invoice transferred is a credit invoice). Supplier account no will be used as cross account.
- Reverse the pre-registration for order match when rejecting invoice
- If enabled then when rejecting an order matched invoice a non-updated batch is be created that reverses the pre-registration batch that has been previously created.
- Do not tolerate any deviation
- If enabled then regardless of how small a deviation in price and amount is the order line will be flagged as outside deviation tolerance. Also, this option needs to be disabled in order for the values in the Incoming invoice deviation tolerance % and Incoming invoice deviation tolerance amount fields to be considered in the calculation of order line deviations.
- Order match automatic invoice receive
- Enables the automatic invoice receive of those order lines that have been order matched and are inside deviation tolerance. This flag and Pre-registration incoming documents cannot be simultaneously enabled.
- No partial invoice receival for order match
- If enabled then the automatic invoice receive is performed only in the
case that all the order lines of an order matched invoice are inside tolerance level.
This flag is checked by the order match processing only if it is simultaneously
enabled in the Order match automatic invoice receive flag under the Order processing 2
field in the Company information table.Note:It is normally recommended to enable this setting to avoid creating multiple vouchers for the same invoice.
- Order match on totals with order booking
- Accumulate gross weight to finished weight
- If enabled, the Order field Finished weight will be updated automatically, accumulated from Gross weight. Finished weight is used to calculate freight, based on settings under Transp. agr. processing and the Transport agreement table.
Shipments
- Do not fill up negative shipments
- Negative shipments will not be filled up first when goods are received.
- No selection on warehouse/product on shipment lookup
- A lookup in the Shipment table from the Order line table takes
into account the Product no. and Warehouse no. fields on the
order line. To prevent this, select this field. Business NXT will then display all shipments during lookups from the Order line table,
regardless of whether you have specified a product/warehouse selection or not. If you
have selected this field and perform a lookup to the Shipment table, you will copy the
values in the Product no., Shipment no. and Warehouse no. fields from
the Shipment table to the
Order line
table. If there are reservations on the shipment, you will get an error message
stating that you cannot alter "Product no.", "Shipment no." or "Warehouse no.". If
Transaction type on the order line = 1 - Sales, Business NXT will also check whether there is a quantity in the Available stock field for the
shipment. Transaction type will be checked in the following sequence:
- The order line
- Order head
- If there is "Trans. type" for both, the Order line will be selected
- Keep shipments
- Shipments are deleted when they reach 0, i.e. when the realised stock, unrealised stock increase and reserved quantity are all 0. If you check Keep shipments, Business NXT will restore shipments if required, for example in connection with crediting. Business NXT will then be able to include information from the invoice transaction. If shipments are deleted when they are no longer required, the processing time is reduced when Business NXT runs through them in FIFO order. In addition, the storage space required is reduced. If, for example, you have a few fixed shipments per product/warehouse combination and you do not need to distinguish between them over time with changing shipment numbers, there is no reason for Business NXT to spend time creating and deleting them repeatedly. They can just as well be kept. Moreover, no information will be lost if the values in all the fields in the shipments are stored. If you use invoice references in connection with crediting, the FIFO order will also be preserved.
- Insert separated shipments before
- When set, any shipments created using the Separate processing in the Shipment table, will be added before the original shipment. For example, if you use Separate to create a new shipment from shipment no 1, the separated shipment will be created as shipment no 1 and the original will be shipment no 2.
Warehouse product and direct order
As order type 2 - Direct order does not use warehouse handling (including picking, reservation, finishing), you have the option to warn or block the user if creating a direct order using a product which is not exempt from warehousing. The warning is given as a status message when the product no is entered.
- Ignore message
- No status message is displayed when the combination of order type 2 - Direct order and product with warehousing is used.
- Warning message
- A status message warning is displayed about the combination of order type 2 - Direct order and product with warehousing being used.
- Blocked
- The entered product no is removed, while a status message warning is displayed about the combination of order type 2 - Direct order and product with warehousing being used.
Stock balances
- Save finished number in stock balance table
- The Finished field in the Stock balance table will be updated with the number counted on finishing and reduced on invoicing of sales orders. By saving this value you can calculate the amount of goods you have on the shelves. To get this to work, you must create a calculated column. You create calculated columns in the Calculated column table.
- Check stock balance for counting in progress
- For stocktaking and where you have set processing method on the order line to add shipments with negative availability, you must also set the parameter to check the Stock balance table for products subject to stocktaking. You do this because if this option is not checked, Business NXT will add a negative shipment even if the product is subject to stocktaking. This parameter is implemented in order to minimise stock errors on completion of a sales order.
- No lent in Countable Qty
- The products you have for loan should be counted when the countable quantity is calculated. Products for loan are part of the physical stock and will normally be included.
- No hired products in Countable Qty
- Hired products are not included when the countable quantity is calculated. Products for hire are part of the physical stock and will normally be included.
- Use order numbers for stock take
- Product transaction from stock take is by default created without order no. When this is set, the product transaction gets an order no and will be possible to track during stock reconciliation.
- Exclude capital assets from stock on purchase orders
- The Exempt from warehousing check box in the Order line table is selected when you enter the capital asset number on the sales order line.
- Warehouse from product
- The Normal warehouse field from the products will be suggested in the order lines and thus override the warehouse number in the order head.
- Account set from warehouse on order lines
- The Account set on the Order line will be fetched from the Warehouse no. instead of from the Order table if enabled.
Serial no.
- No serial no. with credit
- The serial number is not transferred from the reservation lines/order lines to the shipments on crediting.
- Update serial no. table on purchase
- Note:Business NXT updates the Serial no. table with product numbers, warehouse numbers and shipments from the purchase order. This allows a serial number to be queried on the basis of the product, warehouse and shipment number, because all transactions using this shipment store this data in the Product transaction table.Not in use.
Price
- Always overwrite price in price- disc.matrix
- If set, making changes to the Purchase price and/or Purchase discount fields in the Price- and discount matrix table, will
update the Cost price field correspondingly, and vice versa. Updating Cost price will not take Purchase discount fields into account when
updating Purchase price however, resulting in the updated Purchase price being a copy of the Cost price set. Note:If either Purchase price or Cost price fields are empty, entering a value in the other will cause the empty field to be updated automatically, regardless of this setting.
- Sort descending on min. qty. when getting price and discount
- Price and discount rows are sorted by the minimum quantity and not the lowest price and discount. If there are several rows with the same criteria, it is the smallest quantity and the first row with reductions that applies. This also applies for "additions" (negative discounts).
- Copy cost price and date after generating order
- Cost price and date are copied directly to the current sales order when you generate a purchase order.
- Fetch price on order line created by "time to next"
- Rows produced using the Time to next field in the Order line table perform a new lookup in the Price- and discount matrix table.
- Compute average cost price on order line
- Check this box if you want to set the cost price in the order line as a weighted average of the cost prices in the reservation lines. The value is set when you reserve or change cost prices for decrease order lines in the Reservation table. This is based on the reserved quantities and cost prices when the entire quantity on the order line is reserved. This field overrides the corresponding field under Proc. method in the Product table and is valid for all products.
- Cost prices in currency
- The supplier's currency number will be suggested as the cost currency
number in purchase orders.Note:When this setting is on and any stock has been handled in other than the default currency, it is not recommended to turn it off as this will cause differences with stock values. If the setting must be turned off for some reason, this is the recommended procedure:
- Correct stock balance to 0, using order with Transaction type = 4 - Adjustment/internal issue.
- Make sure that both stock balance and accounting is 0.
- Turn off Cost prices in currency.
- Rebuild stock balance using 4 - Adjustment/internal issue to set the correct cost prices in local currency.
Visualization
- Show approval dialog for cash order
- Enabling the approval dialog for cash orders is currently not supported in Business NXT.
- No cash order dialog
- Enabling the cash order dialog is currently not supported in Business NXT.
- Warning for empty order status
- A message will be displayed if the order has been saved with order status equal to 0.
- Dialog at finishing
- The processing in the order head for finishing will lead to a dialog box in which you can choose between finishing the entire order or entering a bar code, product number or transaction information 1 and quantity. If you do not select this field the processing will finish the entire order.
- Suppress warning for stock availability
- If you enter a Quantity on an Order line that exceeds what is available in stock, a warning is displayed by default. Enabling this setting suppresses the warning.
Special processing (invoice)
- Do not change sign when crediting
- If Credit note is selected in the order header, the opposite sign is used for the values typed in the quantity fields. This will not happen if this option is used. The purpose of this option is to ease the manual typing of order lines when the credit note has many positive and only one, or few, negative order lines.
- Rounding of VAT amount on order lines
- The VAT amount will be rounding-off of per order line and not on the
total, which may result in different VAT amounts being produced, depending on whether
you calculate on the net amount in total or per order line.Note:Rounding will ALWAYS be done UP, never down. This functionality is only to be used in British markets according to British rounding regulations.
- Invoice fee only on first invoice
- An invoice fee will only be added if the order is being invoiced for the first time.
- Disable invoice no. and date in dialog
- The system does not take account of the changes made to the invoice number and date in the Invoice received dialog box.
- Only one total line for VAT
- If you run an invoice with a special tax, the VAT on the special tax appears on a separate row on the invoice. If you check this field, all VAT rows are totalled to create one row on the invoice. The last VAT code in the text is used.
- Post addition
- Additions (i.e. negative discounts) will be separated from sales and posted separately in accordance with the account references in the VAT- and accounting information table.
- Document delivery method from invoice customer
- If enabled, the Document delivery method for invoices set on the Invoice customer no. is used for the sales order. All other document delivery methods are fetched from the associate in the Cust. no. field.
- No VAT on prepayment
- This option relates to the Create prepayment line processing in the Order table, and must be used if prepayment shall not include VAT. If you check this field, the prepayment line on the order will fetch amount from Order total gross instead of Order total net. This requires using a prepayment product without VAT handling.
- Create separate orders from Visma.net Expense
- If enabled the Split processing will be automatically started on the newly created order and new separate orders will be created for each customer from the initial sales order from Visma.net Expense. If not enabled, only one sales order is created. Use Transfer processing to move lines to existing orders or use Split processing manually to create new orders for each customer.
- Update stock decrease transactions on credit note
- Credit notes are now handled the same way as purchase orders when it
comes to cost handling. Note:The cost update might decrease the performance when invoicing credit notes.
- Remember document date until layout is closed
- If enabled, the document date in the Order printout dialogue will be used for the next printout if it deviates from todays date.
Transfer to order
- Do not read order lines when transferring appointments
- This selection is used in connection with On account invoicing of orders, where the order number has been entered for the appointment, so that hours that are transferred from appointment to order are entered on the correct order. When Business NXT has been in use for a while, transfers of orders with many order lines begin to take a long time. If you select the Do not read order lines when transferring appointments field, the order will not be read in on transfer from appointments, but processing of such orders will be much faster. This means that the order head totals will not be updated before the next invoicing or before resave is implemented, but the transfer is performed correctly.
- Default Yes in transfer dialog
- When you use the Transfer processing in the Order table, order lines are transferred where the Transferred to order no. field is filled in in the Order line table. If you uncheck the options Default Yes in transfer dialog or Default No in transfer dialog, a dialog box where you must confirm the transfer Yes or No will not appear.
- Default No in transfer dialog
- When you use the Transfer processing in the Order table, order lines are transferred where the Transferred to order no. field is filled in in the Order line table. If you uncheck the options Default Yes in transfer dialog or Default No in transfer dialog, a dialog box where you must confirm the transfer Yes or No will not appear.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Order processing 3 | Integer |
| SQL name | OrdPro3 | The database field name. |
| API identifier | orderProcessing3 | The API identifier used in GraphQL. |
| Number | 8277 |
Org. unit in order
An organisational unit class between 1 and 6. When completing the field for this organisational unit class in the order head, Business NXT will complete fields in the order head from the organisational unit. See the chapter on order entry in the system specification for logistics.
When you have entered an organisational unit in the Org. unit in order field, the EDI import takes this into account and retrieves the customer number from this organisational unit.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Organisational unit classes | Integer |
| SQL name | OrdRNo | The database field name. |
| API identifier | orgUnitInOrder | The API identifier used in GraphQL. |
| Number | 7199 |
Organisation no.
The company’s organisation number in the Norwegian Register of Business Enterprises in Brønnøysund.
| 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 | 498 |
Organisation type
The type of register the organisation is registered in.
This information can be used to comply with the Norwegian Regulation on accounting (Forskrift om bokføring) §5-1-2, that requires the word Foretaksregisteret to be stated on the invoice if the company is a limited company.
The field is added to the one of the standard invoice layouts that is distributed together with Business NXT. If you are using your own invoice layout, you can add the field by using the macro @Bedrift (Organisasjonstype).
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | String of length 50 | Text (50) |
| SQL name | OrgTp | The database field name. |
| API identifier | organizationType | The API identifier used in GraphQL. |
| Number | 16510 |
Organisational unit 1
Which organisational unit you want to use, for example Department.
See also: Organisational units
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Name | Text (80) |
| SQL name | R1Nm | The database field name. |
| API identifier | orgUnit1Name | The API identifier used in GraphQL. |
| Number | 512 |
Organisational unit 2
Which organisational unit you want to use, for example Department.
See also: Organisational units
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Name | Text (80) |
| SQL name | R2Nm | The database field name. |
| API identifier | orgUnit2Name | The API identifier used in GraphQL. |
| Number | 513 |
Organisational unit 3
Which organisational unit you want to use, for example Department.
See also: Organisational units
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Name | Text (80) |
| SQL name | R3Nm | The database field name. |
| API identifier | orgUnit3Name | The API identifier used in GraphQL. |
| Number | 514 |
Organisational unit 4
Which organisational unit you want to use, for example Department.
See also: Organisational units
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Name | Text (80) |
| SQL name | R4Nm | The database field name. |
| API identifier | orgUnit4Name | The API identifier used in GraphQL. |
| Number | 515 |
Organisational unit 5
Which organisational unit you want to use, for example Department.
See also: Organisational units
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Name | Text (80) |
| SQL name | R5Nm | The database field name. |
| API identifier | orgUnit5Name | The API identifier used in GraphQL. |
| Number | 516 |
Organisational unit 6
Which organisational unit you want to use, for example Department.
See also: Organisational units
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Name | Text (80) |
| SQL name | R6Nm | The database field name. |
| API identifier | orgUnit6Name | The API identifier used in GraphQL. |
| Number | 517 |
Organisational unit 7
Which organisational unit you want to use, for example Department.
See also: Organisational units
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Name | Text (80) |
| SQL name | R7Nm | The database field name. |
| API identifier | orgUnit7Name | The API identifier used in GraphQL. |
| Number | 9678 |
Organisational unit 8
Which organisational unit you want to use, for example Department.
See also: Organisational units
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Name | Text (80) |
| SQL name | R8Nm | The database field name. |
| API identifier | orgUnit8Name | The API identifier used in GraphQL. |
| Number | 9679 |
Organisational unit 9
Which organisational unit you want to use, for example Department.
See also: Organisational units
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Name | Text (80) |
| SQL name | R9Nm | The database field name. |
| API identifier | orgUnit9Name | The API identifier used in GraphQL. |
| Number | 9680 |
Organisational unit 10
Which organisational unit you want to use, for example Department.
See also: Organisational units
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Name | Text (80) |
| SQL name | R10Nm | The database field name. |
| API identifier | orgUnit10Name | The API identifier used in GraphQL. |
| Number | 9681 |
Organisational unit 11
Which organisational unit you want to use, for example Department.
See also: Organisational units
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Name | Text (80) |
| SQL name | R11Nm | The database field name. |
| API identifier | orgUnit11Name | The API identifier used in GraphQL. |
| Number | 9682 |
Organisational unit 12
Which organisational unit you want to use, for example Department.
See also: Organisational units
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Name | Text (80) |
| SQL name | R12Nm | The database field name. |
| API identifier | orgUnit12Name | The API identifier used in GraphQL. |
| Number | 9683 |
OSS VAT control account
The general ledger account number defined in the account plan.
The tax control account is used in conjunction with the end of tax terms. The amounts in the tax accounts are then transferred to this account.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | EsTxSetAc | The database field name. |
| API identifier | ossTaxControlAccountNo | The API identifier used in GraphQL. |
| Number | 17544 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | OssTaxControlAccount |
|
OSS VAT reg. no.
The Tax authority identifier for registration and reporting, that applies to non-established companies offering e-services, including electronic communication services to private individuals and non-business customers (B2C).
Foreign suppliers of electronic services to Norwegian consumers (B2C) are liable to collect and pay VAT to the Norwegian tax authorities.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Organisation no. | Text (24) |
| SQL name | EsTaxNo | The database field name. |
| API identifier | ossVatRegistrationNo | The API identifier used in GraphQL. |
| Number | 17541 |
OSS VAT statement series
The VAT statement series is used for vouchers produced when closing tax periods. i.e. approval of printed OSS VAT statements.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | EsTaxVoSr | The database field name. |
| API identifier | ossTaxStatementVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 17542 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | OssTaxStatementSeries |
|
Overdue entries
Business NXT will store overdue entries (i.e. with settlement status 3) in the Open customer entry table if the Overdue entries field contains a value between 1 and 4.
- 1 - Keep until interest computation
- 2 - Keep if customer is subject to interest
- 3 - Keep if entry is subject to interest
- 4 - Keep if customer or entry is subject to interest
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Overdue entries | Integer |
| SQL name | Ovr | The database field name. |
| API identifier | overdueEntries | The API identifier used in GraphQL. |
| Number | 2056 |
Packing slip series
Under company information you enter references to voucher and document series for the various order documents.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | PacVoSr | The database field name. |
| API identifier | packingSlipVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 5985 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | PackingSlipSeries |
|
Payment processing
CID code generating
- No leading zeros in customer/supp. no.
- The customer/supplier number parts in the CID codes will not be completed with leading zeros when the number of digits is less than that stated in the CID cust./suppl. chars. field. This is normally used together with the Length digit check box in Swedish payment transfer.
- Length digit
- A length digit will be included before the check digit which shows the last digit in the total number of characters in the CID code (including the length digit and check digit). (The length digit is also included in the check digit calculation.) This is used in Swedish postal giros, among other things.
- Finnish CID calculation
- Modulus 10 check digits will be replaced by the algorithm for Solo reference payments. This is used in Finland.
- Invoice no. first
The default CID code will be generated with the invoice number first. The order will then be as follows:
Invoice reference + Factoring ID + Customer number + Control digits.
The system will then produce a reversed CID code in connection with invoice printing and on importing OCR files. This enables the CID code to be imported in other accounting systems which expect an OCR with invoice number + customer number or receive OCR produced from accounting systems which have the invoice number before the customer number.
Note:You must not use this parameter together with No leading zeros in customer/supp. no.This field is also included in the Factoring company table and is activated when using Def. Factoring companys/CID code def.
- Use customer no. as CID
- You will only get the customer number and check digit in the CID code when you print invoices, interest notes and reminders.
- Use Invoice no. as CID
- You will only get the invoice number and check digit in the CID code when you print invoices, interest notes and reminders.
Payment suggestion
- Payment if giro no.
- Create payments only for transaction where Bank account or Postal giro is specified in Associate table, or Bank account is specified on the Open supplier entry.
- Use bank partner from supplier/customer
- Used as default value for the corresponding field in the Create payment suggestion processing dialog.
Processing when importing from EFT system
- Prepayment
- Some external EFT system processes OCR transactions for a specified series of advance payments that do not have open entries, but only advance orders that have not been invoiced. The order will be looked up and the suspension on the advance payment will be lifted when this payment is updated. You will find more about advance payments in the section about Advance payment.
- Update bank account
- Some EFT systems updates the bank account/postal giro for suppliers/customers if the format contains sufficient information to find suppliers/customers with an advanced search.
- Generate batch/vouchers for settlement
- The batch is created by the EFT system when the settlement is returned, and you cannot use the Create account batch processing in the Payment line table.
Control EFT system at payment
- Control CID when importing
- The CID code will be checked during data import.
- Control if invoice no. is in the CID field
- This field is used when the CID code field does not contain a complete CID code. This is common for payments from Sweden.
- Only show CID sum
- Only the sum per account is shown on the CID report.
Look up in open entries table
- Search in open customer entries
- Used by some EFT systems. Search for transactions will be done in the Open customer entry table.
- Search in customer transactions
- Used by some EFT systems. Search for transactions will be done in the Customer transaction table.
- Search in open supplier entries
- Used by some EFT systems. Search for transactions will be done in the Open supplier entry table.
- Search in supplier transactions
- Used by some EFT systems. Search for transactions will be done in the Supplier transaction table.
Matching rules
- Invoice no. = one invoice
- A search will be performed for invoice numbers in the invoice number field or the CID field in the file, and a row will be entered with the amount that has been paid.
- Transaction info = Sum invoice
- A search will be performed for invoice numbers from the text field in the file, and rows will be entered for the invoice numbers that are found. The outstanding amount will be entered as a separate row without a reference.
- Customer no. + Amount = One invoice
- A search will be performed for invoice numbers based on customer number in the customer number field or the CID field in the file. This rule will only add a row if the amount paid is equal to an open entry.
- Transaction info + Customer no. + Amount = Sum Invoice
- A search will be performed for all available invoices for customer numbers found in the text field in the field, and all the invoices will then be settled with the amount that has been paid.
- Account no. + Amount = Sum Invoice
- A search will be performed for all customers which have specified account numbers and open entries. The EFT system will then begin to settle the invoices that are found from the oldest invoice onwards.
Posting
- Bank transaction per date
- The bank transactions will be posted per date.
- Bank transaction per Archive reference/batch
- The bank transactions will be posted per archive reference/batch.
- Bank transaction per transaction reference
- The bank transactions will be posted per transaction reference.
- Post rest amount in own customer record when invoice reference is missing
- The outstanding amount will be posted if no references are found. If you have not selected this field, the outstanding amount will be settled against open entries according to the oldest date first.
- Post difference record per processed record
- Difference record per payment with a payment difference is produced.
- Use open entries table for difference record
- This field is not in use.
- Use Cross reference table when paying
- The Cross reference field is not used on the voucher line, but the Cross reference table is used instead when you are creating payments.
- Use cross reference table when receiving payments
- The Cross reference field is not used on the voucher line, but the Cross reference table is used instead when you retrieve OCR data.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Payment processing | Integer |
| SQL name | CIDProc | The database field name. |
| API identifier | paymentProcessing | The API identifier used in GraphQL. |
| Number | 6834 |
Payment series
The Payment series field is used when posting payment transfers.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | RmtVoSr | The database field name. |
| API identifier | remittanceVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 2253 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | RemittanceSeries |
|
Payment suggestion days
For calculation of the Payment due date up to field in the Create payment suggestion processing.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | No. | Integer |
| SQL name | PmtSugDy | The database field name. |
| API identifier | paymentSuggestionDays | The API identifier used in GraphQL. |
| Number | 18483 |
PDF Path
In the PDF Path field you define the directory where you want to store the PDF files. The PDF driver routine uses the report name as a suggestion for the file name. You can override this.
You can print out documents from accounts as PDF files
If you have defined a directory in the PDF Path field, Business NXT will place PDF file printouts in this directory. You can also specify the file name in Home/Print/Page setup under the File parameters tab in the Report name field. You can save the report name in the setup.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Data directory | Text (260) |
| SQL name | PDFPath | The database field name. |
| API identifier | pdfPath | The API identifier used in GraphQL. |
| Number | 11977 |
Per. Credit acc.
The default value for the cross-account for posting credits in accrual accounting.
When you register vouchers in the usual way, you use the Accrual accounting start, Accrual accounting end and Accrual accounting credit fields. The latter is a flag for which account on the voucher line is being accrued. Business NXT performs the following transactions when updating:
- The total amount is posted to the credit account that you created in the Company information/Accrual accounting credit table.
- The transaction is then posted to the period in the periods defined in the General ledger transaction table.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | PerCrAc | The database field name. |
| API identifier | periodizingCreditAccountNo | The API identifier used in GraphQL. |
| Number | 11998 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | PeriodizingCreditAccount |
|
Per. Debit acc.
The default value for the cross-account for posting debits in accrual accounting.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | PerDbAc | The database field name. |
| API identifier | periodizingDebitAccountNo | The API identifier used in GraphQL. |
| Number | 11997 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | PeriodizingDebitAccount |
|
Period voucher series
In the Period key table you can specify criteria for getting accrued vouchers when updating instead of having them expanded in the Voucher table. The accrual voucher is given a voucher number on the basis of what is specified in the Period voucher series field.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | PerVoSr | The database field name. |
| API identifier | periodVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 15524 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | PeriodSeries |
|
Period voucher type
In the Period key table you can specify criteria for getting accrued vouchers when updating instead of having them expanded in the Voucher table. The accrual voucher is given a voucher type on the basis of what is specified in the Period voucher type field.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | No. | Integer |
| SQL name | PerVoTp | The database field name. |
| API identifier | periodVoucherType | The API identifier used in GraphQL. |
| Number | 15525 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher type | VoucherTypeForPeriods |
|
Phone
The company’s 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 | 494 |
Pick list series
Under company information you enter references to voucher and document series for the various order documents.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | PicVoSr | The database field name. |
| API identifier | pickListVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 5986 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | PickListSeries |
|
Picture file name
The name (and path) of any picture file which is linked to the row.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is 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 | 8550 |
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 | 3791 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Postal address | PostalAddress |
|
Postal area
The company’s postal area.
The postal area comes up when you enter the post code.
| 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 | 493 |
Postal giro
The postal giro number of the company, which you can choose to edit out on giros and other printouts.
The field is also transferred in connection with electronic funds transfer.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is 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 | 497 |
Posting errors account
The general ledger account number for posting errors, as defined in the account plan.
The posting errors account (9999) is used when updating vouchers if an account reference is missing or if an account does not exist. For example, it might have been deleted after the vouchers or account reference were entered. Business NXT checks that the posting errors account is defined before it starts updating vouchers.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | ErrAc | The database field name. |
| API identifier | postingErrorsAccountNo | The API identifier used in GraphQL. |
| Number | 507 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | PostingErrorsAccount |
|
Prepayment product no.
This product is used by the Create prepayment line processing in the Order table.
- Exempt from warehousing
- Suppress: Product no. and Quantity
- Exclude from all documents except Invoices/credit notes
- Exclude If 0
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Product no. | Text (40) |
| SQL name | PreProd | The database field name. |
| API identifier | prepaymentProductNo | The API identifier used in GraphQL. |
| Number | 17975 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Product | PrepaymentProductNo |
|
Price protection proc.
This field is suggested in price refund lines in connection with logging price reductions or when you add new rows yourself, and determines which actions are to be performed when saving price refund lines for which the refund status has been changed to 2 (Confirmed).
Sales orders
- Update sales price
- Update cost price
Purchase orders
- Update purchase prices
- Update cost price
____
- Update shipments and produce transactions
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Price protection proc. | Integer |
| SQL name | PrRepP | The database field name. |
| API identifier | priceProtectionProcessing | The API identifier used in GraphQL. |
| Number | 6663 |
Price quantity extent
This field stores the selections made in the dialog box of the Price/discount processing choices under the "Common" tab in the "Price quantity extent" group.
See field explanation under the Price/discount processing field.
Getting price
- Price/discount on buyer
- The buyer (customer number) will be used instead of the invoice recipient when looking up in the price and discount matrix.
- Price refunds independent of stock
- Price rounding after discount
- Business NXT will round the price after discount to two decimals when calculating amounts in order lines. The fields for Price after discount and Price after discount (dom.) in the order lines will then also display two decimals as standard instead of floating decimals.
- Price factor for hire orders
- The order lines contain a Price factor field in which you can enter a factor by which Business NXT is to multiply the product of price and quantity when calculating line amounts. If you have checked Price factor for hire orders field , Business NXT will not multiply by the hire period when calculating line amounts and instead suggest the price factor on the basis of a table of price factors for various hire periods and only multiply by this factor.
- Cost price from the price and discount matrix if sold out
- Business NXT will use cost prices from the price and discount matrix in sales order lines instead of the physical Average cost price from the Stock balance table when the physical stock level is 0 or negative. The last FIFO cost price is retained when the stock level becomes 0 or negative. Business NXT will select the cost price for any supplier stated in the order line or in the order head. When you look up in the Stock balance table, Business NXT includes the normal supplier in the sales order line when the check is in place and the stock level is £0
Comparison date
In this field you define which date forms the basis of comparisons with the from and to dates in the Stock balance table (which states when the goods can be sold), and when referring to the Price- and discount matrix table:
- 0 - Today's date
- The current date will be used.
- 1 - Order/transaction date
- The transaction date in the order line is used, or the order date in the order head.
- 2 - Required/confirmed delivery date
- Business NXT will use the confirmed delivery date in the order line if it has been entered, possibly in the order head, or the required delivery date in the order line or the order head.
Price quantity extent
- Sales price
- Hire price
- Purchase price
- Cost price
Freight cost processing
- Ton rate 1
- Ton rate 2
- Ton rate 3
- Ton rate 4
- Cost 1
- Cost 2
- Cost 3
- Cost 4
Expenses
You check the dialog box if the freight fields from 1 - 4 in the Order table are to be calculated based on a ton rate or by cost.
- Calculate cost price addition from price after discount
- Calculate freight 1-4 based on price after discount
- Account debit/credit freight 1-4 and customs on purchase
- All freight and customs will be posted upon invoice receipt on the purchase order instead of at the time of sale. As before, the cost price of stock will increase with freight and customs, but at the time of sale this value will not be deducted; it is the cost price that will be posted.
Optimization parameters
- Consider empty/zero values for price calculations
Chain discounts
- Subtract discount 1 before discount 2
- If selected, Disc. % and Disc. amount is deducted before calculating discount 2.
- Subtract discount 1 before discount 3
- If selected, Disc. % and Disc. amount is deducted before calculating discount 3.
- Subtract discount 2 before discount 3
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 3.
- Subtract discount 1 before discount 4
- If selected, Disc. % and Disc. amount is deducted before calculating discount 4.
- Subtract discount 2 before discount 4
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 4.
- Subtract discount 3 before discount 4
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 4.
- Subtract discount 1 before discount 5
- If selected, Disc. % and Disc. amount is deducted before calculating discount 5.
- Subtract discount 2 before discount 5
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 5.
- Subtract discount 3 before discount 5
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 5.
- Subtract discount 4 before discount 5
- If selected, Disc. % 4 and Disc. amount 4 is deducted before calculating discount 5.
- Subtract discount 1 before discount 6
- If selected, Disc. % and Disc. amount is deducted before calculating discount 6.
- Subtract discount 2 before discount 6
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 6.
- Subtract discount 3 before discount 6
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 6.
- Subtract discount 4 before discount 6
- If selected, Disc. % 4 and Disc. amount 4 is deducted before calculating discount 6.
- Subtract discount 5 before discount 6
- If selected, Disc. % 5 and Disc. amount 5 is deducted before calculating discount 6.
Discount suggestion
There are two columns of check boxes. The first concerns the discount percentage, the second the discount amount. There are check boxes for each of the 5 pairs of sales discount percentages and amounts. The first pair of check boxes also concerns discount percentages and amounts for hire and purchasing.
% / Amount
- Suggest discount 1 percent
- Suggest discount 1 amount
- Suggest discount 2 percent
- Suggest discount 2 amount
- Suggest discount 3 percent
- Suggest discount 3 amount
- Suggest discount 4 percent
- Suggest discount 4 amount
- Suggest discount 5 percent
- Suggest discount 5 amount
- Search for price - discount amount
- Business NXT will deduct the discount amounts selected from the price in the row. Business NXT will otherwise search for discount amounts separately so that the discount amounts can be shown in different rows from the price and limited to other criteria. Business NXT will then select the highest possible discount amount for the criteria selected. The discount can have a maximum limit if you check the type of discount concerned in the dialog box for the field for fixed prices and discounts.
Prices/discount total field
In this field you can use as a basis totals for lines in the order with the same value in the Product price group 1 field. The Prices/disc. total field under Company information indicates the field on the order lines that is to be totalled. Looking up in this field leads to a dialog box with the following options:
(If you select "Quantity" 1, the quantity is not reduced by the value in the “Free quantity” field in the order line.)
The field is used by the Recalculate prices processing in order page elements and when correcting sales prices and discounts in sales order lines when saving price refund lines for which the refund status has been changed to 2 (Confirmed).
- 0 - (None)
- 1 - Quantity
- 2 - Quantity in base unit
- 3 - Length
- 4 - Area
- 5 - Volume
- 6 - Net weight
Customer- / Supplier- / other orders
Here you can select which criteria Business NXT is to search by in the price and discount matrix, in rows with no product number.
There are three columns of check boxes. The first relates to customer orders (sales, hire and loan), the middle one to supplier orders (purchase) and the last one to other orders (adjustments, goods consumed, production and stock transfers).
If you select as few options as possible in each column, the speed of references in the price matrix will increase, thereby also increasing the speed of order entry and the printing of price lists. When printing price lists, Business NXT starts with the selections in the customer column. Currencies includes testing in both the current currency (for sales, hire and purchase) and the cost currency.
The selections are stored in the Price/disc.-criteria 1 - Price/disc.-criteria 6 fields under Company information.
- Structure product no.
- Included in structure
- Product price group 1
- Product price group 2
- Product price group 3
- Warehouse no.
- Shipment no.
- Customer no.
- Customer price group 1
- Customer price group 2
- Customer price group 3
- Supplier no.
- Employee no.
- Employee price group
- Wage rate no.
- Order no.
- Order price group
- Post code
- Terms of delivery
- Delivery method
- Organisational unit 1
- Organisational unit 2
- Organisational unit 3
- Organisational unit 4
- Organisational unit 5
- Organisational unit 6
- Organisational unit 7
- Organisational unit 8
- Organisational unit 9
- Organisational unit 10
- Organisational unit 11
- Organisational unit 12
- Date
- Unit
- Quantity
- Price unit
- Quantity in base unit
- Length
- Area
- Volume
- Net weight
- Currency
- Gross prices
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Price quantity extent | Integer |
| SQL name | PrNoCst | The database field name. |
| API identifier | priceQuantityExtent | The API identifier used in GraphQL. |
| Number | 6398 |
Price/disc.-criteria 1
Here you can select which criteria Business NXT is to search by in the price and discount matrix, in rows with no product number.
This is the first row.
Getting price
- Price/discount on buyer
- The buyer (customer number) will be used instead of the invoice recipient when looking up in the price and discount matrix.
- Price refunds independent of stock
- Price rounding after discount
- Business NXT will round the price after discount to two decimals when calculating amounts in order lines. The fields for Price after discount and Price after discount (dom.) in the order lines will then also display two decimals as standard instead of floating decimals.
- Price factor for hire orders
- The order lines contain a Price factor field in which you can enter a factor by which Business NXT is to multiply the product of price and quantity when calculating line amounts. If you have checked Price factor for hire orders field , Business NXT will not multiply by the hire period when calculating line amounts and instead suggest the price factor on the basis of a table of price factors for various hire periods and only multiply by this factor.
- Cost price from the price and discount matrix if sold out
- Business NXT will use cost prices from the price and discount matrix in sales order lines instead of the physical Average cost price from the Stock balance table when the physical stock level is 0 or negative. The last FIFO cost price is retained when the stock level becomes 0 or negative. Business NXT will select the cost price for any supplier stated in the order line or in the order head. When you look up in the Stock balance table, Business NXT includes the normal supplier in the sales order line when the check is in place and the stock level is £0
Comparison date
In this field you define which date forms the basis of comparisons with the from and to dates in the Stock balance table (which states when the goods can be sold), and when referring to the Price- and discount matrix table:
- 0 - Today's date
- The current date will be used.
- 1 - Order/transaction date
- The transaction date in the order line is used, or the order date in the order head.
- 2 - Required/confirmed delivery date
- Business NXT will use the confirmed delivery date in the order line if it has been entered, possibly in the order head, or the required delivery date in the order line or the order head.
Price quantity extent
- Sales price
- Hire price
- Purchase price
- Cost price
Freight cost processing
- Ton rate 1
- Ton rate 2
- Ton rate 3
- Ton rate 4
- Cost 1
- Cost 2
- Cost 3
- Cost 4
Expenses
You check the dialog box if the freight fields from 1 - 4 in the Order table are to be calculated based on a ton rate or by cost.
- Calculate cost price addition from price after discount
- Calculate freight 1-4 based on price after discount
- Account debit/credit freight 1-4 and customs on purchase
- All freight and customs will be posted upon invoice receipt on the purchase order instead of at the time of sale. As before, the cost price of stock will increase with freight and customs, but at the time of sale this value will not be deducted; it is the cost price that will be posted.
Optimization parameters
- Consider empty/zero values for price calculations
Chain discounts
- Subtract discount 1 before discount 2
- If selected, Disc. % and Disc. amount is deducted before calculating discount 2.
- Subtract discount 1 before discount 3
- If selected, Disc. % and Disc. amount is deducted before calculating discount 3.
- Subtract discount 2 before discount 3
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 3.
- Subtract discount 1 before discount 4
- If selected, Disc. % and Disc. amount is deducted before calculating discount 4.
- Subtract discount 2 before discount 4
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 4.
- Subtract discount 3 before discount 4
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 4.
- Subtract discount 1 before discount 5
- If selected, Disc. % and Disc. amount is deducted before calculating discount 5.
- Subtract discount 2 before discount 5
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 5.
- Subtract discount 3 before discount 5
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 5.
- Subtract discount 4 before discount 5
- If selected, Disc. % 4 and Disc. amount 4 is deducted before calculating discount 5.
- Subtract discount 1 before discount 6
- If selected, Disc. % and Disc. amount is deducted before calculating discount 6.
- Subtract discount 2 before discount 6
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 6.
- Subtract discount 3 before discount 6
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 6.
- Subtract discount 4 before discount 6
- If selected, Disc. % 4 and Disc. amount 4 is deducted before calculating discount 6.
- Subtract discount 5 before discount 6
- If selected, Disc. % 5 and Disc. amount 5 is deducted before calculating discount 6.
Discount suggestion
There are two columns of check boxes. The first concerns the discount percentage, the second the discount amount. There are check boxes for each of the 5 pairs of sales discount percentages and amounts. The first pair of check boxes also concerns discount percentages and amounts for hire and purchasing.
% / Amount
- Suggest discount 1 percent
- Suggest discount 1 amount
- Suggest discount 2 percent
- Suggest discount 2 amount
- Suggest discount 3 percent
- Suggest discount 3 amount
- Suggest discount 4 percent
- Suggest discount 4 amount
- Suggest discount 5 percent
- Suggest discount 5 amount
- Search for price - discount amount
- Business NXT will deduct the discount amounts selected from the price in the row. Business NXT will otherwise search for discount amounts separately so that the discount amounts can be shown in different rows from the price and limited to other criteria. Business NXT will then select the highest possible discount amount for the criteria selected. The discount can have a maximum limit if you check the type of discount concerned in the dialog box for the field for fixed prices and discounts.
Prices/discount total field
In this field you can use as a basis totals for lines in the order with the same value in the Product price group 1 field. The Prices/disc. total field under Company information indicates the field on the order lines that is to be totalled. Looking up in this field leads to a dialog box with the following options:
(If you select "Quantity" 1, the quantity is not reduced by the value in the “Free quantity” field in the order line.)
The field is used by the Recalculate prices processing in order page elements and when correcting sales prices and discounts in sales order lines when saving price refund lines for which the refund status has been changed to 2 (Confirmed).
- 0 - (None)
- 1 - Quantity
- 2 - Quantity in base unit
- 3 - Length
- 4 - Area
- 5 - Volume
- 6 - Net weight
Customer- / Supplier- / other orders
Here you can select which criteria Business NXT is to search by in the price and discount matrix, in rows with no product number.
There are three columns of check boxes. The first relates to customer orders (sales, hire and loan), the middle one to supplier orders (purchase) and the last one to other orders (adjustments, goods consumed, production and stock transfers).
If you select as few options as possible in each column, the speed of references in the price matrix will increase, thereby also increasing the speed of order entry and the printing of price lists. When printing price lists, Business NXT starts with the selections in the customer column. Currencies includes testing in both the current currency (for sales, hire and purchase) and the cost currency.
The selections are stored in the Price/disc.-criteria 1 - Price/disc.-criteria 6 fields under Company information.
- Structure product no.
- Included in structure
- Product price group 1
- Product price group 2
- Product price group 3
- Warehouse no.
- Shipment no.
- Customer no.
- Customer price group 1
- Customer price group 2
- Customer price group 3
- Supplier no.
- Employee no.
- Employee price group
- Wage rate no.
- Order no.
- Order price group
- Post code
- Terms of delivery
- Delivery method
- Organisational unit 1
- Organisational unit 2
- Organisational unit 3
- Organisational unit 4
- Organisational unit 5
- Organisational unit 6
- Organisational unit 7
- Organisational unit 8
- Organisational unit 9
- Organisational unit 10
- Organisational unit 11
- Organisational unit 12
- Date
- Unit
- Quantity
- Price unit
- Quantity in base unit
- Length
- Area
- Volume
- Net weight
- Currency
- Gross prices
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Price/disc.-criteria 1 | Integer |
| SQL name | PrCrit | The database field name. |
| API identifier | priceAndDiscountCriteria1 | The API identifier used in GraphQL. |
| Number | 4780 |
Price/disc.-criteria 2
Here you can select which criteria Business NXT is to search by in the price and discount matrix, in rows with no product number.
This is the second row.
Getting price
- Price/discount on buyer
- The buyer (customer number) will be used instead of the invoice recipient when looking up in the price and discount matrix.
- Price refunds independent of stock
- Price rounding after discount
- Business NXT will round the price after discount to two decimals when calculating amounts in order lines. The fields for Price after discount and Price after discount (dom.) in the order lines will then also display two decimals as standard instead of floating decimals.
- Price factor for hire orders
- The order lines contain a Price factor field in which you can enter a factor by which Business NXT is to multiply the product of price and quantity when calculating line amounts. If you have checked Price factor for hire orders field , Business NXT will not multiply by the hire period when calculating line amounts and instead suggest the price factor on the basis of a table of price factors for various hire periods and only multiply by this factor.
- Cost price from the price and discount matrix if sold out
- Business NXT will use cost prices from the price and discount matrix in sales order lines instead of the physical Average cost price from the Stock balance table when the physical stock level is 0 or negative. The last FIFO cost price is retained when the stock level becomes 0 or negative. Business NXT will select the cost price for any supplier stated in the order line or in the order head. When you look up in the Stock balance table, Business NXT includes the normal supplier in the sales order line when the check is in place and the stock level is £0
Comparison date
In this field you define which date forms the basis of comparisons with the from and to dates in the Stock balance table (which states when the goods can be sold), and when referring to the Price- and discount matrix table:
- 0 - Today's date
- The current date will be used.
- 1 - Order/transaction date
- The transaction date in the order line is used, or the order date in the order head.
- 2 - Required/confirmed delivery date
- Business NXT will use the confirmed delivery date in the order line if it has been entered, possibly in the order head, or the required delivery date in the order line or the order head.
Price quantity extent
- Sales price
- Hire price
- Purchase price
- Cost price
Freight cost processing
- Ton rate 1
- Ton rate 2
- Ton rate 3
- Ton rate 4
- Cost 1
- Cost 2
- Cost 3
- Cost 4
Expenses
You check the dialog box if the freight fields from 1 - 4 in the Order table are to be calculated based on a ton rate or by cost.
- Calculate cost price addition from price after discount
- Calculate freight 1-4 based on price after discount
- Account debit/credit freight 1-4 and customs on purchase
- All freight and customs will be posted upon invoice receipt on the purchase order instead of at the time of sale. As before, the cost price of stock will increase with freight and customs, but at the time of sale this value will not be deducted; it is the cost price that will be posted.
Optimization parameters
- Consider empty/zero values for price calculations
Chain discounts
- Subtract discount 1 before discount 2
- If selected, Disc. % and Disc. amount is deducted before calculating discount 2.
- Subtract discount 1 before discount 3
- If selected, Disc. % and Disc. amount is deducted before calculating discount 3.
- Subtract discount 2 before discount 3
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 3.
- Subtract discount 1 before discount 4
- If selected, Disc. % and Disc. amount is deducted before calculating discount 4.
- Subtract discount 2 before discount 4
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 4.
- Subtract discount 3 before discount 4
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 4.
- Subtract discount 1 before discount 5
- If selected, Disc. % and Disc. amount is deducted before calculating discount 5.
- Subtract discount 2 before discount 5
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 5.
- Subtract discount 3 before discount 5
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 5.
- Subtract discount 4 before discount 5
- If selected, Disc. % 4 and Disc. amount 4 is deducted before calculating discount 5.
- Subtract discount 1 before discount 6
- If selected, Disc. % and Disc. amount is deducted before calculating discount 6.
- Subtract discount 2 before discount 6
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 6.
- Subtract discount 3 before discount 6
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 6.
- Subtract discount 4 before discount 6
- If selected, Disc. % 4 and Disc. amount 4 is deducted before calculating discount 6.
- Subtract discount 5 before discount 6
- If selected, Disc. % 5 and Disc. amount 5 is deducted before calculating discount 6.
Discount suggestion
There are two columns of check boxes. The first concerns the discount percentage, the second the discount amount. There are check boxes for each of the 5 pairs of sales discount percentages and amounts. The first pair of check boxes also concerns discount percentages and amounts for hire and purchasing.
% / Amount
- Suggest discount 1 percent
- Suggest discount 1 amount
- Suggest discount 2 percent
- Suggest discount 2 amount
- Suggest discount 3 percent
- Suggest discount 3 amount
- Suggest discount 4 percent
- Suggest discount 4 amount
- Suggest discount 5 percent
- Suggest discount 5 amount
- Search for price - discount amount
- Business NXT will deduct the discount amounts selected from the price in the row. Business NXT will otherwise search for discount amounts separately so that the discount amounts can be shown in different rows from the price and limited to other criteria. Business NXT will then select the highest possible discount amount for the criteria selected. The discount can have a maximum limit if you check the type of discount concerned in the dialog box for the field for fixed prices and discounts.
Prices/discount total field
In this field you can use as a basis totals for lines in the order with the same value in the Product price group 1 field. The Prices/disc. total field under Company information indicates the field on the order lines that is to be totalled. Looking up in this field leads to a dialog box with the following options:
(If you select "Quantity" 1, the quantity is not reduced by the value in the “Free quantity” field in the order line.)
The field is used by the Recalculate prices processing in order page elements and when correcting sales prices and discounts in sales order lines when saving price refund lines for which the refund status has been changed to 2 (Confirmed).
- 0 - (None)
- 1 - Quantity
- 2 - Quantity in base unit
- 3 - Length
- 4 - Area
- 5 - Volume
- 6 - Net weight
Customer- / Supplier- / other orders
Here you can select which criteria Business NXT is to search by in the price and discount matrix, in rows with no product number.
There are three columns of check boxes. The first relates to customer orders (sales, hire and loan), the middle one to supplier orders (purchase) and the last one to other orders (adjustments, goods consumed, production and stock transfers).
If you select as few options as possible in each column, the speed of references in the price matrix will increase, thereby also increasing the speed of order entry and the printing of price lists. When printing price lists, Business NXT starts with the selections in the customer column. Currencies includes testing in both the current currency (for sales, hire and purchase) and the cost currency.
The selections are stored in the Price/disc.-criteria 1 - Price/disc.-criteria 6 fields under Company information.
- Structure product no.
- Included in structure
- Product price group 1
- Product price group 2
- Product price group 3
- Warehouse no.
- Shipment no.
- Customer no.
- Customer price group 1
- Customer price group 2
- Customer price group 3
- Supplier no.
- Employee no.
- Employee price group
- Wage rate no.
- Order no.
- Order price group
- Post code
- Terms of delivery
- Delivery method
- Organisational unit 1
- Organisational unit 2
- Organisational unit 3
- Organisational unit 4
- Organisational unit 5
- Organisational unit 6
- Organisational unit 7
- Organisational unit 8
- Organisational unit 9
- Organisational unit 10
- Organisational unit 11
- Organisational unit 12
- Date
- Unit
- Quantity
- Price unit
- Quantity in base unit
- Length
- Area
- Volume
- Net weight
- Currency
- Gross prices
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Price/disc.-criteria 1 | Integer |
| SQL name | PrCrit2 | The database field name. |
| API identifier | priceAndDiscountCriteria2 | The API identifier used in GraphQL. |
| Number | 6671 |
Price/disc.-criteria 3
Here you can select which criteria Business NXT is to search by in the price and discount matrix, in rows with no product number.
This is the third row.
Getting price
- Price/discount on buyer
- The buyer (customer number) will be used instead of the invoice recipient when looking up in the price and discount matrix.
- Price refunds independent of stock
- Price rounding after discount
- Business NXT will round the price after discount to two decimals when calculating amounts in order lines. The fields for Price after discount and Price after discount (dom.) in the order lines will then also display two decimals as standard instead of floating decimals.
- Price factor for hire orders
- The order lines contain a Price factor field in which you can enter a factor by which Business NXT is to multiply the product of price and quantity when calculating line amounts. If you have checked Price factor for hire orders field , Business NXT will not multiply by the hire period when calculating line amounts and instead suggest the price factor on the basis of a table of price factors for various hire periods and only multiply by this factor.
- Cost price from the price and discount matrix if sold out
- Business NXT will use cost prices from the price and discount matrix in sales order lines instead of the physical Average cost price from the Stock balance table when the physical stock level is 0 or negative. The last FIFO cost price is retained when the stock level becomes 0 or negative. Business NXT will select the cost price for any supplier stated in the order line or in the order head. When you look up in the Stock balance table, Business NXT includes the normal supplier in the sales order line when the check is in place and the stock level is £0
Comparison date
In this field you define which date forms the basis of comparisons with the from and to dates in the Stock balance table (which states when the goods can be sold), and when referring to the Price- and discount matrix table:
- 0 - Today's date
- The current date will be used.
- 1 - Order/transaction date
- The transaction date in the order line is used, or the order date in the order head.
- 2 - Required/confirmed delivery date
- Business NXT will use the confirmed delivery date in the order line if it has been entered, possibly in the order head, or the required delivery date in the order line or the order head.
Price quantity extent
- Sales price
- Hire price
- Purchase price
- Cost price
Freight cost processing
- Ton rate 1
- Ton rate 2
- Ton rate 3
- Ton rate 4
- Cost 1
- Cost 2
- Cost 3
- Cost 4
Expenses
You check the dialog box if the freight fields from 1 - 4 in the Order table are to be calculated based on a ton rate or by cost.
- Calculate cost price addition from price after discount
- Calculate freight 1-4 based on price after discount
- Account debit/credit freight 1-4 and customs on purchase
- All freight and customs will be posted upon invoice receipt on the purchase order instead of at the time of sale. As before, the cost price of stock will increase with freight and customs, but at the time of sale this value will not be deducted; it is the cost price that will be posted.
Optimization parameters
- Consider empty/zero values for price calculations
Chain discounts
- Subtract discount 1 before discount 2
- If selected, Disc. % and Disc. amount is deducted before calculating discount 2.
- Subtract discount 1 before discount 3
- If selected, Disc. % and Disc. amount is deducted before calculating discount 3.
- Subtract discount 2 before discount 3
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 3.
- Subtract discount 1 before discount 4
- If selected, Disc. % and Disc. amount is deducted before calculating discount 4.
- Subtract discount 2 before discount 4
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 4.
- Subtract discount 3 before discount 4
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 4.
- Subtract discount 1 before discount 5
- If selected, Disc. % and Disc. amount is deducted before calculating discount 5.
- Subtract discount 2 before discount 5
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 5.
- Subtract discount 3 before discount 5
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 5.
- Subtract discount 4 before discount 5
- If selected, Disc. % 4 and Disc. amount 4 is deducted before calculating discount 5.
- Subtract discount 1 before discount 6
- If selected, Disc. % and Disc. amount is deducted before calculating discount 6.
- Subtract discount 2 before discount 6
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 6.
- Subtract discount 3 before discount 6
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 6.
- Subtract discount 4 before discount 6
- If selected, Disc. % 4 and Disc. amount 4 is deducted before calculating discount 6.
- Subtract discount 5 before discount 6
- If selected, Disc. % 5 and Disc. amount 5 is deducted before calculating discount 6.
Discount suggestion
There are two columns of check boxes. The first concerns the discount percentage, the second the discount amount. There are check boxes for each of the 5 pairs of sales discount percentages and amounts. The first pair of check boxes also concerns discount percentages and amounts for hire and purchasing.
% / Amount
- Suggest discount 1 percent
- Suggest discount 1 amount
- Suggest discount 2 percent
- Suggest discount 2 amount
- Suggest discount 3 percent
- Suggest discount 3 amount
- Suggest discount 4 percent
- Suggest discount 4 amount
- Suggest discount 5 percent
- Suggest discount 5 amount
- Search for price - discount amount
- Business NXT will deduct the discount amounts selected from the price in the row. Business NXT will otherwise search for discount amounts separately so that the discount amounts can be shown in different rows from the price and limited to other criteria. Business NXT will then select the highest possible discount amount for the criteria selected. The discount can have a maximum limit if you check the type of discount concerned in the dialog box for the field for fixed prices and discounts.
Prices/discount total field
In this field you can use as a basis totals for lines in the order with the same value in the Product price group 1 field. The Prices/disc. total field under Company information indicates the field on the order lines that is to be totalled. Looking up in this field leads to a dialog box with the following options:
(If you select "Quantity" 1, the quantity is not reduced by the value in the “Free quantity” field in the order line.)
The field is used by the Recalculate prices processing in order page elements and when correcting sales prices and discounts in sales order lines when saving price refund lines for which the refund status has been changed to 2 (Confirmed).
- 0 - (None)
- 1 - Quantity
- 2 - Quantity in base unit
- 3 - Length
- 4 - Area
- 5 - Volume
- 6 - Net weight
Customer- / Supplier- / other orders
Here you can select which criteria Business NXT is to search by in the price and discount matrix, in rows with no product number.
There are three columns of check boxes. The first relates to customer orders (sales, hire and loan), the middle one to supplier orders (purchase) and the last one to other orders (adjustments, goods consumed, production and stock transfers).
If you select as few options as possible in each column, the speed of references in the price matrix will increase, thereby also increasing the speed of order entry and the printing of price lists. When printing price lists, Business NXT starts with the selections in the customer column. Currencies includes testing in both the current currency (for sales, hire and purchase) and the cost currency.
The selections are stored in the Price/disc.-criteria 1 - Price/disc.-criteria 6 fields under Company information.
- Structure product no.
- Included in structure
- Product price group 1
- Product price group 2
- Product price group 3
- Warehouse no.
- Shipment no.
- Customer no.
- Customer price group 1
- Customer price group 2
- Customer price group 3
- Supplier no.
- Employee no.
- Employee price group
- Wage rate no.
- Order no.
- Order price group
- Post code
- Terms of delivery
- Delivery method
- Organisational unit 1
- Organisational unit 2
- Organisational unit 3
- Organisational unit 4
- Organisational unit 5
- Organisational unit 6
- Organisational unit 7
- Organisational unit 8
- Organisational unit 9
- Organisational unit 10
- Organisational unit 11
- Organisational unit 12
- Date
- Unit
- Quantity
- Price unit
- Quantity in base unit
- Length
- Area
- Volume
- Net weight
- Currency
- Gross prices
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Price/disc.-criteria 1 | Integer |
| SQL name | PrCrit3 | The database field name. |
| API identifier | priceAndDiscountCriteria3 | The API identifier used in GraphQL. |
| Number | 6672 |
Price/disc.-criteria 4
Here you can select which criteria Business NXT is to search by in the price and discount matrix, in rows with no product number.
This is the first row.
Getting price
- Price/discount on buyer
- The buyer (customer number) will be used instead of the invoice recipient when looking up in the price and discount matrix.
- Price refunds independent of stock
- Price rounding after discount
- Business NXT will round the price after discount to two decimals when calculating amounts in order lines. The fields for Price after discount and Price after discount (dom.) in the order lines will then also display two decimals as standard instead of floating decimals.
- Price factor for hire orders
- The order lines contain a Price factor field in which you can enter a factor by which Business NXT is to multiply the product of price and quantity when calculating line amounts. If you have checked Price factor for hire orders field , Business NXT will not multiply by the hire period when calculating line amounts and instead suggest the price factor on the basis of a table of price factors for various hire periods and only multiply by this factor.
- Cost price from the price and discount matrix if sold out
- Business NXT will use cost prices from the price and discount matrix in sales order lines instead of the physical Average cost price from the Stock balance table when the physical stock level is 0 or negative. The last FIFO cost price is retained when the stock level becomes 0 or negative. Business NXT will select the cost price for any supplier stated in the order line or in the order head. When you look up in the Stock balance table, Business NXT includes the normal supplier in the sales order line when the check is in place and the stock level is £0
Comparison date
In this field you define which date forms the basis of comparisons with the from and to dates in the Stock balance table (which states when the goods can be sold), and when referring to the Price- and discount matrix table:
- 0 - Today's date
- The current date will be used.
- 1 - Order/transaction date
- The transaction date in the order line is used, or the order date in the order head.
- 2 - Required/confirmed delivery date
- Business NXT will use the confirmed delivery date in the order line if it has been entered, possibly in the order head, or the required delivery date in the order line or the order head.
Price quantity extent
- Sales price
- Hire price
- Purchase price
- Cost price
Freight cost processing
- Ton rate 1
- Ton rate 2
- Ton rate 3
- Ton rate 4
- Cost 1
- Cost 2
- Cost 3
- Cost 4
Expenses
You check the dialog box if the freight fields from 1 - 4 in the Order table are to be calculated based on a ton rate or by cost.
- Calculate cost price addition from price after discount
- Calculate freight 1-4 based on price after discount
- Account debit/credit freight 1-4 and customs on purchase
- All freight and customs will be posted upon invoice receipt on the purchase order instead of at the time of sale. As before, the cost price of stock will increase with freight and customs, but at the time of sale this value will not be deducted; it is the cost price that will be posted.
Optimization parameters
- Consider empty/zero values for price calculations
Chain discounts
- Subtract discount 1 before discount 2
- If selected, Disc. % and Disc. amount is deducted before calculating discount 2.
- Subtract discount 1 before discount 3
- If selected, Disc. % and Disc. amount is deducted before calculating discount 3.
- Subtract discount 2 before discount 3
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 3.
- Subtract discount 1 before discount 4
- If selected, Disc. % and Disc. amount is deducted before calculating discount 4.
- Subtract discount 2 before discount 4
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 4.
- Subtract discount 3 before discount 4
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 4.
- Subtract discount 1 before discount 5
- If selected, Disc. % and Disc. amount is deducted before calculating discount 5.
- Subtract discount 2 before discount 5
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 5.
- Subtract discount 3 before discount 5
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 5.
- Subtract discount 4 before discount 5
- If selected, Disc. % 4 and Disc. amount 4 is deducted before calculating discount 5.
- Subtract discount 1 before discount 6
- If selected, Disc. % and Disc. amount is deducted before calculating discount 6.
- Subtract discount 2 before discount 6
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 6.
- Subtract discount 3 before discount 6
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 6.
- Subtract discount 4 before discount 6
- If selected, Disc. % 4 and Disc. amount 4 is deducted before calculating discount 6.
- Subtract discount 5 before discount 6
- If selected, Disc. % 5 and Disc. amount 5 is deducted before calculating discount 6.
Discount suggestion
There are two columns of check boxes. The first concerns the discount percentage, the second the discount amount. There are check boxes for each of the 5 pairs of sales discount percentages and amounts. The first pair of check boxes also concerns discount percentages and amounts for hire and purchasing.
% / Amount
- Suggest discount 1 percent
- Suggest discount 1 amount
- Suggest discount 2 percent
- Suggest discount 2 amount
- Suggest discount 3 percent
- Suggest discount 3 amount
- Suggest discount 4 percent
- Suggest discount 4 amount
- Suggest discount 5 percent
- Suggest discount 5 amount
- Search for price - discount amount
- Business NXT will deduct the discount amounts selected from the price in the row. Business NXT will otherwise search for discount amounts separately so that the discount amounts can be shown in different rows from the price and limited to other criteria. Business NXT will then select the highest possible discount amount for the criteria selected. The discount can have a maximum limit if you check the type of discount concerned in the dialog box for the field for fixed prices and discounts.
Prices/discount total field
In this field you can use as a basis totals for lines in the order with the same value in the Product price group 1 field. The Prices/disc. total field under Company information indicates the field on the order lines that is to be totalled. Looking up in this field leads to a dialog box with the following options:
(If you select "Quantity" 1, the quantity is not reduced by the value in the “Free quantity” field in the order line.)
The field is used by the Recalculate prices processing in order page elements and when correcting sales prices and discounts in sales order lines when saving price refund lines for which the refund status has been changed to 2 (Confirmed).
- 0 - (None)
- 1 - Quantity
- 2 - Quantity in base unit
- 3 - Length
- 4 - Area
- 5 - Volume
- 6 - Net weight
Customer- / Supplier- / other orders
Here you can select which criteria Business NXT is to search by in the price and discount matrix, in rows with no product number.
There are three columns of check boxes. The first relates to customer orders (sales, hire and loan), the middle one to supplier orders (purchase) and the last one to other orders (adjustments, goods consumed, production and stock transfers).
If you select as few options as possible in each column, the speed of references in the price matrix will increase, thereby also increasing the speed of order entry and the printing of price lists. When printing price lists, Business NXT starts with the selections in the customer column. Currencies includes testing in both the current currency (for sales, hire and purchase) and the cost currency.
The selections are stored in the Price/disc.-criteria 1 - Price/disc.-criteria 6 fields under Company information.
- Structure product no.
- Included in structure
- Product price group 1
- Product price group 2
- Product price group 3
- Warehouse no.
- Shipment no.
- Customer no.
- Customer price group 1
- Customer price group 2
- Customer price group 3
- Supplier no.
- Employee no.
- Employee price group
- Wage rate no.
- Order no.
- Order price group
- Post code
- Terms of delivery
- Delivery method
- Organisational unit 1
- Organisational unit 2
- Organisational unit 3
- Organisational unit 4
- Organisational unit 5
- Organisational unit 6
- Organisational unit 7
- Organisational unit 8
- Organisational unit 9
- Organisational unit 10
- Organisational unit 11
- Organisational unit 12
- Date
- Unit
- Quantity
- Price unit
- Quantity in base unit
- Length
- Area
- Volume
- Net weight
- Currency
- Gross prices
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Price/disc.-criteria 2 | Integer |
| SQL name | PrCrit21 | The database field name. |
| API identifier | priceAndDiscountCriteria4 | The API identifier used in GraphQL. |
| Number | 7207 |
Price/disc.-criteria 5
Here you can select which criteria Business NXT is to search by in the price and discount matrix, in rows with no product number.
This is the second row.
Getting price
- Price/discount on buyer
- The buyer (customer number) will be used instead of the invoice recipient when looking up in the price and discount matrix.
- Price refunds independent of stock
- Price rounding after discount
- Business NXT will round the price after discount to two decimals when calculating amounts in order lines. The fields for Price after discount and Price after discount (dom.) in the order lines will then also display two decimals as standard instead of floating decimals.
- Price factor for hire orders
- The order lines contain a Price factor field in which you can enter a factor by which Business NXT is to multiply the product of price and quantity when calculating line amounts. If you have checked Price factor for hire orders field , Business NXT will not multiply by the hire period when calculating line amounts and instead suggest the price factor on the basis of a table of price factors for various hire periods and only multiply by this factor.
- Cost price from the price and discount matrix if sold out
- Business NXT will use cost prices from the price and discount matrix in sales order lines instead of the physical Average cost price from the Stock balance table when the physical stock level is 0 or negative. The last FIFO cost price is retained when the stock level becomes 0 or negative. Business NXT will select the cost price for any supplier stated in the order line or in the order head. When you look up in the Stock balance table, Business NXT includes the normal supplier in the sales order line when the check is in place and the stock level is £0
Comparison date
In this field you define which date forms the basis of comparisons with the from and to dates in the Stock balance table (which states when the goods can be sold), and when referring to the Price- and discount matrix table:
- 0 - Today's date
- The current date will be used.
- 1 - Order/transaction date
- The transaction date in the order line is used, or the order date in the order head.
- 2 - Required/confirmed delivery date
- Business NXT will use the confirmed delivery date in the order line if it has been entered, possibly in the order head, or the required delivery date in the order line or the order head.
Price quantity extent
- Sales price
- Hire price
- Purchase price
- Cost price
Freight cost processing
- Ton rate 1
- Ton rate 2
- Ton rate 3
- Ton rate 4
- Cost 1
- Cost 2
- Cost 3
- Cost 4
Expenses
You check the dialog box if the freight fields from 1 - 4 in the Order table are to be calculated based on a ton rate or by cost.
- Calculate cost price addition from price after discount
- Calculate freight 1-4 based on price after discount
- Account debit/credit freight 1-4 and customs on purchase
- All freight and customs will be posted upon invoice receipt on the purchase order instead of at the time of sale. As before, the cost price of stock will increase with freight and customs, but at the time of sale this value will not be deducted; it is the cost price that will be posted.
Optimization parameters
- Consider empty/zero values for price calculations
Chain discounts
- Subtract discount 1 before discount 2
- If selected, Disc. % and Disc. amount is deducted before calculating discount 2.
- Subtract discount 1 before discount 3
- If selected, Disc. % and Disc. amount is deducted before calculating discount 3.
- Subtract discount 2 before discount 3
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 3.
- Subtract discount 1 before discount 4
- If selected, Disc. % and Disc. amount is deducted before calculating discount 4.
- Subtract discount 2 before discount 4
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 4.
- Subtract discount 3 before discount 4
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 4.
- Subtract discount 1 before discount 5
- If selected, Disc. % and Disc. amount is deducted before calculating discount 5.
- Subtract discount 2 before discount 5
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 5.
- Subtract discount 3 before discount 5
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 5.
- Subtract discount 4 before discount 5
- If selected, Disc. % 4 and Disc. amount 4 is deducted before calculating discount 5.
- Subtract discount 1 before discount 6
- If selected, Disc. % and Disc. amount is deducted before calculating discount 6.
- Subtract discount 2 before discount 6
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 6.
- Subtract discount 3 before discount 6
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 6.
- Subtract discount 4 before discount 6
- If selected, Disc. % 4 and Disc. amount 4 is deducted before calculating discount 6.
- Subtract discount 5 before discount 6
- If selected, Disc. % 5 and Disc. amount 5 is deducted before calculating discount 6.
Discount suggestion
There are two columns of check boxes. The first concerns the discount percentage, the second the discount amount. There are check boxes for each of the 5 pairs of sales discount percentages and amounts. The first pair of check boxes also concerns discount percentages and amounts for hire and purchasing.
% / Amount
- Suggest discount 1 percent
- Suggest discount 1 amount
- Suggest discount 2 percent
- Suggest discount 2 amount
- Suggest discount 3 percent
- Suggest discount 3 amount
- Suggest discount 4 percent
- Suggest discount 4 amount
- Suggest discount 5 percent
- Suggest discount 5 amount
- Search for price - discount amount
- Business NXT will deduct the discount amounts selected from the price in the row. Business NXT will otherwise search for discount amounts separately so that the discount amounts can be shown in different rows from the price and limited to other criteria. Business NXT will then select the highest possible discount amount for the criteria selected. The discount can have a maximum limit if you check the type of discount concerned in the dialog box for the field for fixed prices and discounts.
Prices/discount total field
In this field you can use as a basis totals for lines in the order with the same value in the Product price group 1 field. The Prices/disc. total field under Company information indicates the field on the order lines that is to be totalled. Looking up in this field leads to a dialog box with the following options:
(If you select "Quantity" 1, the quantity is not reduced by the value in the “Free quantity” field in the order line.)
The field is used by the Recalculate prices processing in order page elements and when correcting sales prices and discounts in sales order lines when saving price refund lines for which the refund status has been changed to 2 (Confirmed).
- 0 - (None)
- 1 - Quantity
- 2 - Quantity in base unit
- 3 - Length
- 4 - Area
- 5 - Volume
- 6 - Net weight
Customer- / Supplier- / other orders
Here you can select which criteria Business NXT is to search by in the price and discount matrix, in rows with no product number.
There are three columns of check boxes. The first relates to customer orders (sales, hire and loan), the middle one to supplier orders (purchase) and the last one to other orders (adjustments, goods consumed, production and stock transfers).
If you select as few options as possible in each column, the speed of references in the price matrix will increase, thereby also increasing the speed of order entry and the printing of price lists. When printing price lists, Business NXT starts with the selections in the customer column. Currencies includes testing in both the current currency (for sales, hire and purchase) and the cost currency.
The selections are stored in the Price/disc.-criteria 1 - Price/disc.-criteria 6 fields under Company information.
- Structure product no.
- Included in structure
- Product price group 1
- Product price group 2
- Product price group 3
- Warehouse no.
- Shipment no.
- Customer no.
- Customer price group 1
- Customer price group 2
- Customer price group 3
- Supplier no.
- Employee no.
- Employee price group
- Wage rate no.
- Order no.
- Order price group
- Post code
- Terms of delivery
- Delivery method
- Organisational unit 1
- Organisational unit 2
- Organisational unit 3
- Organisational unit 4
- Organisational unit 5
- Organisational unit 6
- Organisational unit 7
- Organisational unit 8
- Organisational unit 9
- Organisational unit 10
- Organisational unit 11
- Organisational unit 12
- Date
- Unit
- Quantity
- Price unit
- Quantity in base unit
- Length
- Area
- Volume
- Net weight
- Currency
- Gross prices
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Price/disc.-criteria 2 | Integer |
| SQL name | PrCrit22 | The database field name. |
| API identifier | priceAndDiscountCriteria5 | The API identifier used in GraphQL. |
| Number | 7208 |
Price/disc.-criteria 6
Here you can select which criteria Business NXT is to search by in the price and discount matrix, in rows with no product number.
This is the third row.
Getting price
- Price/discount on buyer
- The buyer (customer number) will be used instead of the invoice recipient when looking up in the price and discount matrix.
- Price refunds independent of stock
- Price rounding after discount
- Business NXT will round the price after discount to two decimals when calculating amounts in order lines. The fields for Price after discount and Price after discount (dom.) in the order lines will then also display two decimals as standard instead of floating decimals.
- Price factor for hire orders
- The order lines contain a Price factor field in which you can enter a factor by which Business NXT is to multiply the product of price and quantity when calculating line amounts. If you have checked Price factor for hire orders field , Business NXT will not multiply by the hire period when calculating line amounts and instead suggest the price factor on the basis of a table of price factors for various hire periods and only multiply by this factor.
- Cost price from the price and discount matrix if sold out
- Business NXT will use cost prices from the price and discount matrix in sales order lines instead of the physical Average cost price from the Stock balance table when the physical stock level is 0 or negative. The last FIFO cost price is retained when the stock level becomes 0 or negative. Business NXT will select the cost price for any supplier stated in the order line or in the order head. When you look up in the Stock balance table, Business NXT includes the normal supplier in the sales order line when the check is in place and the stock level is £0
Comparison date
In this field you define which date forms the basis of comparisons with the from and to dates in the Stock balance table (which states when the goods can be sold), and when referring to the Price- and discount matrix table:
- 0 - Today's date
- The current date will be used.
- 1 - Order/transaction date
- The transaction date in the order line is used, or the order date in the order head.
- 2 - Required/confirmed delivery date
- Business NXT will use the confirmed delivery date in the order line if it has been entered, possibly in the order head, or the required delivery date in the order line or the order head.
Price quantity extent
- Sales price
- Hire price
- Purchase price
- Cost price
Freight cost processing
- Ton rate 1
- Ton rate 2
- Ton rate 3
- Ton rate 4
- Cost 1
- Cost 2
- Cost 3
- Cost 4
Expenses
You check the dialog box if the freight fields from 1 - 4 in the Order table are to be calculated based on a ton rate or by cost.
- Calculate cost price addition from price after discount
- Calculate freight 1-4 based on price after discount
- Account debit/credit freight 1-4 and customs on purchase
- All freight and customs will be posted upon invoice receipt on the purchase order instead of at the time of sale. As before, the cost price of stock will increase with freight and customs, but at the time of sale this value will not be deducted; it is the cost price that will be posted.
Optimization parameters
- Consider empty/zero values for price calculations
Chain discounts
- Subtract discount 1 before discount 2
- If selected, Disc. % and Disc. amount is deducted before calculating discount 2.
- Subtract discount 1 before discount 3
- If selected, Disc. % and Disc. amount is deducted before calculating discount 3.
- Subtract discount 2 before discount 3
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 3.
- Subtract discount 1 before discount 4
- If selected, Disc. % and Disc. amount is deducted before calculating discount 4.
- Subtract discount 2 before discount 4
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 4.
- Subtract discount 3 before discount 4
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 4.
- Subtract discount 1 before discount 5
- If selected, Disc. % and Disc. amount is deducted before calculating discount 5.
- Subtract discount 2 before discount 5
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 5.
- Subtract discount 3 before discount 5
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 5.
- Subtract discount 4 before discount 5
- If selected, Disc. % 4 and Disc. amount 4 is deducted before calculating discount 5.
- Subtract discount 1 before discount 6
- If selected, Disc. % and Disc. amount is deducted before calculating discount 6.
- Subtract discount 2 before discount 6
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 6.
- Subtract discount 3 before discount 6
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 6.
- Subtract discount 4 before discount 6
- If selected, Disc. % 4 and Disc. amount 4 is deducted before calculating discount 6.
- Subtract discount 5 before discount 6
- If selected, Disc. % 5 and Disc. amount 5 is deducted before calculating discount 6.
Discount suggestion
There are two columns of check boxes. The first concerns the discount percentage, the second the discount amount. There are check boxes for each of the 5 pairs of sales discount percentages and amounts. The first pair of check boxes also concerns discount percentages and amounts for hire and purchasing.
% / Amount
- Suggest discount 1 percent
- Suggest discount 1 amount
- Suggest discount 2 percent
- Suggest discount 2 amount
- Suggest discount 3 percent
- Suggest discount 3 amount
- Suggest discount 4 percent
- Suggest discount 4 amount
- Suggest discount 5 percent
- Suggest discount 5 amount
- Search for price - discount amount
- Business NXT will deduct the discount amounts selected from the price in the row. Business NXT will otherwise search for discount amounts separately so that the discount amounts can be shown in different rows from the price and limited to other criteria. Business NXT will then select the highest possible discount amount for the criteria selected. The discount can have a maximum limit if you check the type of discount concerned in the dialog box for the field for fixed prices and discounts.
Prices/discount total field
In this field you can use as a basis totals for lines in the order with the same value in the Product price group 1 field. The Prices/disc. total field under Company information indicates the field on the order lines that is to be totalled. Looking up in this field leads to a dialog box with the following options:
(If you select "Quantity" 1, the quantity is not reduced by the value in the “Free quantity” field in the order line.)
The field is used by the Recalculate prices processing in order page elements and when correcting sales prices and discounts in sales order lines when saving price refund lines for which the refund status has been changed to 2 (Confirmed).
- 0 - (None)
- 1 - Quantity
- 2 - Quantity in base unit
- 3 - Length
- 4 - Area
- 5 - Volume
- 6 - Net weight
Customer- / Supplier- / other orders
Here you can select which criteria Business NXT is to search by in the price and discount matrix, in rows with no product number.
There are three columns of check boxes. The first relates to customer orders (sales, hire and loan), the middle one to supplier orders (purchase) and the last one to other orders (adjustments, goods consumed, production and stock transfers).
If you select as few options as possible in each column, the speed of references in the price matrix will increase, thereby also increasing the speed of order entry and the printing of price lists. When printing price lists, Business NXT starts with the selections in the customer column. Currencies includes testing in both the current currency (for sales, hire and purchase) and the cost currency.
The selections are stored in the Price/disc.-criteria 1 - Price/disc.-criteria 6 fields under Company information.
- Structure product no.
- Included in structure
- Product price group 1
- Product price group 2
- Product price group 3
- Warehouse no.
- Shipment no.
- Customer no.
- Customer price group 1
- Customer price group 2
- Customer price group 3
- Supplier no.
- Employee no.
- Employee price group
- Wage rate no.
- Order no.
- Order price group
- Post code
- Terms of delivery
- Delivery method
- Organisational unit 1
- Organisational unit 2
- Organisational unit 3
- Organisational unit 4
- Organisational unit 5
- Organisational unit 6
- Organisational unit 7
- Organisational unit 8
- Organisational unit 9
- Organisational unit 10
- Organisational unit 11
- Organisational unit 12
- Date
- Unit
- Quantity
- Price unit
- Quantity in base unit
- Length
- Area
- Volume
- Net weight
- Currency
- Gross prices
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Price/disc.-criteria 2 | Integer |
| SQL name | PrCrit23 | The database field name. |
| API identifier | priceAndDiscountCriteria6 | The API identifier used in GraphQL. |
| Number | 7209 |
Price/discount processing
Getting price
- Price/discount on buyer
- The buyer (customer number) will be used instead of the invoice recipient when looking up in the price and discount matrix.
- Price refunds independent of stock
- Price rounding after discount
- Business NXT will round the price after discount to two decimals when calculating amounts in order lines. The fields for Price after discount and Price after discount (dom.) in the order lines will then also display two decimals as standard instead of floating decimals.
- Price factor for hire orders
- The order lines contain a Price factor field in which you can enter a factor by which Business NXT is to multiply the product of price and quantity when calculating line amounts. If you have checked Price factor for hire orders field , Business NXT will not multiply by the hire period when calculating line amounts and instead suggest the price factor on the basis of a table of price factors for various hire periods and only multiply by this factor.
- Cost price from the price and discount matrix if sold out
- Business NXT will use cost prices from the price and discount matrix in sales order lines instead of the physical Average cost price from the Stock balance table when the physical stock level is 0 or negative. The last FIFO cost price is retained when the stock level becomes 0 or negative. Business NXT will select the cost price for any supplier stated in the order line or in the order head. When you look up in the Stock balance table, Business NXT includes the normal supplier in the sales order line when the check is in place and the stock level is £0
Comparison date
In this field you define which date forms the basis of comparisons with the from and to dates in the Stock balance table (which states when the goods can be sold), and when referring to the Price- and discount matrix table:
- 0 - Today's date
- The current date will be used.
- 1 - Order/transaction date
- The transaction date in the order line is used, or the order date in the order head.
- 2 - Required/confirmed delivery date
- Business NXT will use the confirmed delivery date in the order line if it has been entered, possibly in the order head, or the required delivery date in the order line or the order head.
Price quantity extent
- Sales price
- Hire price
- Purchase price
- Cost price
Freight cost processing
- Ton rate 1
- Ton rate 2
- Ton rate 3
- Ton rate 4
- Cost 1
- Cost 2
- Cost 3
- Cost 4
Expenses
You check the dialog box if the freight fields from 1 - 4 in the Order table are to be calculated based on a ton rate or by cost.
- Calculate cost price addition from price after discount
- Calculate freight 1-4 based on price after discount
- Account debit/credit freight 1-4 and customs on purchase
- All freight and customs will be posted upon invoice receipt on the purchase order instead of at the time of sale. As before, the cost price of stock will increase with freight and customs, but at the time of sale this value will not be deducted; it is the cost price that will be posted.
Optimization parameters
- Consider empty/zero values for price calculations
Chain discounts
- Subtract discount 1 before discount 2
- If selected, Disc. % and Disc. amount is deducted before calculating discount 2.
- Subtract discount 1 before discount 3
- If selected, Disc. % and Disc. amount is deducted before calculating discount 3.
- Subtract discount 2 before discount 3
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 3.
- Subtract discount 1 before discount 4
- If selected, Disc. % and Disc. amount is deducted before calculating discount 4.
- Subtract discount 2 before discount 4
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 4.
- Subtract discount 3 before discount 4
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 4.
- Subtract discount 1 before discount 5
- If selected, Disc. % and Disc. amount is deducted before calculating discount 5.
- Subtract discount 2 before discount 5
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 5.
- Subtract discount 3 before discount 5
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 5.
- Subtract discount 4 before discount 5
- If selected, Disc. % 4 and Disc. amount 4 is deducted before calculating discount 5.
- Subtract discount 1 before discount 6
- If selected, Disc. % and Disc. amount is deducted before calculating discount 6.
- Subtract discount 2 before discount 6
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 6.
- Subtract discount 3 before discount 6
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 6.
- Subtract discount 4 before discount 6
- If selected, Disc. % 4 and Disc. amount 4 is deducted before calculating discount 6.
- Subtract discount 5 before discount 6
- If selected, Disc. % 5 and Disc. amount 5 is deducted before calculating discount 6.
Discount suggestion
There are two columns of check boxes. The first concerns the discount percentage, the second the discount amount. There are check boxes for each of the 5 pairs of sales discount percentages and amounts. The first pair of check boxes also concerns discount percentages and amounts for hire and purchasing.
% / Amount
- Suggest discount 1 percent
- Suggest discount 1 amount
- Suggest discount 2 percent
- Suggest discount 2 amount
- Suggest discount 3 percent
- Suggest discount 3 amount
- Suggest discount 4 percent
- Suggest discount 4 amount
- Suggest discount 5 percent
- Suggest discount 5 amount
- Search for price - discount amount
- Business NXT will deduct the discount amounts selected from the price in the row. Business NXT will otherwise search for discount amounts separately so that the discount amounts can be shown in different rows from the price and limited to other criteria. Business NXT will then select the highest possible discount amount for the criteria selected. The discount can have a maximum limit if you check the type of discount concerned in the dialog box for the field for fixed prices and discounts.
Prices/discount total field
In this field you can use as a basis totals for lines in the order with the same value in the Product price group 1 field. The Prices/disc. total field under Company information indicates the field on the order lines that is to be totalled. Looking up in this field leads to a dialog box with the following options:
(If you select "Quantity" 1, the quantity is not reduced by the value in the “Free quantity” field in the order line.)
The field is used by the Recalculate prices processing in order page elements and when correcting sales prices and discounts in sales order lines when saving price refund lines for which the refund status has been changed to 2 (Confirmed).
- 0 - (None)
- 1 - Quantity
- 2 - Quantity in base unit
- 3 - Length
- 4 - Area
- 5 - Volume
- 6 - Net weight
Customer- / Supplier- / other orders
Here you can select which criteria Business NXT is to search by in the price and discount matrix, in rows with no product number.
There are three columns of check boxes. The first relates to customer orders (sales, hire and loan), the middle one to supplier orders (purchase) and the last one to other orders (adjustments, goods consumed, production and stock transfers).
If you select as few options as possible in each column, the speed of references in the price matrix will increase, thereby also increasing the speed of order entry and the printing of price lists. When printing price lists, Business NXT starts with the selections in the customer column. Currencies includes testing in both the current currency (for sales, hire and purchase) and the cost currency.
The selections are stored in the Price/disc.-criteria 1 - Price/disc.-criteria 6 fields under Company information.
- Structure product no.
- Included in structure
- Product price group 1
- Product price group 2
- Product price group 3
- Warehouse no.
- Shipment no.
- Customer no.
- Customer price group 1
- Customer price group 2
- Customer price group 3
- Supplier no.
- Employee no.
- Employee price group
- Wage rate no.
- Order no.
- Order price group
- Post code
- Terms of delivery
- Delivery method
- Organisational unit 1
- Organisational unit 2
- Organisational unit 3
- Organisational unit 4
- Organisational unit 5
- Organisational unit 6
- Organisational unit 7
- Organisational unit 8
- Organisational unit 9
- Organisational unit 10
- Organisational unit 11
- Organisational unit 12
- Date
- Unit
- Quantity
- Price unit
- Quantity in base unit
- Length
- Area
- Volume
- Net weight
- Currency
- Gross prices
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Price/discount processing | Integer |
| SQL name | PrDcPro | The database field name. |
| API identifier | priceAndDiscountProcessing | The API identifier used in GraphQL. |
| Number | 16207 |
Prices/disc. total field
Indicates the field on the order lines that is to be totalled.
If this field is not filled in, the order lines are processed separately.
Getting price
- Price/discount on buyer
- The buyer (customer number) will be used instead of the invoice recipient when looking up in the price and discount matrix.
- Price refunds independent of stock
- Price rounding after discount
- Business NXT will round the price after discount to two decimals when calculating amounts in order lines. The fields for Price after discount and Price after discount (dom.) in the order lines will then also display two decimals as standard instead of floating decimals.
- Price factor for hire orders
- The order lines contain a Price factor field in which you can enter a factor by which Business NXT is to multiply the product of price and quantity when calculating line amounts. If you have checked Price factor for hire orders field , Business NXT will not multiply by the hire period when calculating line amounts and instead suggest the price factor on the basis of a table of price factors for various hire periods and only multiply by this factor.
- Cost price from the price and discount matrix if sold out
- Business NXT will use cost prices from the price and discount matrix in sales order lines instead of the physical Average cost price from the Stock balance table when the physical stock level is 0 or negative. The last FIFO cost price is retained when the stock level becomes 0 or negative. Business NXT will select the cost price for any supplier stated in the order line or in the order head. When you look up in the Stock balance table, Business NXT includes the normal supplier in the sales order line when the check is in place and the stock level is £0
Comparison date
In this field you define which date forms the basis of comparisons with the from and to dates in the Stock balance table (which states when the goods can be sold), and when referring to the Price- and discount matrix table:
- 0 - Today's date
- The current date will be used.
- 1 - Order/transaction date
- The transaction date in the order line is used, or the order date in the order head.
- 2 - Required/confirmed delivery date
- Business NXT will use the confirmed delivery date in the order line if it has been entered, possibly in the order head, or the required delivery date in the order line or the order head.
Price quantity extent
- Sales price
- Hire price
- Purchase price
- Cost price
Freight cost processing
- Ton rate 1
- Ton rate 2
- Ton rate 3
- Ton rate 4
- Cost 1
- Cost 2
- Cost 3
- Cost 4
Expenses
You check the dialog box if the freight fields from 1 - 4 in the Order table are to be calculated based on a ton rate or by cost.
- Calculate cost price addition from price after discount
- Calculate freight 1-4 based on price after discount
- Account debit/credit freight 1-4 and customs on purchase
- All freight and customs will be posted upon invoice receipt on the purchase order instead of at the time of sale. As before, the cost price of stock will increase with freight and customs, but at the time of sale this value will not be deducted; it is the cost price that will be posted.
Optimization parameters
- Consider empty/zero values for price calculations
Chain discounts
- Subtract discount 1 before discount 2
- If selected, Disc. % and Disc. amount is deducted before calculating discount 2.
- Subtract discount 1 before discount 3
- If selected, Disc. % and Disc. amount is deducted before calculating discount 3.
- Subtract discount 2 before discount 3
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 3.
- Subtract discount 1 before discount 4
- If selected, Disc. % and Disc. amount is deducted before calculating discount 4.
- Subtract discount 2 before discount 4
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 4.
- Subtract discount 3 before discount 4
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 4.
- Subtract discount 1 before discount 5
- If selected, Disc. % and Disc. amount is deducted before calculating discount 5.
- Subtract discount 2 before discount 5
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 5.
- Subtract discount 3 before discount 5
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 5.
- Subtract discount 4 before discount 5
- If selected, Disc. % 4 and Disc. amount 4 is deducted before calculating discount 5.
- Subtract discount 1 before discount 6
- If selected, Disc. % and Disc. amount is deducted before calculating discount 6.
- Subtract discount 2 before discount 6
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 6.
- Subtract discount 3 before discount 6
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 6.
- Subtract discount 4 before discount 6
- If selected, Disc. % 4 and Disc. amount 4 is deducted before calculating discount 6.
- Subtract discount 5 before discount 6
- If selected, Disc. % 5 and Disc. amount 5 is deducted before calculating discount 6.
Discount suggestion
There are two columns of check boxes. The first concerns the discount percentage, the second the discount amount. There are check boxes for each of the 5 pairs of sales discount percentages and amounts. The first pair of check boxes also concerns discount percentages and amounts for hire and purchasing.
% / Amount
- Suggest discount 1 percent
- Suggest discount 1 amount
- Suggest discount 2 percent
- Suggest discount 2 amount
- Suggest discount 3 percent
- Suggest discount 3 amount
- Suggest discount 4 percent
- Suggest discount 4 amount
- Suggest discount 5 percent
- Suggest discount 5 amount
- Search for price - discount amount
- Business NXT will deduct the discount amounts selected from the price in the row. Business NXT will otherwise search for discount amounts separately so that the discount amounts can be shown in different rows from the price and limited to other criteria. Business NXT will then select the highest possible discount amount for the criteria selected. The discount can have a maximum limit if you check the type of discount concerned in the dialog box for the field for fixed prices and discounts.
Prices/discount total field
In this field you can use as a basis totals for lines in the order with the same value in the Product price group 1 field. The Prices/disc. total field under Company information indicates the field on the order lines that is to be totalled. Looking up in this field leads to a dialog box with the following options:
(If you select "Quantity" 1, the quantity is not reduced by the value in the “Free quantity” field in the order line.)
The field is used by the Recalculate prices processing in order page elements and when correcting sales prices and discounts in sales order lines when saving price refund lines for which the refund status has been changed to 2 (Confirmed).
- 0 - (None)
- 1 - Quantity
- 2 - Quantity in base unit
- 3 - Length
- 4 - Area
- 5 - Volume
- 6 - Net weight
Customer- / Supplier- / other orders
Here you can select which criteria Business NXT is to search by in the price and discount matrix, in rows with no product number.
There are three columns of check boxes. The first relates to customer orders (sales, hire and loan), the middle one to supplier orders (purchase) and the last one to other orders (adjustments, goods consumed, production and stock transfers).
If you select as few options as possible in each column, the speed of references in the price matrix will increase, thereby also increasing the speed of order entry and the printing of price lists. When printing price lists, Business NXT starts with the selections in the customer column. Currencies includes testing in both the current currency (for sales, hire and purchase) and the cost currency.
The selections are stored in the Price/disc.-criteria 1 - Price/disc.-criteria 6 fields under Company information.
- Structure product no.
- Included in structure
- Product price group 1
- Product price group 2
- Product price group 3
- Warehouse no.
- Shipment no.
- Customer no.
- Customer price group 1
- Customer price group 2
- Customer price group 3
- Supplier no.
- Employee no.
- Employee price group
- Wage rate no.
- Order no.
- Order price group
- Post code
- Terms of delivery
- Delivery method
- Organisational unit 1
- Organisational unit 2
- Organisational unit 3
- Organisational unit 4
- Organisational unit 5
- Organisational unit 6
- Organisational unit 7
- Organisational unit 8
- Organisational unit 9
- Organisational unit 10
- Organisational unit 11
- Organisational unit 12
- Date
- Unit
- Quantity
- Price unit
- Quantity in base unit
- Length
- Area
- Volume
- Net weight
- Currency
- Gross prices
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Prices/disc. total field | Integer |
| SQL name | PrGrSmF | The database field name. |
| API identifier | priceAndDiscountSumField | The API identifier used in GraphQL. |
| Number | 7086 |
Primary key
A unique number identifying Company information.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | No. | Integer |
| Primary key | Yes | Primary key |
| SQL name | PK | The database field name. |
| API identifier | primaryKey | The API identifier used in GraphQL. |
| Number | 490 |
Prod. order series
Under company information you enter references to voucher and document series for the various order documents.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | ProdVoSr | The database field name. |
| API identifier | productionOrderVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 6827 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | ProductionOrderSeries |
|
Product no. customs
In this field you refer to products from which Business NXT is to retrieve information when printing, producing statistics and posting outgoing shipment costs in sales orders.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Product no. | Text (40) |
| SQL name | CusProd | The database field name. |
| API identifier | customsProductNo | The API identifier used in GraphQL. |
| Number | 6493 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Product | ProductCustoms |
| ||
| Search product | SearchProductCustoms |
|
Product no. freight 1
The box refer to the Product table, from which Business NXT retrieves information in connection with printing, keeping statistics on and posting outgoing forwarding costs in sales orders.
When you invoice via Business NXT EDI and you have entered product numbers in the Product no. freight 1 - 4 fields, you can enter the freight amount in the Freight 1 - 4 in the Order table. The freight amounts are accumulated to the freight and freight zone addition segments in the XML file. If any of the products are also present as separate order lines, these order lines are accumulated to the same segment and are not written as separate product lines.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Product no. | Text (40) |
| SQL name | FrProd | The database field name. |
| API identifier | freight1ProductNo | The API identifier used in GraphQL. |
| Number | 6495 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Product | ProductFreight1 |
| ||
| Search product | SearchProductFreight1 |
|
Product no. freight 2
The box refer to the Product table, from which Business NXT retrieves information in connection with printing, keeping statistics on and posting outgoing forwarding costs in sales orders.
When you invoice via Business NXT EDI and you have entered product numbers in the Product no. freight 1 - 4 fields, you can enter the freight amount in the Freight 1 - 4 in the Order table. The freight amounts are accumulated to the freight and freight zone addition segments in the XML file. If any of the products are also present as separate order lines, these order lines are accumulated to the same segment and are not written as separate product lines.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Product no. | Text (40) |
| SQL name | Fr2Prod | The database field name. |
| API identifier | freight2ProductNo | The API identifier used in GraphQL. |
| Number | 6496 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Product | ProductFreight2 |
| ||
| Search product | SearchProductFreight2 |
|
Product no. freight 3
The box refer to the Product table, from which Business NXT retrieves information in connection with printing, keeping statistics on and posting outgoing forwarding costs in sales orders.
When you invoice via Business NXT EDI and you have entered product numbers in the Product no. freight 1 - 4 fields, you can enter the freight amount in the Freight 1 - 4 in the Order table. The freight amounts are accumulated to the freight and freight zone addition segments in the XML file. If any of the products are also present as separate order lines, these order lines are accumulated to the same segment and are not written as separate product lines.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Product no. | Text (40) |
| SQL name | Fr3Prod | The database field name. |
| API identifier | freight3ProductNo | The API identifier used in GraphQL. |
| Number | 6466 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Product | ProductFreight3 |
| ||
| Search product | SearchProductFreight3 |
|
Product no. freight 4
The box refer to the Product table, from which Business NXT retrieves information in connection with printing, keeping statistics on and posting outgoing forwarding costs in sales orders.
When you invoice via Business NXT EDI and you have entered product numbers in the Product no. freight 1 - 4 fields, you can enter the freight amount in the Freight 1 - 4 in the Order table. The freight amounts are accumulated to the freight and freight zone addition segments in the XML file. If any of the products are also present as separate order lines, these order lines are accumulated to the same segment and are not written as separate product lines.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Product no. | Text (40) |
| SQL name | Fr4Prod | The database field name. |
| API identifier | freight4ProductNo | The API identifier used in GraphQL. |
| Number | 6474 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Product | ProductFreight4 |
| ||
| Search product | SearchProductFreight4 |
|
Product purchase voucher series
The voucher and document series for product purchases is used in voucher lines that Business NXT produces with totals for orders when posting product purchases, when GL trans. per inv. has not been checked.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | PrPuVoSr | The database field name. |
| API identifier | productPurchaseVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 4392 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | ProductPurchaseSeries |
|
Product-/account search processing
In this field you can exempt tables from being included when you are searching in the Product no. field or in the Debit account and Credit account fields.
Exempt from product search
- Product no's
- You are searching for the product in the Product no. field in the
Product
table, when you are searching in the Product no. field.Note:If you select this field, you do not do a lookup in the Product table, and it is recommended not to make this selection.
- EAN product no.
- You are searching for the product in the EAN item no. field in the Product table, when you are searching in the "Product no." field.
- EAN codes
- You are searching for the product in the Product no. field in the Barcode table, when you are searching in the "Product no." field.
- Delivery alternative, Suppl. Product no.
- You are not searching for the product in the Sup. prod. no. field in the Delivery alternative table, when you are searching in the "Product no." field.
- Product customers, Customers prod. no.
- You are searching for the product in the Customer's product no. field in the Product customer table, when you are searching in the "Product no." field.
- Alternative product no's
- You are searching for the product in the Alternative product no. field in the Alternative product table, when you are searching in the "Product no." field.
Choice alternatives
- Use search products for product look-up
- The look-up in the Product table is replaced with the "Search product" view, when you press "*" (star) in the Product no. field in the voucher line. The "Search product" view is made up of the following tables: Search product
- Use all accounts at look-up
- The look-up in the customers, suppliers, general ledger accounts and
capital asset accounts table is replaced with the "Account" view, when you press"*"
(star) in the Debit account/Credit account fields in
the voucher line. The "Account" view is made up of these tables:
- Customers from the Associate table
- Suppliers from the Associate table
- General ledger accounts
- Capital assets
Note:If you use the "Account" view as a look-up, you will not be able to add new rows in the dialog box. - Exempt 1-4 as account type look-up on voucher line
- 1-4 does not act as look-up for respectively, 1" for customers , "2" for suppliers , "3" for general ledger and "4" for capital assets in the Debit account/Credit account fields in the voucher line.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Product-/account search processing | Integer |
| SQL name | PrAcSrchPr | The database field name. |
| API identifier | productAndAccountSearchProcessing | The API identifier used in GraphQL. |
| Number | 16133 |
Purchase gen. processing
Definition of what is to be copied from a sales order to a purchase/production order when you run the Generate purchase/production order processing in the Order and Order line tables. Plus how purchase estimates will be accumulated when you run Generate purchase/production order options processing in the Purchase estimate and Purchase estimate line tables.
The dialog box has double sets of checks for the selections that apply to orders, columns on the left apply to generation from a sales order, while columns on the right apply when orders are being generated from goods consumption lines on a production order.
From sales orders
- Show dialog when generating orders from sales orders
- This Generate purchase/production order dialog box is displayed when you run the processing from the Order and Order line tables.
- Copy delivery address from sales order
- The Delivery associate no. and
Name fields and
addresses are copied from the order from where you run the Generate purchase/production orders
processing.Note:While this selection is available when running the processing from the Order line table, the Delivery associate no. is copied from the Order table.
- Use normal supplier from stock balance
- Copy each order line separately
- Each order line will be copied separately to the purchase order,
otherwise they will be accumulated per warehouse, supplier and product.Note:To activate the other selections that apply to order lines, you must select this.
- One product per order
- One purchase/production order is created per product on the order.
- Copy processing method from sales order
- The processing method fields are copied from the order line from where you run the Generate purchase/production orders processing. This can affect the processing and mean that you get other properties in the purchase order lines than when the purchase order is created manually.
- Copy sales order cost price to purchase order price
- The cost prices from the order line from where you run the Generate purchase/production orders processing are transferred to the price field on purchase or production.
- Copy organisational units from sales order
- The organisational units are copied from the order line from where you
run the Generate purchase/production orders
processing.Note:The order head is not updated with these organisational units.
- Copy seller/buyer from sales order
- The seller/buyer are copied from the order line from where you run the Generate purchase/production orders processing.
Quantity rounding
- Rounding rules from stock balance
- The rounding rules from the Stock balance table are used. This
requires that the you at the very least fill out the Rounding field in the
Stock balance table with
the value 1, which means the number of times the purchase unit will be rounded off.
The rounding method to be used is above.Note:The intention for this parameter is to used it when different units have been applied for sales and purchase, which sometimes is causing decimal values. The rounding rules will then correct this.
- Refill to minimum stock level from stock balance
- The minimum stock balance is taken into consideration, if the amount
is greater than the minimum stock balance in the order from where you are running the
Generate purchase/production orders processing.Note:Calculation formula: Min. stock - (In purchase + In production + Realised stock + Unrealised stock inc. - In order).
- Purchase economic order quantity from delivery alternative or stock balance
- The economic order quantity is taken into account from the Delivery alternative table.
From purchase estimate
- Show dialog when generating orders from purchase estimate
- This Generate purchase/production orders dialog box is displayed when you run the processing from the Purchase estimate and Purchase estimate line tables.
- Aggregate products
- One product per order
- The estimates lines with the same warehouse no., supplier no. and product no. are combined when you run the Generate purchase/production orders processing from the Purchase estimate and Purchase estimate line tables.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Purchase gen. processing | Integer |
| SQL name | PurcGPro | The database field name. |
| API identifier | purchaseGenerationProcessing | The API identifier used in GraphQL. |
| Number | 9036 |
Purchase order voucher series
In the Company information table you enter references to voucher and document series for the various order documents.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | PuOrVoSr | The database field name. |
| API identifier | purchaseOrderVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 4391 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | PurchaseOrderSeries |
|
Quotation series
References to voucher and document series for the various order documents.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | OfVoSr | The database field name. |
| API identifier | quotationVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 5988 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | QuotationSeries |
|
Refund series
When you print price refunds, the document number is taken from the voucher and document series for price refunds.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | RepVoSr | The database field name. |
| API identifier | refundVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 6456 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | RefundSeries |
|
Reminder/interest fee series
The field for reminder/interest fee series is used when posting reminder/interest fees.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | FeeVoSr | The database field name. |
| API identifier | reminderAndInterestFeeVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 2252 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | ReminderAndInterestFeeSeries |
|
Reminders series
The Reminders series field is used when printing reminders.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | RemVoSr | The database field name. |
| API identifier | reminderVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 11009 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | ReminderSeries |
|
Required org. unit sort at transfer appointment to order
Which organisational unit number to include for sorting appointments when transferring to orders. Business NXT generates a new order at this break.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | No. | Integer |
| SQL name | RSrtATO | The database field name. |
| API identifier | orgUnitClassWhenTransferringAppointmentToOrder | The API identifier used in GraphQL. |
| Number | 13761 |
Reservation processing
Exclude from reservation
Purchasing and production order lines can be excluded from this action if you select "No reservation on goods received" in the processing method dialog box.
- Reserve from shipments with inflow qty.
- When you save a purchase/production order a shipment is created where
inflow quantity is filled in. If you select this field, you can make reservations
against this shipment before it is accepted.Note:When a purchase/production order is generated, reservations are generated in the sales order against the shipment created for the purchase/production order, even if the "Reserve from shipments with inflow qty" field is selected.Note:You cannot make pick lists for products that are reserved from inflow; it is only when the shipment it is reserved against has come into stock that this is possible.
- Reserve by confirmed / sent
- The Hard links and Loose links check boxes will be greyed out, and they will be ineffectual. When you run the Confirmed and Sent processings on an order, a reservation will be made against allocated and non-allocated order lines before goods are received.
- Pick reserved against increase
- Take pick lists with reservations made against increases.
By goods receival
- Hard links
- When receiving goods, the reservation that is made on the allocated order line will be updated so that it can be finished, and confirmed delivery date will be set equal to today's date. Note that the Calculate delivery date option Do not move confirmed delivery date to earlier on order will override this functionality.
- Loose links
- On receipt of goods, sales order lines will be reserved against the shipments with available quantity. The confirmed delivery date will be set equal to today's date. This selection is considered and the confirmed delivery date is not moved to a earlier date.
Locations
- Use location control
- Validates locations entered on orders.
- Check location balance
- A check is done against the location balance whether it is possible to add in more goods in this location. Regardless of how each location is defined, it can be checked against quantity, weight and volume.
- Check location values against locations
- Validation of locations are done against the Location table.
- Check location values against item locations
- Validation of locations are done against the Item location table instead of the Location table.
Stock take
- Stock take based on locations
- The stock take is moved from stock balance to item locations and it will not be possible to make a stock correction from stock balances.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Reservation processing | Integer |
| SQL name | RsvOnRe | The database field name. |
| API identifier | reservationProcessing | The API identifier used in GraphQL. |
| Number | 6366 |
Rounding account
The rounding account (), which is used for rounding invoices and interest notes and any rounding differences in batches which Business NXT produces itself.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | RoundAc | The database field name. |
| API identifier | roundingAccountNo | The API identifier used in GraphQL. |
| Number | 3662 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | RoundingAccount |
|
Run SP when saving order
The name of a stored SQL procedure which is to be performed when saving an order.
The order number is sent along as a parameter for the procedure. If you want to create triggers in orders and order lines you should create an order procedure that does the same as the trigger. You should do this to avoid locking problems relating to Business NXT's internal locking routine. This is a routine that is only called when Business NXT has finished processing the order. A procedure is not run without being called, which means that the trigger does not start during the upgrading and import of data.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Stored procedure | Text (20) |
| SQL name | SvOrdSP | The database field name. |
| API identifier | storedProcedureWhenSavingOrder | The API identifier used in GraphQL. |
| Number | 6811 |
Running deviate product no.
This product number is used in order lines which Business NXT adds when saving orders for which the invoiceable amount is overridden in the order head, or in breaklines in an order line page element which is sorted with breaks on something other than product number unless the Deviate prod. no. field is filled in in the order.
See the description of the Invoiceable amount field in the order head and in order lines in the chapter on order entry in the system specification for logistics.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Product no. | Text (40) |
| SQL name | DifProd2 | The database field name. |
| API identifier | runningDeviateProductNo | The API identifier used in GraphQL. |
| Number | 7091 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Product | RunningDeviateProduct |
| ||
| Search product | RunningDeviateSearchProduct |
|
Sales series
The voucher and document series for sales is used in voucher lines that Business NXT produces with totals for orders when posting sales/hire, when GL trans. per inv. has not been checked.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | SaleVoSr | The database field name. |
| API identifier | salesVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 2473 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | SalesSeries |
|
Staged payment product no.
A customer and order preference Deduct client resp./Bank is included, to define whether Business NXT is to withdraw from the client balance for the customer and the client bank account for a staged payment, after using any on account postings for the order. You can combine this option with Post client resp./Bank. Both options are suggested from the Associate table in the order head when the customer number is entered. Business NXT adds an order line with the product number that it finds in the Deviate prod. no. field in the order head.
This field is suggested as equal to the Staged payment product no. field when the value 1 is entered in the Inv. according to plan field.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Product no. | Text (40) |
| SQL name | SetlProd | The database field name. |
| API identifier | stagedPaymentProductNo | The API identifier used in GraphQL. |
| Number | 10800 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Product | StagedPaymentProduct |
| ||
| Search product | StagedPaymentSearchProduct |
|
Standard location
In this field you enter which location is to be used when no other location is specified on the shipment when stock take.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Location | Text (18) |
| SQL name | StLoc | The database field name. |
| API identifier | defaultLocation | The API identifier used in GraphQL. |
| Number | 16132 |
Standard payment terms.
Payment terms which are used when calculating due dates.
The terms are used unless different payment terms are stated for:
- the order (when printing order documents)
- the customer/supplier in the Associate table (when completing the debit/credit account number in a voucher line)
- the voucher line (when updating the voucher)
In the absence of payment terms, Business NXT will use cash for invoicing and 30 days net when entering and updating vouchers.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Payment terms | Integer |
| SQL name | StPmtTrm | The database field name. |
| API identifier | standardPaymentTerms | The API identifier used in GraphQL. |
| Number | 8188 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Payment term | StandardPaymentTerms |
|
Standard time schedule group no.
The time schedule group to be used as default when an employee or a resource does not have a value. This will then be used when generating a time schedule balance.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Time schedule group no. | Integer |
| SQL name | StdTSGr | The database field name. |
| API identifier | standardTimeScheduleGroupNo | The API identifier used in GraphQL. |
| Number | 12225 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Time schedule group | StandardTimeScheduleGroup |
|
Stock take account set
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account set | Integer |
| SQL name | StcCntAcSet | The database field name. |
| API identifier | stockTakeAccountSet | The API identifier used in GraphQL. |
| Number | 16545 |
Supplier account
The general ledger account number defined in the account plan.
Supplier movements are totalled in the general ledger account specified for suppliers (2410 in the default account plan), unless another general ledger account is specified in the Associate table or in the Account no. series table.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | SupAc | The database field name. |
| API identifier | supplierAccountNo | The API identifier used in GraphQL. |
| Number | 505 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | SupplierAccount |
|
Supplier no. for anonymisation
Used by the Delete customer/supplier data processing in the Associate table.
| Property | Value | Description |
|---|---|---|
| Visible by default | No | This field is not visible by default in the table display. |
| Domain | Sup. no. | Integer |
| SQL name | SupNoFAn | The database field name. |
| API identifier | supplierNoForAnonymization | The API identifier used in GraphQL. |
| Number | 18503 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Associate | SupplierNoForAnonymization |
|
Supplier P.E. F.A. amend days
How many days beyond the end of the period vouchers can be posted for suppliers and capital assets.
An error message is generated when completing the fields if the number of days for the general ledger is lower than for the ledgers.
Voucher registration
When you enter the year and period or voucher reversal year and period in the batch head, either directly or indirectly via the value date/voucher reversal date, an error message is generated if the number of general ledger days is specified under company information, but the current date is more than this number of days beyond the accounting period’s to date.
When entering debit/credit account number in a voucher line, Business NXT will generate an error message if the field for the relevant account type is filled in under company information, and the current date is more than this number of days beyond the accounting period’s to date (based on the financial year and period in the voucher line, or in the batch head if they are not overridden in the voucher lines).
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Days | Integer |
| SQL name | SupDy | The database field name. |
| API identifier | supplierAndCapitalAssetAmendDays | The API identifier used in GraphQL. |
| Number | 8515 |
Swift code
SWIFT is a unique code that identifies your bank, used on foreign payments.
The SWIFT address is also known as BIC (Bank Identifier Code).
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is 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 | 17660 |
Tax exemption
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | String of length 40 | Text (40) |
| SQL name | TaxEx | The database field name. |
| API identifier | taxExemption | The API identifier used in GraphQL. |
| Number | 17523 |
Tax registration address
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | String of length 40 | Text (40) |
| SQL name | TaxRegAd | The database field name. |
| API identifier | taxRegistrationAddress | The API identifier used in GraphQL. |
| Number | 17524 |
Time Zone
This is where you define the company’s time zone. The field is used when calculating differences in relation to the user's/associate's time zone. This field currently has no function.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is 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 | 12215 |
Transp. agr. processing
Here you can add what kind of freight cost processing the transport agreement with the supplier should have.
Getting price
- Price/discount on buyer
- The buyer (customer number) will be used instead of the invoice recipient when looking up in the price and discount matrix.
- Price refunds independent of stock
- Price rounding after discount
- Business NXT will round the price after discount to two decimals when calculating amounts in order lines. The fields for Price after discount and Price after discount (dom.) in the order lines will then also display two decimals as standard instead of floating decimals.
- Price factor for hire orders
- The order lines contain a Price factor field in which you can enter a factor by which Business NXT is to multiply the product of price and quantity when calculating line amounts. If you have checked Price factor for hire orders field , Business NXT will not multiply by the hire period when calculating line amounts and instead suggest the price factor on the basis of a table of price factors for various hire periods and only multiply by this factor.
- Cost price from the price and discount matrix if sold out
- Business NXT will use cost prices from the price and discount matrix in sales order lines instead of the physical Average cost price from the Stock balance table when the physical stock level is 0 or negative. The last FIFO cost price is retained when the stock level becomes 0 or negative. Business NXT will select the cost price for any supplier stated in the order line or in the order head. When you look up in the Stock balance table, Business NXT includes the normal supplier in the sales order line when the check is in place and the stock level is £0
Comparison date
In this field you define which date forms the basis of comparisons with the from and to dates in the Stock balance table (which states when the goods can be sold), and when referring to the Price- and discount matrix table:
- 0 - Today's date
- The current date will be used.
- 1 - Order/transaction date
- The transaction date in the order line is used, or the order date in the order head.
- 2 - Required/confirmed delivery date
- Business NXT will use the confirmed delivery date in the order line if it has been entered, possibly in the order head, or the required delivery date in the order line or the order head.
Price quantity extent
- Sales price
- Hire price
- Purchase price
- Cost price
Freight cost processing
- Ton rate 1
- Ton rate 2
- Ton rate 3
- Ton rate 4
- Cost 1
- Cost 2
- Cost 3
- Cost 4
Expenses
You check the dialog box if the freight fields from 1 - 4 in the Order table are to be calculated based on a ton rate or by cost.
- Calculate cost price addition from price after discount
- Calculate freight 1-4 based on price after discount
- Account debit/credit freight 1-4 and customs on purchase
- All freight and customs will be posted upon invoice receipt on the purchase order instead of at the time of sale. As before, the cost price of stock will increase with freight and customs, but at the time of sale this value will not be deducted; it is the cost price that will be posted.
Optimization parameters
- Consider empty/zero values for price calculations
Chain discounts
- Subtract discount 1 before discount 2
- If selected, Disc. % and Disc. amount is deducted before calculating discount 2.
- Subtract discount 1 before discount 3
- If selected, Disc. % and Disc. amount is deducted before calculating discount 3.
- Subtract discount 2 before discount 3
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 3.
- Subtract discount 1 before discount 4
- If selected, Disc. % and Disc. amount is deducted before calculating discount 4.
- Subtract discount 2 before discount 4
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 4.
- Subtract discount 3 before discount 4
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 4.
- Subtract discount 1 before discount 5
- If selected, Disc. % and Disc. amount is deducted before calculating discount 5.
- Subtract discount 2 before discount 5
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 5.
- Subtract discount 3 before discount 5
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 5.
- Subtract discount 4 before discount 5
- If selected, Disc. % 4 and Disc. amount 4 is deducted before calculating discount 5.
- Subtract discount 1 before discount 6
- If selected, Disc. % and Disc. amount is deducted before calculating discount 6.
- Subtract discount 2 before discount 6
- If selected, Disc. % 2 and Disc. amount 2 is deducted before calculating discount 6.
- Subtract discount 3 before discount 6
- If selected, Disc. % 3 and Disc. amount 3 is deducted before calculating discount 6.
- Subtract discount 4 before discount 6
- If selected, Disc. % 4 and Disc. amount 4 is deducted before calculating discount 6.
- Subtract discount 5 before discount 6
- If selected, Disc. % 5 and Disc. amount 5 is deducted before calculating discount 6.
Discount suggestion
There are two columns of check boxes. The first concerns the discount percentage, the second the discount amount. There are check boxes for each of the 5 pairs of sales discount percentages and amounts. The first pair of check boxes also concerns discount percentages and amounts for hire and purchasing.
% / Amount
- Suggest discount 1 percent
- Suggest discount 1 amount
- Suggest discount 2 percent
- Suggest discount 2 amount
- Suggest discount 3 percent
- Suggest discount 3 amount
- Suggest discount 4 percent
- Suggest discount 4 amount
- Suggest discount 5 percent
- Suggest discount 5 amount
- Search for price - discount amount
- Business NXT will deduct the discount amounts selected from the price in the row. Business NXT will otherwise search for discount amounts separately so that the discount amounts can be shown in different rows from the price and limited to other criteria. Business NXT will then select the highest possible discount amount for the criteria selected. The discount can have a maximum limit if you check the type of discount concerned in the dialog box for the field for fixed prices and discounts.
Prices/discount total field
In this field you can use as a basis totals for lines in the order with the same value in the Product price group 1 field. The Prices/disc. total field under Company information indicates the field on the order lines that is to be totalled. Looking up in this field leads to a dialog box with the following options:
(If you select "Quantity" 1, the quantity is not reduced by the value in the “Free quantity” field in the order line.)
The field is used by the Recalculate prices processing in order page elements and when correcting sales prices and discounts in sales order lines when saving price refund lines for which the refund status has been changed to 2 (Confirmed).
- 0 - (None)
- 1 - Quantity
- 2 - Quantity in base unit
- 3 - Length
- 4 - Area
- 5 - Volume
- 6 - Net weight
Customer- / Supplier- / other orders
Here you can select which criteria Business NXT is to search by in the price and discount matrix, in rows with no product number.
There are three columns of check boxes. The first relates to customer orders (sales, hire and loan), the middle one to supplier orders (purchase) and the last one to other orders (adjustments, goods consumed, production and stock transfers).
If you select as few options as possible in each column, the speed of references in the price matrix will increase, thereby also increasing the speed of order entry and the printing of price lists. When printing price lists, Business NXT starts with the selections in the customer column. Currencies includes testing in both the current currency (for sales, hire and purchase) and the cost currency.
The selections are stored in the Price/disc.-criteria 1 - Price/disc.-criteria 6 fields under Company information.
- Structure product no.
- Included in structure
- Product price group 1
- Product price group 2
- Product price group 3
- Warehouse no.
- Shipment no.
- Customer no.
- Customer price group 1
- Customer price group 2
- Customer price group 3
- Supplier no.
- Employee no.
- Employee price group
- Wage rate no.
- Order no.
- Order price group
- Post code
- Terms of delivery
- Delivery method
- Organisational unit 1
- Organisational unit 2
- Organisational unit 3
- Organisational unit 4
- Organisational unit 5
- Organisational unit 6
- Organisational unit 7
- Organisational unit 8
- Organisational unit 9
- Organisational unit 10
- Organisational unit 11
- Organisational unit 12
- Date
- Unit
- Quantity
- Price unit
- Quantity in base unit
- Length
- Area
- Volume
- Net weight
- Currency
- Gross prices
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Transp. agr. processing | Integer |
| SQL name | TspAgPro | The database field name. |
| API identifier | transportAgreementProcessing | The API identifier used in GraphQL. |
| Number | 9038 |
Update order costs
Update order costs.
- Update cost price on orders
- When Business NXT updates sales order lines with values from purchase/production order lines to which they are linked with hard or loose links, Business NXT will update the cost prices at the same time if you have checked the "Update order costs" field, which has a Confirmed delivery date equal to or older than the Arrival/departure date for the order/production.
- Ignore dates
- No reference is made to the date and the order lines are updated. The Confirmed delivery date field is updated with the Arrival/departure date from purchase/production order lines, which then shows when the product is available for delivery.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Update order costs | Integer |
| SQL name | UpdCst | The database field name. |
| API identifier | updateOrderCosts | The API identifier used in GraphQL. |
| Number | 6384 |
User name card payment
The user name used for connecting to credit card company.
Used in connection with Zpider.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | User name | Text (24) |
| SQL name | CardUsr | The database field name. |
| API identifier | cardPaymentUserName | The API identifier used in GraphQL. |
| Number | 15938 |
VAT control account
The general ledger account number defined in the account plan. The tax control account (2740) is used in conjunction with the end of tax terms. The amounts in the tax accounts are then transferred to this account.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | TxSetAc | The database field name. |
| API identifier | taxControlAccountNo | The API identifier used in GraphQL. |
| Number | 506 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | TaxControlAccount |
|
VAT control account receivable
This field was previously used for certain situations related to Finnish VAT, but is now obsolete and should not be used at all.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | OutsTxAc | The database field name. |
| API identifier | taxReceivableAccountNo | The API identifier used in GraphQL. |
| Number | 11260 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | OutstandingTaxAccount |
|
VAT control supplier
Supplier number defined for Altinn payments in the Associate table.
The VAT control supplier is used for creating a payment batch out from Altinn VAT payment information, when running the Create VAT payment processing in the AutoReport archive table.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Sup. no. | Integer |
| SQL name | VatCSup | The database field name. |
| API identifier | vATControlSupplier | The API identifier used in GraphQL. |
| Number | 18214 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Associate | VatControlSupplier |
|
VAT reg. no.
VAT registration number for the company.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is 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 | 7184 |
VAT statement series
The VAT statement series is used for vouchers produced when closing tax periods. i.e. approval of printed VAT statements.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | TaxVoSr | The database field name. |
| API identifier | taxStatementVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 1969 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | TaxStatementSeries |
|
Visit address assoc. no.
You can use this field to join the Company information table and the Associate table key "Visit address assoc. no. -> Associate no.".
You then have access to the fields in the Associate table from the Company information table. For example, if you want the company to have a visiting address that is different from the address registered in the Company information table, you can retrieve the Address line 1-Address line 4, Visit post code and Visit postal area fields from the Associate table. If you select an associate number in the Visit address assoc. no. field, you can use this join for all order documents and other printouts when you want to print the company's visiting address.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Associate no. | Integer |
| SQL name | VstActNo | The database field name. |
| API identifier | visitAddressAssociateNo | The API identifier used in GraphQL. |
| Number | 13786 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Associate | VisitAddressAssociate |
|
Visualisation
Define how certain statuses are visualised.
- Parentheses for non-confirmed delivery dates
- If you have checked the option for brackets around unconfirmed
delivery dates, Business NXT will display brackets around values in the field for:
- confirmed delivery date in sales order lines
- the arrival/departure date on purchase and production order lines
- arrival/received date of shipments
- the order line statuses for confirmed by supplier and sent by supplier are both off (regardless of transaction type), and
- nothing has been reserved in the order line (reserved = 0), if it is a sales order line.
- Underline confirmed delivery date when sent from supplier
- If you have checked the option to underline delivery dates when the
goods are sent by the supplier, Business NXT will underline the values in the field for:
- confirmed delivery date in sales order lines
- the arrival/departure date on purchase and production order lines.
- arrival/received date of shipments
- the order line status for sent from supplier is on, or
- the whole order line is reserved (non-reserved = 0 and reserved > 0), if it is a sales order line.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Visualisation | Integer |
| SQL name | Vis | The database field name. |
| API identifier | visualisation | The API identifier used in GraphQL. |
| Number | 6311 |
Voucher must have amount
Select this if you will refuse to update batches where any of the voucher lines do not have amounts.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Boolean | Integer |
| SQL name | AmOnVo | The database field name. |
| API identifier | voucherMustHaveAmount | The API identifier used in GraphQL. |
| Number | 4834 |
Voucher no. control
Restrictions on the use of voucher numbers and voucher and document series.
- 1 - Allow only one user per voucher series
- Business NXT locks voucher and document series when it retrieves the next free number from them,
and releases when the edits have been saved or withdrawn.
One advantage of this is that the next free number will always be restored if you choose to close the batch window without saving, so that this does not cause any gaps in the series, and some companies (especially in Sweden) prefer to use uninterrupted voucher number series within batches. Other simultaneous users who try to retrieve numbers from the same series will be rejected, with a message telling them that the voucher and document series is in use.
If a batch is locked due to Business NXT not being closed properly, voucher and document series that are locked will be released when you cancel the locks on the relevant process.
- 2 - Check that voucher no. has not been used before
- Business NXT will perform an extra lookup in the Updated voucher table to make sure that the voucher numbers have not been used before. This does not prevent vouchers that run over several lines from having the same voucher number, as long as they are updated at the same time.
- 3 - Check both voucher series and numbers
- Business NXT will perform both the check in option 1 and 2.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher no. control | Integer |
| SQL name | VoNoChk | The database field name. |
| API identifier | voucherNoControl | The API identifier used in GraphQL. |
| Number | 1984 |
Voucher no. from jour. no.
You can use this field to specify a journal number from which tests as to whether a voucher number has been used previously are to be delimited, see the Voucher no. control field. This also applies for authorisation.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Journal no. | Integer |
| SQL name | VoNoJNo | The database field name. |
| API identifier | voucherNoFromJournalNo | The API identifier used in GraphQL. |
| Number | 8747 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Updated journal | VoucherNoFromJournal |
|
Voucher type for trans. compression
Compressed accounting transactions that are generated by the processing for compression in the tables for customers, suppliers, general ledger and capital asset transactions, are given the voucher type referred to in this field, and the associated text is retrieved from the Voucher type table.
The transactions are always given a separate origin code - 15 - Compressing transactions.
Voucher series for automatically generated transactions, automatic entries, tax statements, general notes, interest notes, interest income, reminder/interest fees, payment transfers, OCR and depreciation
These fields refer to the Voucher series table, and are used by Business NXT when it needs voucher numbers and document numbers.
There is nothing to prevent several of the fields from referring to the same voucher and document series if you do not need to differentiate between so many series. Business NXT checks that the necessary voucher and document series are specified before it starts processes that use them.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher type | Integer |
| SQL name | CompVoTp | The database field name. |
| API identifier | transactionCompressionVoucherType | The API identifier used in GraphQL. |
| Number | 6664 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher type | VoucherTypeForTransactionCompression |
|
Wage series
In this field you enter the voucher series to be used when posting wage transactions.
Visma Payroll version 5.0 uses the field when it creates vouchers in Business NXT.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | WageVoSr | The database field name. |
| API identifier | payrollVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 4586 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | PayrollSeries |
|
Web page
The address of a web page.
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 | Yes | This field is visible by default in the table display. |
| Domain | Web page | Text (260) |
| SQL name | IntAd | The database field name. |
| API identifier | webPage | The API identifier used in GraphQL. |
| Number | 6595 |
Week format
The Week format field is used to determine how week columns are processed for completion and presentation.
- 0 - Day / Week / Year
- 1 - Year / Week / Day
- 2 - Week / Year
- 3 - Year / Week
- 4 - Week
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Week format | Integer |
| SQL name | WkFmt | The database field name. |
| API identifier | weekFormat | The API identifier used in GraphQL. |
| Number | 10579 |
Workflow processing
Incoming invoice
- Pre-registration for incoming invoices
- Functionality specific to Swedish users working pre-registration. This
setting changes the behaviour of two processings, the Process document in the Accounting document table
and the Update supplier transactions in
the Batch table. See also: Process document and Update supplier transactionsDifferences in the flow when pre-registration is enabled:
- Process document processing:
- Pre-registration flow is enabled under the Batch processing field on the batch.
- For supplier line: Voucher type from Incoming document pre-registration series is used.
- Amount on cost voucher lines are set without VAT (VAT on supplier line).
- Update supplier transactions processing:
- Assign voucher numbers processing is run automatically to remove the tentative status.
- Previous voucher no. is set as Voucher no. on supplier line.
- "Split batch" occurs - see also: Update supplier transactions
- If enabled:
- Voucher series used will be fetched from the Incoming document pre-registration series field in the Company information table. This Voucher series must have a Voucher type given.
- The account set in the Interim cost account field in the Company information table will be used as Accrual debit account on the Voucher (Credit account if the invoice transferred is a credit invoice).
- Supplier account no will be used as cross account.
- Process document processing:
- Release payment after invoice is approved
- Functionality specific to Swedish users working pre-registration. See also: Pre-registration of supplier invoices for Swedish companies
- Do not create suppliers automatically
- If checked, you will need to run the processing Find or create supplier manually, from the Accounting document table.
- Do not use order match
- When set, order match will not be attempted even if the incoming invoice contains an order reference that matches an existing order.
Approval flow
- Receive Approval events
- Receive all events from approval (approved/rejected/comments/current approver): Enables approval to send messages back to Business NXT every time an approver approves or rejects invoices.
- Send automatically to approval flow
- Please note that this cannot be combined with pre-registration for incoming Invoices.
- Batch must balance before sending
- If enabled, the batch needs to balance before sending, restricting sending to approval if the batch does not balance.
- Add approvers when amount limit is exceeded
- If enabled, the flow group is supplemented with superiors up to the first approver within the amount limit. If not checked, the first superior with a sufficient limit is addressed.
- Calculate flow without flow groups
- Recalculate approval flow after changes
- If enabled, the approval flow will be automatically recalculated whenever relevant changes have been made to the document in the flow (for example amount, organisational units or account details). Disable this option if you want to keep the original approval flow unchanged after modifications.
- Store accounting document no. on batch
- When set, an Accounting document no. is added to the batch, when manually creating a new accounting document for vouchers.
- Approve invoices automatically by supplier contract
- 2100***Block approval on missing mandatory fields on voucher
Assign voucher number
- Manually
- No voucher numbers are assigned to voucher lines during creation. The Assign voucher numbers processing must be run before Update supplier transactions. This setup avoids gaps in the voucher series.
- When voucher is created
- Voucher numbers are assigned during creation, allowing the Update supplier transactions processing to be run without extra steps.
- After voucher has been approved
- Voucher numbers are assigned when the invoice has been approved. If Update supplier transactions is set to When voucher is created, this setting overrides the Assign voucher numbers setting, ensuring voucher numbers are always assigned when the update occurs.
Update supplier transactions
- Manually
- You will need to use the processing Update supplier transactions manually in the Batch table.
- When voucher is created
- Updates supplier transactions when the batch/voucher is created.
- After voucher has been approved
- Updates supplier transactions when the invoice has been approved.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Workflow processing | Integer |
| SQL name | WfProc | The database field name. |
| API identifier | workflowProcessing | The API identifier used in GraphQL. |
| Number | 18988 |
Write off account cash disc.
The processing Write off payments in the Open customer entry table produces a batch of depreciation vouchers for entries where the Write off status field has the value 1 - Write off accepted variance or 4 - Write off variance o/s limit.
You can process several invoice entries at the same time by selecting them.
Error messages are generated if no voucher series or account is specified for writing off payments in the Write off v. series and Write off account cash disc. fields.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | PmtVAc | The database field name. |
| API identifier | writeOffAccountNoCashDiscount | The API identifier used in GraphQL. |
| Number | 8512 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | WriteOffAccount |
|
Write off account misc.
The general ledger account for write-off of the outstanding amount in the customer ledger when you use the option of writing off a payment variant with updating of batch.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Account no. | Integer |
| SQL name | PmtVAc2 | The database field name. |
| API identifier | writeOffAccountNoMisc | The API identifier used in GraphQL. |
| Number | 11036 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| General ledger account | WriteOffAccountMisc |
|
Write off v. series
The voucher series for writing off payment differences in the customer ledger.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | Voucher series no. | Integer |
| SQL name | PmtVVoSr | The database field name. |
| API identifier | writeOffVarianceVoucherSeriesNo | The API identifier used in GraphQL. |
| Number | 8509 |
| To table | Purpose | From columns | To columns | Comments |
|---|---|---|---|---|
| Voucher series | WriteOffVarianceSeries |
|
Years to check incoming invoice no. history
This field can be used for limiting the number of years to check when the Check incoming invoice no. field is enabled with an 'x'.
When this field is empty then all supplier transactions will be checked. When a number is entered in this field only that number of years will be checked for duplicates. For example when the value is 1 then only the current year will be checked, when the value is 2 then current year and the previous year will be checked. There is no limit on how many years to enter in this field.
| Property | Value | Description |
|---|---|---|
| Visible by default | Yes | This field is visible by default in the table display. |
| Domain | No. | Integer |
| SQL name | ChInvNoHst | The database field name. |
| API identifier | checkIncomingInvoiceNoHistory | The API identifier used in GraphQL. |
| Number | 18401 |
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. |