Insights

Integration questions

Will a South African business need an API or a portal for e-Invoicing?

How to choose an integration path for the proposed Digital VAT Model based on transaction volume and existing systems.

API and portal routes for South Africa e-Invoicing readiness

Direct answer

SARS expects different routes for different businesses: larger ERP environments may connect through service providers, while smaller businesses may use accounting packages or provider portals. That does not establish a final API entitlement or a compulsory portal for every taxpayer. Choose a readiness path by transaction volume, data quality and workflow ownership, then revisit it when SARS publishes final requirements.

Source: VAT Modernisation FAQ (South African Revenue Service).

What matters in practice

  • An API is useful when invoices already originate in an ERP or POS.
  • A portal can suit lower volume work but may create duplicate entry.
  • Both routes still need clear correction and audit processes.

When an API is worth evaluating

If hundreds of invoices are created in an ERP, manual re-entry into a portal is a control problem. An integration can carry source IDs, line-level VAT and acknowledgements back to the originating system. Ask who maintains the mapping when SARS changes a specification.

When a portal may be enough

A small business with few invoices and no internal integration team may prefer a provider interface or a compatible accounting package. Check whether it can export transaction status and corrections. A portal that only creates documents but cannot reconcile them may save little work.

The unresolved choice

Current SARS material outlines likely routes, not a final procurement rule. Do not buy a connector solely because it is labelled SARS-ready. Ask for a working data map and a written list of dependencies on future policy decisions.

Choose a starting route

  1. Count monthly invoices and credit notes.
  2. Find the system that owns VAT calculations.
  3. Compare manual correction effort with integration maintenance.

Questions teams ask

Does every business need to build a SARS API?

No such universal requirement is established in the proposal. SARS describes provider, package and portal routes for different business situations.

Can a portal replace the ERP?

A portal may create or exchange documents, but the ERP may still own orders, tax calculations and the ledger. Plan how the two records reconcile.

Sources: VAT Modernisation FAQ. Used for factual background only.

Bring your South African entities, systems, and branch reality.

EazLink can help you see where a future SARS connectivity layer should sit before readiness work becomes a long custom project.