Two SAP markets, not one

SAP for Utilities has its own data model and its own vocabulary. A strong SAP FI or SD background is not a substitute for device management or billing schema experience, and screening that treats them as interchangeable produces bad hires.

The reverse is also true. Plenty of SAP roles at a utility, such as general finance, procurement, analytics and platform work, don't need IS-U at all. For those, a wider SAP market is open to you, and utility context is a bonus rather than a requirement. Getting this split right is the biggest single decision in an SAP search, because it decides how large the market is.

SAP for Utilities roles

Billing and invoicing analyst

  • Owns: rate categories, rate types, schemas, operands and the invoicing run, where the utility's revenue logic lives.
  • Signs of real experience: has changed a rate or schema in production and can explain how bills were checked before and after.

Device management analyst

  • Owns: meters, installations, registers and the mapping between physical devices and what billing reads.
  • Signs of real experience: can trace a wrong bill back to a device or installation setup problem.

FI-CA specialist

  • Owns: payments, dunning, installment plans, write-offs and reconciliation to the general ledger.
  • Signs of real experience: has worked a reconciliation break or a dunning change through to resolution.

EDM and energy data specialist

  • Owns: interval and profile data, its validation, and how it reaches billing and settlement.
  • Signs of real experience: understands how interval data volumes and data quality issues show up downstream.

IS-U ABAP developer

  • Owns: enhancements, custom reports, interfaces and the discipline that keeps an extended system upgradeable.
  • Signs of real experience: can name an enhancement they built in a utility module and explain how they kept it maintainable.

S/4HANA Utilities architect or lead

  • Owns: the target design, the path from IS-U on SAP ECC, and the decisions about what to carry forward and what to retire.
  • Signs of real experience: can explain the tradeoffs of a migration decision they were part of, not only the plan on paper.

Core SAP roles at a utility

  • Finance and controlling (FI/CO). General ledger, cost accounting and reporting. Utility experience helps, but strong SAP finance people from other regulated industries can often make the move.
  • Plant maintenance and asset management. Work orders, maintenance plans and asset records for the physical network. Look for people who have worked alongside field and maintenance teams.
  • Procurement and inventory (MM). Materials, warehouses and purchasing, including storm stock and long-lead equipment.
  • BW and analytics. Reporting and data models across billing, finance and operations. Ask which business decisions their reports actually supported.
  • Basis, platform and integration. System administration, upgrades, security roles and interfaces such as PI/PO or CPI. Utilities' uptime and audit needs make change discipline the thing to test.

Definitions for IS-U, S/4HANA Utilities, FI-CA and EDM are in our utility hiring glossary.

IS-U on SAP ECC or S/4HANA Utilities?

The market splits along this line. Some specialists have years of classic IS-U depth. Others have S/4HANA Utilities exposure with less accumulated billing detail. Which one a role needs depends on where your utility is on its own roadmap, so settle that before the search starts.

If you're planning a move, separate the seats the program needs for a phase from the seats that will own the result. Program seats can be filled with contract specialists, which our parent company, Mako Professionals, handles. Owner seats should be permanent and filled before cutover, so those people learn the new design from the people building it. Check SAP's current maintenance timeline for your release when you plan the timing.

Interview questions that test ownership

  1. "Walk me through one billing or rate change you took to production." A strong answer names the schema or rate, what changed, how bills were compared and what went wrong.
  2. "Tell me about a wrong bill you traced to something other than billing." A strong answer follows it into device management, meter reads or account setup.
  3. "How did you handle a reconciliation break between FI-CA and the general ledger?" A strong answer explains the cause, the fix and how they stopped it recurring.
  4. "What's an enhancement you built, and how did it survive the next upgrade?" A strong answer covers the business need, the design choice and the upgrade impact.
  5. "Which parts of your system ran on ECC and which on S/4HANA, and what changed for your day-to-day work?" A strong answer is specific about their own scope, not the program's.
  6. "What did you migrate, and what would you do differently?" A strong answer gets specific about data, balances and history.
  7. "Tell me about a change you had to defend to finance, audit or a regulator." A strong answer shows how they documented and justified it.
  8. For leads: "How did you decide what was in scope for a release or a migration wave?" A strong answer covers priorities, risk and how they said no.

What to put in the job description

  • Your platform today and your plan: IS-U on SAP ECC, S/4HANA Utilities, or both during a transition
  • The modules or processes the hire will own, such as billing, device management, FI-CA, EDM, finance or asset management
  • How much is configuration, development, support or integration
  • Where the program stands: planning, build, cutover, stabilization or steady state
  • Who they hand off to, and who backs them up
  • Location, work arrangement and on-call expectations
  • The compensation range, if you have one
  • Which requirements are essential, and where adjacent experience fits

Where SAP utility people come from

  • Other utilities on SAP. Production history and regulatory habits, sometimes with less exposure to S/4HANA.
  • Implementation partners. Breadth across programs and current S/4HANA experience. Much of the IS-U community has spent years on implementations, so moving one of these people into a permanent seat is its own conversation about stability, growth and what they want next.
  • Adjacent CIS platforms. Billing analysts from Oracle CC&B or another CIS bring business process knowledge that can carry over for functional roles with a team around them.
  • Other regulated industries. For core SAP roles, finance and platform people from industries with heavy audit requirements often adapt well.

Common hiring mistakes

  • Treating general SAP experience as IS-U experience, or requiring IS-U for a role that doesn't need it.
  • Hiring only for today's platform when the team has to carry the next one.
  • Waiting until after cutover to hire the people who will own the system.
  • Writing one role that covers billing, device management and FI-CA, which few people can fill well.
  • Running a permanent search for an implementation consultant the same way you'd fill a contract role.