Key Takeaways
- Transformance connects to SAP ECC, in production with customers today, with no custom ABAP and no modifications.
- It reads customer master data, open items, invoices, journal entries, bank statements and remittances, and writes clearings, journal entries and reversals back only after a person approves.
- The ERP connection typically takes 2-3 days and your IT team may be involved; a full rollout takes up to 4-8 weeks.
- In S/4HANA, the customer open item tables survive only as read-only views and customers become business partners (SAP conversion guide).
- Your setup carries over to S/4HANA with remapping, and 54% of DACH SAP user companies still run ECC or the older Business Suite (DSAG, 2026).
In This Article
- Key Takeaways
- How does Transformance integrate with SAP ECC?
- Which SAP ECC data does Transformance read?
- What does Transformance write back to SAP ECC?
- How does the connection to SAP ECC work, and how long does it take?
- How does Transformance handle several company codes and ECC instances?
- What changes in SAP when you move from ECC to S/4HANA?
- What carries over from your Transformance setup to S/4HANA?
- Should you connect SAP ECC now or wait for S/4HANA?
How does Transformance integrate with SAP ECC?
Transformance connects to SAP ECC through RFC/BAPI, IDoc, file transfer, middleware or its own on-premises agent, reads FI-AR data and writes clearing postings back only after approval.
What Transformance reads from and writes back to SAP ECC
ECC object names show where ECC stores the data; the objects a given connection uses depend on the method and your system. Confirm with your SAP team. The same map for every ERP: what AR automation reads from and writes to the ERP.
An SAP ECC integration is the connection that lets an AR system read FI-AR data per company code and hand approved postings back to ECC, where they clear like any other FI document.
SAP ECC runs in production with Transformance customers today, alongside SAP S/4HANA, NetSuite, Microsoft Dynamics 365 and Odoo. Nothing of Transformance is installed inside ECC: no custom ABAP, no modifications, no add-on to carry through your next support package.
ECC is still where many groups book their receivables. Among 198 SAP user companies in Germany, Austria and Switzerland surveyed from December 2025 to January 2026, 54% run SAP ECC or the older Business Suite, down from 68% in 2024 (DSAG, 2026; DACH, companies can run more than one system). Every other ERP: ERP integrations overview.
Which SAP ECC data does Transformance read?
Transformance reads customer master data, open items, invoices, journal entries, bank statements and remittances from SAP ECC, per company code, plus the remittances that never reach ECC.
How ECC stores it. Payment terms and the reconciliation account sit in the company code data (KNB1); every FI posting is a header (BKPF) with line items (BSEG), and BSID indexes the open customer items. Bank statements arrive as MT940, camt.053 or, in the US, lockbox files, are imported with FF_5 and post-processed in FEBAN.
What ECC does with the note to payee. The interpretation algorithm “determines how the SAP System interprets the information in the note to payee lines”, and ECC uses it to clear open items automatically: algorithm 001 reads a document or reference number, 011 a check number (SAP Help Portal, FI glossary, R/3 4.70 release, an older SAP page). A bank line that says only “see remittance” finds no document number and waits for post-processing in FEBAN.
What lives outside ECC. The remittance PDF, the email listing 40 invoices and the AP portal download never reach the bank statement. DocSense reads remittances in any format with over 97% extraction accuracy across 100+ document types and 170+ languages, with zero template configuration (how AI reads remittance advice).
What Vero adds. Vero, the Transformance agent, works on Customer 360, one graph per customer, so the open items of every company code, last week’s promise to pay and earlier short pays sit next to the payment. For an exception, Vero investigates from Customer 360, fetches internal and external information to find more matches, and proposes the clearing with its evidence. A person approves.
What does Transformance write back to SAP ECC?
Transformance writes clearing postings, journal entries and other ERP updates, including reversals, back to SAP ECC, and each posting waits for the approver your thresholds name.
Clearing. “A clearing transaction always creates a clearing document” (SAP Learning, financial accounting course), and its number sits on every cleared item, so your auditor can trace a payment from bank line to invoice.
Approvals. ClearMatch validates 100% of postings, and nothing posts without human sign-off. The approval model has four levels (read, recommend, execute, post) with a human in the loop for ERP postings. Thresholds go by amount, entity and customer; admins configure rules, finance approves (who approves what when an AI agent works in your ERP).
Short pays are a configuration decision. Illustrative case (amounts fictional): a EUR 10,000.00 invoice, a EUR 9,820.00 payment, a EUR 180.00 short pay. Your SAP team decides which of three ECC treatments applies to which reason:
- Residual item: the invoice clears and a new EUR 180.00 open item is created, optionally with a reason code.
- Partial payment: the payment posts against the invoice, which stays open.
- Payment on account: the money sits on the customer account without clearing an item (on-account cash).
With a payment advice note, ECC calculates residual items automatically; without sub-items or a reason code, it splits the difference into up to three residual items: gross amount, cash discount and other (SAP Help Portal, R/3 4.6C release, an older SAP page). More: automating partial payments and deductions.
Reversals. Transformance can post reversals back to ECC. SAP’s sequence for a wrong clearing is to “reset the cleared items, reverse the document, and re-enter the original posting correctly” (SAP Learning); in ECC, FBRA, then FB08. The audit side: what an AI agent’s audit trail in finance records.
What a live connection meets. SAP’s controls stay in force on every posting:
- Closed period. SAP closes periods “To prevent documents from being posted to an incorrect posting period” (SAP Learning); ECC manages them in
OB52. A clearing with a 31 October posting date cannot post once October is closed. - Blocked or locked. A posting block on the customer account, or an item another user is processing, stops the posting until released.
- Currency difference. A USD invoice paid at another exchange rate leaves a difference that SAP posts automatically on clearing, per your configuration (SAP Learning).
Agree in setup which checks run before a posting reaches ECC and who takes a case ECC rejects. The full flow: how external systems post payments and clear open items; the SAP side: SAP cash application, a complete guide.
How does the connection to SAP ECC work, and how long does it take?
The SAP ECC connection typically takes 2-3 days, and your IT team may be involved; a full Transformance rollout takes up to 4-8 weeks.
Connection options. APIs, RFC/BAPI and IDoc, file/SFTP, middleware, SAP Cloud Connector or the Transformance on-premises agent; the method follows your environment. In SAP’s definition, “SAP business objects are accessed through BAPIs (Business Application Programming Interfaces), which are stable, standardized methods” (SAP Help Portal, BAPI user guide, R/3 4.6C release).
What your SAP and IT team decides. The method; a dedicated technical user for the integration (never a shared or personal login) with a role scoped to the company codes in scope; the network path or SFTP folder; and the first company code to go live.
Order of switching on. Read-only first, then recommendations next to your team, then postings behind a named approver. The step-by-step view: how AI agents work with SAP for accounts receivable. A proof of value takes 4-5 weeks on one entity; the rest of the rollout is in how long AR automation implementation takes.
Security. Data stays in your region, with VPC deployment in your own cloud, SSO/SAML, RBAC and a full audit trail. No customer data is used to train models (how AI agents access ERP data safely).
How does Transformance handle several company codes and ECC instances?
Several SAP instances and company codes consolidate in one Transformance environment, so one AR team works one queue while postings follow your SAP company code configuration.
In ECC, the company code is the unit with its own complete set of books, and AR posts and clears per company code. Groups often run more than one ECC instance after acquisitions, or ECC next to an already converted S/4HANA system. Both connect into the same Transformance environment.
The hard case is one bank transfer for two company codes. Illustrative example (amounts fictional): a customer transfers EUR 61,400.00 for four invoices in company code 1000 and two in company code 2000. Vero finds all six items in Customer 360 and proposes the split with its evidence: EUR 48,900.00 against 1000, EUR 12,500.00 against 2000. The cross-company posting follows your SAP configuration, and a person approves it.
Thresholds can differ by entity, so a high-volume shared service centre and a small subsidiary need not share one limit. The group operating model: multi-entity order-to-cash.
What changes in SAP when you move from ECC to S/4HANA?
In S/4HANA, line items sit in the Universal Journal, the old index tables become read-only views, customers become business partners and house bank accounts become bank account master data.
What SAP changes from ECC to S/4HANA, and what to recheck for a connected AR system
Rows 1 to 4 follow SAP’s conversion guide for S/4HANA 1511 (SAP, 2016, the most detailed SAP source found; SAP Learning’s current pages did not cover these points); rows 5 and 6 follow the 2023 guide below. Transaction and table names are standard SAP and vary by release.
Reads survive, writes do not. SAP replaced BSID, BSIK, BSAD and BSAK with views “with the same names”, which “ensures the continuation of all read accesses”. But “the views with same names allow only read access”, so any write into them has to be replaced (same 2016 guide).
Master data. “The Business Partner approach is mandatory in SAP S/4HANA”, so every customer record is converted into a business partner, and the mapping to customer numbers and payers has to follow.
Bank data. “House bank accounts have been merged into bank account master data”, and “Classic Cash Management is replaced by the new SAP Cash Management” (same 2016 guide). Bank statement assignment depends on the first, the cash forecast on both (cash flow forecasting from SAP data).
Tooling. SAP’s current conversion guide points to the SAP Readiness Check, the Simplification Item Catalog and custom code migration checks to find what a conversion changes in your system (SAP, conversion guide 2023, 2026 edition). The full S/4HANA map: SAP S/4HANA integration.
What carries over from your Transformance setup to S/4HANA?
Your Transformance setup carries over to S/4HANA with remapping: the connection is pointed at the converted system and mapped to what SAP changed, such as business partners and bank accounts.
Nothing of Transformance lives inside your ECC, so SAP’s custom code check finds no Transformance code to adapt; the remapping concerns the connection and the master data SAP converts. Transformance connects to S/4HANA on-premises, private cloud and public cloud, so the target edition decides the connection route.
How to carry a Transformance ECC setup over to S/4HANA in 7 steps:
- List every ECC instance and company code connected to Transformance, and the conversion wave each one falls in.
- Export the customer numbers in use and check their business partner mapping once CVI has run.
- List the house bank accounts your bank statements post to, and their IDs in bank account master data after conversion.
- In the sandbox conversion, have your SAP team and Transformance set up the connection to the converted system and remap it.
- Run one company code at the recommend level on the sandbox and compare its proposals with production on ECC for the same payments.
- At cutover, open the posting periods, switch the company code over and keep postings behind the approvers and thresholds you confirm for S/4HANA.
- Check the first postings in S/4HANA against the Transformance audit trail: timestamp, what the system did, what the user did, who approved, the input and the confidence.
Step 5 matters most: the same payments on both systems show whether a changed business partner number or bank account ID moves a proposal before any posting depends on it.
Should you connect SAP ECC now or wait for S/4HANA?
Connect SAP ECC now if your S/4HANA go-live is more than one rollout away, because the setup carries over with remapping and AR results start before the conversion.
The SAP clock. SAP gives SAP Business Suite 7 core applications mainstream maintenance to the end of 2027 and optional extended maintenance to “the close of 2030” at “a premium of two percentage points on the existing maintenance basis” (SAP News, 2020).
The user clock. Among DACH SAP user companies that plan ECC investments, 37% want to switch to S/4HANA by the end of 2027 and almost half by the end of 2030 (DSAG, 2026).
The arithmetic. A full rollout takes up to 4-8 weeks, so a conversion planned 12 months out leaves most of a year of AR results on ECC. For reference, ClearMatch reaches a 95% auto-match rate and runs end to end in under 8 minutes, and CollectPulse brings DSO down by 8-12 days on average (Transformance customer data, 2026).
Waiting can make sense when the conversion cutover falls inside the rollout window, or when the business partner conversion is still open and customer numbers are about to move. The business case: SAP ECC end-of-maintenance playbook for AR.
Who Transformance is for
- ERPs: SAP ECC and SAP S/4HANA (on-premises, private or public cloud), both in production with customers today; also 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: connect ECC now, carry the setup to S/4HANA
On SAP ECC, Transformance reads FI-AR data, proposes with evidence and posts only after approval, and because nothing of it lives inside ECC, the setup carries over with remapping.
Start with one company code, read-only, then switch on postings behind a named approver, and plan the remapping into your conversion test cycle. Book a Call to map your company codes and connection method with us.
Key terms
- SAP S/4HANA: SAP’s current ERP suite and the conversion target for SAP ECC.
- Cash application: matching incoming payments to open invoices and clearing them in the ERP.
- Remittance advice: the customer’s note listing which invoices a payment covers.
- Short pay: a payment below the invoice amount that leaves a difference to explain.
- On-account cash: money on the customer account that has not cleared a specific invoice.
- 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 S/4HANA?
- 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?
- SAP ECC end of maintenance 2027: the AR playbook
- How AI agents work with SAP for accounts receivable
Frequently Asked Questions
Does Transformance work with SAP ECC?
Yes, Transformance connects to SAP ECC and runs in production with customers on it today, reading FI-AR data and posting approved clearing entries back without custom ABAP.
Do we need to install anything in SAP ECC?
No custom ABAP and no modifications go into your ECC. The connection uses RFC/BAPI, IDoc, file/SFTP, middleware, SAP Cloud Connector or the Transformance on-premises agent, whichever fits your environment.
How long does it take to connect Transformance to SAP ECC?
The ERP connection typically takes 2-3 days, and your IT team may be involved. The full rollout takes up to 4-8 weeks, and a proof of value runs 4-5 weeks on one entity.
What happens to our Transformance setup when we move from ECC to S/4HANA?
Your setup carries over to S/4HANA with remapping: the connection is pointed at the converted system and mapped to what SAP changed, such as business partners and bank account master data.
Can Transformance handle many company codes, or ECC and S/4HANA side by side?
Yes, several SAP instances and company codes consolidate in one Transformance environment, so an ECC system and an already converted S/4HANA system can run side by side. It is built for mid-market to large enterprises with 250 to 2,000+ employees, including shared service centres.
Which payment volumes and AR processes does Transformance cover on SAP ECC?
Transformance handles from under 1,000 to over 100,000 payments a month, for cash application alone or the full order-to-cash: cash application, deductions, AR collections and cash forecasting.
What does a Transformance integration with SAP ECC cost?
The cost depends on the scope and the number of entities and company codes you connect. Book a Call to walk through your ECC setup.
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.
