What e-conomic gives through its API
Control.dev reads e-conomic through its REST API with an agreement grant token, created when a user approves Control.dev’s app in e-conomic for the agreement being connected. The approval does not give Control.dev the user’s password. Control.dev sends only read requests, never writes to e-conomic, and e-conomic stays the book of record.
- Chart of accounts, VAT accounts, accounting years and periods
- Journals, vouchers and posted entries
- Booked sales invoices, customers and suppliers, with dimensions where the module is on
What an AI client gets from e-conomic alone today
e-conomic’s developer pages describe two RESTful APIs: OpenAPI, where all new functionality is added, and REST, which is in a feature freeze1. An app reaches the accounting data with two tokens, the second created when an accounting user grants the app access through its installation URL, and that user must hold the permissions the app requires2. e-conomic’s help pages say API access for integrations comes with the Plus package and up3.
Inside the product, e-conomic’s own assistant EVA, in beta, helps a user understand their own accounting data. It sees only the agreement the user is in and the data the user can access, and it is read only4.
What Control.dev’s MCP adds above e-conomic
Control.dev reads e-conomic 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 e-conomic 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.
e-conomic 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.
- 01Approve Control.dev’s app in e-conomic In Control.dev, add e-conomic as a data source and sign in to e-conomic in the tab that opens. Select the agreement, approve Control.dev’s access and paste the agreement grant token into Control.dev. Control.dev manages the app credentials, so you create no app of your own. The steps are in the e-conomic 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 an e-conomic group need, and what does it cost?
One per e-conomic 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 e-conomic?
No. Control.dev sends only read requests to e-conomic, so nothing it does changes e-conomic. 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 e-conomic 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 e-conomic’s API give an AI client today, and when do you use both?
e-conomic’s APIs give an app the accounting data of one agreement once a user grants it access2, with new functionality added on OpenAPI1, and EVA, in beta, reads a user’s own data inside the product4. Use them for work inside one e-conomic agreement. Use Control.dev for the group: entities on e-conomic and on other ledgers on one group chart of accounts, with the eliminations done. One AI client can use Control.dev and its other MCP servers in the same conversation.