SAP Consultant Job Description Template 2026

Last updated: September 17, 2026

By Jennifer Burdick, Recruiting Manager, KORE1

An SAP consultant job description should name the module, the SAP edition and release you run, how configuration reaches production, how much the seat travels, and the base pay band. Mid-level functional SAP consultants earn about $105,000 to $145,000 in 2026, and senior ones $145,000 to $185,000. Leave the edition out and the posting attracts experts in a system you do not own.

I manage recruiting at KORE1 and have filled ERP seats here for most of my thirteen years with the firm. Of all the ERP postings that cross my desk, SAP ones do the most damage when they are wrong.

The invoice was for $41,800. It came from the integrator in the summer of 2024, and the line that mattered said the work was to rebuild eleven custom field requests “using key user extensibility.”

The client was a medical device subsidiary in Camarillo, California, about 300 people. Its parent company ran SAP S/4HANA in a private cloud. The subsidiary did not. Corporate had put it on S/4HANA Cloud Public Edition, the standardized system SAP hosts and upgrades itself, with the parent’s heavier system on the other end of the intercompany flows. Two-tier ERP. Perfectly sensible.

The job description for their first in-house SAP hire was not written for that system. Someone in corporate IT had pulled the parent’s old sales and distribution posting from the ECC years and changed the location. It asked for eight years of SD configuration in SPRO, functional specs for user exits and custom ABAP enhancements, and “deep knowledge of the IMG.” They hired exactly that person. He was a genuinely strong SD consultant, and he came in at $158,000 base.

He was in the building for design workshops by the second week. By week five he had asked for eleven custom fields and two enhancements that the public edition will not accept in the form he knew. There is no SPRO there to open. Configuration runs through SAP Central Business Configuration and a set of browser apps, and extensions follow much tighter rules. Nobody had warned him. Nobody writing the posting had known it mattered. The integrator rebuilt his requests their way and billed for it, and he left in his ninth month for an ECC conversion project in Oxnard, which was the job he had applied for in the first place.

One sentence would have prevented most of that. “This role supports SAP S/4HANA Cloud Public Edition, configured through Central Business Configuration, with no custom ABAP in the system.”

Most SAP consultant job descriptions I read have the same bones. A module acronym in the title, a request for two or three full-cycle implementations, SPRO, a list of integration points, and “excellent communication skills.” Every item on that list is real work. The list is just old. It describes a job from about 2015, and it says nothing about the system the person would log into on the first morning, how their work gets to production, or whether they will be on a plane every Monday.

The conflict of interest, before going further. KORE1 is paid when an SAP seat fills through our SAP consultant staffing desk, so a posting good enough to fill itself costs us a fee now and then. I would still rather you had it. Companies that fix the posting first and then call us are much easier to help.

The Job Under the Acronyms

An SAP consultant configures, tests, and supports one part of a company’s SAP ERP system, usually a functional module such as FI, CO, MM, SD, PP, or EWM, and turns the way that business actually buys, makes, sells, and closes its books into settings, master data, and approved changes.

That is the functional seat. Most people mean that one. Technical seats write ABAP, build integrations, or keep the Basis layer alive. Those are separate searches with separate pay, which is why SAP ABAP developer staffing and SAP Basis administrator staffing each run as their own desk here, and HR work sits further off again on SuccessFactors. If your req genuinely covers two of these, our SAP consultant hiring guide walks through splitting it into separate searches.

A functional consultant’s week, on a project or in support, usually holds some mix of the following.

• Workshops with the people who run the process. Mostly listening, and the notes decide what gets built.
• Configuration in the development system, unit tested before anyone else touches it
• Functional specifications for the things standard SAP cannot do, written clearly enough that a developer two time zones away builds the right thing
• Test scripts. A great many test scripts.
• Master data, meaning vendors, materials, customers, and pricing conditions, plus the recurring argument about who owns each one
• Close support, which on the finance side is simply the calendar
• Training key users, then answering their questions for longer than anyone budgeted

Seven lines, and not one of them names a system. The rest of this page is about that gap.

SPRO Does Not Exist in the Public Cloud

Three quite different systems all get called SAP, and plenty of consultants who shine on one of them flounder on the next. The posting has to say which one you run. This is where they differ in the ways a candidate notices.

The public edition column is the one that breaks old postings. SAP’s course on configuring the public edition with Central Business Configuration puts scope, country localizations, the organizational structure, and configuration values all in that one tool. A consultant who has spent a decade in the IMG will recognize every concept and almost none of the screens. Some of them never make peace with how little can be bent. Others find it a relief. You want to know which one you are talking to before the offer, and not in week five.

The upgrade rhythm changes the job as well. SAP’s FAQ on upgrading the public edition describes a major upgrade every February and August that lands on the test system first, with two to four weeks of regression testing before production follows. Somebody on your side runs that regression test twice a year, every year. SAP does not run it. If it is this person, it belongs in the responsibilities.

ECC shops have the opposite problem, which is a calendar with an end on it. SAP’s maintenance strategy gives Business Suite 7 core applications mainstream maintenance until the end of 2027, then optional extended maintenance to the end of 2030 for two extra percentage points on the maintenance basis. For the largest and slowest customers there is one more door. It is narrow. The SAP ERP, private edition, transition option covers 2031 through 2033, goes on sale in 2028, and only applies to systems already moved to SAP ERP, private edition before the end of 2030. If your company has picked one of those dates, write it down in the posting. An ECC support seat that ends in 2027 and one that runs to 2033 are two different jobs. Candidates know that.

On-premise S/4HANA and the private edition sit in between. Starting with S/4HANA 2023, SAP moved those releases to a two-year cycle with seven years of mainstream maintenance each, so name the release. “S/4HANA 2023, upgrading to 2025 next year” tells a consultant far more than “S/4HANA experience required.” The names keep changing too. Newer SAP material calls the two cloud editions SAP Cloud ERP and SAP Cloud ERP Private, and candidates use both the old names and the new ones, so I put the familiar name in the title and the newer one somewhere in the body.

Where the edition decision is still open, say so honestly rather than listing all three. Conversion programs have their own staffing shape, covered on the S/4HANA consultant staffing page and in the S/4HANA hiring guide, and if the ERP itself is undecided, the NetSuite and SAP talent comparison looks at what each choice does to the people you will be recruiting from.

How a Change Reaches Production

Every SAP shop worth working in has a rule about how a configuration change travels. Good candidates want to know yours. Most postings leave it out.

The classic pattern is three systems. Development, where the consultant configures. Quality, where somebody else tests. Production, where nobody configures anything at all. Changes move between them as transports, and something decides who approves each move. In a lot of companies that something is SAP Solution Manager and its change request management, which everyone calls ChaRM, and Solution Manager is on a clock of its own. SAP states that mainstream maintenance for Solution Manager 7.2 runs until the end of 2027 and recommends that every customer move to SAP Cloud ALM before then. Customers who buy extended maintenance for Business Suite 7 keep a narrower set of Solution Manager functions to 2030 at no extra cost, and change control management is one of them.

A 2026 posting can say that plainly. “Changes move through ChaRM today, and this role helps take us to Cloud ALM next year.” That is a real project with a real end date, the kind that shows somebody at your company is paying attention. Strong candidates notice that.

Controls are the other half, and a publicly traded auto parts supplier near Toledo, Ohio, learned that in its 2024 audit. A materials management contractor from its 2023 cutover still held a production role that let him change configuration directly. It had been granted during hypercare and never pulled back. He used it twice. Both times he fixed something small and real. The fixes were good. The external auditors did not care. It became a finding, and the controller’s team spent most of a quarter pulling evidence for every production change made that year, something close to 200 hours that no one had planned for.

Their next SAP posting carried one sentence about it. “This role has no configuration access in production, and emergency changes use logged firefighter access that internal audit reviews.” Candidates from public companies read that line and relax, because they have worked under exactly that rule and most of them prefer it.

The public edition has its own version of the same thing. SAP’s upgrade FAQ describes transports moving from development to test to production, and during the weeks when the test system has already taken the new release, some key user extensibility transports into test can be blocked. If your consultant builds extensions, that wrinkle is part of their February and their August.

Monday Flights, Cutover Weekends, and Two Upgrade Windows

SAP consulting has a travel habit older than most of the people doing the work. Integrators still put project teams on site Monday through Thursday in a lot of industries, and plenty of client-side SAP seats inherit a piece of that rhythm during an implementation before settling down. Hybrid means nothing on its own. The word covers everything from one day a month to five straight weeks, so the posting has to be specific.

I lost a finalist to this once. A manufacturer with a plant outside Spartanburg, South Carolina, advertised a remote SAP FICO consultant seat. It was remote, eventually. The first two months of the job were the Explore phase of its S/4HANA program, and the integrator ran every fit-to-standard workshop at the plant, which meant five of those eight weeks in a hotel off I-85. He found that out on his ninth day, from the project calendar. He had two children under four and a spouse who worked nights. He resigned the next day. The search started over with six weeks gone from a program that had none spare.

The fix is simple.

• Travel by phase, written as a number, such as “on site in [city] for about 60 percent of the first [N] weeks, then one week a quarter”
• The go-live date. Even a date that might slip.
• How long hypercare is expected to run, and whether this person is on the weekend cutover
• Close freezes at quarter-end and year-end, and peak season if you sell or ship anything seasonal
• On the public edition, the February and August upgrade weeks, since regression testing falls on whoever owns the process

When the seat really is fully remote, say that, and say it stays remote after go-live. That sentence by itself pulls good people away from integrator roles that have them flying out every Monday.

SAP Certificates Now Have a One-Year Shelf Life

Plenty of SAP postings still say “SAP certification required.” That phrase changed meaning recently.

According to SAP Learning, SAP certifications are now valid for one year, and holders keep them active by completing a short stay-certified assessment every year, which needs an active SAP Learning Hub subscription. Certifications issued before April 2024 expired on March 31, 2025. So a consultant who earned a module certification in 2019, then moved to an employer that never paid for Learning Hub, may not hold it anymore. Their skills did not lapse. The certificate tells you almost nothing about how well they configure pricing.

I would make the certification line preferred and write it so a real expert can meet it. “Current SAP certification in [module], or [N] years configuring [module] on [edition].” Then ask about it. A candidate whose certification lapsed will usually tell you why without much prompting, and the reason is almost always dull, like a subscription the last employer stopped paying for.

The Federal Code Pays Less Than SAP Work Does

There is no federal occupation code for SAP consultants. The nearest one is computer systems analysts. It is an enormous bucket. The May 2025 OEWS figures from the Bureau of Labor Statistics count 519,530 jobs in it nationally, with pay running from $67,340 at the 10th percentile to $167,710 at the 90th. An experienced S/4HANA finance lead sits near the top of that spread or past it. Price a posting off the middle and it loses exactly the people it was written for.

Build the band from the seat instead. These are the 2026 base and contract ranges from our SAP consultant salary guide.

Two things move a real offer inside those ranges more than anything else I see. A completed S/4HANA go-live in your module pushes toward the top. So does public edition experience at the moment, for the plain reason that fewer people have it. Scarcity pays well. The S/4HANA consultant salary guide breaks out the conversion premium, and you can run a particular module, level, and metro through the free salary benchmark assistant.

Then publish the band. A growing number of states require a range on the posting anyway. SAP people also talk, mostly with former teammates from past programs, so an unposted number gets guessed at in a group chat within a week, and the guess is rarely kind to you.

SAP Consultant Job Description Template

Each bracketed item below is a decision. Most of them are facts only your team has. Brackets that start with “Note” are addressed to you, not to candidates, so strip them out once the facts are in. A bracket nobody can fill after a week of asking usually means the program has not decided something yet, which is worth learning now instead of in the second interview.

Job Title

[SAP S/4HANA FI/CO Consultant / SAP SD Consultant, S/4HANA Cloud Public Edition / SAP MM Functional Analyst, ECC to S/4HANA / Senior SAP PP and QM Consultant] [Note: Module and edition both belong in the title. A public edition consultant skims past a title that could mean ECC, and an ECC veteran does the reverse.]

About the Role

[Company] needs an SAP [module] consultant to [support / implement / convert to] [SAP ECC 6.0, EHP [x] / S/4HANA [release] on premise / S/4HANA Cloud Private Edition, release [x] / S/4HANA Cloud Public Edition] for our [industry] business, based [in city, state / hybrid in city / remote within the United States]. [Describe the program: a brownfield conversion going live in [month, year] / a greenfield public edition build for our [subsidiary] / steady-state support for [number] company codes and [number] plants.] We work with [integrator] on [scope], and this role [leads our side of design decisions / owns the system after hypercare / does both]. You will report to [title].

Responsibilities

• Configure [module] in [SPRO in our development system / Central Business Configuration and its configuration apps], and unit test it before it moves
• Run [design workshops / fit-to-standard sessions] with [plant finance / customer service / procurement], and record what was decided and why
• Write functional specifications for [enhancements / integrations / output forms / reports], then test what comes back
• Move changes through [ChaRM / SAP Cloud ALM / our transport approval process] under our [SOX / internal] change controls
• [Run regression testing for the February and August public edition upgrades]
• Support [month-end close / order-to-cash / MRP runs], including first-line triage when something breaks
• Train key users and keep the documentation they actually open up to date

Experience We Are Looking For

• [N] years configuring SAP [module] on [edition], including [the sub-processes that matter most: intercompany, pricing, batch management, product costing]
• At least one go-live on [S/4HANA / the public edition / ECC] in a hands-on configuration role [Note: Ask which phases they worked. Joining a project in Realize is real experience. It is different experience from Explore.]
• Working knowledge of where [module] meets [FI / MM / SD / a third-party system such as Salesforce or a warehouse management system]
• Current SAP certification in [module], or equivalent configuration experience [Note: SAP certifications now last one year. Do not lose a strong consultant over a lapsed subscription.]

Helpful but Not Required

• [The module next door to yours]
• Moving change control from Solution Manager to SAP Cloud ALM
• [Industry] processes such as [lot traceability / make-to-order / customer rebates]
• Enough ABAP to follow a debug session [Note: Reading only. A seat that writes ABAP is a technical search.]

Systems, Controls, and Calendar

[We run [number] company codes and [number] plants on [edition and release]. Changes move from development to quality to production through [tool] and are approved by [role]. This role has [no / display-only] access in production, and emergency changes use [logged firefighter access / your process]. Go-live is planned for [month, year], with hypercare through [month]. Changes freeze during [quarter-end close / peak season].] [Note: Most SAP postings skip this paragraph entirely, which is exactly why a complete one gets noticed.]

Travel

[On site in [city] about [percent] of the time during [phase], then [frequency] after go-live / Fully remote, including after go-live.]

Compensation

[$105,000 to $145,000 / $145,000 to $185,000] base, plus [bonus], [benefits], and [paid SAP Learning Hub access / certification support]. [Note: Include the range. Technical and architect seats price higher, and the table above shows by roughly how much.]

When Finance and IT Both Edit the Draft

We are staying on ECC until at least 2030. Does S/4HANA belong in the posting at all?

Only if this person will work on the move, and then the posting should say when that work starts, because ECC support seats and conversion seats attract different consultants.

A company on extended maintenance still needs strong ECC people, and some of the best of them are tired of being quizzed about S/4HANA in every interview. Tell them honestly. “Supporting ECC through 2029, with a conversion expected to begin in 2028” is a sentence both kinds of candidate can decide on.

Does a functional SAP consultant need to know ABAP?

No, though being able to read it helps a great deal, since a functional consultant who can follow a debugger through a pricing routine solves problems without waiting on a developer.

Writing ABAP is a technical seat. Some postings genuinely need both skills, and they should say so. That person costs more.

The integrator is already staffing the build. What does our own SAP hire actually do?

Your hire owns the design decisions and the system itself once the integrator’s statement of work ends, so this is the person arguing for your business in design sessions and taking the calls in hypercare.

Integrators are paid to finish, and that is fair. Finishing is not the same as living with the result. A client-side consultant sits in every workshop, reads every design document, and pushes back when the standard answer does not fit how your plant actually runs. Some teams bring this person in as a contract SAP consultant for the build and hire a permanent owner partway through. Others make it a direct hire from day one and let that person help choose the contractors. Both work. The posting just has to say which one this is, and whether the seat outlasts hypercare.

Is “two full-cycle implementations” a fair requirement?

Asking for two full cycles is fair for a lead and unfair for almost everyone else, since most consultants join projects partway through and support roles never see a full cycle at all.

Name the phases you need instead. A consultant who has only ever joined in Realize and Deploy may be excellent at build and cutover and uneasy running a room full of plant managers, which matters a lot if your program is still in Explore and not much if go-live is five months away. Our SAP consultant interview questions include a few that separate those two people quickly.

Should the posting name our integrator?

Name the integrator if the partnership is public, because experienced SAP consultants know the firms and read the name as information about how the program will be run.

Some partnerships are confidential. Describe those instead. “A global systems integrator leads the build, and this role leads our side” is enough. Leaving it out entirely makes candidates assume the worst version, which is usually that they will be the only SAP person in the building with a go-live in six weeks.

How long does an SAP consultant search take once the posting is fixed?

Four to eight weeks is typical for a well-scoped functional seat, while senior finance leads and public edition roles run longer because fewer people have done that exact work.

Some searches run past that. The cause is rarely a shortage. It is usually one of the things on this page surfacing late, most often travel, an unclear edition, or a band set below where the market has moved. Our SAP recruiters see those three far more than anything else.

Write the Edition Into the First Line

The Camarillo team rewrote its posting in an afternoon. The second hire had come off a public edition project at a food company, and the first question she asked in her interview was which week in February the test system would upgrade. Nobody had to check. It was in the posting.

The edition goes first for a reason. It decides the rest. It fixes where configuration happens and what custom code is even possible. It sets whose calendar the upgrades run on, which dates your maintenance contract cares about, and which half of the SAP market will read past the title. A posting can get the module right and the pay right and still be describing a system nobody at your company logs into.

When a posting like this is ready, or when one has been live for a month and produced nothing, talk with our ERP recruiting team. We fill SAP seats as contract engagements, contract-to-hire, or permanent hires, and a year past the start date 92% of our placements have stayed put. SAP postings are one of the places that figure gets decided, long before anyone signs an offer.