Prepare a VAT201 from Supplier Invoices in South Africa

To prepare a VAT201 from supplier invoices in South Africa, build a period working file before you open the SARS return. That file should validate each claimable tax invoice, separate input VAT into Fields 14, 14A, 15, and 15A, capture Field 18 adjustments for credit and debit notes, and reconcile the totals to the supplier ledger before eFiling.

The working file is the bridge between a folder of supplier invoice PDFs and the figures entered on the VAT201. It should preserve the source PDF, page reference, supplier VAT number, invoice type, rate treatment, import flag, capital-goods flag, VAT201 field, and review notes for each row. If SARS verifies the return, the reviewer should be able to move from any input-tax field total back to the document evidence without rebuilding the calculation.

The field split matters because SARS does not treat input tax as one undifferentiated total. The SARS VAT201 return guide says VAT201 Field 14 is for permissible VAT on capital goods or services, Field 14A is for imported capital goods, Field 15 is for other goods or services that are not capital goods, Field 15A is for other imported goods, and Field 19 totals Fields 14, 14A, 15, 15A, 16, 17, and 18.

This is not a substitute for tax judgement. It is a control workflow for the bookkeeper, outsourced preparer, or finance manager who needs to assemble evidence, flag uncertain rows, and make the VAT201 reviewable before it is submitted.

Set the VAT period and source folder before extracting anything

Start with the VAT period, not with the invoice folder. A supplier invoice belongs in the working file because it supports the VAT period being prepared, not simply because it arrived during the month or appears in a download from the accounting system.

For an in-house bookkeeper, the period boundary usually follows the vendor's SARS VAT category and internal close timetable. For an outsourced practice, the same rule has to be applied client by client, because a monthly client and a two-monthly client cannot share the same working-paper rhythm. Name the file around the vendor, VAT number, period, and preparer, then freeze that as the control file for the return.

The intake folder should hold every document that might affect the input-tax side of the return:

• Supplier tax invoices and abridged tax invoices
• Credit notes and debit notes
• Import VAT evidence and customs documents
• Foreign-currency supplier invoices and rate support
• Supplier statements or ledger exports used for reconciliation
• Notes explaining late, duplicate, disputed, or excluded documents

Keep current-period documents separate from late prior-period invoices, duplicate copies, and documents that need review before they can be claimed. Invoice date, time of supply, ledger posting date, and payment date can point in different directions. The working file should make those differences visible instead of hiding them inside a single total.

For practice teams, folder discipline is not admin polish. It is what lets a reviewer understand the file without asking the preparer to reconstruct the month. Use the same folder pattern across clients, keep the source PDFs unchanged, and record any judgement call in the working file while the document is still in front of you.

Extract the columns that make the spreadsheet reviewable

A VAT201 input-tax spreadsheet needs more than supplier, date, and VAT amount. It has to carry enough evidence for a reviewer to understand why each row was included, which VAT201 field it feeds, and where the source document sits if SARS asks for support.

At minimum, build columns for supplier name, supplier VAT number, invoice number, invoice date, document type, gross amount, net amount, VAT amount, currency, ZAR equivalent, rate source, rate type, capital-goods flag, import-goods flag, VAT201 field, s20(4) validity status, source file, page reference, and review notes. If the supplier ledger uses a different supplier code or account name, include that too so the reconciliation does not depend on memory.

One row per invoice is enough only when the invoice has one VAT treatment and one classification. A simple local rent invoice can usually sit on one line. A mixed invoice with standard-rated items, exempt items, delivery charges, or non-VAT disbursements may need line-level rows so the claimable input tax is not overstated. Foreign-currency and import documents also need extra columns, because the ZAR value and evidence trail are part of the claim.

Treat the VAT201 field as a reviewed classification, not a value the extraction process should decide on its own. The extraction step can capture the facts that support the judgement: description, document type, VAT amount, currency, import indicator, supplier details, and source reference. The preparer or reviewer decides whether the row belongs in Field 14, 14A, 15, 15A, Field 18, or outside the claim.

There are three practical execution patterns. Low-volume vendors can capture the required columns manually from the ledger and source PDFs. Cloud-ledger users may use OCR or bill-capture data as the first draft, then add VAT201 review columns. Higher-volume vendors and practices can extract supplier invoice data into a VAT201 working file by uploading invoice batches to Invoice Data Extraction and prompting for the required spreadsheet columns. The product converts uploaded invoices and financial documents into structured Excel, CSV, or JSON files, including batch processing of up to 6,000 mixed-format files per session. It structures the evidence; the VAT judgement still belongs with the bookkeeper, controller, or tax practitioner.

Use the validity gate to decide which rows can support input tax

Every row should pass a validity gate before it contributes to the input-tax fields. The gate is not a second article on invoice law. It is a working-file status that tells the reviewer whether the row is claimable, excluded, or waiting for a corrected document.

For a normal supplier tax invoice, the preparer should be able to see the tax invoice wording where required, supplier name, supplier VAT number, invoice number, invoice date, description, consideration, VAT amount or tax-inclusive total, and recipient detail where the invoice value requires it. Use the working-file status column to mark rows as valid, abridged-valid, missing VAT number, missing recipient detail, no tax invoice, duplicate under review, or corrected invoice requested. The detailed field-by-field rules belong in the existing guide to South Africa VAT invoice requirements for the s20(4) validity gate.

Abridged invoices need careful handling because they are common in high-volume, low-value supplier spend. Fuel slips, courier charges, travel costs, and small restaurant invoices can still matter to the VAT201, but the R5,000 threshold changes which invoice details are expected. Capture an abridged-invoice flag rather than letting those documents disappear into a generic supplier total.

Do the exclusion work at line level where necessary. Zero-rated supplies may have no VAT to claim. Exempt supplies do not support input tax in the same way as standard-rated taxable supplies. A supplier that is not VAT-registered cannot create input VAT for the vendor. If a single supplier invoice mixes claimable and non-claimable rows, split it before it reaches the VAT201 field pivot.

Foreign-currency invoices need their own evidence trail. The full exchange-rate mechanics sit in BGR 11 foreign-currency invoice rules for South Africa. In the VAT201 working file, capture the invoice currency, foreign amount, ZAR equivalent, rate source, rate date, and review note so the converted input-tax value can be traced.

Import VAT should be supported by customs evidence, not only by a supplier invoice. Keep the customs code, import document reference, release evidence, and VAT payment evidence with the row. The existing guide to South Africa customs invoice data requirements for import VAT evidence is the better place for import-document detail; the VAT201 file only needs enough structure to route the row to the right import field and preserve the evidence.

Map each reviewed row to Field 14, 14A, 15, 15A, or 18

Once validity is clear, classify the claimable VAT rows. The field mapping should be visible in the working file before the VAT201 is completed, because this is where a reviewer can still challenge the classification without reopening the whole return.

Use Field 14 for permissible VAT on local capital goods or services. Use Field 14A for imported capital goods. Use Field 15 for local other goods or services that are not capital goods. Use Field 15A for other imported goods. Use Field 18 for relevant adjustments, including credit-note and debit-note items that must be treated as VAT201 adjustments. Field 19 is then the total input-tax figure calculated from the input-tax and adjustment fields.

Fields 16 and 17 also feed Field 19, but they should not be buried inside the ordinary supplier-invoice pivot. Keep second-hand goods or change-in-use items and bad-debt deductions on separate review tabs, with their own support and reviewer sign-off, so the supplier-invoice working file still explains the Fields 14, 14A, 15, 15A, and 18 amounts cleanly.

The capital-goods decision should be a review flag, not a guess hidden in the spreadsheet. Machinery, vehicles, computer equipment, fixtures, and similar long-term assets are the kinds of rows that usually deserve closer review. Rent, accounting fees, cleaning materials, insurance, stationery, telephone costs, utilities, and stock purchases are usually reviewed as other goods or services rather than capital goods. If the description is vague, leave a note and send the row to review.

Credit notes and debit notes need their own document type, original-invoice reference where available, VAT amount, and sign convention. A credit note that reduces a previous claim should not sit unnoticed as a positive invoice row. A debit note should not be merged into the supplier total without showing why it changes the VAT201 adjustment position. Match the document to the original invoice where practical, then record the Field 18 treatment and review note.

Mixed-treatment invoices are where many working files become unreliable. A single supplier PDF can include standard-rated items, exempt items, zero-rated items, non-VAT charges, and a capital item on the same document. If the invoice is not cleanly one treatment, create line-level rows or separate claimable and non-claimable portions before the pivot table is built.

Add sign-off columns for preparer, reviewer, classification note, and unresolved issue. A finance manager should be able to filter the file for all Field 14 and 14A rows, inspect the high-value claims, and see who accepted the classification. That review discipline matters more than a neat spreadsheet total.

Reconcile the working file before entering the VAT201

The working file is not ready because the rows add up. It is ready when the trail is clear: source PDFs to extraction rows, extraction rows to VAT201 field pivots, field pivots to the return, and working-file totals to the supplier ledger or AP subledger.

Run duplicate checks before reviewing the totals. Sort or test by supplier VAT number, invoice number, invoice date, VAT amount, gross amount, and source filename. Duplicate PDFs often enter the file through email forwards, supplier statements, ledger attachments, and reissued invoices. If the same invoice appears twice with slightly different filenames, the working file should show which copy was used and which one was excluded.

The supplier-ledger reconciliation is a bridge, not a simple equality test. The ledger may include unpaid invoices, prior-period late invoices, invoices posted after period close, non-claimable VAT, supplier accounts without VAT registration, and credit notes awaiting matching. Reconcile by explaining the differences, not by forcing the working file to agree with a ledger balance that contains items outside the VAT201 claim.

A useful review pack includes field pivots for Field 14, 14A, 15, 15A, and 18; a list of excluded rows; a duplicate-review tab; a foreign-currency and import-VAT review tab; and a supplier-ledger bridge. The reviewer should be able to filter by supplier, VAT201 field, document type, exception status, and preparer note.

Before eFiling, compare the current period with prior periods. A large Field 14 claim may be correct if the vendor bought equipment, but it should be explained. A negative Field 18 adjustment, a cluster of foreign-currency invoices, or a new import-VAT claim should have support ready. Once the review is done, enter or check the SARS VAT201 field totals and keep the working file with the submitted return evidence.

Keep an evidence pack that can answer SARS verification

The final output is not just a filed VAT201. It is a defensible evidence pack that explains how the filed input-tax figures were prepared.

Keep the final VAT201 working file, the filed return or submission confirmation, source PDFs, import evidence, foreign-currency rate support, supplier-ledger reconciliation, review notes, and unresolved-issue sign-off together. If the return is reviewed weeks or months later, the file should still explain the claim without relying on the preparer's memory.

SARS verification is easier to answer when every figure traces both ways. From the VAT201, a reviewer should be able to open the Field 15 total, see the supplier rows behind it, inspect the source PDFs, and understand why excluded rows did not feed the claim. From a source invoice, the reviewer should be able to see whether it was claimed, excluded, split, adjusted, or held for correction.

This monthly or bi-monthly evidence pack is separate from annual supplier-evidence work, but the discipline overlaps. A clean VAT201 file preserves supplier names, VAT numbers, invoice references, source documents, and review notes that can also support adjacent workflows such as the B-BBEE supplier-invoice evidence pack workflow.

The practical standard is simple: any VAT201 input-tax field total should trace back to the specific invoice row, source document, and judgement note that supports it. If the working file can do that, the preparer has built something more useful than a spreadsheet total.