Microsoft Dynamics 365 Business Central and the battery passport: integration pattern
How data from Microsoft Dynamics 365 Business Central (Microsoft) reaches the battery passport through the BatteryPass API: interfaces, workflows and when we checked them.
An integration pattern, not a ready-made connector: your ERP or integration platform reads and writes through the BatteryPass API with an organisation key. The details below come from the vendor documentation and were checked on the date given.
- Vendor
- Microsoft
- Deployments
- Cloud (Business Central online (API v2.0)); On-premise (Business Central on-premises (API v2.0))
- Checked
- vendor documentation, 25 October 2026
- Managed integration
- —
The standard API returns item ledger entries without serial and lot numbers; that needs a custom AL API page. Webhook subscriptions expire after three days and must be renewed.
Interfaces
| Interface | Protocol | Sign-in | Events | Objects | Checked |
|---|---|---|---|---|---|
| API v2.0Standard API (items, item ledger entries, sales documents) | OData V4 | OAuth 2.0 client credentials | none | Product/material master, Delivery/goods issue | checked in the vendor documentation, 24/10/2026 |
| Webhook subscriptions (/api/v2.0/subscriptions)Change notifications | REST | OAuth 2.0 client credentials | Webhooks | Product/material master, Delivery/goods issue | checked in the vendor documentation, 24/10/2026 |
| Custom AL API pageCustom API page for item ledger entries with serial numbers | OData V4 | OAuth 2.0 client credentials | none | Batch/serial number | checked in the vendor documentation, 25/10/2026 |
Matching workflows
Units from production
Serial numbers from the production confirmation or goods receipt are staged as an import; members review, commit and approve before any passport appears.
Passport links back into the ERP
The middleware follows the change feed and writes the GS1 Digital Link and the passport status to the serial number record in the ERP, so labels and delivery papers carry it.
Returns and repairs as lifecycle events
Completed repairs, inspections and component replacements from service or return orders appear as events in the unit's history.
Product change leads to a new model version
A change to the product master in the ERP triggers a notification; a member creates a new model version in BatteryPass. Declared data is never written automatically.
Import presets
- Business Central item ledger with serial numbers: Item ledger entries from Microsoft Dynamics 365 Business Central with their serial number, as a custom AL API page returns them (the standard itemLedgerEntries API has no serial numbers). Column names of the API page and of the user interface's Excel export (German and English). Assumes that the model identifier is the item number. The posting date stands in for the manufacturing date: export only entries of the entry type Output (the output postings of production), otherwise a transfer or a sale writes the wrong date.
- Generic CSV file: For any ERP and for files a middleware writes itself: GTIN, serial number, manufacturing date, facility (name or GLN), model version and battery status, with German and English column names.