Release notes of Visma Business Severa integration

Starting from Visma Business Severa integration version 1.3.6 changes of each version are reported in this article.

To receive information and updates into your email of changes made in each released version, login to Severa Customer Support portal and click "Subscribe" at the top of this article.

Download the latest integration version from here.

Relese Notes:

Visma Business Severa integration 2.3.1

Bug fixes

  • Costs gets multiplied in Severa when integration transfers it from Visma Business to Severa.


Visma Business Severa integration 2.3

Bug fixes

  • Costs are not transferred at all when "Transfer costs from General Ledger Transaction" is set to Yes when transferring costs for the first time.
  • Incorrect timestamp format in info.xml stops integration.
  • Account/Case etc. gets multiplied in Visma Business, when integration tries to add it from Severa to VB, but it's marked as do not transfer in VB.

Visma Business Severa integration 2.2

New option to fetch costs from General ledger transaction table instead of Updated voucher table

Up until now the integration has checked supplier invoices from "Updated voucher" table in Visma Business. This was an issue for customers using for example Visma Expense or Visma Lönn, because costs coming from those systems did not have any value in "Amount excl. VAT", which was the amount we transferred into Severa. Therefore an option is now introduced to check the costs from "General Ledger Transaction" table.

All costs that have the specified debit and credit accounts are transferred from General ledger and the amount of cost is taken from "Basis" field. Cost transfer can be limited by setting up voucher types that are not included in the transfer.

Possibility to specify the description of cost

Previously "Text" of the voucher was used as "Description" of the item in Severa. A new setting is added into cost transfer, where as default "Text" is selected. You can edit the description by adding more information into the row using the following: Supplier number, Supplier name, Voucher number, Invoice number and Additional text.

Period keys and recognizing revenue of invoices

When invoicing recurring fees, the income should be recognized to many months in Visma Business. In Visma Business, order lines have "period key" value, which distributes the amount of the order line to the months specified by the period key. Now it is possible to map the frequency of recurring fee in Severa, into the period keys in Visma Business. Invoices with recurring fees will get the period key to the order lines based on the recurrence rule in Severa.

Transfer approved work hours

A completely new feature, available for those who have Advanced time tracking with work hour approval enabled. Integration will transfer all approved work hours into specified table in Visma Business, and once hours are invoiced, integration will map order number for the hours. Hours can be used for reporting and recognizing revenue. For each work hour entry price, cost and invoiced amount are transferred.

Improved logging

On one Visma Business server, many companies can run under the same services. To help with following of the logs in event viewer or error emails, name of the company has been added into the entries, to determine better which company's data is being transferred.

Country code of the receiver address transferred with invoice

Previously when sender and receiver where from the same country, country code of the address was not transferred when invoice was transferred.

And some bug fixes:

  • When inactive customer was transferred from Visma Business to Severa, it became active
  • Cost was transferred twice in to Severa in certain scenario.
    This error was due to timestamp of the cost being close to the timestamp of last transfer of costs, since Visma Business saved the timestamp to closest minute and not seconds.
  • Integration stopped for other companies, if one company was inactive
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


  • 0
    Severa R&D

    Visma Business Severa integration 2.0

    We have improved our integration in the following areas:

    Configuration settings & files

    • Settings from configuration files have been moved into Severa. Only Severa API key is still set in company.config on server, all others are now set up in Severa's settings.
    • To have the settings visible in Severa, company must have Visma Business add-on enabled.
    • Watch a 20 minute long video of how to update integration to version 2.0 from Youtube.


    • Fixed bug: When transferring invoice for a case that is not in "won" status, case wasn't transferred.
    • Fixed bug: Product category is required even when setting product categories not to transfer.
    • Fixed bug: Timeout error occurs when transferring lots of invoices, invoices aren't updated properly. Fixed so that if invoice transfer fails, integration tries to update the invoice again when run next time.
  • 0
    Severa R&D

    Visma Business Severa integration 2.1

    We have improved our integration in the following areas:

    Configuration settings & files

    • Integration failed if empty company1.config was left in the folder. Integration now no longer fails.
    • Added a setting to Visma Business integration settings (in Severa), where user can define a product code to map costs (for supplier invoice)
    • Mapping of payment terms with same payment day: Added a new text area field where users can map payment terms the same way as language mappings (14=2, 30=5)
    • Improved error message when annual revenue for customer is too big
    • Validation of text fields in Severa's Visma Business settings to reduce errors in integration


    • Added caching for invoices to reduce the amount of requests


  • 0
    Simon Ström

    Visma Business Severa integration 1.3.10

    We have improved our integration in the following areas:

    • Account
    • Voucher


    • Fixed bug: Contact e-mail address and mobile number did not transfer from Visma Severa to Visma Business


    • Fixed bug: UnitCost was calculated with exchange rate when added to case with other currency than base currency.
  • 0
    Hanna Karppinen

    Visma Business Severa integration 1.3.6


    In Visma Severa when Billing-checkbox was disabled for address that was mapped as billing address in Visma Business, next time when integration was run, this address become delivery address in Visma Business but still the billing address from Visma Business was linked to the same address in Severa and addresses become unmanageable.

    This issue was fixed as follows:
    New key called "VismaBusinessApiCustomerBillingAddressFlag" with default value "Information6" was added into company.config into Accounts-section. One Information-field in Visma Business must be chosen to be used with the Billing address flag. Flag is either 1 or 0, where 1 means billing address and 0 delivery address. Integration now looks up for the Severa addresses with "Billing" checkbox enabled. Changes in address types are now noticed and billing address is changed in Visma Business according to settings in Visma Severa. If in Visma Severa there are multiple addresses chosen as billing addresses, first one in the list is the billing address in Visma Business.
    Note: When viewing Associates table, billing address is shown there twice but this is not a bug. This is because billing address is listed in same list with all other addresses (delivery addresses) and in customer's billing address.


    Minimun transfer interval is limited to 5 minutes, regardless if for example 1 minute is set in Service.exe.config.

  • 0
    Hanna Karppinen

    Visma Business Severa integration 1.3.7


    • New key in Company1.config Orders and Invoices: VismaBusinessApiOrderLineDescriptionOnOwnLine
      • Controls if order line description comes from Visma Business's product register based on the product number and Severa's invoice row description is added to the next order line OR if only Severa's invoice row description is used as order line description (this is the default behaviour).
      • When value is empty (default), only Severa's invoice row description is used as order line description. Change value to "Yes" or "True" to show both product name and invoice row description on the order lines.


    • New key in Company1.config Orders and Invoices: Severa3InvoiceRowBusinessUnitFromUser
      • Controls how order line's department will get its value. The default behaviour is that all order line's get the department of invoice's case's business unit. With this new key, order line will get the the department based on invoice row's user's business unit. If invoice row doesn't have a user, then invoice's case's business unit is used.
      • When value is empty (default), department for all order lines is invoice's case's business unit. Change value to "Yes" or "True" to use invoice row's user's business unit.
    • Invoice row description is wrapped after 60 characters on order row. Descriptions longer than 60 characters are split into new rows.
    • Change in Trans. date on Visma Business order row: Instead of Severa's invoice date, invoice row's date of entry is now order row's


    • New key in Company1.config Associates: Severa3MainAccountGroupNameForMappingToAccountSet
      • Connects Visma Severa's Market segmentation into Visma Business's Account Set. Account set is used together with VAT and accounting group to get the correct VAT and accounting information on orders. Because Severa doesn't have as complex VAT handling as Visma Business, connecting Account/Customer with correct account set, we can be sure that orders in Visma Business get the correct VAT handling. When connection is made, changes can be done either in Severa or in Visma Business.
      • When value is empty (default) account set is not connected to market segmentation.
      • How to set up:
        1. Login to Visma Severa and access Tools > Settings > Market segments.
        2. Enter main segment name and choose "Create as main group", click Add.
        3. Enter main segment name as value for Severa3MainAccountGroupNameForMappingToAccountSet in the company.config.
        4. Add each Account set from Visma Business as a segment under the main segment in Visma Severa. To review what account sets are used in Visma Business, open Layout explorer > Tables > Base data > Text and filter to view only text type 18. The integration matches account set with market segmentation by name, and it is case sensitive.

    Below, how market segmentation/account set is defined in Visma Business and in Visma Severa


    Below, how market segmentation/account set is visible on the account/customer in Visma Business and in Visma Severa


  • 0
    Hanna Karppinen

    Visma Business Severa integration 1.3.7a

    Fixes 2 bugs related to Account set/Market segmentation feature

    • Integration tries to connect Account set with Market segmentation even though value for key "Severa3MainAccountGroupNameForMappingToAccountSet" is empty in company.config
    • Connecting Account set with Market segmentation clears all market segmentation selections in Visma Severa, except the selection for the group connected with Account set.
  • 0
    Simon Ström

    Visma Business Severa integration 1.3.8

    We have improved our integration in the following areas:

    • Invoicing
    • CRM
    • Case
    • Voucher
    • Business Units
    • Other fixes


    • Visma Severa invoice texts are now transferred as order lines

      Important to know is that we are removing the following keys from the company.config-file:
      • "VismaBusinessApiInvoiceNotesFieldName"
      • "VismaBusinessApiInvoiceNotesBeforeInvoiceRowsFieldName"
      • "VismaBusinessApiInvoiceNotesAfterInvoiceRowsFieldName"
      The reason for this change is that the maximum amount of characters in eg. a Information-field is 40.
      In Severa we do not have same limitations, which causes problems with this transfer.

      New keys in the Order section to set up for this to work is:
      • "TransferInvoiceNotes"
        This needs to be set to True or Yes in order for integration to transfer invoice notes.
      • "ProductNoForInvoiceNotes"
        This is optional, you may specify what product number the order lines should have.
        If this key is not set no product number will be used.
      Config keys:
      Invoice fields in Visma Severa:

      Order lines in Visma Business:Invoice_text_fields_Business.PNG
    • Time out increased in order transfer to handle large amount of invoices


    • Transfer Interest rate to customer card

      It's now possible to transfer overdue interest rate between Visma Severa and Visma Business.
      New keys in the Accounts section:
      • "DefaultOverdueInterestRate"
        This value should be equal to the company's overdue interest rate.
        The company overdue interest rate is found from Tools > Settings > Company details and the section Document Preferences.

    The overdue interest case is transferred from Visma Business to Visma Severa only when is is other than the default value.
    The transfer is made from Visma Severa to Visma Business if it's defined in the account card.

    Overdue interestrate settings in Severa:
    Company-config key:


    • Transfer of case short name

      It's now possible to transfer case short name to Visma Business, and then update it based on master settings.
      This is a optional transfer.

      New keys in the Case section of the company-config file:
      • "Transfer Internal Cases"
        Enable or disable the case short name transfer. In order for the transfer to be done enter True or Yes.
      • "VismaBusinessAPICaseShortName"
        What field in the project (OrgUnitX) table that will hold the case short name.


    • You can now enter intervals for voucher types

      In the Voucher section of the company-config file it's now possible to enter voucher types in intervals instead of only comma separated list.
      It's possible to enter one or more series, eg. 1-10, 20-30 or just 1-30.

    Bussiness Unit - Department transfer:

    • Possible to limit transfer of Business Units from Visma Business to Visma Severa

      It's now possible to choose what business units that should not be transferred to Visma Severa.
      New keys in company-config to handle this:
      • "VismaBusinessApiDepartmentDoNotTransferFieldName"
        Name of the field in the 'Departments' (OrgUnitX) table that will hold the flag for business units that should not be transferred
      • "VismaBusinessApiDepartmentDoNotTransferValue"
        The value that indicates that the business unit should not be transferred

    • Removed key for limiting the integration to certain Business Unit by code

      We have removed the key in the company-config for limiting the integration to a certain Visma Severa business unit.
      If you have need for limiting the integration to a selected departments cases or orders, you need to do this by limiting the access rights of the API-user.


    • Error when updating work types to Visma Severa is removed
    • Config-file information is changed for keys:
      • VismaBusinessApiProductsProductCategoryFieldName - Name of the Field in the Products table that will hold the Product Category. Should be one of the ProductCategoryNo fields.
      • VismaBusinessApiProject - Name of the Table that is used to store projects in Visma Business. Should be one of the OrgUnits tables. When using OrgUnit 7 - 12 Severa 3 must be defined case master.
  • 0
    Simon Ström

    Visma Business Severa integration 1.3.9

    We have improved our integration in the following areas:

    • Account
    • Case
    • Invoicing
    • Other


    • Fixed bug: Currency code transfer did not work in account transfer from Visma Business to Visma Severa
      This issue was resolved separate in API-fix.


    • When case is created from Visma Business mileage, per diems and other expenses is now activated. Same as when creating new case in Visma Severa


    • Improved business unit transfer for invoices with multiple cases
      When products was added to case (not through work hour) and invoice was grouped with several case, all products was connected to the main case business unit. 
      Now all products will maintain it's own business unit


    • Correction of incorrect error message when VismaBusinessApiProductsProdoductCategory value is not a ProductCategoryNo field.
    • Removal of incorrect error when adding a travel expense. 

     Update 2014-06-13

    • New version of integration available for Visma Business 9.00
Powered by Zendesk