Ek Anjali Associate logo
Ek Anjali AssociateAccounting, Taxation, Digital & Business ServicesPowered by MK ENGINE™
HomeServicesContactLogin

KYC / AML

KYC Policy

KYC framework for client/agent onboarding and authorised partner workflows.

Draft for legal and partner review. This policy is prepared as a commercial website foundation. Where a regulated bank, BBPS, DMT, payment, insurance, forex or other licensed partner is involved, that partner’s applicable terms, KYC/AML requirements and regulatory obligations will prevail.

1. Purpose

KYC is used to establish identity, reduce fraud and support the customer-due-diligence requirements of regulated or authorised partners where applicable. Ek Anjali Associate will not represent itself as an RBI-regulated entity merely because it collects documents for an authorised partner workflow.

2. Information and Documents

Depending on the service and customer type, the workflow may request PAN, mobile/email verification, address proof, photograph, business proof, authorised-signatory details, beneficial-owner information and an accepted Officially Valid Document. Aadhaar use must follow the applicable legal/partner method and should not be collected unnecessarily.

3. Risk and Enhanced Checks

Higher-risk or regulated transactions may require additional verification, source/purpose information, beneficial-owner checks, sanctions/PEP screening by the authorised partner, transaction limits, manual review or rejection. The partner’s KYC/AML rules prevail for DMT/BBPS/payment/financial workflows.

4. Document Security

KYC files must not be placed in public folders or browser localStorage. Production upload will use an authenticated server endpoint, access controls, audit logging, file-type/size checks, malware scanning where available, and encrypted/protected storage. Agents should only access KYC records necessary for assigned work.

5. Verification and Updates

Users must keep details current and may be asked to refresh KYC where required by law, risk review or the authorised partner. A submitted document is not treated as verified until the applicable verification process is completed.

6. Rejection / Hold

KYC or a transaction may be placed on hold or rejected for mismatch, expired/unclear documents, suspected tampering, fraud indicators, sanctions/provider restrictions, incomplete information or legal/regulatory reasons.