Procountor

With Severa-Procountor integration, you can transfer data automatically between the systems and ensure smooth billing for your company:

✔️ Automatic data transfer: Sales invoices, travel reimbursements, and purchase invoices are transferred automatically between the systems.
✔️ Automated synchronization cycle: The integration fetches invoices to be transferred automatically according to the synchronization schedule, based on the invoice status defined in the system.
✔️ Dimension management: Projects, cost centers, and business units are transferred automatically as dimension data between the systems.
✔️ Purchase invoices as project expenses: Purchase invoices can be imported from Procountor directly into Severa as project expenses.

The integration’s data transfer works automatically in a cycle staggered by time of day. This optimizes system performance and ensures that the data is as up to date as possible when it is needed the most. Data is synchronized according to the following schedule (times in Finnish time):

• Day (08:00–19:00): Data is updated automatically every 10 minutes.
• Evening (19:00–00:00): Data is updated every 1 hour.
• Night (00:00–08:00): No data is transferred during the night. Changes made during the night are synchronized in bulk starting at 08:00 in the morning.

• Country support: Integration is supported in Finland and Sweden.
• System edition: Integration is available in Severa’s Business, Platinum, and Enterprise editions.
• Procountor agreement: Company must have a valid agreement with Procountor for using Procountor and the integration.
• Old integration interface: If the company has used the old interface from Severa to Procountor, the company must terminate it via Procountor’s customer service before taking the new integration into use.
• Invoice numbering: Invoice numbering is always determined in Procountor. Severa’s own invoice number is transferred in the background to the Initial invoice number field and is not visible to the customer.
• Sender information: The invoice sender’s information is updated to the invoice directly from Procountor’s organization details.

Customer data is transferred from Severa to Procountor automatically along with sales invoices according to the following rules:

• Time of transfer: Customer data is created in Procountor’s customer registry when the first sales invoice is created and transferred for that customer.
• Matching criteria: Severa’s customers are matched to Procountor’s business partners based on the customer number. Unlike in the old integration, matching is no longer done using a combination of VAT number and customer number, but only the customer number.
• Before connecting the integration: Carefully ensure that the customer registries in the systems, and especially the customer numbers, correspond exactly to each other so that the data is linked correctly. Also ensure that customers have up-to-date address information filled in Severa (street address, postal code, city, and country) and that the Postal address checkbox is selected for the customer’s address.

Products and work types are transferred from Severa to Procountor automatically along with sales invoices according to the following rules:

• Time of transfer: Product data is created in Procountor’s product registry when the first sales invoice containing those products is created and transferred to the system.
• Code matching: The codes of products and work types used in Severa must match the codes in Procountor’s product registry so that invoice rows are allocated correctly. Products without a code are transferred with the default code defined in the settings. The default code must also exist in Procountor’s product registry.
• Travel expenses: Travel expense codes must also match in both systems. Travel expense codes change yearly. New and up-to-date codes must always be checked in Procountor and updated to Severa.
• Before connecting the integration: Carefully ensure that the product registries in the systems correspond exactly to each other so that the data is linked correctly.

Projects, cost centers, and business units are transferred from Severa to Procountor automatically to the dimensions specified in the integration settings. If a dimension item is closed or disabled, its status is also updated in Procountor. The project name in Severa must not contain special characters to ensure correct transfer to Procountor.

Invoices, travel reimbursements, and purchase invoices are transferred with the following definitions:

• Automatic transfer status: Sales invoices are transferred automatically from the invoice status defined in Severa’s settings to Procountor. The transfer status is defined in Severa’s integration settings.
• Purchase invoices: Purchase invoices are imported into Severa after they have been dimensioned to projects in Procountor and when the status is Approved, Payment queued, Payment sent to bank, Partially paid, Paid, or Marked paid.

Invoice attachments

For sales invoices, you can define how attachments are transferred with the invoice data:

• PDF file: Transfer the PDF file including attachments.
• Invoice breakdown: Transfer the invoice breakdown, which transfers attachments without the PDF image of Severa’s invoice.
• Do not transfer: Attachments are not transferred at all. If attachment transfer is not selected, the attachment is transferred only if the invoice has attachments and line item grouping is enabled. Attachments are transferred with both e-invoices and paper invoices.

Attachments of travel reimbursements (the travel reimbursement + all attachments as one file) are transferred in the integration. Sales and travel invoice attachments must be in GIF, JPEG, or PDF format. The file name must not contain special characters. The maximum file size for attachments is 10 MB.

First, you need to allow API usage:

1. Log in to Procountor
2. Navigate to Management > Company details > Usage settings > Allow the usage of invoiceable API clients
3. Add a new technical API user from Management > Users and permissions > Add new user.
   1. Name the user, for example, as follows: first name is your company name, last name is the software name (Severa).
   2. Email address is mandatory. Use your own email, for example, but we recommend limiting email notifications in Procountor settings.
4. Modify the API user's user rights from Management > Users and permissions. Go through each permission section and set to All rights.
5. To ensure proper access control, activate Allow only M2M login to API. This ensures the integration interface has restricted rights, separate from the user interface.

Then you need to create the API key:

1. Navigate to the API keys page via the Basic information menu located in the top right corner.
2. Click New API key and create a new API key.
3. Insert Client id text: VismaSeveraClient
4. Select Create. After saving the details, a new integration-specific key is created and displayed.
5. Copy the displayed API key to your clipboard.
6. Paste the copied API key to Severa under the gear icon in integration settings > Settings > Integrations > Procountor > General > API key.
7. Click Save.

An admin user can create an API key for another user in the selected organization if the user's permissions are sufficient. This allows the creation of a technical API user with access to the interface but not the UI.

1. Navigate to settings from the gear icon > Settings > Organization > Chart of accounts.

   • Add sales accounts used in Procountor to Severa.
   • Define all sales accounts in use.
   • You can define separate sales accounts for work hours, travel expenses, and products.
   • Enter the sales account name and number. The sales account number must match Procountor's information.

2. Using the Registry comparison report feature in the integration settings, you can check how products and customers are matched between the systems. If necessary, add products in use and ensure they exist in both systems. The same code can be used for all products if desired. If using the same code, skip the following steps and proceed to step 3 of Severa settings. Products will then transfer to Procountor with the default code.

   • Navigate to settings from the gear icon > Settings > Work time, travel expense & product registries > Regular products.
   • Add a new product or edit existing ones.
   • Enter a code for the product and select a sales account to be used (you can also define other details for the product if desired). The code must match the product code in Procountor.
   • Define all products in use.

3. Edit/add work types and work type codes used in Severa to match products in Procountor. Work types ensure the hours on the invoice are allocated to Procountor’s product register.

   • Navigate to settings from the gear icon > Settings > Work time, travel expense & product registries > Work types.
   • Add codes for all work types used in Severa, targeting them as products in Procountor.

4. Edit/add travel expenses used in Severa to match Procountor’s travel expense registry. Severa's travel expense codes must be the same as in Procountor. Codes change annually in Procountor, and the admin user must update the data in Severa.

   • Navigate to settings from the gear icon > Settings > Work time, travel expense & product registries > Travel expense types.
   • Add codes for all travel expenses used in Severa, targeting them as travel expenses in Procountor.

5. Navigate to settings from the gear icon > Settings > Organization > Bank accounts. Click the pencil icon and edit the bank account number to IBAN format.

6. Create invoice statuses in Severa from which sales invoices are fetched to Procountor.

   • Navigate to settings from the gear icon > Settings > Billing > Invoice statuses.
   • Add a new invoice status, e.g., Waiting for transfer to Procountor. Select the following settings for the status: Not editable, Invoice number, Sent. You can also set this status as the default for credit invoices if necessary.
   • When invoices are transferred to Procountor, they automatically change status. You can add a status such as Transferred to Procountor or use the Sent status for this purpose.
   • Drag and drop the invoice statuses in order so that the status with Paid setup remains below the new statuses as the last status in the process.

7. If Travel reimbursements-add-on is enabled in Severa, fill in the employee number and bank account information for every user. Without personal information, travel reimbursements cannot be transferred to Procountor. Ensure the same employee number is also defined in Procountor.

   • Navigate to user management from the gear icon > Settings > User management.
   • Open the user's profile by clicking the user's name.
   • Add the user's Employee number (code) and Bank account number.

8. Create travel reimbursement statuses in Severa from which travel reimbursements are fetched to Procountor.

   • Navigate to settings from the gear icon > Settings > Hours and expenses > Travel reimbursements > Travel reimbursement statuses.
   • Add a new travel reimbursement status, for example, Waiting for transfer to Procountor. Select the following settings for the status: Locked and Approved. You can also use the existing Approved status.
   • When travel reimbursements are transferred to Procountor, they automatically change status. Add a status Transferred to Procountor, with the settings Locked and Approved.

1. Navigate to settings from the gear icon > Settings > Integrations > Procountor > Settings.

2. Select Add settings and choose the desired Company and click Save.

3. Define the needed transfer settings. Make sure that the API key received from Procountor is in place. Integration will not activate without it. If the API key is correct, you will be able to view all existing Procountor dimensions and select accordingly in the Dimension names section.

4. Continue with general transfer settings and ensure all required fields are filled in:

   • Choose whether customers are created in Procountor's customer registry.
   • Choose whether products are added to Procountor's product registry.
   • Define the default code for products. The default code must also be found in Procountor's product registry.
   • Define the default code for work types. The default code must also be found in Procountor's product registry.
   • Define the default code for travel expenses. The default code must also be found in Procountor's travel expense registry.
   • Choose dimension names for business units, projects, and cost centers.
   • If you want to receive email notifications of errors in integration, check the box Send email when integration reports on errors.

1. Select the travel reimbursement statuses in Severa before and after transfer.
2. Select travel reimbursement status in Procountor after transfer. Initially, it is recommended to select the status Not finished, allowing you to edit and check the travel expense in Procountor.
3. Choose whether the business unit is transferred as dimension information for the travel expense line to Procountor.
4. Choose whether the cost center is transferred as dimension information for the travel expense line to Procountor.
5. Choose whether the project is transferred as dimension information for the travel expense line to Procountor.
6. Select whether Severa's users are updated in Procountor's personal register.

1. Select the invoice status from which the invoices are transferred to Procountor. It can be, for example, Waiting for transfer to Procountor.
2. Select the status to which invoices are transferred after transfer, for example, Transferred to Procountor or Sent.
3. Select the status to which invoices are transferred in Procountor:
   1. If you want the invoice to be transferred to Procountor in a not finished status so that the invoice is not yet sent automatically after the transfer, select the status Not finished. This allows you to edit and check the invoice in Procountor before sending it.
   2. If you want the invoice to be sent to the customer immediately after it has been successfully transferred to Procountor, select the status Sent.
4. Choose whether the business unit is transferred as dimension information for the invoice line to Procountor.
5. Choose whether the cost center is transferred as dimension information for the invoice line to Procountor.
6. Choose whether the project is transferred as dimension information for the invoice line to Procountor.
7. Select whether attachments are transferred with the invoice or not (an invoice attachment is an invoice PDF = invoice pages, breakdown + attachments). If you want to transfer only the invoice breakdown page, do not change the setting and leave the selection as Not selected.
8. Optionally, enable email sending of invoices. When the checkbox is marked, the following logic is used for choosing the sending channel:
   • If the customer has e-invoice information filled in their customer information, the invoice is sent as an e-invoice.
   • If the customer does not have e-invoice information filled but a contact person with an email address has been selected for the invoice, the invoice is sent by email to that address. If the customer contact does not have an email address, the email address entered on the customer card is used.
   • If the customer does not have e-invoice information filled, and no customer contact has been selected for the invoice or the selected contact does not have an email address, and no separate email address has been defined in the customer information, the invoice is sent by mail.

If Maventa is used for sending invoices, but you want to transfer invoices from Severa to Procountor for accounting after sending, select Status in procountor > Not sent in the Transfer statuses section of the sales invoice transfer settings. This way, the invoice will not be attempted to be sent again from Procountor to the customer.

Purchase invoice transfer settings

Purchase invoice transfer does not require any specific settings. It can be activated separately if desired. Create a purchase invoice in Procountor and dimension it to a project. Update the invoice’s status to one of the following: Approved, Payment queued, Payment sent to bank, Partially paid, Paid, or Marked paid. Costs will be transferred with a delay of about 10 minutes.

When the settings have been defined, before enabling the integration, make sure of the following:

✔️ Agreement matters: Use of the integration has been confirmed with Procountor, and the old integration interface has been terminated.
✔️ Registry and data matching: Ensure that the customer, product, work type, and travel expense registries as well as projects have been checked to correspond between the systems.
✔️ Bank accounts: Ensure that bank accounts are defined in IBAN format.
✔️ User details: Ensure that users for whom travel reimbursements need to be transferred have an employee number (code) and bank account in Severa, and check that the employee number is the same in Procountor.

When all required information is filled, you can activate the integration:

1. Click the main toggle Enable Procountor in the top right corner of the General section.
2. When the main toggle is enabled, you can separately enable or disable Travel reimbursement and Purchase invoice transfer later in the relevant settings section.

Follow the same instructions as above, but first select the correct company from the Company menu for which you are configuring the settings. Settings need to be defined for all business units that are companies and have their own VAT number.

Leave all other business units undefined, as the integration can transfer data only based on the business unit hierarchy.

Invoice material	Severa	Procountor	Character limit / other information
counterParty / contactPersonName	Billing contact	Contact person	28. The company's own contact person in the detailed information section of the invoice. The invoicing contact person and the customer contact person are separated with a / sign.
counterParty / identifier	Customer business ID (from the invoice)	Business ID or national identification number
counterParty / customerNumber	Customer number (from customer card)	Customer number
counterParty / counterPartyAddress / name	Customer name (from the invoice)	Customer address / Name and details	80
counterParty / counterPartyAddress / street	Customer address (from the invoice)	Customer address / Street address	80. Note that the address information is mandatory when the invoicing channel is mail.
counterParty / counterPartyAddress / city	Customer city (from the invoice)	Customer address / City	40
counterParty / counterPartyAddress / zip	Customer postal code (from the invoice)	Customer address / Postal code	20
counterParty / counterPartyAddress / country	Customer country code (based on address country)	Customer address / Country code
type		Invoice type	SALES_INVOICE
originalInvoiceNumber	Invoice number	Biller's invoice number	Procountor's own invoice number is always used for Procountor's invoice. If needed, you can get Severa's invoice number in Biller's invoice number field. Note that for sales invoices and travel invoices the use of the Other system invoice number field must be agreed separately with Procountor.
date	Invoice date	Invoice date
orderReference	Order number	Order number	70
additionalInformation	Our reference / Your reference / Notes / Free text above the invoice rows / Free text below the invoice rows	Additional information	10 000
paymentInfo / dueDate	Due date	Due date	The payment term can be between 0-999 days.
penaltyPercent	Overdue interest	Overdue interest	Scale: 2.
invoiceChannel		Invoice channel	ELECTRONIC_INVOICE: Selected if e-invoice information is filled in the customer data.EMAIL: Selected if SendByEmail is enabled or receiverContactEmail or billingCustomerEmail is provided.MAIL: Selected if none of the above conditions are met.
status		Invoice status	Always NOT FINISHED
language	Severa's invoice language	Invoice language	Options: english, finnish, swedish, estonian, norwegian and danish.

Invoice material	Severa	Procountor	Character limit / other information
productCode	Product code / work type / travel expense from the invoice row	Product code
product	Description	Product name
quantity	Quantity	Quantity
unit	Unit	Unit
unitPrice	Unit price	Unit price
accountingValue	Dimension	Dimensioning instructions	Used as a basis for the dimension of the accounting row.
vatPercent	Tax rate of the invoice row	VAT-%

Common error situations

If data remains in error in the integration (e.g., in the transfer of sales invoices), a record of this will remain in Severa's transfer log. The transfer log can be found under the gear icon Integrations > Procountor > Transfer log.

As a general guideline for error situations, we always recommend first checking the error message and its content. If the error requires corrections to the invoice, move the invoice to draft status in Severa and make the necessary corrections. After this, you can try the transfer again.

If necessary, please contact our customer service to resolve error situations. You can also find descriptions of the most common error codes on Procountor's website.

Subject	Error message	Solution proposal
Transfer of travel reimbursements/sales invoices	CLOSED_FISCAL_PERIOD	The invoice is attempted to be transferred to a closed fiscal period. Check the invoice date in Severa and the fiscal period in Procountor and try the invoice transfer again.
Transfer of sales invoices	ERROR_BRN_CODE	The customer's business ID on the invoice is in an incorrect format. Correct the business ID on Severa's customer card and try the invoice transfer again.
Transfer of sales invoices	SIZE_MUST_BE_BETWEEN_0_AND_100	The invoice contains rows where the maximum character count has been exceeded. Check the field-specific restrictions in the table above and correct the information on the invoice.
Customer registry	Could not add X to Procountor, because another partner X with the same number and different VAT number already exists there.	The customer cannot be transferred if a customer with the same name and customer number but a different business ID is found in Procountor. Check the formatting of the business ID and correct the information to match between the systems.

Did you find it helpful? Yes No

Send feedback