# SAP S/4HANA Finance Migration Readiness Assessment > Source: https://netray.co/tools/sap-s4hana-finance-migration-readiness-assessment > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Score your finance readiness for an ECC to S/4HANA move and get priorities for the next steps. ## Category sap ## Erp SAP S/4HANA ## Audience - Controller - SAP FICO consultant - Finance IT lead ## Tool **Kind:** assessment **Questions:** #### Which General Ledger do you run today? **Options:** ##### Classic General Ledger only **Score:** 0 ##### New General Ledger with limited features **Score:** 2 ##### New General Ledger with document splitting and parallel ledgers **Score:** 3 #### How clean is your reconciliation between FI and CO? **Options:** ##### Open differences every close **Score:** 0 ##### Differences found and fixed late in the close **Score:** 1 ##### Reconciled routinely with documented results **Score:** 3 #### Have you reviewed customer and vendor master data for the business partner model? **Options:** ##### Not started **Score:** 0 ##### Duplicates identified, cleanup in progress **Score:** 2 ##### Cleansed and mapped to business partner roles **Score:** 3 #### What is the state of your asset accounting setup? **Options:** ##### Classic Asset Accounting, unreconciled **Score:** 0 ##### Classic, reconciled and documented **Score:** 2 ##### Already on new Asset Accounting **Score:** 3 #### How many custom (Z) reports and programs read finance tables directly? **Options:** ##### Many, and no inventory exists **Score:** 0 ##### Inventory exists, impact not assessed **Score:** 1 ##### Inventoried and mapped to ACDOCA or CDS replacements **Score:** 3 #### Have you run the SAP readiness checks and simplification item analysis? **Options:** ##### No **Score:** 0 ##### Run once, findings not worked through **Score:** 1 ##### Run, findings triaged with owners and dates **Score:** 3 #### How would you describe your chart of accounts and cost element setup? **Options:** ##### Many unused accounts and legacy cost elements **Score:** 0 ##### Reviewed but not rationalised **Score:** 2 ##### Rationalised, with a plan for cost elements as G/L accounts **Score:** 3 #### Do you have a tested approach for historical data and archiving? **Options:** ##### No defined approach **Score:** 0 ##### Approach defined, not tested **Score:** 1 ##### Tested with a sandbox conversion **Score:** 3 #### Is finance involved in the project governance and testing? **Options:** ##### No named finance owner **Score:** 0 ##### Named owner, limited time **Score:** 1 ##### Dedicated finance lead with test scripts and sign-off **Score:** 3 #### Have you defined the target for ledgers, currencies and reporting (for example Fiori apps, embedded analytics)? **Options:** ##### No design decisions yet **Score:** 0 ##### Draft decisions **Score:** 2 ##### Approved design with data owners **Score:** 3 **Bands:** #### Early stage **Min:** 0 **Max:** 34 **Verdict:** Major finance foundations are still open. A migration now would carry data and design problems into S/4HANA. **Recommendations:** - Run the SAP readiness check and simplification item analysis first. - Reconcile FI to CO and fix standing differences. - Start customer and vendor data cleansing for the business partner model. #### Partly ready **Min:** 35 **Max:** 64 **Verdict:** Some building blocks are in place, but data, custom code or governance gaps could slow the project. **Recommendations:** - Inventory custom reports that read finance tables and plan replacements. - Assign a dedicated finance lead for design decisions and testing. - Run a sandbox conversion to expose data issues early. #### Mostly ready **Min:** 65 **Max:** 84 **Verdict:** Finance is in reasonable shape. Focus on the remaining gaps and on testing depth. **Recommendations:** - Close the open readiness check findings with owners and dates. - Test period-end and payment processes end to end in a conversion test. - Define the reporting target on the universal journal. #### Ready to plan the cutover **Min:** 85 **Max:** 100 **Verdict:** Your finance foundations look strong. Concentrate on cutover planning, validation and user readiness. **Recommendations:** - Build a detailed cutover and reconciliation plan. - Prepare balance validation reports for before and after conversion. - Train key users on Fiori apps and the new reporting. ## Content **Intro:** Moving SAP finance to S/4HANA changes the data model, master data and reporting, not just the database. This assessment helps you judge how ready your finance team is, and which topics to deal with before you commit to a date. **Sections:** #### How to use the assessment **Body:** Answer the ten questions with the facts as they stand today, not the plan. Be honest: a high score from optimistic answers does not help you. Share the result with the finance and IT leads, and use the recommendations as a starting backlog for the pre-project phase. **Bullets:** - Answer as a group with finance and IT together. - Where you do not know, pick the lower option. - Repeat the assessment after each cleanup milestone. #### Why these topics matter **Body:** S/4HANA Finance consolidates FI and CO into the universal journal ACDOCA, so FI-CO differences must be solved before conversion. Customers and vendors move to the business partner model, which exposes duplicate and incomplete master data. Asset accounting moves to the new version, and cost elements become G/L accounts. Custom code that reads old tables such as BSEG or COEP often needs rework. #### Reading your result **Body:** A low score does not mean you cannot migrate; it means preparation should come first. The most expensive surprises usually come from data quality, unreconciled balances and undocumented custom reports, rather than from the technical conversion itself. Use the band recommendations to build an order of work, and ask your implementation partner to confirm each point against your system landscape. #### Common mistakes **Body:** Teams often leave finance out of design and testing, treat the project as a technical upgrade, or underestimate reporting rework. Another mistake is not planning balance validation: finance should have before and after reports that prove balances match for every ledger and period. Decide early whether you convert historical data or start with a limited history. **Cta:** Netray does not replace your SAP implementation partner, but we can discuss a read-only reconciliation and reporting layer that helps finance validate balances before and after conversion. **Faq:** #### Is this assessment an official SAP tool? **Answer:** No. It is a practical self-check based on common finance conversion topics. SAP provides its own readiness check and simplification item catalogue, which you should run in addition. #### What is the universal journal? **Answer:** It is the single line item table ACDOCA in S/4HANA that holds data for general ledger, controlling, asset accounting and Material Ledger, so FI and CO are no longer reconciled across separate tables. #### Do I need to clean master data before migrating? **Answer:** Yes, ideally. The business partner model exposes duplicate and incomplete vendors and customers. Cleaning before conversion reduces migration errors and avoids carrying poor data into the new system. #### How long does a finance conversion take? **Answer:** It depends on scope, landscape and data volumes. Projects range from a few months for simple systems to a year or more for complex ones. A sandbox conversion gives the best evidence for your own case. ## Search terms s4hana finance migration readiness, ecc to s4hana finance checklist, universal journal migration readiness, sap business partner migration finance, s4hana new asset accounting readiness, sap fico s4hana conversion assessment, s4hana finance preparation, sap migration cockpit finance data --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json