Tax and SARS knowledge base
How do I submit FATCA or CRS information to SARS?
How do I submit FATCA or CRS information to SARS?
Last reviewed:
Direct answer
SARS publishes FATCA and CRS reporting information in its Automatic Exchange of Information area. Its current page says AEOI External BRS version 3.0.0-17 applies from 1 March 2026 for the 2027 reporting period and identifies CRS XML Schema V.3 and revised CRS regulations. A reporting organisation should first identify the applicable period, then use the current SARS specification, validate data and submit through its authorised channel.
The process does not determine whether an organisation is a reporting financial institution or whether an account is reportable. Those are separate classification and due-diligence decisions.
What this means in practice
Version control is essential. SARS's FATCA and CRS page carries current updates, including revised data fields. The page says the 2026 BRS changes include account-holder demographic and financial fields, controlling-person fields, and a rule that an RFI may submit one or more records in a single submission provided all are NULL declaration submissions. Apply the specification for the period in scope, not a format retained from a prior filing cycle.
Create a submission pack: reporting-period confirmation, current BRS and schema, source-data reconciliation, validation output, access authority, final file, declaration approval and SARS acknowledgement. The pack makes it possible to prove what was submitted and which rules were used.
Step-by-step
- Confirm the reporting entity, reporting period and filing obligation with the responsible compliance owner. Do not use this procedural guide to decide classification.
- Download the current SARS AEOI material for that period. Record the BRS version, schema version and page date in the filing workpapers.
- Map source data to the applicable fields. Reconcile account-holder, financial and controlling-person information to the controlled source systems, and document every transformation.
- Validate the file before submission. Resolve warnings and errors using the current SARS material. Preserve the original validation output and the approved final file.
- Use the authorised SARS submission channel and the correct entity profile. Restrict access to staff with approved authority. Do not email data files or credentials through an unverified address.
- Authorise the submission where the channel requires a declaration. Save the acknowledgement, reference and status after the final action.
- Monitor SARS communications. If a file is rejected or SARS releases a relevant update, assess the effect on the submitted period before changing records.
Documents and records to keep
- Period-specific SARS BRS and XML-schema record.
- Source-data reconciliation and validation output.
- Final authorised data file and submission acknowledgement.
- User authority and internal approval record.
- Error messages, corrections and SARS correspondence.
Important limits and exceptions
SARS announced a CRS trade-testing programme from 1 to 18 September 2026. Trade testing can help validate systems and business processes, but it is not a production submission or proof of compliance. SARS also states that the Connect:Direct public certificate changed in February 2026, so teams using that channel should verify their technical configuration through official support channels.
The stated BRS effective date relates to the 2027 reporting period. Do not silently apply a new BRS to an earlier period. If a period is late or an old file must be corrected, get period-specific direction. Before each cycle, record sign-off from the data owner, technical owner and authorised representative so the final file, entity and period are independently checked.
When to get tailored advice
Seek advice where financial-institution classification, account due diligence, reportability, self-certification, an entity merger or cross-border data mapping is uncertain. Escalate quickly if a current specification changes near a deadline, a submission is rejected, or confidential reportable data has been exposed.
Related TaxProof guides
Sources
- SARS, FATCA and CRS