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.
- Costs gets multiplied in Severa when integration transfers it from Visma Business to Severa.
- 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.
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.
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