South Africa Customs Invoice Data Requirements: SARS Guide

South Africa now expects invoice data to be included in electronic customs declarations, and from 1 April 2025 declarations without invoice data face a higher probability of documentary inspection or audit. The highest-risk fields are goods description, brand or product identifiers, quantity and unit, origin, price paid or payable, valuation-related charges, Incoterms, and payment terms.

That expectation became more urgent when SARS's March 2025 notice on invoice details in customs declarations said on 19 March 2025 that trade should include invoice data in all electronic customs declarations submitted to SARS, and that from 1 April 2025 declarations without invoice data would have a higher probability of documentary inspection or audit. That notice is why teams now need declaration-ready invoice data before filing, not only when Customs later asks for supporting documents.

The requirement is no longer just to keep a commercial invoice on file. The declaration process must capture the invoice details SARS needs to test tariff classification, customs value, quantity, origin, and transaction terms.

What Changed and What Still Applies

The April 2025 declaration-data push did not replace the older SC-CF-30 import invoice policy. It sits on top of it.

SC-CF-30 took effect on 24 February 2022 and remains the baseline for imported goods. It sets out the minimum information customs expects on the commercial invoice used for import clearance. It does not govern exported goods, and it does not function as a VAT tax-invoice rule.

The March 2025 notice moved the operational focus from holding an acceptable invoice to reflecting the right invoice data in the electronic customs declaration. SC-CF-30 remains the foundation, but the 2025 change raised the stakes for how invoice data is captured, transmitted, and matched inside filing workflows.

The 16 March 2026 public-comment draft around SAD 509 and SAD 509.01 is still draft development, not a final rule. It is still useful for planning because it points toward more structured supporting-data requirements around invoice and customs worksheet data alongside the SAD 500 process. Track the SARS draft documents page before treating any SAD 509 requirement as binding.

---

Which Commercial Invoice Fields Matter Most for SARS

For South Africa commercial invoice requirements for customs, the safest approach is to treat the commercial invoice as the core evidence behind the customs declaration. Each field below should either appear clearly on the invoice itself or be immediately extractable and defensible from supporting records if Customs asks for proof. If your team is reviewing shipping terms, it helps to align invoice wording with how Incoterms should appear on a commercial invoice.

Start with the fields that received the most attention in the 2025 declaration push: a specific commercial invoice description, brand or proprietary name where relevant, invoice quantity, Incoterms, and payment terms. If those are vague or missing, even a longer invoice can still be weak at declaration stage.

Invoice field	What SARS needs to understand	What good practice looks like
Document identity	Customs must be able to identify the seller, buyer or consignee, issue date, and invoice reference.	Show legal names, addresses, issue date, and a unique invoice number that can be traced to the declaration file.
Description of goods	This is one of the most important fields because Customs needs enough detail to identify the goods for tariff classification and risk assessment.	Avoid vague labels such as parts, samples, accessories, or machinery. Describe the actual goods, their material, function, model, grade, or use.
Proprietary, trade, or brand name	Brand or trade naming can help distinguish one product from another when classification or valuation is sensitive.	Include the proprietary or trade name and brand name where relevant, especially for consumer goods, chemicals, electronics, machinery, and branded components.
Product codes or identifiers	Short or coded descriptions often do not stand on their own. Customs may need line-item identifiers to understand exactly what was sold.	Include SKU, model, part number, or other product identifiers, especially when descriptions are abbreviated or commercially coded.
Line-item detail	Customs reviews goods line by line, not just at document total level.	Break out each product line separately rather than combining unlike goods into a single summary line.
Invoice quantity	Quantity supports tariff treatment, unit price checks, and reconciliation against packing and transport documents.	State the quantity for each line item and make the unit of measure clear.
Price paid or payable	Customs valuation starts with the actual price paid or payable for the imported goods.	Show the line-item price and total price clearly, with the transaction currency.
Valuation-related charges and adjustments	Discounts, commissions, royalties, freight, insurance, handling, packing, taxes, rebates, assists, or tooling charges can affect customs value.	Separate valuation-sensitive amounts instead of burying them in a net total or unexplained lump sum.
Payment terms	Payment terms help Customs interpret the commercial arrangement and support later valuation or audit questions.	State the agreed payment terms clearly rather than relying on separate email chains or purchase orders.
Incoterms	Incoterms help explain which costs and responsibilities sit with the seller or buyer, which matters for valuation and declaration support.	Show the agreed Incoterm and named place clearly so freight and related charges can be interpreted correctly.

A useful rule of thumb is this: if a data point affects what the goods are, who sold them, how many were sold, what was actually paid, or which costs sit inside or outside the transaction price, it belongs in the declaration-ready invoice data set. Where the invoice itself is brief, teams should make sure the missing detail can still be extracted quickly from contracts, price schedules, freight documents, royalty agreements, or other supporting records without leaving gaps that Customs has to interpret on its own.

For the SAD 500, the invoice fields map to declaration support this way:

• Description of goods: tariff classification and product-level risk review
• Quantity and unit of measure: declaration line support and statistical-unit accuracy
• Country of origin: duty treatment and origin-document support
• Prices, dutiable charges, and Incoterms: customs valuation and the logic behind the declared value

If the invoice uses foreign currency, abbreviated item codes, or apportioned charges, keep the supporting calculation close to the declaration file. For a practical breakdown, see South Africa's foreign-currency invoice exchange-rate rules.

Imports, Exports, and the Common Scope Mistakes Teams Make

One of the biggest compliance mistakes is treating every invoice rule as if it applies across customs, VAT, and exports in exactly the same way. It does not. For South African customs purposes, SC-CF-30 is an import invoice policy. It is aimed at invoices used to support import clearance and explicitly does not cover exported goods. That means teams should not assume the same standing invoice policy governs every commercial invoice used in South African cross-border trade.

The 2025 declaration-data push does not make SC-CF-30 an export-invoice policy. Treat SC-CF-30 as the import-invoice baseline, while separately checking the invoice-data fields needed for export declarations.

It is also important not to confuse customs invoice requirements with domestic VAT invoice rules. The same company may issue a tax invoice for VAT purposes and also prepare a commercial invoice for customs support, but the legal tests are different. Customs officers and declarants focus on whether the invoice helps support tariff classification, customs valuation, origin claims, quantity, and the declared SAD 500 data. VAT rules focus on whether the invoice meets tax invoicing standards for input tax and domestic tax compliance. If the same supplier invoices feed the VAT return, keep a separate VAT201 supplier-invoice working file for input-tax classification and reconciliation. If your team needs the VAT side of that distinction, see South Africa VAT invoice requirements.

The easiest way to keep scope clear is to separate documents into three buckets:

1. Customs import support: does the invoice satisfy import acceptance rules and support the declaration data being submitted to SARS?
2. VAT invoicing: does the document meet domestic tax invoice requirements for VAT purposes?
3. Export documentation: does the shipment need export-specific supporting information, declaration data, or other cross-border documents that are not governed by the import invoice policy?

A final scope issue is language. The policy expects invoices in an official language. If a supplier invoice is in a foreign language, it may not be accepted as supporting documentation without translation support. In practice, teams should expect possible translation certificates and prior acceptance arrangements before relying on foreign-language invoices in a customs file. That is a workflow issue as much as a document issue: if multilingual invoices are common in your supply chain, translation should be handled before declaration submission, not after a stop or inspection request.

What Happens When Invoice Data Is Missing, Incomplete, or Later Amended

From 1 April 2025, declarations without invoice data are more likely to be selected for documentary inspection or audit. Missing invoice data can turn into broker queries, clearance delays, storage costs, avoidable rework, and post-clearance review.

For imports, the deeper risk is declaration validity. Under SC-CF-30, a customs clearance declaration may not be valid if a correct and sufficient invoice is not available when Customs asks for it.

Weak invoice data usually creates risk in three places at once:

• Valuation risk: if freight, commissions, royalties, discounts, other charges, or later price changes are missing or unclear, Customs may question whether the declared customs value is complete.
• Tariff risk: if the goods description is too generic, Customs may not be able to confirm the tariff heading from the invoice alone, which can trigger a tariff review or a request for more technical detail.
• Verification risk: if the invoice does not match the goods as imported, or if changes were made after issue and not reported, the declaration can move into documentary inspection, post-clearance verification, or customs audit.

If the invoice changes after issue, the paperwork must also change. SC-CF-30 requires an amended invoice, supplementary invoice, or debit or credit note when relevant particulars are corrected, split, increased, reduced, refunded, or otherwise changed. The importer must produce that document to Customs within one month of receiving it and report the circumstances behind the change. For Customs purposes, the amendment is not fully effective on its own: the declaration also needs to be updated and supported with the amended document and evidence explaining the change.

Recordkeeping matters for the same reason. Declarants must keep books, accounts, documents, and related electronic data for five years from the end of the calendar year concerned, and must produce them on demand. Treat invoice control as both a border-clearance issue and a post-clearance audit issue.

---

A Practical Checklist for Declaration-Ready Invoice Workflows

For a declaration-ready checklist, break the work into four control points before submission.

1. Supplier invoice content

• Check that each commercial invoice identifies the seller, the buyer or consignee, the issue date, and the origin and transaction details relevant to the shipment.
• Require a clear goods description for each line, plus brand or proprietary identifiers where they help distinguish the goods.
• Confirm quantities, prices, freight or other charges, Incoterms, and payment terms are visible or directly supportable from the file.

2. Extraction and validation

• Pull the invoice data into a structured review sheet or broker workflow before anyone keys the SAD 500.
• Flag vague descriptions, missing charges, foreign-currency values, split invoices, debit or credit notes, and any mismatch between the invoice and the goods actually shipped.
• Keep customs checks separate from VAT invoice checks and from export-specific document rules.

3. Declaration preparation

• Make one person responsible for confirming that the declaration data can be traced back to the invoice and supporting documents.
• If brokers and in-house staff both touch the file, define the handoff clearly so descriptions, quantities, and value-affecting charges are not rekeyed differently. This is where disciplined customs broker invoice-processing workflows reduce avoidable errors.
• Do not lodge the declaration until the team can explain how each valuation-sensitive field was derived.

4. Post-entry evidence

• Keep the final invoice, translations, amendments, debit or credit notes, value worksheets, and supporting correspondence retrievable.
• Assume a documentary inspection or later audit will ask you to reproduce the logic behind the entry, not just show a PDF.

The operational goal is consistency: the same description, quantity, charges, origin detail, and supporting logic should survive from supplier invoice to review sheet to declaration file. If your volume makes that difficult, build invoice data extraction workflows for customs paperwork into the process before filing, not after a documentary inspection or query lands.