Skip to main content
Læs siden på dansk The e-conomic connector gives your AI access to your accounts in e-conomic (Visma): debtor overview, booked and overdue invoices, chart of accounts with live balances, entries, daily journals, products and creditors, without exports or spreadsheets. It can also create and edit customers, create, edit and duplicate draft invoices, make draft credit notes and work in the daily journal (create, edit, delete and book selected entries), always behind clear guardrails. You approve the Consile app on e-conomic’s own page, and your AI never sees the access itself.
Read + guardrailed write. 28 tools only read. The 12 write tools change nothing in e-conomic without an explicit confirmation (confirm: true). Without it, you only get a preview. Invoices and credit notes remain drafts, which you book yourself in e-conomic. Entries in the daily journal can be booked, but only the entry numbers you have seen and confirmed. An administrator can set the individual user to Read only. See Actions & guardrails.

Access

Read + guardrailed write. Read only can be chosen per user

Authentication

e-conomic app approval (Superuser)

Hosting

Hosted in the EU · Frankfurt
  • Price: 299 DKK/month excl. VAT. No lock-in, cancel at any time. The price covers 1 user and 1 e-conomic agreement. Each extra user and each extra agreement costs 149.50 DKK/month excl. VAT. See Pricing. e-conomic is also included in the Consile Studio membership and the free edition.
  • Multiple agreements: one connection covers one e-conomic agreement. If you have several agreements, for example several companies, an administrator adds them directly on the connector’s page in the portal: the Connections card → Add agreement. Each extra agreement gets its own address, for example https://mcp.consile.ai/economic-2/mcp, which you add in your AI as a separate connector. See Multiple agreements.
  • Endpoint: https://mcp.consile.ai/economic/mcp (your own named connector in your AI).

Prerequisites

1

Subscription

An administrator buys the connector in the portal. See Buy a connector.
2

Your AI connected

See Connect Claude or Connect ChatGPT. e-conomic can also be used in Microsoft 365 Copilot as a pilot, see Connect Microsoft 365 Copilot.
3

e-conomic approved

Approve the Consile app as a Superuser on the agreement you want to connect, see Connect e-conomic.
4

Access for each user

Whoever buys e-conomic automatically gets the included access. If more colleagues need e-conomic in their AI, an administrator gives them access on the person’s page under Team and chooses their access level at the same time (see Access level per user). Each extra user costs 149.50 DKK/month excl. VAT and is billed pro rata from the day access is given. A colleague without access can still see the e-conomic tools in their AI, but every call is refused with a message to ask an administrator for access. If you have the Consile Studio membership, an administrator instead gives one membership licence per person, and it also covers e-conomic. The access level is still chosen per person. See Team.

What can it do? (tools)

You do not need to know the tool names. You ask in natural language, and your AI picks and calls the right tool itself. Each tool is called economic__<tool> (for example economic__list_customers); in the tables below the names are shown without the prefix. The connector provides 40 tools in total: 28 read-only (pure reading) and 12 guardrailed write tools. A user whom an administrator has set to Read only only gets the 28 (see Access level per user).

Reading (28 read-only)

Debtors & liquidity Invoices Bookkeeping & accounts Daily journal Products & creditors Lookups (reference numbers for customers, invoices and entries) Support

Writing (12 guardrailed tools)

These twelve tools are the only ones that change anything in e-conomic. Eight work with customers and sales documents, four with the daily journal. A call without confirm: true never changes anything, but shows exactly which change would be sent. The change is only carried out when the call contains confirm: true. Normally your AI shows you the preview and only calls again with confirm: true once you have said yes.

Building on top yourself? See the API reference

Full reference with all 40 tools, arguments, pagination, filters, guardrail fields and return values.

How the guardrail works

The guardrails are built into the e-conomic tools:
  1. All twelve write tools are dry-run by default. A call without confirm: true never changes anything in e-conomic. Some tools first read the record they are to change, copy, delete or book, so the preview shows the right content. You get a structured preview of exactly the change (method, path and content) that would be sent.
  2. The change is only carried out with confirm: true. In accounting there is no write without consequences, so there are no exceptions. Booking also requires a check value from the preview and therefore always takes two calls.
  3. Invoices and credit notes remain drafts. The connector cannot book or send an invoice or credit note. You review and book them yourself in e-conomic.
  4. Booking from the daily journal has an extra guardrail. book_journal_entries only books the entry numbers you specify, at most 50 at a time and never the whole journal. The preview shows each entry (type, date, amount, text) and a total per currency. If an entry has changed between preview and confirmation, the booking is refused, and nothing is booked. Booking cannot be undone.
  5. Only drafts can be deleted. delete_journal_entry deletes one unbooked entry at a time. Booked entries and booked invoices cannot be changed or deleted. Corrections are made with a reversing entry or a credit note.
  6. Credit notes always have negative lines. When an invoice is reversed, the credit note is dated today, unless you specify another date. A document that is already a credit note cannot be reversed again.
  7. Edits only change the fields you specify. update_customer, update_draft_invoice and update_journal_entries keep the fields you do not specify. The confirmation call applies your changes to the record as it looks at that time.
In practice your AI normally shows you the plan first and only sends confirm: true once you have said yes. It is the call with confirm: true that actually changes something in e-conomic.
Read the whole confirmation model, which applies across all write connectors, under Actions & guardrails.

Access level per user

For e-conomic, an administrator can choose the access level for each user (this is also possible for Uniconta). You do it in the portal under Team: click the user’s name, and for e-conomic choose between None, Read only (28), Full access (40) and Custom, where you choose exactly the tools the user gets (see Custom access). The numbers count the tools the organization has switched on.
  • Both levels cost the same.
  • The level applies to the user’s access to all your e-conomic agreements.
  • If a user is on Read only, Consile blocks all write operations on the server for that user: the write tools do not show in the user’s AI, and a call to them is refused without anything being changed.
  • The connection to e-conomic belongs to the company, so colleagues with Full access can still write.
  • If an open conversation has already fetched the tool list, the write tools can still be there until the user starts a new conversation. Calls to them are refused.
  • Only administrators can change the level. If you choose a level for a user who does not have access to e-conomic yet, the user gets access at the same time. If it is an extra user, you confirm the purchase first.

Try asking

“Which customers are most overdue right now, and how much do they owe in total?”
“Give me a debtor overview: paid, unpaid and overdue.”
“How much does customer 1024 owe, and how much of it is overdue?”
“Show revenue and profit per account for the current fiscal year.”
“What is the movement on account 1010 in 2025?”
“Show the lines on the latest booked invoice to customer 1024.”
“Show booked invoices from May with a remaining amount.”
“Create a new customer <company name> in DKK.” (you get a preview and must confirm)
“Make a draft invoice for customer 1024 with two lines.” (you are asked to confirm)
“Make a draft credit note that reverses invoice 10234.” (you get a preview and must confirm)
“Find entries in the daily journal with the text ‘rent’, and change the amount to 12,500 DKK. Show me the change first.”
“Book entries 41 and 42 in daily journal 1, but show them to me before anything is booked.”
Mention a fiscal year or a customer number in the question, and the answer is precise right away. Several tools require a year (list_account_entries, get_account_year_total). For creation, your AI looks up reference numbers itself via the list_* tools (group, payment terms, VAT zone, layout, daily journal).

Limitations

  • Writing is guardrailed, not unrestricted. The twelve write tools only work behind the confirmation guardrail above. The guardrail consists of safe defaults in the connector and is not an absolute guarantee.
  • Invoices and credit notes are not booked by your AI. They are created and edited as drafts. A draft is a real document that the bookkeeper sees in e-conomic, but it only affects the accounts when you book it in e-conomic.
  • Booked is booked. Booking from the daily journal cannot be undone, and booked entries and invoices cannot be edited or deleted via the connector. An error is corrected with a reversing entry or a credit note. At most 50 entries per call.
  • The daily journal cannot be searched by text or amount at e-conomic. Your AI narrows down by daily journal, date, account and similar, and finds text and amount in the fetched rows.
  • Invoice PDF in chat: download_invoice_pdf returns the file as base64, which a regular chat cannot turn into an attachment. In a chat, you fetch the PDF in e-conomic.
  • Grant token without renewal: the access is a static token per agreement. If someone removes the Consile app in e-conomic, the connector stops working, and your AI gets the message e-conomic rejected the grant token (401); reconnect required. The same message (with 403) can also mean that the app role is too narrow for a write. validate_connection can confirm the status. The portal can still show Connected, because the access is still stored at Consile. See Reconnect.
Is something not working as expected? See Troubleshooting.