Peliqan

Query and update Uniconta with AI

Connect Uniconta to Claude, ChatGPT, or any MCP client through Peliqan. Ask questions in plain English, get answers from a SOC 2 Type II warehouse, and post vouchers or update invoices back in Uniconta – no .NET API code, no per-call surcharges, no read-only compromises.

Pulling answers out of Uniconta still takes too many clicks

Uniconta runs your accounting, inventory, projects, and logistics in one place – but every quick question still means logging in, switching tabs, exporting reports, and reconciling numbers in Excel. Finance, controlling, and accountancy teams lose hours on questions Claude could answer in seconds.

No natural language interface

"Show me overdue invoices over 30 days for client X" still means filters, OData queries, exports, and pivot tables

Uniconta API has server-call limits

Default 5,000 server calls per 24 hours per user, expandable up to 75,000 with surcharge - heavy AI workloads compete with your bank sync and Power BI flows

No cross-source joins

Combining Uniconta with CRM, ecommerce platforms, payroll, or banking data means custom .NET integrations and a separate warehouse

No native Uniconta MCP exists

There is no off-the-shelf MCP server for Uniconta today - DIY routes mean writing .NET code against the Uniconta API plus building your own MCP wrapper from scratch

Query invoices, GL accounts, customers, vendors, and inventory in plain English

Write changes back - create invoices, post vouchers, update customers, manage stock

Join with 250+ apps - combine Uniconta with CRM, banking, ecommerce, or any source

SOC 2 Type II certified – enterprise-grade security

Type

Cloud ERP for finance, inventory and projects

Markets

Denmark, Nordics, DACH, Benelux, UK and more

Website

One MCP server. Read, write, and join across 250+ sources.

Peliqan syncs your Uniconta data into a built-in Postgres warehouse, exposes it via MCP for instant AI access, and routes writebacks through Peliqan’s connector layer so your live ERP stays protected from rate limits and unsafe writes.

Full read + write through MCP

Where DIY .NET wrappers stop at read-only or take weeks to build, Peliqan supports full writeback out of the box. Create invoices, post vouchers, update customers, manage inventory - all from Claude, ChatGPT, or n8n. The first managed Uniconta MCP that closes the loop.

Cached warehouse, never the live API

Your AI queries a Postgres warehouse, not Uniconta API directly. No risk of hitting the 5,000 calls/24h ceiling, no slowdowns during month-end VAT close. Sync runs incrementally on your schedule (every 15 minutes by default).

Cross-source queries in one SQL statement

Join Uniconta invoices with HubSpot CRM, Shopify orders, or Nordea bank data in a single query. Federated via Trino, all in Peliqan's shared warehouse.

SQL + RAG on vouchers and attachments

Combine structured SQL queries with semantic search across voucher attachments, invoice PDFs, OIOUBL e-invoices, and contract notes. The only MCP that answers questions about both your numbers and your documents.

Claude + Uniconta MCP
Claude + Uniconta MCP
What's our total outstanding receivables in Uniconta? Break it down by customer and flag anything over 60 days.
✓ Querying uniconta.debtor_invoices...

Total outstanding: DKK 2,184,500 across 47 customers.
5 invoices are over 60 days overdue, totalling DKK 287,300:
  • Aalborg Maskin - DKK 94,200 (71 days)
  • NordPak ApS - DKK 68,400 (66 days)
  • Vesterbro Tech - DKK 52,100 (62 days)...
Create a reminder voucher for Aalborg Maskin and post it to GL account 1500 - debtor follow-up.
✓ Voucher posted to Uniconta via writeback

Key Uniconta data available via MCP

Peliqan syncs Uniconta API entities into structured warehouse tables that your AI can query directly.

Entity What your AI can answer Writeback
DebtorInvoices / LinesRevenue by customer, overdue invoices, aging analysis, payment status
GLAccount / GLTransactionsP&L by department, GL drill-down, journal entries, period close
Debtor / CreditorReceivables and payables, debtor/creditor aging, VAT number lookup
InvItem / InvWarehouseStock levels, reorder points, multi-warehouse mix, slow-moving SKUs
SalesOrders / LinesOrder pipeline, quote-to-cash velocity, product mix, order status
PurchaseOrders / LinesOpen POs, supplier spend, on-time delivery, procurement cycle
Project / ProjectTransactionsProject profitability, hours and materials, budget vs actuals, billing
Voucher / DailyJournalPosted vouchers, draft journals, period transactions, audit trail
VAT / DepartmentsVAT codes, period totals for Skattestyrelsen, department-level reportingRead
Attachments / DocumentsVoucher PDFs, OIOUBL e-invoices, contract attachments – queryable via RAGRead

What hotel teams build with MEWS MCP

Cash collection

Daily debtor briefings

"Pull all overdue Uniconta invoices over 30 days, group by customer, and rank by exposure - draft a follow-up plan I can send to the credit team." Claude queries your Uniconta warehouse and returns a Slack-ready summary in seconds.

Useful for: Controllers, finance managers

Inventory and procurement

Reorder agent

Build an AI agent that runs daily, checks Uniconta stock levels against reorder points across multiple warehouses, drafts purchase orders, and posts them for approval. Peliqan writeback creates the PO directly in Uniconta.

Powered by: n8n + Peliqan MCP

Month-end close

VAT and bookkeeping law compliance

"Summarise VAT totals by period, flag any vouchers missing VAT codes, and give me a checklist before submission to Skattestyrelsen." Joins Uniconta vouchers, GL accounts, and VAT codes in one query.

Useful for: Accountants, auditors

Multi-client accountancy

Practice-wide reporting

For accounting firms running Uniconta across dozens of clients - ask Claude to surface clients with declining margins, payroll-tax exposure, or overdue receivables. One query covers every client portfolio without manual file-switching.

Useful for: Danish and Nordic accounting firms

Always-fresh copy, never the live API

Peliqan keeps a working copy of your Uniconta data in a Postgres warehouse, refreshed on your schedule. AI queries the warehouse for speed and safety. When AI needs to make a change, Peliqan routes the writeback through its connector layer – never letting AI hit the live Uniconta API directly.

AI never hits the Unicota API directly

All queries route through Peliqan's warehouse. Writebacks route through Peliqan's connector. Your live ERP never sees a raw AI request.

No server-call surcharges

Uniconta's per-user API call ceilings don't slow your AI down. The warehouse absorbs query load - even during heavy month-end close or large bank reconciliations.

Always fresh, on your schedule

Incremental syncs run as often as every 5 minutes. You decide the cadence based on how fresh your finance, accounting, or controlling team needs the data.

Full data, every record

Every entity, every voucher, every invoice, every client. Ready for cross-source joins, Text-to-SQL, and RAG on attached documents.

AI Clients
Claude
ChatGPT
AI Agents
MCP Protocol
Protocol Layer
Peliqan MCP Server
Query - Writeback - Cross-source joins
SQL Query
Cache Layer
Peliqan Data Warehouse
Full read-only copy - Always in sync
Postgres
Trino
SQL + RAG
ELT Sync
Source Apps
Unicota
AFAS
Salesforce
250+
Live systems stay safe - AI only queries the read-only cache

How to set up the Unicota MCP server

1

Connect Unicota in Peliqan

Click the Uniconta connector in Peliqan and enter your Uniconta login credentials and APP identifier (CUID). Peliqan handles the .NET API session lifecycle – no NuGet packages, no .NET Framework setup. Setup guide →

2

Select and materialize tables

Choose which Uniconta entities to sync – debtor invoices, GL accounts, vouchers, customers, vendors, inventory items, projects. Peliqan materializes them into Postgres on your schedule (default: every 15 minutes). Stay well within Uniconta’s per-user call ceiling. Materializing tables →

3

Create your MCP API handler

Use Peliqan’s built-in MCP template to expose the Uniconta tables and operations your AI agents need. Set role-based permissions for read, write, or both – column-level masking for sensitive financial fields supported. AI agents docs →

4

Connect Claude or ChatGPT

Run pip install mcp-server-peliqan, add your Peliqan API credentials, and start querying Unicota with natural language. Open source on  GitHub.

Enable MCP for Unicota

Learn how to enable the MCP server for Uniconta in Peliqan. See how to connect AI assistants like Claude to your live Uniconta invoices, vouchers, GL accounts, and inventory data in just a few steps.

 

Peliqan vs other Unicota MCP options

There is no off-the-shelf Uniconta MCP server today – so most teams either build their own .NET wrapper or piece together Power BI plus Excel exports. Here’s how the options compare.

DIY .NET wrapper OData + BI exports Peliqan MCP
Writeback to UnicontaCustom code✗ Read-only✓ Audited writeback
Cached warehouse✗ Live APIManual✓ Postgres + Trino
Cross-source queries✓ 250+ sources
RAG on vouchers and OIOUBL✓ SQL + RAG combined
Setup timeWeeksDays✓ Under 30 minutes
Multi-client handlingManualManual✓ Automatic
EU data residencySelf-hostedVaries✓ EU-hosted
BI + ETL + reverse ETL✗ MCP only✗ Read-only✓ Full data platform

The full Peliqan MEWS integration

MCP is one part of what Peliqan offers for Uniconta. The full integration gives you a complete data platform for finance reporting, accounting automation, and AI-powered analytics.

Connect your favourite BI tool, write data transformations in SQL or Python, and set up data quality checks – all on the same platform.

ELT connector

Full sync into built-in warehouse

MCP server

Claude, ChatGPT, n8n, Make

Text-to-SQL

Plain English financial queries

Reverse ETL

Push data back to Unicota

RAG + Graph RAG

Semantic search on documents

Data quality

SQL checks + Slack/email alerts

Skip the .NET wrapper. Skip the Excel exports. Start writing back from day one.

Connect Uniconta, publish your MCP server, and let Claude (or ChatGPT, or n8n) answer accounting, finance, and inventory questions and update records – in minutes.

No credit card required  ·  SOC 2 Type II certified · 2 weeks custom connector SLA

Uniconta MCP, answered

What is the Uniconta MCP server?

The Uniconta MCP server is a Model Context Protocol endpoint that exposes your Uniconta ERP data to AI agents like Claude, ChatGPT, and Cursor. Peliqan’s Uniconta MCP server lets AI query invoices, GL accounts, vouchers, customers, inventory, and projects in plain English, and write updates back to Uniconta – without writing .NET API code or building your own MCP wrapper.

Authenticate Uniconta in Peliqan with your Uniconta login and APP identifier, pick the entities to sync, and add the Peliqan MCP endpoint to Claude Desktop, ChatGPT, Cursor, or n8n. Most finance teams go from Uniconta authentication to first AI query in under 30 minutes. Full setup steps are in the guide above.

Peliqan supports both read and write. Your AI agent can query Uniconta data and also create invoices, post vouchers, update customer records, manage inventory, and trigger other Uniconta API actions, with full audit logging. Writebacks route through Peliqan’s connector layer for safety – so AI never accidentally posts malformed entries to your live ERP.

No. Peliqan caches your Uniconta data in a built-in Postgres warehouse and AI queries hit the cache, not the live Uniconta API. Your Power BI integration, bank sync, and other workflows never compete with AI for Uniconta API throughput. Sync runs incrementally on your schedule (every 15 minutes by default), well within Uniconta’s per-user call ceilings.

Yes. Peliqan handles multi-client Uniconta automatically – one connection covers all client books in your accountancy practice. Your AI agent can run queries like “compare gross margin across all 30 clients last month” without per-client logins or manual file-switching. Particularly powerful for Danish, Norwegian, and Dutch accounting firms running Uniconta across multiple SME portfolios.

Peliqan is EU-hosted, SOC 2 Type II certified, and GDPR-compliant. Row-level and column-level access control let you mask or exclude sensitive fields (payroll details, bank account numbers, personal IDs) from AI agents while still allowing operational queries. Every AI query and writeback is logged with full audit trail – relevant for compliance with the Danish bookkeeping law and similar Nordic regulations.

A custom .NET wrapper around the Uniconta API can take weeks to build, requires ongoing maintenance, and still hits the live API every call. OData exports work for Power BI dashboards but are read-only and don’t let AI write back to Uniconta. Peliqan is the only managed Uniconta MCP that pairs a cached Postgres + Trino warehouse with audited writebacks, joins Uniconta with 250+ other connectors (CRM, ecommerce, banking, BI), and is EU-hosted with SOC 2 Type II.

No. Peliqan includes a built-in Postgres + Trino warehouse. Your Uniconta data lands there automatically – no Snowflake, BigQuery, or dbt project required. If you already have a warehouse, Peliqan can sync to it as well, so your existing BI dashboards and reporting stay intact.