What Spiris gives through its API
Control.dev connects to Spiris with OAuth: you sign in to Spiris from Control.dev, choose the company and approve read access to its accounting, sales and purchase data. Control.dev asks only for read scopes, never writes to Spiris, and Spiris stays the book of record.
- The chart of accounts and general ledger vouchers
- Projects, customers and suppliers
- Company settings, including the accounting lock date
What an AI client gets from Spiris alone today
Spiris hosts its own MCP server, Spiris MCP. In its first phase it works against Bookkeeping & Invoicing, more areas will follow, and it is free to use while in beta1. There is nothing to install, the user logs in with OAuth, and the tools cover customers, quotes, orders and invoices, suppliers, vouchers, the chart of accounts, the balance sheet and income statement with prior-year comparison, bank transactions, projects and cost centres2.
Creating an invoice or a voucher posts it to the accounts straight away, and draft tools let the AI prepare one for review first, booked only when the user approves3. An Administrator switches the service on user by user, and each connection works in the company chosen at login4. In September 2026 Spiris said users will soon be able to connect several customers at once5.
What Control.dev’s MCP adds above Spiris
Control.dev reads Spiris and every other ledger the group runs, then gives the whole group to the same 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 Spiris 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.
Spiris 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.
- 01Turn on API access and connect Spiris A Spiris administrator activates the Integration add-on for the company under Apps and extensions, once. Then you connect the entity’s data source in Control.dev, sign in to Spiris, choose the company and approve the read access. The steps are in the Spiris 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 Spiris group need, and what does it cost?
One per Spiris 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 Spiris?
No. Control.dev sends only read requests to Spiris, so nothing it does changes Spiris. Eliminations and group entries stay in Control.dev.
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 Spiris 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 does Spiris MCP do, and when do you use both?
It lets an AI client work in the Spiris company chosen at login4, and a created invoice or voucher posts straight away, with draft tools for a review first3. Use it for work inside Spiris. Use Control.dev for the group: entities on Spiris and on other ledgers on one group chart of accounts, with the eliminations done. One AI client can use both servers in the same conversation.