Microsoft Dynamics 365 Finance and Supply Chain Management and the battery passport: integration pattern
How data from Microsoft Dynamics 365 Finance and Supply Chain Management (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 (Finance and Supply Chain Management (formerly Finance and Operations))
- Checked
- vendor documentation, 24 October 2026
- Managed integration
- —
Business events announce changes, but according to Microsoft they are no way to export data and may arrive out of order: after the event the middleware reads the data through OData.
Interfaces
| Interface | Protocol | Sign-in | Events | Objects | Checked |
|---|---|---|---|---|---|
| OData data entities (/data)Data entities (products, serials, production, deliveries, returns) | OData V4 | OAuth 2.0 client credentials | none | Product/material master, Batch/serial number, Production order, Delivery/goods issue, Return | checked in the vendor documentation, 24/10/2026 |
| Business eventsBusiness events | REST | OAuth 2.0 client credentials | Business events | Product/material master, Production order, Delivery/goods issue | checked in the vendor documentation, 24/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.
Condition data from BMS and service
A battery management system or a service tool reports measurements such as capacity fade or cycles; BatteryPass accepts newer measurements and publishes according to the organisation's policy.
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
- 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.