Norman Finance — AI Bookkeeping, Accounting & Taxes

Capabilities · Connect · Germany · Poland · Documentation

Connect Norman Finance to your AI assistant to create invoices, organize receipts, reconcile transactions, keep your books up to date and prepare tax returns. Work from the same company records you use in the Norman app.

Use the remote MCP connection with Claude, ChatGPT, Gemini, Grok, Perplexity, Cursor and other compatible clients. Client setup instructions distinguish directory installs, extensions and custom connections.

See Norman in action

https://github.com/user-attachments/assets/10718781-34f2-4640-9253-be4c82de6159

Watch the full Norman demo · Explore workflow examples · Watch the Poland introduction

What you can do

Calculator and form workflows cover public estimates and Polish PDF/DOCX preparation, with deployment prerequisites.

Try asking

• "Create a draft invoice for consulting and use my saved company branding."
• "Which transactions are missing a receipt?"
• "What did we spend on software this quarter?"
• "Review my books and tell me what still needs attention before year-end."
• "Prepare my German VAT return preview. Do not submit it yet."
• "Show my Polish company's JPK register and explain excluded operations."

Get started

1. Create a Norman account, or use your existing one.
2. Add Norman in your AI client's directory or as a remote HTTP MCP server: https://mcp.norman.finance/mcp.
3. Complete Norman OAuth, then confirm the company you want to work with.

For clients that accept an MCP configuration file:

{  "mcpServers": {    "norman-finance": {      "url": "https://mcp.norman.finance/mcp"    }  }}

Using Claude Code?

/plugin marketplace add norman-finance/norman-mcp-server/plugin install norman-finance@norman-finance

All setup guides: Claude Connectors, Claude Code, ChatGPT, Gemini, Grok, Perplexity, Cursor, Replit, OpenClaw, n8n and other MCP clients.

Your company is the accounting context, not the language of the conversation. Use list_companies and switch_company to change it; company://current identifies its country, currency, legal form and chart of accounts.

Market-specific capabilities

One connection supports both Germany and Poland. The workflows differ by jurisdiction:

Germany: accounting, VAT and year-end

Keep day-to-day bookkeeping and full GmbH/UG accounting connected to the same AI workflow. Review SKR03/SKR04 accounts, reconcile transactions, calculate VAT and prepare supported VAT and annual tax returns.

For year-end, create a Draft annual-close workspace, review the workbook and post closing adjustments. Preparing that workspace does not lock the year or submit a return. Tax submission is a separate, explicitly confirmed action.

German invoice workflows also support ZUGFeRD, cancellations (Stornorechnung), corrections (Rechnungskorrektur) and delivery notes (Lieferschein).

Additional workflows include German GmbH/UG payroll and company-formation preparation. Payroll tools cover calculation, approval, payslips and supported Lohnsteuer-Anmeldung filing; sensitive employee identifiers stay in the app. Formation tools prepare draft documents and a notary handoff, not a legal incorporation by chat. Detailed workflows.

DATEV MCP support: EXTF, SKR03 and SKR04

Prepare a DATEV EXTF Buchungsstapel with SKR03 or SKR04 for your tax advisor (Steuerberater), with linked documents when requested. The complete GmbH/UG Ledger export includes opening balances, manual entries, payroll, depreciation and closing postings.

• trigger_datev_export: prepare the export and download package.
• validate_ledger_datev_export: check structure, source coverage and documents before handoff.
• get_datev_changes_since_handoff: list the bookings added, changed or left out since the advisor's last file of each period.
• read_datev_file: inspect an EXTF/DTVF file without importing postings into your books.

Try: "Check the full GmbH Ledger export before I give it to my accountant."

DATEV details and API requirements. Validation is a handoff check, not certification of tax correctness or DATEV import acceptance.

Poland: KPiR, full books and JPK

Cześć, Polsko

https://github.com/user-attachments/assets/aea417ad-64aa-4623-896f-ff8dc4559d4a

Watch the Poland film · 24 seconds · English on-screen text with Polish subtitles built into the video.

This is a product introduction, not a recording of MCP tool calls. The Polish landing page and English landing page introduce the connection in each language.

What the Polish tools cover

• JDG / KPiR: review monthly or annual tax books and explain why an operation is included or excluded.
• Sp. z o.o. / full books: inspect the journal, chart of accounts, account sheets and trial balance; review prepared financial statements and their notes.
• VAT / JPK_V7: compare sales, purchases, totals and exclusions with source operations.
• Tax estimates and status: review PIT/ZUS or CIT estimates, existing JPK/PIT filing status and UPO availability.
• Invoices, receipts and assets: use shared tools with Polish VAT codes, document currencies and depreciation inputs; create proforma quotes and record incoming bills in their original currency. Search receipts by supplier and date.
• Ryczałt settings: propose a revenue category's rate for the owner to review and apply in Norman. The assistant does not change tax settings directly.
• Import review and routines: inspect CSV import batches, preview an exact batch rollback, and confirm or dismiss detected routines. A rollback requires the user's approval and the preview token; confirming a routine does not send invoices.
• Accountant handoff: preview General, Optima or EPP compatibility and review blockers.

Try asking:

• "Pokaż KPiR mojej JDG za wrzesień i wyjaśnij pominięte koszty."
• "Pokaż zestawienie obrotów i sald mojej spółki za trzeci kwartał."
• "Sprawdź rejestr JPK_V7: sprzedaż, zakupy i pominięte operacje."
• "Sprawdź status wysyłki JPK i dostępność UPO. Niczego nie wysyłaj."

The Polish MCP tools do not sign or submit returns to MF/KRS, create manual Polish journal postings, or generate or close annual statements. They inspect existing filing state; an XML download is not an acceptance receipt or UPO.

Polish tool guide, arguments and examples · Start with a Polish company

Interactive UI inside your AI assistant

MCP Apps-compatible hosts can show focused accounting workspaces inside the conversation:

Clients without MCP Apps support receive structured or text results. Polish accounting uses the dedicated structured tools; the German workspaces do not imply equivalent Polish filing functionality.

Skills

Ready-to-use skills compatible with Claude Code, OpenClaw, and the Agent Skills standard.

Browse the skills directory. Each skill guides an accounting task while the Norman API enforces access and action permissions.

Control and privacy

• You choose the company. Company-scoped records stay in the selected accounting context.
• Review before binding actions. Tax filing, payments, external messages and automation approvals require their own decision.
• Keep sensitive identifiers in Norman. Complete restricted identity and payment setup in the app, not in chat.
• Check the result. A draft, preview, queued request or downloaded XML is not proof of filing or payment success.

Polish KPiR and estimate reads can synchronize derived records and therefore declare readOnlyHint=false. Country and book-type guards prevent German procedures from being applied to Polish books. Technical rollout and tool-specific limits are documented in the linked guides.

Documentation

This repository holds the documentation, skills and client manifests of the hosted Norman MCP server. Issues and skill suggestions are welcome; see Contributing and Security.

Website · Report an issue or suggest a feature · MIT license

[mcpbeat] [Norman Finance MCP server]