Tax and SARS knowledge base
How must an insurer submit insurance-payment data to SARS?
What should an insurer verify before submitting insurance-payment third-party data to SARS?
Last reviewed:
Direct answer
An insurer must identify payments covered by the current SARS insurance-data specification, create the prescribed third-party file and submit it through an approved channel. Policyholder, beneficiary, payment and product data must be drawn from controlled source systems and reconciled to the reporting period.
Not every policy movement has the same reporting treatment. Classify the event before mapping it to a field or code.
What this means in practice
Separate policy administration, claims and finance responsibilities in the control schedule. The person who knows why a payment was made may not be the person who can verify the ledger total.
Pay close attention to replacements, reversals, joint ownership, beneficiary payments and corrected identity details.
Step-by-step
- Confirm the current insurance-data specification and period.
- Identify reportable products and payment events.
- Extract policyholder, beneficiary and payment information.
- Reconcile the population and values to the source ledgers.
- Validate identities, tax numbers, dates and reportable codes.
- Submit through the approved channel.
- Investigate response-file rejections at source.
- Submit controlled corrections and sign off the final reconciliation.
Documents and records to keep
- Product and event classification rules.
- Policy and claims source extracts.
- Ledger-to-submission reconciliation.
- Submission and response files.
- Correction register and approval.
Important limits and exceptions
Do not infer a tax result for the recipient solely from the existence of a reported payment.
A rejected identity should be investigated, not replaced with a convenient placeholder.
When to get tailored advice
Get specialist input where product classification is unclear, payments cross borders, ownership changed or the insurer cannot reconcile values.