Create API identifiers
- In Netvisor, choose the company.
- Go to Company → API identifiers.
- Choose Create new API identifier.
- Copy the User ID and Key.
- Find the company’s organization ID in Company → Company information.
Allow Control’s interface resources
- Go to Company → Rights of interface resources.
- Under finished or ready-made integrations, search for
control.dev. - Select control.dev / Finata oy.
- Allow the resources listed below. Only enable the conditional resources for features enabled on the Control data source.
490FC171429C1DA23EE3BE2F954BF7C9.
Editing resource rights requires the appropriate Netvisor administrator rights. Ask the company or accounting-office administrator if you cannot open the page.
Interface resources required
Control only reads these resources. Do not allow unrelated write or payment resources. The ready-made control.dev / Finata oy entry is preferred because it identifies Control clearly in Netvisor’s integration list; verify its resource selections against this table.
Fill the fields in Control
Save and verify the credentials after all three values are present.
Copy the User ID / Käyttäjätunniste exactly as Netvisor displays it under API
identifiers. It can be a long identifier, including a UUID followed by a suffix;
it is not necessarily a short username. Do not replace it with your Netvisor login
name or treat it as an API key based on its length. Copy the separate Key / Avain
into the API Key field.
Data imported
- Chart of accounts, dimensions, and accounting periods
- General-ledger vouchers
- Sales invoices when Load invoices is enabled for the integration
- Purchase invoices when Load purchase invoices is enabled
- Sales payments when Load sales payments is enabled
When Test Credentials fails
Control shows which Netvisor resources were refused and who can unblock them. The two failures below look identical from the outside but have different fixes, so start by reading which one Control reported.”Netvisor has not allowed Control to read this data”
Netvisor accepted the User ID and API Key and then refused the request (SERVICE_ACCESS_ERROR). The keys are fine;
the interface resources listed in the error have not been allowed for Control.
Fix it on the Company → Rights of interface resources page, as described in
Allow Control’s interface resources. Editing that page needs company
administrator (KH) or accounting-office administrator (TPK) rights, so the accounting office often has to do it.
Re-pasting the keys will not help.
”Netvisor rejected the User ID or API Key”
Netvisor did not accept the API identifier at all (AUTHENTICATION_FAILED), so the request never reached the
permission check. Do not change interface resource rights for this. Instead:
- Confirm the identifier still exists and is active under Company → API identifiers. Regenerating a key invalidates the old one.
- Re-copy the User ID and Key with no leading or trailing spaces.
- Check the Organization ID is the company’s Y-tunnus, and that the identifier was created while that same company was selected in Netvisor. A wrong Organization ID reports as “Netvisor could not find this company”.
Common problems
- Cannot create API identifiers: the company’s Netvisor package does not include the API. Upgrade to Professional, Premium, or Palkat in Netvisor Store.
- Missing User ID: enter the API identifier’s User ID, not your email address.
- Control says a long User ID looks like an API key: confirm that it came from Netvisor’s User ID / Käyttäjätunniste field. Long IDs are supported. Refresh Control if it still shows the older warning. If Save and test remains disabled, report the field warning to support without sending the API key; Netvisor has not yet received a verification request from that submission.
- Missing Organization ID: enter the company organization ID, not an integration identifier.
- Only some data is missing: a conditional resource is not allowed. Enabling Load invoices, Load purchase invoices, or Load sales payments on the data source also requires the matching resources from the table above.