How to submit IT3(d) using the HTTPS channel

To submit IT3(d) using the HTTPS channel, the organisation must prepare an IT3(d) third-party data file, upload it through SARS Secure Web: HTTPS, and then declare the submitted data on eFiling.

This route is used for file-based IT3(d) submissions, not for capturing Section 18A receipts directly on the IT3-01 form.

Before using the HTTPS channel, make sure that:

• the organisation has an eFiling profile
• the organisation is enrolled for third-party data submission
• Secure Web: HTTPS is active for the organisation
• the Business Administrator is enrolled
• the Technical Administrator is enrolled
• the Technical User is enrolled
• the IT3 tax type has been activated
• a SARS security certificate has been requested and imported
• the IT3(d) data file has been prepared according to the SARS External BRS

Step 1: Confirm that the organisation is enrolled for Secure Web: HTTPS

Log in to eFiling. Then go to: Services > Enrol 3rd Party Data > Enrol Organisation. Check that the Secure Web: HTTPS channel is selected. Check the enrolment status.

The organisation must show as Legal Entity Enrolled before the HTTPS submission process can continue. If the status shows Legal Enrolment Requested, SARS is still validating the enrolment.

Step 2: Confirm that the Technical Administrator is enrolled

Go to: Services > Enrol 3rd Party Data > Enrol Technical Admin

Check that the Technical Administrator appears on the page.

Check the status of the Technical Administrator. The status should show Link Enrolled.

If the Technical Administrator does not appear, or the status is not enrolled, the Technical Administrator must be enrolled before continuing.

Step 3: Confirm that the IT3 tax type is activated

Go to: Organisation > Tax Types > Manage Tax Type

Check that IT3 appears under the activated tax types. If IT3 is not active, activate the IT3 tax type before continuing.

Step 4: Confirm that the Technical User is enrolled

Go to: Services > Enrol 3rd Party Data > Enrol Technical User

Check that the Technical User appears on the screen. Check the status column, the status should show Role Enrolled. If the status shows Role Enrolment Requested, SARS is still processing the enrolment.

Step 5: Request the SARS security certificate

The Technical Administrator must request the SARS security certificate.

Go to: Services > Enrol 3rd Party Data > Request Certificate

Click Request New Certificate.

Accept the terms and conditions.

Click Continue and Request.

Capture the Interface Name.

Select Manually.

Click Continue.

Click Request Certificate.

Step 6: Retrieve the SARS certificate from email

SARS will send two emails.

Use the emails to get:

• the Reference Code
• the Authorisation Code
• the Registration Link

Open the certificate link sent by SARS.

Click Next.

Enter the Reference Number.

Enter the Authorisation Code.

Click Generate PKC12.

Create the required password.

Click Generate PKC12 again.

Download the certificate file.

Step 7: Import the SARS security certificate

On the computer that will be used for the HTTPS submission, open Internet Options.

Go to: Content > Certificates

Select Import.

Click Next.

Browse to the certificate file that was downloaded.

Select the certificate file.

Click Next.

Enter the certificate password.

Click Next.

Select Automatically select the certificate store based on type of certificate.

Click Next.

Click Finish.

Click OK when the import is complete.

Step 8: Prepare the IT3(d) file

Prepare the IT3(d) data file according to the SARS External BRS.

The file must be structured in the required SARS pipe-delimited text format before it is uploaded.

For IT3(d), the data relates to Section 18A donor and donation receipt information.

Do not upload the file until the data has been checked against the required SARS file structure.

Step 9: Open Secure File Submission

Log in to eFiling and go to: Services > Enrol 3rd Party Data > Secure File Submission

A list of certificates ready for submission will be displayed.

Select the imported certificate.

Step 10: Log in to the Secure File Gateway

After selecting the certificate, eFiling will open the Secure File Gateway.

Enter the Technical User ID.

Enter the Technical User password.

Click the Submission tab.

Step 11: Upload the IT3(d) file

In the Mailbox Path dropdown, select:

/

Click Browse.

Select the prepared IT3(d) file.

Attach the file.

Click Send.

Step 12: Confirm that the file was routed

After sending the file, check the submission status. The status should show Routed. Routed means the file was sent to SARS successfully.

Step 13: Check the response file

Open the Response Files tab and download or save the response file before opening it.

Check the response file to see whether SARS accepted the file or returned issues that need attention.

Step 14: View the submission on the dashboard

To view submitted data, go to: Services > Enrol 3rd Party Data > Submission Dashboard

Use the dashboard to view submitted files and their status.

Step 15: Declare the submitted IT3(d) data

After the IT3(d) file has been submitted through HTTPS, the data must still be declared on eFiling.

Go to: Returns > Third Party Data > Request Return

Select IT3.

Select the applicable third-party data type.

Select the applicable period.

Open the IT3-02 declaration return.

Step 16: Check the IT3-02 declaration

Review the pre-populated IT3-02 declaration.

Check that the declaration information matches the IT3(d) file submitted through HTTPS.

If the information is incorrect, do not submit the declaration yet. Correct the submitted data first.

Step 17: Submit the IT3-02 declaration

If the IT3-02 declaration information is correct, submit the return.

Click Submit Return.

The HTTPS submission process is only complete once the IT3(d) file has been submitted and the IT3-02 declaration has been submitted on eFiling.

Final check

A HTTPS IT3(d) submission should include:

• Secure Web: HTTPS enrolment
• enrolled Technical Administrator
• enrolled Technical User
• activated IT3 tax type
• valid SARS security certificate
• prepared IT3(d) data file in pipe-delimited text format
• successful Secure File Submission
• response file review
• IT3-02 declaration submitted on eFiling