South Africa SARS e-Invoice
SARS Central Tax Hub readiness for Odoo — EN 16931 / Peppol PINT ZA UBL with BYOK transmission and a verification QR
Get ahead of South Africa's VAT modernisation. The Tax Administration Laws Amendment Act (gazetted 1 April 2026) introduces the enabling framework for a 5-corner, Peppol-based clearance model with the SARS Central Tax Hub as the reporting corner, phasing to a 2028 go-live. This connector produces a standards-compliant e-invoice today and transmits it with your own credentials.
Mandate status: SARS e-invoicing is not yet mandatory — as of 2026 it is at the legislative-framework / pilot / voluntary stage. This is a readiness tool: it prepares the standards-compliant document and gives you BYOK transmission to the pilot or a Peppol access point. It ships no live SARS-certified production endpoint (none is published yet); the endpoints are editable placeholders.
EN 16931 / Peppol PINT ZA UBL
Customer invoices and credit notes are rendered as Peppol BIS Billing 3.0 UBL 2.1 with the South-Africa customization identifier, ZAR / VAT defaults and a SARS Central Tax Hub clearance extension.
Note: OpenPeppol has not yet published an official PINT ZA specification. The CustomizationID used here is a provisional, forward-looking identifier and will be updated to the official value once SARS / OpenPeppol release the finalised PINT ZA jurisdiction spec.
BYOK transmission
Submit directly to the SARS hub pilot endpoint or through an accredited Peppol access point (5-corner). Sandbox and production endpoints are editable; OAuth2 bearer or API-key auth; requests retry with exponential backoff and every call is logged.
Accurate VAT categories
Lines are bucketed into the SARS VAT categories — standard (15%), zero-rated, exempt and out-of-scope — with automatic tax-exemption reasons on non-standard subtotals and credit-note referencing of the original invoice.
VAT structural validation
A 10-digit SARS VAT-number validator (leading 4) and a 10-digit income tax reference check run on the company and partners, catching obvious data-entry errors before the document is sent. SARS publishes no VAT checksum, so only the documented structure is enforced (an optional mod-10 self-check is available for typo screening).
Clearance reference + QR
After clearance the hub reference, document SHA-256 hash and a verification-URL QR are captured and rendered to a PNG, shown in the backend and printed on the customer invoice / credit-note PDF — ready for buyer and auditor verification.
Guided onboarding
A wizard validates the VAT number, stores the BYOK credentials and the connection, and can test the endpoint — leaving the company ready to issue SARS e-invoices. An optional cron drains pending invoices.
Built on the e-Invoice Core Engine
This connector reuses the shared e-Invoice Core Engine for the UBL builder, the EN 16931 validation framework, the BYOK REST transport and the e-Invoicing document model — so the South-Africa logic stays focused and the plumbing is battle-tested. Compatible with Odoo 18 and Odoo 19.
Bring your own keys
Your SARS / access-point access token or API key is stored only on your own database and is transmitted solely to the endpoint you configure. We host nothing and own no account on your behalf.
Screenshots
Customer Invoice Sars State
Sars E Invoice Ubl Document
Sars Central Tax Hub Connect
Update date: 2026-07-02