Key Takeaways
- Our guidance: pick the phase of the SAP program rather than a side of the go-live: start on ECC, run through the waves, pause postings at cutover, resume once approvers are confirmed.
- A proof of value takes 4-5 weeks on one entity and a full rollout up to 4-8 weeks, so our guidance is to start on ECC when cutover is more than about three months out.
- Before converting Financial Accounting, SAP’s conversion guide has you lock periods and users and “ensure that no further postings are made”, so no AR go-live belongs in the freeze.
- Transformance uses no custom ABAP and no modifications in SAP, so a setup built on ECC carries over to S/4HANA with remapping.
- 56% of ASUG members are live on S/4HANA or have started to move (ASUG, 2025, US); 37% of DACH SAP users planning ECC investments want to switch by the end of 2027 (DSAG, 2026).
In This Article
- Key Takeaways
- Should you automate AR before or after the S/4HANA migration?
- What does the SAP timeline look like for ECC customers?
- When does it make sense to automate AR before the migration?
- Can you automate AR during the S/4HANA migration?
- What happens to AR automation at cutover and in hypercare?
- When is it better to wait until after the migration?
- Does the transition approach change the answer?
- What does a timeline for AR automation around the S/4HANA move look like?
- What carries over from ECC to S/4HANA, and what is remapped?
Should you automate AR before or after the S/4HANA migration?
Our guidance: automate AR before the S/4HANA migration when go-live is more than one rollout away, during it in wave rollouts, and after hypercare when cutover is close.
Before, during or after the S/4HANA migration: which window fits your AR automation
In every option: no AR go-live inside the cutover freeze or hypercare. The three-month line reflects a 4-5 week proof of value on one entity and a full rollout of up to 4-8 weeks; it is our guidance, not a benchmark.
The migration window is the stretch from the first SAP S/4HANA project phase to the end of hypercare, in which the ERP your AR process posts to changes underneath it. AR automation that lives outside SAP can start on ECC and carry over with remapping. The stretch to keep clear is cutover and hypercare: SAP stops postings there, and your AR key users are busy elsewhere.
ASUG’s April 2025 research reports “56% already live or started to move” to S/4HANA (ASUG, 2025; US, ASUG members, n=176). In DACH, 37% of DSAG respondents planning ECC investments want to switch by the end of 2027 (DSAG, 2026; DACH).
What does the SAP timeline look like for ECC customers?
SAP’s mainstream maintenance for Business Suite 7 core applications ends with 2027, optional extended maintenance runs to the end of 2030, and many groups plan their switch inside that window.
The SAP clock. Extended maintenance runs for three years, “beginning at the start of 2028 and ending at the close of 2030”, with “a premium of two percentage points on the existing maintenance basis”. SAP commits to S/4HANA maintenance “until the end of 2040” (SAP News Center, 2020).
The user clock (DACH). Beyond the 37% aiming for end-2027, almost half of DSAG respondents planning ECC investments target the end of 2030 and 4% the end of 2033 (DSAG, 2026; 198 member companies, surveyed December 2025 to January 2026).
Why dates move. “Skills shortages, parallel transformation projects, and limited budgets are also causing schedules to be pushed back” (DSAG, 2026). Plan AR on the go-live date you trust, not the one on the slide.
The US view. ASUG found that “Brownfield is the leading approach for deployment” and that “Most S/4HANA projects stay on track but prove more complex than expected” (ASUG, 2025, US).
The business case for acting before the deadline is in our SAP ECC end-of-maintenance playbook for AR.
When does it make sense to automate AR before the migration?
Automate AR on SAP ECC first when your S/4HANA go-live is months away or undated, AR costs cash every month, and your customer numbers will survive the conversion.
What “before” looks like. The SAP ECC connection typically takes 2-3 days, and your IT team may be involved. A proof of value runs 4-5 weeks on one entity, and the full rollout takes up to 4-8 weeks (what an AR automation rollout contains). SAP ECC runs in production with Transformance customers today.
What it delivers while ECC is the ledger. ClearMatch reaches a 95% auto-match rate and runs end to end in under 8 minutes for cash application. CollectPulse brings days sales outstanding down by 8-12 days on average (Transformance customer data, 2026). These are platform figures, not ECC-specific results.
How the agent works. For an unmatched payment or a short pay, Vero, the Transformance agent, investigates from Customer 360, fetches internal and external information to find more matches and proposes the clearing with its evidence. A person approves; postings follow your approval thresholds (how AI agents work with SAP for AR).
What changes at the move. Nothing of Transformance lives inside ECC, so the setup carries over to S/4HANA with remapping. The read and write map and the carry-over steps are in how Transformance integrates with SAP ECC.
When “before” turns into “later”. If the business partner conversion (CVI) is due within months and customer numbers will change, every customer mapping would be done twice. Connect after the conversion instead.
Can you automate AR during the S/4HANA migration?
Yes, if the program moves company codes in waves or redesigns AR anyway, but AR go-lives belong between the program’s test cycles, never inside the cutover freeze.
Wave rollouts. When company codes or countries move in waves, ECC and S/4HANA run side by side for months. Several SAP instances and company codes consolidate in one Transformance environment, so one AR team can work one queue while each wave switches over (multi-entity order-to-cash).
New implementation or selective data transition. AR is redesigned in SAP Activate’s Explore phase, where the team runs “the fit-to-standard workshops using the SAP Best Practice content” (SAP Learning, SAP Activate course). Our guidance is to put AR automation into that scope, so the target process is designed and automated once.
Testing. SAP’s conversion guide uses a copy of the development system: “You use the second development system to perform and test all phases of the conversion” (SAP, conversion guide 2023). Our guidance: put the AR connection on the interface list of every test cycle, and agree with your SAP team and your vendor how the AR side is tested, for example by comparing proposals for one company code with ECC production.
Capacity is the real constraint. ASUG members who are live or moving name “Support needed while diverting the team from their primary responsibilities” and “Compatibility with connected applications and/or integrations” among the top eight risks they experienced (ASUG, 2025, US). Name the AR key users for both projects before you start.
What happens to AR automation at cutover and in hypercare?
At cutover your team locks the posting periods and stops postings in SAP, so postings from AR automation pause too; in hypercare, postings resume behind approvers you confirm again on S/4HANA.
What SAP asks finance to do. Before converting Financial Accounting, SAP’s conversion guide lists: make sure “all held documents have either been posted or deleted”; carry balances forward, including the subledgers (F.07 for receivables and payables); “Execute all scheduled jobs and do not schedule any new jobs”; “Lock the periods in Financial Accounting”; lock users without migration tasks; and “Ensure that no further postings are made in your system” (SAP, conversion guide 1511, 2016). It is a period close with the users locked out.
Downtime. “Migration of application data usually happens during release upgrades or updates while the system is down”, and a downtime-optimized conversion shortens that downtime (SAP, conversion guide 2023). Bank statements and remittances keep arriving meanwhile.
Your AR cutover checklist (reader practice):
- Freeze rule changes and approval thresholds two weeks before cutover (our guidance, not an SAP rule).
- Clear or document every open AR exception before SAP locks the periods.
- Agree with your SAP team and your vendor what happens to bank statements and remittances that arrive during the downtime, and who posts them after go-live.
- Agree with your SAP team and your vendor when and by whom the AR connection is switched over with the company code, and put it in the same cutover plan.
- Keep the same approvers, or confirm new ones on S/4HANA, before postings resume.
Hypercare. SAP Activate places “sustainment and hypercare activities in the Deploy phase once the system goes live” (SAP Learning) and gives it no fixed length, so plan to your own hypercare exit. Check the first S/4HANA postings against the audit trail: timestamp, what the system did, what the user did, who approved, the input and the confidence (what an AI agent’s audit trail records).
The control line stays. ClearMatch validates 100% of postings, and nothing posts without human sign-off. Thresholds go by amount, entity and customer; admins configure, finance approves (who approves what).
When is it better to wait until after the migration?
Wait until after hypercare when cutover falls inside your AR rollout window, the business partner conversion is still open, or your AR key users are booked in testing.
Cutover inside the window. With cutover 12 weeks away, the proof of value (4-5 weeks on one entity) and the rollout (up to 4-8 weeks) would run into cutover preparation and the freeze. Our guidance: start on S/4HANA once hypercare has ended.
Customer numbers about to change. “Only customers with customer/vendor integration in place can move to SAP S/4HANA”, and SAP recommends identical business partner and customer numbers, but “this is not possible in every case” (SAP, conversion guide 1511). If your numbers change, connect once, after the conversion, and do the master data management work once.
AR redesign not decided. In a new implementation, AR open items are loaded with the migration cockpit’s accounts receivable open item objects (SAP Knowledge Base, KBA 2853964). Decide the target AR process first, then automate it.
What waiting costs. Waiting costs the AR results of those months (the ROI of AR automation). Because schedules get pushed back, our guidance is to re-check the go-live date every quarter and switch to “before” if it slips.
Starting after is the same product path. Transformance connects to SAP S/4HANA on-premises, private cloud and public cloud, in production with customers today (SAP S/4HANA integration).
Does the transition approach change the answer?
Yes: a system conversion keeps your data and favours starting on ECC, while a new implementation or selective data transition redesigns AR and favours automating inside the program.
ASUG defines brownfield as a system conversion that “attempts to preserve as much as possible from a previous system”, greenfield as “a completely new implementation that starts from scratch”, and selective data transition as one that “combines elements of both approaches” (ASUG, 2025, US).
System conversion (brownfield). Open items, customers and company codes convert in place. What changes for a connected AR system is in the change table on the SAP ECC integration page. Starting on ECC pays off longest here, because the process you automate is the one that converts.
New implementation (greenfield). New customizing, open items loaded by migration object, often new customer numbers. Automating on ECC still pays for the waiting months, and the connection is remapped to the new system at the move. If go-live is less than one rollout away, design AR automation into the Explore scope instead.
Selective data transition. It is often used to merge several SAP systems into one. Several SAP instances and company codes consolidate in one Transformance environment, so AR can run across old and new systems while they merge.
What does a timeline for AR automation around the S/4HANA move look like?
Map AR automation onto the SAP program phases: connect and prove value on ECC, remap in the test cycles, pause at cutover, resume in hypercare, extend in Run.
Where AR automation fits in an S/4HANA program, phase by phase
SAP column: SAP News Center, 2020 (dates); SAP Learning, SAP Activate course (phases, hypercare in Deploy); SAP conversion guides 2023 (test copy) and 1511 (cutover steps). AR column: Transformance deployment figures and reader practice.
SAP Activate has six phases: Discover, Prepare, Explore, Realize, Deploy and Run, where “Run is effectively the support or management of the productive solution post go-live” (SAP Learning). SAP’s page gives no phase durations, so the only durations in the table are ours.
What carries over from ECC to S/4HANA, and what is remapped?
A Transformance setup carries over to S/4HANA with remapping: the connection is pointed at the new system and mapped to what SAP changed, such as business partners and bank accounts.
Transformance keeps SAP clean core, with no custom ABAP and no modifications (clean core and third-party cash application), so SAP’s custom code checks find no Transformance code to adapt. What you check on your side:
- Customer numbers against their business partner numbers once CVI has run.
- House bank accounts against their IDs in bank account master data.
- Company codes and the wave each one converts in.
Agree with your vendor, before the test cycles, which parts of the setup are remapped and who does each step. Approval thresholds by amount, entity and customer are confirmed again for S/4HANA before postings resume. The full carry-over list is on the SAP ECC integration page; editions are on the SAP S/4HANA integration page.
Who Transformance is for
- ERPs: SAP ECC today and SAP S/4HANA (on-premises, private or public cloud) after your move, both in production with customers; 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: choose the program phase for AR automation
Start AR automation on ECC when go-live is more than one rollout away, run through the waves on one environment, pause at cutover, and resume once approvers are confirmed.
Our guidance: put the AR connection on the program’s interface list today and re-check the go-live date every quarter. A person approves every posting Vero proposes, and approvers are confirmed again on S/4HANA before postings resume. Book a Call to place AR automation in your SAP timeline.
Key terms
- SAP S/4HANA: SAP’s current ERP suite and the migration target for SAP ECC.
- Cash application: matching incoming payments to open invoices and clearing them in the ERP.
- Master data management: keeping customer, bank and other master records consistent across systems.
- Period close: closing a posting period so no further entries land in it.
- Audit trail: the record of who or what did which step, when, and who approved it.
- Days sales outstanding: the average number of days it takes to collect receivables after a sale.
Related guides
- Which ERP systems does Transformance integrate with?
- How does Transformance integrate with SAP ECC?
- How does Transformance integrate with SAP S/4HANA?
- Who approves what when an AI agent works in your ERP?
- What does an AI agent’s audit trail in finance record?
- Can a third-party cash application tool keep SAP clean core intact?
- SAP ECC end of maintenance 2027: the AR playbook
Frequently Asked Questions
Should we automate AR before migrating from SAP ECC to S/4HANA?
Yes, if your S/4HANA go-live is more than about three months away or not yet fixed, because a proof of value takes 4-5 weeks on one entity, a full rollout up to 4-8 weeks, and the setup carries over with remapping. The three-month line is our guidance, not a benchmark.
Does AR automation set up on ECC have to be rebuilt for S/4HANA?
No, the setup carries over to S/4HANA with remapping. With no custom ABAP and no modifications, there is no Transformance code inside SAP to adapt; the connection is mapped to what SAP changed, such as business partners.
Can AR automation run on ECC and S/4HANA at the same time during a wave rollout?
Yes, several SAP instances and company codes consolidate in one Transformance environment, so company codes still on ECC and those already on S/4HANA can be worked by one AR team in one queue.
How long does it take to automate AR before the migration?
The SAP ECC connection typically takes 2-3 days, and your IT team may be involved. A proof of value runs 4-5 weeks on one entity, and the full rollout takes up to 4-8 weeks.
Which SAP editions and company sizes is this approach for?
It fits SAP ECC today and SAP S/4HANA on-premises, private or public cloud after the move, for mid-market to large enterprises with 250 to 2,000+ employees, including groups with several entities and shared service centres.
Which AR processes should we automate first around an S/4HANA migration?
Our guidance is to start with cash application on one entity, the scope of a 4-5 week proof of value, and to add deductions, AR collections and cash forecasting once the first company code runs. Transformance handles from under 1,000 to over 100,000 payments a month.
What does automating AR around an S/4HANA migration cost?
The cost depends on the scope and the number of entities and company codes you connect. Book a Call to place AR automation in your SAP timeline.
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.
