Integrations · Dynamics 365 Business Central
Business Central. On the roadmap.
A Dynamics 365 Business Central connector is on the OmniPATH roadmap. It is designed to use service-to-service authentication, so no user login will have to keep the sync alive, and a draft-to-post lifecycle with automatic ledger booking, with GL accounts and dimensions mapped to your departments and cost centres. Today, OmniPATH connects to Xero, QuickBooks and Sage 50, Sage 200 and Sage Intacct.
The planned design
What the connector will do differently.
The AP automation case is the same whatever the ledger. Here is how the Business Central connector is planned to work when it ships.
Unattended
No login
Client-credentials sync will keep running whether or not anyone is signed in.
Controlled
Draft to post
Nothing will book to the ledger until validation passes.
Coded
No re-keying
Line items, dimensions and tax will be mapped on the way in.
Isolated
Per-tenant
Each customer environment will be configured independently.
The planned data flow
What will go which way, and why.
Many Business Central integrations are one-way pushes that stop once an invoice is created. OmniPATH is planned to treat Business Central as the system of record for what is posted, and to enrich everything on the way in so it arrives fully coded.
OmniPATH will write to Business Central
Posted clean, fully coded.
- Purchase invoices with line items
- GL accounts and dimensions per line
- Vendors matched or created on the first invoice
- Drafts created, validated, then posted
OmniPATH will read from Business Central
Kept in step with your ledger.
- Chart of accounts, mapped natively
- Dimensions: departments and cost centres
- Posting status written back for audit
- Vendor ledger entries
Built to the Business Central API
Designed as a real connector, not a generic bridge.
Four design choices that are planned to make this a real Dynamics 365 Business Central integration rather than a CSV exporter with a logo on it.
01 · Planned
Service-to-service authentication
OmniPATH will authenticate to Business Central with client credentials, so sync will keep running whether or not anyone is signed in. No expiring user session, and no broken nightly job because someone left.
- Client-credentials OAuth: unattended, machine to machine
- No per-user login needed to keep sync alive
- Survives staff changes: the connection won’t be tied to a person
02 · Planned
Draft-to-post lifecycle, with control
Each approved invoice is planned to be created in Business Central as a draft, validated against your GL and dimension rules, then posted with automatic ledger booking. You keep the safety of a review step without the manual keying.
- Draft created from the approved OmniPATH invoice
- Validated against GL accounts and required dimensions
- Posted with automatic ledger booking, fully traceable
03 · Planned
Dimension-aware GL mapping
Departments and cost centres will flow through as Business Central dimensions on every line. Map a site or cost centre once in OmniPATH and every invoice line will land on the right account with the right dimension, with no manual tagging at month-end.
- GL account mapping with full dimension support
- Departments and cost centres applied per line item
- Site-to-dimension mapping set once, applied every time
04 · Planned
Per-tenant configuration
Designed for partners and multi-entity groups. Each Business Central environment will get its own GL mapping, dimension rules and sync configuration, isolated from every other customer in the deployment.
- Independent configuration per Business Central environment
- Multi-entity and partner deployments in scope
- Mappings and history isolated per customer
LEDGE and Business Central
What LEDGE will answer once it’s connected.
Once the connector ships, LEDGE, your AI financial intelligence officer, will see both live procurement data and a persistent history from Business Central, so it will answer questions that would otherwise mean exporting two CSVs and pivoting in Excel. It answers the same questions today for Xero, QuickBooks and Sage.
- Trend questionHow has our gross margin changed over the last six months, and which suppliers are driving it?
- Reconciliation questionList approved invoices over £1k where I can’t see the matching payment cleared the bank.
- Pricing questionWhich suppliers have raised prices more than 10% against six months ago?
- Dimension questionShow spend by dimension, Hospitality against Retail by region, for the last quarter.
- Forecast questionBased on three months of outflow, what’s our projected cash position at month-end?
- Audit questionShow every FS Foodservice invoice over £500 posted to Business Central in March, with GRN status.
The OmniPATH layer
Business Central is brilliant for accounting. OmniPATH will be the layer in front.
Procurement, approvals and spend control belong ahead of the general ledger. With the connector, OmniPATH will give finance speed, accuracy and real-time visibility across every transaction before it posts to Business Central.
Without OmniPATH
- Manual draft entry. Re-keying invoice lines into Business Central from PDFs and email.
- No purchase approvals. Spend posts unchecked and surfaces at month-end.
- Manual dimension tagging. Departments and cost centres added by hand, inconsistently.
- Broken nightly syncs. Jobs tied to a user session that expires or leaves.
- Month-end scramble. Reconciliation drags across multiple entities.
With OmniPATH, once the connector launches
- AI invoice capture. Will extract, code and post to Business Central in seconds.
- Digital approval workflows. Nothing will book to the ledger unauthorised.
- Automatic dimensions. Departments and cost centres mapped once, applied to every line.
- Unattended sync. A client-credentials connection that won’t depend on a person.
- Real-time spend visibility. Committed and posted spend visible as it happens.
Available today
Approvals, AI capture, matching and spend visibility work now, whatever your ledger. The ledger connection itself is live today for Xero, QuickBooks and Sage.
What the books looked like before the gate.
Day zero is sealed from the accounting system before OmniPATH changes anything. This is what one year of ledger data looked like going in.
of profiled spend belonged to suppliers keyed under more than one name: one retailer four ways, a food supplier twice, another with a typo.
supplier contacts in the accounting system carried no spend in the sealed year. Every dormant record is a door left open.
of a year's ledger spend was a total on a bill. The largest supplier, nearly a third of profiled spend, had no lines at all.
of spend seen is VAT at stake on rate mismatches. The customer has already actioned 4.0%; 4.6% is still open.
of the year's bills carried a date still in the future when the baseline was sealed. Each one pulls spend into the wrong period.
of profiled spend went to supermarkets, outside any agreed price or catalogue.
From the sealed day-zero epoch of one live single-site hospitality operator (sealed 10 Sep 2026, covering the previous 12 months) and the findings read on 23 Oct 2026. Supplier groupings are our reading of the sealed spend records. How we measured this
Questions
Dynamics 365 Business Central, answered.
Can I connect Business Central today?
Not yet. The Business Central connector is on the roadmap. OmniPATH connects today to Xero, QuickBooks and the Sage range (Sage 50, Sage 200 and Sage Intacct). If Business Central is your ledger, ask during the demo and we will share the current timing.
Which versions will be supported?
The connector is planned for Dynamics 365 Business Central online (SaaS) through the standard Business Central API. It is designed to support single-environment and multi-environment (production and sandbox) tenants, with configuration set per environment so production and test never cross over.
How will OmniPATH authenticate to Business Central?
Through client-credentials OAuth: a service-to-service connection that won’t need a user to be signed in. Scheduled syncs will keep running unattended and the connection will survive staff changes, because it won’t be tied to an individual login.
How will GL accounts and dimensions be handled?
OmniPATH is planned to map your Business Central chart of accounts natively and support full dimensions: departments and cost centres. When you raise a purchase request against a site or cost centre in OmniPATH, the matching dimension will be applied automatically, so every posted line lands on the correct account and dimension without manual tagging.
Will OmniPATH create duplicate invoices in Business Central?
It is designed not to. Each invoice will carry a unique external identifier referencing the source OmniPATH document, and the draft-to-post lifecycle will validate before booking, so the same approved purchase cannot be posted twice.
Will it support multiple companies or entities?
Yes, that is part of the design. Configuration will be per tenant, so multi-entity groups and partners running several Business Central environments get independent GL mappings, dimension rules and sync settings, isolated from one another.
How will the connection be secured?
The same way as our live integrations: OAuth tokens encrypted at rest and all API traffic over HTTPS. Your data lives in a tenant-isolated database with row-level security. LEDGE uses Anthropic Claude under a no-training, no-retention agreement, fully GDPR-aligned.
Business Central. On the roadmap.
Register your interest in a 30-minute demo, and see the same flow working today with Xero, Sage or QuickBooks.
No minimum term · UK-based support