Department/Business unit

Visma Business
SeveraComments
Organisational unit for DepartmentBusiness UnitOrganisational unit 1-12 in VB, depending which is set in the configuration of integration.
NoCode 
NameName 
InformationXGUID of business unitInformation 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 unitParent business unitWhen 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.

Go to top

Employee/User

Visma BusinessSeveraComments
AssociateUser 
InformationXGUID of userInformation 1-8 field in VB, depending which is set in the configuration of integration. GUID is the ID of user generated by Severa API.
GroupXActive/Inactive statusGroup 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 NoCode 
NameFirstName, LastNameWhen 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.
TitleTitle 
Main associate NoSupervisor 
AddressLine1AddresslineWhen 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
AddressLine2Addressline 
AddressLine3Addressline 
AddressLine4Addressline 
Post codePostal code 
Postal areaCity
Country NoCountry
Organisational unit of departmentBusiness unit Business unit of the user
PhonePhone 
Email addressEmail 
Language NoLanguage 

Go to top

Product category

Visma BusinessSeveraComments
Product categoryProduct category 
Product category NoCode 
DescriptionName 

Go to top

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 BusinessSeveraComment
ProductProduct 
Product NoCode 
InformationXGUID of the productInformation 1-8 field in VB, depending which is set in the configuration of integration. GUID is the ID of product generated by Severa API.
DescriptionName 
Default unitMeasurement UnitIn order to map the unit, it must be found from the Unit table in Visma Business
Product category NoProduct categoryIn the integration configuration user defines if he wishes to transfer product categories and if yes, then to which product category in Visma Business.
Sales priceUnit priceIn Visma Business, the prices are handled in Price- and discount matrix table
Purchase price
Cost price
Unit costIn Visma Business, the cost prices are handled in Price- and discount matrix table

Go to top

Customer/Account

Visma BusinessSeveraComments
AssociateAccount 
Customer NoNumber 
NameName 
InformationXGUID of accountInformation 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 NoVat Number 
ResponsibleAccount owner 
Currency NoCurrency code
Language  NoLanguage
Payment terms cust.Payment terms
TurnoverAnnual revenue 
Email addressEmail 
No. of employeesEmployees 
Web page 1Website 
GroupXActive/Inactive statusGroup 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 NoeInvoice operatorCode of the eInvoice operator. eInvoice address information can be transferred if eInvoice is enabled in Severa (Settings > Company details > API parameters).
Ean location codeeInvoice addresseInvoice 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.
InterestRateOverdueInterestOptional. 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.

Go to top

Billing address

VB AssociateS AddressComments
VismaBusinessApiCustomerBillingAddressGuid (from config)GUID 
VismaBusinessApiCustomerBillingAddresslineFieldNames (from config)AddressLineOnly 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
PostCodePostalCode 
PostAreaCity 
CountryNoCountryGUIDmapped
PhonePhone 
Fax1Fax 

Go to top

Other addresses

VB AssociateS AddressComments
VismaBusinessApiCustomerGUID (from config)GUID 
AddressLine1AddresslineWhen 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
AddressLine2Addressline 
AddressLine3Addressline 
AddressLine4Addressline 
PostCodePostalCode 
PostAreaCity 
CountryNoCountryGUIDmapped
PhonePhone 
Fax1Fax 

Go to top

Contact

VB AssociateS ContactComments
VismaBusinessApiCustomerGUID (from config)GUID 
NameFirstName, LastNameWhen 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.
TitleJobTitle 
LanguageNoLanguageGUID 
InactiveIsActiveIsActive=True same as Inactive=0
IsActive=False same as Inactive=1
EmailAddressCommunication Method.Value where Communication Method.Type = “Email” 
MobilePhoneCommunication Method.Value where Communication Method.Type = “Mobile” 
PhoneCommunication Method.Value where Communication Method.Type = “Phone” 
Fax1Communication Method.Value where Communication Method.Type = “Fax” 

Go to top

Project/Case

VB OrgUnitX (from company.config for case)S CaseComments
OrgUnitXNo (from config for case)CaseNumberX=number between 1-8
VismaBusinessApiProjectGuid (from config)GUID 
NameName 
VismaBusinessAPICaseShortName (from config)InternalNameTransferred 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).
CustomerNoAccountGUIDmapped
VismaBusinessApiDepartment (from config)BusinessUnitGUIDmapped
OfficialCaseOwnerUserGUIDmapped
ContactContactGUIDmapped
CurrencyNoCurrencyShortCode 
N/ASalesProcessGUIDDescribed in transferring logic of cases

Go to top

Work hours

Visma BusinessSeveraComments
Free Information XWork hoursThe Free information table defined in the configuration of the integration. Only approved work hours are transferred.
Employee NoUser 
Organisational unit for departmentBusiness unitBusiness unit of the user
Organisational unit for projectCaseProject 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 NoWork type 
Customer NoAccount 
Text1Guid of the hour entryGUID is the ID of work hour entry generated by Severa API.
Text2DescriptionDescription of the hour entry
Text3Invoice descriptionDescription of the invoice row
Text4OvertimeName of the overtime class used
Value1Quantity 
Value2Unit price 
Value3Total price 
Value4Unit cost 
Value5Total cost 
Value6Invoiced quantityIt 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
Value7Total amount invoiced 
Date1Date of the entry 

Go to top

Voucher/Cost

VB UpdatedVoucherS ItemComments
BatchNo+”-“+LineNo+”-“+VoucherJournalNoName 
TextDescriptionAs 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/AQuantityWhen VoucherTypeNo is included in “VismaBusinessApiCostCreditNoteVoucherTypes”, the value is -1; otherwise the value is 1.
(AmountExclusiveVatDomestic * Currency.Rate) * (VismaBusinessApiCostSalesValuePercentage /100)UnitPriceCurrency comes from Visma Severa based on CurrencyGUID of case.
VismaBusinessApiCostSalesValuePercentage comes from config.
N/AIsBillableTrue when UnitPrice is not 0, False when UnitPrice is 0
AmountExclusiveVatDomestic * Currency.RateUnitCost 
VoucherDateEventDate 
When UpdatedVoucher.CreditAccountNo is defined gets Vat.Rate based on UpdatedVoucher.CreditTaxCode. Otherwise gets Vat.Rate based on UpdatedVoucher.DebitTaxCodeVAT 
“OrgUnitX”.”VismaBusinessApiProjectGuid” (from config for case)CaseGUID 

Go to top

Order/Invoice

VB OrderS InvoiceComments
OrderTypeN/AValue=2, “no need to deliver”
VismaBusinessApiOrderGUID (from config)GUID 
CustomerNoAccountGUIDmapped
OrgUnitX (from config for business unit)BusinessUnitGUID 
LanguageNoLanguageGUIDmapped
CurrencyNoCurrencyShortformmapped
OrderDateDate 
PaymentTermsPaymentTermmapped
OurReferenceOurReference 
YourReferenceYourReference 
Contact1ReceiverContactNamemapped
EmployeeNosee ->Read case from Severa by MainCaseGUID and map its CaseOwnerUserGUID to EmployeeNo.
OfficialSenderContactNamename mapped to EmployeeNo
AddressLine1ReceiverAddresslineMultiple lines are split into separate address line fields
AddressLine2ReceiverAddressline 
AddressLine3ReceiverAddressline 
AddressLine4ReceiverAddressline 
PostCodeReceiverPostalCode 
PostalAreaReceiverCity 
CountryNoReceiverCountrymapped
 NotesAdded 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.
 NotesBeforeInvoiceRowsAdded 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.
 NotesAfterInvoiceRowsAdded 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)OrderNumberTarget 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)MainCaseGUIDmapped
VismaBusinessApiInvoiceSenderEmployeeFieldName (from config)SenderContactNamename mapped to EmployeeNo, optional, field name can be e.g. SellerOrBuyer

Go to top

Order line/Invoice row

VB OrderLineS InvoiceRow Comments
ProductNoProductGUIDsIf one product then mapped, but if it could not be mapped, then VismaBusinessDefaultProductNo from config is used
ProductNoTravelExpenseGUIDsIf 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.
ProductNoItemGUIDsIf one item then mapped, but if it could not be mapped, then VismaBusinessDefaultProductNo from config is used
ProductNoHourGUIDsIf at least one hour then mapped, but if it could not be mapped, then VismaBusinessHourProductNo from config is used
ProductNoN/AAll other cases VismaBusinessDefaultProductNo from config is used
OrgUnitX (from config for Cases)MainCaseGUIDmapped
DescriptionarticleNameWhen 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.
QuantitydeliveredQuantity 
PriceInCurrencyrowUnitPrice 
CostPriceInCurrencyrowCostAmount
/
deliveredQuantity
Transferred only when "Transfer Invoice Row Cost" value is Yes or True in config
UnitquantityUnitCodemapped
TaxCodeN/AWhen Invoice.IsTaxFree is true, use value from config VismaBusinessApiReverseChargeTaxCode, otherwise use 0.
EmployeeNoMainUserGUIDmapped
OrgUnitX (from config for Business Units)Case.BusinessUnitGUID or User.BusinessUnitGUIDmapped, 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.
TransactionDateEventDate 

Go to top

Other mappings

VB CountryS CountryComments
CountryNoN/A 
IsoCodeIsoCodea2 

 

VB CurrencyS CurrencyComments
CurrencyNoN/A 
IsoCodeCurrencyShortform 

 

VB LanguageS LanguageComments
LanguageNoN/A 
N/AIetfLanguageTag or GUIDusing languageMappings from config

 

VB UnitS N/AComments
UnitN/A 
DescriptionN/ABased on context e.g. from the quantityUnitCode on the invoice row or from the MeasurementUnit of the product

 

VB PaymentTermsS N/AComments
PaymentTermsN/A 
CreditDaysN/Amapped based on context e.g. from the PaymentTerm of Account

 

VB AutoInvoiceOperator (Visma Business 5.32 and higher)
S N/AComments
NoN/A 
CodeN/Amapped from Account.eInvoiceOperator to AutoInvoiceOperator.Code

 



Oliko tästä vastauksesta apua? Kyllä Ei

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.