Why SARS Supporting-Document Uploads Fail — and What to Check

A supporting-document upload can fail even when the underlying document is valid. The problem is often the file rather than the tax information: it may be too large, difficult to read, password-protected, incomplete, or saved with an awkward filename. A rejection message may not identify the exact cause, so repeatedly uploading the same file is rarely the best first response.

This guide explains a calm, privacy-conscious way to prepare a cleaner copy before trying again. It is general document-preparation information, not tax advice. Always follow the current instructions shown in SARS eFiling for your request and document type.

1. The file is too large

Phone cameras create high-resolution images. A few pages photographed separately and combined into one PDF can quickly become oversized. Screenshots can also add unnecessary data while making text less clear.

Start from the original document where possible. Scan only the relevant pages, crop away the desk or background, and compress the PDF without making small print unreadable. After compression, open the final file and zoom in on names, dates, amounts and reference numbers. A small file that cannot be read is not a useful fix.

Portal limits and requirements can change, so confirm the limit displayed in the upload flow rather than relying on an old checklist or social post.

2. Pages are blurry, dark or skewed

A document can look acceptable as a thumbnail but fail a practical readability check. Motion blur, shadows, glare, folded corners and steep camera angles can hide important details. Automatic image enhancement cannot recover text that was never captured clearly.

Place the paper on a flat, contrasting surface in even light. Hold the phone parallel to the page, keep every corner visible and avoid using flash when it creates glare. Review each page at full size before creating the PDF. If one page is unclear, rescan that page instead of rebuilding everything from poor images.

3. The PDF is encrypted or password-protected

Password protection can prevent an upload service from reading a PDF. Statements and certificates downloaded from financial providers are sometimes protected by default. Do not share the password publicly or send sensitive documents to an unknown online “unlock” service.

Use a trusted workflow on a device you control to create an unprotected copy, provided you are authorised to do so. Then close and reopen the copy to verify that it no longer requests a password and that every page is present. Keep the original securely until the process is complete.

4. The format is not accepted

A file extension is not always a reliable description of a file. Renaming `photo.heic` to `photo.pdf` does not convert it into a PDF. A damaged download may also carry a normal-looking filename but fail to open.

Open the file locally before uploading it. If the requested format is PDF, create a real PDF through a scanner or print-to-PDF workflow. Avoid unusual image formats when the portal requests a standard document type. Check the current eFiling prompt for accepted formats because the correct choice depends on the specific upload screen.

5. The filename causes trouble

Long filenames, punctuation, repeated dots and special characters can create avoidable friction. Use a short, descriptive name with letters, numbers, hyphens or underscores—for example `medical-aid-certificate-2026.pdf`. Do not put passwords, ID numbers or other unnecessary personal information in the filename.

Give different documents different names. Clear naming also helps you confirm that you selected the intended file instead of an earlier draft.

6. Pages are missing, duplicated or in the wrong order

Multi-page scans deserve a final page-by-page review. Confirm that the first and last pages are present, every page is upright, no page appears twice, and related pages are in a logical order. Remove accidental photos of the floor, a blank desk or unrelated correspondence.

Where the request expects one document, combine the relevant pages into one coherent PDF. Where it asks for separate documents, keep them separate. The request shown in eFiling is the source of truth.

Protect the information while you troubleshoot

Supporting documents can contain identity numbers, addresses, account details and medical or financial information. Prefer preparation tools that keep the work on a device you control. Avoid uploading files to an unfamiliar converter merely because it promises a quick fix. Delete unnecessary intermediate copies, use the phone’s screen lock, and share the final document only through the channel required for the task. If another person, such as a tax practitioner, is helping you, agree on a secure transfer method and confirm which pages they actually need. Document preparation should reduce upload friction without creating a new privacy risk.

A pre-upload checklist

Before another attempt:

1. Read the current request and upload requirements in eFiling.
2. Open the final file on your device.
3. Confirm the format matches the upload prompt.
4. Check that there is no password prompt.
5. Zoom in and verify that all important text is readable.
6. Confirm every required page is present and correctly oriented.
7. Use a short, simple filename.
8. Check the final file size against the limit displayed by the portal.
9. Keep the original and the prepared copy securely.
10. Upload the intended file once and retain any confirmation or reference provided.

Prepare the document on your phone

TaxScanZA is designed to help prepare readable, correctly sized tax-document PDFs for eFiling. Processing happens on-device. You can prepare five documents free; Pro is R49 once, with no subscription. The app is available for iOS and Android.

Prepare a supporting document with TaxScanZA

TaxScanZA is independent from SARS. It does not submit tax returns, access your SARS account, or provide tax advice. Using the app cannot guarantee that SARS will accept a document, because acceptance depends on the request, current portal rules and the document itself.