Twelve years of SAP FICO can mean two incompatible things, and the CV almost never says which. The label stretches across two systems that store financial data in fundamentally different shapes, and in the finance CVs I read, the line between them is the one detail nobody thinks to state.

That line is the Universal Journal. In SAP S/4HANA the separate FI and CO tables were merged into one line-item table, ACDOCA, and a category of work that defined a lot of ECC-era finance careers stopped existing. Someone whose hands-on experience stops before that change is configuring a system that no longer behaves the way they learned it.

TL;DR: In S/4HANA, financial accounting and controlling post into a single line-item table, so the reconciliation work that shaped a lot of ECC-era FICO careers was designed out of the architecture. The quickest tell I know is whether a candidate says journal entry or still says accounting document and CO document. And two deployment choices, Central Finance and Group Reporting, are separate shortlists, not variations on the core FICO hire.

What the Universal Journal did to the FICO role

The Universal Journal removed the seam between financial accounting and controlling, and the recurring work that lived on that seam went with it. SAP's definition is blunt: "The universal journal is the book of original entry for business transactions in Financial Accounting (FI) and Controlling (CO)." (SAP's universal journal documentation). One book of record. Two disciplines that each used to keep their own.

The mechanism is a table merge. "Combining the data structures of the different components into a single line item table (ACDOCA) results in a single source of truth that replaces the previously separate physical tables." (SAP's Universal Journal FAQ, 2026). The verb doing the work in that sentence is replaces.

Here is what that means if you don't configure SAP for a living. Under the old architecture the finance ledger and the management ledger were physically separate stores, so they could disagree with each other, and a recurring slice of every month-end went on making them agree again. SAP's claim for the new architecture is categorical: "Since all financial data is based on the same line items, no reconciliation between financial accounting and management accounting is ever required." (the same page).

That matters for a career. Consultants who built their value on managing the gap between two ledgers had to rebuild it somewhere else, and where they rebuilt it is what I am listening for in a first call.

The vocabulary tells you when someone last worked

The quickest date stamp on a FICO CV is the noun the candidate reaches for when describing a posting. SAP put the change on the record: "With the Universal Journal, accounting documents and CO documents have been superseded by journal entries." (SAP's Universal Journal FAQ).

So a candidate who frames the work as reconciling two ledgers, or who talks about the CO document as a separate object that has to be tied back to the accounting document, is describing ECC. The question I use is deliberately plain: ask how a cost posting reaches the general ledger, then count how many documents appear in the answer.

The finance briefs I take almost never name which system the role is really for, and that is where the shortlist goes wrong: a keyword search on "SAP FICO" matches four letters and stops there.

Where the merge stops: not every table moved into ACDOCA

Not every table went into ACDOCA, and the exceptions give you a sharper screening tool than the headline does. Asked directly whether all the old tables were replaced, SAP answers: "No. Many tables have been replaced by table ACDOCA but not all." (the Universal Journal FAQ, 2026).

BSEG is the clearest example. "For example, the former G/L-only table BSEG still exists as it is needed to store the source documents that serve as the basis for journal entries into table ACDOCA." (the same FAQ page). It is a real table doing a real job, holding the source documents the journal entries are built from.

COEP went a different way. SAP's archiving documentation for Controlling describes it like this: "Table COEP was replaced by views of the same name, so-called compatibility views that aggregate the data in the universal journal on the fly in combination with the non-actuals from the original table COEP and in accordance with the old table structures." (SAP Help Portal, Data Archiving in CO, 2026). The old name still resolves. What answers to it, in that specific case, is a view assembled over the journal at read time.

That precision is your filter, and it is the one I lean on hardest. When a candidate tells me everything collapsed into one table, what I hear is a headline, not a project. The careful answer runs: some tables were replaced outright, at least one was rebuilt as compatibility views under its old name, and BSEG is still there because journal entries need source documents to come from.

Asset Accounting: the classic config that is simply gone

Classic Asset Accounting is unavailable in S/4HANA, so a candidate whose asset work stopped in ECC is expert in something the system no longer offers. SAP states it without hedging: "Classic Asset Accounting is no longer available in SAP S/4HANA; this applies to all systems. New Asset Accounting is now available in place of classic Asset Accounting." (SAP Help Portal, Migration to New Asset Accounting, 2026).

If you are moving to S/4HANA and assets are in scope, the migration to New Asset Accounting is part of the project, and it is one of the places I have watched an ECC-shaped consultant stall in front of a programme board.

Assets make a good interview topic because the answer is concrete: the migration is a discrete piece of work with a before and an after. I ask what it involved on their last project. The answers that reassure me describe sequence and consequence, what had to be closed first and what broke when it was not. Reading about the step does not produce that kind of detail.

Central Finance is a different hire

Central Finance is a deployment option with its own consultant profile, and it is the fork most often mistaken for a migration. SAP describes the purpose plainly: "With Central Finance, you can transition to a centralized SAP S/4HANA system or an SAP S/4HANA Cloud Private Edition system without disruption to your current system landscape, which can be made up of a combination of SAP systems of different releases and accounting approaches and non-SAP systems." (SAP Help Portal, Central Finance, 2026).

What you get out of it is a reporting layer. The same page describes a central reporting platform for FI and CO, with the option of a common reporting structure (SAP's Central Finance documentation). Source systems carry on running underneath it. Everything the group reads sits in one place.

Underneath, the plumbing is replication. "The journal entries are replicated from the third-party source system via the SAP Landscape Transformation Replication Server (SAP LT Replication Server) to the Central Finance system." (SAP's replication documentation). Mapping, error handling and cross-system data integrity become the daily work, which is a genuinely different job from configuring a company code.

The most useful screening question here is about what does not arrive. SAP's customising guidance says: "Replicated FI documents which originate from asset postings in the source system are not posted to Fixed Asset Accounting (FI-AA) in the Central Finance system." (SAP Help Portal, Customizing Settings for Asset Documents, 2026). So I ask what does not get posted centrally. In my experience the people who have delivered Central Finance volunteer a boundary like this one before I finish the question, because it is the sort of thing that cost them a weekend once.

Group Reporting is a third hire

Consolidation is a third profile, and SAP's own product history explains why a consolidation CV needs dating. Two predecessor solutions were deprecated on the same release. "The Real-Time Consolidation solution is deprecated starting with SAP S/4HANA 2022. The replacement solution is SAP S/4HANA Finance for Group Reporting." (SAP's deprecation notice for Real-Time Consolidation).

Business Consolidation carries the identical notice, on the identical release, naming the identical replacement (SAP Help Portal, deprecation notice, 2023). Anyone whose consolidation career was built on RTC or BCS has had to move product to stay current, which is worth checking on the CV.

The architecture is the part that matters to a hiring manager. SAP's training material puts it this way: "SAP S/4HANA Cloud for group reporting is an integrated consolidation solution for consolidated financial statements and group reporting." (SAP Learning). The same course notes that "consolidation takes place directly in the operational SAP S/4HANA system" (SAP Learning course on group reporting), which is why the skill sits close to the FICO team without being the same skill.

In an interview, look for a named task. "With Release Universal Journal, you release the reported financial data from the universal journal in accounting for consolidation purposes." (SAP Help Portal, Release Universal Journal, 2026). Naming the task is the easy half; I follow it with what goes wrong inside the step, because that is the part you cannot get from a job description. Plenty of capable core FICO consultants have never touched it. It belongs to a different shortlist.

That fork is also where I most often talk a client out of a hire. If consolidation still runs outside S/4HANA and the group close is not moving this year, a Group Reporting specialist is a role you are creating for a problem you do not yet have. Scope the core FICO seat properly, and buy the consolidation expertise in for the weeks it is genuinely needed.

How to screen an SAP FICO hire

Screen for architecture first and module labels second, because those four letters now cover three separate jobs. Before anything below, decide whether you are hiring core FICO in S/4HANA, Central Finance, or Group Reporting. Briefing all three as one search is the most common reason I see an SAP finance hire drift, and it is the case I make at length for screening depth over CV volume. The drift is quiet: nobody notices for weeks, because every CV arriving is technically on-brief. The rest of the module map sits on my SAP and ERP recruitment page.

1. Listen for the noun. Journal entry is current language. The accounting document and the CO document is ECC language, because those documents "have been superseded by journal entries" (the Universal Journal FAQ). No technical knowledge needed on your side to hear the difference.
2. Probe what did not get replaced by ACDOCA. A strong answer names BSEG as a table that survived and describes compatibility views separately. A weak one says everything is in one table now.
3. Walk through the New Asset Accounting migration. Classic Asset Accounting is gone from S/4HANA entirely, so this is a real project step with a sequence. Ask how that sequence ran on their last project.
4. Test the Central Finance boundary. Replicated FI documents originating from asset postings do not post to FI-AA in the Central Finance system. Ask what does not arrive centrally, and listen for whether the boundary comes from memory or guesswork.
5. Name-check Release Universal Journal. For a Group Reporting role, recognising the task takes ten seconds; the useful part is what they say goes wrong inside it.

This is the same failure mode I wrote about in why SAP EWM consultants are so hard to hire, where the module name survives the keyword search intact. On a conversion programme it compounds, for the reasons I set out in hiring for an S/4HANA brownfield migration.

Common questions about hiring SAP FICO consultants

What is the difference between SAP FICO in ECC and in S/4HANA?

The data model. In S/4HANA the FI and CO data structures are combined into a single line-item table, ACDOCA, which replaces the previously separate physical tables (SAP's Universal Journal FAQ, 2026). Practically, the reconciliation between financial and management accounting that shaped ECC-era finance work is designed out of the system, and the language around postings changed with it.

Is Central Finance the same as an S/4HANA migration?

No. Central Finance takes you to a central S/4HANA system "without disruption to your current system landscape" (SAP Help Portal, Central Finance, 2026), with journal entries replicated in via SAP LT Replication Server while the source systems keep running. It gives you a "Central Reporting Platform for FI/CO". It does not convert the systems feeding it, which is why the consultant profile differs from a conversion project.

Do we need a Group Reporting specialist?

Only if you consolidate inside S/4HANA. In group reporting, "consolidation takes place directly in the operational SAP S/4HANA system" (SAP Learning), and the solution replaced both Real-Time Consolidation and Business Consolidation from SAP S/4HANA 2022. If your consolidation still runs elsewhere, a core FICO hire is the right call and the specialist can wait until it doesn't.

What should we budget for an SAP FICO consultant?

There is no methodologically sound public salary figure for this niche, and saying so is more useful to you than repeating one. A number worth benchmarking against needs four things: a named collecting body, a disclosed sample size, a disclosed collection window, and a stated caveat about self-reported data. The SAP FICO figures I can find on the open web carry none of the four. Benchmark against your own last two finance offers instead, and against what candidates in live processes tell you they turned down.

Does FICO still exist as a role?

Yes, and the title survived the architecture change untouched, which is precisely the problem. SAP still documents the universal journal as the book of original entry for both FI and CO (SAP Help Portal, 2026), so the two disciplines share one posting layer while the job title still names them separately. Treat "SAP FICO" on a CV as where the conversation starts.

---

If you're scoping an SAP finance hire and you're not yet certain whether it is core FICO, Central Finance or Group Reporting, tell me about the role. I run two to four active searches at a time, which is why that scoping conversation happens before any CVs do.