Does KraftHub replace our Business Central?

No. Finance, purchasing, stock and people stay in Business Central. KraftHub takes the work in front of it — enquiry, quote, appointment, site — and hands the documents back in the formats your finance department accepts.

Which versions are covered?

Business Central online and on-premises installations; older NAV releases we look at case by case. The split is the same in every case; the integration route differs.

How does the data get there and back?

Through the three routes above: documents in XRechnung, ZUGFeRD, DATEV and CSV from day one; master data and transactions over the documented APIs; queries from your agents over MCP. The last two we build to fit your business.

Is there an off-the-shelf connector?

No, and we would not trust one. What has to be connected depends on your modules, your customising and which transactions you actually want to send back. We agree the scope with you and your IT and build it with our own engineering team. Route 1 — the document handover — runs from day one regardless.

Do our DLP policies apply?

Yes. Access to MCP servers in Copilot Studio runs through Power Platform connectors per Microsoft's documentation — a policy that governs connectors governs the agent's access to this tool as well.

Who builds the integration?

We do, together with your IT or your implementation partner. Responsibilities are agreed in writing beforehand.

The package price as published. The effort for the integration is quoted by scope before anything is commissioned.

Where is the data held?

In German data centres, under GDPR, with a data processing agreement and tenant separation.

krafthub.aiFor enterprises

Back to main site Book intro call

Integration

KraftHub and Dynamics 365.

Business Central stays the system of record. KraftHub is the layer in front of it — and becomes a tool for your Copilot agent.

Book a first call See the split

KraftHub

Customer enquiry from emailQuote with AI from textAppointmentSite

Belege · Stammdaten · MCP

Microsoft Dynamics 365 Business Central

Financial accountingPurchasingStockSales

The starting point

The problem Business Central does not solve

Business Central brings finance, purchasing, stock and sales together, and since the 2026 Wave 1 release it ships its own agents: a sales order agent, a payables agent, an expense agent. They read incoming documents and prepare postings for approval.

Which makes it worth asking where those documents come from. The enquiry at 6:40, the quote from a photo, the site report — they start in the working day of a trade business that nobody captures in a structured way. What starts badly there, no agent in the ERP can rescue.

Where this work runs today

OutlookEnquiries and confirmations
ExcelCosting per branch
PaperReports in the van
WhatsAppArrangements with the fitter

not documentednot reportabledepends on individual people

The split

Who stays responsible for what

No judgement, just the allocation. On the left what stays in Business Central. On the right what runs beside the system today and gets a surface in KraftHub.

Business Central stays responsible for

Financial accounting, close, reporting
Purchasing, creditors, framework agreements
Stock, items, dispatch
Sales, debtors, dunning
Cost centres and dimensions
Compliance and audit

KraftHub takes over

Customer enquiry from email, phone and web form
Quote with AI from text, voice, photo, plan and PDF
Appointment, scheduling, customer confirmation
Site: hours, photos, daily and variation reports, signature
Project file with an AI answer and its source
Create e-invoices, capture and file incoming documents

KraftHub does not replace Business Central. It hands it the transactions that today start in Outlook and on paper — structured, and with a history.

Integration

How the two systems come together

Three routes, from least effort to most. Route 1 needs no project on the Microsoft side.

01from day one

Documents back to finance

Outgoing invoices, debtors and documents leave KraftHub in the formats your finance department already accepts. After the export KraftHub locks the invoice against later changes.

XRechnungZUGFeRDDATEVCSV · Excel

02in the project with your IT

Master data and transactions over the Business Central APIs

Customers, suppliers, items and orders over the standard Business Central APIs, or through the Business Central Connector for the Power Platform. Which objects move in which direction is settled with your IT — nothing here is prebuilt, and that is deliberate.

OData v4Standard APIsBusiness Central Connector

03in the project with your IT

KraftHub as a tool in your Copilot agent

Copilot Studio accepts third-party MCP servers. Your agent then holds the Business Central MCP server and the KraftHub MCP server side by side — and answers questions where half the answer sits in the ERP and half in the working day.

MCPCopilot StudioPower Platform

Model Context Protocol

KraftHub as a tool for your Copilot agent

Microsoft documents two tools an agent can use to work directly with Business Central: the Business Central Connector for the Power Platform and the Business Central MCP Server. By default the agent only reads; write access is granted per API page.

And Copilot Studio accepts third-party MCP servers — per Microsoft's documentation, through the MCP onboarding wizard or a custom connector in Power Apps, with an API key or OAuth 2.0. Because access runs through Power Platform connectors, your existing DLP policies apply.

In practice: one agent, two tools. It asks Business Central for a customer's credit limit and KraftHub which fitter is free on Thursday — in the same answer. We set the connection up with your IT.

Copilot Studio · one agent, two tools

“Which fitter is free in Kassel on Thursday?”

Business Central interfaces

Credit limit, order, stock

KraftHub MCP server

Fitter, quote, report

What the assistant may do

Access chosen per connection
revocable at any time
every access is logged
change or delete: no

Four reasons your audit will back

No second ERP

You introduce no parallel world for the numbers. The data your audit checks stays one set.

The agents get clean input

A sales order agent is only as good as the documents reaching it. KraftHub is where those documents come into being, structured.

AI without an ERP project

Quoting, inbox, project questions and site documentation run with AI from day one — independent of your ERP's release cycle.

Your policies still apply

Access runs through Power Platform connectors. Whatever your DLP policies say about connectors, they say about this tool too.

What your IT and data protection need to sign off

The documents exist already — no special round, no asking sales.

German data centresGDPRRoles and permissionsTenant separationEncryption in transit and at restTwo-factor sign-inRegular restore testsData processing agreementAligned with the EU AI Act

From first call to rollout

01
First call — management, IT, or both
02
Agree the scope and direction of the interface
03
Test tenant with your master data
04
Pilot with one team
05
Rollout

What businesses running Business Central ask first

Sources: Microsoft Learn on Copilot Studio (connecting an existing MCP server, transport and authentication, data policies) and on Business Central (Business Central MCP Server, Business Central Connector for the Power Platform, built-in agents in the 2026 Wave 1 release). Vendor statements are quoted, not assessed.

A conversation, not a pitch.

45 minutes, with or without your IT. For management we work out what changes day to day and what a move actually involves; for IT, which of the three routes fit your business and what runs without a project on the Microsoft side. Come alone or bring whoever you need.

Book a first call SAP