SAP S/4HANA Consultant Job Description Template 2026

Last updated: October 15, 2026

By Jennifer Burdick, Recruiting Manager, KORE1

An SAP S/4HANA consultant job description should name the S/4HANA objects the seat will own, such as Business Partner, Material Ledger, credit management, or rebate settlement, say how your system got to S/4HANA, and print a closed base range.

For mid-level through senior functional consultants in 2026, that range runs about $110,000 to $195,000 base. What most postings print instead is one line, “5+ years of S/4HANA experience required,” and that line tells a candidate nothing about which parts of S/4HANA they would actually be living in.

S/4HANA reqs have been landing on my desk at KORE1 in a steady stream ever since the 2027 maintenance date started showing up in client budget meetings. The SAP S/4HANA consultant staffing team I work with reads several of these postings a week, and the experience line is almost always the weak spot.

The one I still think about came from a snack-food manufacturer outside York, Pennsylvania, roughly 900 people, in the spring of 2025. They were partway through a brownfield conversion from ECC, the kind where the old system is converted in place and its history comes along. The posting for their in-house sales and distribution lead asked for five years of S/4HANA and two full implementations. They hired a consultant who had both, at $152,000 base. Two S/4HANA go-lives at beverage brands. A strong résumé.

Nobody had looked at what was inside the old system. It held a little over 11,000 rebate agreements with grocery chains and distributors, all built in classic SD rebate processing, which S/4HANA replaces with condition contracts in Settlement Management. At both of his earlier employers, rebates had lived in a separate trade-promotion system, so SD rebate processing was something he had read about and never touched. He had not closed out a single legacy agreement, let alone rebuilt one. The integrator had, and it priced the work at $63,500 as a change order. First-quarter rebate checks to two grocery chains went out three weeks late.

He was a good consultant. He was hired for the wrong half of the project.

What the posting needed was one sentence. “You will retire roughly 11,000 classic SD rebate agreements and rebuild the active ones as condition contracts in Settlement Management before cutover.”

One disclosure, plainly put. KORE1 is paid when a consultant we introduced gets hired, so I am not a neutral party when I say a posting matters. A sharper posting also means some of these searches never reach us at all, and I would still rather you wrote one.

What “S/4HANA Experience” Leaves Out

An SAP S/4HANA consultant configures and supports SAP’s current ERP suite, usually in one functional area such as finance, sourcing and procurement, or order-to-cash, and owns the data objects and processes that S/4HANA changed from ECC, from the Business Partner master to the Universal Journal.

S/4HANA has existed since 2015. Eleven years is long enough for “S/4HANA experience” to cover a dozen very different jobs. A consultant who ran fit-to-standard workshops on a greenfield build, one who spent two years untangling customer and vendor masters before a conversion, and one who has supported a converted system for four years can all claim it honestly. They are not interchangeable, and they do not cost the same.

The difference sits in what SAP calls simplification items. Every functional area that S/4HANA redesigned, removed, or replaced has an entry, with an SAP Note behind it, and conversion work clusters around a handful of them. A posting that names the handful is describing a real job. One that names none is describing a keyword.

The other big decisions live on other pages. Whether you are converting, starting over, or carrying selected data across is the first question in our S/4HANA hiring guide, and the edition, change-control, and travel lines belong to the broader SAP consultant job description template. Once the posting is out, our SAP S/4HANA consultant interview questions hand finalists a printed precheck page to sort. This page is about the objects.

Six Items ECC Consultants Have to Relearn

Each row below is an entry in SAP’s Conversion Guide for SAP S/4HANA 2023, which lists the SAP Note behind each preparatory or follow-on task. The last column is the part of the posting it should change.

Nobody needs all six. A finance seat lives in the second and third rows, an order-to-cash seat in the fourth through sixth, and almost every conversion fights about the first one for longer than planned. Custom pricing routines are usually work for an SAP ABAP developer, so the functional posting should say who writes them rather than quietly assuming the consultant will.

Business Partner is the row I would put in nearly every posting. SAP’s guide lists the Business Partner approach as a preparatory task, which means it happens before the conversion, and in practice the work is mostly business decisions dressed up as data cleanup. Which of the 14,000 vendor records are duplicates. Which customer is really two customers. Whose account number survives. A consultant who has run CVI on a messy system knows those meetings take months. One who has only seen business partners created fresh on a greenfield build does not, through no fault of their own.

The finance rows split the market another way. Plenty of strong FI consultants have configured the Universal Journal on a new build. Far fewer have migrated four years of asset history and reconciled it afterward, which is the actual job on a conversion. If that migration is the seat, write “you will own the migration and reconciliation of [N] company codes of General Ledger and Asset Accounting data,” and our SAP FICO consultant staffing team will tell you the pool for that sentence is smaller than the pool for “S/4HANA FI experience.” It is also the right pool. When the volume is large enough, part of that load belongs to an ERP data migration specialist instead.

The Readiness Check Already Drafted Half the Posting

Most companies planning a conversion already own the document that says which of these rows apply. They just never send it to whoever writes the job description.

SAP Readiness Check analyzes an ECC system and, in the words of SAP’s conversion guide, identifies “the simplification items relevant for your conversion” based on the configuration, data, and usage of the production system. It also reports on custom code, add-ons, and sizing. SAP calls the tool not mandatory but highly recommended, and nearly every integrator I work with runs it in the first weeks of a program.

On the programs I have seen, the summary runs somewhere around 60 to 120 items across finance, logistics, and the cross-application topics, and maybe a dozen of them touch any one seat. Five to eight is the number I would carry into a posting, each one written as a sentence with a count in it, under a heading of its own just below the title.

Greensboro, North Carolina, last year. A home-textiles distributor there, about 400 people, sent me a draft asking for “S/4HANA logistics experience.” I asked for the Readiness Check instead. Their integrator had run it in March, seven months earlier, and nobody in HR had seen it. For the logistics seat it flagged CVI against roughly 21,000 vendor records, FI-AR credit management still active on 31 credit control areas, and warehouse management still running in the old LE-WM component across two buildings. Those three lines went in where the experience sentence had been.

Six weeks later they hired a consultant at $138,000 base who had run CVI twice, once at a paper distributor in Roanoke, Virginia. In her first interview she asked how many of the 21,000 vendors had received a purchase order since 2023. Just over 4,000, it turned out, and most of the rest could be blocked and archived instead of carried into S/4HANA.

A warning about false alarms, though. The Readiness Check reads what exists in the system rather than what the business still does, so an item can show up because somebody configured it in 2009 and walked away. Check with the process owner before it goes in the posting.

Compatibility Packs Ran Out in May

Systems that converted early carry a different problem, and this one comes with a deadline.

When SAP built S/4HANA, it let some classic ECC functions keep running for a while under what it calls compatibility packs, with usage rights for most of them ending on December 31, 2025. On the last day of 2025, SAP announced a final transition period for on-premise customers that moved the expiration to the end of May 2026. That date has passed, and SAP called the extension final.

Classic warehouse management is the example most of my clients run into. A company that converted in 2020 or 2021 and kept LE-WM because it worked is now, in most cases, running a function past its usage rights, and the replacement is SAP Extended Warehouse Management (EWM), usually embedded in the S/4HANA system itself. Which items apply to your license, and which carry later dates, is spelled out in SAP Note 2269324 and its compatibility scope matrix. Your licensing lead or Basis team should check that before the posting goes up.

For hiring, the point is narrower. A seat that exists to move a converted system off its compatibility items is a project with an end, and it attracts a different consultant than a steady run-and-support seat. Say which one it is. “You will lead the replacement of classic WM with embedded EWM across two distribution centers by [quarter]” brings people who have done that cutover. “Support our S/4HANA logistics processes” brings everyone.

Many of those projects are better staffed as a contract SAP engagement with a defined end, plus a permanent hire to own the system afterward. Some are not. The posting should know which.

Close the Range, Because New York Reads the Plus Sign

The 2026 ranges below come straight from our S/4HANA consultant salary guide. I use its numbers as published rather than inventing new ones for this page.

The federal number sits well under these. S/4HANA consultants get no occupation code of their own in federal wage data. The nearest code, computer systems analysts, had a national median of $105,850 in the Bureau of Labor Statistics May 2025 OEWS data, across 519,530 jobs. That is a fair floor for a junior analyst. No consultant who has run CVI on a live system will take it.

Now the plus sign. New York’s pay transparency law, Labor Law Section 194-b, covers employers with four or more employees, and the state’s fact sheet for employers is unusually specific about what a range has to look like. It needs a minimum and a maximum the employer believes in good faith. It cannot be open-ended, and the state’s own example of what is not allowed is “$20+ an hour.” Benefits do not count toward it. A posting that covers several locations or seniority levels needs a separate range for each one.

So the architect row above cannot go into a New York posting as written. “$195,000 to $260,000+” has to become a real ceiling.

The reach is wider than people expect. The fact sheet says remote jobs that report to a supervisor, office, or worksite in New York are covered even when the person works from home in another state. Hauppauge, on Long Island, is where I saw that land. An electronics distributor there posted a remote S/4HANA finance lead seat, “anywhere in the U.S.,” reporting to its controller on Long Island, with “competitive compensation” where the range should have been. A candidate in New Jersey pointed it out during her second interview, politely. The company reposted at $160,000 to $185,000 the same week and hired her at $178,000.

If the seat could be filled at more than one level, post more than one range. Mid-level and senior in a single posting means two ranges in New York. A specific module and metro can be checked against our salary benchmark assistant before you pick the numbers.

SAP S/4HANA Consultant Job Description Template

Copy the template and work through the brackets. Any bracket that begins with “Writer” is guidance for the person drafting, and it gets deleted before the posting is published anywhere. Most of the other brackets can be filled from the Readiness Check summary, the integrator’s statement of work, and the hiring manager’s calendar for the next twelve months.

Job Title

[SAP S/4HANA Finance Consultant, Brownfield Conversion / SAP S/4HANA Order-to-Cash Lead, Settlement Management / SAP S/4HANA Logistics Consultant, Classic WM to Embedded EWM / Senior SAP S/4HANA Consultant, Business Partner and CVI] [Writer: Put the area and the job in the title. “S/4HANA Consultant” by itself attracts every SAP consultant who has heard of S/4HANA.]

Our System and How It Got Here

[Company] runs SAP S/4HANA [release] [on premise / in the private cloud] with [number] company codes and [number] plants in scope. We [are converting from ECC 6.0, EHP [x], with go-live planned for [month, year] / converted from ECC in [year] / built S/4HANA new in [year]]. [Integrator] leads [the build / the technical conversion / nothing at present], and this role [represents our side in design decisions / owns the system once the integrator leaves / does both].

What This Role Owns

• [Business Partner and customer vendor integration for [number] customer and [number] vendor records, currently [not started / under way / complete]]
• [Migration and reconciliation of General Ledger, Asset Accounting, and Material Ledger data for [number] company codes]
• [SAP Credit Management, including [number] credit segments and the credit hold process]
• [Closing out or rebuilding [number] SD rebate agreements as condition contracts in Settlement Management by [date]]
• [Replacing [classic WM / another compatibility item] with [embedded EWM / its successor] by [quarter, year]]

[Writer: Keep only the lines that are real for this seat, and add the other simplification items your Readiness Check flagged in this area. Three to six lines is usually right.]

Day to Day

• Run [fit-to-standard workshops / design sessions] with [finance / customer service / the warehouse] and write down what was decided and why
• Configure and unit test in development, then support integration and user acceptance testing
• Write functional specifications for [enhancements / interfaces / forms] and test what the developers return
• Stay with [the month-end close / order-to-cash / warehouse operations] after go-live and take first-line triage when something breaks
• Teach key users the new screens, and keep their how-to notes current

Background We Are Looking For

• [N] years of hands-on SAP configuration in [area], with at least [one] S/4HANA project where you personally handled [the item that matters most from the list above]
• Hands-on work with [CVI on a system with more than [N] records / finance data migration on a conversion / Settlement Management / embedded EWM]
• [ECC experience in [area], since much of this work is understanding what the old system did] [Writer: Keep this line for conversions and early-converted systems. Drop it for greenfield builds.]
• SAP certification in [area], or equivalent configuration experience

Would Help

• [The neighboring area, such as Material Ledger for a controlling seat or credit management for an order-to-cash seat]
• Experience on a [brownfield / selective data transition] project
• [Industry] processes such as [rebate-heavy distribution / lot-controlled inventory / make-to-order]

Pay, Benefits, and Where You Work

[$[minimum] to $[maximum]] base, [bonus], and [benefits, listed separately]. [Fully remote / hybrid in [city] / on site in [city]], reporting to [title] in [city, state]. [For contract seats, about [N] months, ending at [milestone].] [Writer: In New York, and for remote seats reporting to someone in New York, the range needs a real minimum and maximum with no plus sign, and a separate range for each level or location the posting covers.]

Margin Notes From the Steering Committee

Our integrator ran the Readiness Check. Can we paste the whole list into the posting?

Paste only the five to eight items in this consultant’s area, because a list of a hundred simplification items reads like a system audit and hides the work the person will actually do.

The full report still earns its keep in the interview. Hand the candidate the summary page and ask which items they have personally worked on. You learn more from that than from an hour of résumé questions, and our SAP consultant interview questions add a few that pair well with it.

Is “five years of S/4HANA experience” a fair requirement in 2026?

Five years is reachable, since S/4HANA dates to 2015, but it measures time in the product rather than the work, so a consultant with three years of hands-on CVI and finance migration often fits a conversion better.

Ask for the item instead of the duration. “Has run customer vendor integration on a system with more than 10,000 records” screens harder than any year count.

We converted in 2021. Why would a support posting mention Business Partner?

Converted systems still carry leftovers, such as duplicate business partners, unsynchronized records, and custom code built around the old masters, and the person in a support seat inherits all of it.

One line covers it. “Our customer vendor integration is live, and you will own business partner data quality for [N] records.” Candidates who have lived with a converted system know exactly what that means.

Does one consultant cover finance and the Material Ledger, or is that two seats?

Usually one seat on a mid-sized conversion, provided the posting spells that out, since Material Ledger valuation sits close to controlling and product costing and many senior FICO consultants have done both.

Actual costing is the exception. If it is in scope, it can fill a consultant’s year on its own, and that is worth a separate line or a separate person.

The seat is remote in Pennsylvania, reporting to our office in Albany. Does New York’s law apply?

According to the New York Department of Labor fact sheet, it does, because the law covers remote jobs that report to a supervisor, office, or worksite in New York even when the employee works from home in another state.

Post a closed range and keep a record of it. If the role is open at two levels, post two. Your employment counsel should confirm anything unusual about your setup.

We only need someone to retire classic WM. Permanent or contract?

Contract, in most cases, because replacing a compatibility item finishes on a known date, and the consultants who have done it several times tend to prefer project work.

Pair it with a permanent owner if the warehouse will need ongoing support, which it usually will. Some clients make that hire through direct hire placement partway through the project so the two overlap for a few months.

Put the Item List Above the Experience Line

The York manufacturer rewrote its posting for the second SD seat in about an hour. The rebate sentence went first, ahead of the years and the certifications. The consultant who took the job had closed out legacy rebate agreements at a dairy cooperative, and in her first week she asked for the count of agreements still open past their validity date. Nobody had to explain why it mattered.

That is really all this page argues. The list already exists, in the Readiness Check, in the integrator’s statement of work, and in the hiring manager’s head. Write the items in, and “S/4HANA experience” becomes a question a candidate can actually answer. If you would like another set of eyes on it before posting, share the draft with our ERP search team along with the Readiness Check summary, and we will send back notes written from the seat of a strong candidate. Ninety-two percent of the consultants we place are still working for that client when the first year closes out, and most of those searches started with a posting like this one.