What Actually Comes Up in SAP FI/CO Interviews
Most people walking into an SAP FI/CO interview don't realize that the questions are rarely about defining terms. They want to know whether you have actually configured or supported a live system and what happens when things break. The difference between a hire and a no-hire usually comes down to one or two answers where you show you understand the interaction between modules, not just the screen in front of you. I have sat on both sides of these interviews over the years, so I can tell you what the patterns look like. Let me walk through the ones that actually matter. You will get asked about operating concerns, company codes, and chart of accounts. The trap is giving a textbook definition. Instead, explain how they chain together. The operating concern is the highest level for sales area customization, the company code is the smallest entity that produces its own legal balance sheet, and the chart of accounts can be grouped at the chart level or used individually at the company code level. If a company uses a group chart of accounts, every company code inherits the same account structure but can assign different G/L accounts to different accounts in individual charts.
I once saw a candidate explain this backwards and then try to recover by talking about fiscal years. It did not help. The interviewer had already checked out.
T-Code and Integration Questions
Expect questions like which transaction codes control payment runs, what FBZP does, and how FI connects to MM and SD. You should be comfortable naming FK10N for vendor line item display, FBL5N for customer line items, F-28 for incoming payments, and F-44 for outgoing payment runs. For integration, the critical point is that goods receipt posts to inventory and GR/IR automatically, and billing from SD creates the receivable and revenue entry in FI without manual intervention. The deeper question they sometimes ask is about the GR/IR clearing account. This account should normally sit at zero after reconciliation. If it does not, you have unreconciled invoices or missing goods receipts. I once spent three days tracking down a GR/IR imbalance that turned out to be a single vendor with fifty-plus invoices posted against the wrong company code during a migration. The workaround was a mass reversal through a custom ABAP report, which we then validated against the PO history before clearing.
Get the Full Details
Tax and Payment Procedure Logic
Tax determination in FI is one of those areas where people memorize OBY6 and move on. The reality is more specific. You need to understand how tax conditions link to purchasing groups, country keys, and tax codes. In a real implementation, we had a scenario where a vendor in one country was subject to reverse charge while the same vendor in another country was not, and the tax condition type needed to differentiate based on the plant location rather than just the vendor master. That required extending the access sequence in schema configuration, not just adding another tax code. Payment procedures follow a similar pattern. The ZAP1 transaction controls which check formats, electronic payment media formats, and surcharge calculations apply. Interviewers who know their stuff will ask what happens when a payment run fails for a single vendor due to a blocked house bank account. The answer is that the system marks it as not paid and moves to the next vendor. You do not rerun the entire payment program. You correct the issue and process a correction run for only the affected vendors using the appropriate payment run variant with the exclusions field filled correctly.
Closing and Period-End Processes
The closing cycle is where most juniors stumble. You need to walk through it in order: depreciation run first, then currency valuation if you operate in multiple currencies, followed by accounts payable and receivable reconciliation, balance sheet reconciliation, and finally the period close settings check. I have seen candidates put depreciation after valuation and then get confused when the balance sheet did not tie because the revaluation had already happened on stale asset values. A counter-intuitive point that most beginners miss is that the fiscal year variant does not determine the number of special periods for asset accounting. Asset depreciation areas have their own posting periods controlled separately. If your asset depreciation area is set to a different fiscal year variant than the general ledger area, you can end up with mismatched posting periods that cause the closing to fail silently until you notice the asset register does not reconcile to the GL.
Common Pitfalls That Show Up in Interviews
The biggest mistake I see is treating FI and CO as separate systems. They are not. Cost center allocation runs pull from FI postings, product costing feeds into CO-PC and then posts results back to FI, and internal orders sit right in the middle of both. If you cannot explain how a settlement from an internal order to a cost center affects both the CO overhead calculation and the FI general ledger, you are not ready for a senior role. Another frequent blind spot is master data governance. Vendor and customer master records contain more fields than most candidates realize, especially the reconciliatory account indicator and payment blocking reasons. A vendor marked with a reconciliation account in the company code view is what ties the AP subledger to the general ledger. Change that setting by accident and your reconciliation report breaks immediately.
What They Are Really Testing
Interviewers are looking for three things: whether you understand the data flow between FI and other modules, whether you know where errors surface and how to trace them, and whether you can explain configuration decisions in business terms rather than just transaction codes. The last one is the one that gets people hired or rejected. When they ask why you set up a particular clearing account or why you chose one payment method over another, do not say it was the standard configuration. Say what business requirement drove it. If you cannot, be honest about that instead of bluffing. I have watched strong functional consultants get passed over because they tried to sound impressive and ended up contradicting themselves within two minutes. A calm, accurate answer about something you know well beats a flashy answer about something you do not. There is no single document that covers every possible question. The best preparation is reviewing your own projects, understanding why each configuration choice was made, and being able to explain the downstream impact of changing it. That is what separates people who have done SAP from people who have only read about SAP.
