Key Takeaways
- SAP rates every extension by the least clean object it uses, on four clean core levels from A (released APIs) to D (modifications and table writes).
- An external layer stays clean when none of its code sits in SAP, every read and posting uses a classified interface, and SAP books each clearing.
- RISE with SAP adds no separate rule for third-party tools; your edition decides what is allowed.
- Transformance needs no custom ABAP and no modifications in SAP, with 100% posting validation and nothing posted without human sign-off.
- Your SAP team can test any vendor’s clean core claim in six checks in its own quality system.
In This Article
- Key Takeaways
- Can a third-party cash application tool keep SAP clean core intact?
- What does SAP mean by clean core?
- How do SAP’s clean core levels A to D apply to a cash application integration?
- What changes between public cloud, private cloud and on-premises?
- What does RISE with SAP change for a cash application tool?
- What must an external cash application layer do, and never do, in SAP?
- How does Transformance connect to SAP without touching the core?
- How do you check a vendor’s clean core claim before you sign?
Can a third-party cash application tool keep SAP clean core intact?
Yes, if it runs outside the SAP core, reads and posts only through interfaces SAP classifies for that use, and leaves every clearing to SAP’s own posting logic.
Clean-core checklist for an external cash application layer in SAP S/4HANA
Classification and level names follow SAP’s own documentation; your release and edition decide which interfaces exist.
In SAP’s words, “Extensions are evaluated based on the lowest-ranked technology used within them” (SAP Learning, clean core extensibility course). One table write or internal object decides the level of the whole integration.
Integration is also where SAP users put their money: in the DSAG Investment Report 2026, 45% of 198 SAP user companies in the DACH region plan high or medium investments in integration on SAP BTP, up from 27% in 2024, ahead of analytics (38%), application development and automation (27%) and AI (16%). DSAG says customers should make their existing systems “clean-core-ready” (DSAG, 2026; DACH).
Transformance needs no custom ABAP and no modifications, and connects from outside the core by a method that follows your environment.
What does SAP mean by clean core?
Clean core is SAP’s approach of keeping an S/4HANA system standard in five dimensions, processes, extensions, data, integrations and operations, so upgrades do not break custom work.
SAP defines integrations as “Communication between solutions”. A newly provisioned S/4HANA Cloud system with standard processes is “clean” by definition, and “The goal is to continue to keep the system clean moving forward as extensions and integrations are built” (SAP Learning, SAP Cloud ALM for RISE course). Every new integration is a decision about staying clean.
For the integration dimension, SAP names the target: “SAP standard integration scenarios as exposed in the SAP Business Accelerator Hub”, using OData, SOAP or events, with “proper monitoring and error resolution capabilities” (SAP Learning, SAP Activate course).
Finance cares because an AR integration that touches internal objects becomes regression work at every upgrade, and in the public edition “software updates run automatically and for all customers simultaneously” (SAP Learning, clean core extensibility course).
How do SAP’s clean core levels A to D apply to a cash application integration?
SAP rates each extension by the least clean object it uses: released APIs are level A, classic APIs level B, internal objects level C, modifications and table writes level D.
SAP sorts objects into four classes: released APIs carry SAP’s stability promise; classic APIs are ABAP artifacts “recognized as upgrade safe”; internal objects are “Artifacts that are not classified as ‘Classic APIs’”; not recommended objects are “Artifacts known to introduce upgrade challenges” (SAP Learning). The levels follow:
- Level A applies to “both side-by-side implementations on SAP BTP” and on-stack development that use released objects only.
- Level B: “Extensions qualify for Level B when they use only SAP objects and development patterns classified as classic APIs or released APIs.” SAP’s own example is a wrapper around a BAPI.
- Level C includes “read-only access to SAP tables not endorsed for external consumption”. For AR: reading open items straight from SAP tables instead of a released view or API is a level C pattern.
- Level D covers “Modifications, extensions, and unsupported write operations on SAP tables”, implicit enhancements and objects in the “noAPI” state. For AR: writing clearing data into SAP tables instead of posting a document is level D.
A cash application flow has four touchpoints: reading customers and open items in the sub-ledger, reading bank statements and remittances, posting the clearing, and correcting it. Ask which object class each touchpoint uses; the lowest one sets the level.
If your team still speaks of tiers, SAP “has evolved its original three-tier model into the clean core level concept” (SAP News, 2025).
What changes between public cloud, private cloud and on-premises?
The public edition allows only released APIs and extension points; private cloud and on-premises also allow classic APIs, which keeps more routes open but asks for more discipline.
Public cloud. SAP’s rules: “Modifications of SAP objects are not permitted”, “Extensions must be clearly separated from SAP code”, and only released APIs and extension points may be used (SAP Learning). An external system connects through a communication system, a communication user “not intended for human authentication” and a communication arrangement that defines the messages exchanged (SAP Learning, public edition course). For postings and clearings from outside, SAP provides its released journal entry APIs.
Private cloud and on-premises. “In situations where the ABAP Cloud development model cannot be used, classic extensibility is still available and supported.” Classic APIs such as BAPIs stay possible at level B, and IDoc or file routes stay open; the question becomes which class each interface belongs to.
SAP ECC. Clean core levels are SAP’s S/4HANA model. On ECC, the same discipline (no modifications, no table writes) protects the later move (SAP ECC integration).
Edition by edition, the Transformance connection is on how Transformance integrates with SAP S/4HANA.
What does RISE with SAP change for a cash application tool?
RISE with SAP is SAP’s transformation journey to cloud ERP, and its methodology builds clean core checks into every phase, so integrations get reviewed at each quality gate.
“RISE with SAP is the transformation journey for existing SAP customers moving from on-premise ERP to cloud ERP.” Until April 2025 it was a distinct sales package; today it can include the public edition or SAP Cloud ERP Private, SAP’s new name for S/4HANA Cloud Private Edition (SAP Learning, SAP Cloud ALM for RISE course).
Clean core principles are “embedded in Governance & Framework of the RISE with SAP Methodology”, “anchored with quality gates”, and in the run phase SAP asks customers to “Establish a continuous ‘keep clean’ process” (SAP Learning, SAP Activate course).
For a cash application tool, that means two things:
- Have the vendor’s interface list ready before the quality gate.
- Plan monitoring: SAP Cloud ALM integration monitoring covers “end-to-end processing of messages, events and business objects” (SAP Learning, building integration lesson).
Timing the move: automate AR before or after the S/4HANA migration.
What must an external cash application layer do, and never do, in SAP?
A clean external layer stays outside the core, uses a technical user and classified interfaces, and lets SAP create every document; it never installs code, modifies objects or writes tables.
Must:
- Run outside the SAP system, under a dedicated technical user (public edition: a communication user) with a role scoped per company code.
- Read through released interfaces, or classic ones where none is released (private cloud and on-premises).
- Post clearings and journal entries as SAP documents, so SAP’s periods, tolerances and authorisations apply: “A clearing transaction always creates a clearing document” (SAP Learning, financial accounting course).
- Keep a log that matches the SAP document, and follow SAP’s correction sequence.
Must never:
- Deliver ABAP code or transports into your system.
- Modify SAP objects, use implicit enhancements or “noAPI” objects, or write to SAP tables.
- Log in as a person, or post around a closed period or a tolerance check.
The correction path. SAP’s sequence for a wrong cleared payment is to “reset the cleared items, reverse the document, and re-enter the original posting correctly” (same lesson). In the public edition, SAP’s knowledge base reports that one of its released journal entry APIs rejects reversing a cleared posting: “Reversal of already cleared or reversed postings is not supported.” (SAP Knowledge Base Article 3669001). Agree the correction path before go-live and rehearse it once.
Tolerance groups. SAP compares a payment difference with “the tolerance groups of the employee and the customer or vendor” (SAP Learning, payment differences lesson), so the technical user’s tolerance group is a setup decision. The full flow: how external systems post payments and clear open items.
When a payment arrives short or with no usable reference, Vero, the Transformance agent, investigates from Customer 360 and fetches internal and external information to find more matches. Vero proposes the clearing with its evidence, a person approves, and only then does SAP post it: logic outside, ledger inside. Identity and access: how AI agents access ERP data safely.
How does Transformance connect to SAP without touching the core?
Transformance needs no custom ABAP and no modifications in your SAP system: it connects from outside, reads AR data, and writes postings back only after a person approves.
Editions and routes. Transformance connects to SAP S/4HANA on-premises, private cloud and public cloud, and to SAP ECC; S/4HANA and ECC run in production with Transformance customers. Connection options are APIs, RFC/BAPI and IDoc, file or SFTP, middleware, SAP Cloud Connector or the Transformance on-premises agent; the method follows your environment (edition by edition). The ERP connection typically takes 2-3 days; your IT team may be involved.
Reads and writes. Transformance reads customer master data, open items, invoices, journal entries, bank statements and remittances. It writes clearing postings, journal entries and other ERP updates, including reversals (field map).
Controls. A multi-level approval model (read, recommend, execute, post) keeps a human in the loop for ERP postings, with thresholds by amount, entity and customer; admins configure rules, finance approves (approvals and thresholds).
ClearMatch reaches a 95% auto-match rate and runs end to end in under 8 minutes, with 100% posting validation (Transformance customer data, 2026).
Audit trail. The audit trail stores the timestamp, what the system did, what the user did, who approved, the input and the confidence (audit trail and reversals).
Remittances. DocSense reads remittances with over 97% extraction accuracy across 100+ document types and 170+ languages, with zero template configuration, so no remittance logic lives in SAP (how AI reads remittance advice).
Groups and data. Several SAP instances and company codes consolidate in one Transformance environment; data stays in your region, and no customer data is used to train models.
How do you check a vendor’s clean core claim before you sign?
Ask for the interface list per touchpoint and edition, check each object’s state in SAP’s own repositories, then prove the posting and correction path in your quality system.
Checking a vendor’s clean core claim in six steps:
- Ask for the interface list per touchpoint (customers, open items, bank statements, remittances, clearing, reversal) and per edition.
- Look up each interface’s state in the SAP Business Accelerator Hub, the released objects view or the Cloudification Repository.
- Ask which transports, add-ons or ABAP objects would be delivered into your system. For a clean external layer, the list is empty.
- Create the technical user and role yourself, scoped to the company codes in scope (public edition: communication user and arrangement).
- In your quality system, post one clearing, one partial payment and one correction, and check each SAP document against the vendor’s log.
- Put the interfaces and the technical user’s role into your regression tests for the next upgrade.
For released APIs, “SAP guarantees the stability of these interfaces from release to release” (SAP Learning).
SAP enforces released-only use in customer code “by syntax checks and ABAP test cockpit checks” (same lesson). If the vendor installs nothing, there is no vendor code to check; the review moves to the interfaces and the technical user’s role.
Who Transformance is for
- ERPs: SAP S/4HANA on-premises, private or public cloud with no custom ABAP and no modifications, 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: logic outside, ledger inside
A cash application tool keeps clean core intact when the matching and investigation run outside SAP and every posting is an SAP document that a person approved first.
SAP’s levels are the yardstick; the checklist and six steps turn them into evidence. Book a Call to walk your SAP team through the checklist with us.
Key terms
- SAP S/4HANA: SAP’s current ERP suite, on-premises, in a private cloud or in the public cloud.
- Cash application: matching incoming payments to open invoices and clearing them in the ledger.
- Journal entry: an accounting document with balanced debit and credit lines.
- Sub-ledger: the customer ledger where open items are posted and cleared.
- Period close: closing a posting period, after which SAP rejects postings into it.
- 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?
- How do external systems post payments and clear open items?
- Who approves what when an AI agent works in your ERP?
- Should you automate AR before or after the S/4HANA migration?
- SAP cash application: a complete guide for finance teams
- How AI agents access ERP data safely
Frequently Asked Questions
Does RISE with SAP change what a cash application tool may do in SAP?
No, RISE with SAP adds no new rule: your edition, public or private, decides which interfaces are allowed, and RISE’s quality gates check that integrations stay clean.
Which SAP editions does Transformance connect to without custom ABAP?
Transformance connects to SAP S/4HANA on-premises, private cloud and public cloud, and to SAP ECC, with no custom ABAP and no modifications.
Is reading open items through an interface enough to stay clean core?
It depends on the interface: in SAP’s model, a released API keeps that read at level A, while read-only access to tables SAP has not endorsed for external use is level C.
How long does a clean-core connection to SAP take?
The ERP 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.
Does it work for groups with many company codes and high payment volumes?
Yes, several SAP instances and company codes consolidate in one Transformance environment, built for 250 to 2,000+ employees and from under 1,000 to over 100,000 payments a month.
Does our SAP team have to retest Transformance at every upgrade?
Nothing of Transformance sits in your SAP code, so there is no add-on to upgrade. Your regression tests cover the interfaces in use and the technical user’s role.
What does a clean-core cash application set-up with Transformance cost?
The cost depends on your scope and the number of entities and company codes, so we quote it after a short 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.
