What Actually Comes Up When You Walk Into an SAP FICO Interview
Most people preparing for these interviews spend weeks memorizing textbook definitions, which doesn't help when the interviewer asks you to walk through a real scenario. The gap between knowing what FI and CO modules are and being able to explain how they interact under pressure is where candidates typically stumble. I've sat on both sides of that table more times than I'd like to count, so I'm going to break down what actually matters, what trips people up, and how to approach this without wasting your time. Here's the thing about SAP FICO interviews: the questions reveal whether someone has actually configured the system or just read a certification guide. The standard ones come up every time — tell me about the integration between FI and CO, explain document splitting, walk me through the financial statement version setup. But the real differentiator is what comes after. When someone says they understand document splitting, I'll ask what happens when a cost center isn't assigned to an item and the document is parked. If they hesitate or give a generic answer, that tells me everything I need to know. Technical depth matters more than breadth here. I once had a candidate who could recite every menu path for OBYC but couldn't explain why G/L account 40011000 appeared in their test environment when it wasn't in the configuration at all. Turns out it was a residual clearing account left over from a prior test script that never got cleaned up. That kind of answer separates people who've actually worked in systems from people who've only studied for exams.
Integration Scenarios You Need to Know Cold
The FI-CO integration is the single most important concept in these interviews, and it's also the area where most candidates give surface-level answers. Here's what you actually need to understand: every single CO posting triggers a corresponding FI posting, but not every FI posting triggers a CO posting. The direction is not symmetric. When you post a goods receipt in MM, the system debits inventory and credits GR/IR in FI, but it also posts to the relevant cost object in CO. Understanding which postings are integrated and which aren't will save you in almost any interview. I remember working on a project where a client's month-end close was taking four days instead of one. The root cause turned out to be a misconfigured automatic account determination rule in OBYC that was routing intercompany eliminations through a manual reconciliation account instead of an automated one. We fixed the movement type to account assignment group mapping in the customizing, and the close dropped to two days. If someone asks about integration issues in an interview, that's the level of detail they're looking for — not that FI and CO are connected, but how a specific configuration choice ripples through the entire process.
Cost Center Accounting and Profit Center Accounting
These two areas come up constantly, and candidates frequently confuse how they function. Cost center accounting tracks where money is spent within an organization. Profit center accounting tracks profitability by business segment. The distinction matters because the reporting structures are completely different, and mixing them up during an interview is an immediate red flag. One thing most guides don't emphasize enough: distribution and assessment cycles in cost center accounting are not interchangeable. Distribution moves primary costs only — things like salaries or rent. Assessment moves both primary and secondary costs by allocating them through cost segments. If you're assigning overhead from a maintenance cost center to production cost centers and your numbers look wrong, check whether you set up distribution when you should have set up assessment, or vice versa. I spent three weeks tracking down a reporting discrepancy that boiled down to this exact mistake on a client engagement. For profit center accounting, the key interview topic is profit center intercompany elimination. When Company A sells to Company B and both are profit centers within the same group, the system needs to eliminate the internal revenue and cost of goods sold automatically. This requires the right settings in SPAU and the elimination program to run correctly. Most candidates haven't touched this in a real implementation.
Get the Full Details
Technical Configuration Areas That Separate Juniors From Seniors
If you want to stand out, focus on the configuration paths that most people skip. Let me give you a few that actually come up. Automatic payment program configuration in FBZA and FZ09 is deceptively complex. The held item functionality, payment methods per company code, and bank determination logic together create a configuration area where small mistakes cause big problems. I've seen payment runs process the wrong vendor bank account because someone changed the country-specific payment method without updating the bank master data template. In an interview, being able to walk through the payment run step by step — from creating the payment proposal to releasing the blocked items and executing the run — demonstrates practical knowledge that certification studying alone won't give you. Parallel accounting and ledger groups are another area where interviewers test real understanding. If a company operates in Germany and the US, they might use IFRS and US GAAP simultaneously. The ledger concept in ECC versus S/4HANA is different, and that distinction matters. In ECC, you configure parallel ledgers through valuation views. In S/4HANA, the universal journal (table ACDOCA) handles everything in a single table. Saying you understand this transition shows you've actually kept up with the product evolution rather than studying from materials that are five years old.
ABAP and Debugging — Don't Pretend You Don't Know This Exists
Even if you're purely functional, interviewers will ask about your ability to debug basic issues. You don't need to be an ABAP developer, but you should know how to use SE38, SE16N, and the debugger to trace a posting. I once had a situation where a customer payment was posting to the wrong G/L account. Instead of immediately calling the basis team, I used SE16N to check the BSEG table for the document, traced back through BKPF, and identified that a custom routine in the account determination was overriding the standard logic. Fixed it in OBYC within an hour. Being able to describe that kind of troubleshooting process in an interview is worth more than any certification badge. Here are the patterns I see repeatedly, and they're all fixable with the right approach. First, candidates define terms instead of explaining processes. When asked about opening balance migration, don't just say it's transferring old data into the new system. Walk through the steps: extract from legacy, reconcile totals, load using CIA or LSMW, validate against the general ledger, and resolve discrepancies. The process is what matters, not the definition.
Second, they treat SAP as if it works the same everywhere. It doesn't. A configuration that works perfectly in a greenfield implementation can cause problems in a brownfield migration. I learned this the hard way when a client's existing custom tables from a prior upgrade conflicted with a new S/4HANA conversion. The standard interview answer about migration strategies doesn't cover the edge cases where your master data cleanup reveals that 40 percent of your vendor masters have incomplete tax numbers, and you have to decide whether to freeze master data creation or proceed with gaps. Third, candidates don't ask clarifying questions. If an interviewer asks about invoice verification, responding with a detailed walkthrough of MIRO without first asking whether they mean the standard three-way match or a specific variant for consignment or subcontracting shows you're reciting rather than thinking. The best answers come from understanding what the interviewer actually needs.
How to Prepare Without Wasting Six Months
Focus on three things. First, understand the configuration paths for your core areas — FI-GL, FI-AP, FI-AR, and CO-PC. Know the T-codes, the customizing steps, and what breaks when something is configured incorrectly. Second, practice explaining integration points out loud. Pick a transaction like goods receipt and walk through every system action from the moment the goes into the warehouse to the moment the cost center is charged and the invoice is ready for verification. Third, read through at least one implementation methodology document, whether it's ASAP or Activate. Not to memorize it, but to understand the lifecycle perspective that senior interviewers expect. There's no substitute for hands-on practice. A trial system or a sandbox license lets you make mistakes without breaking production. The configuration you understand because you broke it and fixed it will come out naturally in an interview. The configuration you only read about will feel stiff and rehearsed.
