Case Study
Building a Hosted Fortnox MCP and Finance Operations Platform
Nordsynk connects Fortnox to Claude, ChatGPT, Cursor, and other MCP clients through a secure hosted gateway. We built the product around a clear promise: work faster with live finance data, keep humans in control, and show the evidence behind every recommendation.

Overview
Nordsynk started from a precise product question: what would it take to let Swedish finance teams work with live Fortnox data from the AI tools they already use, without asking them to self-host infrastructure, manage API credentials, or trust an unrestricted agent with accounting writes?
The answer became a hosted MCP platform for Fortnox. The public surface is intentionally compact: connect your company, ask for the finance work you need, review the evidence, and approve sensitive changes before anything is written. Behind that simple experience is a product system for consent, access control, usage visibility, onboarding, support, and bureau-specific multi-company workflows.
The Challenge
Fortnox is not a toy integration. Customers expect access to invoices, customers, suppliers, vouchers, orders, payments, and workflow state. Accounting bureaus need to move across many connected client companies, and finance teams need confidence that an AI assistant understands the context before it suggests action. On top of that, any write must be treated as a real accounting operation, not just another API mutation.
The product also needed to work across modern MCP clients. Claude, ChatGPT, Cursor, and desktop clients all have slightly different UX constraints around authentication, tool discovery, and interactive approval. Nordsynk had to make the core Fortnox experience consistent across those clients while staying strict about tenant boundaries and write intent.
What we built
The platform runs as a hosted remote MCP service, so customers do not need to self-host a server or manage Fortnox credentials. OAuth consent anchors the connection, and every action is evaluated against the company, user, and workflow context before the assistant gets access to the relevant finance surface.
We designed the assistant interface to feel broad without feeling chaotic. It can handle common Fortnox workflows, answer finance questions with source context, and prepare next actions, while the product keeps sensitive operations behind explicit review.
Safety model
The key design decision was to separate discovery, read operations, suggested actions, and writes. Reads can happen through the authenticated Fortnox runtime. Suggested actions can be presented by the assistant. But mutating Fortnox requests must carry explicit write intent and pass through an approval flow that is locked to the exact request being executed.
The approval experience is designed for non-technical users: explain the accounting change, show enough context to verify it, and only proceed when the human confirms the exact action. This gives the product its edge without turning every session into a risk negotiation.
Product layers
The customer-facing web app handles setup, Fortnox consent, activation, support, and dashboard surfaces. The operational side gives the team the visibility needed to support a finance product in production without exposing customers to internal complexity.
For accounting bureaus, we built a dedicated Byra edition. A bureau can connect many client companies, invite consultants, grant client access, track connection health, and manage the operational reality of serving multiple Fortnox customers from one workspace.
Finance Control Preview
Nordsynk also includes a read-only finance-control preview. The daily playbook checks payment changes, overdue invoice reminders, delivery readiness, cost movement anomalies, and open accounting questions. It never writes to Fortnox; it turns review work into a structured queue of findings, decisions, and feedback.
Each finding carries evidence pointers back to the Fortnox or Nordsynk object that supports it. This matters for trust: the AI layer is not asking finance teams to accept unsupported summaries. It shows which source record or remembered decision explains the recommendation.
Nordsynk was designed around a simple trust boundary: read approved records, show the evidence, remember human decisions, and require an explicit approval before changing Fortnox.
Engineering outcomes
The result is a production-grade AI finance platform rather than a thin API demo. Nordsynk pairs broad Fortnox coverage with a trust model that finance teams can understand: connect securely, inspect the evidence, approve writes intentionally, and give bureaus a practical way to manage many client companies from one place.