Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 1 of 6

Finance first: when Central Finance makes sense

11 min

Listen to this lesson

0:00 / 7:31

Central Finance (SAP S/4HANA for central finance) is an SAP S/4HANA system that receives accounting documents from other ERP systems in real time and posts them into its own Universal Journal. The source systems keep running their logistics and their local books; the central system gives finance one ledger, one chart of accounts and one set of reports across all of them. It is often described as a finance-first route to SAP S/4HANA, and as a coexistence tool for groups that will run several ERPs for years.

Contoso Motor Co. chose a system conversion of ECC (EP1) to SAP S/4HANA. But during the strategy phase, the option it studied most seriously was Central Finance: put an SAP S/4HANA central finance system in front of EP1 and the Alternadores del Norte legacy ERP, harmonize finance first and convert logistics later. This course uses that evaluated design as a clearly labeled what-if, because it shows exactly what Central Finance asks of a program, and what has to be tested.

What Central Finance does and does not do

TopicCentral Finance doesCentral Finance does not
AccountingReplicates FI and CO documents into one Universal JournalReplace the source systems' own books
Master dataMaps source keys to harmonized central keysClean the source master data for you
LogisticsShows the financial result of source logisticsRun sales, purchasing or production centrally
ProcessesCan take over payments and dunning (Central Payments)Move every process off the sources automatically
TransitionGives finance S/4HANA capabilities earlyConvert the source system; that remains a separate decision
Central Finance in one table.
The Sign-Off Table · thesignofftable.com/academy/sap-fin-309

When it fits

  • Many ERPs, one finance view. A group with several SAP and non-SAP ERPs wants a single ledger without first replacing them all.
  • Finance first. Finance needs SAP S/4HANA reporting, a new chart of accounts or a new ledger design before logistics can move.
  • Acquisitions. New companies join faster by replicating their finance than by migrating their whole ERP.
  • Shared services. Payments, collections and closing move into a central system that a shared service center operates.
  • Stepping stone. The central system later becomes the target into which source systems are consolidated.
One ERP, low needConvert directly; Central Finance adds a system without much benefit
Many ERPs, low needConsider consolidation tools such as Group Reporting instead
One ERP, high needWeigh Central Finance against a conversion with finance redesign
Many ERPs, high needStrongest case for Central Finance
Where Central Finance earns its cost.
The Sign-Off Table · thesignofftable.com/academy/sap-fin-309

Why Contoso did not choose it

Contoso's case sat in the "one ERP, high need" corner for about a year, with the Alternadores acquisition pushing it toward "many ERPs". The steering group, chaired by Grace, compared the two routes. Central Finance would have given Dan a harmonized ledger for 1710, 1810 and the future 1910 within months. But it meant running and testing three systems in parallel (EP1, the Alternadores ERP and the central system), building and governing thousands of mappings, and still converting EP1 later. A system conversion, followed by migrating Alternadores into the converted system in Wave 2, gave the same end state with one fewer system to reconcile.

The questions Contoso's steering group asked; the answers led to a system conversion.
The Sign-Off Table · thesignofftable.com/academy/sap-fin-309
  1. Phase 1Central system buildSAP S/4HANA central system, chart of accounts, ledgers, mappings
  2. Phase 2Initial load and replicationBalances and open items loaded; real-time replication from EP1 and the legacy ERP
  3. Phase 3Central processesCentral Payments, central close and group reporting on the central system
  4. Phase 4Logistics transitionSource systems converted or moved into the central system over time
The phases of the evaluated what-if design.
The Sign-Off Table · thesignofftable.com/academy/sap-fin-309
FactorCentral Finance first (what-if)System conversion (chosen)
Systems to test in parallelThree: EP1, legacy ERP, central systemOne converted system, plus Wave 2 migration
Finance benefits arriveEarly, before logistics changesAt go-live, together with logistics
Mappings to governThousands of key and value mappingsNone between systems
Reconciliation effortContinuous: sources versus central ledgerAt cutover and Wave 2 load
End stateStill needs logistics transition laterOne SAP S/4HANA system

The comparison that decided Contoso's route.

What would you do?

A US manufacturer with two SAP ECC systems and three non-SAP ERPs from acquisitions wants a single ledger and central payments within a year, while the plants keep their ERPs for at least three more years. What should its architects propose first?

The decision path at Contoso: the acquisition strengthened the case, but one converted system won.
The Sign-Off Table · thesignofftable.com/academy/sap-fin-309

What goes wrong in testing a finance-first route

PitfallEffectPrevention
Testing the central system aloneDefects appear only when real source data arrivesEvery test starts with a posting in a source system
No source test systems paired with the central QASMappings tested against the wrong dataPair each source QAS with the central QAS and refresh them together
Reconciliation designed after buildNobody can prove the ledger is right at go-liveDesign reconciliation reports in the blueprint and test them in the first sprint
Source changes not regression tested centrallyA new source account or document type breaks replicationEvery source change includes a central replication test

Program-level pitfalls of a Central Finance route.

The last row is the one programs underestimate. As long as sources run, every change in a source system, such as a new G/L account, a new document type, or a support package, is also a change to Central Finance. The release process for the sources must include a central replication and reconciliation check, which means the central test system must be available whenever any source releases.

Key points
  • Central Finance replicates FI and CO documents from SAP and non-SAP ERPs into one SAP S/4HANA system.
  • It fits groups with many ERPs and a need for harmonized finance before logistics moves.
  • It adds a system, mappings and continuous reconciliation to the program.
  • Contoso evaluated it and chose a system conversion; the course follows that evaluated design as a what-if.

Check your understanding · not graded

Lesson check

  1. 1. What does Central Finance replicate into the central system?

  2. 2. Which situation is the strongest case for Central Finance?

  3. 3. Why did Contoso choose a system conversion over Central Finance?

  4. 4. What still has to happen to the source systems after Central Finance goes live?