| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 2881 |
| Technical Name |
l10n_za_sars_einvoice |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 2881 |
| Technical Name |
l10n_za_sars_einvoice |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
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 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.
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.
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.
Real VAT validation
A 10-digit SARS VAT-number validator (leading 4, Luhn check digit) and income tax reference validator run on the company and partners, stopping data-entry errors before the document is sent.
Clearance reference + QR
After clearance the hub reference, document SHA-256 hash and a verification-URL QR are captured and rendered to a PNG for the printed invoice — 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.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module