Visma - Connector Settings
This document details the connector-specific settings for the Visma connector, which allow administrators and implementation consultants to configure how App4Sales integrates with Visma ERP systems. These settings influence various aspects of data synchronization, order processing, and customer management.
Settings are typically stored within the App4Sales portal UI and are applied at runtime when the Visma connector performs operations such as data synchronization or order submission. Proper configuration ensures accurate data exchange and alignment with business processes.
Settings Table
Setting | Description | Values / Defaults | Dependencies / Effects |
Extended descriptions module active | Determines whether the extended descriptions module is active, enabling the use of longer item descriptions from the ERP system. | Boolean (True/False) | If enabled, the connector will attempt to retrieve and use extended item descriptions. |
Unit module active | Controls whether the unit of measure module is active, allowing for the synchronization and use of different units of measure for items. | Boolean (True/False) | Enables advanced unit handling for items. |
Send contact as administration contact | When creating or updating customers, this setting determines if the contact person should be sent as the administration contact in Visma. | Boolean (True/False) | Affects how contact persons are mapped and created in the Visma ERP for customer records. |
Send contact as main contact | When creating or updating customers, this setting determines if the contact person should be sent as the main contact in Visma. | Boolean (True/False) | Affects how contact persons are mapped and created in the Visma ERP for customer records. |
Synchronize prospects | Enables or disables the synchronization of prospect accounts from App4Sales to Visma. | Boolean (True/False) | If enabled, prospect data will be synchronized. |
Vat included in items | Indicates whether VAT (Value Added Tax) is already included in the item prices synchronized from Visma. | Boolean (True/False) | Affects how prices are displayed and calculated within App4Sales. |
Accountview customer code start number | Specifies the starting number for customer codes when new customers are created in AccountView via App4Sales. | Integer | Used for auto-numbering new customer records in Visma AccountView. |
Accountview contact code start number | Specifies the starting number for contact codes when new contacts are created in AccountView via App4Sales. | Integer | Used for auto-numbering new contact records in Visma AccountView. |
Pricelist 1 code | The code for the first pricelist to be used or synchronized from Visma. | String | Identifies a specific pricelist in Visma. |
Pricelist 2 code | The code for the second pricelist to be used or synchronized from Visma. | String | Identifies a specific pricelist in Visma. |
Pricelist 3 code | The code for the third pricelist to be used or synchronized from Visma. | String | Identifies a specific pricelist in Visma. |
Pricelist 4 code | The code for the fourth pricelist to be used or synchronized from Visma. | String | Identifies a specific pricelist in Visma. |
Show order history prices incl Vat | Determines whether prices shown in the order history within App4Sales should include VAT. | Boolean (True/False) | Affects the display of historical order prices to users. |
Use username as employee for new customer | If enabled, the username of the App4Sales user creating a new customer will be used as the employee associated with that customer in Visma. | Boolean (True/False) | Links new customers to specific employees based on App4Sales user accounts. |
Enable autonumbering for customers | Activates automatic numbering for new customer records created through App4Sales and sent to Visma. | Boolean (True/False) | Requires Accountview Customer Code Start Number to be configured if using AccountView. |
Show open orders on order history | Determines whether open orders from Visma should be displayed in the order history section of App4Sales. | Boolean (True/False) | Expands the order history view to include currently open orders. |
Item synchronization pagesize (default: 100) | Defines the number of items to be retrieved per page during item synchronization, optimizing performance for large catalogs. | Integer, Default: 100 | Adjusting this value can impact the speed and resource usage during item synchronization. |
Filter blocked items in sync request | If enabled, items marked as "blocked" in Visma will be excluded from synchronization to App4Sales. | Boolean (True/False) | Prevents inactive or unavailable items from appearing in App4Sales. |
Alternative itemclass field to use | Specifies an alternative field in Visma to be used as the item class for App4Sales items. | String | Overrides the default item class field mapping. |
Don't sync items without itemclass value | If enabled, items that do not have a defined item class in Visma will be excluded from synchronization. | Boolean (True/False) | Ensures only items with a valid item class are synchronized. |
EAN code field in AccountView | Specifies the name of the field in AccountView that contains the EAN (European Article Number) code for items. | String | Used to map the EAN code from Visma to App4Sales. |
Subtract depot quantity from available stock | If true, the quantity in a depot location will be subtracted from the total available stock when reporting stock levels in App4Sales. | Boolean (True/False) | Affects the calculation of available stock visible in App4Sales. |
Label for order note | Defines the prefix for order notes sent from App4Sales to Visma. | String, Default: "App4Sales order note: - " | Customizes the appearance of order notes in Visma. |
Add orderline instruction to item description | If enabled, any specific instructions added to an order line in App4Sales will be appended to the item's description when sent to Visma. | Boolean (True/False) | Allows for detailed order line instructions to be visible in the ERP. |
Customer VAT liable codes (comma separated) | A comma-separated list of VAT codes from Visma that indicate a customer is liable for VAT. | String (comma-separated values) | Used for determining VAT liability for customers. |
Swap delivery and visit address to AccountView | If enabled, the delivery address will be used as the visit address and vice-versa when customer data is transferred to AccountView. | Boolean (True/False) | Alters the mapping of address types for customer records in Visma AccountView. |
Retrieve size/color table information | Enables the retrieval of size and color variant information for items from Visma, supporting matrix items. | Boolean (True/False) | Required for displaying and ordering items with multiple size and color options. |
Custom field for package size | Specifies a custom field in Visma that holds information about the package size of items. | String | Used to map package size details to App4Sales. |
Discount from order line | If true, discount calculations will be applied at the order line level rather than the header level. | Boolean (True/False) | Affects how discounts are processed and displayed in App4Sales and sent to Visma. |
Use price from app when discount isn't filled | If no discount is specified for an item, this setting dictates whether the price entered in the App4Sales application should be used. | Boolean (True/False) | Ensures a price is always used, even if no discount is applied. |
Use all pictures (L,M,S) for items | If enabled, all available sizes (Large, Medium, Small) of item pictures from Visma will be synchronized to App4Sales. | Boolean (True/False) | Provides a richer visual experience with multiple image resolutions. |
Item fields that should be empty (otherwise skip them) | A comma-separated list of Visma item fields that, if populated, should cause the item to be skipped during synchronization. | String (comma-separated values) | Allows for filtering out items based on specific field values. |
Item fields that should not be false (otherwise skip them) | A comma-separated list of Visma item fields that, if false, should cause the item to be skipped during synchronization. | String (comma-separated values) | Allows for filtering out items based on specific boolean field values. |
Skip pricelists in sync | If enabled, pricelists will be excluded from the item synchronization process. | Boolean (True/False) | Reduces synchronization time if pricelists are managed elsewhere or not needed. |
Price list 2 field | Specifies the Visma field used to determine the second pricelist. | String | Used for dynamic pricelist selection. |
Price list 3 field | Specifies the Visma field used to determine the third pricelist. | String | Used for dynamic pricelist selection. |
Price list 4 field | Specifies the Visma field used to determine the fourth pricelist. | String | Used for dynamic pricelist selection. |
Price for customer multiplied by quantity | If enabled, the item price for a customer will be multiplied by the ordered quantity to determine the total line price. | Boolean (True/False) | Affects how item prices are calculated in orders for customers. |
Vatliable when a customer has no vatcode | If true, customers without a specified VAT code will be considered VAT liable by default. | Boolean (True/False) | Provides a fallback for VAT liability determination. |
Customer No VAT liable codes (comma separated) | A comma-separated list of VAT codes from Visma that indicate a customer is NOT liable for VAT. | String (comma-separated values) | Used for determining VAT liability for customers. |
Retrieve exclusive item price from live call | If enabled, the exclusive item price will be fetched via a live API call to Visma, ensuring real-time pricing. | Boolean (True/False) | Ensures up-to-date pricing but may increase API call frequency. |
Number of orderlines per request | Sets the maximum number of order lines to be included in a single request when sending orders to Visma. | Integer, Default: 250 | Optimizes order submission performance for large orders. |
Connect free fields to the item synchronization (JSON) | Allows mapping and renaming of custom/free fields from Visma to App4Sales item synchronization using a JSON configuration. | String (JSON format) | Provides flexibility for synchronizing additional item attributes. |
Collection account code for new customers | Specifies the default collection account code to be used for newly created customers in Visma. | String | Ensures new customers are assigned to the correct financial accounts. |
Use quantity without depot as shelf stock | If true, the stock quantity that is not assigned to a depot will be considered as shelf stock in App4Sales. | Boolean (True/False) | Affects how available stock is presented in App4Sales, distinguishing between depot and shelf stock. |
Use the web description for items | If enabled, the web description field from Visma will be used as the primary item description in App4Sales. | Boolean (True/False) | Prioritizes web-specific descriptions for items. |
Use economic stock as available stock | If true, the economic stock level from Visma will be used as the available stock in App4Sales. | Boolean (True/False) | Influences the stock quantity displayed as available for sale. |
Don't synchronise item pictures from AccountView | If enabled, item pictures will not be synchronized from AccountView. | Boolean (True/False) | Useful if item pictures are managed through another system or manually. |
Use SBA table from Accountview to retrieve the matrix items | If true, the SBA table in AccountView will be used to retrieve matrix item information. | Boolean (True/False) | Enables advanced matrix item handling for products with variants. |
Use article field for item status, (Presale,Stock) | Specifies an article field in Visma to determine the item's status (e.g., "Presale", "Stock"). | String | Allows for dynamic item status management based on ERP data. |
Fixed value on orders as employee code | A fixed value to be used as the employee code for all orders sent to Visma. | String | Overrides individual employee assignments for order processing. |
Selection code for orders | Specifies a selection code to be applied to orders when they are sent to Visma. | String | Used for categorizing or filtering orders within Visma. |
Custom field for stock | Specifies a custom field in Visma that holds stock information for items. | String | Allows for mapping custom stock fields to App4Sales. |
Don't send discount to AccountView | If enabled, discount information will not be sent to AccountView when orders are synchronized. | Boolean (True/False) | Useful if discount management is handled entirely within App4Sales or another system. |
Don't send price to AccountView | If enabled, price information will not be sent to AccountView when orders are synchronized. | Boolean (True/False) | Useful if price management is handled entirely within App4Sales or another system. |
Custom boolean field to filter which customers to sync | Specifies a custom boolean field in Visma that can be used to filter which customers are synchronized to App4Sales. | String | Provides granular control over customer synchronization. |
Map order reference to custom field (leave empty to use comment3/INTERNAL_NOTE) | Specifies a custom field in Visma to which the order reference from App4Sales should be mapped. If left empty, it defaults to comment3 or INTERNAL_NOTE. | String | Allows for flexible mapping of order references to Visma fields. |
Special Logic & Filters
There are several settings that control filtering and special logic during synchronization. For instance, Item synchronization pagesize directly impacts the batching of item data during sync operations. The settings Filter blocked items in sync request and Don't sync items without itemclass value act as filters, preventing certain items from being synchronized based on their status or data completeness in Visma. The PriceListsBasedOnItemFields is a derived setting, its value depends on whether PriceList2Field, PriceList3Field or PriceList4Field are set.
Domain Specifics
Authentication
The connector handles authentication with Visma using OAuth tokens (AccessToken, RefreshToken), which are securely stored and managed internally. These settings are hidden from the administrator as they are handled automatically by the system.
Catalog
Settings like Extended descriptions module active, Unit module active, and Retrieve size/color table information are crucial for configuring how item data, including rich descriptions, units of measure, and matrix item variants (sizes and colors), are synchronized and displayed in App4Sales.
The PriceList1Code, PriceList2Code, PriceList3Code, and PriceList4Code settings allow for the selection and synchronization of specific pricelists from Visma. The fields PriceList2Field, PriceList3Field, and PriceList4Field can be used to dynamically determine which pricelists apply based on item attributes. Skip pricelists in sync can be used to entirely disable pricelist synchronization.
Item synchronization pagesize allows for optimization of item data retrieval. EAN code field in AccountView maps the EAN code. Custom field for package size allows for mapping additional item data.
Settings such as Additional values that should be empty (otherwise skip them) and Additional values that should not be false (otherwise skip them) provide advanced filtering capabilities for item synchronization.
Order Processing
Settings such as Send contact as administration contact and Send contact as main contact dictate how contact information is handled when creating customers. Use username as employee for new customer assigns new customers to App4Sales users. Enable autonumbering for customers manages automatic customer ID generation.
For order specifics, Show order history prices incl Vat and Get open orders for history affect the visibility of order information. Add orderline instruction to item description allows for detailed notes. Customer VAT liable codes (comma separated) and No VAT liable codes (comma separated) are used for VAT determination.
OrderLinesBatchCount allows for optimizing the number of order lines sent in a single request to Visma. Discount from order line and Use price from app when discount isn't filled influence how discounts and pricing are applied to orders. DontSendDiscountToBackoffice and DontSendPriceToBackoffice control whether discount and price information is sent to AccountView.
Map order reference to custom field (leave empty to use comment3/INTERNAL_NOTE) provides flexibility in how order references are stored in Visma.
Stock Management
Subtract depot quantity from available stock and Use quantity without depot as shelf stock influence how stock quantities, especially those related to depots, are calculated and presented as available stock in App4Sales. Use economic stock as available stock uses the economic stock level from Visma as the available stock.
Related Settings & Prerequisites
Ensure that the necessary API credentials and permissions are configured in the App4Sales platform for the Visma connector to establish a connection and perform operations. Incorrect API URLs or missing credentials will block all synchronization jobs.
Known Limitations
The connector explicitly hides internal authentication tokens (AccessToken, RefreshToken, AccessTokenExpired, CompanyId) and the dynamically derived property (PriceListsBasedOnItemFields) from direct configuration by administrators, as these are managed automatically by the system. The connector assumes that required fields for item synchronization are available in Visma; if not, items may be skipped as per filtering settings.