NSE FATF Compliance Submission Is Due August 21: Trading Members Told to Update ENIT New Compliance
National Stock Exchange (NSE) trading members had to complete the FATF compliance submission for the June 2026 plenary cycle by Friday, 21 August 2026. The filing is made in the FATF module of the Exchange's ENIT New Compliance system. Members for whom a jurisdiction or requirement does not apply can select "not applicable" and submit the declaration, but they still have to file.
What the NSE circular requires
NSE Circular No. 42/2026 (Download Ref. No. NSE/INSP/75505) dated 31 July 2026, issued by the Inspection Department, is titled "FATF Public statement on jurisdictions on call for action and increased monitoring - June 2026 Plenary". It refers to Exchange circular NSE/ISC/75328 dated 22 July 2026, which relayed the Financial Action Task Force (FATF) statements, and to the earlier circular NSE/INSP/73792 dated 17 April 2026.
All trading members must update the actions taken by them, in the prescribed format, in the FATF module. NSE fixed 21 August 2026 as the due date and told members to comply within the timeline "to avoid any penal charges/disciplinary actions" for non-submission or late submission.
How to file
The user manual in Annexure A of the circular sets out the route: Member Portal, then ENIT NEW COMPLIANCE, Compliance, FATF, Member Submission. There are two options:
- One-time declaration: for members doing proprietary trading only, where no data needs to be submitted.
- Data submission: for all other members. Select each applicable jurisdiction from the drop-down, download the Excel template, fill in client information without changing the original file name, and upload it. Repeat for every applicable jurisdiction, then click "Save and View Declaration".
The system then generates a PDF declaration. It must be digitally signed by the designated directors or the Compliance Officer and uploaded with the system-generated file name followed by "-signed.pdf". On successful submission, an acknowledgement goes to the compliance officer's email address.
The FATF statements behind the filing
In its statement of 19 June 2026, the FATF named three jurisdictions on its list of high-risk jurisdictions subject to a call for action:
| Jurisdiction | FATF call |
|---|---|
| Democratic People's Republic of Korea | Countermeasures, including terminating correspondent relationships with DPRK banks and limiting business relationships and transactions with DPRK persons |
| Iran | Countermeasures, including refusing new branches or subsidiaries of Iranian financial institutions and prohibiting new correspondent relationships |
| Myanmar | Enhanced due diligence proportionate to the risk; the FATF will consider countermeasures if there is no further progress by October 2026 |
The FATF's list of jurisdictions under increased monitoring as of 19 June 2026 has 22 names: Angola, Bolivia, Bosnia and Herzegovina, Bulgaria, Cameroon, Cote d'Ivoire, Democratic Republic of the Congo, Haiti, Iraq, Kenya, Kuwait, Lao PDR, Lebanon, Monaco, Nepal, Papua New Guinea, South Sudan, Syria, Venezuela, Vietnam, Virgin Islands (UK) and Yemen. Bosnia and Herzegovina and Iraq were added at the June plenary, while Algeria and Namibia were removed after completing their action plans.
What compliance teams should check
- Confirm the June 2026 plenary submission is complete in ENIT New Compliance, not just saved.
- Where no jurisdiction applies, make sure the "not applicable" declaration was actually submitted.
- For applicable jurisdictions, check that each client-data template was uploaded in the right format and sequence.
- Verify that the PDF was signed by a designated director or the Compliance Officer and uploaded with the correct file name.
- Keep the acknowledgement email as evidence, and refresh client screening against the updated FATF lists, since Bosnia and Herzegovina and Iraq are new to the increased monitoring list.
Updated on 27 September 2026: linked NSE Circular No. 42/2026 and the FATF statements of 19 June 2026, added the full increased-monitoring list with the June additions and removals, and the signed-file naming rule.
