Reading Path: FI-CA and Convergent Invoicing

In 30 seconds

What it is This path takes an FI-CA and Convergent Invoicing consultant through the 72-app FI-CA catalogue, the transaction lookup and corrections that qualify it, the scope decisions the wider programme is closing, and the cutover checks specific to FI-CA. Five pages, about 29 minutes.

You use it when You are an FI-CA or Convergent Invoicing consultant scoping, testing or handing over Fiori apps for business partner, contract account, billing and collections processes on an S/4HANA 2025 conversion or upgrade.

Guide covers Migration / Start Here

Five pages, about 29 minutes in total.

FI-CA and Convergent Invoicing Fiori Apps in S/4HANA 2025: 72 Apps by Task — 12 min. The full FI-CA and Convergent Invoicing app catalogue for this release, grouped by the task you already own.
Transaction Code to Fiori App Lookup for SAP Utilities and FI-CA (S/4HANA 2025) — 5 min. Cross-check the transactions your users run today against what the export associates with each app.
Reading the Fiori 2025 App List Correctly: 14 Corrections That Change Upgrade Scope — 4 min. Corrections that change how you should read the catalogue in step 1, before you shortlist anything.
Before an S/4HANA 2025 Upgrade: 8 Fiori and Scope Decisions to Close First — 5 min. The scope decisions the wider programme is closing that will shape what your FI-CA shortlist is allowed to include.
S/4HANA 2025 Cutover Validation for SAP Utilities and FI-CA: What to Test Separately — 3 min. What your test scripts need to cover separately for FI-CA before cutover sign-off.

FI-CA and Convergent Invoicing sit underneath Utilities billing on most conversion and upgrade programmes, which means an FI-CA consultant inherits volume and exception patterns set upstream in meter-to-cash. A generic finance or receivables reading of these Fiori apps misses that: FI-CA clarification cases, dunning and collections apps here are shaped by billing exceptions raised in IS-U, not by finance’s own transaction mix. Read the transaction lookup with that upstream link in mind.

The pages in this path draw on the SAP export of September 2026 for product 2025 (Private Cloud): 72 app records sit in the five FI-CA components FI-CA-FIO, FI-CAC-FIO, FI-CA-INV, FI-CA-INV-FIO and FI-CAX-INV-FIO, and 21 of the 72 carry a supplied transaction code across 18 distinct codes. The snapshot has not been revalidated against the live SAP Fiori Apps Reference Library.

Coming next for this role

Still to come that will extend this path: FI-CA transformation, and testing, cutover and hypercare.

S/4HANA 2025 Conversion and Upgrade journey map — the full workstream and phase view behind this path.

Frequently asked questions

Why does this path include a scope-decision checklist written for release upgrades?

Because scope decisions on Fiori for FI-CA are the same whether the programme arrived by system conversion or release upgrade. Read it for the decisions, not the journey it happens to be filed under.

Does the transaction lookup in step 2 cover FI-CA codes on its own?

It covers Utilities and FI-CA together in one table, so you will see IS-U rows alongside FI-CA ones. Use it to check your own FI-CA transactions. Do not expect any shared codes: in this export no transaction code appears on both an IS-U app and an FI-CA app, so the two areas' rows never meet on a code.