Free live session with Noel D’Costa: Saturday 24 October, 1:00 PM Eastern / 10:00 AM Pacific. Reserve your place
All interview questions
SAP FICO · 16 QUESTIONS · THREE LEVELS

SAP FICO interview questions and answers

The questions SAP FI and CO interviewers ask at three levels, what each question is really testing, and how to answer from your own project work rather than from a definition. Covers ECC and S/4HANA.

Freshers and first roles

At this level the interviewer checks that you understand the building blocks and can explain them in business terms.

1. What is a company code, and how does it relate to a controlling area?

What it tests: Whether you understand the organisational structure that every posting depends on.

A company code is the smallest unit for which a complete, self-contained set of accounts is produced for legal reporting. A controlling area is the unit for internal cost accounting. One controlling area can contain several company codes, provided they use the same operating chart of accounts and fiscal year variants with the same posting periods.

Say why it matters: the assignment decides whether costs can flow between companies in controlling, for example when one shared service centre charges costs to several legal entities.

2. Explain the chart of accounts types: operating, group and country.

What it tests: Whether you know why one company may need more than one chart.

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

If you have seen a group with local statutory reporting needs, describe how the alternative account was used.

3. What do the fiscal year variant and the posting period variant control?

What it tests: Basic period-end understanding and how finance controls posting periods.

The fiscal year variant defines the number of posting periods and special periods and how calendar dates map to them. The posting period variant controls which periods are open for posting, by account type and range, and is maintained in transaction OB52.

A good answer mentions that finance usually opens the new period and closes the old one in a controlled sequence, and that special periods are used for audit adjustments.

4. What is a field status group?

What it tests: Whether you can explain why a field is mandatory or hidden on a posting screen.

A field status group, assigned in the GL account master, decides whether fields such as cost centre, business area or assignment are required, optional or suppressed when you post to that account. It works together with the field status of the posting key.

Give an example of a posting error you or a user met because a field was required, and how you traced it.

5. What is a reconciliation account?

What it tests: Understanding of how subledgers connect to the general ledger.

A reconciliation account is a GL account assigned in the customer or vendor master. Every posting to the subledger account updates it automatically, so the general ledger always agrees with the subledger. You cannot post to it directly.

Mention that different reconciliation accounts are used for different groups, such as domestic and foreign suppliers or related parties, so the balance sheet can show them separately.

6. What is the GR/IR clearing account and why does it matter?

What it tests: Understanding of the procure-to-pay link between logistics and finance.

The goods receipt / invoice receipt account is credited at goods receipt and debited when the invoice is posted. If quantities or prices differ, or one of the two is missing, a balance remains. At period end the open items are analysed and regrouped so the balance sheet shows goods received but not invoiced and invoices received for goods not yet delivered.

Mention that a growing GR/IR balance is often a process problem, not a configuration problem.

Three to five years

Here the interviewer wants evidence that you have configured, tested and supported real processes. Every answer should point to a project.

1. Walk me through how you configured the automatic payment program.

What it tests: Hands-on configuration depth and an understanding of the full run.

Cover the main settings in transaction FBZP: all company codes, paying company codes, payment methods per country and per company code, bank determination with ranking order and house banks, and available amounts. Then explain the run in F110: parameters, proposal, review and edit, payment run, and printing or payment medium creation through DMEE.

Describe one real issue, such as a vendor missing bank details or a payment method not allowed in the vendor master, and how you diagnosed it from the exception list.

2. How does document splitting work, and why would a company use it?

What it tests: New GL and S/4HANA understanding beyond the basics.

Document splitting divides line items by characteristics such as profit centre or segment so that a balanced balance sheet can be drawn up for each one. The configuration covers classifying GL accounts and document types, defining the splitting characteristics, and deciding whether they must be balanced (zero balancing).

Explain the business reason you met: for example segment reporting, or a requirement for a full balance sheet by profit centre. Mention that switching it on after go-live is a project in itself.

3. What changes for finance in S/4HANA compared with ECC?

What it tests: Whether your experience is current.

Cover the points that affect daily work: the Universal Journal (table ACDOCA) brings FI and CO line items together; cost elements are GL accounts with a cost element category; customers and vendors are maintained as business partners; new asset accounting is mandatory; the material ledger is active for inventory valuation; and account-based profitability analysis is the default.

Then say which of these you worked with on a project, such as business partner conversion or asset accounting migration.

4. Explain the period-end close activities you have supported.

What it tests: Whether you understand the sequence and the dependencies.

A typical sequence includes opening and closing periods, recurring entries, accruals, foreign currency valuation (FAGL_FCV), GR/IR regrouping, depreciation run (AFAB), cost allocations such as assessments and distributions, settlement of internal orders and projects, and reconciliation of subledgers to the GL.

Describe one close you supported: what ran late, what failed, and what you changed so it did not happen again.

5. How does foreign currency valuation work at month end?

What it tests: Whether you understand revaluation of open items and balances, and its accounting effect.

Open items in foreign currency, such as customer and vendor invoices and bank balances, are revalued at the period-end rate in FAGL_FCV. The valuation method decides whether gains and losses are posted, and whether the posting is reversed at the start of the next period. Account determination for unrealised gains and losses is configured per account or account group.

Describe how you checked the results with finance, and any exchange rate or valuation method issue you resolved.

6. How are primary and secondary cost elements handled, and how do assessments differ from distributions?

What it tests: Controlling depth: how costs move inside CO and what the receiver sees.

Primary costs come from finance postings such as salaries or rent. Secondary costs exist only inside controlling, for allocations and activity allocation. In S/4HANA both are GL accounts with a cost element category. A distribution moves primary costs and keeps the original cost element; an assessment uses a secondary assessment cost element, so the receiver sees the allocation rather than the original cost.

Say which one you chose in a real cycle and why.

Senior and lead consultants

Senior interviews test judgement: design trade-offs, cutover, integration and leading others.

1. How would you design the enterprise structure for a group with several legal entities in different countries?

What it tests: Design judgement and the ability to ask the right business questions.

Start with the business questions: legal reporting needs, currencies, shared services, intercompany flows, and how management wants to see the business. Then explain the choices: company codes per legal entity, one or several controlling areas, operating and country charts of accounts, ledgers for parallel accounting, and profit centre and segment design.

Show that you know the cost of getting it wrong: some decisions are very hard to change after go-live.

2. How have you handled data migration for finance in an implementation?

What it tests: Ownership of cutover and reconciliation.

Cover the objects: GL balances, open items for customers and vendors, fixed assets with accumulated depreciation, and open purchase and sales documents where finance is affected. Then the approach: mock loads, reconciliation reports signed off by the business, and a cutover plan with clear owners.

Describe a reconciliation difference you found during a mock load and how it was resolved before go-live.

3. How would you set up and support intercompany processes?

What it tests: Cross-module integration and group reporting awareness.

Explain the flows you have seen: intercompany sales with internal billing, cross-company postings, and intercompany reconciliation. Cover the key settings: trading partner in the customer and vendor masters, intercompany clearing accounts, and how eliminations are prepared for consolidation.

Point to how you kept reconciliation differences under control at month end.

4. Tell me about a time a design decision you made caused a problem later.

What it tests: Honesty and learning, which matter more at senior level than a perfect record.

Pick a real example, describe the decision and the context, the impact you saw, and what you would decide differently now. Interviewers trust candidates who can talk about their mistakes clearly.

How to prepare

Before the interview

  • Choose two projects you can explain in depth: scope, your role, the design decisions and what changed after go-live.
  • Be ready to name the transaction codes and tables you used, and to say which release you worked on.
  • Prepare one period-end close story and one production issue you resolved.
  • Know what is different in S/4HANA if you have only worked on ECC, and say so honestly.

Going deeper: the ECC to S/4HANA migration guide, by Noel D’Costa on noeldcosta.com.

Transaction codes, tables and options vary by release and by how a system has been configured. Answer from the system you actually worked on, and say which release it was.

Make yourself comfortable

Optional campaign attribution

Remember the campaign that brought you here. Rejecting does not affect assessments, orders or sign-in. Withdrawing clears saved attribution.

Current choice: Not yet chosen