Docs: System guides
Read e-conomic into Maplith
On this page
Best path
Recommended: export files. No official MCP server or client connector was found, and e-conomic's own complete export (Eksportér data) gives every register as a CSV file with all fields in one go, filtered by date. That is cheaper and more complete than fetching ledger entries through a chat.
Try the paths in this order:
- Your agent fetches it, with the access you already gave it. No named connector is confirmed: check the tools your agent already has. Your agent checks whether it already has an e-conomic tool it trusts, and if so reads only the chart of accounts, customers and products. Ledger entries and invoices should come from the export.
- Maplith reads an MCP server you already run. No official MCP server confirmed. Several community MCP servers for e-conomic exist on GitHub, but none is from Visma e-conomic. Maplith reads a server that serves MCP resources and takes a token a person types under Data sources › Systems, such as one your IT runs for a database.
- Export files, the fallback that always works. See the export steps below.
Datasets that make a good map
| Dataset | One row is | Key columns | Joins to |
|---|---|---|---|
| Customers (Kunder) | One customer with number, group, address and payment terms. | customer number, CVR number of a business customer, customer group, customer email (Maplith tries to mask it) | CRM companies by CVR number; webshop customers by email; booked invoices by customer number. |
| Booked invoices and lines (Bogførte fakturaer) | One booked sales invoice, with one row per invoice line. | invoice number, customer number, product number, other reference / order reference, invoice date, due date | Webshop orders by order reference; payment providers and bank lines by invoice number; Customers by customer number; Products by product number. |
| Products (Varer) | One product or service with number, group and sales account. | product number, product group | Webshop and inventory products by product number (SKU); invoice lines by product number. |
| Entries (Posteringer) | One booked line on one account, with date, voucher number and amount. | account number, voucher number, entry date, VAT code | Chart of accounts by account number; bank statements and payouts by date and amount; invoices and purchases by voucher number. |
| Chart of accounts (Kontoplan) | One account in the ledger, with number, name, type and VAT code. | account number, account type, VAT code | Entries, products and invoice lines by account number. |
| Suppliers (Leverandører) | One supplier with number, group and payment terms. | supplier number, CVR number of a business supplier, supplier group | Expense tools and purchase systems by CVR number; entries by supplier number. |
Columns are named, never their values. Maplith tries to mask personal data such as email addresses, but that is best effort: you decide what goes in.
Joins and identifiers the vendor documents
e-conomic’s documentation states these keys. Maplith checks them against the exports you share: a stated join is not a confirmed one.
| From | To | How many | Source |
|---|---|---|---|
Booked invoices and lines (Bogførte fakturaer), customer_number | Customers (Kunder), customer_number | many to one | restdocs.e-conomic.com |
Structure files
e-conomic can describe its structure without any rows. Share structure only: no examples, rows or credentials.
- e-conomic endpoint schemas (remove the values before you share it): Have your agent follow the schema-name links for customers and booked invoices in the REST documentation. Retain field types and references, removing example responses and defaults before sharing. Source: restdocs.e-conomic.com.
The access to give
Who usually has the rights: The superuser (superbruger) of the e-conomic agreement, or the external accountant or bookkeeper added as an administrator. e-conomic app roles have no read-only role, so pick the narrowest role that covers the data.
Choose the narrowest access that covers the data:
- Sales (customers, invoices, orders, products)
- Bookkeeping (accounts, accounting years, journals, entries)
- Superuser (everything)
Where to click:
- Click the orange gear (tandhjul)
- Alle indstillinger
- Udvidelser (left menu)
- Apps
- Add the app and approve access; the role chosen for the app (for example Sales or Bookkeeping) limits what it can reach
- To remove access later, click the cross next to the token on the same Apps page
A key or token made here stays in the tool that reads the system, never in a chat. Maplith asks for one only under Data sources › Systems in the app.
Export steps
Format: CSV Date range: The current and previous financial year
- Click the orange gear (tandhjul) and choose Alle indstillinger.
- Under Virksomhed in the left menu, choose Eksportér data.
- Choose Download lister enkeltvis (krypteret).
- Fill in Fra dato and Til dato to limit the period (blank exports everything).
- Click Send data, then click each register you need (customers, products, booked invoices and lines, entries, accounts, suppliers) to download it as a comma-separated file.
How much data
About 50–800 invoices; 300–5,000 entries a month (an estimate). Estimate for a small company, not a measured figure: each invoice, purchase and bank line creates a few entries, and e-conomic is used by somewhat larger small companies than the micro-business systems.
An agent that reads rows through a chat reads every one of them, about one token per four characters. Above a few thousand rows a dataset, or for a daily refresh, an MCP server or an export is the better path.
Always
- Read-only, and never a credential sent to Maplith through a chat.
- The same recent period, a few months, from every system.
- You decide what goes in.
Sources
Written from public documentation, last checked 2026-10-20: