ERP connector / durable document sync
Connect Business Central records to controlled EDI delivery
Verify the exact company, synchronize changed records and keep ERP state separate from partner mapping, delivery and acknowledgement evidence.
Direct answer
Direct answer
Shipment Sentry’s Dynamics 365 Business Central EDI integration encrypts Microsoft Entra credentials, verifies the exact company, pulls changed sales orders, sales invoices, purchase orders, purchase invoices, customers, vendors and items through API v2.0, and stores tenant-scoped cursor and ETag evidence. It can create or update the four document resources, process clientState-verified webhook notifications idempotently, and renew short-lived subscriptions on a schedule. Partner-specific mapping and release gates still control the EDI output.
Why a parser is not enough
ERP synchronization and EDI acceptance are different state machines. A Business Central record can synchronize successfully while a partner mapping is missing, an EDI preflight blocks, AS2 delivery fails or the receiver rejects the business document. Keeping those states correlated but separate gives users actionable detail.
What the control should check
- 01Encrypt tenant, environment, company, client and secret configuration.
- 02Verify the configured company before activating synchronization.
- 03Pull only records changed after the resource cursor.
- 04Store external ID, ETag, content hash and encrypted normalized payload.
- 05Validate webhook handshake and clientState, then deduplicate notifications.
- 06Use If-Match on update and renew subscriptions before their short expiry.
Working example
BUSINESS CENTRAL API v2.0
salesOrders / purchaseOrders / invoices / master data
↓ cursor + ETag + encrypted record
CANONICAL MAPPING → PARTNER PACK → EDI RELEASE
↓
transport receipt ≠ business acknowledgementPush is limited to sales orders, sales invoices, purchase orders and purchase invoices. Master-data resources are read into the mapping boundary.
Failure modes worth catching
- Valid credentials point to the wrong Business Central company.
- A webhook is accepted without checking clientState.
- Concurrent ERP edits are overwritten without an ETag.
- An ERP sync success is shown as partner acceptance.
Put it into the dispatch workflow
- 1Create the Microsoft Entra app and grant Business Central API permissions.
- 2Save encrypted credentials and verify the exact company.
- 3Select document and master-data resources to synchronize.
- 4Run an initial pull and inspect durable record evidence.
- 5Register webhook subscriptions and let scheduled renewal maintain them.
- 6Map canonical records, certify the partner pack and release validated output.
Questions
Implementation answers
Which Business Central records synchronize?
Sales orders, sales invoices, purchase orders, purchase invoices, customers, vendors and items can be pulled; the four document resources can also be pushed.
How are webhook notifications secured?
Each connector has a random callback token, and notifications must match the encrypted clientState before a deduplicated queued pull begins.
Are subscriptions permanent?
No. Business Central subscriptions are short-lived, so Shipment Sentry renews active connector subscriptions on a schedule.
Sources and limits
Reviewed 2026-07-20. Public references cannot establish every partner-specific rule. Current implementation guides and agreements remain controlling.
Keep investigating