Business Central Integrations
Business Central
integrations
that keep running
after the next update.
We connect Business Central to your shop, your trading partners, DATEV, shipping and CRM. Your systems stay. The manual copying disappears.
- Update-safe extensions
- APIs and events
- Cloud / on-premises
Starting point
Today, people work
between your systems.
Orders are retyped from the shop. Delivery notes arrive by email. Accounting exports to DATEV every month. Each of these handovers costs time and creates errors. Time for automation.
Duplicate entry
The same record is maintained in two or three systems.
Silent errors
A transfer fails. Nobody notices until a customer calls.
Blocked updates
Old customisations keep Business Central from staying current.
Knowledge in one head
Only one person knows how the integration works.
Excel as glue
Spreadsheets connect what systems don't.
No transparency
Nobody can see which data flows where and when.
Interfaces
We connect Business Central
to what you already use.
Every integration follows the same standards. Only the systems differ.
Shop integration
Shopware | Shopify | WooCommerce | Amazon
Items, prices and stock flow into the shop. Orders come back to Business Central as sales orders. Every minute instead of the next morning.
EDI with trading partners
EDIFACT | XML | Partner formats
Exchange orders, delivery notes and invoices electronically with your customers and suppliers. In the format your trading partner requires.
DATEV integration
DATEV | Tax advisors
Hand over postings and documents cleanly to your tax advisor. If a standard solution is enough, we recommend it. We only build what is missing.
Shipping integration
DHL | DPD | UPS | GLS
Create shipping labels straight from the order. Tracking number and status flow back automatically.
CRM integration
HubSpot | Salesforce | Dynamics 365 Sales
Your sales team sees orders, revenue and open items right at the customer. Without their own ERP access.
Power BI and Microsoft Fabric
Power BI | Fabric | Data Lake
Incoming orders, margin, liquidity and delivery capability in one dashboard. From Business Central and other sources.
Documents and e-invoicing
DMS | XRechnung | ZUGFeRD
Pass documents to your document management system. Receive, check and create e-invoices.
API connections and legacy systems
REST | OData | File import
An industry solution, production software or a system without a standard connector. We find the most stable route to Business Central.
How we work
Six rules for
every integration.
An integration is only finished when it runs reliably in operation. We align every decision with that.
Standard before customising
If a suitable standard connector exists, we use it. We only develop what the standard cannot do.
Built to survive updates
We develop as an extension in AL and connect via APIs and events. No changes to the standard code. Microsoft updates go through.
Error handling built in
Every transfer is logged. If it fails, it is retried or reported. No record gets lost silently.
Monitoring with alerts
You see which data flowed where and when. If something breaks, the responsible person knows before the business team asks.
Documented for people
Technical documentation for your IT. A clear description for the business team. No knowledge locked in one head.
Secure from the start
Sign-in via Entra ID, minimal permissions, credentials in Azure Key Vault. Data processing exclusively in EU data centres on request.
Process
Four steps to a
running integration.
01System audit
Duration: 2 days
We map your systems and data flows. You get an overview, a prioritisation and a reliable effort estimate.
- 02
Architecture
Duration: 1–2 weeks
We define which data flows in which direction, how often and with which error handling. In writing, before a single line of code is written.
- 03
Build and test
Duration: depends on scope
Development in a sandbox, automated tests, acceptance with your business team. Only then does the integration go live.
- 04
Operation
Duration: ongoing
We monitor, maintain and adapt when your systems change. With a fixed service contract on request.
Result
We measure before.
And after.
Before the project starts, we record three values with you. After go-live, we measure them again. That makes the benefit traceable, not just claimed.
- 01
Manual effort
Minutes per order, delivery or posting.
- 02
Error rate
Corrections, follow-up questions and duplicate entries.
- 03
Lead time
From the customer's order to the finished order in the system.
For IT managers
Technology that doesn't add to your IT's workload.
- Platform
- Business Central Online. On-premises after checking the version.
- Development
- AL extensions following Microsoft AppSource guidelines.
- Connectivity
- Business Central APIs (REST, OData), webhooks and events.
- Integration
- Azure Logic Apps, Azure Functions and Service Bus where it makes sense.
- Operation
- Azure Monitor and Application Insights with alerting.
- Security
- Entra ID, OAuth 2.0, Azure Key Vault, role-based permissions.
- Quality
- Code review, automated tests, versioning, CI/CD.
- Handover
- Training, documentation, knowledge transfer
Getting started
Start with
the system audit.
2 days. Fixed price. A clear result. If you then commission the implementation, we credit the full price.
€2,999 net
Request a system auditAudit results
- 01Map of your systems and data flows
- 02List of all manual handovers with estimated time spent
- 03Prioritised order of the integrations
- 04Architecture proposal and effort estimate
Questions
Frequently asked questions about
Business Central integrations
What does a Business Central integration cost?
That depends on the systems, the data volume and the direction of the data flows. After the system audit, you get a fixed price or a fixed budget. No surprises during the project.
How long does implementation take?
The system audit takes two days, the architecture one to two weeks. A single integration, for example to DATEV or a shipping provider, is often running after a few days. EDI or several systems with complex data flows may take longer. After the audit, you know the schedule.
Does an integration block later Business Central updates?
No. We develop as an extension in AL and connect via APIs and events. The standard code stays untouched, Microsoft updates go through. In operation, we test new versions in a sandbox first.
Standard connector or custom development?
Standard first. If a suitable connector exists, we recommend it, even if it means less development for us. We only build custom what the standard cannot do. Often it's a combination: a standard connector plus a lean extension for your special cases.
Can you take over an existing integration?
Yes. We analyse the existing integration, document it if needed and check whether it is update-safe. Then we decide together: keep running it, modernise it selectively or replace it. Afterwards, the knowledge no longer sits in just one head.
Do you work with our Business Central partner?
Yes. Your partner stays responsible for Business Central, we take responsibility for the integrations. We coordinate extensions, permissions and update dates directly with them. There is no need to change partners.
Where is our data processed?
In your Microsoft environment. Business Central and the Azure services for the integration run in your tenant. Exclusively in EU data centres on request. Credentials are stored in Azure Key Vault, permissions are limited to what is necessary.
Do you use AI?
Yes, where it helps and stays traceable. For example, when reading incoming documents or matching items from partner formats. The core logic of your integrations remains rule-based and verifiable. Your data does not flow into the training of public AI models.
Where is your company losing time it doesn't need to? Let's find out what will accelerate your company.
No obligation. Easy to follow. Focused on your specific business value.
In an intro call, we work out which processes offer the biggest lever – functionally, technically and commercially. No buzzwords, just a clear view of feasibility, risks and benefits.