What Procountor gives through its API
Control.dev reads Procountor through its API with a dedicated technical user that has viewing rights, never payment or approval rights, and an API key for that user. Ledger access is read-only by default, and Procountor stays the book of record. The Finnish page Procountor-konserniraportointi covers the same setup.
- General ledger receipts and their rows
- Chart of accounts and dimensions
- Invoices, payments and payroll data, if you allow them
What an AI client gets from Procountor alone today
Procountor’s developer pages describe a RESTful API that connects software directly to financial management in Procountor, available in all Nordic countries1.
Procountor’s AI page says Finago AI Build will connect AI agents to Procountor workflows through Procountor MCP, marked as coming, and that its first phase builds and tests with selected accounting firms2.
What Control.dev’s MCP adds above Procountor
Control.dev syncs each Procountor company through its own integration, consolidates it with the group’s other ledgers, and gives the whole group to your AI client over MCP.
- Every entity on one group chart Each entity’s accounts are mapped to one group chart of accounts, and the eliminations, currency translation and CTA are done before the client reads. The eliminations sit in a column of their own.
- Statements first, not a raw export The client starts from the statements and the group structure, not a raw export of the general ledger. It finds what needs attention there and traces it to the entries.
- Every figure opens to its entries Every actual opens to the transactions behind it, and every row stays connected to its source system and legal entity.
- Your role decides what it sees Over MCP the client gets at most the access your role allows in Control.dev, and a read-only session rejects write tools.
- A plan with a reason on every cell The client can also draft budget values over MCP, and every value it writes carries its reason. The budget version keeps its change history, so a later variance analysis compares the actuals with the assumptions.
- Other MCP servers in the same conversation The client can use its other MCP servers in the same conversation, a CRM for example, and bring that data into a plan or an analysis next to the group’s actuals.
How each AI client connects is on the Control.dev MCP server, every tool it exposes on MCP tools and reusable instructions on finance skills, every integration and what comes in from it on the integrations page, and how the group view is built on multi-entity consolidation.
Already connected Claude to Procountor yourself? Control.dev vs building it yourself with Claude compares what you build and keep alive, what the client reads, who may change what, and what it costs.
Procountor MCP in three steps
Our team sets up the integration with you. Most companies have live data in under two hours from the first call, a larger group takes days, the hardest a few weeks, and there is no setup fee.
- 01Create a technical user in Procountor A Procountor administrator creates a dedicated technical user for Control.dev with viewing rights and an API key for it, and allows invoiceable API clients in Procountor’s integration settings. The steps are in the Procountor integration guide.
- 02Copy the server URL and the client ID into your client In Control.dev, open Data outputs and then MCP Server. Add the server URL and the client ID from the MCP Server page to Claude, ChatGPT or Codex as a remote MCP server, then sign in with your Control.dev login. If the page shows no client ID yet, ask us: registering your client is part of setup.
- 03Ask something you already know One company, one month, one figure. Check it against the same view in Control.dev, then ask the bigger questions.
Questions
How many integrations does a Procountor group need, and what does it cost?
One per Procountor company: one integration is one connected accounting system, such as one entity’s ledger. Control.dev publishes its monthly prices, excluding VAT: EUR 249 for one entity and one integration, EUR 499 for consolidation with three integrations and EUR 999 with five, where a Stripe connection counts as one integration, with no implementation fee, no multi-year contract and a notice period from one month. Larger groups are priced on request: book a demo.
Does Control.dev write to Procountor?
Not by default. Control.dev reads each ledger read-only by default, and eliminations and group entries stay in Control.dev without changing Procountor. Write-back is off unless you turn it on, and then it posts only drafts an Owner or Admin approved.
Where does the AI process our data?
Control.dev’s own AI features process data in the EU, and Control.dev’s data is hosted on Google Cloud in Hamina, Finland, encrypted in transit and at rest. What your AI client reads is processed under your agreement with its provider, so where that data goes is your decision.
How fast does a correction in Procountor reach the group view?
Scheduled syncs run at least daily, and you can trigger a refresh on demand. Backdated entries and corrections are synced again automatically, so the next sync carries a correction into the group view and into what the client reads.
What do Procountor’s pages say about MCP, and where does Control.dev fit?
Procountor’s AI page lists Procountor MCP as coming, built first with selected accounting firms2. Control.dev works at the group level: it reads each Procountor company through its own integration, and your AI client reads the consolidated group in Control.dev, within the access your role allows. An AI client can use other MCP servers in the same conversation as Control.dev.