Microsoft Dynamics 365 Business Central and JAGGAER integration

What moves between them

The main flow runs from JAGGAER into Microsoft Dynamics 365 Business Central. ml-connector reads the supplier invoices captured in JAGGAER through the J1P invoice endpoint and posts them into Business Central as draft purchase invoices, mapped to the matching vendors, GL accounts, and dimensions. Master data flows the other direction: Business Central vendors and the chart of accounts are pushed into JAGGAER so suppliers and accounting codes line up with the finance system. Purchase orders are kept aligned so an invoice in JAGGAER references a Business Central purchase order, and JAGGAER payment status reflects what has been paid in Business Central. GL accounts are read only in Business Central and JAGGAER does not write GL accounts or payment records, so the ledger stays in Business Central and ml-connector never writes financial entries back into JAGGAER.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the JAGGAER side it requests an OAuth2 client credentials token from the Keycloak realm J1p-integrations on the customer host, caches it, and refreshes it before the roughly one hour expiry. On the Business Central side it runs the Entra client credentials flow against the api.businesscentral.dynamics.com scope and builds the base URL from the stored tenant and environment name, since BC publishes no shared host. Because the J1P API has no publicly documented webhook, ml-connector polls JAGGAER invoices on a schedule rather than waiting for a push, and reads each invoice header and its line items by id. Vendors and GL accounts are mapped first, so every imported invoice line references a Business Central vendor and account that already exist, and the purchase order reference is carried so JAGGAER matching and the Business Central document line up. Business Central draft purchase invoices are not posted automatically; ml-connector creates them as drafts and leaves the Microsoft.NAV.post action to a controlled step so nothing posts to the ledger unreviewed. Business Central has no idempotency key header and JAGGAER deduplicates on the supplier invoice number, so ml-connector filters on the document number before creating a record and uses a stable BullMQ jobId built from the JAGGAER invoice id to avoid double booking a re-read invoice. Where Business Central webhooks fire on a vendor or invoice change, ml-connector takes the signal, fetches the changed record, and renews the three day subscription before it expires. Every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized manufacturer with around 700 employees runs Microsoft Dynamics 365 Business Central for finance and accounts payable and uses JAGGAER for sourcing, purchasing, and invoice capture across several sites. Before the integration, buyers raised purchase orders and suppliers submitted invoices in JAGGAER, then an AP clerk rekeyed each approved invoice into Business Central, which meant invoices sat for days, GL coding was sometimes wrong, and the supplier list in JAGGAER drifted out of step with the finance system. With Microsoft Dynamics 365 Business Central and JAGGAER connected, each captured invoice lands in Business Central within the polling window as a draft for review, coded to the right vendor and dimension and matched to its purchase order, while new vendors and account changes in Business Central appear in JAGGAER automatically. The rekeying step is gone and AP starts from records that already reconcile.

What you can do

• •Pull supplier invoices captured in JAGGAER through the J1P invoice endpoint and post them into Microsoft Dynamics 365 Business Central as draft purchase invoices.
• •Push the Business Central vendor master and chart of accounts into JAGGAER so suppliers and procurement coding stay aligned with finance.
• •Match each JAGGAER invoice to its Business Central purchase order and report payment status back to JAGGAER.
• •Bridge Entra OAuth2 and the environment URL on the Business Central side with the JAGGAER Keycloak token from the J1p-integrations realm.
• •Poll JAGGAER on a schedule with document number and jobId dedup, retries, and a full audit trail on every record.

Questions

Which direction does data move between Microsoft Dynamics 365 Business Central and JAGGAER?

The main flow is JAGGAER into Microsoft Dynamics 365 Business Central. Captured supplier invoices move from JAGGAER into Business Central as draft purchase invoices, while the Business Central vendor master and chart of accounts are pushed back into JAGGAER. JAGGAER reads GL accounts for coding but does not write them and its payment status is read only, so the ledger stays in Business Central and ml-connector never writes financial entries back into JAGGAER.

Does JAGGAER push invoices, or does ml-connector poll for them?

ml-connector polls. JAGGAER claims an event-driven push mode for its J1P API but does not document it publicly, so it is treated as poll only until JAGGAER professional services configures event delivery for the tenant. ml-connector reads invoices from the J1P invoice endpoint on a schedule you control and tracks the last processed invoice so each run only picks up new captures.

How does the integration bridge the two different authentication models?

ml-connector handles both. On the Business Central side it runs the Microsoft Entra OAuth2 client credentials flow and builds the base URL from the stored tenant and environment name, since BC has no shared host. On the JAGGAER side it requests a client credentials token from the Keycloak realm J1p-integrations on the customer-specific host and refreshes it before the roughly one hour expiry.