Threshold Transactions Reporting (TTR) - Nepal

              Threshold Transactions Reporting (TTR) 

Definitions:

TTR : It stands for Threshold Transactions Reporting.

TTR is a report that financial institutions and Designated Non-Financial Businesses and Professions are required to file to FIU-Nepal for :
  • Deposit,
  • Withdrawal,
  • Exchange of currency,
  • Other payment or transfer;
if it exceeds prescribed threshold limit Provided by FIU-Nepal.

 Reporting Thresholds for Reporting Entities

The regulators of REs have designated different threshold limits as stated in their AML/CFT directives.

The designated thresholds for REs have been categorized into;

1) Bank and Financial Institutions – 5 Regulators
2) Other Reporting Entities. – 6 Regulators

Threshold :- Bank and Financial Institutions

Currently, the designated thresholds for Bank and Financial Institutions in Nepal are as follows by the regulatory NBR ( Nepal Rastra Bank):
  • Cash deposit or withdrawal of more than Rs. 1 million in one transaction –> TTR-Cash
  • Withdrawal of more than Rs. 1 million in one transaction  -> TAR-Withdrawl
  • Multiple of transactions in one day in single account.
  • Cross border electronic or other transfer of more than Rs. 1 million by a customer in single or in a series of transactions in one day. ->TTR Cross Border
  • Exchange of foreign currency equivalent to Rs 5,00,000/- or more by a customer in one transaction or in a series of transactions in one day. ->TTR FCY
        Nepal Rastra Bank is the Regulators for all the available Banks and Financial Institutions in Nepal.


Location: Kathmandu 44600, Nepal

Comments

Post a Comment

Popular posts from this blog

How do you stay curious about product details as a project manager

How do you stay curious about product details as a project manager? Interview question asked in Infosys? Staying curious about product details as a project manager isn’t just helpful — it's often the secret to bridging the gap between vision and execution. Here’s how experienced PMs keep that curiosity alive and useful: How to Stay Curious About Product Details as a PM. 1. Ask “Why” Like a Newbie — Even When You’re Not > Don’t just manage tasks — ask why that feature matters, who it’s for, and what happens if it’s removed. “Why did we pick this flow?” “Why does this feature need to launch in Phase 1?” This opens up dialogue with devs, designers, and users — and reveals assumptions you may need to challenge. 2. Join Customer Support Channels or Feedback Loops Sit in on support calls or read user feedback in tools like Zendesk, Intercom, Reddit, or app reviews. Curiosity grows when you see the product through users’ eyes. > Real users ask the best questions — and t...
Read more

Interview as a Requirements Gathering Technique: A Business Analyst's Perspective

Interview as a Requirements Gathering Technique: A Business Analyst's Perspective Requirements gathering is a crucial phase in any project, as it lays the foundation for developing solutions that meet business and user needs. One of the most effective techniques for eliciting requirements is conducting interviews with stakeholders. This technique allows Business Analysts (BAs) to obtain detailed insights, clarify ambiguities, and understand business goals directly from key individuals. Interview as a Requirements Gathering Technique An interview is a structured conversation between the Business Analyst and stakeholders to extract necessary information regarding project requirements. It can be formal or informal, depending on the project's scope and complexity. Types of Interviews Structured Interviews – These follow a predefined set of questions to ensure consistency in data collection. Unstructured Interviews – These are open-ended and flexible, allowing for free discuss...
Read more