OUR DISCIPLINES
ERP and Enterprise Systems in South Africa.
ERP is the only technology in most businesses where a bad design decision shows up in the audited accounts. It runs finance, supply chain, manufacturing, procurement and payroll, it touches every part of the operation, and the version of it that most South African businesses are running was configured by people who have since left.
This is how SAP, Oracle, Dynamics and the platforms around them really work here: in businesses where the system is twelve years old, heavily customised, and carrying a vendor deadline that was set somewhere else. The roles, the market, and what it takes to get the hire right, whether you are building the team or building your own career.
A LOOK AT THE MARKET
The ERP and enterprise systems market in South Africa.
ERP hiring in this country runs on a calendar, and the calendar belongs to the software vendors.
SAP ends mainstream maintenance for ECC 6.0 enhancement packages 6 to 8 on 31 December 2027. Extended maintenance runs to the end of 2030 at a surcharge on the maintenance base, and from January 2031 there is customer-specific maintenance, which comes with no new fixes and no legal updates. That last phrase is what actually forces the decision locally. A business can live with an unsupported general ledger for a while. It cannot run payroll through a February tax year end on software that will no longer receive statutory updates, because SARS changes tax tables, PAYE, UIF, SDL and ETI rules every year and the system has to carry them before the first March payslip goes out.
Oracle sits in a different position, and it changes the hiring pattern completely. Premier Support for E-Business Suite 12.2 now runs through at least 2036, extended a year at a time since 2018 under the Continuous Innovation model, alongside PeopleSoft, JD Edwards and Hyperion. Oracle customers move when the business case moves. SAP customers move when the clock runs out. So SAP work in South Africa arrives as programmes with hard dates and heavy contractor content, and Oracle work arrives as modernisation projects that get approved, deferred, and approved again.
Where those estates sit is a very local question. Mining and resources run some of the deepest SAP installations on the continent, built around plant maintenance, procurement and costing that took years to get right. Retail and FMCG run large supply chain and merchandising estates where a bad go-live is visible on the shelf within a day. Banking and insurance tend to run SAP or Oracle for finance and HR while the core product systems sit elsewhere. Manufacturing, agriculture, logistics and utilities carry the plant and asset side. The public sector and the SOEs work to their own rules, and municipalities run to the Municipal Standard Chart of Accounts, which is a genuine specialisation with a small population of people who understand it properly.
Payroll deserves its own paragraph, because it is the part of an enterprise estate that South African businesses most often underestimate. Local payroll carries annual statutory change, bargaining council agreements, multiple employment categories and a reconciliation calendar that does not move. It is also the module where an error is visible to every employee on the same morning. The people who can run it well are scarce, they are expensive relative to their apparent seniority, and they are almost impossible to import, because the knowledge is legislative rather than technical.
Then there is the money side, which shapes more of this market than anyone writes about. Licences, cloud subscriptions and partner rates are priced in dollars and euros while budgets are in rands. South African businesses stretch existing estates longer than their European parent companies do, choose brownfield conversion over greenfield re-implementation more often, and carry custom code they should have retired three upgrades ago. The premium sits with people who can land a conversion inside a budget that was set optimistically, and who can get a business to give up a customisation it has grown attached to.
Supply has not moved to meet the deadline. The senior SAP and Oracle population here is small, older on average than the rest of the technology market, and almost nobody arrives in it straight from university. The route in has always been a finance, supply chain or HR career plus a first implementation, which makes the pipeline slow by design. It is also no longer priced locally. Gulf S/4HANA programmes, European partners and UK systems integrators hire South African consultants remotely or on rotation, and they pay in a currency that wins.
The last thing to factor in is where the capability actually sits. Most ERP experience in this country lives inside implementation partners and the global systems integrators rather than inside the businesses running the systems. Those people have seen a lot of templates and a lot of environments. Far fewer have lived with a system for five years after go-live, which is where you find out what a design decision made in a workshop actually did to the month end. Worth establishing early which side of go-live somebody has spent their career on
THE TITLE
Why 'SAP Consultant' tells you almost nothing.
It is the most overloaded title in South African enterprise technology.
The same two words are used for someone who configures financial accounting, writes ABAP, runs a Basis platform, administers authorisations, manages a data migration, and someone whose entire job is answering support tickets against a system they did not design. Those people share a logo on their CV and very little else.
The first question to ask is which module and layer the person owns. Finance and controlling, materials management and procurement, sales and distribution, production planning, plant maintenance, warehouse management, HR and payroll, or the technical layers underneath: development, integration, platform, security and authorisations. That single question makes an ERP CV readable, and most hiring processes skip it because the title implies it has already been answered.
The second is to understand the difference between somebody who configures a system and someone who designs them.
A configurator can make the system do what the specification says. They know the transactions, the configuration nodes, they can build what they are handed, and there are a lot of them, because that is what most project roles ask for.
A designer decides what the specification should say. They understand the finance or supply chain process well enough to challenge the business when the process it describes is the problem, they know which requirement is a legal obligation and which is a habit, and they can see what a decision made in a workshop will do to month end two years later. That judgement is the expensive part of this discipline and no certification tests it.
The third question to ask is anchored in phase. Greenfield implementation, brownfield conversion, and running an established estate are three different jobs. Someone who has only done template-led greenfield builds has not necessarily converted a twenty-year-old customised estate, and someone who has spent eight years supporting one system may never have designed anything. Ask how many full lifecycles the person has been through and which phase they owned, because in this discipline that is a more useful number than years of experience.
Certifications will not draw the line for you. SAP and Oracle credentials are worth having, and a candidate who has invested in them is usually serious about the work. What they tell you is that somebody has been taught a body of knowledge and passed an exam on it. They do not tell you the person has held a design decision against a business unit that wanted its old process back.
If you are hiring, write the spec around the process the person will own and the decisions they will be trusted to make.
If you are deciding your own next move, be honest about which of those two jobs you have been doing, because it becomes visible within twenty minutes of a technical conversation.
THE ROLES
The roles, and what each one involves.
The roles below are defined by what breaks when it is done badly, and by where in the lifecycle it gets involved.
Product knowledge matters and is worth paying for.
Basis and ERP platform specialist
Keeps the system up, upgraded, patched and performing, and increasingly decides where it runs: on-premise, in a hyperscaler region, or on a vendor-managed subscription. Quiet, unglamorous and the reason a conversion weekend either lands or does not.
Common areas: SAP Basis and HANA administration, system copies and refreshes, upgrade and conversion technical execution, performance tuning, cloud hosting and RISE-style managed environments, backup and disaster recovery.
Change and adoption lead
Gets the business to actually use what was built, which is where most ERP disappointment originates. The role that decides whether a technically successful go-live turns into a productivity dip lasting one month or one year.
Common areas: business readiness assessment, process impact analysis, training design and delivery, super-user networks, communications, post-go-live adoption measurement.
Data migration and cutover specialist
Moves the data, and more importantly decides what does not come across. Most ERP delays are data delays, and this role is consistently under-resourced at the start of programmes and over-staffed in a panic at the end.
Common areas: data profiling and cleansing, SAP Migration Cockpit or LTMC, ETL tooling, master data governance, mock loads and reconciliation, cutover planning.
ERP application support manager
Owns the system after the programme has gone home: the support queue, the release calendar, the small enhancements, the month end that will not close. The role that inherits every decision the project made and has to live inside it.
Common areas: incident and problem management, service levels and support tiering, release and transport management, enhancement backlog prioritisation, vendor and partner management, continuous improvement.
ERP programme manager
Owns scope, sequence, budget, vendor and the go-live decision on an ERP programme specifically, where the constraints are technical, the dependencies are unforgiving and the deadline usually belongs to a software vendor. Related to project and programme management and briefed differently, because a general programme manager without ERP lifecycle experience tends to discover the sequencing rules the expensive way.
Common areas: programme governance, systems integrator management, budget and change control, cutover and hypercare planning, executive and board reporting, benefits tracking.
ERP security and authorisations specialist
Designs who can do what inside a system that can move money, approve purchases and change pay. Undervalued until an auditor arrives, and then suddenly the most important person in the programme.
Common areas: role design and redesign, segregation of duties, SAP GRC or Oracle Risk Management, emergency and firefighter access, audit evidence, periodic access reviews.
ERP test leads
Runs the process that proves the thing works before it touches the business: scenario design, integration testing, user acceptance, regression and the cutover rehearsals. Strong test leads surface design problems, not only defects.
Common areas: test strategy and scripting, integration and end-to-end cycles, UAT coordination with the business, automated regression tooling, defect triage, go-live readiness criteria.
Finance functional consultant
Configures and designs the general ledger, controlling, asset accounting, treasury and the reporting finance signs off. The most process-dependent role in the discipline, because the system has to match how this business actually closes its books.
Common areas: SAP FI/CO and S/4HANA Finance, Oracle Financials or Fusion ERP, Dynamics 365 Finance, chart of accounts and cost object design, month end and close, statutory and group reporting, South African tax configuration.
Integration architect
Decides how the estate talks to itself and sets the patterns everyone else has to build to. In businesses that have grown by acquisition, this is frequently the highest-leverage architecture role and the hardest one to fill locally.
Common areas: integration patterns and reference architecture, event-driven and API-led design, middleware platform selection, data flow and master data ownership mapping, interface rationalisation.
Integration specialist
Builds and owns how the ERP talks to everything else: the banks, the warehouse system, the online store, the third-party payroll provider, the acquisition that is still on its own platform. The workstream most likely to be underestimated at the start of a programme.
Common areas: SAP BTP and Cloud Integration, PI or PO, Oracle Integration Cloud, API design and management, IDocs and interface monitoring, middleware patterns, error handling and reconciliation.
HR and payroll functional consultants
Runs the part of the estate where mistakes are visible to every employee within a day. South African payroll carries annual statutory change, bargaining council rules and a fixed reporting calendar, which makes this the least exportable and most consistently scarce skill set in the discipline.
Common areas: SAP HCM and Payroll, SuccessFactors, Oracle HCM or Workday, time and attendance, South African payroll localisation and statutory reporting, leave and organisational management, interfaces to finance and third-party providers.
Integration specialist
Builds and owns how the ERP talks to everything else: the banks, the warehouse system, the online store, the third-party payroll provider, the acquisition still running on its own platform. The workstream most often underestimated at the start of a programme.
Common areas: SAP BTP and Cloud Integration, PI or PO, Oracle Integration Cloud, API development, IDocs and interface monitoring, error handling and reconciliation, file-based and legacy interfaces.
Supply chain and manufacturing functional consultant
Covers procurement, inventory, sales and distribution, production planning, plant maintenance and warehousing. In mining, manufacturing and retail this is where the real complexity in South African estates has accumulated.
Common areas: SAP MM, SD, PP, PM, QM and EWM, Oracle SCM, Dynamics 365 Supply Chain, S/4HANA supply chain design, third-party logistics and warehouse integration, planning and forecasting configuration.
Technical developer
Builds what the standard system does not do, and increasingly the job is to remove what was built before. In a conversion, the developer who can prove a custom object is no longer needed saves more money than the one who can rewrite it.
Common areas: ABAP and ABAP RAP, Fiori and UI5, BTP extensions and CAP, custom code remediation and simplification analysis, Oracle PL/SQL and OIC, Dynamics X++ and Power Platform.
Other disciplines we recruit in
AI & Machine Learning · Software engineering · DevOps and cloud engineering · Fintech · Project and programme management and more
IF YOU'RE HIRING
You're hiring someone to remove things.
The typical instinct in this discipline is to hire a module list: S/4HANA, FI/CO, ten years, certified, conversion experience. Yes, it will produce a shortlist that is easy to defend and tells you almost nothing, because everybody serious has the same list and none of it says how the person behaves when a business unit wants its old process back and has an executive sponsor.
ERP hires spend a large share of their time persuading people to give something up: a report, a customisation, a workaround, a process that has been in place since 2011 and belongs to someone who is not enjoying the conversation. Configuration may be the method, but getting a design accepted and kept is the job.
Where we have seen ERP hiring go well is when the interview is built around real decisions and real go-lives. Here are some thought starters to add to your list of questions:
- Ask them to explain a business process end to end without naming a transaction code. If the answer stays at the level of the screen, you have your answer.
- Understand what they configured that they would now do differently, and what it cost the business at month end.
- Ask about a custom object or a report they removed, and how they got the business to let it go.
- Learn about a go-live that went badly. What broke, when did they know, and what happened in the first forty eight hours.
- Ask who they had to refuse, and whether the decision held after they left the room.
- Find out what the data looked like when they arrived. The answer tells you whether they were near the real work or near the plan.
The key is to listen for whether the answers contain processes, people and consequences, or only modules and phases. Then look for the two core capabilities that separate the good from the exceptional in this market.
Process depth. The ability to reason about how finance, procurement, manufacturing or payroll actually works, independently of any one system. Candidates with that depth can tell you when a requirement is wrong. Those without it build exactly what they were asked for, which is how businesses end up automating a bad process at considerable expense.
The ability to make a decision that sticks. ERP design is a sequence of tricky decisions that somebody has to own, defend and revisit. A consultant who produces a good design and loses every argument about it has cost you more than one who produces an adequate design and holds it, because in a conversion every reopened decision has a schedule cost attached.
A large share of South African ERP vacancies read as version numbers and module abbreviations, which reliably attracts the population that matches version numbers and module abbreviations.
If the role exists because your ECC estate has a 2027 problem, or because a first attempt at a conversion stalled, or because an acquisition left you running two ERPs and a manual reconciliation, or because your payroll localisation is one legislative change away from breaking, say so. The people you want will read that and recognise a problem they have already solved.
WHY LEVELS MATTER
Understanding seniority.
Seniority in this discipline is measured in full lifecycles and in the phases somebody owned, more reliably than in years. Here is a top line view of what each level looks like in practice, whether you are writing a brief or working out where you sit.
-
A junior associate consultant works inside a design somebody else set: configuring to specification, writing and running test scripts, cleaning data, doing cutover tasks and clearing tickets. Hire at this level for curiosity about the business process rather than familiarity with the system. The good ones want to know why the process works that way, and they are visibly uncomfortable configuring something they cannot explain.
-
A mid-level functional or technical consultant owns a module or a work stream: running their own workshops, documenting the design, resolving defects, handling the integration points into their area. Usually the level at which somebody notices that the system as configured and the process as described are different things, and starts fixing it rather than reporting it.
-
A workstream or team lead carries a set of consultants, a budget line and a delivery date, and is the level at which somebody starts arbitrating between what two parts of the business each want the system to do. Much of the job is sequencing and negotiation, and technical strength on its own stops being enough.
-
A Head of ERP, or programme director owns the estate, the roadmap, the vendor relationship and the money. The technical grounding still has to be real, because a leader who cannot interrogate a systems integrator's estimate is dependent on it. What changes is that the job becomes making a multi-year technology decision legible to a board that is being asked to fund it.
Where the money is, and where it isn't
What influences salary in this discipline is scale, phase and scarcity. Configuring a clean template and converting a heavily customised twenty-year-old estate are different jobs, and the market prices the second one properly because far fewer people have done it.
Four kinds of experience move it most
- Brownfield conversion on a customised estate. Not a template build, and not a lab. A real system with custom code nobody documented, historical data that does not reconcile, and a business that cannot stop trading.
- S/4HANA and Fusion rather than the legacy release. ECC-only and EBS-only rates have flattened. Current-generation design, clean core thinking and cloud deployment experience have pulled away.
- Design phase ownership. Having run the workshops and written the design, rather than having configured against somebody else’s. It is the clearest single divider in this discipline and it shows within two questions.
- Payroll and South African localisation. Scarce, legislatively sensitive, and the one area where a mistake is visible to every employee at once.
Underneath all of that, the fundamentals still carry: understanding the finance or supply chain process independently of the software, being able to read the data, and being able to write a design document that a business person can argue with.
What the package is really worth
Senior ERP packages in South Africa are set by a wider market than the local one, with an important exception. The strongest technical, integration and current-generation functional consultants are visible to employers in Europe, the UK and the Gulf, and many can work for them without relocating, so those roles are benchmarked internationally whether you intend them to be or not.
South African payroll and statutory specialists sit outside that pressure entirely, because the knowledge does not travel, which is why local businesses can underpay that skill set for years before discovering what replacing it costs.
Beyond the number, three things shape what an ERP package is worth.
- The programme. Joining a conversion and joining a support queue are different careers. Access to a real design phase is a genuine part of the offer, and candidates who understand this negotiate for it.
- Where the design authority sits. If the systems integrator holds the design and the client holds the budget, the client-side role is smaller than the title suggests. Ask who signs off the design before accepting either side of that arrangement.
- Cutover, month end and travel. Go-live weekends, hypercare, plant visits and close support carry a load that does not show up in an annual figure. Businesses that price it honestly retain people that businesses treating it as goodwill do not.
THE COST
Contract vs Permanent.
ERP is the most contract-heavy discipline in South African enterprise technology, and for a straightforward reason. The work arrives as programmes with real end dates, set by a vendor rather than by the business, and it needs depth that no business can justify carrying permanently between programmes.
The work that suits contract is clear enough. The conversion itself, data migration and cutover, an integration workstream, a payroll localisation project, hypercare, a rescue after a stalled go-live, or an interim ERP lead while a permanent search runs. Real scope, a definitive deadline, and experience the business needs for eighteen plus months rather than forever. Paying a day rate to somebody who has taken four businesses through the same conversion usually costs less than a permanent hire learning it on yours.
Where we would draw the line is the run team. An ERP programme hands over to the people who will operate the system for the next decade, and their first difficult month end is where you find out what was never explained to them. A support team that can operate a system without understanding why it was built that way turns every question into a change request, and the cost of that arrangement compounds quietly for years.
So keep some things permanent: the process ownership, the run team, and at least one person close enough to the programme to inherit the reasoning rather than only the configuration. Put them inside the design conversations early, while there is still something to learn, rather than at handover when the contractors are already booked onto the next thing.
There is a practical consideration too. ERP contractors need production access to finance, procurement and payroll data, which brings segregation of duties, vetting and access records into the picture. That is a reason to plan contracting properly rather than to avoid it, and it is worth agreeing before anyone starts.
Two Acuity-specific notes that come up constantly in this discipline. If you have already found the contractor yourself, Contractor Payroll Services handles the PAYE, SARS administration and compliant contractor structures without a recruitment engagement, which matters when a programme has fifteen specialists on different arrangements. And where you need a permanent ERP leader and cannot afford to wait, an interim while the search runs is a sound answer, and a better one than appointing quickly at that level.
For the professional, contract in ERP builds lifecycle count faster than any permanent route, because you see how several businesses solved the same problem with different amounts of discipline. What you give up is the years after go-live, where you find out what your design actually did to the people using it.
ERP and solutions architecture salaries in South Africa.
FOR CONTRACTOR ROLES
Seniority
Indicative hourly rate
> Junior or associate ERP consultant
R500 – R600
> Mid-level functional or technical consultant
R600 – R700
> Senior functional or technical consultant
R900 – R1100
> ERP workstream or team lead
R1100 – R1300
> ERP programme lead or interim Head of ERP
R1300 – R1500
FOR PERMANENT ROLES
Seniority
Annual cost to company
> Junior or associate ERP consultant
R750K – R850K
> Mid-level functional or technical consultant
R800K – R1M
> Senior functional or technical consultant
R1.2M – R1.6M
> ERP workstream or team lead
R1.2M – R1.6M
> Head of ERP or ERP programme director
R1.9M – R2.5M
Figures are drawn from Acuity’s own placements across the South African market and are indicative ranges, not quotes. Actual pay and rates vary with specific skills, sector, location and how in-demand a role is at the time. Contractor rates are excluding VAT. Last reviewed: September 2026
IF YOU'RE BUILDING A CAREER
Nobody builds a career on a template they configured
Two consultants can spend four years on the same programme and come out worth very different money, because one of them learned the configuration and the other learned the business. The difference shows up in the first interview where the questions go past the screen and into the process.
So the useful question about a role is what you would be allowed to design. Ask whether you would run your own workshops or receive a specification. Ask who holds the design authority, the client or the partner, and whether you would ever be in that room. Ask which phase you are joining, because a support queue and a conversion teach entirely different things. Ask what happens when the business asks for a customisation, since the answer tells you whether this estate is being simplified or quietly added to.
Three things are worth building deliberately.
Get onto a current-generation programme. ECC and EBS skills still pay today and the curve is flattening while S/4HANA, Fusion, clean core design and cloud deployment pull away. The 2027 date is doing you a favour if you use it.
Go deep in one process area rather than collecting surface familiarity across four. Depth in finance, supply chain, payroll or integration is what the scarce, well paid roles are asking for, and breadth without depth reads as a career of short assignments.
Decide consciously about localisation. South African payroll and statutory knowledge is scarce, well paid and hard to replace locally, and it travels poorly if you later want a role in Dubai or Amsterdam. Both paths are legitimate. Choosing one by accident is what to avoid.
At Acuity we take the time to understand where you are trying to get to, not only what is already on your CV, and we only put you forward for roles that move you that way. You stay in control the whole way through, and we would rather point you at the right role than hurry you into the nearest one.
COMMON QUESTIONS
ERP questions, answered.
FOR BUSINESSES LOOKING TO LEAD, BUILD & SCALE
How do you hire a good SAP consultant?
Ask them to walk you through a business process end to end without naming a screen or a transaction code. Strong consultants talk about how a business closes its books or moves stock, and where the design made that harder than it needed to be. Then ask what they configured that they would now do differently. Anyone who has genuinely owned a design has an answer ready.
What happens if we stay on SAP ECC after 2027?
Extended maintenance carries you to the end of 2030 at a surcharge on the maintenance base, and from 2031 customer-specific maintenance gives you no new fixes and no legal updates, which is what eventually breaks payroll and tax reporting. Most businesses use that window to convert rather than to wait. On hiring, start with the people who can size the problem: an ERP or platform architect to assess the estate and settle the brownfield versus greenfield question, and technical capability to establish how much of your custom development still earns its place. Data migration and integration come next, because those two workstreams are where conversions slip, and functional consultants join once the target design is agreed.
How much does a SAP consultant cost in South Africa?
Contractor rates run from roughly R450 an hour for a junior consultant to R1700 for a programme lead, and permanent packages from R450K to R2.8M cost to company. The full breakdown by seniority is in the salary tables above. What lifts somebody to the top of a band is conversion experience on a heavily customised estate, integration depth, South African payroll and statutory knowledge, and current-generation work rather than the legacy release.
Should ERP sit under IT or finance?
Both arrangements work, but they do fail differently. Under IT the system stays well run while the process design drifts away from what finance actually needs. Under finance the process stays sharp while technical debt quietly accumulates. What matters more than the reporting line is whether there is a named business process owner with the authority to decide, since ERP programmes stall on unowned decisions more often than on technical problems.
How do we keep the knowledge when the programme ends?
Name the permanent people who will run the system before the design phase finishes, and put them in the workshops rather than in a handover session. Ask for decisions to be documented with the reasoning and the options that were rejected, not only the final configuration. Then keep two or three contractors through the first full quarter end rather than releasing everyone at go-live, because the questions that matter only surface when the business tries to close on the new system.
Can we run the conversion with contractors and keep a small permanent team?
Yes, and it is the arrangement most South African businesses land on. Contract the work that has a real end date: migration, cutover, the integration workstream, hypercare. Keep design authority, process ownership and the run team permanent, and make sure those people sit inside the programme rather than waiting for a handover pack. For a enterprise insurer, Acuity assembled a 15-strong contractor team of senior engineers, engineering leads, cloud and DevOps specialists in a short space of time, which is the same staffing pattern a conversion needs.
How long should a senior SAP or Oracle search take?
Longer than an equivalent software engineering search, because the population is smaller and the strongest people are usually mid-programme somewhere. Notice periods at this level run to two and three months, and good candidates weigh the programme as carefully as the package. Building the shortlist is the quick part of this. Getting the right person free is what sets the date.
FOR PROFESSIONALS EXPLORING
Is SAP ECC experience still in demand?
Yes, through the conversion window, and it narrows after it. Demand holds while businesses are still running the old estate, and the rates have flattened while S/4HANA, clean core and cloud deployment experience pull away. The move worth making is onto a conversion programme in whatever role you can get, because that is where the current-generation experience is and it is being staffed right now.
Should I work for an SAP implementation partner or in-house?
A partner gives you volume: more clients, more templates, more full lifecycles in less time, and a CV that builds quickly. In-house gives you the years after go-live, where you find out what your design did to the people using it and build the relationships that get you into the decisions. Most strong ERP careers here contain both, and the order matters less than staying long enough in each to get the benefit.
Which SAP module is most in demand in South Africa?
Finance and supply chain carry the volume, payroll carries the scarcity, and integration sits underneath everything and is the hardest skill set to replace. Choose on the business process you find genuinely interesting, because depth here takes years and it shows in an interview when somebody picked a module for the rate. Whichever you choose, get onto current-generation work rather than the legacy release.
How much does a SAP consultant earn in South Africa?
The seniority bands and ranges are in the salary tables above, for both contract and permanent. What moves your own number inside a band is the phase you have owned rather than the years you have served: full lifecycles completed, whether you designed or configured, conversion experience on a customised estate, and depth in payroll or integration. Contract rates sit higher on paper and carry no benefits, leave or guaranteed continuity, so compare the annualised figure honestly before making the switch.
Can South African SAP consultants work remotely for overseas companies?
Many already do, and Gulf, UK and European programmes hire here remotely or on rotation. They want current-generation and cross-industry experience rather than South African localisation, so what makes you valuable locally is not always what makes you hireable abroad. If your depth is in local payroll and statutory work, that expertise is well paid here and travels poorly, so it is worth deciding whether you are building a South African career or an exportable one before you take the role.