What Tripletex gives through its API
Control.dev reads Tripletex through its API with an employee token that a Tripletex user creates for Control.dev’s approved application, and it sends only read requests. Control.dev only reads Tripletex, never writes to it, and Tripletex stays the book of record.
- Vouchers, general ledger postings and the chart of accounts
- Departments and projects
- Sales and supplier invoices, customers, suppliers and bank transactions
What an AI client gets from Tripletex alone today
Tripletex runs its own hosted MCP server, Tripletex MCP (Beta): an account administrator activates it for the company, and each employee then connects their own AI client with their own Tripletex login1. Tripletex says the server already covers over a hundred operations, from invoicing and time tracking to vouchers, VAT and payroll2.
The AI client gets exactly the access rights the user has in Tripletex, actions such as sending an invoice or posting a voucher need the user’s approval before they run, and all activity is logged3. The beta is free, and Tripletex says it will introduce a monthly price before launch, with notice in good time4.
What Control.dev’s MCP adds above Tripletex
Control.dev reads Tripletex 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 Tripletex 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.
Tripletex 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 an employee token for Control.dev Control.dev holds the consumer token, so you create only the employee token. The Tripletex user who will own it opens their API access settings, selects the application named Control, grants the accounting, invoice, customer and supplier, department and project, and bank areas, and copies the token into Control.dev. The steps are in the Tripletex 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 Tripletex group need, and what does it cost?
One per Tripletex 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 Tripletex?
No. Control.dev sends only read requests to Tripletex, so nothing it does changes Tripletex. 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 Tripletex 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 Tripletex MCP do, and when do you use both?
It lets an AI client work in your Tripletex account with your own access rights, and actions such as sending an invoice or posting a voucher wait for your approval3. Use it for work inside Tripletex. Use Control.dev for the group: entities on Tripletex 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.