> For the complete documentation index, see [llms.txt](https://doc.duaer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.duaer.com/guides/dynamics-365-finance-operations-processes.md).

# Dynamics 365 Finance and Operations: see where purchase to pay and order to cash wait

Connect Dynamics 365 Finance and Operations to Duaer. It reads the steps of each purchase or sales order of one legal entity through OData.
## What does Duaer read from Finance and Operations?

Each purchase or sales order is a case, with the vendor or customer, the legal entity, currency and amount. The steps are:

- Purchase to pay: Order created (accounting date), Goods received (product receipts), Invoice posted (posted vendor invoices), Paid (settlement date).
- Order to cash: Order created, Goods issued (packing slips), Invoice created, Paid (settlement date).
- Canceled orders are left out. The steps match the process templates, so the boards in My processes on the employee portal work as they are.

## How do you connect Finance and Operations to Duaer?

1. Register an application in Microsoft Entra and create a client secret.
2. In Finance and Operations, open System administration › Setup › Microsoft Entra applications, add the application's client ID and link it to a user with read access only.
3. In Duaer, create a Dynamics 365 Finance and Operations API credential with the environment host (like acme.operations.dynamics.com), the tenant ID, the client ID and the client secret.
4. As an owner or admin, open Data sources, select Add source, choose Dynamics 365 Finance and Operations, choose the credential, enter the legal entity (for example USMF), select Check connection and confirm.

## How often does it read, and how much?

Each run reads four streams, one page each at most: orders, receipts or packing slips, invoices and settlements. Finance and Operations documents carry business dates rather than change times, so streams read date windows; after each window the next starts two weeks back, to catch documents posted with a past date. A step is never written twice. Read only.

## What are the limits?

- The resources, entities and tables read follow the vendor's published documentation and are not yet checked against a real system; the first real read may need adjustments. An environment's entity names can be checked at /data/$metadata.
- One source reads one process of one legal entity.
- Purchase requisitions are not read yet.
## Questions

### Can I read several legal entities?

Yes: add one source per legal entity.

## Related

- [Add a process source in Duaer](https://doc.duaer.com/build/process-sources.md)
- [See the process in your data and generate workflows in Duaer](https://doc.duaer.com/build/process.md)
- [Process findings and SOP conformance in Duaer](https://doc.duaer.com/build/process-findings.md)
- [SAP S/4HANA purchase to pay: see where each order waits](https://doc.duaer.com/guides/sap-s4hana-purchase-to-pay.md)
- [NetSuite purchase to pay and order to cash: see where each order waits](https://doc.duaer.com/guides/netsuite-purchase-to-pay-order-to-cash.md)