Key Takeaways
- Transformance’s AI agents sit outside SAP on every path, so what matters is what each path carries. For a new implementation’s open-item load, SAP’s migration object documentation for S/4HANA 1909 (SPS04, updated April 2026) says: “no documents will be migrated. Only balances and open items will be taken over” (SAP).
- SAP calls system conversion, new implementation and selective data transition “three equally important approaches” (SAP Learning).
- In the 1909 documentation, down payments, bills of exchange and open tax items sit outside the standard object for AR open items, so each needs its own plan.
- Transformance sits outside SAP on every path: the connection is pointed at the target system and mapped, and after a conversion the setup carries over with remapping.
In This Article
- Key Takeaways
- Brownfield vs greenfield S/4HANA: what happens to accounts receivable?
- What do brownfield, greenfield and selective data transition mean in SAP’s own words?
- What happens to customers and open items on each path?
- What happens to cleared history, dunning data and disputes?
- What does SAP’s standard migration object for AR open items cover?
- What happens to bank statements, dunning runs and AR reports?
- Where does AR automation sit on each path, and what do you reconnect?
- What should the AR team ask the SAP partner, whichever path you take?
Brownfield vs greenfield S/4HANA: what happens to accounts receivable?
Transformance’s AI agents keep working on every S/4HANA path: a conversion carries data and history, a new implementation loads customers and open items, and selective data transition carries what you select.
What each S/4HANA path does to accounts receivable, drawn from SAP’s documentation
SAP cells: SAP Learning (read 31 Oct 2026), SAP’s conversion guide (release 1511, 2016) and SAP’s migration object documentation for S/4HANA 1909 SPS04 (April 2026); cells without a quotation are our reading of SAP’s description. The last row is Transformance’s.
A transition path is the route by which an SAP ERP system becomes an SAP S/4HANA system: converted, built new, or built from selected data.
Which program phase to automate in, per path: does the transition approach change the answer? What SAP changes technically: the SAP ECC integration page.
Takeaway: every path keeps AR running; the paths differ in what arrives with it.
What do brownfield, greenfield and selective data transition mean in SAP’s own words?
SAP describes a system conversion as a 1:1 conversion of an existing system, a new implementation as a brand new installation, and selective data transition as migrating selected data.
SAP Learning names them a system conversion “(also known as Brownfield)”, a new implementation “(also known as Greenfield)” and a landscape transformation approach “(also known as Selective Data Transition)” (SAP Learning).
- System conversion: a “guided technical process for a 1:1 conversion of an existing SAP ERP system to SAP S/4HANA”; the system “must be on recent release”, and it is “1:1 transition only, not applicable for system consolidation” (SAP Learning).
- New implementation: a “brand new installation of a system” that inherits no custom code; “a phased rollout can be done (based on company code, for example)” (SAP Learning).
- Selective data transition: it “covers the migration of relevant business data from SAP ERP to SAP S/4HANA” (SAP Learning), including consolidating data from several ERP systems.
Public Edition. “There is no system conversion or landscape transformation option for SAP S/4HANA Cloud Public Edition; a new implementation is the only choice” (SAP Learning). For the public cloud, read the greenfield column.
Where AR has a say. Among the factors customers weigh, SAP Learning names “the need to retain historical data”: that is AR’s input. On an earlier SAP release, start with AR automation on SAP R/3 or ECC.
Takeaway: the three paths are SAP’s own, and SAP calls them “three equally important approaches”.
What happens to customers and open items on each path?
Customers become business partners on every path; open items stay in place in a conversion and load per company code at a migration key date in a new implementation.
Customers. “The Business Partner approach is mandatory in SAP S/4HANA”, and for a conversion “only customers with customer/vendor integration in place can move” (SAP conversion guide 1511, 2016). In a new implementation, SAP’s Customer migration object loads “BP Roles”, “Company data including dunning” and “Bank data”, and “is based on the assumption that business partner and customer are using the same partner ID” (SAP, 1909 SPS04). SAP also recommends that you “identify and eliminate duplicates” first (SAP Learning): a duplicate customer splits one payer’s history in two.
Open items by path. In a conversion they stay where they are, because the system converts “as is” (SAP Learning). In selective data transition you select “open items and a time-slice of historical closed items” (SAP Learning). In a new implementation “you must define an overall migration key date for each company code”, and the Customer, G/L account, Cost center, Profit center and Exchange rate objects must be maintained or migrated first (SAP, 1909 SPS04).
SAP’s recommended approach speaks directly to AR: “Clear as many of the open items payable, receivables, taxes and outgoing checks as possible from the accounts in the source system.” Fewer open items, SAP adds, mean a lower possibility of error and less reconciliation.
Two checks from the same object. “If a default payment block is assigned to a payment term, then the open item will be blocked accordingly.” And “External accounting document number” is out of scope, so agree which field carries the original invoice number: customers keep quoting the numbers on the invoices they received.
Every payment collected and applied before the key date is one open item fewer to load: the daily work of cash application and AR collections. After the load, compare open-item totals per customer and company code.
Takeaway: customers convert or load as business partners; open items stay, travel by selection, or load at a key date.
What happens to cleared history, dunning data and disputes?
A conversion keeps cleared history, selective data transition carries the time slice you select, and a new implementation loads no cleared items, so that history stays in the source system.
Cleared items. “A clearing transaction always creates a clearing document” (SAP Learning), and in a new implementation SAP Learning lists “completed, closed, and partially closed transactional data” as not migrated, with orders as its examples. With the open-item object “no documents will be migrated”, so cleared invoices and their clearing documents stay behind. SAP’s time slice of “2 years” for selective data transition is an example, not advice.
What AR uses history for. Payment behaviour per customer, how deductions and disputes were resolved, and a days sales outstanding trend that stays comparable. Where it must stay readable is a retention decision for finance and IT.
Dunning data. The Customer object’s dunning data “does not contain the Dunning Area field”; a separate Dunning Data sheet exists, but “this sheet is not used in the standard shipment” and is mapped in the project (SAP, 1909 SPS04). Dunning levels already reached on open items are not covered in the documentation we read: ask your SAP partner.
Disputes. Ask your SAP partner how dispute records and notes move with their open items.
Takeaway: decide how much history AR needs before the program decides for you.
What does SAP’s standard migration object for AR open items cover?
SAP’s object for AR open items, in its 1909 SPS04 documentation, lists down payments, bills of exchange and open tax items among the items it names as out of scope.
The documentation for the accounts receivable open item object lists as out of scope, among others (SAP, S/4HANA 1909 SPS04, April 2026):
- “Down payment and down payment request.”
- “Bill of exchange”, the items with special G/L type “W”: “This data must be posted manually in financial accounting.”
- “Open tax items / VAT line items (must be settled before data migration. Exception: Deferred tax).”
- “Special G/L indicator leading to the noted item.”
- “Multiple customer line items per document post.”
- Open items “with tax attributes from a country/region different from the company code country/region”.
For each group, list the items affected and agree who posts or settles them by when.
Read it for your release. This is SAP’s documentation for S/4HANA 1909 SPS04, updated in April 2026; later releases may cover more, and SAP notes that the direct-transfer documentation is “currently only available in the system”. Check your target release with your SAP partner.
Takeaway: the standard object covers balances and ordinary open items; give everything else an owner early.
What happens to bank statements, dunning runs and AR reports?
A conversion reuses most of your AR processes, selective data transition carries the configuration you select, and a new implementation configures bank statements, dunning and reports anew.
Conversion. The steps “implement SAP S/4HANA mandatory items and simplification items and reuse most of the original business processes”, after “custom code needs to be cleaned up” (SAP Learning). “House bank accounts have been merged into bank account master data” (SAP conversion guide 1511, 2016).
Selective data transition. A shell conversion converts a copy of production “without master and transaction data”; mix and match creates a new install to which “elements of existing configuration and ABAP repository are transferred” (SAP Learning).
New implementation. SAP’s best-practice content is activated and the team enters configuration values (SAP Learning). From the bank accounts in the general ledger “only the balance needs to be migrated” (SAP, 1909 SPS04). Before design starts, list your bank statement formats, dunning procedures, payment terms with a default payment block, and weekly AR reports.
Takeaway: a conversion carries the AR set-up with changes; a new implementation rebuilds it, so document yours first.
Where does AR automation sit on each path, and what do you reconnect?
Transformance sits outside SAP on every path, so the connection is pointed at the target system and mapped; after a conversion, the setup carries over with remapping.
How it connects. Transformance connects to SAP S/4HANA (on-premises, private cloud, public cloud) and SAP ECC, both running in production with customers today, with no custom ABAP and no modifications in your SAP system (clean core and third-party cash application). The ERP connection typically takes 2-3 days, and your IT team may be involved; a full rollout takes up to 4-8 weeks (how long implementation takes). Editions: SAP S/4HANA integration page.
What you reconnect, per path:
- Conversion: point the connection at the converted system and map it to what SAP changed.
- Selective data transition: point it at the target system, map it, and check which closed items the time slice brought.
- New implementation: connect the new system, map it, and reconcile open items per company code before the first posting.
Phased rollouts. Several SAP instances and company codes consolidate in one Transformance environment; agree with us how ECC and S/4HANA are connected while company codes move in waves (multi-entity order-to-cash).
Example (illustrative, numbers made up). A food manufacturer runs three company codes on ECC; company code A moves first in a new implementation, B and C later.
- Ahead of the key date, A has 6,200 open customer items; the AR team clears 1,100, which leaves 5,100.
- Of those, 60 are down payments and 15 carry a special G/L indicator; each gets an owner, and 5,025 items load with the open item object.
- The AR team compares the open-item total per customer between ECC and S/4HANA for A.
- One Transformance environment is connected to S/4HANA for A and ECC for B and C. When a payment quotes an ECC invoice number, Vero, the Transformance agent, investigates from Customer 360, fetches internal and external information and proposes the match with evidence.
- A person approves the first postings on S/4HANA, with approvers and thresholds confirmed again for the new system.
ClearMatch reaches a 95% auto-match rate, and nothing posts without human sign-off (Transformance customer data, 2026); thresholds go by amount, entity and customer (who approves what).
Takeaway: the path changes what you map, not where the AR automation sits.
What should the AR team ask the SAP partner, whichever path you take?
Six questions from the AR side apply to every path: history depth, open-item clean-up, out-of-scope items, bank and dunning set-up, approvals and testing the AR connection.
- History: how many years of cleared items does AR need in the new system, and where does the rest stay readable?
- Clean-up: who clears open items before the key date per company code, and which field keeps the original invoice number?
- Out-of-scope items: how are down payments, bills of exchange, open tax items and other special G/L items handled in our target release?
- Bank and dunning: how are bank statement import, house banks, dunning areas and dunning levels already reached set up or carried over?
- Approvals: when are AR approvers and thresholds confirmed again on the new system?
- Testing: when is the AR connection tested on the target system, and on which company code first?
Timing per path is in does the transition approach change the answer?, the ECC deadline in the SAP ECC end-of-maintenance playbook, and how the connection is tested before it posts anything in the onboarding hub.
Takeaway: six answers turn a path decision into an AR plan.
Who Transformance is for
- ERPs: SAP S/4HANA (on-premises, private or public cloud) and SAP ECC, both running in production with customers today, and other ERPs through our integrations hub.
- 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: know what your path carries, then prepare AR for it
Every path leads to an S/4HANA system where AR keeps running. Read SAP’s object documentation for your release, clear what you can before the key date, and give every out-of-scope item an owner. Book a Call to map your path, company codes and key dates with us.
Key terms
- SAP S/4HANA: SAP’s current ERP suite and the target of every transition path.
- Master data management: keeping customer and business partner records consistent.
- Sub-ledger: the customer-level ledger behind the general ledger, where open items live.
- Dunning: staged reminders for overdue invoices.
- Days sales outstanding: the average number of days to collect after a sale.
- Cash application: matching incoming payments to open invoices and clearing them in the ERP.
Related guides
- Which ERP systems does Transformance integrate with?
- Should you automate AR before or after the S/4HANA migration?
- How does Transformance integrate with SAP S/4HANA?
- How does Transformance integrate with SAP ECC?
- Can you automate AR on SAP R/3 or ECC without S/4HANA?
- Can a third-party cash application tool keep SAP clean core intact?
Frequently Asked Questions
Does it matter for AR automation whether we choose brownfield or greenfield?
Not for where it sits: Transformance runs outside SAP on every path, and you point the connection at the target system and map it. What differs is the AR data your SAP path carries.
What happens to our open items in a greenfield S/4HANA?
They load per company code at a migration key date, after the customers, and SAP recommends clearing as many as possible first, because only balances and open items are taken over.
Is cleared payment history migrated in a greenfield project?
Not by the standard open-item object, which takes balances and open items only. Selective data transition can carry a time slice of closed items, for example two years, if you select it.
Does Transformance work with ECC and S/4HANA at the same time during a phased move?
Transformance connects to SAP ECC and SAP S/4HANA, both running in production with customers, and several SAP instances and company codes consolidate in one Transformance environment. We agree the phased plan with you.
How long does it take to connect the new S/4HANA system?
The ERP connection typically takes 2-3 days, and your IT team may be involved. A full rollout takes up to 4-8 weeks, and a proof of value runs 4-5 weeks on one entity.
Which company sizes and payment volumes is this for?
Mid-market to large enterprise with 250 to 2,000+ employees, including groups with several entities and shared service centres, handling from under 1,000 to over 100,000 payments a month.
What does AR automation around an S/4HANA move cost?
It depends on scope and the number of entities, from cash application alone to the full order-to-cash. Book a Call and we scope it with you.
SAP and SAP S/4HANA are trademarks of their respective owners (SAP SE). Transformance is not affiliated with or endorsed by SAP SE.
