How ERPNext helps with South Africa VAT and the VAT audit report
If you run a South African company on ERPNext and need VAT figures for your own review or for an auditor, the starting point is ERPNext's South Africa regional section, which provides a VAT Audit Report. That report is only as good as the data behind it, and its output depends on correct tax templates and the accounts they post to. Before you trust any total, confirm that the sales and purchase tax templates carry the right rates and that every tax account is mapped to the correct line of the report. A wrong template or a missing account will produce a clean-looking report with wrong numbers.
Set these up with your finance and tax advisers before go-live, not at the end of a period. Decide which accounts hold output VAT, input VAT and any adjustments, confirm how zero-rated and exempt supplies are coded on items and customers, and test the report against a small set of known invoices and credit notes. Check the regional documentation for the exact settings and fields it expects in your ERPNext version, since the regional code changes between releases. Your own team should own the configuration and keep a record of what was set and why.
ERPNext does not file returns with the South African Revenue Service, and it does not issue audit opinions or certify that your VAT position is compliant. The report helps you prepare and reconcile figures, but the filing, the sign-off and the assurance remain with your tax practitioner, your management and your independent auditor. DeployOpen can plan, configure and document the setup and prepare the evidence your auditor will ask for, but it does not provide tax advice or attestations. Confirm the detailed filing requirements with SARS and your advisers.
Which VAT requirements map to which ERPNext settings
This table maps each VAT requirement for a South African company to the ERPNext capability that supports it, the configuration it needs and the person who should own it. Read each row as a checklist to confirm with your tax adviser, since rates and treatment decisions remain with the business and SARS guidance.
| Requirement | ERPNext capability and configuration | Owner in the company |
|---|---|---|
| South Africa regional localization | Enable the South Africa regional section on the company and confirm the version-16 regional code is present in your ERPNext release before go-live | ERP lead with the finance controller |
| VAT Audit Report | Run the VAT Audit Report from the South Africa section for the filing period, then test it against a sample of invoices and purchase documents | Finance controller |
| Output VAT on sales | Sales tax templates linked to item tax templates, with the VAT rate and output VAT account set for each treatment you use | Tax adviser defines treatments; finance configures |
| Input VAT on purchases | Purchase tax templates with the input VAT account, applied to supplier invoices where input tax is claimable | Accounts payable lead with tax adviser |
| Tax accounts in the chart of accounts | Separate VAT payable and VAT receivable accounts created under the company, mapped in the tax templates so balances reconcile to the VAT return | Financial controller |
| Zero-rated, exempt and non-VAT items | Item tax templates per treatment, so each item carries the correct category and the audit report groups it correctly | Product or master data owner with tax adviser |
| Company and customer tax details | VAT registration number and address on the company and customer records, shown on invoices and used in the audit report | Master data owner |
| Access to tax settings | Restrict edits to tax templates and accounts to named roles, and log changes to rates, since these affect every later invoice | Security or ERP administrator with finance |
What the South Africa localization changes in ERPNext
The South Africa localization is regional code that sits alongside the core ERPNext accounting, not a separate product. ERPNext's South Africa section documents the regional features, including the VAT Audit Report, and the version-16 branch of the ERPNext repository carries the South Africa localization within its regional code folder. Before you plan around it, confirm which ERPNext major version your environment runs and whether that version is still supported. Support status depends on the version in use, so check the supported versions page as the reference rather than assuming the latest branch matches your production system.
The regional features do not produce VAT on their own. They read the tax setup you define. Item tax templates attach a specific tax rate and tax account to an item, while sales and purchase tax templates apply the taxes to invoices and orders. Each tax line posts to a tax account in the chart of accounts, and the VAT Audit Report summarizes what those accounts and transactions hold. If an item carries the wrong template, or a template points at an account that does not match the VAT account structure your accountants use, the report will reflect that error faithfully. Map these links before you rely on any output.
Treat the tax templates and accounts as a design decision with an owner, not a configuration afterthought. Decide which items are standard rated, zero rated or exempt, who approves changes to templates, and how changes are logged. Ask your finance and tax team to sign off the account mapping against a sample of real invoices and purchases before the first filing period. A useful test is to reconcile the report totals to the VAT control account in the general ledger. Confirm the exact report layout and field names with your tax adviser, since the filing requirements are theirs to define and the software only presents the data.
Configuring South Africa VAT in ERPNext step by step
This sequence builds the South African VAT setup in dependency order, so each account and template exists before the items and invoices that use it. It ends with a VAT Audit Report run on test transactions that you check by hand before any live invoice is posted.
Confirm the ERPNext version and tax scope
Confirm that the ERPNext version you will deploy includes the South Africa localization. The version-16 regional code includes it, and the ERPNext South Africa documentation describes the setup. Check Frappe's supported versions page for the support window of your chosen release. Ask your VAT adviser to confirm your registration status, standard-rated, zero-rated and exempt supply types, and any imports or exports you make. Your adviser should approve each treatment in writing before you configure it. This step is done when you hold a written list of treatments and the version you will install.
Enable the South Africa localization on the company
On the Company record, set the country and the regional settings that switch on the South Africa localization. The exact fields and their location depend on your version, so confirm them against the South Africa section of the documentation in a test site first. Save the company and check that South Africa-specific reports and settings appear in the navigation. Your IT team or implementation partner usually performs this step, and the company owner or finance lead reviews the result. This step is done when the company shows the localization settings and the VAT Audit Report is visible in the reports list.
Create VAT accounts in the chart of accounts
Add the VAT input and output accounts to the chart of accounts, under the account types and parent groups your adviser specifies. Keep output VAT and input VAT separate so the balances can be reconciled to the VAT return later. Name the accounts consistently and set the company and currency on each one. Also confirm any account that will hold VAT on imports or adjustments. Your finance team should review the tree before any transaction is posted. This step is done when every VAT account is listed under the correct company, and a trial balance shows zero balances on the new accounts.
Build sales and purchase tax templates
Create a sales tax template and a purchase tax template for each rate or treatment that your adviser approved. Link each row to the output or input VAT account created in the previous step, and set the rate and the tax description so they appear correctly on invoices. Keep the templates for standard, zero-rated and exempt supplies separate so the VAT Audit Report can classify each transaction. Your finance lead owns the templates, and the adviser reviews the rate and account mapping. This step is done when each template saves without error and its rows point to the intended accounts.
Assign item tax templates to items
For each item or item group, add an item tax template that matches its VAT treatment. Standard-rated goods and services, zero-rated exports and exempt supplies should each use the template your adviser confirmed. Review items that are sold and bought, because they may need both a sales and a purchase treatment. Keep a list of item codes and their assigned templates so the decisions can be audited later. This step is done when every active item has a documented VAT treatment and no item is left on a default that nobody approved.
Test sales and purchase invoices
Create a set of test sales invoices and purchase invoices on a non-production site. Include one example of each treatment, such as a standard-rated sale, a zero-rated export, an exempt supply and a standard-rated purchase. Check that the tax lines, totals and general ledger postings hit the accounts you created. Record the expected result for each test in a table before you post, so the comparison is objective. Illustrative example: a 100 sale at a 15 percent rate should show 15 of output VAT on the correct account only if your adviser confirms that rate applies. This step is done when every test document matches its expected tax and ledger result.
Run the VAT Audit Report on test data
Open the VAT Audit Report from the South Africa section and run it for the test period. Compare each row against your test table, checking that the transactions appear in the expected categories and that the totals agree with the ledger. Investigate any transaction that is missing, duplicated or classed differently than your adviser expects, then correct the template, item or account and rerun the test. Ask your adviser to review the output format against the filing requirements they will apply. This step is done when the report reconciles to the test data and the adviser has signed off on the treatments before live use.
What evidence the VAT Audit Report and ledger give an auditor
An auditor tests the VAT return against the underlying transactions, not against a single report. The cards below list the evidence to keep for South Africa VAT in ERPNext, and each one shows what the report can and cannot prove on its own.
VAT Audit Report output
The VAT Audit Report is the starting point for reconciling output and input VAT for a period in the South Africa regional section. Export it for each filing period and store the file with the period close record, noting the filters used, the company and the date run. Re-run it later and compare results, because a report regenerated after late postings or amendments can differ from the version you submitted. Treat it as a summary that points to source documents, not as the evidence itself.
Underlying invoices and ledger entries
Auditors will sample sales and purchase invoices and trace each one to its General Ledger postings and tax lines. Keep the submitted invoices, any amended or credit note versions, and the ledger entries that carry the VAT amounts. Confirm that cancelled and amended documents remain traceable to their originals, and that frozen periods prevent later changes to closed months. Ask your auditor which sample sizes and date ranges they will select.
Tax template and account configuration history
The VAT figures depend on which item tax templates and tax accounts were in force on each invoice date. Record every change to sales and purchase tax templates, item tax templates and the linked VAT accounts, with the date, the approver and the reason. Keep a dated export of the configuration so you can show the rates and mappings that applied to a past transaction. Without this history, a correct report can still be impossible to defend.
Change records for customizations and scripts
Custom fields, print formats, server scripts or reports that alter how VAT is calculated or displayed are part of the evidence chain. Keep the exported customization files, the version of ERPNext and the South Africa localization in use, and a change ticket for each modification. Note which version was live for each filing period. Server Scripts are disabled by default from version 15, so confirm whether any were enabled and who approved them.
User access and export or print logs
Auditors often ask who could post, change or export VAT data and who actually printed or downloaded it. Keep the role assignments and user permission records for the VAT period, plus access logs that show prints and exports of invoices and reports. Review them for segregation of duties, such as whether the same user prepared and submitted the return. Confirm how long your deployment keeps these logs, since default retention depends on your configuration.
Filed return and correspondence
The submitted VAT return, the payment record and any correspondence with the revenue authority belong in the same evidence set. Link each filing to the report run, the ledger period and the configuration version used. Store copies outside the ERPNext site as well, so the record survives a database restore or a site migration. Confirm your record retention period with your tax adviser before setting any backup or archive schedule.
Loading historical VAT data without breaking the audit trail
Load historical invoices with tax lines only after the tax templates and their accounts exist in ERPNext. The Data Import tool can create and update records from CSV or Excel files using its downloadable templates, and it supports child table rows, so invoice items and tax rows can travel together. The documentation advises importing only a few thousand records at a time, which means a multi-year invoice history is a batched job with a log of each batch, not a single upload. If the tax accounts or item tax templates are missing or named differently, the tax lines will not map to the VAT Audit Report categories, and you will discover the gap only when the report is run.
Before the first VAT period in ERPNext, reconcile totals against the source system: invoice counts, net amounts, VAT amounts per rate and the closing VAT control account balance for each historical period. Keep the source exports, the import files and the reconciliation sheet together as evidence. Confirm with your current accounting vendor how it exports tax detail, including whether VAT is stored per line or only per invoice, whether zero-rated and exempt supplies are separated, and whether credit notes carry their original invoice reference. Those answers decide whether the imported rows can rebuild the same VAT figures your filed returns already show.
Decide early whether historical data goes in as imported records or is kept only in an archive, since the two choices have different audit consequences. Imported invoices become ERPNext documents that later changes, cancellations and amendments will follow, so the migration batches should be loaded into a test site first and checked against the reconciliation. Ask whether your auditors expect the original source reports to remain available alongside the ERPNext figures, and confirm how the ERPNext South Africa documentation describes the regional setup before you map your own tax codes.
Questions buyers ask about ERPNext and South African VAT
Does ERPNext produce the VAT return for SARS?
ERPNext's South Africa regional section provides a VAT Audit Report, which summarizes the VAT transactions your books hold so you can review them against what you plan to declare. It does not submit anything to SARS, and it does not replace the return itself. Your tax adviser should confirm which figures on the VAT201 map to which accounts and tax templates in your setup, and check that the report reconciles to your ledger before anyone files. Read the VAT Audit Report documentation for the fields it covers and how it is generated.
What does a South African VAT setup cost in ERPNext?
Self-hosting ERPNext is free, so the cost is the labor to configure and verify it, plus hosting if you do not run it yourself. The ERPNext pricing page lists Frappe Cloud shared site hosting from 5 US dollars per month, and servers from 20 US dollars per month for shared instances and 125 US dollars per month for dedicated servers. Implementation is available through certified partners, and that work is priced by scope. Cost rises with the number of companies, the volume of historical data, the number of tax templates and items that need separate treatment, and the amount of tax adviser review. Ask any partner for a fixed-scope quote that lists each deliverable, the tax settings covered, and what is excluded.
How long does ERPNext VAT setup take?
The duration depends on what the setup has to cover, not on a standard period. The main drivers are how many companies and tax regimes are involved, how clean the chart of accounts already is, how many item tax treatments need defining (standard-rated, zero-rated, exempt and out of scope), how much historical data is migrated, and how quickly your tax adviser can review each mapping. Testing the VAT Audit Report against known filed periods usually takes longer than the configuration itself. Ask for a timeline in the written scope that ties each phase to a named dependency on your side.
What must our company provide before ERPNext VAT work starts?
Most of the delay in a VAT project comes from inputs the implementation team cannot decide alone. Expect to provide:
- A tax adviser who signs off on VAT treatments, account mappings and the final report layout.
- A chart of accounts that reflects your ledger, including the accounts that carry input and output VAT.
- A list of items and services with their VAT treatment, and evidence for any zero-rated or exempt classification.
- Sample invoices, credit notes and purchase documents from each period you need to test.
- Named people who can approve configuration changes and test results.
Can an internal team set up ERPNext VAT without a partner?
Yes, if the team has ERPNext administration skills and access to a tax adviser for the rules. The configuration itself is documented in the South Africa section and the VAT Audit Report page, so a capable administrator can work through the tax templates, accounts and settings. The risks are in the places that documentation cannot decide for you: which transactions are zero-rated or exempt, how a mixed supply is treated, and whether the report output matches the return you file. Teams that build in-house usually need a review step from a tax adviser and a documented test against past periods. A partner adds value mainly where the scope spans several companies, custom apps or integrations that feed invoices into the ledger.
What should a written scope for ERPNext VAT include?
A written scope should name the ERPNext version and the deployment model, such as Frappe Cloud or self-hosting with Docker Compose or bench. It should list the companies, the South Africa settings to be configured, the tax templates and accounts, and the item treatments to be applied. It should state the reports to be validated, the historical periods used for testing, and the acceptance criteria your tax adviser will sign. Also require the exclusions, such as filing, integrations with payroll or point-of-sale systems, and ongoing maintenance. Finally, ask how changes to the regional code during upgrades will be tested, since ERPNext releases are frequent. DeployOpen provides work under a fixed-scope written agreement, and it prepares the configuration and evidence while your tax adviser and auditors make the compliance judgments.
Which ERPNext versions support the South Africa localization?
The version-16 branch of the regional code includes the South Africa localization, so confirm the exact version your deployment runs before you plan the work. According to Frappe's supported versions page, version 14 reached end of life on January 31, 2026, version 15 is planned to be supported until the end of 2027, and version 16 until the end of 2029. Check the ERPNext regional code for version 16 and the release notes for the version you choose, and ask your partner to confirm which South Africa features exist in that branch before the scope is signed.
How DeployOpen scopes and delivers South African VAT configuration
DeployOpen plans and configures ERPNext for South African VAT inside infrastructure you control, starting from your VAT registration, accounts and reporting needs. Each engagement is agreed as a fixed scope in writing, with the VAT setup, tax templates and VAT Audit Report checks defined before build work begins.
How we scope
- Confirm your VAT registration details, filing periods and the transaction types your business issues and receives.
- Map which sales, purchase and import items need standard, zero-rated or exempt tax treatment in your chart of accounts.
- Agree in writing which ERPNext version, South Africa localization settings and report outputs are included in the fixed scope.
How we build
- Configure the South Africa regional settings, VAT accounts and item and sales tax templates against your agreed mapping.
- Test sample invoices, purchases and adjustments end to end, then reconcile the VAT Audit Report totals to the general ledger.
- Confirm which ERPNext release and Frappe Framework version your site runs, and check the regional code for that branch before go-live.
How we hand over
- Document the VAT account structure, template assignments, item tax rules and the steps used to produce the VAT Audit Report.
- Provide test evidence showing the reconciled figures, the configuration changes made and the open points your team must confirm.
- Walk your finance and tax staff through the monthly filing routine and the controls they must keep in place after handover.
How we support
- Review the VAT setup again when your tax treatment, chart of accounts or ERPNext version changes.
- Offer ongoing support and upgrades as a retainer, scoped separately from the original fixed-scope build.
- Ask your tax adviser or SARS-facing specialist to confirm filing rules and report requirements, since DeployOpen does not issue tax opinions or filing approvals.
