ERP Implementation, South Africa

Why South African ERP projects drift

The causes of drift in South African projects repeat from one company to the next, and few of them are technical.

• Branches adding scope. Each depot or store has its own way of working, and every one asks for its variation to be kept. Without a firm process for changes, the build grows quietly.
• Migration underestimated. Years of debtor and creditor accounts, stock codes and adjustments in the old package need far more cleaning than a one-line estimate allows.
• Integrations owned by nobody. Bank files, payroll journals, point-of-sale and warehouse devices each sit with a different supplier, and nobody checks the whole chain.
• Outages ignored in planning. Testing, training and cutover are scheduled as if power and connectivity were guaranteed.
• Key users stretched. The people who know the processes best are also running the business, and testing gets their leftover time.

None of this calls for a bigger budget. It calls for a person on the buyer's side who chases decisions, questions the data, protects testing time and tells directors plainly where things stand. My ERP implementation service covers this role in general terms.

How I oversee a South African implementer

A good implementer brings platform skills, local tax setup experience and people who can be on your premises. My role is to make sure that capability is directed at what your business actually needs and signed for.

Each week I meet the implementer's project lead to review progress, risks and open decisions, and I send your financial director a brief written summary. Before an area is configured, I walk process owners through the proposed design: how orders flow from branch to warehouse, how imports are costed, how approvals work and which reports management will use. Owners approve in writing; where the design misses something, it is captured as a gap or a formal change.

For tax, I check that VAT codes, item and customer defaults and the treatment of imports follow your accountant's instructions, and that every figure on the VAT report can be traced to transactions. For integrations, I keep a register of each connection, from the bank to the payroll provider, with its owner and test status, and that register becomes part of the go-live criteria.

When the implementer says a request falls outside the contract, I go back to the proposal and the requirement list and give your directors a clear view of the choices. That keeps disputes short and protects a relationship you will rely on long after go-live.

Data migration from Sage, Pastel, Xero and QuickBooks

South African companies most often migrate from a Sage-based package, frequently the Pastel line, or from Xero or QuickBooks, usually with stock and job information in spreadsheets alongside. The data tends to carry years of history that needs sorting before it can be trusted in a new system.

With your finance and warehouse teams, I work through the recurring problem areas:

• customer and supplier accounts with duplicates, closed accounts and missing VAT registration numbers
• stock codes that have drifted over time, with inconsistent descriptions and units
• open invoices, credit notes, unallocated receipts and supplier payments as they stand at cutover
• imported stock still in transit or at the clearing agent, with its costs
• foreign currency balances for customers or suppliers billed in dollars or euros

How much history to carry, and how the old package stays reachable for audit, is settled jointly with your accountant. Trial loads are tested line by line: ledger accounts, debtor and creditor ageing, then stock per item and per site, each confirmed by whoever answers for those numbers. For the general approach see ERP data migration, while migration from legacy software covers common pitfalls.

Cutover around VAT periods, payroll and power

South African cutovers have a few particular risks, and the plan needs an owner and a check for each one.

Timing. Aligning go-live with the start of a VAT period keeps returns cleaner, and companies generally avoid their financial year end, when the old books still need closing for the auditors. Your accountant confirms the approach.

Payroll. Payroll usually stays with a local provider that keeps up with statutory deductions. The cutover confirms that payroll journals land in the right accounts and cost centers in the new ledger from the first run.

Power and connectivity. I plan the final data load and the first trading day with your IT team's view of backup power and connectivity at each site. The checklist includes what happens if a scheduled interruption falls during the load window, how branches capture sales if they lose access on the first day, and how those transactions are entered or synced afterward without duplicates.

Banking and stock. Bank details, debit order or payment files and opening stock counts are confirmed before the go or no-go review.

Each step is timed and rehearsed in the test environment where possible. My ERP go-live support service covers cutover and hypercare in more depth.

UAT, training and hypercare for branch-based businesses

Testing proves little unless it is carried out by the system's future daily users: branch and counter staff, buyers, warehouse teams, debtors and creditors clerks and approvers. My scripts reflect South African operations, such as an import costed through to landed stock, a zero-rated export alongside a local sale, a credit note with its VAT reversal, a payroll journal posted from the provider and a branch sale captured while offline. Issues are logged and classified with the implementer, so real faults are fixed first and training needs go to the trainers. ERP testing and UAT sets out the method.

Sessions are recorded and organized by job role, so staff who miss a session because of an outage or a busy shift can catch up. The engagement runs in English, and where floor staff prefer another language, your key users or the implementer adapt the material.

Hypercare is remote: a brief morning check-in where key users and the implementer review overnight problems, a single issue log and priorities that put invoicing, dispatch and payments first. I remain on the project until your accountant has reviewed the opening month's close and VAT figures produced by the new ledger. Businesses yet to pick a platform can begin with ERP selection work in South Africa, or see the South Africa overview.