Business Central integrations that keep running after the next update.
We connect Business Central with your shop, your trading partners, DATEV, shipping and CRM. Your systems stay. Manual data transfer disappears.
Starting point
Today, people work in between your systems.
Orders are retyped from the shop. Delivery notices arrive by email. Accounting exports to DATEV every month. Every one of these handoffs costs time and creates errors. Time to automate.
01
Duplicate data entry
The same record is maintained in two or three systems.
02
Silent errors
A transfer fails. Nobody notices until a customer calls.
03
Blocked updates
Old customizations keep Business Central from staying current.
04
Knowledge in one head
Only one person knows how the integration works.
05
Excel as glue
Spreadsheets connect what systems don’t.
06
No transparency
Nobody can see which data flows where, and when.
Integrations
We connect Business Central with the tools you already use.
Every integration follows the same standards. Only the systems differ.
01
Shop integration
Shopware Shopify WooCommerce Amazon
Items, prices and stock levels flow into the shop. Orders come back to Business Central as sales orders. Every few minutes instead of the next morning.
02
EDI with trading partners
EDIFACT XML partner formats
Exchange orders, delivery notices and invoices electronically with your customers and suppliers. In whatever format your trading partner requires.
03
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’s missing.
04
Shipping integration
DHL DPD UPS GLS
Create shipping labels straight from the order. Tracking numbers and status flow back automatically.
05
CRM integration
HubSpot Salesforce Dynamics 365 Sales
Your sales team sees orders, revenue and open items right on the customer record. Without needing its own ERP access.
06
Power BI and Microsoft Fabric
Power BI Fabric Data Lake
Order intake, margin, liquidity and delivery capability in one dashboard. From Business Central and other sources.
07
Documents and e-invoicing
DMS XRechnung ZUGFeRD
Pass documents on to your document management system. Receive, validate and create e-invoices.
08
APIs 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 into Business Central.
How we work
Six rules for every integration.
An integration is only finished when it runs reliably in day-to-day operations. Every decision we make is aimed at that.
Rule 01
Standard before customization
If there’s a suitable standard connector, we use it. We only build custom what the standard can’t do.
Rule 02
Built to survive updates
We develop extensions in AL and connect via APIs and events. No changes to the standard code. Microsoft updates go through.
Rule 03
Error handling built in
Every transfer is logged. If it fails, it is retried or reported. No record gets lost silently.
Rule 04
Monitoring with alerts
You can see which data flowed where, and when. If something breaks, the person responsible knows before the business team asks.
Rule 05
Documented for people
Technical documentation for your IT. A plain-language description for the business team. No knowledge locked in one head.
Rule 06
Secure from day one
Sign-in via Entra ID, least-privilege permissions, credentials in Azure Key Vault. Data processing exclusively in EU data centers on request.
Process
Four steps to a running integration.
System Audit
½-day workshop
We map your systems and data flows. You get an overview, a prioritization and a reliable effort estimate.
Architecture
Duration: 1–2 weeks
We define which data flows in which direction, how often and with what error handling. In writing, before a single line of code is written.
Implementation and testing
Duration: depends on scope
Development in a sandbox, automated tests, acceptance by your business team. Only then does the integration go live.
Operations
Duration: ongoing
We monitor, maintain and adapt when your systems change. With a fixed service agreement on request.
Results
We measure before. And after.
Before the project starts, we record three metrics with you. After go-live, we measure them again. That way the benefit is traceable, not just claimed.
Manual effort
Metric 01
Minutes per order, delivery or posting.
Error rate
Metric 02
Corrections, follow-up questions and duplicate entries.
Lead time
Metric 03
From the incoming order to the finished sales order in the system.
For IT managers
Technology that doesn’t add to your IT team’s workload.
- Platform
- Business Central online. On-premises after checking the version.
- Development
- AL extensions following the 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.
- Operations
- 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.
½-day workshop. Fixed price. A clear result. If you then commission the implementation, we credit the full price.
€2,999net
Audit deliverables
Map of your systems and data flows- List of all manual handoffs with the estimated time spent
- Prioritized order of integrations
- Architecture proposal and effort estimate
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.
In the System Audit we decide with you in a half-day workshop what comes first. The architecture is then ready in one to two weeks. A single integration, for example with DATEV or a shipping provider, is often up and running within a few days. EDI or several systems with complex data flows may take longer. After the audit, you’ll know the schedule.
No. We develop extensions in AL and connect via APIs and events. The standard code stays untouched, and Microsoft updates go through. In operations, we test new versions in a sandbox first.
Standard first. If there’s a suitable connector, we recommend it, even if that means less development for us. We only build custom what the standard can’t do. Often it’s a combination: a standard connector plus a lean extension for your special cases.
Yes. We analyze the existing integration, document it where needed and check whether it is update-safe. Then we decide together: keep running it, modernize it selectively or replace it. Afterwards, the knowledge no longer sits in a single head.
Yes. Your partner remains responsible for Business Central; we take responsibility for the integrations. We coordinate extensions, permissions and update dates directly with them. There’s no need to switch partners.
In your Microsoft environment. Business Central and the Azure services used for the integration run in your tenant. Exclusively in EU data centers on request. Credentials are stored in Azure Key Vault, and permissions are limited to what’s necessary.
Yes, where it helps and stays transparent. For example, when reading incoming documents or mapping items from partner formats. The core logic of your integrations remains rule-based and auditable. Your data is not used to train public AI models.