SAP FICO Interview Questions and Answers: 60 Questions from Easy to Hard
This guide is for commerce and finance freshers in India starting out as SAP FICO consultants or end users, and for consultants, accountants and finance key users with 1 to 10 years of experience facing SAP S/4HANA Finance interviews. It has 60 questions with answers in three levels: enterprise structure, GL, payables, receivables and controlling basics; day-to-day configuration, MM and SD integration and debugging; and senior questions on the universal journal, document splitting, closing and GST design. Read each answer, explain it aloud with an example from your own work, then take the mock test. The questions are written by CoreHRx for practice. CoreHRx is not affiliated with or endorsed by SAP, and these are not actual SAP certification exam questions. Features change by release, so check the official SAP documentation for your version.
- 60 questions, 3 levels
- Updated
- CoreHRx Jobs
Practice questions written by CoreHRx. CoreHRx is not affiliated with or endorsed by SAP, and these are not actual SAP certification exam questions.
What SAP FICO interviews cover
- Enterprise structure: company code, chart of accounts, fiscal year variant, posting period variant and controlling area, and how they are assigned to each other.
- Financial accounting: general ledger, accounts payable, accounts receivable, asset accounting and bank accounting, including the automatic payment program and the bank statement.
- Controlling: cost centres, profit centres, internal orders, allocations, settlement and CO-PA, and how all of them land in the universal journal in S/4HANA.
- Integration and closing: the postings MM and SD create in FI, the GR/IR account, month-end and year-end closing, and GST in SAP for Indian companies.
How to prepare (freshers and experienced)
- Freshers: get the accounting right first. Be able to write the journal entry for each business event, such as a purchase, a sale, a payment or depreciation, before you learn the T-code that posts it.
- Learn the setup order of a company code: company code, chart of accounts, fiscal year variant, posting periods, field status, document types and number ranges, and be ready to explain why each step exists.
- Experienced: prepare two or three stories from your projects, such as a go-live, a month-end issue you fixed or an integration error you traced, with the business impact and what you changed.
- Know what changed in S/4HANA: the universal journal, the business partner, cost elements as GL accounts, new asset accounting and the new credit management. Panels test this often.
- Revise Indian GST basics such as CGST, SGST, IGST, reverse charge and input tax credit, because almost every Indian SAP project has to handle them.
Common mistakes and interview-day tips
- Do not answer with a list of T-codes. Explain the business purpose, the setting behind it and the accounting entry; the T-code is the last detail, not the answer.
- Do not claim experience you do not have. Say clearly what you have configured, what you have only used as an end user and what you know from study.
- Keep ECC and S/4HANA apart. Saying that you create cost elements in KA01 or that balances live in totals tables tells the panel your knowledge is from older releases.
- For an error question, walk through how you would find the cause: read the message and its long text, check the setting it points to, test the fix in a quality system and document it.
SAP FICO interview questions: Easy questions (freshers)
20 questions1. What is the difference between SAP FI and SAP CO?
FI is financial accounting: it records every business transaction for external reporting, so its output is the balance sheet, the profit and loss statement and the statutory books used by auditors, tax authorities and shareholders. CO is controlling: it uses the same costs and revenues for internal management, showing where costs arose and which products, departments or projects earn money. In S/4HANA both write to the same universal journal, so FI and CO always reconcile. A common mistake is to call CO a second set of books; it is another view of the same postings.
2. What is a company code, and what must be assigned to it before you can post?
A company code is the smallest organisational unit for which a complete, self-contained set of accounts, a balance sheet and a profit and loss statement, can be drawn up for external reporting. It usually matches a legal entity, such as a private limited company registered in Pune. Its key has four characters and it carries a country, a currency and a language. It is defined with OX02 and then assigned to a chart of accounts with OB62, a fiscal year variant with OB37 and a posting period variant. Until these assignments exist, no document can be posted in it.
3. What are the operating, group and country charts of accounts?
The operating chart of accounts is the one a company code uses for daily postings in FI and CO, and each company code has exactly one. A group chart of accounts serves consolidated reporting: every operating account carries a group account number, so several company codes can be reported on one common basis. A country chart of accounts holds the account numbers that local law requires, linked through the alternative account number field in the company code data of each GL account. Charts are listed in OB13 and assigned to the company code in OB62.
4. What is a fiscal year variant, and how does V3 work for an Indian company?
A fiscal year variant tells SAP how many posting periods a year has, how calendar months map to periods and how many special periods exist. Indian companies with an April to March year usually use V3: 12 normal periods starting in April plus 4 special periods for year-end adjustments; normal and special periods together are limited to 16. For January to March the year shift is -1, so a posting dated 15 February 2025 falls in fiscal year 2024, period 11. People expect 2025 because they call it FY 2024-25, a common mistake. K4 is the calendar-year variant.
5. What is a posting period variant, and how do you open and close periods?
A posting period variant controls which periods are open for posting. Several company codes can share one variant, so finance can open and close them together. In OB52 the + row covers all account types, and further rows for assets (A), customers (D), vendors (K), materials (M) and GL accounts (S) let you, for example, close vendors while GL stays open for adjustments. The first interval can be limited to an authorisation group, so only the closing team can still post. Materials management keeps its own period, moved forward with MMPV, which is a separate step.
6. What are the two segments of a GL account master, and in which tables are they stored?
A GL account has a chart of accounts segment and a company code segment. The chart of accounts segment holds data valid in every company code using that chart, such as the account number, the GL account type and the group account number; it is stored in SKA1, with the texts in SKAT. The company code segment holds local settings, such as the account currency, tax category, reconciliation account type, open item management, sort key and field status group; it is stored in SKB1. In S/4HANA you maintain both in FS00. Forgetting to extend an account to a new company code is a common go-live error.
7. What is a reconciliation account, and why can you not post to it directly?
A reconciliation account is a GL account that sums up a subledger, such as Trade Payables for vendors, Trade Receivables for customers or the fixed asset account of an asset class. Each posting to a vendor, customer or asset updates the subledger and, at the same moment, its reconciliation account, so the GL always equals the subledger total. The account is flagged with the type D, K or A in its company code segment and entered in the customer or vendor master or in the asset account determination. Direct postings are blocked because they would change the GL without a subledger entry.
8. What are posting keys and document types? Give common examples.
A two-digit posting key tells SAP, for each line item, whether it is a debit or a credit, which account type it posts to and which fields appear. Common keys: 40 debit and 50 credit for GL accounts, 01 customer invoice and 15 incoming payment, 31 vendor invoice and 25 outgoing payment, 70 asset debit and 75 asset credit. A document type classifies the whole document and controls its number range and allowed account types: SA for GL documents, KR vendor invoices, KZ vendor payments, DR customer invoices, DZ customer payments, AA asset postings.
9. Show the journal entry when a vendor invoice for office services is posted in FB60 with GST.
FB60 posts the expense and the tax in one document. The vendor is credited with the gross amount using posting key 31, the expense account is debited with the base amount, and SAP calculates the GST lines from the tax code. With an assumed 18% intra-state rate on ₹50,000, CGST and SGST input tax are ₹4,500 each and the vendor is credited ₹59,000. For a supplier in another state, an inter-state tax code would post ₹9,000 IGST instead. Picking a tax code for the wrong state combination is the usual error, and it shows up in the GST return reconciliation.
Assume: Pune supplier, Pune business place, GST 18% (9% + 9%)
PK Account Debit Credit
40 Office services expense 50,000
40 CGST input tax 4,500
40 SGST input tax 4,500
31 Vendor (Trade payables) 59,00010. Why is the business partner mandatory in S/4HANA, and what are BP roles?
In S/4HANA, customers and vendors are created and changed through the business partner, transaction BP; older transactions such as XK01 and XD01 send you to it. One BP holds the general data, such as name, address, tax numbers and bank details, only once, and roles add the views you need: FLVN00 for vendor company code data, FLVN01 for purchasing data, FLCU00 for customer company code data and FLCU01 for sales data. Customer-vendor integration keeps LFA1, LFB1, KNA1 and KNB1 filled, so FI postings work as before. A party that is both supplier and customer needs only one BP.
11. Walk through a customer invoice and its payment in FI, including clearing.
A customer invoice entered in FI with FB70 debits the customer with posting key 01 and credits revenue and output tax; the customer line is an open item on the Trade Receivables reconciliation account. When the money arrives, F-28 posts the incoming payment: the bank or bank clearing account is debited and the customer is credited with posting key 15, and the payment is matched with the open invoice so both items are cleared and get a clearing document and date. SD billing documents post the same way automatically. A receipt posted without clearing stays on account, so both items remain open.
12. How do payment terms and cash discount work? Work out the discount for 2% within 10 days, net 30.
Payment terms, defined in OBB8 and entered in the customer or vendor master, are copied into each invoice and set the baseline date, due date and any cash discount. With 2% within 10 days and net 30, a customer paying an assumed ₹2,00,000 invoice within 10 days of the baseline date may pay ₹1,96,000, and the ₹4,000 discount is posted automatically to the cash discount granted account when the payment clears the invoice. After day 10 the full amount is due by day 30. Whether the discount base includes tax is a company code setting, so check it before you quote a figure.
13. What is the universal journal in S/4HANA?
The universal journal is one line item table, ACDOCA, into which S/4HANA writes almost every accounting posting: general ledger, controlling, asset accounting, material ledger and account-based profitability analysis. Each line carries the GL account together with its CO details, such as cost centre, profit centre, segment and functional area, and amounts in several currencies. So FI and CO cannot drift apart, and no reconciliation ledger is needed. Balances are no longer stored in totals tables; reports add up line items on the fly. Headers stay in BKPF and the entry view in BSEG.
14. What is a cost centre, and what is the standard hierarchy?
A cost centre is a place in the organisation where costs arise and someone is responsible for them, such as Finance, the IT helpdesk or a packing line in a Chennai plant. It is created with KS01 in a controlling area, with a validity period, a person responsible, a category and the assigned company code and profit centre. Every cost centre must sit in the standard hierarchy, a tree of the whole controlling area that makes sure none is left out of reports; extra cost centre groups give other views. Costs reach it from FI postings and allocations, and you compare them with plan.
15. What is the difference between a cost centre and a profit centre?
A cost centre collects costs for an area of responsibility so you can plan and control spending. A profit centre is a management unit, such as a product line or a region, for which you measure profit: revenue, cost of sales and expenses, and in S/4HANA also balance sheet items such as receivables and inventory. Each cost centre is assigned to one profit centre, so its costs flow into that result, while revenue reaches profit centres through material masters and sales documents. A cost centre shows spending; a profit centre shows earnings. Profit centres are created with KE51.
16. What is an internal order, and when do you use a statistical one?
An internal order collects costs for a short-term job or event, such as a trade fair in Mumbai, a marketing campaign or a machine repair, so you can budget and track it apart from the cost centre. A real internal order is a true cost object: at period end you settle its costs to a receiver such as a cost centre, an asset or a profitability segment. A statistical order only holds a copy of the costs for reporting; the real account assignment still goes to a cost centre, and nothing is settled. Use it when tracking is all you need. Orders are created with KO01 under an order type.
17. What are an asset class, a chart of depreciation and a depreciation area? Give a simple depreciation example.
An asset class, such as Plant and Machinery or Computers, groups assets and supplies defaults: account determination, number range, screen layout and depreciation terms. The chart of depreciation, assigned to the company code, lists the depreciation areas, each a separate valuation of the same asset, such as book depreciation and a tax area. A machine costing ₹12,00,000 with an assumed 5-year life, straight-line method and no residual value is depreciated ₹2,40,000 a year, ₹20,000 a month, in the book area. Assets are created with AS01 and the depreciation run is AFAB.
18. What is a house bank, and why are bank clearing accounts used?
A house bank is a bank branch where the company code holds accounts, with a house bank ID and account IDs, each linked to a GL account; in S/4HANA the accounts are managed in Bank Account Management with the Manage Bank Accounts app. Most companies post through clearing accounts rather than the main bank GL: outgoing payments, cheques issued and cheques deposited first hit clearing accounts, and only the bank statement moves the amount to the main account. The main account then matches the bank exactly, and open items on clearing accounts are the reconciling items in the bank reconciliation.
19. How does SAP decide between CGST plus SGST and IGST on a sale?
GST depends on whether the supply is within one state or between states. In S/4HANA set up for India, the condition-based tax procedure TAXINN finds tax through condition records that compare the region of the supplying plant or business place with the place of supply, usually the customer ship-to region. At an assumed 18% on ₹1,00,000, a sale from Maharashtra to a Maharashtra customer posts CGST ₹9,000 and SGST ₹9,000, while a sale to a Karnataka customer posts IGST ₹18,000. Each GSTIN is set up as a business place, so tax is reported per registration.
20. What accounting entries do a goods receipt in MIGO and an invoice in MIRO create?
For a stock material on a purchase order, the goods receipt in MIGO, movement type 101, debits the inventory account found through transaction key BSX and credits the GR/IR clearing account through WRX. The invoice in MIRO then debits GR/IR and input GST and credits the vendor. For 100 units at ₹250 of a moving-average material with an assumed 18% intra-state GST, MIGO posts ₹25,000; MIRO clears ₹25,000 from GR/IR, posts CGST and SGST of ₹2,250 each and credits the vendor ₹29,500. An open GR/IR balance means received not invoiced, or the reverse.
Ready to check yourself? Take the free SAP FICO mock test
SAP FICO interview questions: Medium questions (1-3 years)
20 questions21. What does document splitting do, and why is zero-balancing needed?
Document splitting copies account assignments such as profit centre and segment onto lines that have none, like the vendor, customer or tax line, so a full balance sheet can be drawn up per profit centre or segment. In the example an invoice of ₹1,00,000 charged 60:40 to two profit centres has its vendor line split ₹60,000 and ₹40,000 in the GL view, while the entry view keeps one vendor line. Zero-balancing makes each profit centre balance to zero within a document, adding clearing lines where needed. Splitting is set up with a splitting method, item categories and business transactions.
Invoice ₹1,00,000, no tax, two cost lines
Entry view (BSEG)
Dr Travel expense PC-NORTH 60,000
Dr Travel expense PC-SOUTH 40,000
Cr Vendor - 1,00,000
GL view (ACDOCA) after splitting
Dr Travel expense PC-NORTH 60,000
Dr Travel expense PC-SOUTH 40,000
Cr Vendor PC-NORTH 60,000
Cr Vendor PC-SOUTH 40,00022. What is the difference between parking, holding and posting a document?
Posting updates the accounts at once and takes a number from the real number range. Parking, for example with FV50 for a GL document or FV60 for a vendor invoice, saves a complete or incomplete document with a document number but without updating any balance, so a second person can check it and post it with FBV0; it is the usual maker-checker route, alone or with workflow. Holding only saves a draft for the same user under a temporary name, with no document number and no visibility to others. A common mistake is to count a parked invoice as a liability; until it is posted, it updates nothing.
23. A user gets an error that a field is required while posting to a GL account. How do field status groups cause this?
Each field in an FI line item can be suppressed, required or optional, and the final status comes from two places: the field status group in the GL account, read from the field status variant of the company code maintained in OBC4, and the field status of the posting key. SAP combines them and the stricter wins: required beats optional, suppressed beats optional, and required against suppressed is an error. So check the account field status group first, then the posting key. Note that a primary cost account always needs a CO account assignment such as a cost centre, which is a separate check.
24. Explain the automatic payment program F110 and its main configuration.
F110 pays due vendor items in one controlled run. You enter parameters: company codes, payment methods, the next payment date, which decides what must be paid now and what can wait, the vendor range and any free selection. SAP builds a proposal that the team reviews and edits; the payment run then posts payment documents that clear the invoices, and the payment medium, a bank file or cheques, is created last. FBZP holds the configuration: all and paying company codes, payment methods per country and company code, and bank determination with ranking order and available amounts.
F110 parameters (example)
Run date 30.11.2024 Identification PAY01
Posting date 30.11.2024 Docs entered to 30.11.2024
Company code 1000 Payment methods T (transfer)
Next pay date 07.12.2024 Vendors 100000-19999925. How are vendor down payments handled, and why does a down payment request not update the GL?
A down payment uses a special GL indicator to keep it apart from payables. The request, posted with F-47 and indicator F, is a noted item: it records that money is to be paid and can be picked up by F110, but it updates no GL balance because nothing has happened yet. The actual payment, posted with F-48 or through F110, uses indicator A and goes to the down payment reconciliation account, shown as an advance to suppliers in the balance sheet. When the invoice arrives, F-54 clears the down payment against it. Skipping F-54 leaves the vendor showing both the advance and the full liability.
26. How is TDS deducted on a vendor invoice in SAP? Work out an example.
India uses extended withholding tax. You define withholding tax types that deduct at invoice or at payment, withholding tax codes with the rate and the income tax section, and section codes that group TDS for challans and certificates per TAN, then assign the type and code to the vendor in its company code data. With an assumed 10% TDS on ₹1,00,000 of professional fees and an assumed 18% GST on top, TDS is ₹10,000 on the base, so the vendor is credited ₹1,08,000, that is ₹1,18,000 minus ₹10,000. Rates and sections change, so keep them in configuration.
27. What is the difference between a partial payment and a residual payment? Use an example.
Both handle a customer who pays less than the invoice, but they leave different items open. With a partial payment the invoice stays open and the payment is posted as a separate open credit item that refers to the invoice, so for a ₹1,50,000 invoice paid with ₹1,00,000 you see two open items until the rest arrives and all are cleared together. With a residual payment the invoice is cleared and SAP creates a new open item for the ₹50,000 difference. Residual is easier to read, but depending on settings the new item may get its own dates and hide how overdue the debt is.
28. What is CO-PA, and how are characteristics filled on a sales posting?
Profitability analysis shows margin by market segment, such as customer, product, region or sales channel. The operating concern, created with KEA0 and assigned to the controlling area, defines the characteristics, and for costing-based CO-PA also value fields such as revenue and freight. On a billing document, characteristics come from the sales document and master data; characteristic derivation, maintained in KEDR, fills others, such as product group, from rules and tables. Other costs reach CO-PA through settlement or top-down distribution, and reports such as KE30 show margin by segment.
29. How does credit management work in S/4HANA compared with ECC?
In ECC most companies used FI-AR credit management with credit control areas and FD32. S/4HANA replaces it with SAP Credit Management, part of FSCM: credit limits, risk class and check rules are kept in the business partner in credit segments, and SD calls the credit check when a sales order or delivery is saved. If the exposure, made up of open orders, deliveries, billing documents and open receivables, exceeds the limit, the document is blocked and a documented credit decision is created for the credit team. Upgrades must map credit control areas to credit segments.
30. A billing document was saved but not posted to accounting. How do you find and fix the cause?
Start with VFX3, which lists billing documents blocked for accounting, and read the error log of the document. The usual causes: no revenue account found in VKOA for the combination of chart of accounts, sales organisation, account assignment groups and account key such as ERL; the posting period closed in OB52; a required field missing, often profit centre or business place; or a tax code not valid for the country. Once the setting is fixed, release the document from VFX3 and it posts with its original data. Fix the rule or master data behind it, or the next invoice fails too.
31. How does MM find GL accounts, and what happens to a price difference on a standard-price material?
Automatic account determination in OBYC links each movement to transaction keys: BSX for inventory, WRX for GR/IR, GBB for offsetting entries such as consumption and PRD for price differences. The account depends on the chart of accounts, the valuation grouping code, the valuation class from the material master and, for GBB, an account modifier. For a standard price of ₹100, a receipt of 50 units at a PO price of ₹105 posts inventory at ₹5,000, credits GR/IR ₹5,250 and sends ₹250 to PRD. With moving average price, the ₹250 goes to stock.
Standard price ₹100, PO price ₹105, 50 units received
Key Account Debit Credit
BSX Raw material stock 5,000
PRD Price differences 250
WRX GR/IR clearing 5,25032. Why does the GR/IR clearing account keep old balances, and how do you clean it up?
GR/IR should net to zero for each purchase order item once goods and invoice match, but balances remain when quantities or prices differ and nobody follows up: a partial delivery never invoiced, an invoice for a quantity never received, or a price gap left open. At month end you analyse the account per PO item, ask purchasing and stores to post the missing receipt or invoice, and write off genuine small differences with MR11 after approval. For the balance sheet, the remaining balance is regrouped into goods received not invoiced and invoices received not delivered, so netting hides neither.
33. How is an asset bought from a vendor posted in S/4HANA, and what is the technical clearing account?
In S/4HANA an integrated acquisition, such as MIRO for a PO assigned to an asset, is split into an operational part and a valuating part. The operational part credits the vendor and debits the technical clearing account for integrated asset acquisition. The valuating part, posted for each accounting principle and its ledgers, debits the asset balance sheet account and credits the same clearing account, so it nets to zero. This way each ledger values the asset its own way at once. A balance left on the clearing account means a valuating posting is missing.
34. How do you sell an asset in SAP, and how is the gain or loss worked out?
You post a retirement with revenue, with a customer if you invoice the buyer in FI or against a clearing account if billing happens elsewhere, giving the asset, retirement date and sale value. SAP calculates depreciation up to the retirement date, removes cost and accumulated depreciation and posts the gap between sale value and net book value as gain or loss to the accounts in the account determination. For cost ₹10,00,000 and accumulated depreciation ₹6,00,000 on that date, net book value is ₹4,00,000, so a sale at ₹4,50,000 gives a gain of ₹50,000. The table shows the net effect before GST.
Net effect of the sale (GST not shown)
Account Debit Credit
Customer 4,50,000
Accumulated depreciation 6,00,000
Plant and machinery (cost) 10,00,000
Gain on sale of assets 50,00035. What is the difference between assessment and distribution? Allocate an IT cost centre by headcount.
Both move costs from a sender cost centre to receivers by a rule kept in a cycle, such as fixed percentages or a statistical key figure like headcount. Distribution moves only primary costs and keeps the original cost element, so receivers see which expense, such as rent or power, they got. Assessment can move primary and secondary costs together under one assessment cost element, category 42, which is simpler but hides the detail. Here ₹6,00,000 of IT cost by headcount gives ₹2,40,000, ₹2,10,000 and ₹1,50,000. Cycles are created with KSU1 or KSV1 and run with KSU5 or KSV5.
Sender: IT cost centre, actual cost ₹6,00,000
Tracing factor: headcount (statistical key figure)
Receiver Headcount Share Allocated
Sales 40 40% 2,40,000
Production 35 35% 2,10,000
Finance 25 25% 1,50,00036. How do budgets, availability control and settlement work for an internal order?
You enter the original budget on the order, for example with KO22, and the budget profile of the order type decides whether availability control is active. Availability control compares actual costs plus commitments, such as open purchase orders, with the budget and reacts at tolerance limits you set, for example a warning at 90% and an error that stops the posting at 100%. At period end the order is settled with KO88, or collectively with KO8G, by its settlement rule, such as 70% to a cost centre and 30% to a profitability segment. A common mistake is to set it to warn only.
37. How does SAP derive the profit centre on a posting, and what is a dummy profit centre?
Most postings take the profit centre from the account assignment: a cost centre, internal order or WBS element carries one in its master data, and for sales and stock postings the material master at plant level supplies it. Balance sheet lines with no assignment of their own, such as vendor or tax lines, get it through document splitting. If nothing can be derived, it goes to the dummy profit centre of the controlling area. A growing dummy balance is a warning sign: fix the missing master data, and use a substitution only when master data cannot carry the rule.
38. How is an electronic bank statement configured and posted?
The bank file, such as MT940, is imported with FF_5, and each line has an external transaction code from the bank. In configuration you group bank accounts under a transaction type, map each external code to a posting rule and define for each rule what posting area 1 does in the GL, such as main bank debit and cheque clearing credit, and what posting area 2 does in the subledger, such as clearing the customer item. Interpretation algorithms read the note to payee to find what to clear. Unmatched lines are finished in FEBAN; what stays on clearing accounts goes into the bank reconciliation.
39. How does foreign currency valuation work at month end? Work it out for a USD vendor invoice.
Open items and balances in foreign currency are revalued at the closing rate so the balance sheet shows their rupee value on the reporting date. Rates are kept per exchange rate type, usually M, in OB08, and in S/4HANA the valuation runs with FAGL_FCV. A USD 10,000 vendor invoice booked at ₹83.00 is ₹8,30,000; at a month-end rate of ₹84.20 it is ₹8,42,000, so an unrealised loss of ₹12,000 is posted. Depending on the valuation method it is reversed in the next period or adjusted by delta at the next run, and payment books the realised difference. Accounts are set in OBA1.
Open vendor invoice USD 10,000
Booked at 83.00 = ₹8,30,000
Month-end (M) 84.20 = ₹8,42,000
Unrealised loss = ₹12,000
Account Debit Credit
Unrealised exchange loss 12,000
Balance sheet adjustment (vendor) 12,00040. How is reverse charge GST posted in SAP for a service on which the buyer pays the tax?
Under reverse charge the buyer, not the supplier, pays the GST, so the vendor is credited only with the base amount. A reverse charge tax code posts the tax twice: input tax as a debit, which you claim as credit if eligible, and an RCM liability as a credit, which is paid to the government in cash. For assumed legal fees of ₹40,000 at 18% intra-state, CGST and SGST are ₹3,600 each on both sides and the vendor gets ₹40,000. Using a normal input tax code by mistake credits the vendor ₹47,200 and leaves the RCM liability out of the return.
Assume: legal fees, reverse charge, GST 18% (9% + 9%)
Account Debit Credit
Legal expense 40,000
CGST input (RCM) 3,600
SGST input (RCM) 3,600
CGST RCM payable 3,600
SGST RCM payable 3,600
Vendor 40,000Ready to check yourself? Take the free SAP FICO mock test
SAP FICO interview questions: Hard questions (experienced)
20 questions41. What changed in S/4HANA for custom reports that read BSIS, BSAS or FAGLFLEXT?
In S/4HANA the index tables BSIS, BSAS, BSID, BSAD, BSIK and BSAK and totals tables such as GLT0 and FAGLFLEXT are no longer physical tables; they are compatibility views that read the universal journal. Old SELECT statements usually still run, but writing to them is impossible and complex views can be slow, so performance-critical reports should read ACDOCA directly or, better, released CDS views such as I_JournalEntryItem, with ledger, company code, fiscal year and period in the filter. Do not forget the ledger: leaving it out doubles amounts when a company runs parallel ledgers.
-- Movements per account, periods 1-8 of fiscal year 2024
SELECT racct, SUM(hsl) AS amount_cc_currency
FROM acdoca
WHERE rldnr = '0L' AND rbukrs = '1000'
AND gjahr = '2024' AND poper BETWEEN '001' AND '008'
GROUP BY racct;42. How would you design parallel accounting for an Indian subsidiary that reports under Ind AS locally and IFRS to a foreign parent?
S/4HANA supports two approaches. With the ledger approach, each accounting principle has its own ledger on the same accounts; SAP usually recommends that the leading ledger 0L follow the group principle, here IFRS, with Ind AS in a non-leading ledger. Common postings go to all ledgers, adjustments only to the ledger concerned. The accounts approach uses separate accounts in one ledger for items that differ, simpler at first but it clutters the chart of accounts. An extension ledger, storing only delta postings, suits small adjustment views. Decide early.
43. In S/4HANA cost elements are GL accounts. What does that change for configuration and allocations?
There is no separate cost element master any more: an account in FS00 gets a GL account type, and the types Primary Costs or Revenue and Secondary Costs make it a cost element with a category, such as 1 primary costs, 11 revenue, 21 internal settlement, 42 assessment and 43 internal activity allocation. Secondary cost accounts are created like other accounts but only CO allocations post to them. Allocations post to ACDOCA, so those across company codes or profit centres reach the GL at once, with no reconciliation ledger. KA01 is gone, while default account assignment in OKB9 still matters.
44. What finance prerequisites must be met before converting an ECC system to S/4HANA?
Every customer and vendor must be synchronised to a business partner through customer-vendor integration before the conversion. New asset accounting is mandatory: map depreciation areas to ledgers or accounts. The material ledger becomes mandatory for inventory valuation, and classic credit management is migrated to SAP Credit Management. The data must reconcile first: check FI against CO, AA and MM and clear inconsistencies, because the migration builds ACDOCA from existing data. Document splitting cannot simply be switched on during the conversion; plan it as a separate project.
45. Compare account-based and costing-based CO-PA. Which would you recommend in S/4HANA and why?
Account-based CO-PA, called margin analysis in S/4HANA, writes profitability characteristics such as customer, product and region straight onto universal journal lines, so profitability always reconciles with the GL. Costing-based CO-PA keeps its own tables with value fields, takes cost of sales from a billing condition and can hold values with no GL account, but needs reconciling with FI. SAP recommends margin analysis for new projects; newer releases can split cost of goods sold by cost component. Timing differs: account-based records cost of sales at goods issue, costing-based at billing.
46. How would you plan the sequence of a month-end close in S/4HANA, and why does the order matter?
Order follows dependency: a step must run after everything it reads. A typical sequence: open the next period, finish logistics such as goods receipts, invoices and the MM period, post accruals and recurring entries, run depreciation, revalue foreign currency items, analyse GR/IR, then run CO: activity allocations, distributions, assessments, overhead and order settlement, then reconcile and close. Within CO the cycle design decides the order: if orders settle to cost centres that are then assessed, settle first. Teams often run it from a closing cockpit with owners and timings.
47. How are cross-company code postings and intercompany reconciliation handled?
When one document touches two company codes, for example a Hyderabad company paying an invoice of its Chennai sister company, SAP creates a document in each company code and balances each with automatic intercompany receivable and payable lines set in OBYA, linked by a cross-company code number. Lines carry the trading partner, taken from the partner company or the customer or vendor master, so consolidation can eliminate intercompany balances. At month end both sides are matched, and differences from exchange rates, timing or a wrong trading partner are corrected before consolidation.
48. When would you use a validation or a substitution in FI, and what are the risks?
A validation checks a posting against a rule and stops it or warns, such as requiring a cost centre on a travel expense account in one company code; a substitution changes field values, such as filling a profit centre or the assignment field from a rule. Both are defined in GGB0 and GGB1 with a prerequisite, a check or substitution and a message, and activated per company code and call-up point, document header, line item or complete document, in OB28 and OBBH. They are powerful but hidden: a careless rule can block all postings or quietly change data. Keep rules few, documented and tested.
Validation (GGB0), call-up point: line item
Prerequisite: company code 1000 and GL account 400100
Check: cost centre (BSEG-KOSTL) is not initial
Message: type E, Cost centre is required for travel
Activation: OB28, company code 1000, active49. A MIRO invoice for a moving-average material is priced above the PO, but part of the stock has already been issued. Where does the difference go?
For a material valued at moving average price, SAP posts an invoice price difference to the stock account only for the quantity still in stock, so stock stays correctly valued; the part for quantities already issued goes to the price difference account through PRD, because that stock no longer exists. In the example the ₹1,000 difference splits into ₹600 to inventory and ₹400 to PRD, and the moving average price becomes ₹210. With a standard price, all ₹1,000 would go to PRD. Interviewers use this to test whether you know stock coverage logic.
GR 100 units at PO price ₹200 = ₹20,000
Issued 40 units before the invoice; 60 in stock
MIRO 100 units at invoice price ₹210 = ₹21,000
Difference ₹1,000:
in stock 60/100 ₹600 -> inventory (BSX)
issued 40/100 ₹400 -> price difference (PRD)
New moving average price = (12,000 + 600) / 60 = ₹21050. What is different about asset accounting in S/4HANA compared with classic asset accounting in ECC?
New asset accounting is mandatory. Every depreciation area that posts to the GL does so in real time to the ledgers of its accounting principle, so the periodic posting of values for parallel areas is no longer needed. Asset values sit in the universal journal, and planned depreciation is recalculated as soon as master data or a transaction changes it. The depreciation run posts depreciation for each individual asset to the universal journal. Integrated acquisitions go through the technical clearing account. Plan the chart of depreciation and ledgers together.
51. An Indian company needs Companies Act book depreciation and Income Tax depreciation for the same machine. How do you set this up, and what is the gap in year 1?
Use one asset master with two depreciation areas in the chart of depreciation: a book area using straight-line over the useful life, and a tax area using written-down value at the income tax rate, each with its own depreciation key. With assumed values, a ₹18,00,000 machine put to use on 15 October 2024 with a 15-year life gets ₹60,000 book depreciation for six months, while the tax area at 15% WDV, halved for use under 180 days, gets ₹1,35,000. The ₹75,000 gap is a timing difference for deferred tax. Tax law works on blocks of assets, so reconcile the tax area block-wise.
Machine cost ₹18,00,000, put to use 15.10.2024
Days used in FY 2024-25: 168 (under 180)
Area Method (assumed) Year 1
Book SLM, 15 years, 6 months 60,000
Tax WDV 15% x 1/2 = 7.5% 1,35,000
Timing difference 75,00052. How would you design GST for a company with GSTINs in five states?
Create one business place per GSTIN and link plants to it, so each purchase and sale picks up the right registration. Keep tax lines identifiable by GSTIN, through the business place on every tax line or separate GL accounts, for CGST, SGST, IGST and RCM, because returns and credit are per registration. Tax codes in FTXP and condition records decide intra- or inter-state tax from the supplying and receiving regions. Stock transfers between your own GSTINs are taxable supplies, so they need billing and tax, not just a stock movement. Plan e-invoicing from current SAP documentation.
53. How do you handle ineligible input tax credit, and how do you match SAP input tax with GSTR-2B?
Ineligible credit needs a non-deductible tax code: the tax is calculated as usual but added to the expense or asset cost instead of an input tax account. For an assumed ₹60,000 expense whose 18% GST is blocked, the expense becomes ₹70,800 and no credit is booked. For eligible credit, input tax per GSTIN must be matched every month with the supplier data in GSTR-2B (as of 2025): export the input tax lines with GSTIN, vendor GSTIN, invoice number and date, match them and follow up gaps with the vendor or hold the credit. Store the supplier invoice number in the reference field.
54. How does document splitting handle a payment that clears invoices with several profit centres?
At payment the vendor line is cleared, and the bank and discount lines have no profit centre of their own. Passive splitting copies the account assignments of the cleared items onto the clearing line, and the bank and discount lines are split in the same ratio as those base items. Here the 70:30 split of the invoices carries over, so the ₹98,000 bank line splits ₹68,600 and ₹29,400 and the ₹2,000 discount ₹1,400 and ₹600. Without this, the bank line would land on a dummy profit centre. Test partial payments, residual items and cross-company payments too.
Cleared vendor items: PC-NORTH 70,000, PC-SOUTH 30,000
Payment with 2% cash discount
Line PC-NORTH PC-SOUTH Total
Vendor (debit) 70,000 30,000 1,00,000
Bank (credit) 68,600 29,400 98,000
Discount (credit) 1,400 600 2,00055. Explain activity price planning and under-absorption on a production cost centre with an example.
A production cost centre plans its costs and its output as an activity type, such as machine hours. The plan price, calculated with KSPI or set by hand, is plan cost divided by plan activity, here ₹300 an hour. During the month confirmations charge activity to production orders at that price, crediting the cost centre ₹16,20,000 for 5,400 hours. Actual cost was ₹17,10,000, so ₹90,000 stays as under-absorption. Variance calculation splits it into categories such as input price and volume variance, and you can revalue orders at an actual price from KSII.
Plan: cost ₹18,00,000 / 6,000 machine hours
plan price (KSPI) = ₹300 per hour
Actual: 5,400 hours x ₹300 = ₹16,20,000 credited
actual cost of the cost centre = ₹17,10,000
under-absorbed (debit balance) = ₹90,00056. What does a settlement profile control, and how would you design settlement for a capital investment order?
The settlement profile in the order type controls the allowed receivers such as cost centre, asset or profitability segment, the default receiver, whether the order must be settled in full, and it points to the allocation structure that maps cost elements to settlement cost elements, the source structure and the PA transfer structure for CO-PA. For a capital order building a line in a Pune plant, costs settle to an asset under construction while work runs, then the AuC is settled to the final assets when it is capitalised, and costs that cannot be capitalised go to a cost centre instead.
57. How would you design outgoing payments to Indian banks for a company with many bank accounts?
Use F110 with a payment method per instrument, such as NEFT or RTGS transfer and cheque, and bank determination that picks the house bank and account by payment method, currency and ranking order, with available amounts so no account is overdrawn. The payment medium workbench builds the bank file from a DMEE format tree for the bank layout, and the file goes over a secure host-to-host channel, not a manual upload. Add dual control on vendor bank details, keep the person who runs the proposal apart from the one who releases the file, and use positive pay for cheques where the bank offers it.
58. What happens at year end in FI, and how are balances carried forward?
Before closing, the team posts final adjustments, often in special periods 13 to 16, and gets audit sign-off. The balance carryforward in S/4HANA, FAGLGVTR, carries balance sheet accounts into period 0 of the new year and moves the profit and loss result to the retained earnings account, set in OB53 through the P&L statement account type in the GL master. Customer and vendor balances are carried forward with F.07. After the first run, later postings into the old year carry forward automatically. Before 1 April, make sure document number ranges exist for the new year in FBN1.
59. How are intercompany sales posted when one company code sells and another delivers?
Say a Delhi sales company sells goods shipped from a plant of its Chennai sister company. The sales company bills the customer as usual and records revenue and the receivable. The delivering company code posts the goods issue, so its stock and cost of sales move, then creates an intercompany billing document to the sales company at an internal price, usually condition PI01. That creates a receivable in the delivering company and, through invoice receipt, a payable and cost of goods in the sales company. Consolidation eliminates the internal sale using the trading partner.
60. How would you add a new reporting dimension, such as a sales channel, to finance postings in S/4HANA?
First check whether an existing field can carry it, for example a CO-PA characteristic in margin analysis, which is stored on universal journal lines and filled by characteristic derivation. If a true new coding block field is needed, key user extensibility such as the Custom Fields app can add a field to the journal entry and make it available in posting screens and reports; it must then be filled by derivation, substitution or the source document, or it stays empty. Every new field must be filled consistently from MM, SD and manual journals, so agree the derivation rule before building.
Practice questions for November 2026
New every month3 questions from the SAP FICO mock test, the way they appear in it. A new set comes on the 1st of every month. Pick your answer, then open it.
-
A PO is for 10 units at Rs 1,500. All 10 units are received, but the vendor invoice covers only 8 units. What is left on the GR/IR clearing account?
- Rs 12,000 debit
- Rs 3,000 debit
- Rs 15,000 credit
- Rs 3,000 credit
Show the answer
Answer: Rs 3,000 credit. The goods receipt credits GR/IR with 10 x 1,500 = Rs 15,000; the invoice for 8 units debits it with Rs 12,000. The Rs 3,000 credit left is goods received but not yet invoiced.
-
Which transaction runs a CO-PA profitability report?
- FBL3N
- KE30
- KE51
- KSB1
Show the answer
Answer: KE30. KE30 executes CO-PA reports (KE31 creates them). KE51 creates a profit centre, KSB1 lists cost centre line items and FBL3N GL line items. In S/4HANA Fiori apps also read margin analysis.
-
A cost centre has the lock indicator "actual primary costs" set. What happens?
- Primary cost postings to it are refused, but other flows can continue
- Its plan data is deleted, and only actual postings are accepted
- Its budget is frozen, but all postings continue to be accepted
- Every posting to it is refused, including all allocations received
Show the answer
Answer: Primary cost postings to it are refused, but other flows can continue. Lock indicators work per flow: actual primary, plan primary, actual secondary, plan secondary, revenues. Locking actual primary costs stops FI expense postings but not, for example, allocations.
Ready to apply?
Browse the open jobs on CoreHRx. Create a free profile once and apply with it.