Key Takeaways
- Transformance’s AI agents connect to an on-premise ERP through an interface its vendor already documents: Business Central on-premises, for example, serves OData on port 7048 by default once an administrator enables it (Microsoft Learn, 2026).
- Outbound-only access is an established pattern: Microsoft’s on-premises data gateway “requires no inbound ports to your network” (Microsoft Learn, 2026).
- Transformance’s on-premise agent connects outward only: no inbound firewall change, and passwords for the ERP stay inside your network.
- ClearMatch reaches a 95% auto-match rate and runs end to end in under 8 minutes; nothing posts without human sign-off (Transformance customer data, 2026).
- Matching, approvals and the audit trail work the same on premise and in a cloud-hosted ERP; only the connection differs.
In This Article
- Key Takeaways
- How does AR automation work with an on-premise ERP?
- What does an on-premise ERP already do in order-to-cash?
- What stays inside your network and what crosses it?
- How does the connection get made, step by step?
- What changes between an on-premise and a cloud-hosted ERP, and what does not?
- What does a worked example look like?
- Where do you start with an on-premise ERP?
How does AR automation work with an on-premise ERP?
Transformance’s AI agents use an interface the ERP already documents, connecting outward from inside your network; the ERP stays the ledger and a person approves every posting.
Seven on-premise ERPs: the interface the vendor documents, the routes the integrations hub offers, and what to agree with your ERP team
Sources for the left column: SAP Learning; Microsoft Learn for Business Central (2026), Dynamics NAV 2018, Dynamics GP and Dynamics AX 2012; Oracle for E-Business Suite Integrated SOA Gateway and JD Edwards Orchestrator. The route follows your environment; the table is not a ranking.
“On premise” describes where the ERP runs, not how good it is. Many companies run their ERP on their own servers by choice: for control, for regulated data, or for years of tailoring to how the business works.
This page covers standard on-premise ERP systems. For a home-grown system or one not on any list, see connecting AR automation to a custom ERP; the IT task list is on what IT needs to do in a rollout, and SAP R/3 and ECC have their own page. Every ERP and its status: the ERP integrations overview.
The interface decides how data arrives; what happens next does not depend on where the ERP runs. ClearMatch reaches a 95% auto-match rate and runs end to end in under 8 minutes, and nothing posts without human sign-off (Transformance customer data, 2026).
Takeaway: the ERP’s own documented interface is the door; the agent inside your network opens it from your side.
What does an on-premise ERP already do in order-to-cash?
Each ERP documents its own functions for importing bank data and applying payments by rules; agents build on these and take the payments, remittances and follow-ups that need judgement.
Three examples, each from the vendor’s own documentation:
- Business Central applies payments to open entries in the Payment Reconciliation Journal “based on a matching of data on a bank statement line (journal line) with data on one or more open entries”, by rules you define on the Payment Application Rules page. Each suggestion carries a Match Confidence of Low, Medium or High (Microsoft Learn, 2025). Teams add agents for the lines the rules set for review.
- Oracle E-Business Suite runs AutoLockbox as “a three step process”: import, validation and Post QuickCash. Where the matching rules do not apply, Post QuickCash applies the receipt with the AutoCash rule set, and a receipt the AutoCash rules cannot apply is assigned the status Unapplied (Oracle Receivables User Guide 12.2). Teams add agents for the Unapplied receipts.
- SAP, in its electronic bank statement documentation, reads the note to payee fields with an interpretation algorithm that “determines how the information in the note to payee fields is to be interpreted by the system”. A document is found when the reference arrives “in exactly the same form and with exactly the same number of characters” as it is stored (SAP Help Portal). Teams add agents for references that arrive in another form.
On top of that base, agents take the AR work around any ERP:
- Reading remittance advice in any format: emails, PDFs, spreadsheets.
- Proposing matches, with evidence, for partial, wrong or missing references.
- Classifying short pays and deductions.
- Prioritizing AR collections and calling customers about overdue invoices.
- Forecasting cash from open items and payment behavior.
When a payment stays open, Vero, the Transformance agent, investigates it from Customer 360, its working memory for each customer, and fetches further internal and external information to find more matches. It proposes the match with the evidence; a person approves, changes or rejects it. Which payments suit rules and which suit an agent: rule-based vs AI cash application.
CollectPulse actions 100% of overdue invoices within 24 hours, and ClaimIQ reaches 97% deduction identification accuracy (Transformance customer data, 2026).
Takeaway: the ERP’s rules stay in place; agents take the exceptions the rules hand on.
What stays inside your network and what crosses it?
Credentials and the connection stay inside your network; open items and customer data travel outward to a platform hosted in your region, and approved postings come back.
The data-boundary ledger: what runs inside your network, what crosses it, and who controls it
Data does leave your network, outward and by design; the password to your ERP never does.
A lightweight agent is installed on a host inside your network. It connects outward only, so no inbound ports are opened and no VPN is needed. Passwords for on-premise systems are entered and stored inside your network and never sent to the cloud. Every action the agent can take is labeled read, write or execute, so IT approves exactly what a workflow may do.
The pattern is established. Microsoft’s on-premises data gateway “initiates outbound connections to the cloud, but requires no inbound connections” (Microsoft Learn, 2026). SAP’s Cloud Connector “acts as a reverse invoke proxy, eliminating the need to open inbound ports in the on-premise firewall” (SAP Learning); for SAP it is one of the options, and the method follows your environment.
What crosses the boundary is hosted in your own region, US customers in the US and EU customers in the EU, with VPC deployment in your own cloud available (data in your region). No customer data is used to train models. Reads and post-backs run on the schedule you agree, for example hourly or daily.
The firewall claim is precise: no inbound firewall change. IT still approves the agent host, the one outbound destination and the action list. More depth: technical user and least privilege, the full field map and how the clearing posting comes back.
Takeaway: your data travels outward to your region; your ERP password stays home.
How does the connection get made, step by step?
Your ERP team and ours choose the route, install the agent inside your network, connect the test system, test on your own transactions, run in parallel, then go live.
- Route. Pick the interface from the table with your ERP team: API, file, database or the on-premise agent. For a system outside the table, see connecting a custom ERP.
- Host and rules. IT installs the agent on a host inside the network, allows one outbound destination and approves the action list (IT tasks in a rollout).
- Credentials. The technical user’s password goes into the agent on site; other credentials go into secure slots in the onboarding hub, never by email.
- Test system first. The same workflow points at a test or a production system by a setting.
- Your own transactions. Test scenarios run on your own transactions in staging, then a parallel run sits next to your current process.
- Sign-off. Go-live follows an acceptance report, and a person approves everything that reaches production (onboarding, kickoff to go-live).
The onboarding hub guides the connection setup with your IT team in the loop. After go-live, a monitor explains each failed record in plain language, with a retry. Inside the integrations hub, AI agents run the standardized integration process (discover, map, build, test, schedule, monitor), and a person approves every change that reaches your system (an agent-run integration platform).
For SAP S/4HANA, SAP ECC, Business Central and Oracle E-Business Suite, the ERP connection typically takes 2-3 days, and your IT team may be involved. For the other ERPs in the table, the connection is planned inside the full rollout of up to 4-8 weeks. A proof of value runs in 4-5 weeks on one entity (implementation time).
Takeaway: test system first, your own transactions second, production last, with a person’s sign-off at each gate.
What changes between an on-premise and a cloud-hosted ERP, and what does not?
Only the connection changes: the agent, the route and the credentials sit on your side for an on-premise ERP, while matching, approvals, thresholds and the audit trail work the same.
The approval model and its thresholds: who approves what when an AI agent works in your ERP. The audit log records the timestamp, what the system did, what the user did, who approved, the input and the confidence (audit trail and reversals).
If you later change ERP or deployment, the approval rules and AR collections cadences you set up stay in the platform; the connection is set up again for the new system. SAP teams weighing timing can read automating AR before or after the S/4HANA migration.
Takeaway: where the ERP runs changes the connection, not the controls.
What does a worked example look like?
A manufacturer with 900 employees and 6,000 customer payments a month, ERP on premise, would leave about 300 payments a month for a person at a 95% auto-match rate.
The inputs are illustrative assumptions you replace with your own; only the 95% is a Transformance figure (Transformance customer data, 2026).
- Payments a month: 6,000 (assumption).
- Auto-matched at 95%: 6,000 x 0.95 = 5,700 payments proposed with evidence.
- Left for a person: 6,000 minus 5,700 = 300 payments, each with Vero’s investigation attached.
The 5,700 still post only after sign-off, within your thresholds. Results depend on your data (remittance quality, payer mix, how references arrive); a proof of value on one entity shows your real number.
Takeaway: at 6,000 payments a month, the work moves from 6,000 lines by hand to about 300 reviewed exceptions.
Where do you start with an on-premise ERP?
Start with the scope that matters most, cash application alone or the full order-to-cash, and a short call on your ERP, its version and the route your IT team prefers.
Bring the ERP and version, the interfaces your team already uses and your monthly payment volume; for an ERP outside the table, feasibility is checked on sample records first. Book a Call to map your route.
Takeaway: the first conversation is about your interface, not about changing your ERP.
Who Transformance is for
- ERPs: SAP S/4HANA (on-premises, private or public cloud), SAP ECC, NetSuite (including OneWorld subsidiaries), Microsoft Dynamics 365 Finance & Operations and Business Central, and Odoo run in production with customers; Oracle and Infor are supported; other on-premise ERPs (and other ERPs) connect through our integrations hub.
- 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: keep the ERP where it runs, agree what crosses the line
An on-premise ERP needs two things from AR automation: a door its vendor already documents, and a clear ledger of what crosses your network boundary. With an outbound-only agent, credentials on site and a person approving every posting, cash application and AR collections run on top of the ERP you chose.
Key terms
- Cash application: matching incoming payments to open invoices and posting the clearing.
- Order-to-cash: the process from customer order to cash received.
- Remittance advice: the customer’s note of which invoices a payment covers.
- Lockbox: a bank service that collects customer payments and sends the payment data.
- Audit trail: the record of who or what did what, and when.
- SAP S/4HANA: SAP’s current ERP suite, run on premises or in the cloud.
Related guides
- Which ERP systems does Transformance integrate with?
- Can AR automation connect to a custom ERP?
- What does IT need to do when you roll out AR automation?
- How can AI agents help Dynamics NAV, GP and AX teams with AR?
- How can AI agents help JD Edwards teams automate AR?
- How can AI agents help Oracle E-Business Suite teams with AR?
- How do AI agents access your ERP and customer data safely?
Frequently Asked Questions
Does AR automation work with an on-premise ERP?
Yes: AI agents connect through an interface the ERP already offers (an API, a file or an approved database route), carried outward by an agent inside your network. The ERP stays your ledger.
Do we have to open our firewall?
No inbound firewall change is needed, because the agent inside your network opens the connection outward. Your IT team still approves the agent host, the one outbound destination and the actions the agent may take.
Does our data leave our network?
Open items, invoices and customer master data travel outward to a platform hosted in your own region, with VPC deployment in your cloud available. Passwords for your ERP stay on site, and no customer data is used to train models.
Which on-premise ERPs does Transformance work with?
SAP S/4HANA (on-premises) and SAP ECC run in production with customers, and Transformance connects to Business Central, Oracle E-Business Suite, JD Edwards, Dynamics NAV, GP and AX and other ERPs through its integrations hub. For a system outside this list, feasibility is checked on sample records first.
Is Transformance built for our size and payment volume?
Transformance is built for companies with 250 to 2,000+ employees and from under 1,000 to over 100,000 payments a month.
How long does the connection take and what does it cost?
For SAP S/4HANA, SAP ECC, Business Central and Oracle E-Business Suite, the ERP connection typically takes 2-3 days, and your IT team may be involved; the full rollout takes up to 4-8 weeks. The cost depends on scope and the number of entities, so Book a Call for a quote.
Do we have to move to a cloud ERP first?
No: Transformance connects to the ERP you run today. If your ERP or deployment changes later, the approval rules and AR collections cadences you set up stay in the platform, and the connection is set up again for the new system.
SAP, SAP S/4HANA, Microsoft, Dynamics 365, Business Central, Oracle, NetSuite, Odoo, Infor, Dynamics NAV, Dynamics GP, Dynamics AX, JD Edwards and Oracle E-Business Suite 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.
