Do you require AL extensions in our tenant?

No. The connector uses the standard Business Central REST API. Optional AL bundles are available where deep manufacturing hooks are needed.

Does this work with Business Central on-premise?

Yes, both Cloud and on-premise are supported.

What about Dynamics NAV?

Older NAV tenants can be supported via file-based integration; talk to us about migration timing.

Integration

Microsoft Dynamics 365 Business Central integration.

If Dynamics 365 Business Central runs finance today, Worldover slots on top as the substance, formula, regulatory and manufacturing operating layer. The connector uses the Business Central REST API and is bi-directional at the object level: no CSVs, no shadow spreadsheets, no per-tenant custom code.

Quick answer

The Worldover Dynamics 365 Business Central integration is a bi-directional connector built on the Business Central REST API. It syncs items, customers, vendors, purchase orders, sales orders, item ledger entries and invoices. Worldover owns the substance master, formula and BOM, batch record, QC and regulatory documentation; Business Central continues to own the general ledger, AR, AP and financial reporting. Typical outcomes: zero CSV reconciliation, one source of truth per record, no per-tenant AL code, deployed in 3 to 4 weeks alongside Phase 1.

Built on Business Central REST API, no per-tenant AL code
Bi-directional sync at object level, no CSV reconciliation
Items, customers, vendors, POs, SOs, item ledger, invoices
Business Central keeps GL, AR, AP; Worldover owns substance and batch
Cloud (SaaS) and on-premise supported
Deployed in 3 to 4 weeks alongside Phase 1

See how Worldover handles the Dynamics 365 Business Central connector for you

How this connects to Worldover

Replacing five subscriptions with one system you actually run the business on?

Worldover is the AI operating system for chemicals, cosmetics and supplement businesses. One platform, one data model, custom-built around each team.

See how Worldover works

Which objects sync, and which way

Items: created in Worldover from the substance and formula record, pushed to Business Central as inventory items.
Customers and vendors: bi-directional, with Business Central as the finance master.
Purchase and sales orders: raised in either system, mirrored in the other.
Item ledger entries: batch and lot movements owned by Worldover, financial stock value posted to Business Central.
Invoices: raised in Business Central from the shipped sales order.

What stays in each system

Business Central stays the general ledger and financial reporting layer. Worldover owns the substance master, formula, BOM, batch record, QC, regulatory documentation and customer document portal.

Cloud and on-premise

Business Central Cloud (SaaS) and on-premise are both supported. Authentication uses OAuth 2.0 against Entra ID for Cloud and service-to-service for on-premise.

Worldover for this

See object ownership and a live transaction flow

In 20 minutes a Worldover specialist will walk the Business Central connector on a sample tenant: exact object ownership per record type, field mappings, and a live sales order flowing between the two systems with batch and lot data attached. You leave knowing exactly what stays in Business Central and what moves to Worldover.

Book a connector demo

FAQs

Common questions.

Why Worldover? Great question.

It takes a little longer to answer properly, so it might be worth pouring a cup of tea. Substance-based businesses need technology that understands their ontology, and generic ERPs just aren't up to the job. This is why an AI-native operating system is the play.

Read the essay

See Worldover on your operation.

A 20-minute working session. Your SKUs, your customers, your documentation. No slide deck.