Key Takeaways
- Six ERP products run in production with customers: SAP S/4HANA, SAP ECC, NetSuite, Dynamics 365 Finance & Operations, Business Central and Odoo. Oracle and Infor are supported.
- The ERP connection typically takes 2-3 days and your IT team may be involved; the full rollout takes 4-8 weeks.
- Transformance needs no custom ABAP and no modifications in your SAP system, on any S/4HANA edition or on ECC.
- Multiple SAP instances and company codes, NetSuite subsidiaries and Dynamics 365 legal entities consolidate in one Transformance environment.
- Nothing posts to the ERP without human sign-off, and ClearMatch validates 100% of postings before they go through.
In This Article
- Key Takeaways
- Which ERP integrations run in production, and which are supported?
- How does Transformance connect to each ERP?
- What does Transformance read from and write back to the ERP?
- How does Transformance handle several ERPs, instances and entities?
- Who approves what before Transformance posts to the ERP?
- Where does the ERP’s order-to-cash end and Transformance start?
- How long does the ERP connection take, and what does your IT team do?
- Which integration guide answers your question?
Which ERP integrations run in production, and which are supported?
Transformance integrates with SAP S/4HANA, SAP ECC, NetSuite, Dynamics 365 Finance & Operations, Business Central and Odoo, all in production with customers, and supports Oracle and Infor.
Common options are APIs, file/SFTP, your existing middleware or Transformance’s own on-premises agent. The connection method follows your environment, and your IT team may be involved. ERP terms in the table are the ERP vendors’ own. “In production with customers” means these connections run at customers today; “supported” means Transformance connects to that ERP.
Almost every larger company has an ERP: ERP applications are the most widely used e-business applications in the EU, used by 89% of large enterprises and 41% of small ones in 2025 (Eurostat, 2026, EU data). SAP estates are rarely a single edition. Among 198 respondents to the DSAG Investment Report 2026, 56% use S/4HANA on-premises, 54% SAP ECC or the older Business Suite, 17% S/4HANA Private Cloud and 5% S/4HANA Public Cloud (DSAG, 2026, DACH SAP users). Many run several at once, which is why the S/4HANA row lists three editions and ECC has its own guide.
How does Transformance connect to each ERP?
Transformance connects through the route your environment allows: APIs, RFC/BAPI or IDoc and SAP Cloud Connector for SAP, file or SFTP, middleware, an Azure app registration or its on-premises agent.
The per-ERP guides cover each case. The short version:
- SAP S/4HANA and ECC. Transformance needs no custom ABAP and no modifications in your SAP system. That fits SAP’s clean core principle: SAP describes released APIs as “stable, supported, and safe for customers and partners to use for building extensions” and “upgrade-safe by design” (SAP Learning, accessed 2026).
- Dynamics 365 Finance & Operations. In Microsoft’s procedure, an external application is registered in Microsoft Entra ID and then entered under System administration > Setup > Microsoft Entra applications. Microsoft calls “a dedicated service account that has the correct permissions” the better practice (Microsoft Learn, 2026). The registration lives in your Azure tenant, so your IT team creates it.
- Business Central. Microsoft describes third-party connections as Connect apps, a point-to-point connection “typically created using standard REST API” (Microsoft Learn, 2026).
- Odoo. If your route is Odoo’s external API, check your plan first: Odoo’s documentation says “Access to data via the external API is only available on Custom Odoo pricing plans” (Odoo documentation, version 18.0, accessed 2026).
- NetSuite, Oracle and Infor. APIs, file/SFTP or your existing middleware, or the on-premises agent where the ERP runs behind your firewall, depending on your environment.
Whatever the route, we recommend one rule: give Transformance its own technical user or integration role, never a person’s login. Every change in the ERP then points to the integration, and you can withdraw access in one place.
What does Transformance read from and write back to the ERP?
Transformance reads customer master data, open items, invoices, journal entries, bank statements and remittances, and writes back clearing postings, journal entries and ERP updates, including reversals, after approval.
The reads give Vero, the Transformance agent, the full picture of each customer account. The writes close the work in the ledger: an open item cleared against a payment, a journal entry for a difference, an update on the customer record, or a reversal when a posting has to be undone. Each write passes posting validation, and nothing posts without human sign-off.
Remittances often never reach the ERP. They arrive as email bodies, PDFs or portal downloads, and DocSense reads them with over 97% extraction accuracy across 100+ document types and 170+ languages, with no templates to set up.
A live connection meets the exceptions your team already knows: a closed posting period, a customer account blocked for posting, a EUR 9,950 payment against a EUR 10,000 invoice that leaves a EUR 50 residual item (illustrative amounts), or a USD invoice paid at a different exchange rate than it was booked at. These are the cases where the approver needs the evidence before anything reaches the ledger. How external systems post payments and clear open items walks through each one, what AR automation reads from and writes to the ERP is the field-by-field map, and the audit trail guide shows how a posting is reversed. The same open items also feed a cash forecast from SAP, Oracle and NetSuite data.
How does Transformance handle several ERPs, instances and entities?
Multiple SAP instances and company codes, NetSuite subsidiaries and Dynamics 365 legal entities consolidate in one Transformance environment.
Each ERP keeps its own entity unit: the company code in SAP, the subsidiary in NetSuite OneWorld, the legal entity in Dynamics 365. Transformance reads that structure as it is, and each entity’s ERP stays its system of record.
Access scoping matters here. In Dynamics 365 Finance & Operations, OData “returns only data that belongs to the user’s default company” unless the cross-company option is set, and a specific company is filtered by its dataAreaId (Microsoft Learn, 2026). Which companies the integration user may see is a decision for the first workshop.
Above the entities, Vero works on Customer 360, one graph per customer. A customer that buys from three of your entities and pays from one bank account is one record, with every open item, promise to pay and dispute in view. Illustrative example: a shared service centre sends EUR 61,400 covering invoices from SAP company codes 1000 and 2100. Vero sees both sets of open items in the same record, proposes the split with its evidence, and a person approves within the thresholds set for each entity. The operating model is in running AR across legal entities.
Who approves what before Transformance posts to the ERP?
Nothing posts to your ERP without human sign-off: Transformance uses a multi-level approval model with thresholds by amount, entity and customer, and separates who configures rules from who approves.
The model’s levels are read, recommend, execute and post. Thresholds work by amount, entity and customer, so a EUR 400 clearing on a domestic account and a EUR 250,000 clearing for a strategic customer can sit under different thresholds (illustrative amounts). Administrators configure the rules and finance approves; good practice is that whoever writes a matching rule does not approve the postings it produces.
The audit log stores six things for every action: the timestamp, what the system did, what the user did, who approved, the input and the confidence.
Data is hosted in your region, and VPC deployment in your own cloud is available (AR automation that keeps your data in your region). Access runs through SSO/SAML and RBAC. No customer data is used to train models; Transformance works with several models, and you can bring your own. The detail sits in who approves what when an AI agent works in your ERP and how AI agents access ERP data safely.
Where does the ERP’s order-to-cash end and Transformance start?
The ERP keeps the ledger, invoicing, clearing and its configured rules; Transformance adds the work around them: reading remittances, matching and AR collections, with sign-off before posting.
The split is factual: the ERP records and clears; Transformance reads what arrives outside it and proposes. Odoo shows the ERP side clearly. Its bank reconciliation “selects the matching items automatically when possible”, using default matching rules and reconciliation models, and each bank transaction sits on the journal’s suspense account until it is fully reconciled (Odoo documentation, accessed 2026).
For an item the ERP’s rules leave open, Vero investigates from Customer 360 and fetches internal and external information to find more matches. It then proposes with the evidence attached, and a person approves. ClearMatch, the cash application module, reaches a 95% auto-match rate and runs end to end in under 8 minutes (Transformance customer data, 2026).
The step-by-step split is in where ERP order-to-cash ends and AR automation starts. How configured SAP rules and an agent work side by side is in how AI agents work with SAP for accounts receivable.
How long does the ERP connection take, and what does your IT team do?
The ERP connection typically takes 2-3 days, and your IT team may be involved; the full rollout takes 4-8 weeks, with a proof of value in 4-5 weeks on one entity.
The connection is one step of the rollout, not the rollout. What your IT team typically prepares:
- A technical user or integration role with read rights for the entities in scope.
- The network route: the on-premises agent, SAP Cloud Connector, an SFTP folder or your middleware endpoint.
- For Microsoft ERPs, the Azure app registration in your tenant.
- Write rights for the postings in scope, which only take effect behind approval.
A sequence that works: read access on one entity first, recommendations next, postings with sign-off last. The full timeline is in how long AR automation implementation takes.
On SAP ECC, timing has a second clock. SAP provides mainstream maintenance for SAP Business Suite 7 core applications until the end of 2027, followed by optional extended maintenance until the end of 2030 (SAP News, 2020). Because the ECC connection is in production with customers, AR automation does not have to wait for the migration; see the ECC end-of-maintenance playbook for AR.
Which integration guide answers your question?
Each ERP and each control question has its own guide: start with your ERP’s page, then read the data map, posting, approval and audit guides.
- How does Transformance integrate with SAP S/4HANA?: on-premises, private and public cloud, what is read and written back in SAP terms, and why no custom ABAP is needed.
- How does Transformance integrate with SAP ECC?: the ECC connection today, and what carries over when you move to S/4HANA.
- How does Transformance integrate with NetSuite and OneWorld?: NetSuite records read and written, and how OneWorld subsidiaries are handled.
- How does Transformance integrate with Dynamics 365 F&O?: legal entities, and the Microsoft Entra app registration your IT team sets up.
- How does Transformance integrate with Business Central?: what Transformance reads and writes in Business Central, and how it connects.
- How does Transformance integrate with Odoo?: the Odoo connection, from open invoices to reconciled payments.
- How does Transformance connect to Oracle Fusion and EBS?: how Transformance connects to Oracle receivables.
- What data does AR automation read from and write to the ERP?: the master field map across ERPs, every data set read and every write-back.
- Where does ERP order-to-cash end and AR automation start?: which steps the ERP covers with standard functions and where an AR automation layer starts.
- How do external systems post payments and clear open items?: the posting and clearing flow from an external system, with the exceptions that block it.
- Who approves what when an AI agent works in your ERP?: approval thresholds by amount, entity and customer, and who configures versus who approves.
- What does an AI agent’s audit trail in finance record?: what the audit log stores for each action, and how a posting is reversed.
These pages are the integration documentation. How AI agents work with each ERP stays in how AI agents work with SAP for accounts receivable and how AI agents work with Oracle and NetSuite.
Who Transformance is for
- ERPs: SAP S/4HANA, SAP ECC, NetSuite, Microsoft Dynamics 365 Finance & Operations and Business Central, and Odoo in production with customers; Oracle and Infor 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 environment over every ERP, the ERP stays the record
Transformance connects to the ERPs finance teams run, six of them in production with customers today, and the ERP connection typically takes 2-3 days. The ERP stays the system of record: Transformance reads what it needs, Vero proposes with evidence, and nothing posts without human sign-off within your thresholds. Pick your ERP’s guide above, or Book a Call to map your entities and connection route.
Key terms
- SAP S/4HANA: SAP’s current ERP suite, run on-premises, in a private cloud or as a public cloud edition.
- Sub-ledger: the AR (customer) ledger where open items sit before they roll up to the general ledger.
- Journal entry: a posting with balanced debits and credits, one of the writes Transformance makes after approval.
- Audit trail: the record of who or what did what, when, on which input, and who approved it.
- Cash application: matching incoming payments to open invoices and clearing them in the ERP.
- Order-to-cash: the process from customer order to cash received and applied.
Related guides
- How does Transformance integrate with SAP S/4HANA?
- How does Transformance integrate with Dynamics 365 F&O?
- What data does AR automation read from and write to the ERP?
- How do external systems post payments and clear open items?
- Who approves what when an AI agent works in your ERP?
- How AI agents work with SAP for accounts receivable
- How AI agents access ERP data safely
Frequently Asked Questions
Which ERP systems does Transformance integrate with?
Transformance integrates with SAP S/4HANA (on-premises, private cloud, public cloud), SAP ECC, NetSuite including OneWorld, Microsoft Dynamics 365 Finance & Operations and Business Central, and Odoo, all in production with customers, and supports Oracle and Infor. The connection method follows your environment: APIs, file/SFTP, middleware or the on-premises agent, plus RFC/BAPI, IDoc and SAP Cloud Connector for SAP and an Azure app registration for Microsoft.
Does Transformance need custom code or changes in SAP?
No. Transformance needs no custom ABAP and no modifications in your SAP system, on S/4HANA on-premises, private cloud or public cloud, or on SAP ECC.
How long does it take to connect Transformance to our ERP?
The ERP connection typically takes 2-3 days and your IT team may be involved; the full rollout takes 4-8 weeks, and a proof of value runs 4-5 weeks on one entity. Your IT team typically sets up the technical user, the network route and, for Microsoft ERPs, the Azure app registration.
Can Transformance work across several ERPs and legal entities?
Yes. Multiple SAP instances and company codes, NetSuite subsidiaries and Dynamics 365 legal entities consolidate in one Transformance environment, for groups from 250 to 2,000+ employees. Each entity’s ERP stays its system of record, and Vero sees each customer as one record across entities.
What payment volume is Transformance built for?
Transformance handles from under 1,000 to over 100,000 payments a month. ClearMatch reaches a 95% auto-match rate and runs end to end in under 8 minutes (Transformance customer data, 2026).
Can we connect the ERP for cash application only?
Yes. You can start with cash application alone and add deductions, AR collections and cash forecasting later.
What does an ERP integration with Transformance cost?
The cost depends on scope and the number of entities, so we size it with you in a call: Book a Call.
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.
