Finance & Operations connector for enterprise ERP
Microsoft Dynamics 365 Finance & Operations (FinOps) connector for enterprise-scale financial data retrieval and posting.
Authentication: OAuth 2.0 via Entra ID service principal
System type: D365_FINOPS
Protocol: OData v4
API reference: Finance & Operations OData API
See your Finance & Operations data in Claude — book a 30-minute call.
Supported resources
Section titled “Supported resources”Resources are discovered from your Finance & Operations OData endpoint. The adapter supports batch fetch and batch write operations against standard F&O data entities.
| Resource | FETCH | PUSH |
|---|---|---|
| OData entities (dynamic) | ✓ Yes | ✓ Yes |
Registers this connector fills
Dynamics 365 Finance & Operations keeps 10 registers current in Civil Memory. Each name is the record you ask for, not the system it came from - ask for it in Studio or from your own AI client.
| Register | What it holds | Fields from Dynamics 365 Finance & Operations |
|---|---|---|
Budget vs actualbudget_vs_actual | Budget against actual spend for the organisation, by expense category. | Fills all of 10 |
Customer listcustomer_list | Customers registered in your ERP. | Fills all of 27 |
Employee listemployee_list | Employees registered in your payroll system. | Fills all of 21 |
Gl journal entrygl_journal_entry | General ledger journal entries: payroll, payables, receivables and manual postings. | Fills all of 13 |
Invoice issuedinvoice_issued | Invoices your organisation has issued to customers. | Fills all of 25 |
Payable entrypayable_entry | Outstanding supplier bills and the aged payables balance. | Fills all of 18 |
Profit and lossprofit_and_loss | Profit and loss for a period. | Fills all of 14 |
Receivable entryreceivable_entry | Outstanding customer invoices and the aged receivables balance. | Fills all of 15 |
Trial balancetrial_balance | Debit and credit balance per general ledger account. | Fills all of 13 |
Vendor listvendor_list | Vendors and suppliers registered in your ERP. | Fills all of 24 |
The full field list, requiredness and an example record for any register are on its published contract. Where more than one system fills a register, the register is the same shape either way.
Integration model
Section titled “Integration model”Uses OAuth 2.0 client credentials to authenticate against the F&O OData v4 endpoint. The adapter performs batch fetch and batch write operations. EXECUTE and LOOKUP verbs are not currently supported.
This connector is in Beta - it is functional for read and batch write workflows but does not yet support the full feature set of the Business Central adapter.
Connection setup
Section titled “Connection setup”Required values:
- Client ID - the Entra app registration client ID
- Client Secret - the app registration secret
- Environment URL - your F&O OData endpoint
Security
Section titled “Security”Access type: Read and governed write
Demiton reads and writes F&O data entities via OData. Writes occur only through governed workflows. Use a dedicated Entra service principal with the minimum data entity access required.
What Demiton does not touch: F&O user accounts, security roles, and access control remain owned by Finance & Operations.
Next steps
Section titled “Next steps”- Connecting a System - step-by-step wizard for setting up the connector
- Business Central - the stable companion ERP connector
- MCP Server - query your F&O data through Claude once connected
- Connect your operation - talk to us about scoping a Connected deployment
Talk to the team
Tell us what you run - your ERP, field, payroll and document systems - and we will show you the registers Demiton would keep current from them, on your data, in a 30-minute call.