SAP FICO interviews test two things: whether you understand the finance processes behind the system (record-to-report, procure-to-pay, order-to-cash) and whether you can configure and troubleshoot them in SAP S/4HANA. The questions below move from SAP FI and SAP CO basics for freshers to Universal Journal, document splitting, closing and migration topics for experienced consultants.
The scenario-based section mirrors what client and project-manager rounds actually ask: a cost posted to the wrong cost center, a payment run that skipped vendors, a GR/IR account that will not clear. Practise explaining your approach step by step, because the reasoning is what gets scored.
Answers reflect SAP S/4HANA terminology. Transaction codes, menu paths and cloud features can vary by release and edition, so confirm details in your project system.
Start here if you are new to SAP Finance or moving from accounting into SAP. These SAP FI and SAP CO interview questions check vocabulary, organisational structure and the basic posting logic.
SAP FICO combines two components. FI (Financial Accounting) records business transactions for external, statutory reporting: General Ledger, Accounts Payable, Accounts Receivable, Asset Accounting and bank accounting. CO (Controlling) supports internal management reporting: cost centers, internal orders, profit centers, product costing and profitability analysis.
| SAP FI | SAP CO | |
|---|---|---|
| Audience | Auditors, tax authorities, shareholders | Internal managers |
| Key outputs | Balance sheet, P&L, tax reports | Cost center reports, margins, product costs |
| Main objects | G/L accounts, vendors, customers, assets | Cost centers, internal orders, profit centers |
In SAP S/4HANA both write to the same line-item table, the Universal Journal (ACDOCA), so FI and CO no longer need a separate reconciliation.
A company code is the smallest organisational unit for which a complete, self-contained set of accounts can be produced for external reporting, typically one legal entity. It is defined with its country, currency and language, and then assigned to a chart of accounts, a fiscal year variant, a posting period variant, a field status variant and a controlling area.
Example: an Indian group with a manufacturing entity and a separate services entity would normally have two company codes, because each files its own statutory financial statements.
LinkA company represents a group-level consolidation unit and can contain one or more company codes. It is mainly used for consolidation and trading partner reporting. A company code is the legal entity level at which balance sheets and P&L statements are prepared. Defining a company is optional; defining a company code is mandatory.
LinkA chart of accounts is the list of G/L accounts available to one or more company codes. SAP supports three types:
Several company codes can share one operating chart of accounts, which keeps reporting consistent across a group.
LinkA fiscal year variant defines how many posting periods a company code has and how they map to calendar dates. SAP allows up to 12 regular periods plus up to 4 special periods used for year-end adjustments. An Indian company following an April–March financial year uses a non-calendar variant (commonly V3), while a calendar-year company uses K4.
A posting period variant controls which periods are open for posting. It is assigned to company codes, and periods are opened or closed in OB52. You can set different ranges by account type (+ for all, A assets, D customers, K vendors, M materials, S G/L) and restrict certain periods to an authorisation group, for example allowing only the finance closing team to post into the prior month.
A field status variant is a collection of field status groups assigned to a company code. A field status group is set in the G/L account master and decides whether fields such as cost center, business area or text are required, optional or suppressed when posting to that account. Posting keys have their own field status, and SAP combines both; if one setting says *required* and the other says *suppressed*, the posting raises an error.
LinkA posting key is a two-character code that controls the debit or credit side, the account type that can be posted, and which fields appear on the line item. Common examples:
40 / 50 – G/L debit / credit31 / 21 – vendor invoice (credit) / vendor credit memo (debit)01 / 11 – customer invoice (debit) / customer credit memo (credit)70 / 75 – asset debit / creditA document type classifies accounting documents and controls the number range, the account types allowed and the reversal document type. Typical examples: SA G/L posting, KR vendor invoice, KZ vendor payment, DR customer invoice, DZ customer payment, AA asset posting, WE goods receipt and RE logistics invoice receipt.
A reconciliation account is a G/L account that is linked to a subledger such as customers, vendors or assets. Every subledger posting updates it automatically in real time, so the G/L always matches the subledger. You cannot post directly to a reconciliation account; it is entered in the business partner (company code data) or determined through asset class account determination.
LinkOpen item management means line items on an account remain *open* until they are cleared against offsetting items. It is used for accounts such as GR/IR clearing, bank clearing and salary payable, where you need to see what is still outstanding. Customer and vendor accounts are always managed on an open item basis. Switching open item management on for an account that already has postings requires a dedicated conversion, so it should be decided during design.
LinkIn S/4HANA the Business Partner (transaction BP) is the single entry point for customers and suppliers. Customer–Vendor Integration (CVI) keeps the classic customer and vendor tables synchronised in the background. A business partner can hold several roles, for example FLVN00 (FI vendor) and FLVN01 (supplier for purchasing), or FLCU00 (FI customer) and FLCU01 (customer for sales). BP groupings control number ranges.
Tolerances limit what users can post and how payment differences are handled:
These are both a control (preventing a junior user from posting large amounts) and a convenience (automatic write-off of small differences).
LinkA cost center is an organisational unit in Controlling where costs are incurred, usually a department, function or location such as *Finance Bangalore* or *Plant Maintenance*. It belongs to a controlling area and company code, is linked to a profit center and must sit in the standard hierarchy. Managers use cost center reports to compare plan and actual overhead costs.
LinkA profit center is a management-oriented unit that is responsible for both revenues and costs, for example a product line or region. Cost centers only collect costs; profit centers allow an internal P&L and selected balance sheet items. In S/4HANA, profit center values are stored in the Universal Journal, so there is no separate classic profit center ledger.
LinkA controlling area is the organisational unit in which cost accounting is performed. Several company codes can be assigned to one controlling area for cross-company cost accounting, provided they use the same operating chart of accounts and fiscal year variant. Using one controlling area across a group lets you allocate costs between legal entities.
LinkFor candidates with project or support exposure. These questions test configuration knowledge, integration and how S/4HANA changed classic SAP Finance.
The Universal Journal (table ACDOCA) is the single line-item table in SAP S/4HANA for G/L, Controlling, Asset Accounting, Material Ledger and margin analysis. Each line carries G/L, CO and market-segment fields together, so finance and management reports read from one source of truth.
Practical impact:
Cost elements are no longer separate master records. They are G/L accounts created in FS00 with account type *Primary costs or revenue* or *Secondary costs*, and a cost element category. Examples: category 1 primary costs, 11 revenues, 21 internal settlement, 42 assessment and 43 internal activity allocation. The older transaction KA01 is not used for maintenance in S/4HANA.
In FS00 the G/L account type decides how the account behaves:
Newer releases also offer a cash account type for bank-relevant accounts.
LinkDocument splitting divides line items by characteristics such as profit center or segment so that a complete balance sheet can be produced for each characteristic, not just a P&L.
Example: a vendor invoice of ₹1,00,000 has two expense lines, ₹60,000 for profit center A and ₹40,000 for profit center B. With document splitting active, the vendor line and the tax line are split 60:40 as well, so each profit center shows its share of the liability.
Key configuration elements: splitting method, item categories for G/L accounts, business transaction variants, document splitting characteristics (with *zero balance* and *mandatory* flags), a zero-balance clearing account, and inheritance or default account assignment.
Link0L)** – mandatory; represents the group's primary accounting principle and is fully integrated with CO.0L and local GAAP in a second ledger.MIGO, movement type 101) – Dr Inventory (BSX), Cr GR/IR clearing (WRX).MIRO) – Dr GR/IR clearing, Cr Vendor; any price difference goes to inventory or a price difference account (PRD), depending on price control and stock coverage.F110 or manual) – Dr Vendor, Cr Bank.Accounts are determined automatically through OBYC using the valuation class of the material and the transaction key.
OBYC, transaction keys GBB and BSX).VF01) – Dr Customer, Cr Revenue and output tax. Revenue accounts come from VKOA based on chart of accounts, sales organisation, customer and material account assignment groups, and the account key from the pricing procedure (for example ERL for revenue, ERS for sales deductions).F110 selects due open items for vendors (and customers, for refunds), creates payment documents and generates payment media.
Configuration (in FBZP) covers: all company codes, paying company codes, payment methods per country and per company code, bank determination (ranking order, bank accounts, available amounts, value days) and house banks.
Run steps: maintain parameters (run date, identification, next payment date, company codes, payment methods, vendor range) → proposal → review and edit proposal → payment run → print forms or create the payment medium file (DMEE).
LinkA house bank is a bank where the company code holds accounts. Each house bank can have several accounts identified by an account ID, and each account is linked to a G/L account. In S/4HANA, bank accounts are maintained through Bank Account Management (for example the *Manage Bank Accounts* Fiori app), while house banks are still used in payment configuration.
LinkA dunning procedure defines dunning levels, the interval between runs, minimum amounts and interest, charges and the letter text for each level. The procedure is assigned to the customer in the business partner (company code data). The dunning run (F150) follows the same pattern as the payment run: parameters, proposal, edit, print.
Asset Accounting in S/4HANA (sometimes called *new asset accounting*) posts acquisition and production costs in real time to all relevant depreciation areas and ledgers. Key elements:
AFAB), which posts depreciation for each period.The asset explorer (AW01N) shows planned and posted values for an asset.
A parked document is saved without updating balances; it receives a document number and can be completed, changed or posted later, often by another user as part of an approval process. A held document is a temporary save for the same user, without a document number and without validation. Parking is used for maker–checker control; holding is simply a "save draft" convenience.
LinkBoth are defined with prerequisites and can run at document header, line item or complete document level. In newer S/4HANA releases, Fiori apps are also available for managing validation and substitution rules.
LinkAt period end, open items and balances held in foreign currency are revalued at the current exchange rate (transaction FAGL_FCV in S/4HANA). Configuration includes the valuation method, exchange rate type, and the accounts for unrealised gains and losses. Realised gains or losses are posted at clearing. Valuations of open items are commonly reversed at the start of the next period so they are recalculated on fresh rates.
Internal orders collect costs for a specific job, event or short project, for example a trade fair or a machine overhaul. They can be statistical (for reporting only, the real posting stays on the cost center) or real (costs settled later). Order types control number ranges, settlement profile and budget profile. Settlement (KO88 for an individual order) moves costs to receivers such as cost centers, G/L accounts, fixed assets or profitability segments.
Margin analysis (account-based CO-PA) posts profitability data into the Universal Journal using G/L accounts plus market segment characteristics such as customer, product and region. It reconciles with FI by design and is SAP's strategic direction in S/4HANA. Costing-based CO-PA uses value fields and separate tables; it is still available in S/4HANA on-premise but is not part of the Universal Journal. Many projects activate margin analysis and keep costing-based CO-PA only where specific requirements exist.
LinkThese SAP FICO interview questions for experienced candidates (typically 4+ years) focus on closing, S/4HANA design decisions, migration and cross-module finance processes. Interviewers expect you to talk from project experience.
A typical sequence, adjusted to each client's calendar:
OB52; MM period via MMPV).AFAB).FAGL_FCV).Many companies orchestrate these tasks with SAP's financial closing tools so that dependencies, owners and status are visible.
LinkThe Material Ledger records inventory values in multiple currencies and valuations. In S/4HANA it is mandatory for inventory valuation, while actual costing is optional. With actual costing active, the periodic costing run distributes purchase price and production variances to inventory and cost of goods sold, giving an actual periodic unit price at month end.
LinkACDOCA) for FI, CO, AA, ML and margin analysis.For companies that want to redesign as well as convert, a selective data transition is an alternative to a pure system conversion.
LinkCentral Finance replicates financial postings from multiple source systems (SAP ECC, SAP S/4HANA or non-SAP) into a central S/4HANA system in near real time, typically using SAP Landscape Transformation (SLT). Mapping of master data and organisational units is required, and replication errors are monitored centrally. Organisations use it for group-wide reporting, centralised processes such as payments, or as a stepping stone towards a full S/4HANA landscape.
LinkSAP Credit Management (part of FIN-FSCM) manages credit exposure per business partner and credit segment. Credit limits can be calculated with scoring rules or maintained manually. During sales order processing a credit check is triggered; if the check fails the order is blocked and a documented credit decision can be created for the credit analyst to release or reject. Classic SD credit management is not available in S/4HANA.
Link0L for IFRS, another ledger for local GAAP). Valuation-specific postings are made to the relevant ledger only, and reports are run per ledger.The ledger approach gives cleaner reporting but more ledgers to maintain; the accounts approach is simpler but inflates the chart of accounts.
LinkIn S/4HANA, CO postings are stored in the Universal Journal in real time. When a CO allocation crosses company codes, profit centers or functional areas, the corresponding FI entries are generated automatically, including intercompany clearing where required. This replaces the classic reconciliation ledger used in older releases.
LinkCK11N for one material, CK40N for mass costing) uses the BOM, routing, activity prices and overhead to calculate the standard price. Marking and releasing the estimate updates the material master.Cross-company postings use intercompany clearing accounts so each company code stays balanced. Intercompany sales use a trading partner on the business partner, which is carried into the journal entry for later elimination. Reconciliation compares receivables and payables between entities; S/4HANA offers intercompany matching and reconciliation tools, and consolidation (for example SAP S/4HANA Finance for group reporting) eliminates the balances.
LinkEach country uses a tax calculation procedure assigned in configuration. Tax codes are defined per country with rates and account keys, and G/L accounts for each account key are determined automatically. For India, GST is handled with separate components for CGST, SGST/UTGST and IGST, with business places and GSTIN-relevant settings. Withholding tax (TDS) is handled with extended withholding tax: withholding tax types, codes and assignment to suppliers.
LinkFAGLGVTR), with P&L balances moving to the retained earnings account.Start with legal and reporting requirements: each legal entity becomes a company code; currencies, fiscal year and chart of accounts strategy follow. Then decide controlling area scope (usually one per group for cross-company allocations), profit center and segment design for management and segment reporting, and how plants and sales organisations map to company codes. Validate the design in fit-to-standard workshops, and leave room for acquisitions or new entities.
LinkA segment is a reporting dimension for segment reporting under IFRS 8 and similar standards. It is typically derived from the profit center master record and can be a document splitting characteristic, so a balance sheet and P&L can be produced per segment.
LinkACDOCA – Universal Journal line items.BKPF / BSEG – document header and entry view line items.BSID, BSAD, BSIK, BSAK – open and cleared customer and vendor items; available as compatibility views in S/4HANA.SKA1 / SKB1 – G/L account master (chart of accounts / company code level).BUT000 – business partner general data; KNA1 / LFA1 – customer and supplier general data.CSKS – cost center master; CEPC – profit center master; T001 – company codes.Real-world situations from implementation and support projects. There is rarely one correct answer; interviewers want a structured approach, awareness of controls and a sensible fix.
MIRO) or an FI invoice, and whether it is paid or in a closed period.KB61, or the corresponding Fiori app for reassigning costs). The supplier balance and tax remain untouched.MR8M for logistics invoices, FB08 for FI documents) and repost correctly.OKB9), substitution rules or user training.Start with the payment run's exception list in the proposal log, then check:
MR11) to write them off.SAP has separate period controls, so check the one that matches the transaction:
OB52) for the account type and the user's authorisation group.MMPV / MMRV) for goods movements and logistics invoices.OKP1) for specific CO business transactions.Also check whether the user is trying to post into a special period that is only open to the closing team.
LinkReason codes can be configured to charge off differences to specific G/L accounts.
LinkCheck the asset master in the asset explorer (AW01N): depreciation key, useful life, capitalisation date and acquisition values. Correct the master data, recalculate depreciation if needed, and then rerun depreciation for the period. In S/4HANA the run posts the difference between already-posted and newly calculated values. If the issue affects many assets, analyse whether the asset class defaults or a mass change caused it.
Check the exchange rates and rate type used (OB08), the valuation method and key date, the accounts assigned for gains and losses, and whether the previous period's valuation was reversed. Confirm the run was executed for the correct ledgers and valuation areas. Always run in test mode first; if the posting is wrong, reverse it and rerun after correcting the cause.
An internal order with an order type that includes a budget profile and availability control. Costs are posted directly to the order, the budget is maintained on the order, and availability control warns or stops postings when tolerance limits are reached. At period end, the order is settled to a cost center or to profitability analysis. If the campaign has several phases and deliverables, a WBS element in Project System may be a better fit.
LinkImmediate action: identify both payment documents and contact the supplier for a refund or to offset against future invoices. In SAP, reset clearing (FBRA) on the duplicate payment if needed and post the refund or offset. Root cause: check whether the invoice was entered twice with different references, and whether duplicate invoice checks are active in the supplier master and logistics invoice verification settings. Recommend controls such as mandatory reference fields.
Common causes are document splitting not being active, profit center not defined as a mandatory splitting characteristic with zero-balancing, or balance sheet postings without a profit center (for example manual journal entries or migrated balances). Check splitting configuration, add validations to make profit center mandatory, and correct historical postings. Activating document splitting retrospectively is a project in itself and should be planned carefully.
LinkDisplay the document (FB03 or the *Manage Journal Entries* app) to show who posted it, when, the document type, reference and header text. Show change documents, any attachments, and the approval history if the document was parked and approved. Explain which validations applied. Good practice is to make reference, text and attachments mandatory for manual journal entries above a threshold.
Hands-on questions about transactions and configuration. In S/4HANA many processes also have Fiori apps; know both where your project used them.
| Area | Transactions |
|---|---|
| G/L master and postings | FS00, FB50, F-02, FB03, FB08 |
| AP / AR | FB60, FB70, F-53, F-28, F110, F150 |
| Line items | FBL1N, FBL3N, FBL5N (or the Fiori line item apps) |
| Periods and close | OB52, FAGL_FCV, FAGLGVTR |
| Assets | AS01, AW01N, AFAB |
| Controlling | KS01, KSB1, KO88, KB21N |
Payment terms are defined in OBB8: day limits, baseline date calculation, and cash discount percentages with their days, for example *2% within 10 days, net 30*. Instalment payment terms are defined separately in OBB9. Terms are entered in the business partner and copied into invoices, where they can be changed.
OBYC maps transaction keys to G/L accounts by chart of accounts, valuation grouping code (if active) and valuation class. Important keys: BSX inventory, WRX GR/IR clearing, PRD price differences, and GBB offsetting entries with account modifiers such as VBR (consumption) and VAX (cost of goods sold). The valuation class comes from the material master and is linked to material types through the account category reference.
VKOA uses the condition technique. The access sequence checks tables such as *customer account assignment group / material account assignment group / account key*, and the account key (for example ERL) comes from the pricing procedure. When a billing document cannot be released to accounting, missing VKOA entries are one of the first things to check.
Number range intervals are defined per company code and fiscal year (or for all years) and assigned to document types. Intervals can be internal (system assigned) or external (user or interface assigned). Keep separate ranges for supplier invoices, customer invoices and G/L postings so audit trails stay clear.
LinkDistribution moves primary costs from a sender cost center to receivers while keeping the original cost element, so receivers see exactly which costs they received. Assessment moves costs using a secondary cost element (category 42), which summarises costs and is simpler to report. Both are cycle-based and run at period end; distribution is limited to primary costs.
An activity type (for example *machine hours* or *consulting hours*) represents output from a cost center. A plan activity price is set per cost center and activity type, and direct activity allocation (KB21N) or confirmations from production and maintenance orders credit the sender cost center and debit the receiver using a secondary cost element of category 43.
A financial statement version (FSV) defines the hierarchy of G/L accounts for the balance sheet and P&L, including nodes for profit and loss result and items whose position depends on the balance (debit or credit). It is used by financial statement reports and is often aligned with the statutory reporting format of each country.
LinkCreate the tax code for the country (FTXP), choose the tax type (input or output), maintain percentage rates against the condition types of the tax procedure, and make sure account keys have G/L accounts assigned (OB40). Test with a supplier and customer invoice and check the tax lines and reporting fields.
Testing typically runs in layers: unit tests for individual configuration, integration tests across procure-to-pay, order-to-cash and record-to-report, then user acceptance testing with business users. Cutover rehearsals validate data migration, opening balances and reconciliations. Keep test scripts, expected accounting entries and evidence, because auditors may ask for them.
LinkA focused preparation plan beats reading hundreds of random questions. Use these steps in order, and spend most of your time on the parts you would struggle to explain out loud.
Revise accounting basics (double entry, accruals, depreciation, receivables and payables) and the SAP organisational structure. If you cannot explain why a reconciliation account exists, configuration questions will be difficult.
Walk through enterprise structure, G/L, AP, AR, asset accounting and the main CO objects in a sandbox. Note the configuration step and the business reason for each.
Use the scenario questions on this page. For each one, write the steps you would take, the transactions you would use and the risk you would avoid.
Draw the accounting entries for procure-to-pay, order-to-cash and production. Interviewers almost always test MM-FI and SD-FI account determination.
Learn to read message numbers, check period controls, analyse missing account determination and use line item reports. Support roles are largely about this.
Prepare a clear account of one implementation phase or a set of support tickets: your role, the problem, what you configured and the result. Be honest about what you did personally.
Every tool and process on your resume is fair game. Prepare a two-minute project summary and examples in situation–action–result form.
Know the S/4HANA changes, key tables, common Fiori apps and how you would write a functional specification for a report or enhancement. If you need structured practice on a live system, Aplus Edtech's SAP FICO training covers these configuration and integration topics hands-on.
Yes. Many companies are still moving from SAP ECC to S/4HANA; SAP has announced mainstream maintenance for core ECC releases until the end of 2027, with optional extended maintenance until the end of 2030. Finance is part of almost every SAP project, so consultants who understand S/4HANA Finance remain in demand.
It is possible but harder. Interviewers expect you to understand accounting concepts such as journal entries, accruals and reconciliations. Commerce, finance or CA/CMA backgrounds have an advantage; others should learn accounting basics alongside SAP.
Most companies run two to four rounds: a technical or functional round, a scenario or client round, and a managerial or HR discussion. Consulting firms often add a project deep-dive with a senior consultant.
S/4HANA Finance changes, document splitting, period-end close, integration with MM and SD, asset accounting, support ticket examples and at least one migration or rollout story. Expect scenario-based questions more than definitions.
Certification is not mandatory, but it can help freshers get shortlisted. Practical system knowledge and the ability to explain real scenarios matter more in interviews.
You do not need to write ABAP code, but you should be able to write functional specifications, understand enhancements such as BAdIs, and work with developers on debugging and reports. Basic table knowledge helps a lot.
If several answers on this page felt unfamiliar, the gap is usually hands-on practice rather than theory. Aplus Edtech's SAP FICO / S/4HANA Finance programme is instructor-led, with practice on SAP S/4HANA and real business scenarios, so you can walk an interviewer through what you configured, built or fixed.
Share your background and target role. An advisor will explain batch timings, curriculum and the right module for you.
Explore SAP Training +91 910-8249-111Last updated: · Prepared by the Aplus Edtech SAP training team.