create_customer
Add a new customer.
LABSCO SUMMARY
create_voucher stating that rows must balance is the tool telling an agent the one rule it cannot violate.
Double-entry is not a validation nicety, it is what makes the ledger a ledger, and an agent composing a journal entry has no reason to know that unless told. Putting the constraint in the description means a malformed entry is caught by the caller rather than by the accountant. Cost centres and projects being exposed is the other sign this was built by someone who does the work — expense allocation is where bookkeeping actually gets tedious, and most integrations omit it entirely. Be clear that send_invoice emails a real customer and create_voucher posts to real books; this is not a reporting layer.
What it is
A Visma eAccounting client covering the accounting cycle in both directions: sales side with customers, quotes, orders, invoices and payments; purchase side with suppliers and their bills; plus journal entries and the ledger structure underneath.
What you get
- Customer invoices listed with OData filter syntax, opened in full, created with line items, sent by email, and their payments listed separately.
- The purchase side kept distinct: incoming supplier invoices listed and recorded, with supplier details available.
- create_voucher states its own constraint — rows must balance, total debit equal to total credit — so a malformed journal entry is refused rather than posted.
- The ledger structure is readable: the chart of accounts, fiscal years, and company settings.
- Projects and cost centres listed for expense allocation, which is where most accounting integrations stop short.
- Sales orders and quotes covered alongside invoices, so the pre-invoice stage exists too.
Requirements
VISMA_ACCESS_TOKEN. This writes to real books — invoices are created and sent, and journal entries posted.
Setup effort
One command plus a key — npx -y visma-eaccounting-mcp-server, then supply credentials
USE CASES
01
Invoicing a customer
Find or create the customer, raise the invoice with its line items, and send it — the send being a real email to a real person.
02
Chasing what has not been paid
Filter invoices with OData syntax and check the payments recorded against them.
03
Recording an expense
Record the supplier invoice against the right supplier, allocating it to a project or cost centre.
04
Posting a manual journal entry
Create the voucher with rows that balance — the tool requires debit to equal credit — against accounts read from the chart.
05
Quoting before invoicing
Raise a quote for the customer and track the sales orders behind it.
20 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
create_invoice
Create a new customer invoice with line items.
create_quote
Create a quote/offer for a customer.
create_supplier_invoice
Record a new supplier invoice (expense/bill).
create_voucher
Create a manual journal entry. Rows must balance (total debit = total credit).
get_company_info
Get company information and settings.
get_customer
Get full details of a specific customer.
get_invoice
Get full details of a specific customer invoice.
get_supplier
Get details of a specific supplier/vendor.
list_accounts
Get the chart of accounts.
list_cost_centers
List cost centers for expense allocation.
list_customers
Search and filter customers.
list_fiscal_years
Get information about fiscal/accounting years.
list_invoice_payments
List customer invoice payments.
list_invoices
List and filter customer invoices. Uses OData $filter syntax.
list_orders
List and filter sales orders.
list_projects
List all projects.
list_supplier_invoices
List incoming supplier invoices (bills/expenses).
list_vouchers
List journal entries/vouchers.
send_invoice
Send a customer invoice via email.
BEFORE YOU INSTALL
What to know first
Tools you get
20 tools when we connected.
Requires
- npx on PATH
- VISMA_ACCESS_TOKEN in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 20 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y visma-eaccounting-mcp-serverMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"visma": {
"command": "npx",
"args": [
"-y",
"visma-eaccounting-mcp-server"
],
"env": {
"VISMA_ACCESS_TOKEN": "<YOUR_VISMA_ACCESS_TOKEN>"
}
}
}
}
