Key Takeaways
- Transformance’s integrations hub is an agent-run integration platform for finance: agents prepare six steps (discover, map, build, test, schedule, monitor), and a person approves every change that reaches a customer system or production.
- The integration agents are live today: they read system documentation and setup answers, propose field mappings, draft workflows, run the test plan and report, and draft plain-language failure explanations.
- Transformance builds, runs, monitors and fixes the connections; your team approves access and production changes.
- If a system has an API, a database, a file drop or a mailbox, it can be connected, including systems behind the firewall through an on-premise agent that connects outward only.
- An ERP connection typically takes 2-3 days and your IT team may be involved; full rollout takes up to 4-8 weeks (Transformance customer data, 2026).
In This Article
- Key Takeaways
- What is an agent-run integration platform for finance?
- What does the integrations hub give you today?
- How does the standardized integration process run, step by step?
- iPaaS, prebuilt connectors or a vendor-run hub: which fits finance?
- How does it reach systems behind the firewall?
- What does a person approve, and what is logged?
- Which systems does it connect?
What is an agent-run integration platform for finance?
A platform where Transformance builds, tests and runs your ERP, bank and mailbox connections; its agents prepare each step, and a person approves every change reaching your systems or production.
The standardized integration process: what happens, what the agent does, what a person approves
“Agent-run” describes how the hub works, not a level of autonomy. Transformance’s integration agents do the repeatable preparation that used to fill an integration project: reading API descriptions and file specifications, drafting the steps, running the same tests every time. They propose and prepare; a person decides.
A general-purpose integration tool connects anything to anything and leaves the finance logic to whoever builds the flow. The integrations hub is made for finance data, so its approvals, audit trail and monitor answer a controller’s questions: which open items came across, which postings went back, which run failed and who owns it.
Takeaway: the agents do the repeatable work; people own the decisions.
What does the integrations hub give you today?
A visual workflow builder and an API workbench in one place, with custom code steps, schedules, webhooks, a secrets vault, a full run history and a monitor finance can read.
- A drag-and-drop canvas shows how data moves: pull open items, transform them, load them, confirm the posting.
- Reusable steps: an API request, database query or custom function is saved once and used in many workflows.
- Testing in place: run one step or the whole workflow, and re-run from the step that failed instead of starting over.
- Triggers: schedules in any time zone (daily, at month end, any pattern), webhooks and on-demand runs.
- A secrets vault: credentials are referenced by name and never appear in workflows, logs or exports.
- Per-customer separation of workflows, secrets, settings and runs.
- A full run history: trigger, timing, inputs, outputs and every step’s result.
- The Integration Monitor: when each job last ran and last succeeded, and a plain-language exception queue.
Analysts build visually; developers add a Python or JavaScript step where a transformation needs it.
The hub works with the onboarding hub: during onboarding, the needed connections are tracked, credentials are collected through secure slots instead of email, and integrations are tested on your own transactions in staging. Vero, Transformance’s AI agent, uses the same hub, so its actions that touch outside systems share the same security, logging and retry behavior.
Takeaway: builder, workbench, vault, run history and monitor live in one place instead of across scripts, servers and inboxes.
How does the standardized integration process run, step by step?
Six steps, the same for every system: discover, map, build, test, schedule and monitor. Agents prepare each step, and a person approves before anything reaches your systems or production.
1. Discover. What does the system offer (API, database, file drop or mailbox), and in which environments? The agent reads the documentation and your setup answers and lists the options; your IT team confirms access. For an ERP it helps to settle early which entities, posting periods and currencies are in scope, because they decide what a sync may write.
2. Map. Which source field fills which target field, with rules and constants such as entity codes and mailbox addresses. The agent proposes the mapping from documentation and sample data; the finance owner confirms it. Finance knowledge matters most here: where a bank reference goes, how a residual item is posted, which lockbox field carries the customer number.
3. Build. The agent drafts the workflow on the canvas from reusable steps, with custom code only where a step needs it. A named reviewer approves it before activation.
4. Test. The agent runs the test plan in the test environment, from the connection to a forced failure and its retry, and reports each result. Named people from finance and IT sign off. The plan, test by test: how AI agents build and test an ERP integration.
5. Schedule. The trigger is set: daily, at month end or on a webhook. Environment-aware settings point the same workflow at the test or the production system. A person activates the production run.
6. Monitor. Every run reports to the Integration Monitor. When a run fails, the agent drafts the plain-language explanation and the owner decides about the retry or the fix. When only some records fail, the monitor lists each one, so only those are re-run.
Illustrative example (names and figures fictional). At 6:00 the bank statement for one house bank is missing. The exception queue does not show a log line; it shows: “Statement file for the operating account of entity US01 did not arrive by 6:00. Cash application for US01 waits for it. Owner: treasury.” Later, a clearing run reports 3 of 214 postings rejected because the period is closed in the ERP; the explanation names the three items, and the AR lead decides to post them in the next open period.
For the posting-level log, see the audit trail for agent postings and reversals.
Takeaway: every step has an agent preparing it and a named person approving it.
iPaaS, prebuilt connectors or a vendor-run hub: which fits finance?
A connector fits one standard link; an iPaaS fits an IT team that builds many integrations itself; a vendor-run hub fits finance teams that want connections built, run and fixed.
In plain words:
- iPaaS (integration platform as a service): a vendor-run cloud service in which your own team builds integrations between applications. The platform is the vendor’s; the integrations, monitoring and fixes are yours.
- Prebuilt connector: a ready-made link between two named systems for a fixed set of data.
- Integration middleware: the older, often self-hosted layer that routes and transforms data between systems.
The real decision is who builds, who maintains and who fixes a failed sync.
Three ways to run integrations for finance: who builds, who maintains, who fixes
Each row is right for someone. The hub row gives finance one place and one accountable owner for the order-to-cash data flows.
Hybrid setups are normal: a group iPaaS or middleware layer can feed the hub, and SAP teams can keep their own SAP middleware route (connecting through SAP middleware).
Questions to ask of any approach:
- Does it write back to the ERP as well as read?
- Which ERP versions, entities and currencies does it cover?
- Who gets the alert when a sync fails?
- Can a failed record be re-run on its own?
- What is the exit route?
Takeaway: choose by who fixes a failed sync at 6:00, not by the length of a connector list.
How does it reach systems behind the firewall?
A lightweight on-premise agent runs inside your network and connects outward only: no inbound firewall change, no VPN, and credentials for on-premise systems stay on site.
The on-premise agent runs end to end today. It reaches what the cloud cannot see: an on-premise ERP, a database server, a file share or an internal API. Every on-premise action is labeled read, write or execute, so IT approves exactly what a workflow may do; actions cover SAP services and function modules, database queries, file reads and writes, internal APIs and existing automation scripts.
Where a legacy screen has no other route, robotic process automation closes the gap: Transformance runs your existing scripts as a workflow step and builds new bots where needed. More routes for older systems: connecting AR automation to a custom or legacy ERP.
Your IT team approves the agent installation and the actions it may run; the ERP connection typically takes 2-3 days (Transformance customer data, 2026), and your IT team may be involved. The IT task list is in what IT does in an AR automation rollout; connection options per ERP are in which ERP systems Transformance integrates with.
Takeaway: outbound only, credentials on site, every action labeled for IT approval.
What does a person approve, and what is logged?
A person approves every change that reaches a customer system or production, and every run and every change is recorded with who did what and when.
A person approves the field mapping, the activation of a workflow, the production schedule and every write action to a customer system. Roles separate who configures (administrators) from who approves (finance). Postings follow the 4-level approval model (read, recommend, execute, post) with a human in the loop for ERP postings, and thresholds are set by amount, entity and customer (approval thresholds for AI agents).
The control design follows a neutral frame. OWASP’s guidance on excessive agency recommends human approval for high-impact actions before they are taken, and limiting an agent’s permissions on other systems to the minimum necessary (OWASP Gen AI Security Project, LLM06:2025 Excessive Agency, 2025). The hub maps to it: minimal permissions per workflow, labeled on-premise actions, a person approving every change.
What is recorded:
- Runs: trigger, timing, inputs, outputs and every step’s result.
- Changes: who created and last changed each workflow and building block, and when.
- Postings: timestamp, what the system did, what the user did, who approved, the input and the confidence.
Data is hosted in your region, and no customer data is used to train models (AR automation that keeps your data in your region). For access control, see how AI agents access ERP data safely.
Takeaway: agents prepare, people approve, and the log shows both.
Which systems does it connect?
If a system has an API, a database, a file drop or a mailbox, it can be connected; the route, from REST API to MCP server, follows your environment.
Workflows in use today, by system class
SAP S/4HANA, SAP ECC, NetSuite, Microsoft Dynamics 365 Finance & Operations and Business Central, and Odoo run in production with customers; Oracle and Infor are supported. Routes: API (REST and SOAP), OData, RFC and BAPI, the ERP’s own MCP server where one exists, files, database, mailbox, the on-premise agent and RPA. Vero connects to customer ERPs through the ERP’s MCP server or its API, in production today.
Write-back runs through the ERP’s own interfaces (API, OData, BAPI or MCP); direct database writes happen only where you explicitly agree (what AR automation reads and writes in your ERP).
Entities on different ERPs, for example SAP, NetSuite and Dynamics, run in one Transformance environment with one worklist and one forecast across cash application, deductions, AR collections and cash forecasting (multi-ERP finance automation). A production ERP connection typically takes 2-3 days (Transformance customer data, 2026); for a custom system, the timeline is agreed after the feasibility check.
Takeaway: any system with an API, a database, a file drop or a mailbox can be connected, and one environment holds every entity.
Who Transformance is for
- ERPs: SAP S/4HANA (on-premises, private or public cloud) and SAP ECC, NetSuite (including OneWorld subsidiaries), Microsoft Dynamics 365 Finance & Operations and Business Central, and Odoo in production with customers; Oracle and Infor supported; connected through APIs, files and SFTP, middleware or our on-premise agent, whichever your environment needs.
- Size: mid-market to large enterprise, 250 to 2,000+ employees, including groups with several entities and shared service centers.
- 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 process for every connection, a person on every change
An agent-run integration platform replaces one-off integration projects with one standardized process. Transformance’s agents read the documentation, propose mappings, draft workflows, run the tests and explain failures; Transformance builds, runs, monitors and fixes the connections; a person on your side approves every change that reaches your systems or production. Transformance works with customers across Europe, the United States and Australasia. Book a Call to walk through your systems and the first connection.
Key terms
- Robotic process automation (RPA): software bots that operate an application’s screens like a user, where no other route exists.
- Audit trail: the record of who did what, when and with which input.
- Payment reconciliation: matching received payments to the invoices and bank lines they belong to.
Related guides
- Which ERP systems does Transformance integrate with?
- How do AI agents build and test an ERP integration?
- Can AR automation connect to a custom or legacy ERP?
- What does IT need to do when you roll out AR automation?
- How do you automate finance when every entity runs a different ERP?
- How AI agents access ERP data safely
Frequently Asked Questions
Is an agent-run integration platform the same as an iPaaS?
No. An iPaaS is a general-purpose service your own team uses to build and run integrations; Transformance’s integrations hub is made for finance data and run by Transformance, with approvals, an audit trail and an exception queue.
Are the integration agents available today?
Yes. They read system documentation and setup answers, propose field mappings, draft workflows, run the test plan and report, and draft plain-language failure explanations. A person approves every change that reaches a customer system or production.
Does it replace our IT team?
No. Your IT team approves access, the on-premise agent and what each action may do. The ERP connection typically takes 2-3 days and your IT team may be involved; full rollout takes up to 4-8 weeks, and a proof of value runs 4-5 weeks on one entity (Transformance customer data, 2026).
Which ERPs and editions does it connect to?
SAP S/4HANA (on-premises, private and public cloud), SAP ECC, NetSuite, Microsoft Dynamics 365 Finance & Operations and Business Central, and Odoo run in production with customers; Oracle and Infor are supported.
Can it connect to systems behind our firewall?
Yes, through a lightweight on-premise agent that connects outward only, so no inbound firewall change or VPN is needed and credentials stay on your site.
Does it work for a group with many entities, several ERPs and 100,000 payments a month?
Yes. Transformance is built for mid-market to large enterprise groups, from under 1,000 to over 100,000 payments a month, and entities on different ERPs run in one environment with one worklist and one forecast.
What does it cost?
It depends on scope and on the number of entities and systems. Book a Call and we size it with you.
SAP, SAP S/4HANA, SAP ECC, Microsoft, Microsoft 365, SharePoint, OneDrive, Dynamics 365, Business Central, Oracle, NetSuite, Odoo, Infor, Stripe and Zendesk are trademarks of their respective owners. Transformance is not affiliated with or endorsed by them.
