SAP FICO (Financial Accounting and Controlling) is one of the most in-demand SAP modules. These SAP FICO interview questions cover the organisational structure, GL, AP, AR and asset accounting for freshers, then controlling, integration with MM and SD, period-end closing and S/4HANA Finance for experienced consultants.
30 questions · Updated
Fundamentals, definitions and simple scenarios. Good for freshers and warm-ups.
FI (Financial Accounting) records transactions for external reporting: general ledger, accounts payable, accounts receivable, asset accounting and bank accounting, producing the balance sheet and profit and loss statement.
CO (Controlling) is for internal management reporting: cost centres, profit centres, internal orders and product costing.
In S/4HANA both post into one table, the Universal Journal (ACDOCA).
A company code is the smallest unit for which a complete set of financial statements is produced, usually one legal entity.
Above it, a company groups company codes for consolidation.
A chart of accounts lists the GL accounts, a fiscal year variant defines the periods, and in CO a controlling area groups company codes for cost accounting.
Business areas and segments support extra reporting.
A fiscal year variant defines the fiscal year and its periods, for example K4 (calendar year with 12 periods and 4 special periods) or V3 (April to March, common in India).
Special periods are used for year-end adjustments.
A posting period variant controls which periods are open for posting, so finished months can be closed to prevent changes.
The operating chart of accounts is used for daily postings in company codes and is mandatory.
The group chart of accounts supports consolidated reporting across companies by mapping operating accounts to group accounts.
The country chart of accounts meets local legal reporting requirements through an alternative account number.
A company code must have an operating chart of accounts.
A GL account (FS00) has a chart of accounts segment, with the account number, description, account type (balance sheet, primary or secondary cost element in S/4HANA, or non-operating) and account group, and a company code segment with the currency, tax category, open item management, line item display, sort key, field status group and reconciliation account type. The account group controls number ranges and field status.
A document type classifies an accounting document and controls which account types it can post to and its number range, for example SA for GL postings, KR for vendor invoices, KZ for vendor payments, DR for customer invoices and DZ for customer payments. Number ranges (FBN1) assign document numbers per company code and fiscal year, internally or externally.
A posting key is a two-digit code that tells SAP whether a line item is a debit or credit, which account type it posts to and which fields appear. Examples are 40 (GL debit), 50 (GL credit), 31 (vendor credit, for an invoice), 21 (vendor debit), 01 (customer invoice, debit) and 15 (incoming payment, customer credit).
A field status group, assigned in the GL account's company code data, controls which fields are required, optional or suppressed when posting to that account, such as making a cost centre mandatory for expense accounts or business area optional.
Field status variants group these settings and are assigned to company codes.
Posting keys also have field status, and the stricter setting wins.
Tolerance groups limit the amounts employees can post and the payment differences they can accept.
Employee tolerance groups (OBA4) set maximum document and line-item amounts and permitted cash discount and payment differences; customer and vendor tolerance groups (OBA3) set differences allowed when clearing open items.
Users are assigned to groups so larger postings need authorised staff.
A held document is saved temporarily with your own reference, without a document number or validation, so you can finish it later.
A parked document gets a document number and can be checked, changed and posted by someone else, which supports approval workflows, but does not update balances.
A posted document updates the ledgers and can only be reversed, not deleted.
FB50 (GL posting), FB60 (vendor invoice), FB70 (customer invoice), F-53 and F-28 (outgoing and incoming payments), F110 (automatic payment program), FBL1N, FBL3N and FBL5N (vendor, GL and customer line items), FS00 (GL master), OB52 (open and close periods), FB08 (reverse document), FAGLB03 (GL balances) and KS01 (create cost centre). In S/4HANA many of these also have Fiori apps.
Applied problems, trade-offs and questions about your own projects.
A reconciliation account is a GL account linked to a subledger, such as vendors, customers or assets.
Postings to individual vendor or customer accounts automatically update the reconciliation account, and it cannot be posted to directly.
This keeps the general ledger and subledgers always in agreement.
Normal GL accounts are posted to directly.
When goods movements happen in MM, such as goods receipt or goods issue, the system finds the GL accounts automatically through configuration in transaction OBYC.
It uses the valuation class of the material, the transaction key (such as BSX for inventory, WRX for the GR/IR clearing account and GBB for offsetting entries) and the valuation area.
This is how logistics transactions post to finance without manual entries.
A vendor invoice for a purchase order is entered in MIRO and matched with the PO and goods receipt, clearing the GR/IR account and crediting the vendor.
Non-PO invoices are posted in FB60.
Payments are made with the automatic payment program (F110), which selects due items based on payment terms and methods, posts the payment and generates payment files, or manually with F-53.
A cost centre collects costs for a department or area of responsibility, such as HR or IT, for cost control.
A profit centre represents a part of the business, such as a product line or region, for which revenue and costs are reported to measure profitability.
An internal order collects costs for a temporary activity, such as a marketing campaign or event, which are then settled to a cost centre or asset.
Customer invoices are posted from SD billing or FB70 and payments are received and cleared with F-28 or automatically from bank statements.
Open items are monitored with FBL5N and ageing reports.
Dunning (F150) sends reminder letters to customers with overdue items based on a dunning procedure that defines levels, intervals, charges and texts, and can block further sales.
A chart of depreciation defines depreciation areas, such as book depreciation and tax depreciation (for the Indian Companies Act and Income Tax Act).
Asset classes group assets such as buildings, vehicles and computers and supply default settings, including depreciation keys.
Assets are created with AS01, acquired through purchase orders or F-90, transferred, retired, and depreciated by running AFAB at period end.
House banks and their accounts are set up with GL accounts for the main bank account and clearing accounts for incoming and outgoing payments.
Electronic bank statements, in formats such as MT940 or CAMT.053, are uploaded with FF_5 or Fiori apps, and interpretation algorithms match lines to open items and post clearing entries automatically.
Unmatched items are processed manually (FEBAN).
In FBZP you configure all company codes (paying company code, tolerance days), paying company codes (minimum amounts, forms), payment methods per country (such as bank transfer or cheque, with required master data and payment medium format), payment methods per company code (amount limits, bank selection), bank determination (ranking order and available amounts) and house banks. F110 then runs proposals and payments.
Document splitting in the new GL splits line items by characteristics such as profit centre, segment or business area, so complete balance sheets and profit and loss statements can be produced for each.
For example, a vendor invoice for expenses in two profit centres also splits the vendor and tax lines between those profit centres.
It is configured with splitting methods, item categories and business transaction variants.
The leading ledger (0L) contains the full set of accounts according to the main accounting standard, such as Ind AS, and is integrated with CO. Non-leading ledgers support parallel accounting for other standards, such as IFRS or local GAAP, or tax reporting.
Ledger groups let an adjustment posting be made only to selected ledgers.
In S/4HANA extension ledgers store only the differences.
Profitability Analysis analyses profit by market segments such as customer, product, region and sales channel.
Costing-based CO-PA uses value fields and its own tables, while account-based CO-PA uses GL accounts and reconciles directly with finance; in S/4HANA account-based (margin analysis) is integrated into the Universal Journal and recommended.
Billing documents, settlements and assessments feed it.
System design, deep internals, leadership and tough follow-ups.
Typical steps are opening the next period, posting accruals and recurring entries, running depreciation (AFAB), revaluing foreign currency open items (FAGL_FCV), clearing GR/IR and checking for open items, assessments and distributions in CO, settling internal orders, reconciling subledgers with the GL, and generating financial statements before closing the period. The Financial Closing Cockpit helps schedule and track these tasks.
The Universal Journal (ACDOCA) stores FI, CO, asset accounting and material ledger postings in one table, removing the need to reconcile FI with CO and making totals and index tables unnecessary. Cost elements became GL accounts, Business Partner replaced separate customer and vendor masters, new asset accounting is mandatory, the material ledger is active, and reporting is real time through Fiori apps.
GST uses the condition technique: tax procedure TAXINN with condition types for CGST, SGST, IGST and UTGST, with GL accounts assigned to each.
Business places and section codes represent GST registrations, and each state registration (GSTIN) is maintained.
Materials carry HSN codes and services SAC codes, and condition records determine rates.
Input tax credit and output tax postings feed the GST returns, often through SAP's e-invoicing and e-way bill integration.
Standard cost estimates (CK11N for a single material, CK40N for mass costing) calculate a product's cost from its bill of materials, routing, activity prices and overheads, and when released they update the standard price in the material master. During production, actual costs are collected on production orders, work in progress is calculated, and variances between actual and standard costs are calculated and settled to finance and CO-PA.
Both allocate costs from a sender cost centre to receivers using cycles and segments.
Assessment uses a secondary cost element (an allocation account in S/4HANA), so the original cost element is lost on the receiver, which suits allocating combined overheads such as building costs.
Distribution keeps the original primary cost element, so receivers see the actual expense types, and only works for primary costs.
When one company code pays or posts on behalf of another, cross-company code postings automatically create intercompany receivables and payables using clearing accounts configured in OBYA.
Intercompany sales use SD and MM with internal billing between company codes.
At period end these balances are reconciled with intercompany reconciliation tools and eliminated during consolidation.
Greenfield is a new implementation that redesigns processes around standard S/4HANA and migrates only needed data.
Brownfield is a system conversion of the existing ECC system, keeping processes and history, with a technical conversion and simplification checks.
Selective data transition (bluefield) combines both, moving chosen data and processes.
Finance needs particular care with ledgers, assets, the customer-vendor to Business Partner conversion and open items.
The GR/IR clearing account holds the difference between goods received and invoices received for purchase orders.
I analyse open items with the GR/IR monitoring apps or MB5S, find causes such as missing invoices, quantity or price differences and wrong postings, and get them corrected in MM.
Small residual differences are cleared with MR11 after approval, and at period end GR/IR is regrouped (F.19 or Fiori) into goods received not invoiced and invoices received not delivered.
See all SAP & CRM Consultant interview questions, covering SAP FICO, SAP MM, SAP SD, SAP ABAP, Salesforce and more.