Tax and SARS knowledge base
Why was my SARS bulk-payment file rejected?
Why was my SARS bulk-payment file rejected?
Last reviewed:
Direct answer
A SARS bulk-payment file can be rejected because its structure, required values or payment data do not match the current eFiling validation requirements. Preserve the original file and the exact error message, correct the controlled source data, generate a new version and validate it again. A rejected upload does not cancel the liability it was intended to pay.
The safest first move is to stop rather than repeatedly upload altered files. Identify whether the rejection relates to the CSV format, a missing field, a taxpayer or tax-type mismatch, or payment details. The specific on-screen validation message and SARS's current bulk-payment guidance should determine the repair.
What this means in practice
Bulk payment processing is useful because it can group many liabilities into a controlled workflow. It also means that a poor input can affect several obligations. A rejection may be harmless when it is caught early, but it becomes urgent when a due date is close or the team cannot tell whether an earlier version has already been authorised.
Start from the liability schedule, not from the rejected CSV. The schedule should show the taxpayer, tax type, period, payment reference, amount and supporting return or assessment for each line. If those facts are wrong, fixing a column delimiter will not solve the actual problem.
Use a separate file version for every attempted correction. It should be possible to see which version was rejected, which change was made, who reviewed it and whether the corrected file was later accepted. This protects the taxpayer and makes a later SARS or internal reconciliation much easier.
Step-by-step
- Save the evidence before editing.
Download or capture the validation output, save the rejected CSV and record the upload date, time and eFiling profile used. Do not overwrite the file called "final.csv" with an unlabelled replacement.
- Confirm the status of any earlier instruction.
Check whether the file was only rejected at validation or whether any payment instruction reached bank authorisation. If there is uncertainty, do not create a second payment route until the status is clear.
- Classify the rejection.
Read the current eFiling message closely. It may point to file structure, a required value, a reference, an amount or a record that does not match the selected taxpayer profile. Avoid assuming that a familiar message has the same meaning as it did in a previous filing period.
- Compare the source schedule with SARS records.
Check the tax type, period, amount and PRN against the related return, assessment or PAN. A payment reference is designed to help the amount reach the right taxpayer account, so a mismatched reference must be investigated before resubmission.
- Check the CSV format against the current SARS guide.
Confirm the prescribed file type, required fields and current eFiling instructions. Spreadsheet applications can change text values, dates and long reference numbers on export. Inspect the exported CSV, not just the source workbook.
- Correct the source and regenerate a new version.
Record what changed, then create a newly named CSV. Submit only the corrected version. Maintain the rejected file and its message as part of the audit trail.
- Validate, authorise and reconcile separately.
A successful upload only means the file passed that stage. Complete any bank authorisation required, retain the bank evidence and review the SARS Statement of Account later to see whether the payment is allocated as intended.
Documents and records to keep
- The original and corrected CSV files, with version names.
- The eFiling rejection message and later validation result.
- Liability schedule, returns, assessments and PANs.
- PRNs, bank authorisation evidence and account statements.
- A note recording reviewer, preparer and final outcome.
Important limits and exceptions
Do not guess an error code or change a PRN merely to bypass a validation message. That can create an allocation problem that is more difficult than the original rejection. A rejected file also does not extend a filing or payment deadline.
If a payment may be duplicated, a deadline has passed, or the file contains PAYE, VAT or several business entities, pause and reconcile before resubmitting. The correct SARS path can depend on the tax type and the stage the payment reached.
When to get tailored advice
Get help when the eFiling response is unclear, the total is material, a payment has been authorised but is not visible, or a replacement may duplicate a prior payment. TaxProof can help build an evidence-led recovery plan before the next submission.