Key Takeaways
- Transformance connects to Microsoft Dynamics 365 Finance & Operations, which is running in production with customers; the connection typically takes 2-3 days, and your IT team may be involved.
- It reads customer master data, open customer transactions, invoices, journal entries, bank statements and remittances, and writes clearing postings, journal entries and reversals after a person approves.
- In Dynamics 365, each legal entity is its own company (DataAreaId), and OData returns only the user’s default company unless a cross-company query is used (Microsoft Learn, 2026).
- Approval thresholds are set by amount, entity and customer; the audit log records who approved, the input and the confidence of each decision.
- Microsoft recommends a certificate rather than a client secret for production apps and limits client secrets to 24 months (Microsoft Learn, 2025).
In This Article
- Key Takeaways
- How does Transformance connect to Dynamics 365 Finance & Operations?
- What does Transformance read from Dynamics 365 F&O?
- What does Transformance write back to Dynamics 365 F&O?
- How is the Microsoft Entra app registration set up?
- How does Transformance handle many legal entities in Dynamics 365?
- What stops a posting in Dynamics 365, and how do you prevent it?
- Who approves postings, and what does the audit trail record?
- How long does it take to connect Transformance to Dynamics 365 F&O?
How does Transformance connect to Dynamics 365 Finance & Operations?
Transformance connects to Dynamics 365 Finance & Operations through an app registration in your Microsoft Entra tenant, or through middleware, file/SFTP or its own on-premises agent, depending on your environment.
What Transformance reads, writes and connects in Dynamics 365 F&O
Dynamics 365 names as in Microsoft’s documentation; your environment may use extensions or different labels.
Dynamics 365 Finance & Operations is running in production with Transformance customers. The connection typically takes 2-3 days, and your IT team may be involved, mostly for the Entra registration and the service account.
How Dynamics 365 accepts an external application is Microsoft’s design. The app is registered in Microsoft Entra ID, then added on System administration > Setup > Microsoft Entra applications with its client ID, a name and a user ID. Microsoft’s walkthrough uses the Admin user as its example, then recommends, “as a better practice”, a dedicated service account “that has the correct permissions” (Microsoft Learn, 2026). The mapped user’s roles decide what the connection can see, so the service account is where most scoping work happens.
Microsoft documents four integration patterns for finance and operations apps: OData for synchronous, relatively low-volume exchange, “subject to service protection limitations and throttling”; the Data Management Framework package API for large, asynchronous volumes; recurring integrations for scheduled files; and business events for notifications (Microsoft Learn implementation guide, 2024). The method follows your environment and your IT team’s standards; we agree it in scoping.
Your data stays in your region, in a separate Azure environment per location, and VPC deployment in your own cloud is available. People sign in through SSO/SAML with role-based access control (RBAC). No customer data is used to train models.
What does Transformance read from Dynamics 365 F&O?
Transformance reads customer master data, open customer transactions, invoices, journal entries, bank statements and remittances, in every legal entity your Dynamics 365 service account is allowed to see.
In Dynamics 365 terms, a customer is a customer account per legal entity, linked to a party in the global address book; Microsoft treats customers in three legal entities as one because “they share the same global address book ID” (Microsoft Learn, 2026). Open items are each legal entity’s open customer transactions, with due date, cash discount date, currency and remaining amount.
The legal-entity trap sits in the read. Microsoft states: “By default, OData returns only data that belongs to the user’s default company.” The cross-company=true option returns every company the user can access, and a dataAreaId filter narrows it to one (Microsoft Learn, 2026). An integration that misses this sees one legal entity’s open items and none of the others’, until the second legal entity’s customers get reminders for invoices they have paid.
The day-one check: compare the open-item count and balance per legal entity with that legal entity’s AR aging. If one shows zero items, look at the service account’s roles there first.
Bank statements come from Cash and bank management in Dynamics 365, or Transformance processes the bank files directly. Remittances do not have to come from Dynamics 365 at all: DocSense reads emails and PDFs with over 97% extraction accuracy across 100+ document types and 170+ languages, with zero template configuration (payments with no reference).
Every read lands in Customer 360, one graph per customer and the working memory of Vero, the Transformance agent. The field map across all ERPs is in what AR automation reads from and writes to the ERP.
What does Transformance write back to Dynamics 365 F&O?
Transformance writes clearing postings, journal entries and other ERP updates, including reversals, back to Dynamics 365, and every posting waits for a person’s approval and passes posting validation first.
A clearing posting, in Dynamics 365 terms, is a customer payment journal line settled against one or more open invoices. Microsoft’s manual version: you “mark the invoices that were paid by the customer” and can enter a partial amount; a prepayment can post unsettled, because “settlement to an invoice can happen at a later time” (Microsoft Learn, 2025).
What happens to a difference depends on each legal entity’s Accounts receivable parameters (Settlement area): Automatic settlement, Maximum penny difference, Maximum overpayment or underpayment and Cash discount administration. Above the penny-difference limit, with no cash discount applicable, “the remaining amount is retained as an open balance on the payment transaction” (Microsoft Learn, 2026).
An illustrative case: with a maximum penny difference of 5.00 in one legal entity and 1.00 in another, a 4.80 short pay posts to the penny-difference account in the first and stays open on the payment in the second, as on-account cash someone has to work. Larger short pays belong with an approver anyway (partial payments and deductions).
On our side, ClearMatch auto-matches 95% of payments and runs end to end in under 8 minutes. Every proposed posting passes 100% posting validation, and nothing posts without human sign-off (ClearMatch).
Journal entries land as general journal lines in the legal entity they belong to. Reversals also post back after approval; the Dynamics 365 conditions are in the failure table below and the full flow in audit trail and reversals. Posting logic across ERPs: how external systems post payments and clear open items.
How is the Microsoft Entra app registration set up?
Your Entra administrator registers the app and adds its credential, then a Dynamics 365 administrator maps its client ID to a dedicated service account with only the roles it needs.
Six steps from Entra registration to a working Dynamics 365 connection
- Entra administrator: register the application in your Microsoft Entra tenant and note its application (client) ID.
- Entra administrator: add a credential. Microsoft recommends a certificate for production, and a client secret expires after 24 months at most.
- Entra administrator: add the API permissions Microsoft documents for Microsoft Dynamics ERP, within your security policy.
- Dynamics 365 system administrator: create a dedicated service account user and give it only the AR, cash and bank roles it needs, in every legal entity in scope.
- Dynamics 365 system administrator: on System administration > Setup > Microsoft Entra applications, add the client ID, a name and the service account as the user ID.
- Dynamics 365 system administrator: set a throttling priority for the client ID, then test the reads per legal entity in UAT before production.
The credential decides how often this connection can break. Microsoft “recommends that you use a certificate instead of a client secret before moving the application to a production environment”; a client secret lives 24 months at most, and Microsoft recommends an expiry of less than 12 months (Microsoft Learn, 2025).
Three failure modes show up in the first weeks:
- An expired secret stops every read and write on the same day.
- An app registered in Entra but never added on the Microsoft Entra applications page gets a token, then fails authorisation in Dynamics 365.
- A service account with roles in one legal entity returns nothing from the others.
Plan for throttling too. On the Throttling priority mapping page, an Entra application gets Low, Medium or High priority, so that “low-priority integrations throttle before high-priority integrations”; the setup needs the System administrator or Integration priority manager role (Microsoft Learn, 2026). A throttled request returns a retry-after value (Microsoft Learn implementation guide, 2024).
Least privilege in general: how AI agents access your ERP data safely.
How does Transformance handle many legal entities in Dynamics 365?
All legal entities of your Dynamics 365 environment consolidate in one Transformance environment; each posting lands in its own legal entity, under thresholds by entity, amount and customer.
Microsoft draws the boundary: every legal entity has a company ID, or DataAreaId; companies “are used as a boundary for data security”, and “users can access data only for the company that they’re currently signed in to” (Microsoft Learn, 2026). An integration inherits that boundary through its service account.
Three groups of settings differ by legal entity and change what a posting does:
- Settlement parameters in each legal entity’s Accounts receivable parameters: automatic settlement, penny difference, over- and underpayment limits, cash discount administration.
- Period status: once a fiscal calendar is selected for a legal entity, its period statuses and posting permissions are set on that legal entity’s Ledger calendar page (Microsoft Learn, 2026). One legal entity can be closed for September while another still accepts postings.
- Posting setup: bank accounts, customer posting profiles and any fixed dimension on the AR main account.
Centralized payments add a second layer. One legal entity, which Microsoft calls “the legal entity of the payment”, receives payments for all operating legal entities, and settlement generates due-to and due-from transactions. In Microsoft’s example, Fabrikam receives 600.00 and settles an invoice in Fabrikam East: Fabrikam credits “Due to Fabrikam East”, Fabrikam East debits “Due from Fabrikam”. The Intercompany accounting page decides which legal entity posts the cash discount and the realised exchange gain or loss (Microsoft Learn, 2026). If you run centralized payments, tell us in scoping: the payment posts in the receiving legal entity, not the invoice’s.
This is where Vero earns its place. When a payment matches no open item in the legal entity that received it, Vero investigates from Customer 360 plus internal and external sources, proposes the match with its evidence, and a person approves. The posting then follows that legal entity’s threshold.
A proof of value typically runs on one legal entity (4-5 weeks); add the others once the six checks below pass. The operating model is in running AR across many legal entities, dunning governance in AR collections across entities.
What stops a posting in Dynamics 365, and how do you prevent it?
Six Dynamics 365 conditions stop or distort a posting from an external system: a closed period, a settled transaction, a tolerance breach, a fixed dimension, an expired credential and throttling.
What stops a posting in Dynamics 365, and what to check per legal entity
Sources: Microsoft Learn, Can’t reverse a transaction (2024), Configure settlement (2026), Entra app credentials (2025) and Throttling prioritization (2026).
Run the six checks for every legal entity in UAT before it goes live, because each one carries its own calendar, parameters and roles. The fixed-dimension row is the easiest to miss: Microsoft explains that fixed dimensions “aren’t defaulted onto payment journals”, so settlement adds an adjusting entry with “a debit and credit to the same ledger account” (Microsoft Learn, 2026). The ledger balances, but your AR reconciliation carries lines nobody expected.
At month-end, put the integration’s posting cut-off into each legal entity’s close calendar, so a payment received on the last day is not rejected by a period finance has already put on hold (period close).
Who approves postings, and what does the audit trail record?
Postings follow Transformance’s multi-level approval model with thresholds by amount, entity and customer; admins configure the rules, finance users approve, and the audit log records every decision.
Transformance works with a 4-level approval model (read, recommend, execute, post) and keeps a human in the loop for ERP postings. Roles separate who configures the rules (admins) from who approves (finance), which keeps segregation of duties inside the AR process. Approvals run in Microsoft Teams, where finance already works.
The audit log stores the timestamp, what the system did, what the user did, who approved, the input and the confidence: the record an auditor asks for when a clearing posting looks wrong three months later.
In Dynamics 365, the Entra application is mapped to the service account’s user ID, so that is the user Dynamics 365 sees. Who approved it sits in the Transformance audit trail. Tell your auditors where each half lives; the questions they and IT ask are in the enterprise AI vendor checklist for finance, thresholds in detail in who approves what when an AI agent works in your ERP.
How long does it take to connect Transformance to Dynamics 365 F&O?
The Dynamics 365 connection typically takes 2-3 days and your IT team may be involved; a proof of value takes 4-5 weeks on one entity, full rollout 4-8 weeks.
In those days, IT runs the six setup steps above, first against a sandbox or UAT environment, then production. Microsoft applies all updates “first to the user acceptance testing (UAT) environment and then to the production environment”; customers can pause for a maximum of one consecutive service update, and Microsoft recommends that customers with data integrations test them (Microsoft Learn, 2026). Add the Transformance connection to your UAT test plan for every service update.
Week by week: how long AR automation implementation takes.
Who Transformance is for
- ERPs: Microsoft Dynamics 365 Finance & Operations across legal entities, in production with customers, as are SAP S/4HANA, SAP ECC, NetSuite, Dynamics 365 Business Central and Odoo; Oracle and Infor are supported.
- Size: mid-market to large enterprise, 250 to 2,000+ employees, including groups with several entities and shared service centres.
- Payment volume: from under 1,000 to over 100,000 payments a month.
- Industries: manufacturing, consumer goods and food and beverage, logistics, e-commerce, agriculture, energy and professional services.
- Scope: cash application alone, or the full order-to-cash (cash application, deductions, AR collections, cash forecasting).
Conclusion: one connection, decided per legal entity
A Dynamics 365 Finance and Operations integration works when each legal entity’s roles, tolerances and periods are checked once, so Transformance reads across all legal entities and posts only approved items.
Start with the Entra registration and one legal entity in UAT, and add legal entities after the six checks pass. Book a Call to scope your legal entities.
Key terms
- Cash application: matching incoming payments to open invoices and clearing them in the ERP.
- Sub-ledger: the customer ledger (Accounts receivable in Dynamics 365) that holds open customer transactions per legal entity.
- Journal entry: a posting line; in Dynamics 365, payment and general journal lines become vouchers when posted.
- On-account cash: a payment, or the rest of one, that is posted but not settled against an invoice.
- Period close: closing an accounting period; in Dynamics 365 the period status is set per legal entity.
- Audit trail: the record of who did what, when and on which input.
Related guides
- Which ERP systems Transformance integrates with
- How Transformance integrates with Business Central
- What AR automation reads from and writes to the ERP
- How external systems post payments and clear open items
- Who approves what when an AI agent works in your ERP
- What an AI agent’s audit trail records, and how a posting is reversed
- How AI agents access your ERP and customer data safely
- Running AR across many legal entities
Frequently Asked Questions
Which Dynamics 365 products does Transformance integrate with?
Transformance integrates with Microsoft Dynamics 365 Finance & Operations and with Dynamics 365 Business Central, and both are running in production with customers. Business Central has its own guide: how Transformance integrates with Business Central.
How many legal entities can Transformance handle in Dynamics 365?
Transformance consolidates multiple Dynamics 365 legal entities in one environment, with approval thresholds by entity, and is built for groups with several entities and shared service centres. A proof of value typically runs on one legal entity (4-5 weeks).
How long does a Dynamics 365 F&O rollout with Transformance take?
The ERP connection typically takes 2-3 days, and your IT team may be involved for the Microsoft Entra app registration and the service account; full rollout takes 4-8 weeks.
Does the connection need a Microsoft Entra app registration?
The connection can run through an app registration in your Microsoft Entra tenant, mapped in Dynamics 365 to a dedicated service account, or through middleware, file/SFTP or Transformance’s on-premises agent, depending on your environment.
What payment volume does Transformance handle on Dynamics 365?
Transformance is built for companies with from under 1,000 to over 100,000 payments a month. ClearMatch auto-matches 95% of payments and runs end to end in under 8 minutes.
What does a Dynamics 365 integration with Transformance cost?
The cost depends on scope (cash application alone or the full order-to-cash) and on the number of legal entities, so we price it after a scoping call. Book a Call to get a figure for your setup.
Can Transformance reverse a posting in Dynamics 365?
Yes, Transformance can post a reversal back to Dynamics 365 after a person approves it. In Dynamics 365, a settled payment needs Undo settlement first, and the reversing date must fall in an open period of that legal entity (audit trail and reversals).
SAP, SAP S/4HANA, Microsoft, Dynamics 365, Business Central, Oracle, NetSuite, Odoo and Infor are trademarks of their respective owners (SAP SE, Microsoft Corporation, Oracle Corporation, Odoo S.A., Infor). Transformance is not affiliated with or endorsed by them.
