Microsoft Dynamics 365 F&O and Monday.com integration

What moves between them

The main flow runs from Microsoft Dynamics 365 F&O into Monday.com. ml-connector reads vendors, purchase orders, and vendor invoices from the OData service and creates or updates the matching items on the Monday boards you nominate, filling amount, status, date, reference, and vendor-link columns. A return flow reads Monday item and status changes by webhook and applies them to writable Dynamics entities, for example updating a pre-posting vendor invoice header or a vendor record. Reference data such as vendor accounts and financial dimension values is aligned so each Monday item links to a record that exists in Dynamics. Posted Dynamics journal entries are read-only, so they are mirrored to Monday for visibility but never written back from a board.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the Dynamics side it requests an Entra ID client-credentials token per environment host and refreshes it when a call returns 401, and it accepts the tenant-specific host plus the legal entity (dataAreaId) as configuration since there is no shared base URL. On the Monday side it sends the API token as a raw Authorization header and writes each column value as a JSON-encoded string against the board and column IDs you map. Pushing to Monday is prompt: a Dynamics Business Event such as invoice posted carries only identifiers, so the connector reads the full record over OData, then creates or updates the Monday item. Coming back, Monday webhooks need challenge verification on registration, are scoped one per board and event, and carry no HMAC on a personal-token webhook, so an OAuth app webhook with a signed JWT is preferred for production. Dynamics returns HTTP 429 with Retry-After under service protection limits and Monday caps board mutations at forty per minute, so the connector backs off and retries on both sides. Monday cursors expire, so item reads complete in one pass. Idempotency uses the Business Event ControlNumber inbound and a Monday Idempotency-Key on retried mutations, plus a full audit trail and error replay.

A real-world example

A mid-sized distributor running Microsoft Dynamics 365 F&O for procurement and accounts payable manages its approval and exception work in Monday.com. Before the integration, an AP clerk re-entered posted invoices and open purchase orders into a Monday board by hand so the team could chase approvals and disputes, and the board drifted out of date within a day. With the two systems connected, each posted vendor invoice and confirmed purchase order appears as a Monday item with its amount, due date, status, and vendor link already populated, and when a reviewer moves an item to approved or updates a field, the change is written back to the matching pre-posting Dynamics record. The board stays current automatically and the manual copy step is gone.

What you can do

• •Mirror Dynamics 365 vendor invoices, purchase orders, and vendors as Monday.com items with amount, status, date, and vendor-link columns.
• •Push promptly from Dynamics Business Events, reading the full record over OData before creating or updating the Monday item.
• •Write Monday status and column changes back to writable Dynamics entities such as pre-posting invoice headers and vendor records.
• •Bridge Entra ID OAuth client-credentials tokens to a raw Monday API token, mapping legal entity and board and column IDs.
• •Handle Dynamics 429 Retry-After limits and Monday's forty-per-minute mutation cap with backoff, retries, and a full audit trail.

Questions

Which direction does data move between Microsoft Dynamics 365 F&O and Monday.com?

The main flow is Dynamics into Monday: vendors, purchase orders, and vendor invoices become tracked items on the boards you choose. A return flow reads Monday status and column changes by webhook and applies them to writable Dynamics entities such as pre-posting invoice headers. Posted Dynamics journal entries are read-only, so they are mirrored to Monday for visibility but never written back from a board.

How does the integration push changes promptly when Dynamics events carry only identifiers?

Dynamics 365 Business Events fire on actions like invoice posted or purchase order confirmed, but each payload carries only key identifiers and a ControlNumber, not the full record. ml-connector uses the event as a trigger, reads the complete record back over the OData service, then creates or updates the Monday item. The ControlNumber is used to deduplicate events, since delivery order is not guaranteed.

Since Monday.com has no native ERP objects, how are invoices and POs represented?

Monday.com stores everything as boards, items, and typed columns, so an invoice or purchase order is an item on a board you configure, with columns carrying the amount, status, date, and a Connect Boards link to its vendor. The connector is configured with your specific board IDs and column IDs to give the data meaning. Column values are written as JSON-encoded strings, which ml-connector formats for each column type.