Business Central + Pabau
Keep your clinic's customer records in step with your ERP.
If finance runs on Microsoft Dynamics 365 Business Central, Pabau keeps it fed. The Data Sync connector maintains a two-way link between Pabau clients and Business Central customers — created, updated and numbered the way your finance team expects, with every delivery logged.
- Two-way client ↔ customer sync
- Number-series-aware record creation
- Standard API or custom OData pages
Up and running in three steps
Connect with your Entra ID app
Enter your Microsoft Entra tenant, client ID and secret plus your Business Central environment and company — credentials are stored encrypted.
Choose API shape and rules
Use Business Central's standard API v2.0 or your own custom OData pages. Set customer numbering, delete behaviour and sync directions to match your finance policy.
Map fields and go live
Map Pabau client fields to Business Central customer fields, link any records that already exist on both sides, and watch deliveries in the sync log.
Everything the integration handles
Two-way customer sync
Pabau clients and Business Central customers stay aligned, with per-object direction control (out, in, or both).
Near-real-time delivery
Client creates and updates sync as they happen — not on a nightly batch.
Number series respected
New customers are created through your Business Central number series, or with a prefix pattern you define.
Standard API or custom pages
Works with Business Central's standard customer API v2.0 or your own OData V4 pages for customised BC environments.
Finance-grade guard rails
Configurable delete handling, create-on-update policy and inbound-create protection keep the ledger side safe.
Full sync log
Every delivery is recorded with status, payload and retries — with stuck records self-healing via background sweeps.
Finance stops re-typing the front desk's work
Every new patient the clinic registers appears in Business Central as a properly numbered customer — no exports, no manual account creation, no drift between systems.
- Customers created with your number series
- Demographic updates flow through automatically
- Two-way option keeps edits from either side
- Existing records linked with a guided wizard
Built to survive real BC environments
Custom pages, strict numbering, delete policies, sandbox vs production — the connector was built and proven against customised Business Central deployments, not just the demo tenant.
- Custom OData V4 page support
- Configurable delete and create policies
- Encrypted Entra ID credentials
- Delivery log with automatic retries
Frequently asked questions
What do I need to connect?
A Microsoft Entra ID app registration (tenant ID, client ID, client secret) with access to your Business Central environment, plus the environment and company you want to sync with.
Does it work with a customised Business Central?
Yes. Alongside the standard customer API v2.0, the connector supports custom OData V4 pages — so it can work with the entities and fields your BC partner has built.
How are new customer numbers assigned?
Your choice: let Business Central assign numbers through its number series, or have Pabau generate them with a prefix pattern you configure.
What happens if a delivery fails?
Failed deliveries are retried automatically and remain visible in the sync log with their status and payload; background sweeps self-heal stuck records.
See Business Central + Pabau in action
Join thousands of clinics running bookings, records, billing and marketing on Pabau — with Business Central connected.
