Switching your mutual fund investments to a new broker using a Change of Broker (COB) request should ideally be smooth. But in some cases, even after the COB is completed, users on the Angel One platform notice that some mutual fund units are not visible, and they are unable to place withdrawal or switch requests.
This guide explains why that happens, when it happens, and what steps you need to take to resolve it.
Why You Might Not See Your Mutual Fund Portfolio After a Broker Transfer (COB)?
The Problem: Missing Portfolio or Blocked Withdrawals
Even after completing the COB to Angel One, some investors face the following issues:
- Certain mutual fund schemes are not visible in the app
- Withdrawal or switch options are disabled or result in an error
- In some cases, even after a switch is processed, the withdrawal remains blocked
These situations can be frustrating, especially when the COB appears to have gone through.
When Does This Happen?
These issues typically come up after the broker code has been successfully updated with the Registrar and Transfer Agent (RTA), but the following gaps exist:
- The mutual fund units are still lying in your old broker’s Demat account
- The app is expecting to find units in your Angel One Demat account, but they are not yet transferred
- You submitted a Delivery Instruction Slip (DIS) to transfer units, but did not complete the mandatory offline COB form, so the transfer was never executed
- The investment is actually held in physical mode, but was incorrectly treated as Demat, causing the system to look in the wrong place
How Does This Happen?
Let’s walk through a few real scenarios:
Case 1: Units Still in Old Brokers Demat (ICICI Example)
- The COB request was successfully processed, and the broker code was updated to Angel One
- However, the actual mutual fund units were not moved from your ICICI Demat account to Angel One
- As a result, when you try to initiate a transaction from the Angel One app, it fails due to absence of units in the target Demat account
Case 2: DIS Submitted but COB Form Not Submitted
This is a common oversight:
- The investor submits a DIS, assuming it’s sufficient for the transfer
- But the required offline COB form is not submitted to the Depository Participant
- Without this form, the unit transfer request is rejected, and the units stay with the old broker
- The Angel One platform cannot detect these units, and any transaction attempt fails
Case 3: Folio in Physical Mode Treated as Demat
- The COB was processed for a mutual fund scheme that was actually in Physical mode
- However, the folio was mistakenly interpreted as Demat mode
- The app tried to locate units in the Demat account, found nothing, and blocked the withdrawal request
- Once the holding type was correctly identified as Physical, transactions could proceed normally
What Should You Do?
Here is a clear path based on your situation:
If Units Are Still with the Previous Broker
- Submit a Delivery Instruction Slip (DIS)to initiate a transfer of units from your old broker’s Demat account to Angel One’s Demat account
- Make sure you also complete and submit the offline COB formrequired for processing the DIS
- Until both these steps are completed and the units appear in Angel One’s Demat, transactions like withdrawal or switch will not work
If the Investment Is in Physical Mode
- If the app does not allow withdrawal or shows units as unavailable, but you know the investment was not in Demat, it may be a classification issue
- In such cases, the holding type will need to be verified with the RTA
- Once confirmed to be Physical, the system will reflect this correctly, and you will be able to place a redemption request
Other Scenarios to Be Aware Of
Folio Is in Physical Mode but Treated as Demat
Incomplete or incorrect data from the RTA may cause folios to be wrongly identified. If this happens, the app expects to find units in the Demat account, and when it does not, blocks the transaction. Once the folio is correctly recognized as Physical, you can proceed with redemptions.
Units Not Transferred Despite COB Completion
A common misconception is that completing COB also transfers the units. In reality:
- COB only updates the broker code with the RTA
- The actual transfer of units requires a DIS
- And the DIS will only be processed if the offline COB form is also submitted
- Skipping any of these steps means your units remain with your previous broker, and Angel One will not show them in your portfolio.
Final Thoughts
Completing a COB request is an important first step, but it does not automatically move your mutual fund units. For your investments to show up correctly in Angel One and to enable transactions:
- Make sure the broker code is updated
- Submit both the DIS and the offline COB form
- Confirm that your folio is correctly classified as Demat or Physical
If you have already taken these steps and still face issues, our support team can help you trace the unit status, resolve classification errors, and guide you through any pending action.
Understanding these backend processes helps ensure your investments remain visible, accessible, and transactable without unnecessary delays.
FAQs
How does the user not see the portfolio / face the issue?
- The client is unable to place withdrawal requests for certain mutual fund schemes despite COB being completed to Angel One.
- The app throws error messages when the client tries to initiate SW or Withdrawal request.
- In some cases, SW was completed but the withdrawal option showing as disabled.
When does this arise?
- This issue typically occurs after the COB has been processed, but the units are still lying in the old broker’s Demat account (ICICI).
- It also arises when the Dion system shows folio as DP, but no units are available in Angel One Demat.
How does this arise?
Primary Scenario (ICICI Demat Account – 4 Schemes)
- COB was processed and broker code was updated to Angel One.
- However, units were not transferred from the client’s ICICI Demat account to Angel One Demat account.
- Since units are not held in Angel One Demat, any withdrawal or SW transaction from Angel One platform gets rejected due to absence of units.
Edge Case Scenario (Kotak Fund – Physical Mode Mismatch)
- COB processed for a Kotak scheme, but the folio was actually in Physical mode, not in Demat.
- However, in Dion, it was incorrectly marked as DP, so Spark app tried to treat it as a DP folio.
- Since there were no units in Angel One Demat, the client was unable to place the withdrawal request.
- Once the folio was corrected to Physical mode in Dion, the client was able to initiate the redemption successfully.
What action does the user need to take?
For Demat Mode Folios
Client must submit a DIS slip to initiate DP-to-DP transfer of units from ICICI Demat to Angel One Demat account.
Until the units reflect in Angel One’s Demat account, no transaction (Withdrawal/SW) will go through from Angel One platform.
For Incorrect DP Mapping (like Kotak MNC Fund)
If a folio is mistakenly marked as DP in Dion but is actually in Physical mode:
-
WMS OPS team will verify with RTA and check for unit availability in Angel Demat.
-
If no units found, update Dion mode to Physical, enabling the client to transact.
Any edge cases?
1. Folio is actually in Physical Mode but incorrectly marked as DP in the system
In some cases, DION may have marked a folio as Demat mode based on incomplete RTA data.
Example: In the Kotak fund case, the folio was in physical mode, but was mistakenly marked as DP in Dion.
Result: The system tries to fetch units from the Demat account (Angel One), finds nothing, and hence blocks for withdrawal.
Fix: Once the folio mode was corrected to Physical in the DION, the app allowed the client to proceed with withdrawal.
2. Units held in previous broker’s Demat account even after COB
COB (Change of Broker) updates only the broker code with the RTA, but does not move the actual units from the previous broker’s Demat account to Angel One’s Demat account.
Example: For ICICI Demat account, even after COB, units were not transferred to Angel Demat.
Result: Transactions initiated via Angel One fail, since the system doesn’t detect units under AngelOne’s DP.
Misconception: Clients assume COB also transfers the units – they may not be aware that a DIS needs to be submitted separately for actual DP transfer.