See also: ERP Documentation - Visma.net
Start by clicking "New Integration" in Semine.
Semine Connect root and client configuration
FIELD | VALUE | Decscription |
---|---|---|
Integration Name | Visma Integration |
|
Dimensions* |
Example: 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 Example: <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 |
|
Additional configured fields |
Specify additional fields if ERP support. Example - |
|
Payment method |
When invoice is marked "Do not pay", then what should be the payment method system should sent to ERP when posting. |
|
Tax calculation mode |
How tax should be calculcated in ERP.
|
|
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. |
|
Default project id |
Set project id which should be sent to ERP when posting invoices. Default is |
|
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.
|
|
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. |
|
Update purchase order details |
When there is an deviation in amounts/unit price in SEMINE and ERP, SEMINE amounts will get updated to purchase orders in ERP. |
|
Send all attachments for the invoice during posting |
When set, all attachments will be sent to the ERP during invoice posting. |
|
Allow invoice processing in background |
When set, invoice posting from Semine to ERP will happen in background operation supported by ERP. See procedure below. |
|
Default page size for fetching purchase orders from ERP |
The number of purchase orders we will fetch from ERP at a time. |
|
No of days old purchase reciepts we will fetch from last successful run |
The number of days we set here, purchase receipts will be fetched based on CurrentDate - 'the number specified here in this text box. |
|
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. |
|
GET ../PDF
and then exported to Visma.netGetting field values from Visma.net
-
Start by logging in
-
Set language to English
-
Dimensions
Procedure in Visma net:-
For other dimensions (Project and Employee)
- Search for "Segmented Keys" under Preferences
- All Segmented Key IDs can be added in the Semine integration field Dimensions
- If customer has Deferral codes then that can be configured as Periode dimension in the box.
- Pipe (
|
) is used as separator among different dimensions.
-
For other dimensions (Project and Employee)
-
Segment keys
Procedure in Visma net:- Search for Segmented Keys under Registers
- Segmented Key ID: Click on the magnifying glass and select SUBACCOUNT
- Click on Segment ID 1 in the list.
- You should now see this screen
- Copy value from Segmented Key ID (SUBACCOUNT) into Root segment key.
-
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 benull
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 benull
in the configuration.
Example:null,D1,RequirementOrNoValue,Dimension|null,null,RequirementOrNoValue,VatCode
- Pipe (
-
Payment method
Navigate to Bills and Adjustments
-
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
4. Select the Companies.
5. Organisation ID from ERP will be the equivalent Semine field(Branch number).
-
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 PurchaseOrderCategorySync 0 */4 * * * Every 4th hour PurchaseOrderReceiptsSync 0 20 * * * Every day at 8 PM PurchaseOrderSync 0 */3 * * * Every 3rd hour InTransitInvoiceSync */20 * * * * Every 20 minutes - Configure Invoice Processing in background:
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.
Comments
0 comments
Please sign in to leave a comment.