Data questions
How should credit notes and corrections be mapped for future SARS e-Invoicing?
Practical invoice lifecycle mapping for South African ERP teams preparing for structured e-Invoicing and e-Reporting.
Direct answer
Treat a credit note as a linked business event, not as a silent edit to the original invoice. Keep the original invoice reference, tax amounts, reason and approval history together so an ERP can map the relationship into a future structured format. SARS discusses electronic debit and credit notes in its consultation paper, but the final field schema and submission sequence are not yet settled.
Source: VAT Modernisation consultation paper (South African Revenue Service).
What matters in practice
- Never overwrite an issued invoice to hide a correction.
- Preserve the link from credit note to original invoice and order.
- Map cancellations, partial refunds and price changes as different events.
Start with the business reason
A returned item, an overcharge and a cancelled order can all reduce VAT, but they do not have the same operational trail. Capture the reason and approver where the correction is made. The tax integration should receive that context, not try to infer it from a negative amount.
Fields worth preserving now
Keep the original invoice identifier and date, the credit note identifier and date, affected line items, VAT treatment, counterparty and branch. Retain the prior version and any external acknowledgement. These are internal data controls; they are not a claim about the final SARS field list.
- Test full and partial credits.
- Check whether one credit can refer to several invoice lines.
- Reconcile credit totals against the ERP ledger and future reporting extracts.
Where to wait for the standard
The SARS proposal points toward machine-readable documents and e-Reporting. It does not yet provide every mapping rule an ERP vendor needs. Keep the outbound schema configurable and record which assumptions came from consultation material.
Correction mapping test
- Issue a partial credit against a paid invoice.
- Trace the link through ERP, middleware and reporting extract.
- Confirm finance can explain the net VAT result without editing history.
Questions teams ask
Can we just change the original invoice?
That weakens the audit trail. Model a separate, linked correction event and check final SARS rules for its required representation.
Does SARS already publish the final credit-note API?
The consultation discusses electronic credit notes, but it is not a complete production API specification.
Sources: VAT Modernisation consultation paper. Used for factual background only.