Skip to main content
📊 See what this connector supports ↓

​
Introduction

Procountor is a Finnish cloud accounting and financial management software covering bookkeeping, invoicing, payments and payroll. The connector supports Procountor companies in Finland and Sweden.

​
Activate Procountor

​
Partner keys

You’ll need your own developer account, registered with Procountor. Procountor issues one API client (a client ID and a client secret) per integration. You can request it yourself, or ask your Chift point of contact to file the request with Procountor for you. Procountor reviews every request and can refuse it. It publishes no criteria, and may ask for an interview about your integration first. In our experience, allow about a week.
1

Register as a developer

Register on Procountor’s developer site. For questions, Procountor’s integration team answers at integrations@procountor.com.
2

Test with the test company

Procountor gives you a test company on its test server, with a client ID and a client secret for it. See Test Procountor below.
3

Request production access

When your integration is ready, fill in Procountor’s production access form. Procountor then issues your production client ID and client secret.

Activate Procountor in your Chift account

In Connectors, enter your Client ID and Client secret.

​
Connector settings

The Environment setting in the Chift connector settings for Procountor, set to Sandbox
Environment selects the Procountor server Chift connects to.
  • Production (default): Procountor’s production server.
  • Sandbox: Procountor’s test server (PTS).
Choose Sandbox while you test with your test company, and enter the client ID and client secret of that test company: production credentials do not work on the test server. End users then create their API key in Procountor’s test environment: a production key does not work on the test server, and a test key does not work in production.

​
Test Procountor

The test server is free and works like production, with a lower rate limit (see Rate limits). Procountor does not allow real or sensitive customer data on it (general information).

​
Vendor fees

Software editor (you)

No fees. The partner program and the test server are free.

End user

In Finland: €12.90 per month, plus €2.49 per month for each connected software, excl. VAT. In Sweden: the API is included in every plan.
In Finland, the fee is the same whatever the company’s plan. There is no opening fee. In Sweden, there is no opening fee either. In both countries, what is created through the API is priced as if it were created in Procountor, so vouchers count towards the plan’s quotas (general information). For plans and pricing, see Procountor’s Finnish price list and its Swedish API page.

​
Connect Procountor

Procountor setup guide for end users

The full step-by-step, with screenshots.
Before they start, your end users need:
  • an active Procountor account (Financials, Taloushallinto in Finnish)
  • admin access to the company, to create a dedicated user with at least accounting write rights
  • one connection per Procountor company: several companies means several connections
To connect, they:
  • create the dedicated user in Procountor
  • in Procountor, go to Basics › API client keys, click New API key, and enter the Client ID shown on the connection form
  • paste the generated key into the API key field of the connection form
There is no consent screen: the connection is active as soon as the form is submitted. If you set Environment to Sandbox, they create the key in Procountor’s test environment.

​
Rate limits

Procountor applies a fixed quota per API client: 60 requests per second in production, and 90 requests per minute on the test server. The budget is shared by all connections that use the same Client ID. Exceeding the limit may lead Procountor to suspend the service for the API client. Procountor says the limit may change, and does not document a way to raise it. Chift automatically manages these limits to optimize performance and prevent interruptions. However, once the API rate limit is reached, Chift cannot bypass these limitations. See Procountor’s API request documentation.

​
Limitations & specificities

One company per connection: a Procountor API key gives access to a single company. The connector always returns one folder.
Account type: Procountor has no account type field. The connector infers it from the account number, using the Finnish or Swedish standard ranges for the company’s country. An account outside the standard ranges may get the wrong type.VAT codes: Procountor has no single VAT code. A VAT treatment combines a rate, a type (sales or purchase) and a VAT status. The connector builds one code from the three, for example 25.5-SALES-1. Use the codes returned by the VAT codes endpoint.
One journal type: every entry created through the API is a generic JOURNAL receipt. You cannot choose another journal.Reverse charge: with a reverse-charge VAT code, send a reversed VAT account. With any other code, do not send one. Otherwise, the entry is rejected.VAT amount: the VAT amount of a line must equal its amount multiplied by the code’s rate, rounded to the cent, or the entry is rejected.Clients and suppliers: a line on a client or supplier is booked on that partner’s default receivable or payable account in Procountor. If the partner has none, the entry is rejected. Set it in Procountor, or send the general account on the line.Drafts: an entry not sent as posted stays a draft in Procountor. If its attachment or its approval fails, the draft is invalidated.Employee lines: lines on an employee account are not supported.Foreign currency: an entry in another currency than the company’s needs an exchange rate.
Entry number: Procountor has no dedicated field for it. The number goes into the receipt’s free-text name, which has no uniqueness check, so duplicates are not caught.
PDF size: a PDF attached to an entry is limited to 10 MB.

​
Coverage