SAP S/4HANA Finance (FICO) Interview Questions for Freshers

25 SAP S/4HANA FICO interview questions freshers actually face — enterprise structure, the Universal Journal, Business Partner, document splitting, asset accounting, MM-FI integration and period-end closing — with clear answers and notes on what interviewers are checking.

  SAP Training   Oct 13, 2026   6  Add to Reading List
Quick Answer: S/4HANA FICO interviews for freshers cover four areas — enterprise structure (company code, chart of accounts, fiscal year), what changed in S/4HANA (Universal Journal, cost elements as GL accounts, Business Partner, New Asset Accounting), daily processes (procure-to-pay and order-to-cash entries, payments) and integration with period-end closing. Clear journal entries and one real scenario you configured matter more than memorised definitions.

SAP FICO remains one of the most hired-for SAP modules in India, and almost every opening now specifies S/4HANA. That shift has caught out many freshers: a large share of interview material online still describes ECC, and answers built on it — separate cost element master data, customer and vendor created in different transactions — immediately signal outdated preparation.

The 25 questions below are the ones freshers report most often, grouped the way interviews usually flow. Each answer is kept to what you would actually say, and where it helps there is a note on what the interviewer is listening for.

Part 1: Enterprise Structure and Basics (Q1–7)

Every FICO interview opens here. These look simple, but a fresher who answers them crisply sets the tone for the rest of the round.

Q1. What is a company code, and how does it relate to the client?

The client is the highest level in SAP — a self-contained unit with its own master data and configuration. A company code is the smallest organisational unit for which a complete, independent set of books can be drawn up for legal reporting: balance sheet and profit and loss. One client usually holds several company codes, for example one per legal entity in a group.

What they are checking: whether you tie company code to legal reporting, not just call it 'a company'.

Q2. What are the three types of chart of accounts?

The operating chart of accounts is used for daily postings and is assigned to the company code. The group chart of accounts supports consolidated reporting across company codes using different operating charts. The country chart of accounts meets local statutory requirements, with the GL account carrying an alternative account number to link the two.

Q3. What is a fiscal year variant?

It defines the fiscal year: how many normal posting periods there are, how they map to calendar months, and how many special periods are available for year-end adjustments. For a typical Indian company with an April-to-March year, the variant has 12 normal periods shifted so that April is period 1, plus up to four special periods.

Q4. What is a posting period variant, and why does it matter at month-end?

It controls which periods are open for posting, by account type, and is assigned to company codes. Finance teams open the new period and close the old one to stop back-dated entries after the books are finalised. In the classic GUI this is maintained in transaction OB52.

What they are checking: practical awareness — mentioning that periods can be opened separately for assets, customers, vendors and GL accounts is a strong detail.

Q5. What is a field status variant?

It groups field status groups, which decide whether each field on a posting screen is required, optional or suppressed. The field status group is assigned in the GL account master. If a cost centre must be entered for every expense posting, it is the field status group that enforces it.

Q6. What are document types and posting keys?

A document type classifies a business transaction — SA for GL postings, KR for vendor invoices, DR for customer invoices, AA for asset postings — and controls number ranges and which account types are allowed. A posting key, which belongs to the line item, determines debit or credit and the account type: 40 and 50 for GL debit and credit, 01 for a customer invoice debit, 31 for a vendor invoice credit.

Q7. What is a controlling area, and how does it relate to company codes?

The controlling area is the organisational unit for cost accounting, within which costs are allocated. One controlling area can include several company codes as long as they share the same operating chart of accounts and fiscal year variant. That condition is a common follow-up question.

Part 2: What Is Different in S/4HANA (Q8–14)

This section separates candidates who studied current material from those who learned from old ECC notes. Expect at least three of these in any interview for an S/4HANA role.

Q8. What is the Universal Journal?

The Universal Journal, table ACDOCA, is a single line-item table that holds financial accounting, controlling, asset accounting, material ledger and profitability data together. In ECC these were spread across separate tables that had to be reconciled. Now one posting creates one line item carrying all the dimensions — GL account, cost centre, profit centre, segment and more — so FI and CO reconcile by design. The header table BKPF still exists for document headers.

What they are checking: that you know the table name and can explain one practical consequence, such as no more FI–CO reconciliation at month-end.

Q9. How are cost elements handled in S/4HANA?

Cost elements are no longer separate master data. They are GL accounts, maintained in the GL account master (FS00). Primary cost elements are created as GL accounts of type 'primary costs or revenue', and secondary cost elements — used for internal allocations — as type 'secondary costs', with a cost element category set in the same master record.

Q10. What is the Business Partner, and why is it mandatory?

In S/4HANA, customers and vendors are created and maintained through the Business Partner (transaction BP) with roles such as FI Customer or FI Vendor. The classic customer and vendor tables still exist underneath, kept in sync through customer–vendor integration, but the Business Partner is the single point of maintenance. It also means one organisation that is both customer and supplier can be one business partner with two roles.

Q11. What are ledgers in S/4HANA, and what is the leading ledger?

A ledger holds a complete set of accounting figures. The leading ledger, usually 0L, follows the group's main accounting principle and is integrated with controlling. Non-leading ledgers support parallel accounting — for instance Ind AS in one ledger and IFRS group reporting in another. Extension ledgers store only adjustment postings on top of a base ledger rather than a full copy.

Q12. What changed in Asset Accounting?

New Asset Accounting is mandatory. Depreciation is posted to the GL in real time as values are calculated, with the periodic depreciation run (AFAB) posting the planned values per period. Parallel valuation is handled through depreciation areas tied to ledgers, and the old reconciliation between asset and GL balances is no longer needed because both sit in the Universal Journal.

Q13. What is Margin Analysis?

Margin Analysis is account-based profitability analysis in S/4HANA, and it is the recommended approach. Because it posts into the Universal Journal using GL accounts, profitability reconciles with the financial statements. Costing-based CO-PA still exists but runs in its own structures. Freshers should know the account-based approach is the default direction.

Q14. Is Material Ledger optional in S/4HANA?

No. Material Ledger is mandatory for inventory valuation, which means inventory can be valued in multiple currencies and valuations as standard. Actual costing, which recalculates actual material prices at period-end, remains optional and is activated separately.

Part 3: GL, AP, AR and Assets in Practice (Q15–20)

Q15. What is document splitting?

Document splitting divides line items by characteristics such as profit centre and segment, so that a balanced balance sheet can be drawn up for each of them, not only for the company code. For example, a vendor invoice for expenses across two profit centres has its payable line split across both. It is configured in the new GL and must be planned before go-live, because switching it on later is difficult.

What they are checking: whether you know why it exists — segment reporting under accounting standards — not just its name.

Q16. What is a tolerance group?

Tolerance groups set limits. Employee tolerance groups cap the amount a user can post per document or line item and the cash discount they can grant. Customer and vendor tolerance groups define acceptable payment differences, so a small short-payment can be cleared automatically and written off rather than left open.

Q17. Explain the procure-to-pay process from a finance view.

A purchase order is created in MM with no accounting entry. At goods receipt (MIGO), inventory or expense is debited and the GR/IR clearing account credited. At invoice verification (MIRO), GR/IR is debited and the vendor credited, with tax. At payment, usually through the automatic payment program F110, the vendor is debited and the bank credited. Being able to state each entry is the point of this question.

Q18. Explain order-to-cash from a finance view.

Sales order creation posts nothing. At goods issue, cost of goods sold is debited and inventory credited. At billing, the customer is debited and revenue and output tax credited. When payment arrives, the bank is debited and the customer cleared. Revenue account determination for billing is configured through VKOA.

Q19. What is the GR/IR account, and why does it need regrouping?

GR/IR clearing is an interim account that bridges goods receipt and invoice receipt. At period-end, open items may reflect goods received but not invoiced, or invoiced but not received. Regrouping reclassifies these balances to the correct balance sheet accounts so the statements show liabilities and receivables accurately.

Q20. What is the automatic payment program?

Transaction F110 selects open vendor items due for payment based on parameters such as company codes, payment methods and next run date, produces a proposal that can be reviewed and edited, then executes the payment run and creates payment media. House bank, payment method and ranking order configuration drive which bank pays which invoice.

Part 4: Integration and Period-End (Q21–25)

Q21. How does MM–FI integration work?

Through automatic account determination, configured in OBYC. Valuation class on the material master, movement type and transaction keys such as BSX for inventory, WRX for GR/IR and GBB for offsetting entries together decide which GL accounts a goods movement posts to. That is why a goods receipt posts to accounting without anyone selecting an account.

What they are checking: that you can name at least BSX and WRX. Interviewers love this question because it is where FI meets the business.

Q22. What are the main period-end closing activities?

Typical steps: post accruals and provisions, run depreciation, perform foreign currency valuation of open items (FAGL_FCV), regroup GR/IR, run assessment and distribution cycles in controlling, settle internal orders and projects, close and open posting periods, carry forward balances at year-end, and run reports such as the trial balance. In S/4HANA many of these are coordinated through Financial Closing cockpit tools and Fiori apps.

Q23. What is the difference between assessment and distribution?

Both allocate costs from a sender cost centre to receivers. Distribution passes primary costs on under their original cost elements, so receivers see the original nature of the cost. Assessment uses a secondary cost element, so receivers see one combined charge. Assessment is simpler to report; distribution preserves detail.

Q24. Which Fiori apps should a FICO fresher know?

At minimum: Manage Journal Entries, Display Line Items in General Ledger, Trial Balance, Manage Banks, and Display Financial Statement. Knowing that many GUI transactions still work but that clients increasingly run daily finance work through Fiori shows you understand current projects.

Q25. Tell me about a scenario you configured end to end.

This closes most fresher interviews. Choose one — for example, setting up a company code and posting a vendor invoice and payment. Walk through the configuration steps in order, the master data you created, the entries that resulted, and one error you hit and fixed. A specific error is more convincing than a perfect story.

What they are checking: whether you have actually worked in a system. Two follow-up questions reveal memorised answers.

How to Prepare in the Last Two Weeks

Write out every journal entry in procure-to-pay and order-to-cash from memory until you can do it without hesitation. These come up in nearly every interview, and confident entries do more for a fresher than any definition.

Practise in a system, not only from notes. Create a company code, a GL account, a business partner, post an invoice, run a payment, and run depreciation on an asset. When something fails, note the error and the fix — those notes become your best interview answers.

Prepare one clear explanation of the Universal Journal and one of document splitting; both are high-frequency and easy to answer badly. And be honest about experience. Interviewers expect freshers to have training and practice, not project history; claiming a project you did not do is easy to expose. Our SAP FICO course is built around S/4HANA configuration on a live system, with mock interviews covering exactly these questions.

People Also Ask / FAQ

Can a fresher get an SAP FICO job without experience?

Yes, especially with a commerce or finance background, hands-on system practice and a certification. Entry roles are often support or junior consultant positions in partner firms.

Do interviewers still ask ECC questions?

Sometimes, usually as "what changed from ECC?" Learn S/4HANA as your base and know the main differences so you can answer either way.

Should I memorise transaction codes?

Know the common ones — FS00, BP, F110, MIGO, MIRO, OB52, OBYC, AFAB — but focus on what each does. Interviewers care more about the process than the code.

Is accounting knowledge necessary for SAP FICO?

Yes. Debits and credits, accruals, depreciation and the structure of financial statements are assumed. SAP configures accounting; it does not replace understanding it.

How many interview rounds are typical?

Usually two or three: a functional technical round, sometimes a scenario or configuration round, and an HR or managerial round.

Prepare for S/4HANA FICO Interviews on a Live System

Live classes online and in select cities across India Explore the SAP FICO Course