# e-conomic: how to read it into Maplith

*Accounting · also known as Visma e-conomic, economic · last checked 2026-10-20 · recipe `maplith://systems/e-conomic`*

e-conomic holds a company's customers, suppliers, products, booked invoices, chart of accounts and every ledger entry, which tie sales, purchases and payments to the books.

## 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 (ADR-0031):

1. **Your agent fetches it**, with the access your human already gave you. No named client connector confirmed: check the tools you already have. The customer's 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.
2. **Maplith reads an MCP server your human already has.** No official MCP server confirmed. Several community MCP servers for e-conomic exist on GitHub, but none is from Visma e-conomic. Maplith reads only a server that serves MCP resources and takes a token a person types under Data sources › Systems in the Maplith app, such as the customer-run template for a database (ADR-0028).
3. **Export files**, the fallback that always works: see *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: your human decides what goes in.

## Declared joins and identifier formats

Vendor documentation states these keys; Maplith checks them against the shared exports. A declaration is not a confirmation.

- Booked invoices and lines (Bogførte fakturaer).customer_number → Customers (Kunder).customer_number (N:1). Source: https://restdocs.e-conomic.com/

## Structure artefacts

- **e-conomic endpoint schemas** (api_spec; remove values before sharing): 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: https://restdocs.e-conomic.com/

Share structure only: no examples, rows, credentials or pinned data. Your human chooses what to send.

## Read-only access

**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.

**For the key your own agent's client uses, choose only these read permissions:** `Sales (customers, invoices, orders, products)`, `Bookkeeping (accounts, accounting years, journals, entries)`, `Superuser (everything)`

**Where to click:**

1. Click the orange gear (tandhjul)
2. Alle indstillinger
3. Udvidelser (left menu)
4. Apps
5. Add the app and approve access; the role chosen for the app (for example Sales or Bookkeeping) limits what it can reach
6. 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 for your human, never in a chat. Maplith asks for one only under Data sources › Systems in the app, and only for an MCP server it can read.

## Export steps

**Format:** CSV · **Date range:** The current and previous financial year

1. Click the orange gear (tandhjul) and choose Alle indstillinger.
2. Under Virksomhed in the left menu, choose Eksportér data.
3. Choose Download lister enkeltvis (krypteret).
4. Fill in Fra dato and Til dato to limit the period (blank exports everything).
5. 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.

## Volume hint

**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.

Every row an agent reads passes through its context, about one token per four characters. Above a few thousand rows a dataset, or for a daily refresh, prefer an MCP server or an export over fetching through the chat.

## Always

- Read-only, and never a credential sent to Maplith through the chat.
- The same recent period, a few months, from every system.
- Your human decides what goes in.

## Sources

Written from the vendor's public documentation, last checked 2026-10-20:

- https://www.e-conomic.dk/support/artikler/eksporter-data-fra-e-conomic
- https://www.e-conomic.dk/support/artikler/om-api-token
- https://www.e-conomic.com/developer/connect
- https://www.e-conomic.com/developer/permissions
- https://www.e-conomic.dk/support/artikler/handtering-af-eksterne-administratorer-revisor-bogholder
- https://restdocs.e-conomic.com/