Last updated: October 15, 2026
By Tom Kenaley, President and Senior Partner, KORE1
SAP S/4HANA consultant interview questions in 2026 should hand the candidate real conversion artifacts, such as a precheck printout, a downtime window, and a custom report that still reads old tables, then ask what they would do first. Module trivia comes later, if at all. Plenty of people pass that part.
A building-products manufacturer in Chattanooga hired a finance lead last year who interviewed beautifully. Universal journal, document splitting, parallel ledgers. She answered every question the panel had, and the panel had borrowed its questions from a good list.
Then the first mock conversion stopped cold.
The Simplification Item Check had flagged customer and vendor integration, the step where every customer and supplier record has to become a business partner before the conversion is allowed to run. Roughly 8,400 vendor records had no partner yet. About a third of them were duplicates left over from a 2019 acquisition, and the duplicates had to be cleaned before anything could be synchronized. She had done two S/4HANA projects. Both were greenfield builds, where business partners get created fresh and nobody ever opens the synchronization cockpit. Smart person. Wrong history. The program lost three weeks while a contractor we sent sorted the vendor master, and the finance lead, to her credit, said in the retro that nobody had ever asked her about it.
Nobody had. That is the gap this piece is written for.
We see that pattern on the S/4HANA consultant staffing side of our ERP practice often enough that we stopped calling it bad luck. Some of the ground is already covered elsewhere, so I will skip it here. Choosing between brownfield and greenfield, comp bands, and the five conversion questions about custom code triage, cutover weekend, and the first close all sit in our 2026 guide on hiring for S/4HANA conversions. Module-by-module probing for FICO, MM, SD, ABAP, and integration lives in our SAP consultant interview questions. What follows is the part those two leave alone, the paperwork and plumbing of an actual conversion.
One disclosure, then the questions. Our fee comes due only when you hire a candidate this firm put in front of you, so read everything below knowing that I would profit, at least a little, from you finding this hard to do alone. Run the loop yourself if you like. It works without us.
Why an S/4HANA Interview Is Not an SAP Interview
An SAP S/4HANA consultant interview tests whether a candidate can move a company’s SAP system onto the HANA data model and keep it running afterward. Module knowledge is assumed going in. The questions that matter probe conversion prechecks, data loads, custom code that still reads retired tables, downtime planning, Fiori roles, and clean-core extensions.
Most interview lists stop at the first sentence of that definition. They ask what ACDOCA is. Fine, but a candidate can learn that from a training course in an afternoon, and the training course will not teach them what to do when the business partner precheck throws four thousand errors on a Thursday.
The deadline makes this urgent rather than academic. Back in February 2020, SAP’s maintenance announcement set the end of 2027 as the last year of mainstream support for ECC’s core, and priced the optional three extra years, 2028 to 2030, at two points above the existing maintenance basis. Every company still on ECC is now hiring for the same skills in the same two or three years. Federal wage data barely registers it. There is no S/4HANA occupation in the federal tables, so we lean on the BLS profile for computer systems analysts as a stand-in. Its May 2025 median was $105,850, and the outlook through 2035 calls for 8 percent growth with roughly 32,900 job openings each year. That category is full of reporting analysts. Treat it as a floor.
KORE1 has recruited for enterprise IT since 2005 and works searches in better than 30 U.S. metros. On a typical IT req, the first qualified candidate reaches the client in about 17 days. S/4HANA conversion seats run slower than that average, mostly because the people who have run a real precheck are already booked.
The Precheck Printout Round
If a client tells me they only have time for one round, this is the one I tell them to run. Print a page from a Readiness Check or Simplification Item Check result. Your own, with the company name blacked out, or a made-up one built from the rows below. Hand it over. Give them fifteen minutes and one instruction. Sort these into three piles, the ones that stop the conversion from running, the ones that stop you going live, and the ones that can wait until after.
No laptop. No SAP system. Just the page and a pen.
| Row on the printout | Weak answer | What you want to hear |
|---|---|---|
| Customer and vendor integration, 8,400 vendors without a business partner | “Basis handles that during the upgrade.” | Blocks the run. Clean duplicates first, map number ranges and account groups, then synchronize in the cockpit (MDS_LOAD_COCKPIT) well before the mock. |
| Credit management, FI-AR-CR in use | “It converts automatically.” | Moves to SAP Credit Management. Limits, risk classes, and blocked-order behavior need re-testing with the credit team, not just a migration step. |
| SD rebate agreements still open | “We’ll keep using them.” | New rebates run as condition contracts under settlement management. Decide which agreements settle out the old way and when sales stops creating them. |
| Material number field length, extended to 40 characters | “Nice, more room.” | Usually left off at first. Interfaces and custom code that assume 18 characters get checked before anybody switches it on. |
| Output management, NAST-based forms | “Forms are a phase-two thing.” | Pick per document type, new BRF+ output or the old framework where still allowed. Invoices and delivery notes break customer-facing first. |
| Asset accounting, classic model active | “Finance will check it.” | New asset accounting is mandatory. Every depreciation run posted, periods clean, and the fixed asset team in the room for the mock. |
What you are grading is the sorting, more than any single row. A finance lead who puts credit management in the “later” pile has never watched a sales order sit blocked on go-live morning. Someone who files the material number row under “blocks the run” is being cautious without knowing why. And the strongest candidates do something nobody asked for. They ask what release the check was run against, and how old the printout is. Simplification items change between releases. A six-month-old Readiness Check is a historical document.
Watch who they say owns each row, too. “The SI” is an answer. It is not a good one.
Questions for the Finance Seat
Skip the universal journal lecture. The module guide covers it, and every candidate has rehearsed it.
“The trial load left $212,000 between customer open items and the reconciliation account. Where do you look first?”
A real data migration produces a difference like this almost every time. The question is whether they have chased one. Good answers start with what the number is made of rather than with a fix. Down payments and other special G/L items post to their own reconciliation accounts, so a candidate who has done this will ask whether the open item extract included them. Then foreign currency items valued at a different rate. Then timing, meaning items cleared in the old system between the extract and the load. Somebody who has really done it will also tell you who signs off the tie-out and in what format, because auditors will ask for it later.
The weak answer is “we’d re-run the load.” That changes nothing. Same extract, same gap.
“What has to be true in ECC before the finance data migration is allowed to start?”
Listen for a checklist from memory, not from a slide. Periods closed. Depreciation posted for every period. Ledgers reconciled with each other before conversion, because the migration will happily carry an existing inconsistency into the new tables and make it harder to find. Some candidates mention running the reconciliation reports twice, once at the mock and once at the dress rehearsal, which tells you they learned it the hard way.
Then ask who in the client’s finance team they needed, by job title. A controller, a fixed asset accountant, somebody from AR. A consultant who says “finance” as a single noun has not spent a week chasing three different people for signatures.
“Cost elements are G/L accounts now. What does your controller notice first?”
Short question, short answer expected. Secondary cost elements become accounts in the chart, so account maintenance and cost element maintenance stop being two jobs done by two teams. Good candidates name the political part, which is who now owns creating them.
Questions for the Logistics Seat
Logistics candidates tend to get waved through in conversion interviews, mostly because the order-to-cash and procure-to-pay processes look familiar on the surface and the panel runs out of time after spending forty minutes on finance. Purchase orders still look like purchase orders. That is exactly the trap.
Start with rebates, because the answer reveals whether they worked a sales-side conversion or only read about one. “A distributor runs 340 active rebate agreements with three customers on a calendar-year cycle, and you go live in August. What happens to those agreements?” You want condition contracts, settlement management, and a cutover decision about which agreements settle out under the old process before sales stops creating new ones. A candidate who has lived through it will also mention the sales reps, who will keep trying to create the old agreement type for at least a month.
Output is next. Ask which documents they moved to the new output management on their last project and which ones stayed behind. Nobody moves everything at once. If they claim they did, ask how long the invoice forms took. Delivery notes and invoices are the documents a customer sees first, and customers notice.
MRP is a quick one. Ask whether their last client ran MRP Live and what the planners complained about. Planners always complain about something.
And then the material number. “A customer’s EDI map expects 18 characters. Someone wants to switch on 40-character material numbers in year two. Who has to say yes?” It is a better logistics question than it looks, because the honest answer involves the EDI team, the label printers, and two outside trading partners.
Custom Code That Still Reads the Old Tables
For the technical seat, hand them a description of one custom report rather than asking them to recite anything. Here is the one we suggest.
A Z-report built in 2014 reads open vendor items straight from BSIK, pulls totals from FAGLFLEXT, and, at the end of each run, writes a status flag back into one of those totals tables so the next run can skip what it already processed. Then ask two things. Will it still run after conversion? And which part breaks?
The reads mostly survive. In S/4HANA, the old index and totals tables in finance became compatibility views that pull their data from the universal journal, so a SELECT against BSIK or FAGLFLEXT still returns rows. Slower, sometimes much slower, but rows. The write is the problem. You cannot write into a view, and writing to SAP standard tables is exactly what SAP’s clean core level concept, published in August 2025, places at level D, the not-recommended end of its A through D scale. A strong candidate catches the write within a minute and proposes moving the flag into a custom table the report owns. The best ones also ask what reads that flag, because something always does.
Inventory has the same shape. MKPF and MSEG gave way to MATDOC, with compatibility views on top. Ask the candidate whether they have seen a report get slower after conversion and what they did about it. Developers who have remediated real code have a story about a nightly job that went from ten minutes to three hours.
Then a design question. “Sales wants a customs tariff code on the sales order, printed on the delivery note. How do you build it?” A clean-core habit sounds like a key-user custom field, added through the Custom Fields app and pushed to the form and the API without touching code. The older habit sounds like an append structure on the sales header, a user exit, and a copied print program. Both work on day one. Only one survives the next upgrade without somebody re-testing it, and that difference is the whole conversation about clean core in a single question. If your seat is pure development, our ABAP on HANA developer staffing page lays out how we screen that lane.
The Downtime Window Question for Basis
Basis candidates get asked about HANA sizing a lot. Ask about time instead. Hours are what the business actually cares about.
Give them the scenario on paper. Production is 7 terabytes on Oracle. The second test conversion, run on a full copy, took 61 hours from the start of downtime to the system handed back. The business will give you Friday at 6 p.m. to Monday at 6 a.m., which is 60 hours, and finance wants 12 of those to validate numbers and decide whether to proceed. So the technical work has to fit in about 48. Where do the 13 hours come from?
Nobody fixes this with one trick, and a candidate who names a single lever, whether it is more hardware or more parallel processes, has probably read about downtime planning rather than sat through a weekend of it. What you want is a mix, roughly in this order.
- Shrink the database first. Archiving and housekeeping on the usual giants, IDoc tables, change documents, application logs, often buys more than any tuning.
- Move what you can into uptime. Downtime-optimized options in SUM copy selected large tables while the system is still live and catch up the changes later.
- Tune the run itself, process counts and table splitting, using the durations from the last mock instead of guesses.
- Then talk to the business about the window. Sometimes the right answer is a four-day weekend.
Here is the follow-up that sorts the experienced from the well-read. Ask which tables they could not move into uptime. The ones touched by the new S/4HANA data model, the finance and inventory tables that get restructured during conversion, cannot be selected for that treatment in a system conversion, and SAP gates the more aggressive downtime-optimized conversion behind a training assessment and a password requested through a support ticket. Somebody who has used it will know about the password. They will probably sigh about it.
Last question for this seat. How many mock conversions did their last program plan, and how many did it actually run? Three planned and five run is a normal, honest answer. One planned and one run is a story about luck. Our SAP Basis administrator staffing page covers the rest of that profile.
Fiori Roles, or Why Go-Live Monday Goes Badly
Every conversion has a morning where half the accounts payable team can’t do their jobs. It is almost never a functional problem. It is roles.
So ask the scenario. Two AP clerks have the same job title. Both see the Manage Supplier Line Items tile on their launchpad. One opens it and sees invoices. The other opens it and gets an empty list, no error. What happened?
The answer you want separates two layers. The launchpad side, business catalogs and the spaces and pages SAP introduced with the 2020 release to replace the old groups layout, decides whether a tile shows up and whether the app launches. The back-end role decides what data comes back. An empty list with no error points at the back end, often a company code authorization such as F_BKPF_BUK that one clerk has and the other doesn’t. A good candidate says they would run an authorization trace, SU53 or STAUTHTRACE, on the clerk with the empty screen rather than comparing the two roles by eye.
Ask the security person and the finance lead the same question. You learn something different from each. The finance lead who knows the answer has been through a go-live. The one who says “that’s a security ticket” is probably right, and has also never been the person the AP manager called at 7:40 a.m.
Public Cloud Résumé, Private Cloud Job
More and more of the résumés we screen come off S/4HANA Cloud Public Edition projects, usually greenfield builds at mid-sized companies that chose the subscription model so they would never have to run a conversion again. That experience is real, and it is different. Public cloud configuration runs through Central Business Configuration and self-service configuration screens rather than the full IMG, extensions stay on released APIs, and the system takes two releases a year, 2508 and 2602 being the recent ones, whether you were ready or not.
If your program is a private cloud or on-premise brownfield conversion, ask it straight out. “Your last two projects were public cloud. Here, you’ll have SPRO, fifteen years of custom code, and a release we choose ourselves. What do you expect to find hard?” The answer you want is specific and a little humble. Custom code volume. Configuration nobody documented. Freedom to do things the wrong way. A candidate who says nothing will be different hasn’t thought about it, and those six weeks of learning will be paid for by your schedule.
The reverse happens as well. A brownfield veteran moving to public cloud will reach for the IMG, and the IMG isn’t there.
Run It in Four Sittings
You do not need every question above. You need the ones that match the seat. Here is how we suggest clients split it.
| Sitting | Who runs it | What goes in | Time |
|---|---|---|---|
| Screen | Recruiter or program lead | Edition and path of the last two projects, and what stopped the first mock conversion | 30 min |
| Precheck printout | Program lead plus one functional lead | The sorting exercise, then the seat questions for finance or logistics | 60 min |
| Seat round | Your technical or Basis lead | Z-report, downtime window, or Fiori roles, whichever matches the seat | 45 min |
| Business sitting | Controller or operations owner | The $212,000 tie-out, or the rebate cutover, explained to a non-SAP person | 30 min |
The last sitting matters more than it looks. A conversion consultant spends half their week explaining things to people who do not care what ACDOCA is. Put one of those people on the panel.
Move fast. The candidates who can pass this loop are usually juggling two or three other conversations at once, and every extra round you add because someone on the panel felt left out is another week in which a faster company makes the offer. Still drafting the posting? Our S/4HANA consultant job description template separates the conversion seats before the panel ever meets, and the broader SAP consultant job description template covers roles outside the conversion.
What a Good Candidate Asks Back
Strong S/4HANA people interview you, and their questions are worth more than most of the answers you get.
Which release and feature package is the target? Someone who asks this knows simplification items move between releases. When was the last Readiness Check run, and has anyone read it? You will be surprised how often the honest answer is “the SI ran it last year.” Who owns the data cleanup, us or the partner? That one is a test of your SOW, and it is fair.
Watch for anybody who asks how many mock conversions are in the plan, because people only think to ask that after they have sat through a program that planned exactly one and then spent a weekend finding out why that was optimistic.
And if a candidate asks nothing about the system at all and everything about the rate, that is information too. Not always bad information. But information.
Before Your Panel Sits Down With a Conversion Candidate
Can we use the same questions for a contract consultant and a direct hire?
Mostly, though the weight shifts. A contractor on a dated conversion should ace the precheck printout and the seat round, because they are being paid to have done this before. A permanent hire who inherits the system needs a stronger business sitting, since they will be explaining the system to your controller long after the partner leaves. If the role is a conversion seat with an end date, our contract staffing model is usually the cleaner fit.
Is it fair to hand a candidate a real Readiness Check from our system?
Yes, once the company name and anything sensitive come off it. A real printout beats a made-up one because the candidate can’t have seen it before, and their questions about it tell you a lot. Remove customer names, vendor counts that identify you, and anything under NDA. Keep the release, the item titles, and the error counts. Those are what the exercise is about.
How senior does someone need to be to pass the precheck round?
Three or four years and at least one brownfield conversion, roughly. Juniors can sort some rows correctly from training, but they usually can’t say who owns each item or why the release matters. That is fine for an associate seat. For a lead, a credit management row filed under later is a real warning, because that row turns into blocked sales orders on go-live morning.
Our partner says these questions are their job. Should we still ask them?
Ask them anyway, because the consultants you hire directly are the ones who stay. Your integrator owns delivery under the SOW and will run the prechecks. Your own people need to understand the results well enough to challenge them, or you will be signing off on decisions nobody inside the company can explain. Fifteen minutes with the printout shows you who can.
What does an S/4HANA consultant cost if they pass all of this?
$110 to $200 an hour on contract in 2026, with direct-hire bases roughly $110,000 to $195,000 for functional consultants and more for architects. The people who handle the precheck and downtime rounds well sit at the upper half of those bands. Pay by workstream and city is in our SAP S/4HANA salary guide for 2026, and the salary benchmark assistant narrows it to your metro.
Can the precheck and seat rounds be done over video?
All four sittings work remotely, and most of our S/4HANA searches run that way. Share the printout as a static image or a PDF rather than a live system, and ask the candidate to talk through their sort out loud. The only thing you lose on video is watching someone write on paper, which matters less than people think. What matters is the order they work in.
Print the Precheck Before You Book the Panel
Most failed S/4HANA hires we get called about did not fail on knowledge. They failed on a history the interview never asked about. Greenfield only. Public cloud only. Never been in the room when a mock conversion stopped.
So decide what your program actually looks like before the panel meets. Path, edition, release, and which seat. Then print one page from your own precheck and hand it across the table. Fifteen minutes with that page will tell you more than an hour of module questions.
If you want a shortlist built around your conversion rather than a keyword, talk to a recruiter on our SAP desk. Our direct placements hold at 92 percent after twelve months, and on conversion seats most of that comes from asking questions like these before an offer goes out, when changing your mind is still free. For the finance modules specifically, see our SAP FICO consultant staffing page. Hiring across more than one ERP? The platform-neutral version of this loop is in our ERP consultant interview questions.
