- MCP Server
- Visma E-conomic
Query Visma E-conomic with AI and write back
to your books
Connect Visma E-conomic to Claude, ChatGPT, or any MCP client through Peliqan. Ask questions across your Danish and Norwegian books in plain English, join e-conomic with HubSpot or any Visma sibling (Yuki, Silverfin, Teamleader), and post audited journal entries back to your books with Bogforingsloven and SAF-T aware guardrails.
Most e-conomic MCPs are SQL-only or single-app.
There are a few Visma E-conomic MCP options today: iPaaS wrappers, community GitHub repos, generic adapter platforms. They handle a few READ endpoints and a handful of writes against e-conomic alone. But Visma owns 100+ accounting, HR, and payroll brands across the EU, and your accountancy firm rarely lives in just one of them. The moment you need to read across Visma E-conomic and Yuki and Silverfin and Teamleader, single-app MCPs run out of road.
Single-source MCPs miss the Visma quadrant
A Nordic accountancy firm running clients across e-conomic (DK), Yuki (NL), Silverfin (BE), and Teamleader (BE) needs four MCP servers, four auth flows, and four governance layers. AI cannot answer "show me clients across all books with overdue VAT" in one prompt.
Raw e-conomic credentials end up in AI client configs
DIY Visma E-conomic MCP setups usually paste OAuth refresh tokens or app secret tokens directly into Claude Desktop, Cursor, or n8n environment files. Real credentials, real audit headaches, real Bogforingsloven exposure if those tokens leak.
Action-based MCPs charge per task
Zapier, Pipedream (now Workday-owned since the November 2025 announcement), and viaSocket price per task or per action. At AI scale across many client books and many agents, those bills grow fast and quotas slow your accountants down at month-end.
- What you get
Query invoices, vouchers, accounts, customers, and VAT in plain English
Audited writeback to e-conomic with Bogforingsloven and SAF-T aware guardrails
Join Visma E-conomic with HubSpot, Yuki, Silverfin, Teamleader, and 300+ apps in one query
SOC 2 Type II, ISO 27001, GDPR-native, HIPAA, CCPA - all certified
Type
Danish cloud accounting platform (Visma Group)
Auth
REST API, App Secret + Agreement Grant tokens
Website
- The solution
One MCP server. Visma E-conomic plus the whole Visma ecosystem, with audited writebacks.
Peliqan connects to your Visma E-conomic account via the standard two-token model (App Secret Token + Agreement Grant Token), exposes it through MCP alongside 300+ other sources, and routes every read and write through a governance layer with column masking, role-based access, and full audit logging.
Cross-source joins federated via Trino
e-conomic-only MCPs need every other source ELT-ed into e-conomic before joining. Peliqan lets AI join e-conomic with HubSpot, Klarna, Stripe, or any of 300+ sources directly. One SQL statement, federated by Trino, no ELT required for one-off questions.
Audited writeback to Visma E-conomic
Post invoices, create vouchers, update customers, register payments through e-conomic's REST API. Every write is logged with user, agent, timestamp, and the exact API payload. Bogforingsloven (Danish bookkeeping act) and Norwegian SAF-T workflows get a clean trail your auditor will accept.
The whole Visma ecosystem in one MCP
Peliqan ships MCP servers for four Visma-owned platforms: Yuki (NL), Silverfin (BE and global), Teamleader (BE / NL), and Visma E-conomic (DK / NO). Run AI across the full Visma ecosystem in one MCP endpoint, not four. One auth flow, one governance layer, one set of audit logs.
Found 62 customers with overdue invoices totalling DKK 3,840,000. 14 accounts have a silent CS owner this month.
- Aarhus Bygg ApS - DKK 412,000 (45 days)
- Copenhagen Tek A/S - DKK 287,000 (38 days)
- Odense Logistik ApS - DKK 218,000 (62 days)
- Data access
What AI can do with your Visma E-conomic data
Peliqan exposes Visma E-conomic accounts, invoices, vouchers, customers, and VAT data through MCP, with granular controls on what AI can read, where it can write, and how it federates with other sources.
| Capability | What your AI can do | Writeback |
|---|---|---|
| Schema introspection | List e-conomic entities, fields, account groups, and chart of accounts structure | Read |
| Invoices and accounts receivable | Outstanding invoices, aging, customer payment patterns, AR drill-down by period | ✓ Opt-in |
| Vouchers and journals | Search vouchers, post Bogforingsloven-compliant journal entries, year-end close prep | ✓ Opt-in |
| Customers and suppliers | Lookup, segment, update contact and payment terms, sync to and from CRM | ✓ Opt-in |
| VAT and tax reporting | VAT period totals, momsangivelse prep, Norwegian SAF-T extraction, Skattestyrelsen reconciliation | ✓ Opt-in |
| Cross-source joins | Join e-conomic with Yuki, Silverfin, Teamleader, HubSpot, Klarna, 300+ more | Read |
| Column masking | Hide CPR numbers, bank account numbers, salaries from AI per role | Policy |
| Multi-tenant access | Scope AI to specific e-conomic client accounts in a partner setup | Policy |
| Audit logging | Every query and writeback logged with user, agent, timestamp, payload | Always on |
| SQL + RAG combined | Mix structured e-conomic SQL with semantic search across PDFs, contracts, receipts | Read |
- How it works
One MCP. Visma E-conomic plus your Nordic stack.
Peliqan connects to e-conomic via the standard App Secret + Agreement Grant token model, exposes it through MCP alongside 300+ other sources, and federates cross-source queries through Trino. Writebacks route to the right system (e-conomic itself or your CRM, billing, or Visma sibling) through Peliqan’s connector layer.
Server-side token storage
Peliqan stores your Visma E-conomic App Secret Token and per-customer Agreement Grant Tokens server-side. AI clients never see raw e-conomic credentials. Rotate or revoke a Peliqan API token without touching e-conomic.
Visma sibling federation
Connect Visma E-conomic alongside Yuki, Silverfin, and Teamleader in the same Peliqan workspace. Trino federates cross-tool joins so an AI prompt like "show overdue invoices across all Visma tools" actually works.
Smart writeback routing
When AI says "post an e-conomic voucher and notify the controller in Slack," Peliqan reads from e-conomic, writes the voucher through the e-conomic API, and sends the Slack message. One prompt, three systems, one audit trail.
EU-hosted
Peliqan is EU-hosted with SOC 2 Type II, ISO 27001, and GDPR compliance. Audit policies and column masking can mirror Danish bookkeeping act requirements and Norwegian SAF-T expectations, relevant for accountancy firms with reviewer responsibilities.
- Setup
Connect Visma E-conomic to Claude in under 30 minutes
No DIY MCP server to host, no stored procedures, no extra ELT vendor. Activate the integration on the e-conomic account, authorise in Peliqan, and your MCP server is live.
1
Generate your Agreement Grant Token
An e-conomic user (or administrator) opens the Peliqan app Installation URL, signs in, and grants Peliqan access to the accounting agreement. e-conomic returns an Agreement Grant Token. For administrator agreements, click “Administer” on the specific accounting agreement first, then follow the Installation URL.
2
Add Visma E-conomic in Peliqan
In Peliqan, go to Connections, add Visma E-conomic, and paste the Agreement Grant Token from step 1. Peliqan combines it with the App Secret Token (stored server-side, never exposed) on every API call. Tokens never land in Claude Desktop, Cursor, or any AI client config.
3
Create your MCP API handler
Use Peliqan’s built-in MCP template to choose which e-conomic entities your AI agents can read and write. Apply column masking for CPR numbers or salary data. Set per-agent role-based access for partner setups managing many client accounts. AI agents docs →
4
Connect Claude or ChatGPT
Run pip install mcp-server-peliqan, add your Peliqan API credentials (not your e-conomic tokens), and start querying Visma E-conomic with natural language. Open source on GitHub.
Peliqan vs other Visma E-conomic MCP options
Visma E-conomic MCP options come in three flavours: task-priced iPaaS wrappers, community open-source repos, and generic adapter platforms. Here is where Peliqan fits for Danish and Norwegian accountants and Nordic accountancy firms that need more than basic SELECT plus a few writes.
| Zapier e-conomic MCP | Pipedream MCP (Workday) | Community GitHub MCPs | viaSocket | Peliqan MCP | |
|---|---|---|---|---|---|
| Read e-conomic data | ✓ | ✓ | ✓ | ✓ | ✓ |
| Audited writeback to e-conomic | Limited, task-capped | Action-based | Community / DIY | Action-based | ✓ Full audit trail |
| Cross-source SQL joins | ✗ | ✗ | ✗ | ✗ | ✓ 300+ sources |
| Visma quadrant in one MCP | ✗ | ✗ | ✗ | ✗ | ✓ Yuki, Silverfin, Teamleader |
| Task / call quotas | Per-task pricing | Per-action pricing | Self-hosted limits | Per-operation pricing | Flat plan |
| Governance for AI | Workflow-level | Workflow-level | ✗ | Workflow-level | ✓ Per-agent policy |
| EU hosting | ✗ US | ✗ US | Self-hosted | Varies | ✓ EU-hosted |
| SOC 2 + ISO 27001 + GDPR | SOC 2 | SOC 2 | ✗ | Varies | ✓ All three |
| BI + ELT + reverse ETL bundled | ✗ MCP only | ✗ MCP only | ✗ MCP only | ✗ MCP only | ✓ Full data platform |
- Beyond MCP
The full Peliqan Visma E-conomic integration
MCP is one way to use your Visma E-conomic in Peliqan. The full integration gives you a complete data platform for AI agents, ELT into your warehouse, BI on e-conomic plus other sources, and reverse ETL back into e-conomic. All in one workspace.
Connect your favourite BI tool, write data transformations in SQL or Python, and set up data quality checks on your Postgres tables.
ELT to your warehouse
e-conomic data into Postgres, Snowflake, BigQuery
MCP server
Claude, ChatGPT, n8n, Make
Text-to-SQL
Plain English e-conomic queries
Reverse ETL
Push data back into e-conomic
Visma quadrant federation
e-conomic + Yuki + Silverfin + Teamleader
Data quality
SQL checks + Slack alerts on e-conomic data
Your AI agents. 300+ business apps. One MCP server.
Connect Visma E-conomic, Exact Online, AFAS, Salesforce, and more to any MCP client – without writing API code, managing rate limits, or sacrificing governance.
Live in minutes - pip install, paste your token, query.
Read + write - pull data and push updates back to source.
Governed by default - SOC 2 Type II · GDPR · EU-hosted.
Visma E-conomic MCP, answered
What is the Visma E-conomic MCP server?
A Visma E-conomic MCP server is a Model Context Protocol endpoint that lets AI agents like Claude, ChatGPT, and Cursor query a Visma E-conomic account in plain English and post audited writebacks. Peliqan’s e-conomic MCP server adds cross-source joins (e-conomic plus 300+ apps), writeback routing to business apps like HubSpot or Slack, column masking for CPR numbers and salary data, and a single MCP endpoint that covers e-conomic alongside its Visma siblings Yuki, Silverfin, and Teamleader for Nordic accountancy practices.
What is the Visma quadrant and why does it matter?
Visma (HQ Oslo) is one of Europe’s largest accounting and HR software groups, with 100+ brands under its umbrella. Four of those brands matter most for Nordic and Benelux accountancy firms: Visma E-conomic (Denmark, Norway accounting), Yuki (Netherlands bookkeeping), Silverfin (Belgium and global compliance), and Teamleader (Belgium and Netherlands CRM and invoicing). Visma acquired e-conomic in 2015, Silverfin in 2023, and the others over recent years. Peliqan ships MCP servers for all four, so a single MCP endpoint covers the full Visma quadrant. AI can ask “which clients across the practice are behind on VAT” once, instead of running four separate queries.
How does Peliqan authenticate to Visma E-conomic?
Peliqan uses Visma E-conomic’s standard two-token authentication. Peliqan holds an App Secret Token server-side (identifying the Peliqan integration), and each customer grants Peliqan an Agreement Grant Token by completing the e-conomic Installation URL flow. Both tokens are sent on every API call as X-AppSecretToken and X-AgreementGrantToken headers. Tokens stay server-side in Peliqan. Your AI clients never see e-conomic credentials directly.
Can AI write to my e-conomic books?
Only if you allow it. Peliqan defaults to read-only access. You can enable invoice creation, voucher posting, customer updates, and other writebacks per role. Every write is logged with the user, agent, timestamp, and exact API payload. You can also restrict AI to specific voucher series or accounts, so it can post draft journal entries that an accountant reviews before final commit. The audit trail is built for Danish Bogforingsloven and Norwegian SAF-T expectations.
Does this work for accountancy firms running many e-conomic client books?
Yes. A Danish or Norwegian accountancy firm running 200+ e-conomic client books can connect each via the App Secret + Agreement Grant token model into one Peliqan workspace, expose them through a single MCP server, and scope each AI agent to specific clients. Cross-client analytics (which clients are behind on momsangivelse, which need year-end attention, which have unusual voucher activity) become natural-language queries instead of spreadsheet pulls. Pair with Yuki, Silverfin, or Teamleader for cross-border Nordic and Benelux practices.
How is Peliqan different from Zapier or Pipedream e-conomic MCPs?
Zapier and Pipedream (now Workday-owned, with the acquisition expected to close at the end of January 2026) are excellent for simple action-style flows like “when an e-conomic invoice is created, send a Slack message.” They are task-priced or action-priced, which gets expensive at AI scale, and they cannot join e-conomic with other sources in one SQL query. Peliqan is built around a federated query layer (Trino) plus an MCP server, so the same workspace covers cross-source joins, audited writebacks across many systems, ELT into your warehouse, BI on top, and reverse ETL back out. If your use case is a single Zap, use Zapier. If you are building AI agents that need to read across systems and act safely, Peliqan adds the missing layer.
What does Peliqan cost for a Visma E-conomic setup?
Peliqan pricing is flat-rate, not task-priced. Connect starts at 75 EUR per month for small teams. Pro is 500 EUR per month with full MCP, governance, and cross-source features. Enterprise is custom for larger firms with multi-tenant needs. Whitelabel starts at 1,500 EUR per month if you want to offer a branded MCP to your own customers. Custom e-conomic-side adjustments or extra source connectors are covered by Peliqan’s 2-week custom connector SLA. See pricing for the full breakdown.