Skip to main content

Visma.net - Config

Jarl Frode Arntzen
  • Updated

See also: ERP Documentation - Visma.net

Start by clicking "New Integration" in Semine.

 

If you are setting up the integration for organization for the first time then use the below given postman collection and environment variables to generate the Token for the first time. 

VismaNet - Environment.postman_environment.json
VismaNet Requests.postman_collection.json


Semine Connect root and client configuration

FIELD VALUE Decscription
Integration Name Visma Integration  
Base Url https://integration.visma.net/API/ Root only
Token* See procedure below
Access token to communicate with external API.		  
Company Id* See procedure below Company Id from ERP
Dimensions*

Example: SUBACCOUNT|Periode

Periode is deferral codes in Visma.Net

 Separator |
Base Currency* Example: NOK Root only
Segment keys Example: SUBACCOUNT Separator |
Sync all master data at root level. Mark this checkbox if ERP organization has multiple branches which shares same master data. Then all master data will be synced only once at organization level in Semine and all clients can use that. Root only
Dimension/vat relations for account
 If all account should have any predefined relations.
See procedure below		  
Map buyer reference field to description?

If this setting is on, then <cac:BuyerReference> field from ubl invoice

Example:

<cac:BuyerReference> 
      Ola Nordmann 
</cac:BuyerReference>  

This value in EHF will be passed to ERP along with invoice text when invoice is posted, in the description field on the invoice header.

Note: when this setting is on then all accounting lines in Semine must have same project selected else posting will fail.

 
Sync parameter relations only once?

If this setting is on then Dimension/VatCode relations what we define above will be set only once and afterwards it wont override any adjustments done in Semine.

 
Additional configured fields

Specify additional fields if ERP support. Example - Amount|VatAmount|PaySelected|Note

 
Payment method

When invoice is marked "Do not pay", then what should be the payment method system should sent to ERP when posting.
See procedure below.

 
Tax calculation mode

How tax should be calculcated in ERP.
Default option is TaxSetting.

Use one of the following:
TaxSetting

Gross

Net

 
Tax calculation mode for partial VAT

Whether ERP has different rules for handling partial vat then that can be set. Default would be Tax calculation mode chosen above.

 
Tax calculation mode for reverse VAT

Whether ERP has different rules for handling partial vat then that can be set. Default would be Tax calculation mode chosen above.

 
Branch number

Company organization number in ERP.
See procedure below.

 
Default project id

Set project id which should be sent to ERP when posting invoices. Default is X.

 
Voucher number

Visma.net will set the voucher number during posting invoices from Semine to ERP. This parameter is set on org level in Semine.

 

mceclip0.png

 
Approve invoice in ERP immediately.

When the setting is active, the invoice going from Semine will be approved automatically in Visma.net and ends up in status Open.
If the setting is inactive, the invoice will end up in status Balanced.

 
Semine Email*

The username for the integration user with access to the Semine client data.

 
Semine Password*

The password for the integration user with access to the Semine client data.

 
Note: Invoice attachments are not exported to Visma.net During invoice export, only the active invoice image is exported, not any of the attachments. This image is retrieved from the API through GET ../PDF and then exported to Visma.net

Getting field values from Visma.net 

  1. Start by logging in

  2. Set language to English
    mceclip0.png

  3. Base Url
    This is always the same for all Visma_net integrations https://integration.visma.net/API/

  4. Token
    You must setup token once for the organization, because if you set it up again then all existing integrations created for that organization must be updated with latest token.
    How to set up a Token 

  5. Company Id
    Procedure in Visma net:

    1. Click on Financials
      mceclip1.png
    2. Click on Admin --> Companies --> Select Company from list --> Find Company ID
      mceclip2.png

      OR in Financials, change to correct company and copy the value after CompanyID= in the URL. If you have only one company for the organization then you will not get the value from the URL. So in that case you must contact ERP admin to provide you the value or use the attached postman collection(above) to get the value.

      mceclip0.pngThe CompanyID needs also to be added to the ERP external ID when you are creating the new client in SEMINE.mceclip0.png

  6. Dimensions
    Procedure in Visma net:

    1. For other dimensions (Project and Employee)
      1. Search for "Segmented Keys" under Preferences
      2. All Segmented Key IDs can be added in the Semine integration field Dimensions
        mceclip4.png


      3. If customer has Deferral codes then that can be configured as Periode dimension in the box.
      4. Pipe (|) is used as separator among different dimensions.

  7. Segment keys
    Procedure in Visma net:

    1. Search for Segmented Keys under Registers
    2. Segmented Key ID: Click on the magnifying glass and select SUBACCOUNT
    3. Click on Segment ID 1 in the list.
    4. You should now see this screen
      mceclip5.png
    5. Copy value from Segmented Key ID (SUBACCOUNT) into Root segment key.
  8. Dimension/vat relations for account
    Specify if all accounts should have pre-defined relations. On selecting an account in Semine all other accounting parameters are pre-filled automatically according to the template.

    Template : <ValueCode>, <DimensionType>, <RelationType>, <TypeOfParameter>
    Example : 1,D1,Requirement,Dimension|1,null,Requirement,VatCode
    In the example above, for all accounts we are setting the Avdeling dimension 1 as required and 1 vat code as required. Instead of putting Avdeling directly we are putting D1. D is static text followed by segment id of avdeling dimension which is 1 here. So it becomes D1. Similar way if we have dimension Department which has segment Id as 2, then while configuring the relation we will use D2 and so on.

    Note:
    • Pipe (|) must be used to separate different dimensions.
    • Comma , is used to separate template elements within one dimension.

      Summary of types of relations available and their effect in the Invoice Line in the Invoice Details page

    • Requirement
      The related related accounting parameter will be set by default and cannot be changed
      Example:
      1,D1,Requirement,Dimension|1,null,Requirement,VatCode

    • Suggestion
      The accounting parameter values available as suggestions are listed in a dropdown.
      The user must select one of them.
      Example:
      1,Avdeling,Suggestion,Dimension|1,null,Suggestion,VatCode

    • NotApplicable
      The related accounting parameter is blank and cannot be edited.
      Example:
      1,Avdeling,NotApplicable,Dimension|1,null,NotApplicable,VatCode

    • AnyValue
      All values from the related accounting parameter are available in a dropdown.
      <ValueCode> must be null in the configuration.
      Example:
      null,D1,AnyValue,Dimension|null,null,AnyValue,VatCode

    • RequirementOrNoValue
      The accounting parameter values available as requirements are listed in a dropdown.
      The user must select one of them or blank.
      <ValueCode> must be null in the configuration.
      Example: null,D1,RequirementOrNoValue,Dimension|null,null,RequirementOrNoValue,VatCode


  9. Payment method
    Navigate to Bills and Adjustments
    blobid0.png

  10. How to find Branch number from ERP
    (Only applicable when organization has multiple companies)
    1. Login to Visma.net Financials
    2. Select the right company and branch
    3. Search for companies in the search box
    mceclip0.png
    4. Select the Companies.
    5. Organisation ID from ERP will be the equivalent Semine field(Branch number). mceclip1.png

  11. Configured Schedules for jobs
    Job type Cron expression Description
    Accounting codes 0 */2 * * * Every 2nd hour
    Vat codes 0 */3 * * * Every 3rd hour
    Dimension values 0 14 * * * Every day at 14:00
    Invoices */5 * * * * Every 5 minute
    Suppliers */15 * * * * Every 15 minute
    Currencies 0 */5 * * * Every 5th hour

 

 

 

InvoiceSync

Note : Settings --> Client --> SEMINE General
Make sure this setting is Active. If it is inactive, you will get one accounting line for each period which is not compatible with Visma.net.

 

Related articles

Comments

0 comments

Please sign in to leave a comment.