March 30, 2026
ChapmanAlbin is investigating Avinesh Shankar (CRD 6232970) after public records described alleged forged annuity applications, non-genuine customer signatures, and commissions he was allegedly not entitled to receive. The main public record investors should understand is a March 2026 FINRA settlement order imposing a permanent bar. Shankar’s most recent reported firm was Pruco Securities, LLC. This page is based on public records, including FINRA BrokerCheck and regulatory documents, and explains the key allegations in plain English for investors reviewing their options.
CRD: 6232970
Most recent firm: Pruco Securities, LLC.
Primary concern: Alleged forged annuity applications, unearned commissions, and a FINRA bar.
Products mentioned in public records: Variable annuities and fixed annuities.
Potential investor claim themes: Fraud and Misappropriation, Failure to Supervise, and unauthorized paperwork or signature issues.
The public records describe allegations that between late 2022 and early 2024, Shankar signed customer names on 115 annuity applications without permission and submitted those applications without the customers’ knowledge. The records say the applications involved 64 customers and that the annuities were never funded. Even so, the firm allegedly advanced more than $511,000 in commissions tied to those applications.
BrokerCheck reflects a pending FINRA regulatory matter and a FINRA investigation, while the separately provided settlement order shows that FINRA accepted an offer of settlement and barred Shankar from associating with any FINRA member in any capacity. Public records also show that Pruco discharged him after alleging that numerous annuity applications contained inaccurate information and non-genuine electronic customer signatures.
Forged signatures and unauthorized application activity can matter even when a product was never ultimately funded. Investors may still need to understand whether personal information was used without permission, whether account paperwork was altered or submitted without clear authorization, and whether the firm’s supervision should have caught a pattern sooner. These facts can also raise questions about compensation incentives, documentation practices, and whether a broader compliance breakdown occurred.
The records reference both variable annuities and fixed annuity applications. Annuities can be complex products, and investors should be wary when paperwork is rushed, signatures are handled electronically without a clear review process, or the sales process feels more focused on commissions than on the investor’s actual goals.
If you worked with Avinesh Shankar and do not recognize annuity paperwork, application activity, or electronic signatures connected to your account, gather your records and compare them carefully against what you remember authorizing. Depending on the facts, an investor claim may involve the broker, the supervising firm, or both. ChapmanAlbin can help review the timeline, identify missing documents, and assess whether the facts support a recovery claim.
A FINRA bar means the individual is prohibited from associating with FINRA member firms. For investors, it is a strong signal to review account records, applications, and communications carefully.
It still matters because the public records allege that customer information and signatures were used without permission and that commissions were advanced anyway. Investors may still have questions about authorization, privacy, and firm supervision.
Not necessarily. But forged signatures are serious because they can show that paperwork was submitted without proper authorization. The exact investor harm can vary from case to case.
Yes. Depending on the facts, investors may look at whether the firm reasonably supervised application activity, electronic signatures, compensation practices, and follow-up on unfunded annuities.
This page is for informational purposes only and is not legal advice. Past outcomes are not a guarantee of future results. Every matter depends on its own facts and should be evaluated individually.
"*" indicates required fields