Home / SAP staffing / Evaluating SAP functional consultants

How to evaluate an SAP FI/CO, MM or SD consultant before you hire

A strong SAP functional consultant knows the module, the business process behind it and the release your team runs. This guide shows how to test all three: what to put in the role, the signals that separate S/4HANA experience from ECC, questions for FI/CO, MM and SD, red flags, and a one-page scorecard.

Book a hiring call Call (561) 567-8381

Module, platform and role: get these right first

Most mismatched résumés start with a job title that mixes these up.

Term	What it means	Example
Module	The business area configured in SAP	FI/CO (finance and controlling), MM (procurement and inventory), SD (order to cash)
Platform	The SAP release and how it's deployed	ECC 6.0, or S/4HANA on-premise, private cloud or public cloud
Role	What the person does	A functional consultant gathers requirements, configures the module and tests it with the business. Code, system administration and interfaces belong to technical specialists.

A posting for an "S/4HANA consultant" with no module attracts everyone. A posting for "S/4HANA FI/CO consultant, brownfield conversion, asset accounting and period-end close" attracts the people you need.

S/4HANA or ECC: signals in the interview

Ask what changed for their module in S/4HANA. Someone who has done the work answers in specifics.

Module	What an S/4HANA-experienced consultant can explain
FI/CO	The Universal Journal (one line-item table, ACDOCA, for finance and controlling), cost elements kept as G/L accounts, new asset accounting, and customers and vendors as Business Partners
MM	Suppliers as Business Partners, material documents in one table (MATDOC), and Fiori apps for purchasing and inventory
SD	Customers as Business Partners, SAP Credit Management in place of SD credit management, and settlement management (condition contracts) in place of SD rebates
All modules	Fiori apps alongside SAP GUI, and whether their project was a conversion or a new implementation

Questions to ask, by module

Three questions per module, with what a strong answer covers. Ask for a real example every time.

FI/CO

"Walk me through period-end close in the last S/4HANA system you supported. What ran in which order, and what went wrong?" A strong answer gives a specific sequence (depreciation, accruals, settlements, allocations, foreign currency revaluation), their own part in it, and one problem they fixed.
"How did the Universal Journal change the way you reconcile FI and CO?" A strong answer: one journal instead of separate ledgers to reconcile, and what that changed for reporting.
"Tell me about a configuration you owned from requirement to go-live." A strong answer names the objects (account determination, cost center hierarchy, asset classes), how it was tested and who signed it off.

MM

"Describe procure-to-pay in a system you configured. Where did invoice problems come from?" A strong answer covers requisition, purchase order, goods receipt and invoice, the three-way match, tolerances and GR/IR clearing.
"How is account determination for inventory postings set up, and how have you traced a wrong posting?" A strong answer: valuation class, movement type and transaction keys, with an example they debugged.
"What changed for supplier data when you moved to Business Partner?" A strong answer covers BP roles, customer-vendor integration and what they learned migrating the data.

SD

"Walk me through order to cash, including where pricing and credit checks happen." A strong answer covers sales order, delivery, billing and the posting to finance; the pricing procedure; and where credit management steps in.
"Tell me about a pricing procedure you designed for a complex customer agreement." A strong answer: condition types, access sequences, requirements, and how they tested the edge cases.
"What replaced SD rebates in S/4HANA, and have you worked with it?" A strong answer: settlement management and condition contracts, or an honest "not yet" and what they'd need to learn.

What our recruiters see when screening

Our recruiters see these patterns again and again. Here's what each one can hide and what we ask to find out.

"S/4HANA" on every project

When a résumé lists S/4HANA everywhere, we ask which projects were conversions, which were new implementations and which were support after go-live, then what changed in their module. If every answer sounds like ECC, S/4HANA was the system around them, not work they configured.

A support specialist applying for a project role

Long-time support consultants often know the business better than anyone. We ask whether they've written a design, run a mock data load or worked a cutover weekend. If not, they may fit hypercare better than design.

The all-module résumé

When FI, CO, MM, SD, PP and WM are all listed at expert level, we ask the candidate to pick the one they'd defend at a whiteboard and go deep there. Real breadth exists, and we've placed it, but it shows up as depth in each area, not a longer list.

The integration gap

A capable SD consultant who can't explain how a billing document posts to finance is a risk on order to cash. We ask them to walk through revenue account determination, because many order-to-cash problems sit at the seam between SD and FI.

Certified, not configured

A recent S/4HANA certification and one project as a "functional analyst". We ask what they personally configured and how they tested it. A certificate shows study; our clients are hiring for what someone has done in a system.

Public cloud to private cloud, or the reverse

S/4HANA public cloud work is mostly fit-to-standard, with less room to configure. We ask how much they configured versus adopted as standard, and whether that matches what the program needs.

Red flags

Every module and every release listed at the same level, with depth in none
Can't say what changed in S/4HANA for their own module
Projects described only as "supported" or "part of the team", with nothing they owned
Can't explain how their module posts to finance or hands off to the next module
A certificate offered as the main evidence of hands-on work
Vague about the release, deployment type or project phase they worked in

Not a red flag on its own: only support experience, or only new implementations. That's a question of fit with your project's phase.

A one-page scorecard

Score each line from 1 to 4 during or right after the interview: 1 means no evidence, 2 some, 3 solid with examples, 4 has led it.

Criterion	What a 4 looks like
Module depth	Configured and owned the core processes of your module, with examples
S/4HANA fit	Explains what changed for the module and has done the work on your release and deployment type
Hands-on configuration	Names the objects they set up and how they tested them
Integration	Explains postings and hand-offs to finance and neighboring modules
Project phase	Has worked the phase you're hiring for: design, build and test, cutover or support
Business communication	Explains a process change clearly to someone who doesn't use SAP
Work model fit	Location, hours and contract terms match the role

When you need a technical specialist instead

Some gaps aren't functional at all. If the problem looks like one of these, a functional consultant won't close it.

If the problem is	Bring in
Custom reports, enhancements or forms	ABAP developer
Fiori apps that need building or fixing	Fiori/UI5 developer
Performance, transports, upgrades or system copies	Basis administrator
Interfaces with other systems	Integration developer (PO/PI or BTP Integration Suite)
Roles, authorizations and access reviews	Security and GRC analyst
Data models and analytics	HANA data modeler or BW specialist

See the roles we staff on SAP staffing.

Recent SAP work

One consultant, five disciplines (2026).

A global wellness brand moving from SAP PO to BTP Cloud Integration, with a new WMS rollout of about 30 interfaces running in parallel, needed Basis, ABAP, functional, BTP administration and integration development. One senior consultant covered all five instead of a five-person team.

A greenfield S/4HANA team in a validated environment.

A global biopharmaceutical company needed a project manager, security analyst, Basis administrator, HANA data modeler and S/4HANA Finance consultant for a greenfield implementation under GxP rules. We delivered all five in 12 days, with 100% retention through the implementation.

Before you open the role: a checklist

The module, and the sub-areas that matter (for example asset accounting or period-end close)
Release and deployment: ECC, or S/4HANA on-premise, private cloud or public cloud
Project phase: design, build and test, cutover, or support
The integration points the person must know
Contract, contract-to-hire or full-time
Location and work model
Who interviews, and who fills in the scorecard

Questions hiring managers ask

What's the difference between an SAP functional and technical consultant?

A functional consultant configures the module and works with the business on processes. A technical consultant writes code, runs the system or builds interfaces. Most projects need both.

Does an SAP FI/CO consultant need S/4HANA experience?

If you run S/4HANA or are moving to it, yes for configuration work. Finance changed the most, with the Universal Journal, Business Partner and new asset accounting. A strong ECC consultant can learn it, but plan for ramp-up time.

Can one consultant cover FI/CO and MM or SD?

Some can, especially on integration work. Depth in the module you're hiring for matters more, so test the integration points directly.

Share the role and we'll help you scope it.

Tell us the module, release and phase. We'll tell you what to screen for and send submittals within 48 hours of a clear requirement.

Book a hiring call Share your requirements