You can use either the SOAP API, REST API or the user interface to open and manage company accounts. However, the user interface requires manual work so if the integration will have multiple companies or a complex set-up, API is recommended.
Steps to open account over API
When company account has been created, it can be configured by updating company settings, adding new users and activating services.
Note how the user creation works!
user_emailparameter doesn’t exist, a new user is created based on email and added to the company
user_emailparameter exists, this existing user is added to company
In situations where a new user is created, method returns unique
user_api_key. If method is called with an existing user, for security reasons only
company_uuid is returned.
Creating a company requires a vendor key and a user API key. You may use an existing user or create a new one.
When company account has been created, it can be configured by updating company settings, adding new users and activating services. Some services for receiving can only be activated after the verification step.
You can update the receiving setting (enable/disable) also using company_invoice_receiving. Note, that invoice receiving needs to be enabled in order to register company account to Peppol network or to use additional services such as Scanning.
Services allowed for an unverified company, for basic settings
Other services can be activated after the authorization is completed.
Verifying the account means that someone strongly authenticated needs to verify the account for the company before it can be used for sending and downloading. The purpose is to ensure customer is known and to prevent potential misuse of service. For Finnish companies, verification creates also automatically the request to open bank network.
Strong authentication includes an element that enables the service provider to verify the identity of the user with certainty. It can be implemented e.g. with login codes of online banks, mobile ID, bankID, an electronic identity card or passport.
The authentication of customer can happen as part of the partner onboarding process or with Visma Sign electronic signature service. Visma Sign is always used if the account is registered over Maventa UI. To use the account it is also required that the customer has accepted the Terms of Service .
Before implementing the verification part, decide which authorisation method suits your integration. If you want to use the partner authorisation, you need to check with Maventa that your process to authenticate the customer meets the authorisation requirements.
The account verification takes place with Visma Sign electronic signature service. A person who has rights to represent company related to electronic invoicing authenticates strongly with bank credentials, BankID or mobileID and signs a document where they confirm that account can be taken into use for the company.
Strong authentication via Visma Sign is currently available for the following countries: Finland, Sweden, Norway, Denmark.
If the customer has already signed the Terms of Service and has been strongly authenticated on the partner side before they start to use Maventa, it is possible to agree with Maventa about verification without the Visma Sign step. In this case, the authorisation of the account is not a visible step to the end customer when they open Maventa account. The partner provides in the authorisation API call an identifier that can be stored and used to link to authorisation event on their side (e.g.contract number, signing eventID). If needed partner has to be able to show that the authorisation has happened.
vendor_api_keyso that the correct authorisation option, Visma Sign or partner, follows the call).
company_stateparameter) changes from unverified (-1) to verified (1) and the account is ready to be used.
company_stateneeds to be verified (1).
|verified (1)||Company is authorised. Account can be used to send, download and register to Peppol network.|
|unverified (-1)||Authorisation required. Sending, downloading and registering to Peppol network is not possible.|
|unknown (0)||Authorisation functionality not in use. Account has not been verified with authorize_companies method, but can be used to send, download and register to Peppol network. This status is possible for older accounts / integrations.|
1) Request to sign sent to an email given in the API call
2) Signee logs into Visma Sign with a password given in the email
3) Signee sees a document that contains statement of authorisation and accepting attached Terms of Service
Authorisation for company “CompanyName (BID)” I assure that I have the right to represent the company “CompanyName (BID)” in matters concerning invoice transfer and hereby authorise it for sending and receiving of e-invoices. By signing this document I accept the Terms of Service (below).The signing of this document does not cause any expenses for the company. Visma Solutions Oy only invoices the company “CompanyName” based on the number of sent and received invoices according to the valid price list.
For Finnish companies there is additional mentioning of bank network opening
4) Signee authenticates strongly and signs the document electronically in Visma Sign.
1) Signing is ready
After Visma Sign flow has been completed, account is set to verified state (1) and is ready to be used.
You can complete Visma Sign authorization request with these test credentials:
For bankID you can use Nets test users from https://www.nets.eu/developer/e-ident/eids/Pages/testusers.aspx
In Partner verification, verifying the account is not a visible step to end customer company.
Authorize_companies method called - link to authentication event on the partner side given in the call in options - parameter.
After the API call, account is set to verified state (1) and is ready to be used.
In cases where the same signee has rights to represent more than one company it is possible to use one signing for multiple companies at the same time. For example in case of a housing company or accounting office that has signing / representation rights for multiple customers. One API call can be used to authorize up to 50 companies in time. For the authorisation to work, the companies that are authorised need to be from the same country.
New companies with a new user can be created for:
If you need to create a new company for an existing user, log-in to Maventa UI first.
Before production account can be used it needs to be verified using strong authentication and electronic signing. When the user logs in to the account for the first time, user needs to go through a set-up wizard where they add information of the company and configure some of the basic settings. The last step of the wizard is the company verification process with Visma Sign service. This signing process is the same as described with Visma Sign for API above, but in this case the process is initiated from UI. Visma Sign authorisation is not required if the company is created in the testing environment.
Different settings can be configured further in the web UI after user has logged in. Dedicated sections help to find the wanted settings and tell more information what the settings are about.
In Maventa there are two type of accounts; Company accounts and Partner accounts. Company account is the default account type. Partner accounts are used by the integrating partners (ERPs and such with multiple customers).
The key difference between a Partner and a regular Company account is that Partner accounts have an own identifier,
vendor_api_key, that is used to link actions to the partner company. The vendor api key is used for billing and reporting purposes. One Partner company can own many vendor_api_keys, for example one for each country they have customers in.
Integrators don’t need to worry about controlling the account types, all accounts registered to Maventa are first created as Company account and changed to account type Partner if and when needed by Maventa.
API endpoints tagged with [EXPERIMENTAL] should be considered as work in progress making them subject to change. Once the tag is removed, the contracts for these endpoints should be considered stable.