Financial Accounting — FI
General Ledger, AP, AR, FI-AA, bank, payments, closing and Universal Journal.
SAP FI is Financial Accounting. SAP CO is Controlling. SAP FICO is the commonly used combined term for FI + CO. It is not a separate SAP module.
SAP FI-CA is Contract Accounts Receivable and Payable. SAP RAR is Revenue Accounting and Reporting. Both are related SAP Finance capabilities on the same SAP S/4HANA 2023 practice environment. They are not FI or CO submodules.
One named login. Four related capabilities. Open the section you need.
General Ledger, AP, AR, FI-AA, bank, payments, closing and Universal Journal.
Cost centres, internal orders, product costing, actual costing, Margin Analysis, planning and settlement.
High-volume contract-account receivables and payables. Not standard FI-AR.
RAI, contracts, performance obligations, SSP, recognition and FI posting.
FI↔CO, FI↔MM, FI↔SD, FI-CA↔GL, RAR↔SD/FI. TRM and FSCM stay on their own pages.
FI
SAP FI is Financial Accounting: legal books, subledgers and financial statements on SAP S/4HANA. On this tenant you practise FI processes authorised for your user in SAP GUI and Fiori. Customer and vendor masters are Business Partner, not classic XD/XK-only ECC masters.
G/L accounts, journal entries, open-item G/L where used, clearing, document display and reversal, ledgers, and financial statements sit here. On SAP S/4HANA the operational posting table is the Universal Journal (ACDOCA). That does not mean every finance object in the product lives only there — asset, tax, and some subledger tables still exist beside it.
Start posting in FB50 or F-02. Display in FB03. Reverse with FB08. Line items: FBL3N. Balances: FS10N and FAGLB03. G/L master: FS00.
Supplier invoices, credit memos, open items, outgoing payments, automatic payment run, clearing, down payments and payment blocks. The supplier is a Business Partner with the supplier role. Display the BP/vendor in FK03 (or BP), post in FB60 or F-43, pay in F-53, list open items in FBL1N, run F110 (and F111 where authorised), clear in F-44.
Customer invoices, incoming payments, open items, partial and residual payments, clearing, dunning and down payments. The customer is a Business Partner with the customer role. Post in FB70 or F-22, incoming payment F-28, clear F-32, line items FBL5N, dunning F150.
FI-AA is the current name for Asset Accounting. FI-AM is a legacy label; do not use it as the module name. Practise asset master, asset class, acquisition, depreciation, transfer, retirement, Asset Explorer and the G/L integration. Masters: AS01 / AS02 / AS03. Depreciation: AFAB. Explorer: AW01N. Acquisition, transfer and retirement transactions such as ABZON, ABUMN and ABAON are SAP-supported — confirm on your user.
House banks, bank accounts, payment methods, payment processing, bank statements and reconciliation. Classic house-bank work still uses FI12 and statement entry such as FF67 where authorised. Bank Account Management in Fiori is the modern product path for bank-account master data. Use whichever interface your catalogs expose. Do not treat classic FI12 as a native Fiori app.
Posting periods, foreign-currency valuation, depreciation, AP/AR review, closing adjustments and reporting. Valuation: FAGL_FC_VAL. Period control OB52 is Customizing — use it only where authorised; it is not a customer posting transaction. Review balances in FS10N / FAGLB03 and open items in FBL1N / FBL5N.
Document splitting splits accounting lines (for example by profit centre) so documents stay balanced at those dimensions. You can observe it on posted Universal Journal documents where the company code is configured for it. This page does not claim Customizing of split characteristics.
Tax codes on FI documents, line-item tax views in FBL3N, and tax-on-sales/purchases reporting (S_ALR_87012357) where authorised. FTXP is tax-code Customizing, not a posting drill. This is not a statutory tax-return product.
On SAP S/4HANA, FI and CO actuals share the Universal Journal. A vendor invoice with a cost centre updates Financial Accounting and Controlling actuals on the same document. ACDOCA is the operational line-item table for that journal. Totals, configuration, and some subledgers still have their own objects — do not say “everything in finance is stored only in ACDOCA”.
CO
SAP CO is Controlling: management accounting on the same named login as FI. You practise cost objects, allocations, product costs, actual costing, profitability and settlement where authorised. This section replaces the former commercial CO hub after migration.
Cost-centre master data, actual postings, planning, allocations and activity allocation. Masters: KS01 / KS02 / KS03. Actual line items: KSB1. Manual repost: KB11N. Activity allocation: KB21N. Assessment KSU5, distribution KSV5. Planning: KP06 (separate from the actuals drill). Activity price: KP26.
Order master, actual costs, planning and settlement. Create/change/display: KO01 / KO02 / KO03. Line items: KOB1. Settlement: KO88.
Profit centres for responsibility reporting on the Universal Journal. Master: KE51. Line items: KE5Z. Manual postings such as 9KE0 where authorised. Segment / profit-centre reporting sits with FI on the same login.
Cost estimates, standard costing, costing runs and production integration where a BOM and routing exist. Estimate: CK11N / display CK13N. Costing run: CK40N. Material cost analysis: CKM3N. Manufacturing depth stays on SAP PP.
Material Ledger actual costing, price differences and periodic actual cost calculation as provisioned. Cockpit: CKMLCP. Material display: CKM3 / CKM3N. A complete actual-costing close is an SAP product capability — confirm the run on your user rather than treating it as a guaranteed lab.
On SAP S/4HANA, account-based profitability is Margin Analysis on the Universal Journal. Classic costing-based CO-PA may still exist in the product. Characteristics, contribution/margin reporting and line items: KEA0, KE21N, KE24 / KE24N, KE30 / KE30N. SD billing can feed characteristics where configured.
Cost-centre planning KP06, activity-price planning KP26, order planning KPF6. Planning is not the same drill as KB11N actuals.
Assessments (KSU5), distributions (KSV5) and activity allocations (KB21N). Cycles must exist on the tenant; confirm before you treat a cycle as a guaranteed exercise.
Internal-order settlement KO88. WBS settlement CJ88 is Project System integration on the same user — depth stays on SAP PS. Production-order settlement is relevant where a PP order exists.
FICO
SAP FICO is the commonly used combined term for SAP Financial Accounting (FI) and SAP Controlling (CO).
FI is external accounting: legal books and subledgers. CO is internal accounting: cost objects, allocations and management reporting. Integrated postings with a cost assignment update both. The Universal Journal is why FI and CO are commonly learned and used together on SAP S/4HANA. You do not buy a second “FICO server” — this is one named login.
FI-CA
SAP FI-CA is designed for high-volume receivables and payables on contract accounts. It is not standard FI-AR. Utilities, insurance and similar contract-account industries are common examples; this hub is not an industry-marketing page.
Core objects: Business Partner, Contract Account, and Contract Object where used. You post FI-CA documents, work open items, clear, take payments, process returns, dunning and mass processing, then integrate to the General Ledger.
SAP-supported transactions commonly used in practice: FPE1 (post document), FPL9 (account display), FP06 (account maintenance / clearing). Payments, returns and dunning (for example FP05, FP09, FPVA) are SAP product capabilities — confirm executable status on your user. Do not mix these rows into the FI AP/AR table without the FI-CA label.
RAR
SAP RAR is Revenue Accounting and Reporting. It is not an FI submodule. It accounts for revenue contracts, performance obligations and recognition, then posts into Financial Accounting.
Source information from SD or other senders becomes Revenue Accounting Items (RAI). RAI processing is an SAP product capability. On this practice tenant, work the RAR contract and fulfilment apps as provisioned for your user.
A revenue contract holds the customer arrangement. Performance obligations (POBs) are the distinct promises to the customer. Fulfilment of a POB is what typically drives recognition.
Standalone selling price (SSP) is used to allocate transaction price to POBs. Allocation and reallocation after a contract modification are SAP product functions. Confirm the apps on your user.
Additions, changes and reassessment of POBs when the contract changes. Treat a full modification lab as product capability unless your user can run it.
Event-based or fulfilment-based recognition, recognised revenue, deferred revenue and accrued revenue. RAR posts into FI and supports reconciliation and period-end processing. Monitoring covers contracts, POBs, processing status and posting/recognition status in the RAR Fiori apps where assigned.
Verified on this practice environment: RAR is in the finance practice landscape; contract, POB and recognition flows are available through the provisioned RAR contract and fulfilment apps, with FI posting on the same named login. Company code, accounting principles, BRF+ rules, RAI types and exact POB logic are not published as tenant facts here — do not invent them. IFRS 15-style contract/POB/SSP drills use your own materials on the live system.
Integrated accounting and management reporting on the Universal Journal when a cost object is on the FI document.
Procurement, GR/IR, supplier liability, inventory and expense. Detail: SAP MM.
Billing, revenue, tax and customer receivable. Detail: SAP SD.
Sales source information, recognition, and FI posting from RAR on this login.
Contract-account subledger integration into the General Ledger.
The codes in the transaction table are SAP GUI transactions. Fiori is a separate interface on the same provision. Names below are current SAP product capabilities. Available Fiori applications depend on the business catalogs and roles assigned to the user. Tenant visibility is not claimed for every app — use the App Finder after login. Never treat a GUI transaction as a native F-number Fiori app.
F0717A) — current successor of F0717F0707A) — current successor of F0707. This is not F0718A.F2217)F0711)F0712)F1443A) — current successor of F1443. Native SAP Fiori (UI5) for cost-centre master data. Not a GUI transaction.F0963) — Fiori Launchpad reporting app (Web Dynpro). Not a native UI5 app and not KSB1.W0081) — Fiori Launchpad reporting app (Web Dynpro). Successor path versus older plan/actual tiles; confirm in App Finder.Available apps depend on assigned business roles and catalogs. Tenant visibility is not claimed for every Controlling app.
Contract-account and Revenue Accounting Fiori apps are SAP product capabilities. On this tenant use the FI-CA and RAR apps assigned to your user. Classic GUI (FPE1, FPL9, RAR monitoring) can also be launched from Launchpad — that does not make them native Fiori apps.
Prioritised transactions consultants actually run. The site-wide list is on SAP transaction codes. Customizing is labelled. Status means SAP-supported unless noted; confirm on your user.
Swipe sideways to see all columns
| Component | Area | Transaction | Purpose | Type | Tenant status |
|---|---|---|---|---|---|
| FI | GL | FS00 | G/L account master | SAP GUI | SAP-supported; confirm on your user |
| FI | GL | FB50 / F-02 | G/L document posting | SAP GUI | SAP-supported; confirm on your user |
| FI | GL | FB03 / FB08 | Display / reverse document | SAP GUI | SAP-supported; confirm on your user |
| FI | GL | FBL3N / FS10N / FAGLB03 | Line items and balances | SAP GUI | SAP-supported; confirm on your user |
| FI | AP | FB60 / F-43 / F-53 | Vendor invoice / outgoing payment | SAP GUI | SAP-supported; confirm on your user |
| FI | AP | FBL1N / F-44 / F110 | Vendor line items, clearing, payment run | SAP GUI | SAP-supported; confirm on your user |
| FI | AR | FB70 / F-22 / F-28 / F-32 | Customer invoice, incoming payment, clearing | SAP GUI | SAP-supported; confirm on your user |
| FI | AR | FBL5N / F150 | Customer line items / dunning | SAP GUI | SAP-supported; confirm on your user |
| FI | FI-AA | AS01 / AS02 / AS03 / AFAB / AW01N | Asset master, depreciation, explorer | SAP GUI | SAP-supported; confirm on your user |
| FI | Bank | FI12 / FF67 | House banks / statement entry | SAP GUI (classic) | SAP-supported; BAM Fiori may replace FI12 |
| FI | Closing | FAGL_FC_VAL | Foreign-currency valuation | SAP GUI | SAP-supported; confirm on your user |
| FI | Customizing | OB52 / OBA7 / OBD4 / OBH2 / FTXP / FBCJC2 | Periods, document types, account groups, number ranges, tax codes, cash journal | Customizing | Not advertised as customer posting; use only if authorised |
| CO | CCA | KS01 / KS03 / KSB1 / KB11N | Cost centre master and actuals | SAP GUI | SAP-supported; confirm on your user |
| CO | Allocations | KSU5 / KSV5 / KB21N | Assessment, distribution, activity allocation | SAP GUI | Cycles must exist; confirm on your user |
| CO | Orders | KO01 / KOB1 / KO88 | Internal order actuals and settlement | SAP GUI | SAP-supported; confirm on your user |
| CO | PCA | KE51 / KE5Z | Profit centre master / line items | SAP GUI | SAP-supported; confirm on your user |
| CO | Costing | CK11N / CK13N / CK40N / CKM3N / CKMLCP | Estimates, costing run, actual costing | SAP GUI | SAP-supported; CKMLCP close not guaranteed |
| CO | CO-PA | KEA0 / KE21N / KE24N / KE30N | Operating concern, actuals, reports | SAP GUI | SAP-supported; confirm on your user |
| CO | Planning | KP06 / KP26 | Cost centre / activity-price planning | SAP GUI | SAP-supported; confirm on your user |
| FI-CA | Documents | FPE1 / FPL9 / FP06 | Post, account display, clearing | SAP GUI | SAP-supported; confirm executable on SSA user |
| RAR | Contracts | RAR contract / fulfilment Fiori | Contracts, POBs, recognition, FI posting | Fiori (product) | As provisioned; no unpublished company-code/BRF+ claims |
Seven drills. After portal credentials, use SAP GUI or Fiori with your own materials.
Display the supplier, post FB60, display FB03, pay or clear with F-53 / F-44 or F110. Reverse with FB08 to repeat.
Post FB70, incoming payment or partial in F-28, open items in FBL5N, dunning F150 where authorised, clear F-32.
Create or display an asset, post acquisition, run AFAB, then transfer or retire and read AW01N.
Display a cost centre in KS03, repost with KB11N, review KSB1, then run an assessment/distribution cycle if one exists.
Create a cost estimate in CK11N where BOM/routing exist, or settle an internal order with KO88.
Post in FPE1, display FPL9, clear or maintain in FP06. Add payment or dunning only if those transactions open on your user.
Open a revenue contract, identify a POB, process fulfilment, recognise revenue, then display the FI follow-on. Stop if the provisioned apps do not expose that step.
Certification stays on dedicated pages. This purchase is the live SAP user. Official exams, vouchers, coaching, dumps and pass guarantees are not included.
Certification practice hub · Certification guide · Access plans
Rehearse Financial Accounting, Controlling and the combined FICO flow on one named login, with your own materials.
Work contract accounts and revenue accounting as provisioned. Not a dedicated utilities or IFRS project landscape.
Finance key users and people using their own SAP Learning materials. The exam is not in the box.
Not a local SAP install. Browser path: access without install. A short trial login is available on request.
Finance hub last reviewed: 30 August 2026 · Live system: SAP S/4HANA 2023
Also searched
FICO practice on this site is the live SAP S/4HANA 2023 tenant — not a classic ECC 6.0 or IDES system.
Live now Named login to SAP S/4HANA 2023
Not a live product here ECC 6.0 and IDES are comparison pages, not hosted tenants
SAP FICO is the commonly used combined term for SAP Financial Accounting (FI) and SAP Controlling (CO). It is not a separate SAP module.
No. FI and CO are the modules. FICO is the combined name people use when they practise both on one system.
SAP FI is Financial Accounting — legal books and subledgers. SAP CO is Controlling — cost objects, allocations and management reporting. On S/4HANA they share the Universal Journal.
Financial Accounting. Main areas on this hub: General Ledger, Accounts Payable, Accounts Receivable, Asset Accounting (FI-AA), Bank Accounting, payments and closing.
GL, AP, AR, FI-AA, bank accounting, payment processing and financial closing, plus Universal Journal postings.
ACDOCA is the Universal Journal line-item table on SAP S/4HANA. FI and CO actuals share it. It is not the only table in finance.
FI-AA is Asset Accounting: asset master, acquisition, depreciation, transfer and retirement. FI-AM is a legacy name.
Operationally you work Business Partner with customer and supplier roles. Classic FK03/XD display may still open. You do not maintain separate ECC-only XD01/XK01 as the S/4HANA master path.
Yes. Vendor invoice to payment and customer invoice to incoming payment/dunning are on this login where authorised.
Cost Center Accounting, internal orders, profit centres, product costing, actual costing/Material Ledger, Margin Analysis, planning, allocations and settlement.
Cost centres collect overhead continuously. Internal orders collect costs for a job or event and then settle.
Profitability analysis. On S/4HANA, account-based profitability is Margin Analysis on the Universal Journal. Classic costing-based CO-PA may still exist in the product.
Material Ledger actual costing: periodic actual costs and price differences. CKMLCP is the cockpit. Confirm the close on your user.
Contract Accounts Receivable and Payable — high-volume contract-account subledger work. Not standard FI-AR.
FI-AR is standard Accounts Receivable. FI-CA uses contract accounts, mass processing and a different document model, then posts to the G/L.
The FI-CA account object that holds open items for a Business Partner contract relationship. Display it in FPL9 where authorised.
Revenue Accounting and Reporting. It manages revenue contracts, performance obligations and recognition, then posts to FI. It is not an FI submodule.
A performance obligation is a distinct promise in a revenue contract. Fulfilment of a POB typically drives recognition in SAP RAR.
Standalone selling price. RAR uses SSP to allocate transaction price to performance obligations. Confirm the apps on your user.
No training, exams, vouchers or dumps are included. After portal credentials use SAP GUI for HTML and Fiori in the browser. A desktop GUI file is in the portal if you want it.
Same full system on every plan — pick duration, checkout once, credentials in minutes.
View S/4HANA access plans