Why ERP readiness will define your e-invoicing success

In our previous e-invoicing article, E-invoicing and SARS: a shift to real-time compliance we unpacked how SARS is moving towards real-time, transaction-level compliance and what that means for the way businesses report and manage VAT. The next question is more practical: what does it take to operate in that environment, and how prepared are your systems, your data and your processes for what is coming?

As South African Revenue Service moves towards e-invoicing, one thing is becoming clear: this is not something businesses can manage manually.

Real-time compliance requires systems that can generate, validate and transmit data seamlessly. That places ERP at the centre of the conversation.

“In the e-invoicing world, your ERP is no longer just a system of record,” says epic ERP managing director, Stuart Scanlon. “It becomes your compliance engine.”

From finance tool to compliance engine

Traditionally, ERP systems have been used to record transactions and support reporting. Under e-invoicing, their role expands significantly.

A modern ERP must be able to:

  • Generate structured invoice data in XML or JSON
  • Integrate directly with SARS or an accredited access point
  • Validate transactions before they are issued
  • Maintain a secure, searchable digital audit trail

These capabilities are not optional. Without them, businesses risk rejected invoices, delayed processes and compliance failures.

“Trying to bolt e-invoicing onto manual processes is not sustainable,” says Stuart. “It needs to be built into your core system.”

The importance of data governance

Technology alone is not enough. The quality of your data becomes a critical factor.

Customer and supplier records must be complete and accurate. VAT numbers, addresses and tax treatments need to be consistent across the business.

If the data is wrong, the invoice will be wrong. And if the invoice is wrong, it will be rejected.

“There is no safety net anymore,” says Stuart. “The system forces you to get it right the first time.”

This has implications beyond finance. Sales, procurement and operations all play a role in maintaining data quality.

How the market is responding

The ERP market in South Africa has already moved into a high-alert phase.

Global vendors and local partners are actively developing solutions aligned to the SARS roadmap:

  • Microsoft Dynamics 365 is enabling electronic document frameworks, supported by local SARS connectors
  • A number of small accounting platforms are currently building real-time VAT visibility and direct integrations
  • Middleware providers such as Pagero and Sovos are acting as access points for businesses with legacy systems

Epicor is taking a global approach, using its Country Specific Functionality and Avalara integration to support real-time validation and reporting. There is also a strong push towards cloud deployments, where regulatory updates can be applied quickly.

“The pace of change from SARS means your system needs to be adaptable,” says Stuart. “Cloud platforms make that possible.”

What you should be asking now

With timelines already in motion, the right questions matter. If you are engaging with your ERP provider, ask:

  • Can our system generate PEPPOL-compliant structured data?
  • Do we have direct integration capability with SARS or a service provider?
  • Is our master data accurate and governed properly?
  • Are we on a platform that can adapt to regulatory changes quickly?

If the answers are unclear, that is your starting point.

Preparing for what is coming

E-invoicing is not just a compliance project. It is an operational shift that affects how the business runs. The organisations that prepare early will be in a far stronger position, not only to comply, but to operate more efficiently.

“The biggest risk is doing nothing,” Stuart concludes. “By the time this becomes mandatory, the gap between prepared and unprepared businesses will be very obvious.”

E-invoicing is coming. The systems you have in place today will determine how smoothly you make that transition.

Let us know how far you are in your planning and how we can help to ensure you’re compliant when the time comes.

epic ERP to the rescue!

Implementing an ERP system is never just about choosing a well‑known brand. Whether you are evaluating Epicor, Microsoft, Sage, SAP, Oracle, Infor, IFS, or Acumatica. Success starts well before any software is configured. It starts with a clear understanding of how your organisation operates, where the real pressure points lie, and what you are genuinely trying to improve. From process clarity and scope definition to data, integrations, governance, testing, and change management, lasting value comes from disciplined execution.  Not the software alone.

During 2024, we were approached by a company with a failed ERP implementation.

“The provider in question provided such a bad ERP implementation that the consultancy had no option but to start again, but this time, having chosen a stronger partner” explains Stuart Scanlon, epic ERP MD.

But why did things go wrong? And what was the impact?

Famous examples

Globally, failed ERP implementations have made very public and very expensive headlines. Well-known examples include Hershey’s, which lost millions in unprocessed orders after supply chain and data issues derailed its rollout, and Nike, which reportedly absorbed losses of more than $100 million when an ERP implementation disrupted fulfilment.

Closer to home, SPAR Group has also faced challenges following a “botched SAP implementation”, which has reportedly resulted in significant operational disruption and a R168 million lawsuit, further highlighting the real-world risks of poorly executed ERP projects. You can read more here.

“These stories are rarely about technology alone,” says Stuart. “They point to a familiar set of issues that consistently undermine ERP projects.”

Poor planning sits at the top of the list.

“When objectives are vague, timelines are unrealistic, and scope is not clearly defined, critical activities such as user training, data validation and end-to-end testing are often rushed or skipped altogether,” says Stuart.

Another frequent issue is weak process alignment reinforced by inadequate testing. When end‑to‑end processes are not clearly validated before go‑live, misalignment only becomes visible in production, impacting data quality, stability, and user confidence.

The importance of change management and training is often underestimated as well.

“A good ERP implementation reshapes processes, roles and ways of working,” says Stuart. “Without structured change management, strong leadership commitment and proper user training, adoption falters and systems fail to deliver value.”

Choosing the wrong system or implementation partner can also be costly. A mismatch between business requirements and vendor capability leads to workarounds, underperformance and frustration long after the system goes live.

Unrealistic expectations compound the problem. Oversold benefits and underplayed complexity set projects up for disappointment when the promised outcomes do not materialise as quickly or easily as expected.

Finally, the absence of executive buy-in is often fatal.

“Without visible leadership support, ERP projects struggle to secure the authority, resources and organisational alignment they need to succeed,” says Stuart.

At epic ERP, the sales discovery process itself forms part of the project delivery. Time is spent understanding how the business operates, meeting key stakeholders and identifying potential blind spots before the project formally begins. This ensures that the scope is grounded in operational reality rather than assumption.

“Successful ERP implementations are built long before go‑live,” says Stuart. They are shaped by clear process understanding, realistic expectations, strong governance, and informed decision‑making at every level of the organisation. When these fundamentals are in place, ERP systems become enablers of operational clarity and growth, not sources of disruption.