Key Takeaways
- Transformance connects to SAP S/4HANA on-premises, private cloud and public cloud with no custom ABAP and no modifications.
- It reads customers, open items, invoices, journal entries, bank statements and remittances, and writes clearings, journal entries and reversals back after approval.
- The connection typically takes 2-3 days and your IT team may be involved; a full rollout takes up to 4-8 weeks.
- ClearMatch reaches a 95% auto-match rate with 100% posting validation; nothing posts without human sign-off.
- Among 198 SAP user companies in the DACH region, 56% use S/4HANA on-premises, 17% private cloud and 5% public cloud (DSAG, 2026).
In This Article
- Key Takeaways
- How does Transformance integrate with SAP S/4HANA?
- Which SAP S/4HANA editions does Transformance support?
- How does the connection work in each edition?
- What does clean core mean for a Transformance connection?
- What does Transformance read from SAP S/4HANA?
- What does Transformance write back to SAP, and who approves it?
- How does Transformance handle several company codes or SAP instances?
- How long does it take to connect SAP S/4HANA to Transformance?
How does Transformance integrate with SAP S/4HANA?
Transformance connects to SAP S/4HANA from outside the SAP core, reads customers, open items, bank statements and remittances, and writes clearing postings and journal entries back after approval.
What Transformance reads from and writes back to SAP S/4HANA
Object names follow SAP’s standard documentation; your release and configuration decide the exact objects. The map for every ERP: what AR automation reads from and writes to the ERP.
SAP S/4HANA runs in production with Transformance customers today. Transformance also connects to SAP ECC, so a group that runs both generations connects both (SAP ECC integration). Every other ERP is on the ERP integrations overview.
SAP stays the system of record for the ledger, open items and clearing documents. Transformance reads, matches and proposes; a posting goes back into SAP only after a person approves. How an agent works inside FI-AR day to day: how AI agents work with SAP for accounts receivable.
One integration has to cover all three editions, because SAP customers run all three. Among 198 SAP user companies in Germany, Austria and Switzerland surveyed in December 2025 and January 2026, 56% use S/4HANA on-premises, 17% S/4HANA private cloud and 5% S/4HANA public cloud (DSAG, 2026; DACH, companies can run more than one system).
Which SAP S/4HANA editions does Transformance support?
Transformance connects to all three S/4HANA editions, on-premises, private cloud (S/4HANA Cloud Private Edition) and public cloud (S/4HANA Cloud Public Edition), with the same read and write scope on each.
SAP S/4HANA editions and the Transformance connection
SAP draws the line itself. In the public edition, “software updates run automatically and for all customers simultaneously”, while private cloud and on-premises allow “a more traditional (that is, customer specific) upgrade project”. The other two have the broader functional scope, and in the public edition “Modifications of SAP objects are not permitted” (SAP Learning, clean core extensibility course).
For Transformance, the edition changes only the connection route your SAP team can use. The objects read, the postings written back, the thresholds and the audit trail stay the same on all three.
How does the connection work in each edition?
The Transformance connection to SAP S/4HANA follows your environment: APIs, RFC/BAPI, IDoc, file or SFTP, middleware, SAP Cloud Connector or Transformance’s own on-premises agent.
Public cloud. In S/4HANA Cloud Public Edition, SAP sets up an API integration through three objects. The communication system holds “the technical connection details and the authentication method”; the communication user is a technical user “not intended for human authentication”; the communication arrangement “defines the specific inbound and outbound messages to be exchanged” (SAP Learning, public edition implementation course). That is SAP’s rule for every external system: in the public edition, an external system connects through a communication arrangement your administrator sets up, so what is exchanged is defined inside SAP. Which route applies to your public edition tenant is agreed with your SAP team in setup.
On-premises and private cloud. The wider option set applies: APIs, RFC/BAPI and IDoc, file or SFTP, and middleware. For a system inside your network, the link runs through SAP Cloud Connector or the Transformance on-premises agent. SAP’s Cloud Connector “acts as a reverse invoke proxy, eliminating the need to open inbound ports in the on-premise firewall” (SAP Learning, BTP security course).
Identity. Whatever the route, give Transformance its own technical user and authorisation role, never a person’s login, restricted to the company codes in scope. A posting written under that user then shows it in SAP as the one who entered it.
Security. Your data stays in your region, VPC deployment in your own cloud is available, access runs through SSO/SAML and role-based access control (RBAC), and a full audit trail records every step. No customer data is used to train models. More in how AI agents access ERP data safely and AR automation that keeps your data in your region.
The ERP connection typically takes 2-3 days; your IT team may be involved.
What does clean core mean for a Transformance connection?
For Transformance, clean core means no custom ABAP and no modifications in your SAP system: the connection sits outside the core and uses the interfaces your edition allows.
SAP grades extensions in four clean core levels (SAP News, 2025):
- Level A: “fully compliant extensions using only publicly released and stable SAP interfaces”.
- Level B: compliant extensions that also use “SAP’s classic APIs and technologies”.
- Level C: partially compliant extensions “allowing access to SAP internal objects”.
- Level D: extensions “not considered ‘clean’”, for example modifications or write access to SAP tables.
The practical result for your SAP team: nothing of Transformance sits in your SAP code. There is no add-on to install, no Z-program to maintain and no modification to carry through your next upgrade. Your regression tests cover the interface in use and the technical user’s role.
Postings stay SAP postings. When Transformance writes back an approved clearing, SAP books it like any other clearing: “A clearing transaction always creates a clearing document” (SAP Learning, financial accounting course). SAP’s own checks on posting periods, tolerances and authorisations apply to it.
What does Transformance read from SAP S/4HANA?
Transformance reads customer master data, open items, invoices, journal entries, bank statements and remittances from SAP S/4HANA, per company code, and also reads remittances that arrive outside SAP.
Customer master. In S/4HANA, the business partner is “a single point of entry to create, edit, and display master data”. Payment terms and the reconciliation account sit in the company code segment, and “Any company that wishes to do business with a specific business partner has to create a company code segment” (SAP Learning, financial accounting course).
Open items and invoices. In SAP’s words, “Open items, such as invoices that have not been paid, are incomplete transactions” (SAP Learning). Transformance reads open customer invoices and credit memos with amounts, due dates and payment terms.
Journal entries. They show what a payment, credit memo or adjustment has already touched before a new posting is proposed.
Bank statements. Transformance reads the electronic bank statement once SAP has imported it, whether it arrived as camt.053 or MT940.
Remittances. Payment advices, remittance emails, PDFs and portal exports often never reach SAP. DocSense reads them with over 97% extraction accuracy across 100+ document types and 170+ languages, with zero template configuration. How it works: how AI reads remittance advice and matches payments.
Vero, the Transformance agent, works on Customer 360, one graph per customer, so the payer’s open items, payment history, promises to pay and disputes sit in one place when an exception comes up. The same data feeds the cash forecast (cash flow forecasting from SAP, Oracle and NetSuite data).
What does Transformance write back to SAP, and who approves it?
Transformance writes clearing postings, journal entries and other ERP updates, including reversals, back to SAP S/4HANA, and each posting follows the approval thresholds your finance team sets.
Approvals. Transformance works in a multi-level approval model (read, recommend, execute, post) with a human in the loop for ERP postings. You set thresholds by amount, entity and customer; roles separate who configures rules (admins) from who approves postings (finance). More in who approves what when an AI agent works in your ERP.
ClearMatch reaches a 95% auto-match rate and runs end to end in under 8 minutes, with 100% posting validation. Nothing posts without human sign-off.
Exceptions. For a payment with no usable reference or a short payment, Vero investigates from Customer 360 and fetches internal and external information to find more matches, then proposes the clearing with its evidence. A person approves, and the posting follows your thresholds.
What SAP does with a payment difference. SAP checks it against “the tolerance groups of the employee and the customer or vendor”. Within tolerance, “the difference is automatically posted as either cash discount adjustment or unauthorized deduction”. Otherwise, “the difference is processed manually”: as a partial payment, a residual item (a new document number referencing the originals), a posting to another account through reason codes, or a write-off (SAP Learning, financial accounting course).
Illustrative example (amounts fictional): your tolerance allows differences up to EUR 20. A payment of EUR 11,985.00 on a EUR 12,000.00 invoice leaves EUR 15.00, inside tolerance, so SAP posts the gap automatically. A payment of EUR 11,400.00 leaves EUR 600.00, outside: as a partial payment, “All the documents remain in the account as open items”; as a residual item, the invoice clears and “Only the residual item remains”, for EUR 600.00. Because SAP checks the employee’s tolerance group too, agree which group the Transformance technical user carries.
What a live connection meets. SAP’s controls stay in force, and each is a rule to plan for:
- SAP does not accept a posting into a closed posting period; the period has to be opened first (SAP Learning, posting periods).
- An open item that another user is processing at that moment is locked against parallel changes, so plan for a retry.
- Clearing open items in a foreign currency creates automatic postings for exchange rate differences, per your SAP configuration (SAP Learning).
- To correct a cleared payment, SAP’s sequence is to reset the cleared items, reverse the document, then re-enter it correctly (same SAP Learning lesson).
Agree with us in setup which checks run before a posting reaches SAP. The full flow: how external systems post payments and clear open items.
Audit trail. The audit trail stores the timestamp, what the system did, what the user did, who approved, the input and the confidence. Reversals and the full log: what an AI agent’s audit trail in finance records.
How does Transformance handle several company codes or SAP instances?
Several SAP instances and company codes consolidate in one Transformance environment, and SAP still clears each open item in the company code that owns it.
For a group, that changes three settings:
- Read access per company code. Scope the technical user to the company codes in each rollout wave, and widen it wave by wave.
- Thresholds per entity. A EUR 50,000 clearing may sit below the threshold in a large sales company and above it in a small one; set thresholds per entity, not group-wide.
- Approvers per company code. Where local finance teams sign off, keep one approver list per company code.
A customer buying from several of your entities is one business partner with several company code segments in SAP, and one graph in Customer 360, so its payment history sits together across entities.
A group on S/4HANA in some countries and SAP ECC in others connects both; both run in production with Transformance customers (SAP ECC integration, multi-entity order-to-cash).
How long does it take to connect SAP S/4HANA to Transformance?
The S/4HANA connection typically takes 2-3 days, and your IT team may be involved; proof of value takes 4-5 weeks on one entity, full rollout up to 4-8 weeks.
Connecting SAP S/4HANA to Transformance in seven steps:
- Name an SAP owner on your side and pick the first company codes in scope.
- Confirm your edition and release, and agree the connection route with your SAP and IT team.
- Create a dedicated technical user and role for Transformance, scoped to those company codes (in the public edition, SAP’s own model is a communication user and a communication arrangement set up by your administrator).
- Start read-only: customer master, open items, bank statements. Check counts and balances against SAP.
- Set approval thresholds by amount, entity and customer, and separate who configures rules from who approves postings.
- Test write-back in your test or quality system: a clearing posting, a journal entry and a reversal, each checked in SAP.
- Go live per company code, then add further company codes or SAP instances.
Your SAP basis team creates the technical user and the connection, finance sets thresholds and approvers, and Transformance configures matching and approvals. Week by week: how long AR automation implementation takes.
Who Transformance is for
- ERPs: SAP S/4HANA on-premises, private or public cloud, plus SAP ECC, NetSuite, Microsoft Dynamics 365 Finance & Operations and Business Central, and Odoo in production; 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 integration, three editions, SAP stays the ledger
Transformance connects to every S/4HANA edition without custom ABAP, reads what AR needs and posts back only what a person has approved, after typically 2-3 days of connection work.
Your edition decides the route, your thresholds decide what posts, and SAP keeps the ledger. Book a Call to map your company codes and route with us.
Key terms
- SAP S/4HANA: SAP’s current ERP suite, run on-premises, in a private cloud or in the public cloud.
- Remittance advice: the customer’s note listing which invoices a payment covers.
- camt.053: the ISO 20022 end-of-day bank statement format that SAP imports as an electronic bank statement.
- Journal entry: an accounting document with balanced debit and credit lines.
- Audit trail: the record of who or what did which step, when, and who approved it.
Related guides
- Which ERP systems does Transformance integrate with?
- How does Transformance integrate with SAP ECC?
- 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?
- What does an AI agent’s audit trail in finance record?
- How AI agents work with SAP for accounts receivable
- How AI agents access ERP data safely
Frequently Asked Questions
Does Transformance work with SAP S/4HANA Cloud Public Edition?
Yes, Transformance connects to SAP S/4HANA Cloud Public Edition as well as private cloud and on-premises, through the interfaces each edition allows and with no custom ABAP. In SAP’s public edition, every external system connects through a communication arrangement your administrator sets up.
Does a third-party cash application tool need custom ABAP in SAP S/4HANA?
No, Transformance needs no custom ABAP and no modifications in your SAP system; it connects from outside the core with a dedicated technical user and the route your SAP team chooses.
How long does it take to connect SAP S/4HANA to Transformance?
The SAP S/4HANA connection typically takes 2-3 days and your IT team may be involved. A proof of value takes 4-5 weeks on one entity, and a full rollout up to 4-8 weeks.
Can Transformance work across several SAP company codes or instances?
Yes, several SAP S/4HANA or ECC instances and company codes consolidate in one Transformance environment, with approval thresholds set per entity.
Which company sizes and payment volumes is Transformance built for on SAP?
Transformance is built for mid-market to large enterprises with 250 to 2,000+ employees and from under 1,000 to over 100,000 payments a month, including groups with several entities and shared service centres.
What does a Transformance integration with SAP S/4HANA cost?
The cost depends on your scope and the number of entities and company codes in scope, so we quote it after a short call. Book a Call to walk through your SAP setup.
Does Transformance use our SAP data to train AI models?
No, Transformance does not use customer data to train models. Your data stays in your region, with VPC deployment in your own cloud available.
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.
