Dynamics 365 Finance

Access and limits

Authentication

Microsoft Entra application (client credentials)

Plans and access

Dynamics 365 Finance or Supply Chain Management (cloud). The Microsoft Entra application must be registered in Finance under System administration > Setup > Microsoft Entra applications. Calls run as the Finance user mapped to the Entra application and follow that user's security roles.

Test environment

Use a Tier 2 sandbox (*.sandbox.operations.dynamics.com) with the same app registration.

Rate limits

Priority-based throttling returns HTTP 429 with Retry-After when the environment is under load; Nexra waits and retries reads.

Pagination

Prefer: odata.maxpagesize (up to 1,000 here; server maximum 10,000) with @odata.nextLink.

Provider events

Business events and data events (to Azure Service Bus, Event Grid or Power Automate) are configured in Finance. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.

Before you build a flow

• Reads are scoped to the configured legal entity with cross-company=true and a dataAreaId filter; main accounts are shared.
• Documents are written as drafts only: sales and purchase orders are left unconfirmed, vendor invoices stay pending and general journals stay unposted. Confirming, posting, invoicing, settling and workflow submission are excluded.
• Data entities do not expose a modified timestamp, so no read can pick up only changed records. Reconciliation reads (sales and purchase orders, sales invoices, credit notes, free text and pending vendor invoices, journal lines, customer and vendor payments) run since the last run on their creation, document or transaction date and re-read the previous day; a record changed later, or posted later with an older date, is not picked up. Use Read everything each run, change tracking or data events for full change capture.
• Bank transactions: Finance publishes no public OData entity for posted bank account transactions or imported bank statement lines, so bank reconciliation reads are not available. Customer and vendor payment journal lines show the bank account each payment used.
• Credit notes are read as posted sales invoices with a negative total. Posted vendor credit notes are not available: this connector reads vendor invoices only while they are pending.
• Deletes are not implemented.
• The MainAccounts and SalesInvoiceHeadersV2 collection names are taken from their entity public names and are not listed on a Microsoft Learn entity page; confirm them in /data/$metadata.
• Ledger account display values require the ledger dimension format configured under Financial dimension configuration for integrating applications.
• Sales quotations are written in Created status only; sending, confirming (which creates a sales order) and marking lost or cancelled are excluded.
• Excluded by design: posting, invoicing, confirmation and workflow actions, free text invoice creation, writing customer and vendor payment journals, settlements, fixed asset transactions and all deletes. No OData bound actions are called.
• The SalesQuotationHeaders, SalesQuotationLines, FreeTextInvoiceHeaders, CustomerPostalAddresses, Currencies, ExchangeRates, PaymentTerms, LegalEntities, OperationalSites, WarehousesOnHand, TaxGroups, TaxCodes, FinancialDimensionValues, FixedAssets, Projects, PurchaseAgreements, CustomerPaymentJournalLines and VendorPaymentJournalLines collections and their fields are taken from the OData client Microsoft publishes in the Dynamics-AX-Integration samples. Newer releases may add V2 versions of some entities; confirm the collections in /data/$metadata.
• Every $filter value is validated against a strict pattern or enum and quoted as an OData literal; dates are normalised to UTC.

Developer reference