SAP FI interview questions

Written by an SAP Finance & Treasury practitioner working with SAP since 2008 · how the guides are written · Updated 4 October 2026

SAP FI interview questions are the scenarios a finance interviewer uses to find out whether you can make the design decisions a project will put in front of you: organisational structure, ledgers and document splitting, integration with purchasing and sales, the period-end close, and the migration of balances.

The same ground is covered in an SAP FICO interview, an SAP finance consultant interview or an S/4HANA finance interview. Where finance and controlling are hired as one seat — what an SAP FICO consultant does covers that role — expect the questions that cross into controlling as well. The table maps each theme to what is being tested and where to read up; the sections after it work through the themes as scenarios, because that is how the good interviews are run.

How is an FI interview different from a finance quiz?

It asks you to design for a company instead of reciting what a field is called. Lists of questions and answers circulate for every SAP area, and interviewers know them, so the good ones describe a business, let you design, then change one fact and ask what you would change. The finance area lends itself to this because nearly every decision in it has a consequence that shows up later, in a report or at a close, and the interviewer wants to see whether you can see that far ahead. The functional interview guide describes the general structure; what follows is the finance-specific content that fills it.

Which organisational structure decisions get tested?

The count and purpose of company codes, charts of accounts and controlling areas, and what is expensive to change later. A typical opener: "A group has legal entities in several countries, two of them sharing one management team. How many company codes, how many charts of accounts, how many controlling areas, and why?" This is the opening scenario in many FI interviews because it exposes whether you know what each object is for. A company code is a legal entity that produces its own statutory accounts; a chart of accounts is a list of accounts that can be shared, with a country-specific one alongside for local reporting and a group one above for consolidation; a controlling area binds company codes together for management reporting, with conditions on what they must share. The follow-ups test the edges: what happens to fiscal year variants when one country closes on a different date, what a change of currency at group level implies, and what is expensive to change after go-live — which is the real question, since organisational structure is the one design you cannot easily undo.

How do document splitting and parallel ledgers come up?

As reasoning, not definitions. "The CFO wants a balance sheet by business segment. What do you need to switch on, and what does it cost the business?" Document splitting is the mechanism that gives every line of a posting a segment or profit centre so that balance-sheet accounts can be reported by that dimension; the cost is that every posting must be able to derive that dimension, which means master data discipline and rules for the lines that have no natural owner. "The group reports under one accounting standard and each entity under its local one. How do you keep both sets of books?" Parallel ledgers are the answer most projects give now — the same postings, valued differently where the standards differ — and the interviewer wants to hear you weigh that against the older approach of parallel accounts, and say when a ledger-specific posting is needed. Answers that mention the closing implications, and the controlling side of the same decision, are the ones that sound like a consultant who has lived with the consequences.

Which integration questions test MM and SD?

The ones that start from a finance symptom and make you work back into purchasing or sales, because finance is where the other areas' postings land. "The goods-received-not-invoiced account carries a balance that never clears. What is in it?" wants the receipts still waiting for an invoice, the invoices that arrived without a receipt, the tolerance that let a mismatch through, and the regrouping the balance sheet needs at year-end before an auditor asks. "Sales for the whole year sit in one revenue account and the CFO wants them split by product line" wants you to say where the split is derived from before you promise it, and to warn that the correction is master data on thousands of records rather than one table entry. The procurement and sales areas own those derivation chains (and the MM interview scenarios put the same clearing account from the buyer's side); what finance is tested on is the consequence — which account a change lands in, who reads that account, and what it does to the close. The last question in this block is usually the governance one — a neighbouring team proposes a change to a setting that determines an account, and the interviewer wants to know whether finance finds out before the change is made or at the next close.

Name the settings as you go, because the interviewer will. Goods-movement accounts are determined in OBYC by transaction key — BSX for stock, WRX for the GR/IR account, GBB for offsetting entries such as consumption, PRD for price differences — and revenue accounts in VKOA. A GR/IR line that will never be invoiced is cleared with MR11 rather than posted around, and saying so is the difference between having run a close and having read about one.

Which FICO questions cross from FI into CO?

The ones that start in one half and end in the other, because the combined seat exists for that seam. Expect a symptom rather than a definition: a purchase invoice for a service with no cost centre on it, an assessment run that moved cost into a company code that should not have received it, a costing run that released a price the controller disputes, a margin report that no longer ties to revenue after a new billing type went live (the billing side of that story is rehearsed in the SAP SD interview scenarios). The interviewer is watching whether you trace it through account determination, the default account assignment in OKB9 and the Universal Journal, or stop at the half you know. Have one story from each half that you personally owned, say plainly which half is your weaker one, and be ready to name the transaction for anything you claim to have done.

What does the period-end scenario look like?

It is a request to walk through a real close in order, with owners: "Take me through a month-end close in a company you supported." The interviewer is listening for order and for ownership: what runs automatically and what a person must trigger, what depends on what, and where the close usually stalls. Recurring entries and accruals, the clearing of the goods-received-not-invoiced account, foreign currency valuation of open items and balances, the depreciation run in assets, allocations coming across from controlling, then the checks before the period is locked. The follow-up is nearly always "and what went wrong the time it went wrong" — the posting in the closed period, the valuation run that had to be reversed, the sub-ledger that did not reconcile to the general ledger and the way you found the difference. A candidate who has sat with a finance team on the last working day of a period sounds different from one who has read the closing checklist, and usually names the steps as the team ran them: FAGL_FCV for the valuation, AFAB for depreciation, KSU5 for an assessment cycle from controlling, OB52 to lock the period.

How is the data-migration scenario asked?

As a question of order and proof: "We go live at the start of a period. What finance data do you migrate, in what order, and how do you prove it is right?" The answer has a structure: master data first — accounts, customers, suppliers, assets, cost objects — then balances as at the cutover date, with open items for customers and suppliers loaded item by item so that they can be cleared later, assets loaded with their accumulated depreciation so the future runs are correct, and general-ledger balances loaded against a migration clearing account that must be zero at the end, usually loaded through the S/4HANA Migration Cockpit (the Migrate Your Data app). Proof is reconciliation: the trial balance of the old system against the new one, the open-item lists agreeing in count and value, the auditors' sign-off. The migration stream does the loading, but the finance consultant owns the answer to "is it right", and interviewers want to hear that you know it.

What are interviewers really testing?

Whether you think in consequences. Every scenario above has a decision at the front and a report, a close or an audit at the back, and the interviewer is watching for the moment you connect them unprompted. Whether you can talk to accountants in their language and to developers in theirs. Whether your knowledge of the standard process is deep enough that you can tell a genuine gap from a habit. And whether your stories have the texture of real projects — the client's name withheld but the shape of the mess intact — which is how experience is read across the ecosystem.

How should you prepare for an SAP FI interview?

Rebuild your own material rather than memorising someone else's. Draw one organisational structure you configured from memory and defend each object; walk a close in order with the failure story at the step where it happened; trace a goods receipt, a billing document and a payroll run to their accounts; and refresh the accounting behind the configuration, because interviewers can tell understood accounting from configured accounting. The general interview guide covers the format; the scenarios above decide the outcome.