Supplier transaction

If the standard currency, given in the Company information table is defined as Currency type 2 or 3 in the Currency table, the Amount in EURO will be calculated with the exchange rate given for Euro in Sales rate field in the Currency table.

The transaction has been approved for payment in Visma.net Approval. When this token follows the payment, approval of the payment in Visma.net AutoPay should not be required.

Used in Visma.net AutoPay for viewing of invoices.

See also: Authorisation

The fields can for example be used in connection with electronic funds transfer. In some companies, incoming invoices must be authorised by several people, for example invoices that are to be distributed between several organisational units. Business NXT sets the Auth. date 1 field to the current date when entries are authorised. If you delete the field in the Open supplier entry table, the transaction status for the general ledger transaction that it has been authorised is withdrawn.

The date is validated using the regional settings in Windows.

The fields can for example be used in connection with electronic funds transfer. In some companies, incoming invoices must be authorised by several people, for example invoices that are to be distributed between several organisational units. Business NXT sets the Auth. date 1 field to the current date when entries are authorised. If you delete the field in the Open supplier entry table, the transaction status for the general ledger transaction that it has been authorised is withdrawn.

The date is validated using the regional settings in Windows.

The Empl. no. is a unique number identifying one specific Employee.

If you did not complete the field during entry, Visma Business will retrieve the giro number from the Bank account or Postal giro field for the relevant associate in the Associate table.

The value in the field is also transferred to the Payment line table when you create a payment suggestion.

This field is also used for IBAN bank account numbers, depending on the recipient's country. You must in some cases also complete the Bank branch and Swift code fields. Which fields you must complete depend on the recipients country requirements. You can contact your bank or supplier for more information about this.

In this way, the outlay retrieves data from a bank account other than the default bank account.

If no cash amount is entered on the voucher line, but a payment term with a cash discount has been entered, the cash amount will be calculated during the update and inserted on this record

If no Cash amount is entered on the Voucher line, but a payment term with a cash discount has been entered, the cash amount will be calculated during the update and inserted on this record

If you have not entered the cash due date on an invoice, it is calculated on the basis of the Voucher date and Payment terms if the Payment terms carries a cash discount %.

The date is validated using the regional settings in Windows.

The field can be used for selection of credit amounts. Eg for reporting and analysis purposes

The cross reference can be entered in the Cross reference field on the voucher and will update this field on customer transactions, open customer entries, supplier transactions and open supplier entries.

If a cross reference has been entered on a voucher, this voucher will match against the open supplier entry or an open customer entry with the same value in its reference field.

The cross reference can also be entered or overridden direct in the Open supplier entry or the Open supplier entry table, to complete the entries before running the Match references processing in these tables.

The Cross reference field in the Customer transaction table and the Supplier transaction table will show the reference of the open entry to which the transaction was matched, but only if the matching was performed by running the processing Match entry-for-entry.

If postings are made to both debit and credit accounts in the same voucher line, the Cross-account no. and Cross-account type fields indicate the customer, supplier, Capital assetor General ledger accountaccount relating to the other transaction generated from the voucher line.

If the Posting errors account from the Company information table has been used, because the original account is non-existent, the Cross-account no. and Cross-account type fields indicate instead the customer, supplier, Capital asset or General ledger account to which you attempted to post the voucher.

If postings are made to both debit and credit accounts in the same voucher line, the Cross-account no. and Cross-account type fields indicate the customer, supplier, Capital asset or General ledger account account relating to the other transaction.

If the Posting errors account from the Company information table has been used, because the original account is non-existent, the Cross-account no. and Cross-account type fields indicate instead the customer, supplier, Capital asset or General ledger account to which you attempted to post the voucher.

1 - Customer

The account number refer to a customer.

2 - Supplier

The account number refer to a supplier.

3 - General ledger account

The account number refer to a general ledger account.

4 - Capital asset

The account number refer to a capital asset.

The field originally contains the same value as the Outstanding amount, or the Posted amount field if the correction is run on General ledger transaction or Capital asset transaction.

Each time the Currency correction processing is run, the field will be updated with the product of Curr. corr. exch. rate and Outstanding amount in currency or the Amount in currency if the correction is run on General ledger transaction or Capital asset transaction.

If no exchange rate adjustment has been performed, the field shows the same value as the Value date field.

The date is validated using the regional settings in Windows.

The field is updated when you run the Transfer corrections to table processing from the Currency correction data table. If no exchange rate adjustment has ever been performed, the field shows the same value as the Exchange rate field, which is inherited from the voucher.

The currency number is normally inherited from the voucher. If no currency number was entered on the voucher, the field will anyway be updated with the Currency no. from the Company information table.

If the field is already filled in, the value is overwritten by the bank reconciliation system. If bank reconciliation is not in use the field can be used manually.

The date is validated using the regional settings in Windows.

If the field is already filled in, the value is overwritten by the bank reconciliation system. If bank reconciliation is not in use the field can be used manually.

The date is validated using the regional settings in Windows.

The currency number you want Business NXT to use for the payment if it diverts from the suppliers standard currency.

The receiver of the products. It will only have a value if the receiver of the product is different from the receiver of the invoice.

If you have not entered a due date on an invoice voucher, it will be calculated on the basis of the Voucher date and the Payment terms fields. If you have not entered the due date (i.e. the payment date) in payments and credit notes vouchers, it is set equal to the voucher date.

Due date can be overridden. The new date is used for Reminder, interest computation and payment history.

The Due date field is also used when you execute the Create payment suggestion processing from the corresponding open entry table. A selection will be made in relation to the outlay date.

The date is validated using the regional settings in Windows.

The values are included on open supplier entries and supplier transactions.

The values are included on open supplier entries and supplier transactions.

For payment abroad, this field is used to enter the declaration code in accordance with national rules. You define valid values and related texts in the Declaration code table. The values are included on open supplier entries and supplier transactions.

The values are included on open supplier entries and supplier transactions.

If several errors are detected, they are listed with a comma separating them.

Illegal value date

Unknown organisational unit 1

Unknown organisational unit 2

Unknown organisational unit 3

Unknown organisational unit 4

Unknown organisational unit 5

Unknown organisational unit 6

Unknown debit account, Cust. no., Account no. or Cap. asset no.

Unknown credit account, Cust. no., Account no. or Cap. asset no.

Unknown debit VAT code or VAT code

Unknown credit VAT code or VAT code

Unknown debit VAT rate

Unknown credit VAT rate

Unknown debit investment tax

Unknown credit investment tax

Unknown debit payment terms

Unknown credit payment terms

Unknown distribution key

Illegal debit turnover cl. or Turnover class

Illegal credit turnover cl. or Turnover class

Missing credit turnover cl. or Turnover class

The grace period for the debit has exceeded

The grace period for the credit has exceeded

Unknown organisational unit 7

Unknown organisational unit 8

Unknown organisational unit 9

Unknown organisational unit 10

Unknown organisational unit 11

Unknown organisational unit 12

Missing accounting period

This date is used as basis for transactions to be picked when processing Create payment suggestion in table Open supplier entry is run.

You can automatically have the estimated payment date set to a workday in the voucher line before update, if the calculated payment date is a Saturday for example. You can thus have payment-free days. To make use of this, proceed as follows:

The date is validated using the regional settings in Windows.

Is updated from the Voucher table.

Is updated from the Voucher table.

If the field is already filled in, the value is overwritten by the bank reconciliation system. The value is updated from Voucher. If a bank reconciliation system is not in use the field can be used manually.

If the field is already filled in, the value is overwritten by the bank reconciliation system. The value is updated from Voucher. If a bank reconciliation system is not in use the field can be used manually.

If the field is already filled in, the value is overwritten by the bank reconciliation system. The value is updated from Voucher. If a bank reconciliation system is not in use the field can be used manually.

The fixed amount is given on the voucher and can contain of eg freight, packaging, insurance or other parts of the total invoice amount from which no cash discount shall be deducted.

The fixed amount in currency is given on the voucher and can contain of eg freight, packaging, insurance or other parts of the total invoice amount from which no cash discount shall be deducted.

The fixed Amount in EURO is derived from the fixed Amount in currency

Only relevant on payments where the currency differ from the currency on the matched invoice.

If the Invoice no. field is empty on the Voucher, this field will be updated with the Voucher no. field instead. This requires that Affects turn./purch. is selected in the Voucher type table.

The field will equal the Amount field if no Currency correction processing has been performed.

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.

The actual memo is stored in the Memo table.

The number of the Order from which the transaction has its origin.

Organisational units fields can be used freely according to company needs to split accounting, sales and purchases into organisational units. The most common types are department, project and campaign. It is also possible to limit the organisational units a user should see by limiting the organisational units in the Limitation groups, User limitation groups and Limitations. The field appear with the name assigned to it in the Company information table.

Organisational units fields can be used freely according to company needs to split accounting, sales and purchases into organisational units. The most common types are department, project and campaign. It is also possible to limit the organisational units a user should see by limiting the organisational units in the Limitation groups, User limitation groups and Limitations. The field appear with the name assigned to it in the Company information table.

Organisational units fields can be used freely according to company needs to split accounting, sales and purchases into organisational units. The most common types are department, project and campaign. It is also possible to limit the organisational units a user should see by limiting the organisational units in the Limitation groups, User limitation groups and Limitations. The field appear with the name assigned to it in the Company information table.

Organisational units fields can be used freely according to company needs to split accounting, sales and purchases into organisational units. The most common types are department, project and campaign. It is also possible to limit the organisational units a user should see by limiting the organisational units in the Limitation groups, User limitation groups and Limitations. The field appear with the name assigned to it in the Company information table.

Organisational units fields can be used freely according to company needs to split accounting, sales and purchases into organisational units. The most common types are department, project and campaign. It is also possible to limit the organisational units a user should see by limiting the organisational units in the Limitation groups, User limitation groups and Limitations. The field appear with the name assigned to it in the Company information table.

Organisational units fields can be used freely according to company needs to split accounting, sales and purchases into organisational units. The most common types are department, project and campaign. It is also possible to limit the organisational units a user should see by limiting the organisational units in the Limitation groups, User limitation groups and Limitations. The field appear with the name assigned to it in the Company information table.

The field appear with the name assigned to it in the Company information table.

The field appear with the name assigned to it in the Company information table.

The field appear with the name assigned to it in the Company information table.

The field appear with the name assigned to it in the Company information table.

The field appear with the name assigned to it in the Company information table.

The field appear with the name assigned to it in the Company information table.

The automatically generated transactions are labelled as to their origin (for example reminder, interest note or payment).

1 - Manually entered

2 - Automatically generated

13 - Automatic entry

3 - VAT report

41 - OSS VAT report

10 - Direct debiting

4 - Reminder

5 - Interest note

8 - OCR payment

21 - Write off payments

6 - Giro payment

7 - Direct payment

11 - Depreciation on capital assets

9 - Order processing

23 - Incoming invoice

12 - Import

Normal text import.

14 - Previous batch

15 - Compressing transactions

16 - Posting of costs

18 - Internal invoicing

17 - Differences

When you update a batch with this origin code debit/credit control is not carried out.

19 - EDI invoice import

20 - Payroll

22 - Visma Business Services

24 - Activate Capital asset

25 - Calculate client interest

26 - Document Center temporary batch

27 - Document Center finished batch

28 - Debt collector

29 - Split invoice

30 - Currency correction

31 - External application

If this origin code is used, this value can be used by other applications that use BIG or SQL and create batches.

32 - Cash order document

33 - Sell or scrap capital asset

34 - Initializing capital asset

35 - EDI read dirdeb vouchers

37 - Accrual accounting

38 - Order processing with picking after invoicing

39 - Picked after invoicing

40 - Correction of costs

42 - Accounting document

Batch was created from Accounting document table.

43 - Order match pre-registration

44 - Self billing invoice

45 - Split batch, supplier transactions

Batch was created by Update supplier transactions processing for supplier transactions only.

46 - Split batch, cost transactions

Batch was created by Update supplier transactions processing for cost and capital transactions to be adjusted after payment.

47 - Account statement vouchers

Batch was created by Create voucher processing in the Account statement transaction table.

48 - WebFaktura

49 - Central

The number can be used to trace the transactions generated from orders.

The field can be reset to not paid if the entry has been processed to a payment suggestion by mistake. You can then delete the payment suggestion in the payment lines table and run the payment suggestion processing again.

The field is set as soon as you have approved the payment suggestion. This means as soon as you have pressed OK in the dialog box which appears when you run Create payment suggestion. If you run Create payment suggestion for a part payment, the field will be left blank. If the part payment is equal to the amount that you are to pay, the field is not left blank.

Accumulates remitted part payments.

Updated each time you match a payment against an open entry.

The date is validated using the regional settings in Windows.

1 - Fully open entry

Has not been matched against any entry yet.

2 - Partially open entry

Has been matched against one or more entries, but an amount remains outstanding.

3 - Paid late

The entry is retained pending the backdated calculation of interest.

4 - Paid on time

The entries were settled before the payment deadline and their processing as an open entry is complete. Open entries are deleted as soon as they have status 4, after which they are stored in the transactions tables. If any entries with this status remain, you can terminate them by selecting the lines and running the Terminate entry processing in the Open customer entry table.

This amount will be suggested for the next payment suggestion. The field is emptied when you run the Create payment suggestion processing. The Part payment in currency field will be accumulated to the Paid curr. amount field, when the payment suggestion is created.

This amount will be suggested for the next payment suggestion. The field is emptied when you run the Create payment suggestion processing. The Part payment in currency field will be accumulated to the Paid curr. amount field, when the payment suggestion is created.

This field is normally to be used only on entries with its origin from cash orders. (Orders with order type = 3).

This field is updated with the payment number when you run the processing Create payment suggestion in the Open customer entry table.

The period batch number is included in automatic entries. On normal transactions, the value is taken from the Batch unless it is given on vouchers.

The transaction has been approved for payment in Visma.net Approval. Approval of the payment in Visma.net AutoPay should not be required. This value can be removed, but not be set.

The field is mainly used for sorting and selecting purposes.

If the Reference field is not filled in on the voucher line, Visma Business will set this field equal to the Invoice no. field. If the Invoice no. field is also not filled in on the voucher line, then the Voucher no. field will be used.

In use only on records concerning payments and used in those cases when the payment exchange rate differs from the exchange rate on the (paid) invoice.