Department/Business unit
Visma Business | Severa | Comments |
Organisational unit for Department | Business Unit | Organisational unit 1-12 in VB, depending which is set in the configuration of integration. |
No | Code | |
Name | Name | |
InformationX | GUID of business unit | Information 1-8 field in VB, depending which is set in the configuration of integration. GUID is the ID of business unit generated by Severa API. |
Currency no. | Currency | |
Main unit | Parent business unit | When Organisational hierarchy addon enabled in Severa and business units form hierarchies of parents and children. |
GroupX | - | Group 1-12 in VB, depending which is set in the configuration of integration. No corresponding field in Severa, since used for excluding departments toer from Visma Business to Severa. |
Employee/User
Visma Business | Severa | Comments |
Associate | User | |
InformationX | GUID of user | Information 1-8 field in VB, depending which is set in the configuration of integration. GUID is the ID of user generated by Severa API. |
GroupX | Active/Inactive status | Group 1-12 in VB, depending which is set in the configuration of integration. For active users, 0 is set into the Group field in VB. When user is inactive, the Group field shows the value, which is defined in the configuration settings, usually "1". |
Employee No | Code | |
Name | FirstName, LastName | When transferring to Severa, name is split into first and last name. The last space in Name separates the FirstName and LastName. If there is no space in Name, question mark is used for FirstName |
When transferring to Visma Business, FirstName and LastName are combined to Name separated by space. | ||
Title | Title | |
Main associate No | Supervisor | |
AddressLine1 | Addressline | When transferring to Severa, multiple address lines are combined together separated by line break. |
When transferring to Visma Business, multiple lines are split into separate address line fields | ||
AddressLine2 | Addressline | |
AddressLine3 | Addressline | |
AddressLine4 | Addressline | |
Post code | Postal code | |
Postal area | City | |
Country No | Country | |
Organisational unit of department | Business unit | Business unit of the user |
Phone | Phone | |
Email address | ||
Language No | Language |
Product category
Visma Business | Severa | Comments |
Product category | Product category | |
Product category No | Code | |
Description | Name |
Product
When product is transferred from Severa to Visma Business and the product does not have generic price in PriceAndDiscountMatrix, a new row is added to this table; otherwise a row with generic price is updated. When product is read from Visma Business, a product’s prices are read from PriceAndDiscountMatrix. Also in this case a row with generic price is selected. If the product does not have a generic price, 0 prices are transferred to Severa. A generic price row is the row where following fields have value 0: CustomerNo, CustomerPriceGroup1, CustomerPriceGroup2, CustomerPriceGroup3, ProductPriceGroup1, ProductPriceGroup2, ProductPriceGroup3, EmployeeNo, EmployeePriceGroup, OrderNo, OrderPriceGroup.
Visma Business | Severa | Comment |
Product | Product | |
Product No | Code | |
InformationX | GUID of the product | Information 1-8 field in VB, depending which is set in the configuration of integration. GUID is the ID of product generated by Severa API. |
Description | Name | |
Default unit | Measurement Unit | In order to map the unit, it must be found from the Unit table in Visma Business |
Product category No | Product category | In the integration configuration user defines if he wishes to transfer product categories and if yes, then to which product category in Visma Business. |
Sales price | Unit price | In Visma Business, the prices are handled in Price- and discount matrix table |
Purchase price | ||
Cost price | Unit cost | In Visma Business, the cost prices are handled in Price- and discount matrix table |
Customer/Account
Visma Business | Severa | Comments |
Associate | Account | |
Customer No | Number | |
Name | Name | |
InformationX | GUID of account | Information 1-8 field in VB, depending which is set in the configuration of integration. GUID is the ID of account generated by Severa API. |
Company No | Vat Number | |
Responsible | Account owner | |
Currency No | Currency code | |
Language No | Language | |
Payment terms cust. | Payment terms | |
Turnover | Annual revenue | |
Email address | ||
No. of employees | Employees | |
Web page 1 | Website | |
GroupX | Active/Inactive status | Group 1-12 in VB, depending which is set in the configuration of integration. For active users, 0 is set into the Group field in VB. When user is inactive, the Group field shows the value, which is defined in the configuration settings, usually "1". |
AutoInvoice operator No | eInvoice operator | Code of the eInvoice operator. eInvoice address information can be transferred if eInvoice is enabled in Severa (Settings > Company details > API parameters). |
Ean location code | eInvoice address | eInvoice address of the customer. |
AccountSetForCustomer | mapped, when Severa3MainAccountGroupNameForMappingToAccountSet has a value in config. Mapping is performed by name. From Visma Business the name comes from Text table with TextTypeNo 18 in company’s language. Text.TextNo is used as AccountSetForCustomer. From Severa the name comes from account group under main account group (from config). It’s mapped when only one group is selected. If none selected, then mapped to null. When unknown name or more than one selected, then it’s an exception. Also when name from config is not known or is not main level account group, it’s an exception. | |
InterestRate | OverdueInterest | Optional. From Visma Severa to Visma Business: if the OverdueInterest is not known then DefaultOverdueInterestRate from config will be used. From Visma Business to Visma Severa: the OverdueInterest will be overridden when it differs from InterestRate or from DefaultOverdueInterestRate when InterestRate is not known. |
Billing address
VB Associate | S Address | Comments |
VismaBusinessApiCustomerBillingAddressGuid (from config) | GUID | |
VismaBusinessApiCustomerBillingAddresslineFieldNames (from config) | AddressLine | Only to those address lines defined in the config file. Logic: When transferring to Severa, multiple address lines are combined together separated by line break. When transferring to Visma Business, multiple lines are split into separate address line fields |
PostCode | PostalCode | |
PostArea | City | |
CountryNo | CountryGUID | mapped |
Phone | Phone | |
Fax1 | Fax |
Other addresses
VB Associate | S Address | Comments |
VismaBusinessApiCustomerGUID (from config) | GUID | |
AddressLine1 | Addressline | When transferring to Severa, multiple address lines are combined together separated by line break. When transferring to Visma Business, multiple lines are split into separate address line fields |
AddressLine2 | Addressline | |
AddressLine3 | Addressline | |
AddressLine4 | Addressline | |
PostCode | PostalCode | |
PostArea | City | |
CountryNo | CountryGUID | mapped |
Phone | Phone | |
Fax1 | Fax |
Contact
VB Associate | S Contact | Comments |
VismaBusinessApiCustomerGUID (from config) | GUID | |
Name | FirstName, LastName | When transferring to Severa, name is split into first and last name. The last space in Name separates the FirstName and LastName. If there is no space in Name, question mark is used for FirstName When transferring to Visma Business, FirstName and LastName are combined to Name separated by space. |
Title | JobTitle | |
LanguageNo | LanguageGUID | |
Inactive | IsActive | IsActive=True same as Inactive=0 |
IsActive=False same as Inactive=1 | ||
EmailAddress | Communication Method.Value where Communication Method.Type = “Email” | |
MobilePhone | Communication Method.Value where Communication Method.Type = “Mobile” | |
Phone | Communication Method.Value where Communication Method.Type = “Phone” | |
Fax1 | Communication Method.Value where Communication Method.Type = “Fax” |
Project/Case
VB OrgUnitX (from company.config for case) | S Case | Comments |
OrgUnitXNo (from config for case) | CaseNumber | X=number between 1-8 |
VismaBusinessApiProjectGuid (from config) | GUID | |
Name | Name | |
VismaBusinessAPICaseShortName (from config) | InternalName | Transferred only when the field name is given. Case’s Master setting defines which system is the master for this data (the value in the slave system will be updated). |
CustomerNo | AccountGUID | mapped |
VismaBusinessApiDepartment (from config) | BusinessUnitGUID | mapped |
Official | CaseOwnerUserGUID | mapped |
Contact | ContactGUID | mapped |
CurrencyNo | CurrencyShortCode | |
N/A | SalesProcessGUID | Described in transferring logic of cases |
Work hours
Visma Business | Severa | Comments |
Free Information X | Work hours | The Free information table defined in the configuration of the integration. Only approved work hours are transferred. |
Employee No | User | |
Organisational unit for department | Business unit | Business unit of the user |
Organisational unit for project | Case | Project to which the work hour entry is made |
Order No | - | When work hour is invoiced in Severa and invoice is sent as order to Visma Business, the number of that order is updated for the work hour entry |
Product No | Work type | |
Customer No | Account | |
Text1 | Guid of the hour entry | GUID is the ID of work hour entry generated by Severa API. |
Text2 | Description | Description of the hour entry |
Text3 | Invoice description | Description of the invoice row |
Text4 | Overtime | Name of the overtime class used |
Value1 | Quantity | |
Value2 | Unit price | |
Value3 | Total price | |
Value4 | Unit cost | |
Value5 | Total cost | |
Value6 | Invoiced quantity | It is possible to change the quantity on invoice. This field shows how much was invoiced where as the Value1 shows what was the actual entered amount |
Value7 | Total amount invoiced | |
Date1 | Date of the entry |
Voucher/Cost
VB UpdatedVoucher | S Item | Comments |
BatchNo+”-“+LineNo+”-“+VoucherJournalNo | Name | |
Text | Description | As a 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. |
| |
| --- |
N/A | Quantity | When VoucherTypeNo is included in “VismaBusinessApiCostCreditNoteVoucherTypes”, the value is -1; otherwise the value is 1. |
(AmountExclusiveVatDomestic * Currency.Rate) * (VismaBusinessApiCostSalesValuePercentage /100) | UnitPrice | Currency comes from Visma Severa based on CurrencyGUID of case. |
VismaBusinessApiCostSalesValuePercentage comes from config. | ||
N/A | IsBillable | True when UnitPrice is not 0, False when UnitPrice is 0 |
AmountExclusiveVatDomestic * Currency.Rate | UnitCost | |
VoucherDate | EventDate | |
When UpdatedVoucher.CreditAccountNo is defined gets Vat.Rate based on UpdatedVoucher.CreditTaxCode. Otherwise gets Vat.Rate based on UpdatedVoucher.DebitTaxCode | VAT | |
“OrgUnitX”.”VismaBusinessApiProjectGuid” (from config for case) | CaseGUID |
Order/Invoice
VB Order | S Invoice | Comments |
OrderType | N/A | Value=2, “no need to deliver” |
VismaBusinessApiOrderGUID (from config) | GUID | |
CustomerNo | AccountGUID | mapped |
OrgUnitX (from config for business unit) | BusinessUnitGUID | |
LanguageNo | LanguageGUID | mapped |
CurrencyNo | CurrencyShortform | mapped |
OrderDate | Date | |
PaymentTerms | PaymentTerm | mapped |
OurReference | OurReference | |
YourReference | YourReference | |
Contact1 | ReceiverContactName | mapped |
EmployeeNo | see -> | Read case from Severa by MainCaseGUID and map its CaseOwnerUserGUID to EmployeeNo. |
Official | SenderContactName | name mapped to EmployeeNo |
AddressLine1 | ReceiverAddressline | Multiple lines are split into separate address line fields |
AddressLine2 | ReceiverAddressline | |
AddressLine3 | ReceiverAddressline | |
AddressLine4 | ReceiverAddressline | |
PostCode | ReceiverPostalCode | |
PostalArea | ReceiverCity | |
CountryNo | ReceiverCountry | mapped |
Notes | Added as order lines when TransferInvoiceNotes (from config) is either ‘Yes’ or ‘True’. When ProductNoForInvoiceNotes in config is given then it’s used on order line. | |
NotesBeforeInvoiceRows | Added as order lines when TransferInvoiceNotes (from config) is either ‘Yes’ or ‘True’. When ProductNoForInvoiceNotes in config is given then it’s used on order line. | |
NotesAfterInvoiceRows | Added as order lines when TransferInvoiceNotes (from config) is either ‘Yes’ or ‘True’. When ProductNoForInvoiceNotes in config is given then it’s used on order line. | |
VismaBusinessApiInvoiceOrderNumberFieldName (from config) | OrderNumber | Target field’s data type can be string or numeric. Cannot be OrderNo because it’s primary key and handled automatically by Visma Business. |
OrgUnitX (from config for Cases) | MainCaseGUID | mapped |
VismaBusinessApiInvoiceSenderEmployeeFieldName (from config) | SenderContactName | name mapped to EmployeeNo, optional, field name can be e.g. SellerOrBuyer |
Order line/Invoice row
| VB OrderLine | S InvoiceRow | Comments |
| --- | --- | --- |
| ProductNo | ProductGUIDs | If one product then mapped, but if it could not be mapped, then VismaBusinessDefaultProductNo from config is used |
| ProductNo | TravelExpenseGUIDs | If one travel expense then mapped, but if it could not be mapped then VismaBusinessDefaultTravelExpenseProductNo from config is used. If more than one then VismaBusinessDefaultTravelExpenseProductNo from config is used. |
| ProductNo | ItemGUIDs | If one item then mapped, but if it could not be mapped, then VismaBusinessDefaultProductNo from config is used |
| ProductNo | HourGUIDs | If at least one hour then mapped, but if it could not be mapped, then VismaBusinessHourProductNo from config is used |
| ProductNo | N/A | All other cases VismaBusinessDefaultProductNo from config is used |
| OrgUnitX (from config for Cases) | MainCaseGUID | mapped |
| Description | articleName | When VismaBusinessApiOrderLineDescriptionOnOwnLine in config is yes or true then Description on real order line is not set therefore logic in Visma Business is used. A new order line is created for the description. This order line contains description only. When articleName from Severa exceeds the maximum length of the Description column, the description is wrapped to next order line, which contains description only. |
| Quantity | deliveredQuantity | |
| PriceInCurrency | rowUnitPrice | |
| CostPriceInCurrency | rowCostAmount
/
deliveredQuantity | Transferred only when "Transfer Invoice Row Cost" value is Yes or True in config |
| Unit | quantityUnitCode | mapped |
| TaxCode | N/A | When Invoice.IsTaxFree is true, use value from config VismaBusinessApiReverseChargeTaxCode, otherwise use 0. |
| EmployeeNo | MainUserGUID | mapped |
| OrgUnitX (from config for Business Units) | Case.BusinessUnitGUID or User.BusinessUnitGUID | mapped, when Severa3InvoiceRowBusinessUnitFromUser (from config) is true or yes, in which case when the invoice row has data associated to user (e.g. hour entries or travel costs) then main user’s business unit is used. Otherwise row will get the business unit of the main case on the row, if any. If for some reason there is no main case on the row, business unit from order is used. |
| TransactionDate | EventDate | |
Other mappings
VB Country | S Country | Comments |
CountryNo | N/A | |
IsoCode | IsoCodea2 |
VB Currency | S Currency | Comments |
CurrencyNo | N/A | |
IsoCode | CurrencyShortform |
VB Language | S Language | Comments |
LanguageNo | N/A | |
N/A | IetfLanguageTag or GUID | using languageMappings from config |
VB Unit | S N/A | Comments |
Unit | N/A | |
Description | N/A | Based on context e.g. from the quantityUnitCode on the invoice row or from the MeasurementUnit of the product |
VB PaymentTerms | S N/A | Comments |
PaymentTerms | N/A | |
CreditDays | N/A | mapped based on context e.g. from the PaymentTerm of Account |
VB AutoInvoiceOperator (Visma Business 5.32 and higher) | S N/A | Comments |
No | N/A | |
Code | N/A | mapped from Account.eInvoiceOperator to AutoInvoiceOperator.Code |