--- title: Microsoft Dynamics 365 Finance and Operations API Integration on Truto slug: msfinance category: Accounting canonical: "https://truto.one/integrations/detail/msfinance/" --- # Microsoft Dynamics 365 Finance and Operations API Integration on Truto **Category:** Accounting **Status:** Generally available ## Unified APIs ### Unified User Directory API - **Users** — The User object represents a User. ## How it works 1. **Link your customer's Microsoft Dynamics 365 Finance and Operations account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Microsoft Dynamics 365 Finance and Operations.** The Proxy API is a 1-to-1 mapping of the Microsoft Dynamics 365 Finance and Operations API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Sync Chart of Accounts and Financial Dimensions for Expense Categorization** — Spend management and expense SaaS platforms can pull MainAccounts, FinancialDimensions, and Cost Centers from their customers' D365 F&O environments so employees categorize expenses using the exact accounting structure their finance team expects — eliminating manual mapping and dual-entry. - **Automate Accounts Payable Invoice Matching Against Purchase Orders** — AP automation platforms can read open PurchaseOrderHeaders and PurchaseOrderLines from D365 F&O to perform 3-way invoice matching, then write approved vendor invoices back into the ERP to queue them for payment runs without manual intervention. - **Push Journal Entries from SaaS Workflows into the General Ledger** — Any SaaS product that generates financial transactions — payroll, billing, corporate cards — needs to post those transactions as LedgerJournalHeaders and LedgerJournalLines in D365 F&O so the customer's books stay accurate without re-keying data. - **Pull Master Data for Customer and Vendor Records** — B2B platforms that manage procurement, sales, or onboarding workflows need reliable access to Customers and Vendors master data in D365 F&O to ensure records stay consistent across the customer's tool stack. - **Inject Sales Orders from External Commerce Platforms** — E-commerce, CPQ, and wholesale portal SaaS products can push completed orders as SalesOrderHeaders into D365 F&O, triggering the customer's native fulfillment, invoicing, and revenue recognition workflows without custom middleware. ## What you can build - **User Directory Sync with D365 F&O** — Use Truto's Unified User Directory API to pull user and employee records from your customers' D365 F&O environments for provisioning, role mapping, or identity management within your product. - **GL Account and Dimension Picker** — Build an in-app dropdown that lets your users select from their own D365 F&O Chart of Accounts and Financial Dimensions when categorizing transactions, ensuring every entry maps to their live accounting structure. - **Automated Journal Entry Posting** — Ship a one-click export that batches approved transactions from your SaaS into D365 F&O journal entries, complete with debits, credits, and dimension tagging. - **Real-Time Inventory Availability Display** — Query D365 F&O's InventSiteOnHand data to show live stock levels in your storefront or order management UI, preventing overselling across warehouses. - **Vendor and Customer Master Data Sync** — Keep vendor and customer records in your product continuously aligned with D365 F&O so your users never work with stale contact details, payment terms, or tax IDs. - **Purchase Order to Invoice Reconciliation** — Automatically match incoming invoices against open D365 F&O purchase order lines and surface discrepancies for review before writing the approved invoice back to the ERP. ## FAQs ### How does authentication work for Microsoft Dynamics 365 Finance and Operations? D365 F&O uses OAuth 2.0 via Microsoft Entra ID (Azure AD). Truto handles the OAuth flow, token refresh, and tenant-specific endpoint resolution so your end users can connect their D365 F&O environment without you managing any auth infrastructure. ### What API does D365 F&O expose, and how does Truto interact with it? D365 F&O exposes an OData v4.0 REST API built around logical 'Data Entities' — updatable views like CustomersV3, VendorsV2, MainAccounts, and LedgerJournalLines. Truto communicates with these OData endpoints and abstracts away pagination, query syntax, and entity-specific quirks. ### Are there specific Truto tools already available for D365 F&O? D365 F&O integration tools and additional Unified API resources are built on request. The Unified User Directory API (Users) is available today. Contact Truto to scope the specific data entities and workflows you need — typical turnaround for new tools is fast. ### How does Truto handle D365 F&O's multi-entity and multi-company architecture? D365 F&O scopes most data to a Legal Entity (company code). Truto manages the cross-company query parameters and data partitioning so your integration can target the correct legal entity without your end users needing to configure OData headers manually. ### What about rate limits and large data volumes? D365 F&O enforces throttling based on concurrent OData requests and payload size. Truto handles retry logic, pagination via OData continuation tokens, and request batching so you can reliably sync large datasets like full product catalogs or historical journal entries without hitting limits. ### Can I read and write custom fields or custom Data Entities? Yes. D365 F&O customers frequently extend standard Data Entities with custom fields or create entirely new entities via the AOT (Application Object Tree). Truto can be configured to read and write these custom extensions as long as the entity is published to the OData endpoint in the customer's environment.