What Easor gives through its API
Control.dev connects to Easor with a server-to-server application that is granted access to the organisations you choose, and it uses only read operations. Control.dev only reads Easor, never writes to it, and Easor stays the book of record.
- General ledger vouchers and their posting rows
- The chart of accounts, accounting periods and dimension settings
- Cost centres, cost types, projects and project types
What an AI client gets from Easor alone today
Easor’s integrations page describes a REST API with JSON and OAuth2 authentication. Its standardised data model covers sales and purchase invoices, accounting entries, the customer register, the product register and journal vouchers, among others, and the API can create, fetch, update and delete data1.
Easor Marketplace’s developer page lists the interfaces Sales Invoicing, Invoice Payments, Accounting Settings, General Ledger and Organization. API credentials are not granted automatically: a developer registers in the developer portal and tells Easor’s integration support, and credentials are issued per use case with the rights limited to the minimum2.
What Control.dev’s MCP adds above Easor
Control.dev reads Easor 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 Easor 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.
Easor 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.
- 01Ask Easor to grant the access Ask your Easor contact to enable the Control.dev integration for the organisation, covering its organisation information, accounting settings and general ledger. You then enter the organisation number and the API region in Control.dev. The organisation number is the Talenom customer number shown in your service agreement or onboarding material, not the business ID, and Control.dev’s field for it is Talenom Organization Number. The steps are in the Easor by Talenom 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 Easor group need, and what does it cost?
One per Easor organisation: 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 Easor?
No. Control.dev sends only read requests to Easor, so nothing it does changes Easor. 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 Easor 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 Easor’s API do, and when do you use both?
It lets other software create, fetch, update and delete invoices, accounting entries and register data in Easor1, with credentials issued per use case and limited to the minimum2. Use it, and the integrations built on it, for work inside Easor. Use Control.dev for the group: entities on Easor and on other ledgers on one group chart of accounts, with the eliminations done, read by your AI client over MCP. That client can use its other MCP servers in the same conversation.