Tax and SARS knowledge base
How do I upload a bulk-payment CSV file to SARS eFiling?
How do I upload a bulk-payment CSV file to SARS eFiling?
Last reviewed:
Direct answer
Prepare the bulk-payment CSV from reconciled payment data, using the current SARS bulk-payment specification, then upload it through the appropriate bulk-payment function in the correct eFiling profile. Review every validation result before any payment is authorised. An accepted upload creates no guarantee that money has been released by the bank or allocated by SARS.
Do not begin with a spreadsheet exported from payroll or bookkeeping and assume it is ready. First establish exactly which liabilities, tax types, periods and payment references are meant to be included. A bulk file is a payment instruction tool, not a substitute for reconciling your liabilities.
What this means in practice
Bulk payments help an employer, tax practitioner or administrator handle a set of liabilities efficiently. The efficiency also concentrates risk. One incorrect amount, period, reference or column value can delay a group of payments, produce a rejection, or create a difficult reconciliation later.
Treat the source workbook as your controlled record and the uploaded CSV as an output. Give the file a clear date and version, restrict edit access, and keep a copy of the exact version submitted. If one person prepares the file and another authorises it, record both checks. That small discipline is valuable when a payment is queried after staff changes or a deadline.
SARS provides a guide for bulk and additional payments on eFiling. Use the current guide and the current eFiling validation messages rather than a historic screenshot or a CSV layout supplied by a third party. Platform fields and validation rules can change.
Step-by-step
- Reconcile the liabilities first.
List every intended payment with the taxpayer, tax type, tax period, amount and supporting return, assessment or payment advice. Remove duplicates and confirm that the total agrees to your approved payment schedule.
- Confirm that you are in the correct eFiling profile.
Organisations can have more than one entity or tax product. Check the registered taxpayer name and reference number before creating or uploading anything. Do not use a company profile for a personal liability, or a personal profile for PAYE.
- Obtain the current SARS file requirements.
Use the current SARS bulk-payment guide and the live eFiling instructions to establish the accepted format. Do not rely on a prior month's field order, separator, date convention or mandatory-field rule.
- Create the CSV from controlled data.
Export only the required records. Check that every value has retained its leading zeros, decimal format and reference data. Spreadsheet software can silently alter long numbers, dates and text values, so inspect the final CSV in a plain-text or CSV viewer as part of the review.
- Upload the file and read the response.
Use the bulk-payment area made available in eFiling. Keep the upload confirmation or validation output. If eFiling flags an error, stop and determine whether the problem is file structure, missing data, an invalid reference or a mismatch in the payment schedule.
- Correct the source, not only the symptom.
Preserve the rejected file. Amend the controlled source data, regenerate a new version, and validate it again. Do not overwrite the original submission without keeping a version trail.
- Authorise only after the review is complete.
A successful upload is not the same as a completed payment. Follow the applicable bank authorisation process, retain the bank confirmation, and later check the SARS account for allocation to the intended liabilities.
Documents and records to keep
- The approved payment schedule and source reconciliation.
- The exact CSV uploaded, including version and upload date.
- Validation, rejection or acceptance messages from eFiling.
- Related returns, assessments, PANs and PRNs.
- Bank authorisation evidence and the later SARS Statement of Account.
Important limits and exceptions
An accepted file does not prove that payment is complete, while a rejected file does not remove the underlying tax debt. Do not upload a replacement if you are uncertain whether the first file has progressed to bank authorisation. Check the file or payment status first to avoid duplicate payment risk.
Where the payment date is close to a due date, build in enough time for validation and bank cut-off requirements. If you cannot determine whether a file has been submitted, authorised or rejected, preserve the evidence and obtain help before sending another instruction.
Never email unprotected payment files to unknown recipients or act on a bulk-payment request delivered through an unexpected link. Access eFiling through the official SARS route.
When to get tailored advice
Ask for help where a file contains multiple tax types, a high-value payment, a rejected file near a deadline, or a possible duplicate. TaxProof can help reconcile the file, underlying liabilities and available SARS evidence before another instruction is created.