Customer document

Corresponds to the @GiroAmount macro function on the form.

Corresponds to the @GiroAmountInCurrency macro function on the form.

Selection

Exclude

When set, the corresponding row in the Associate table will no longer be displayed in the drop-down list of related lookups. The purpose of this flag is to allow the external employees to be distinguished from internal users.

Bank account

Do not read bank account when creating payments

The accounts for payments are not read from the external system.

Organisation no.

Do not read organisation no. during input

When reading an incoming e-document in the Visma XML format, a lookup is done on the Organisation no. to try to find the correct customer/supplier no. in the internal system. If you have several associates with the same Organisation no., you can block out the once you do not want to have associated with the organisation no. If all associate have option Do not read organisation no. during input selected in the Associate table, a second lookup will be done on the EAN location code.

VAT registered

The associate is in the VAT register. Will be updated automatically if qualified, when running the Update directly from Visma Bizweb processing.

Visma Bizweb

Exclude from mass update

When selected, the associate will be excluded from update when running the Update directly from Visma Bizweb processing.

EAN Location usage

Customer

When writing an e-document and check box Use EAN Location Code is selected in the EDI processing field in the Company information table, the EAN loc. code field for the customer (EANLocCd) can be found by adding the customer no. to the customer number tag of the associate. If XML Compliant format is selected in the EDI processing field in the Company information table, the Ord_CustNo tag will be used, if the XML Compliant format is not selected it will be the Ord.CustNo tag.

If EAN location code cannot be obtained an error message will be added to the EDI error message table.

Customer is blocked

When reading an incoming e-document in the Visma XML format, a lookup is done on the EAN loc. code field to try to find the correct customer no. in the internal system. If you have several associates with the same EAN location code, you can block out the once you do not want to have associated with the EAN location code. However, you will always try to first do a lookup on the Organisation no. field to try to find the corresponding internal customer no. If you instead want to use the EAN loc. code field, you can block the reading of the Organisation no. field by selecting Do not read organisation no. during input in the associate processing dialog.

Invoice customer

When writing an e-document and check box Use EAN Location Code is selected in the EDI processing field in the Company information table, the EAN loc. code field for the associate being invoiced EANInvoNo can be found by adding the customer no. to the invoice customer number tag of the associate. If XML Compliant format is selected in the EDI processing field in the Company information table, the Ord_InvoCust tag will be used, if the XML Compliant format is not selected it will be the Ord.InvoCust tag.

Invoice customer is blocked

When reading an incoming e-document in the Visma XML format, a lookup is done on the EAN loc. code field to try to find the correct invoice customer no. in the internal system. If you have several associates with the same EAN location code, you can block out the once you do not want to have associated with the EAN location code. However, you will always try to first do a lookup on the Organisation no. field to try to find the corresponding internal invoice customer no. If you instead want to use the EAN loc. code field, you can block the reading of the Organisation no. field by selecting Do not read organisation no. during input in the associate processing dialog.

Deliver to associate

When writing an e-document and check box Use EAN Location Code is selected in the EDI processing field in the Company information table, the EAN loc. code field for the associate being delivered to EANDelAct can be found by adding the customer no. to the deliver customer number tag of the associate. If XML Compliant format is selected in the EDI processing field in the Company information table, the Ord_DelActNo tag will be used, if the XML Compliant format is not selected it will be the Ord.DelActNo tag.

Delivery to associate is blocked

When reading an incoming e-document in the Visma XML format, a lookup is done on the EAN loc. code field to try to find the correct Delivery associate no. If you have serveral associates with the same EAN location code, you can block out the once you do not want to have associated with the EAN location code. However, you will always try to first do a lookup on the Organisation no. field to try to find the corresponding internal Delivery associate no. If you instead want to use the EAN loc. code field, you can block the reading of the Organisation no. field by selecting Do not read organisation no. during input in the associate processing dialog.

Supplier

When writing an e-document and check box Use EAN Location Code is selected in the EDI processing field in the Company information table, the EAN loc. code field for the supplier (EANSupNo) can be found by adding the supplier no. to the supplier number tag of the associate. If XML Compliant format is selected in the EDI processing field in the Company information table, the Ord_SupNo tag will be used, if the XML Compliant format is not selected it will be the Ord_SupNo tag.

Supplier is blocked

When reading an incoming e-document in the Visma XML format, a lookup is done on the EAN loc. code field to try to find the correct supplier no. in the internal system. If you have several associates with the same EAN location code, you can block out the once you do not want to have associated with the EAN location code. However, you will always try to first do a lookup on the Organisation no. field to try to find the corresponding internal supplier no. If you instead want to use the EAN loc. code field, you can block the reading of the Organisation no. field by selecting Do not read organisation no. during input in the associate processing dialog.

Send to associate

When writing an e-document and check box Use EAN Location Code is selected in the EDI processing field in the Company information table, the EAN loc. code field for the associate being sendt to EANShpNo can be found by adding the associate no. to the sendt associate number tag of the associate. If XML Compliant format is selected in the EDI processing field in the Company information table, the Ord_ShpActNo tag will be used, if the XML Compliant format is not selected it will be the Ord.ShpActNo tag.

Send to associate is blocked

When reading an incoming e-document in the Visma XML format, a lookup is done on the EAN loc. code field to try to find the correct ship to associate no. If you have several associates with the same EAN location code, you can block out the once you do not want to have associated with the EAN location code. However, you will always try to first do a lookup on the Organisation no. field to try to find the corresponding internal ship to associate no. If you instead want to use the EAN loc. code field, you can block the reading of the Organisation no. field by selecting Do not read organisation no. during input in the associate processing dialog.

Liaison associate

This check box is currently not in use.

Liaison associate is blocked

This check box is currently not in use.

Liaison associate 2

This check box is currently not in use.

Liaison associate 2 is blocked

This check box is currently not in use.

AutoInvoice

Do not use EAN for PartyIdentification

EAN loc. code field content will not be used for AutoInvoice PartyIdentification.

Specify operator code when sending invoice

When set, the value in AutoInvoice operator no. is used for routing when invoices are sent through Visma.net AutoInvoice. In most cases, it is not recommended or necessary to specify an operator code for invoice, unless there are conflicting routes available in AutoInvoice (meaning it is possible to deliver through more than one external access point) and an override is required.

Note:

This setting is not required for B2C invoicing with operator code.

Exclude e-invoice as route when sending invoice

When set, electronic route will be disregarded when AutoInvoice attempt to deliver the invoice. Meaning that even if the customer is able to receive invoices electronically, the invoice will be delivered as e-mail or printed.

Exclude EU goods stat. no. when sending invoice

When set, value in the EU goods stat. no. field will not be included in the XML invoice.

External processing

No access to delete

The row can not be deleted, even if there are no transactions linked to the row. This check box is intended for use when another program has imported the data and you want to prevent the row being deleted by mistake.

Note:

There are no restrictions on who can select or deselect this check box.

Inactive in external system

The associate is inactive in the external system.

Exclude from Visma Mobile

The associate is excluded from Visma Mobile Sales Order.

Exclude from Visma On Demand

The associate is excluded from Visma On Demand.

Exclude from Master Data Management

Created automatically

This setting is automatically selected when new associate is created from an incoming document.

Document center

Document processor

The value must be updated from Visma Document Center.

Document manager

The value must be updated from Visma Document Center.

Accountant

The value must be updated from Visma Document Center.

E-mail warning

The value must be updated from Visma Document Center.

External user

User in Time Ease

The associate is a Visma TimeEase user. If check box is selected, an x will be shown in the TimeEase user field in the Associate table.

User in Zpider

The associate is a Zpider user.

User in External system 3

The associate is a User in External system 3 user.

User in External system 4

The associate is a User in External system 4 user.

AutoInvoice payment means

Use default for all

The payment information is selected from the customer's location: Domestic customers get Bank account and/or Postal giro, international customers get IBAN. This is the standard behaviour, used for all customers where nothing else is selected.

Use domestic for all

When selected, Bank account and/or Postal giro is used as payment information on all invoices to this customer, also when the customer is international. Use this for customers abroad that cannot handle IBAN. If no bank account is found for the company, the invoice will not be transferred to AutoInvoice.

Use IBAN for all

When selected, IBAN is used as payment information on all invoices to this customer, also when the customer is domestic. Use this for domestic customers that require IBAN for payment. If no IBAN is found for the company, the invoice will not be transferred to AutoInvoice.

The authorisation official is suggested when you enter vouchers for the supplier.

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

0 - Not set

The document was printed without AutoInvoice as document delivery method, or the document delivery method was disregarded by using a different print method (Override to printer, Quick print, Print to PDF, Send e-mail, Design Excel template, Print to Excel, Print to clipboard, Print to file or Only approval). The document is ready to be sent to Visma.net AutoInvoice, unless it has been printed using an XML print form or the Document delivery method = EDI is set.

Note:

The document type 3 - Packing slips is always created with AutoInvoice status = 0 - Not set because of the way the document is processed.

1 - Transferred

The document has been delivered to Visma.net AutoInvoice. This status does not indicate what has happened after Visma.net AutoInvoice received the document. No further processing possible.

2 - Pending

The document is ready to be sent, but has not yet been processed. This status should only appear if the Document copies option Only approval - print later from document archive has been selected.

3 - Failed transfer

An error occurred while sending to Visma.net AutoInvoice. See the EDI error message table for more details. This status could indicate problems logging in to Visma.net AutoInvoice, communication with Visma.net AutoInvoice (firewall etc.) or issues with creating the XML data (corrupt data etc.).

4 - Cannot transfer

Status set when running the Set AutoInvoice status Cannot transfer processing. This status disables sending the document to Visma.net AutoInvoice. The processing is available for documents that have a status other than 1 - Transferred and 4 - Cannot transfer.

5 - Validation failed

This status is only in use if the System information processing setting Test content is selected. This setting is only available if AutoInvoice test is selected. The status indicates that the XML content includes validation errors, according to the PEPPOL BIS format rules. Detailed error message(s) can be found in the AutoInvoice validation error table.

6 - Preparing to send

7 - Sent from AutoInvoice

8 - Unsuccessful delivery

The field is used for payments using the Telepay format. In some cases, the SWIFT code is also sent, as determined by the receiving bank/country. Your bank or supplier will tell you if you need to include this field. Used by Visma.net AutoPay as Fedwire information on payments to USA.

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

Corresponds to the @CID macro function on the form.

You can also define that for ranges of customer numbers in the Account no. series table. If the field is blank, account references in the Company information table are used.

You can also define that for ranges of customer numbers in the Account no. series table. If the field is blank, account references in the Company information table are used.

You can also define that for ranges of customer numbers in the Account no. series table. If the field is blank, account references in the Company information table are used.

There is no limit to the number of contacts an associate can have. You can join the Associate table to itself using this field to view all contacts for an associate.

You define default country in the Company information table. The Country no. field is used to enter the country number that applies to the associate.

When the country number is entered, values get updated in the Language no. and Currency no. fields if you have entered this information for the relevant country in the Country table. The values can be changed if required. The country number determines, amongst other things, the parameters to be used for invoicing, reminders and calculation of interest. The field appears in two sets in the order head, and is suggested based of the customer/supplier and the recipient. If required, the country can also be edited out in forms as a part of the address, by retrieving the name of the country (or nationality code) from the Country table.

The value is copied to the Customer document table when you create open entry lists.

The customer has its credit suspended when you approve reminders for the country in question.

Entering orders

If you have suspended the customer's credit Business NXT will not let you enter orders for the customer, and you have to cancel the credit suspension before you can enter new orders. You can, however, always enter credit notes (as long as you have checked Credit note in the order head before entering the customer number). Control takes place on the basis of the invoice recipient, whether the invoice issuer's customer number is filled in directly or indirectly via the customer number. If you cancel the credit suspension for a customer and the Set credit suspension on open customer orders? check box is selected under the Accounting processing dialog in the Company information table, Business NXT removes the credit suspension for all orders entered for the customer.

Voucher registration

When you run vouchers for a customer whose credit is suspended, you receive a message stating that the customer's credit is suspended, but Business NXT does not block this as the transaction has of course already taken place.

You should place the customer number within the range for account type 1 (customers). You define this range in the Account no. series table. This enables you to avoid entering the account type when entering vouchers.

Giro document

The customer document has a giro amount (greater than 0).

Order

Gross orders

The same check box will be selected in the Order options dialog box, based on the buyer (customer number).

Reserve on save

The same check box will be selected in the Order options dialog box, based on the buyer (customer number).

Reserve within lead time

The same check box will be selected in the Order options dialog box, based on the buyer (customer number).

Batch invoice

When this customer is set as the invoice recipient on an order the order will be suggested to be included in a batch invoice. See Order options domain.

Justify exchange rate

The same check box will be selected in the Order options dialog box, based on the buyer (customer number).

Exempt from invoice fee

The same check box will be selected in the Order options dialog box, based on the invoice recipient (the invoice's customer number).

Accept changes manually

The same check box will be selected in the Order options dialog box, based on the buyer (customer number).

Send confirmations automatically

The customer is sent confirmations for orders received by EDI.

Include all lines on delivery notes

All order lines are included on delivery notes, not only those with the order line status that they are ready for printing on delivery notes.

Pick complete orders

The same check box will be selected in the Order options dialog box, based on the buyer (customer number).

Invoice no. from 'Label'

The same check box will be selected in the Order options dialog box, based on the invoice recipient (the invoice's customer number).

Withdrawal from client bank account

The same check box will be selected in the Order options dialog box, based on the buyer (customer number).

Post client funds

The same check box will be selected in the Order options dialog box, based on the buyer (customer number).

Use client responsibility 2

The same check box will be selected in the Order options dialog box, based on the buyer (customer number).

Use client responsibility 3

The same check box will be selected in the Order options dialog box, based on the buyer (customer number).

Prepayment

You block the order from being processed at a higher status level than the order confirmation. In order for the order to be processed, you must enter a payment against this order in the voucher entry.

Do not move confirmed delivery date to earlier

The confirmed delivery date will not be changed for allocated orders which are to be delivered after the confirmed date. Orders with an earlier date get an updated confirmed delivery date with a confirmed date from the purchase production order when the Confirmed and Sent processings are used. For loose allocations, future orders will not be reserved if this field has not been selected:

• Reserve by confirmed / sent under Reservation processing in the Company information table
• Reserve against all orders in the dialog box for the Confirmed and Sent processings. A check is suggested when Reserve by confirmed / sent in Reservation processing in the Company information table is selected.

You can also select Do not move confirmed delivery date to earlier on order:

• as standard for all orders in the Calculate delivery date field in the Company information table
• at each individual order in the Order options field in the Order table

Use original exchange rate on credit notes

Use buyer's item ID to find the product

When selected, processing incoming orders will try to identify the product based on the customer's product ID in the XML, first searching Product customer field Customer's product no. followed by Product no. in Product. If not found, the default product search is run.

Accounting

Suggest VAT code

The VAT code and the Turnover class -derived from the Trade area- for the customer is suggested when you register vouchers.

Reminder suggested

No reminders

The customer is exempted from reminders. This can also be done automatically after approval of the last reminder for the country in question, using the After last reminder field in the Country table.

No debt collection

No functionality has been implemented in this field. You can process them further in an external application such as BIG if required.

Private person

The customer is treated as a private customer. This is relevant for the interest rate that is used and whether compound interest is calculated. See the description of the Country table.

Invoicing: When set, the customer will be identified as consumer when invoicing to Visma.net AutoInvoice. This means that if the route is available, the invoice may be sent electronically to the customer's bank for processing. If not available, the invoice will either be sent by e-mail or be printed and sent by mail.

No interest

The customer is exempted from interest computation. This can also be done automatically after approval of the last reminder for the country in question, using the After last reminder field in the Country table.

Foreign payment

You are making a payment transfer to a customer abroad.

No payment

The supplier is not to receive payment.

Use Postgiro for payments - Swedish

This field is used by some EFT systems for Swedish payments. Postgiro is also used with other formats, so you must leave this field unchecked if you are using bank formats other than Swedish ones.

Suspended on voucher

You will not be able to post the voucher lines directly on the customer. You will see the message "Customer xxxxxxx is suspended from direct posting" in the status bar.

Debt collection

To debt collection

This check box is selected when you have run the final reminder and checked the Set debt collection flag after last letter field under Accounting processing in the Company information table, and the customer is sent to debt collection.

Transferred to debt collection

This check box is selected when the customer is sent to debt collection. All vouchers that are registered after the customer has been sent to debt collection are registered as being subject to debt collection and can be sent in a change list to the debt collection company. This applies in particular to payments that have been sent to debt collection.

Information field internally in Business NXT.

The date is validated using the regional settings in Windows.

Assigned value 2 or 3 for Direct Debit. Can be done manually, or when importing customer agreements from Visma.net AutoPay.

1 - Process inquiry

For customers wishing to enter into an agreement on direct debiting.

2 - Agreement w/o notification

In the direct debiting dialog box, which you call up via the processing for direct debiting, there is an option to create new direct debitors. This will send an inquiry to the bank for approval of the associates with direct debiting status 1 and simultaneously change the status to 2.

3 - Agreement with notification

The debitor is accepted by the bank.

4 - Rejected

The debitor is rejected by the bank.

5 - e-Invoice

6 - B2B direct e-mail

7 - e-Invoice and AvtaleGiro

8 - e-Invoice and Vipps

Information field internally in Business NXT.

The date is validated using the regional settings in Windows.

Originates from the Up-to-date from field in the print dialog box to the Reminders or Interest notes report.

Corresponds to the @DocDate macro function on the form.

The date is validated using the regional settings in Windows.

Corresponds to the @ReminderDocumentNo macro function on a Reminder form, or the @InterestNoteNo macro function on an Interest note form.

1 - Reminder

2 - Interest note

The method is suggested in the order head for the associate.

Order documents

The dialog box contains boxes for each of the relevant document types, that you can check to define required delivery methods. You can send the same document in several different ways by selecting several delivery methods. No documents are sent unless you select at least one of the delivery methods. There is a block against removing all selections in invoices; at least one of the delivery methods must be selected. Print previews of the documents works regardless of which delivery methods have been selected.

Accounting documents

You can send interest notes and reminders as fax and e-mail attachments in the same way as the order documents.

In addition to the document types with the associated delivery methods described above, there are some additional settings.

EDI Settings

Media type

E-media

Print

Postage type

1. class mail

2. class mail

____

Stop before sending e-mail

Used to prevent immediate transmission by e-mail. This means you can edit the e-mail before it is sent to the contact.

The method is suggested in the order head for the associate.

Order documents

The dialog box contains boxes for each of the relevant document types, that you can check to define required delivery methods. You can send the same document in several different ways by selecting several delivery methods. No documents are sent unless you select at least one of the delivery methods. There is a block against removing all selections in invoices; at least one of the delivery methods must be selected. Print previews of the documents works regardless of which delivery methods have been selected.

Accounting documents

You can send interest notes and reminders as fax and e-mail attachments in the same way as the order documents.

In addition to the document types with the associated delivery methods described above, there are some additional settings.

EDI Settings

Media type

E-media

Print

Postage type

1. class mail

2. class mail

____

Stop before sending e-mail

Used to prevent immediate transmission by e-mail. This means you can edit the e-mail before it is sent to the contact.

Corresponds to the @DueDate macro function on the form.

The date is validated using the regional settings in Windows.

The GLN/GS1 number is a numbering system developed to identify the legal entities involved in a transaction. Legal entities might be buyers, sellers, banks, hauliers, etc. You can also use the code to identify geographical locations in company addresses, departments, warehouse locations, loading bay doors, etc.

The allocation procedures guarantee that the location number is unique everywhere in the world. The number consists of a total of 18 digits. The structure can vary between member states.

If you have checked the Use EAN Location Code field under EDI processing field in the Company information table, a lookup is performed in this field during EDI import. It is important that two associates do not have the same GLN/GS1 number, as the lookup during EDI import would then lead to errors. If a company has administration and warehouse in different places, the company must have several GLN/GS1 numbers.

You can upload the field to the EDI export file.

An EAN/GTIN item number has either 8 or 13 digits. The 8-digit version is used for small packages. EAN/GTIN codes with 13 digits are unique all over the world, and the 2 or 3 first digits identify the country where the code was assigned.

If you do not enter a value here the account references from the Company information table will be used.

This is used for printing invoices and OCR scanning payments.

If you have a large number of customers abroad, you create payment accounts abroad for the customers in the relevant countries, and you define the CID code in this field according to the national requirements.

May originate from the Associate, Country or Reminder table.

Corresponds to the @ReminderFee macro function on the form.

Originates from the Form drop-down list in the print dialog box to the Reminders or Interest notes report.

Refers together with the form type 3 - Reminder or 4 - Interest note to the Form table.

In the Created date field you bring up the date on which you created the associate.

The date is validated using the regional settings in Windows.

May originate from the Associate or Country table.

Corresponds to the @InterestRate macro function on the form.

The language determines which texts are printed in documents that are sent to the customer/supplier.

The date is validated using the regional settings in Windows.

Refers to the Window table.

Corresponds to the @LetterNo macro function on the form.

The test is performed for orders if the associated field has a value greater than 0.

It overrides the corresponding fields under Company information.

It is used for the warning or block on the credit control setting in the Company information table. It overrides corresponding fields under Company information.

When you send a reminder to a customer you define the reminder number and the reminder text. When you reach a number of reminders that you have specified in the field for the maximum number of reminders, the final reminder for the country is used. If you have not specified a maximum number of reminders all reminders will be written.

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.

This field is obsolete. No. of reminders is given per invoice in the Open customer entry and Customer transaction tables.

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

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.

Refers together with the Layout no. field to the Window element table.

The value you enter here is suggested when you run vouchers for the supplier, and is carried forward to open customer and supplier entries and transactions. The priority can also be suggested from the voucher type.

Suggested when you enter orders for the supplier.

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.

If you enter a postcode that exists in the Postal address table, Business NXT fills in the Postal area field and the cursor jumps to the next field.

This is relevant if you want to print completed postal giro forms in connection with reminders, interest notes and payments, or if you use electronic funds transfer. You can restrict payments to associates for whom at least one of the Bank account or Postal giro fields is completed. To do this you must select the Payment if giro no. option in the Payment processing field in the Company information table.