Summary : SEBI’s circular dated 11 November 2026 moves registered intermediaries that qualify as Reporting Financial Institutions into the revised Automatic Exchange of Information framework under section 508 of the Income-tax Act, 2025, Rules 238 to 240 of the Income-tax Rules, 2026 and Form 166. It is not a direction to every SEBI intermediary to report every client. The first control is classification: determine whether the intermediary is an RFI and whether an account is reportable under the Rules. For an in-scope intermediary, the circular requires the revised due-diligence and reporting requirements to be built into customer onboarding and KYC, and it identifies four system changes—self-certification validity, controlling-person roles, account type and pre-existing/new status, and the new mandatory fields in Form 166 XML. It also requires client FATCA and CRS certifications to be uploaded to KRA systems and places responsibility for obtaining and reporting those certifications on the intermediary. This guide converts the circular into a data-lineage, exception and evidence model without treating a KRA upload or a valid XML file as proof that the underlying classification is correct.
- What the 11 November 2026 Circular Changes for SEBI Intermediaries
- Rules 238–240 Must Be Reflected in Onboarding and KYC
- Do not confuse ordinary KYC with AEOI due diligence
- Validity must be a controlled status, not free text
- Controlling-person roles need coded precision
- Form 166 XML: Build a Data-Lineage Control Before Filing
- KRA Upload Is a Separate Obligation and a Reconciliation Point
- Governance, Testing and Evidence for the First Revised Cycle
- Assign ownership across compliance, tax, operations and technology
- Test changed fields with both positive and negative cases
- Preserve an auditable filing package
- Frequently Asked Questions
- Does every SEBI-registered intermediary have to file Form 166?
- What replaced Form 61B references for the revised regime?
- Is a collected self-certification automatically valid?
- Why must controlling-person roles be stored separately?
- Does successful XML validation prove correct reporting?
- Does uploading a certification to a KRA shift responsibility to the KRA?
- What should be reconciled before submission?
- Key Takeaways
What the 11 November 2026 Circular Changes for SEBI Intermediaries
The circular is addressed to all SEBI-registered intermediaries, stock exchanges and depositories, but its operative reporting obligation is directed to registered intermediaries that qualify as Reporting Financial Institutions. Rule 238 supplies the relevant definitions. The compliance file should therefore start with a documented entity-level classification rather than an assumption based only on SEBI registration. That memorandum should identify the entity’s activities, the financial accounts it maintains, any exclusions relied on and the approving legal or tax reviewer.
SEBI records that the earlier securities-market circulars were framed under section 285BA of the Income-tax Act, 1961, Rules 114F to 114H and Form 61B. From 1 April 2026, the governing references are section 508 of the Income-tax Act, 2025, Rules 238, 239 and 240 and Form 166 of the Income-tax Rules, 2026. Legacy procedures may still contain accurate operational concepts, but references, field names, validation rules and evidence maps must be reconciled to the new law before they are reused.
| Control layer | Required 2026 position | Evidence that should exist |
|---|---|---|
| Entity classification | Confirm whether the intermediary is an RFI under Rule 238 | Approved classification memorandum and activity map |
| Account classification | Identify reportable status and pre-existing/new account status | Rule-based decision record linked to account master |
| Self-certification | Capture certification and its validity indicator | Source form, validation outcome, date and exception trail |
| Controlling persons | Capture the applicable role, not only a name | Ownership/control analysis and role-coded master data |
| Return output | Generate Form 166 XML with all mandatory fields | Schema version, validation log and filed acknowledgement |
| KRA record | Upload FATCA/CRS certifications obtained from clients | KRA response, rejection queue and reconciliation |
Rules 238–240 Must Be Reflected in Onboarding and KYC
Do not confuse ordinary KYC with AEOI due diligence
Identity and address verification under the securities KYC framework is necessary but does not by itself answer FATCA and CRS questions. AEOI due diligence may require tax residence, taxpayer identification information, entity classification, controlling-person information and indicia review. The onboarding journey should preserve which question produced each data element, who supplied it, whether documentary evidence was reviewed and which rule-based test converted the answers into an account classification. A generic ‘FATCA compliant’ flag is too coarse for audit or correction work.
Validity must be a controlled status, not free text
SEBI specifically requires self-certification collection procedures to capture a validity indicator. The data model should distinguish received, valid, invalid, expired or superseded, and pending remediation. A certification should not be marked valid merely because mandatory boxes are populated. Controls should test internal consistency, completeness, signature or authentication, tax-residence logic and any reason-to-know issue arising from other KYC data. Where a certification is rejected, the account should enter a dated exception workflow with an owner, permitted interim treatment and escalation date.
Controlling-person roles need coded precision
The circular calls for roles such as settlor, trustee, protector, beneficiary and other to be captured. A single ‘controlling person’ label loses the relationship that the revised return expects. For trusts and similar arrangements, the source file should show the legal role, the basis for control, identifying particulars, tax residence and the link to the relevant entity account. When one individual occupies more than one role, the system and Form 166 mapping should preserve each reportable relationship rather than overwrite the earlier value.
Form 166 XML: Build a Data-Lineage Control Before Filing
A file that passes portal validation can still contain a wrong classification, stale certification or incorrectly mapped controlling person. The Form 166 process should therefore trace every mandatory XML element back to an approved source field. The mapping document should record the business meaning, source system, transformation rule, permitted values, blank treatment, validation rule and accountable owner. The version of the Income-tax schema used for generation should be frozen for each reporting cycle and changes should be tested before production deployment.
SEBI warns that omission of new mandatory fields will produce Income-tax portal validation errors. Rejection management should separate structural errors from substantive exceptions. Structural errors include invalid format, missing mandatory tags or value-length problems. Substantive exceptions include a questionable tax residence, inconsistent TIN, missing controlling-person role or an invalid self-certification. The former may be corrected by technology; the latter requires a compliance decision supported by the underlying customer file.
| Reconciliation | Population | Failure that it detects |
|---|---|---|
| RFI account master to due-diligence output | All financial accounts maintained by the RFI | Accounts omitted from the classification engine |
| Valid certifications to KRA upload | All certifications accepted as valid | Accepted certification never uploaded or KRA rejection ignored |
| Reportable accounts to Form 166 XML | Every account meeting reportability rules | Reportable account or controlling person missing from return |
| XML acceptance to filed return archive | Every upload attempt and final acceptance | Corrected file not tied to acknowledgement |
| Prior-year data to current-year status | Continuing accounts and changed circumstances | Stale tax residence or account classification carried forward |
KRA Upload Is a Separate Obligation and a Reconciliation Point
The circular requires registered intermediaries to upload FATCA and CRS certifications obtained from clients onto KRA systems. The intermediary retains the onus for obtaining and reporting the certification and related compliance. KRA storage does not transfer the legal responsibility or validate the intermediary’s classification. The upload interface should return a reference, status or rejection message that can be linked to the client and certification version. Batch totals should reconcile to the population marked valid and due for upload.
Where multiple intermediaries rely on the same KRA record, each should follow its own reason-to-know and changed-circumstances controls. A certification that is visible centrally may have been collected for an earlier account, a different entity type or before a material change. The intermediary should document the basis on which it treats the certification as usable and should not silently replace a newer client submission with an older central record.
Governance, Testing and Evidence for the First Revised Cycle
Assign ownership across compliance, tax, operations and technology
The policy owner should approve the RFI interpretation and due-diligence logic; operations should own document collection and exception follow-up; technology should own schema-controlled generation and audit logs; and an independent reviewer should test population completeness and sample classifications. Vendor-operated onboarding, KRA connectivity or XML generation remains within the intermediary’s control environment. Contracts and service reports should support access to source data, correction timelines and evidence retention.
Test changed fields with both positive and negative cases
Testing should cover valid and invalid self-certifications, multiple controlling-person roles, pre-existing and new accounts, missing mandatory fields, changed tax residence, closed accounts and corrected submissions. Each test should retain input, expected output, actual output and resolution. A small test population is not sufficient if it excludes complex entities or trust relationships that drive the new role fields.
Preserve an auditable filing package
The final archive should contain the applicable Rules and circular version, entity classification, account population, due-diligence results, exception approvals, KRA reconciliation, XML hash or controlled copy, validation report, submission acknowledgement and any correction history. The archive should permit a reviewer to move from a reported XML element back to the client evidence and from the complete account population forward to the filing conclusion.
Frequently Asked Questions
Does every SEBI-registered intermediary have to file Form 166?
No automatic conclusion should be drawn from registration alone. The entity must first determine whether it qualifies as a Reporting Financial Institution under Rule 238 and then apply the account and reportability rules.
What replaced Form 61B references for the revised regime?
SEBI’s circular points to section 508 of the Income-tax Act, 2025, Rules 238 to 240 and Form 166 of the Income-tax Rules, 2026 from 1 April 2026.
Is a collected self-certification automatically valid?
No. The intermediary should apply completeness, consistency, authentication and reason-to-know checks and retain a validity status and exception trail.
Why must controlling-person roles be stored separately?
The revised data requires the relationship—such as settlor, trustee, protector or beneficiary—not merely the person’s identity. Multiple roles may need separate representation.
Does successful XML validation prove correct reporting?
No. Validation mainly tests the file against the schema. Classification, source evidence and completeness require separate compliance controls.
Does uploading a certification to a KRA shift responsibility to the KRA?
No. SEBI states that the onus for obtaining and reporting FATCA/CRS certification and related compliance remains with the intermediary.
What should be reconciled before submission?
At minimum, reconcile the account master to due diligence, valid certifications to KRA uploads, reportable accounts to Form 166 and accepted XML to the final acknowledgement.
Key Takeaways
- Begin with a documented RFI classification; SEBI registration alone is not the reporting test.
- Rebuild legacy section 285BA, Rules 114F–114H and Form 61B references around section 508, Rules 238–240 and Form 166.
- Store self-certification validity, controlling-person roles and pre-existing/new status as auditable data.
- A valid XML file and a KRA upload do not prove substantive accuracy or completeness.
- The intermediary remains accountable for collection, reporting, reconciliation and correction evidence.
*****
Disclaimer: This article is a general editorial explanation of SEBI Circular No. HO/38/14/(18)2026-MIRSD-POD2/I/25560/2026 dated 11 November 2026 and the statutory references identified in that circular. It is not legal, tax, regulatory, technology, data-protection, KYC, FATCA, CRS, treaty or reporting advice and does not classify any intermediary, account, entity, trust, controlling person or customer as reportable or non-reportable. The definitions, exclusions, due-diligence procedures, aggregation rules, changed-circumstances standards, filing dates, reportable data and correction processes must be applied from the Income-tax Act, 2025, Income-tax Rules, 2026, Form 166 schema, CBDT guidance, SEBI requirements and portal specifications in force for the relevant cycle. A portal acceptance, KRA upload, vendor certificate or prior-year treatment does not establish substantive compliance. Facts concerning activities, account types, tax residence, ownership, control, legal roles, documentary evidence and the validity of self-certifications can materially change the result. Intermediaries should obtain advice from appropriately qualified legal, tax, compliance and systems professionals, test the actual production data and preserve evidence of classification, review, filing and corrections. Any example or control described here is illustrative and must be adapted to the entity’s systems and obligations. TaxGuru accepts no responsibility or liability for any omitted account, incorrect classification, portal rejection, regulatory action, data error, customer consequence, missed deadline, penalty, information-security event or other loss arising from reliance on this article, incomplete facts, system behaviour, later clarification or subsequent change in law, schema or regulatory practice.






