How do you check whether a mutual-fund SWP or STP happened correctly? Do not compare only the scheduled amount with a bank credit. First identify the instruction, then reconcile the source folio, applicable NAV date, units debited, destination details and the official transaction record. An SWP is a scheduled redemption process ; an STP is a scheduled switch or transfer process whose exact operation depends on the current scheme documents and servicing route.
Direct answer : Keep the original registration acknowledgement, frequency, dates, amount or units, source scheme and destination details. For each instalment, compare the official transaction record with the applicable NAV, units debited or credited, proceeds or destination entry, and bank posting where relevant. A schedule is an instruction record, not proof that every instalment completed.
Reviewed by GFS Research Desk.
Why a schedule is not the same as a completed transaction
Households often store one confirmation email and assume it explains every future instalment. It does not. A standing instruction can have a registration date, start date, end date, frequency, amount or unit field, source scheme, destination scheme or bank details, and a status. Each later instalment creates an event record. That event may be processed, rejected, skipped, reversed, pending or posted differently across the systems involved.
In an SWP, units are redeemed from the source scheme under the applicable transaction terms and proceeds are paid to the registered bank account. In an STP, an amount or units may be transferred from a source scheme to a destination scheme through a switch-like scheduled process. The current Scheme Information Document (SID), Key Information Memorandum (KIM), addenda and the servicing route define the exact mechanics. This article explains a checking method, not which facility or scheme a household should use.
This draft was checked on 26 July 2026. Interfaces, cut-off provisions, holidays, forms, bank-validation steps and scheme terms can change. For a live instruction, use the current official document and the exact confirmation issued by the responsible AMC, registrar or authorised servicing route.
The six records to keep together
Create a private folder for the instruction, with masked identifiers in ordinary notes. Keep these six records separate:
- Registration record: acknowledgement or form showing the facility, date, source scheme and instruction terms.
- Schedule: start and end dates, frequency, amount or units, and any stated instalment count.
- Source record: source folio, plan, option and units or balance before the event, as shown by the official statement.
- Event record: instalment date, transaction type, applicable NAV, units redeemed or switched, amount and status.
- Destination record: bank credit for an SWP, or destination-scheme transaction row for an STP.
- Exception record: failed, skipped, cancelled, rejected, reversed or amended event, plus the official ticket.
Do not merge these into one invented “transaction date.” The registration date proves that an instruction was accepted for setup. It does not prove that an individual instalment was completed. A bank credit proves money reached an account, subject to the bank record’s description; it does not by itself prove the NAV or units used. A destination entry can show that a transfer was recorded, but it does not replace the source-side event record.
SWP: trace amount, units and proceeds separately
A scheduled withdrawal creates a particularly important distinction: the requested amount and the number of units redeemed are not necessarily the same kind of field. If the instruction is amount-based, the transaction record may show the amount and the units calculated using the applicable NAV. If the instruction is unit-based, the proceeds are derived from the units and applicable NAV, subject to the terms and any applicable charges or adjustments stated in the current documents.
Use this neutral reconciliation table for each instalment:
| Question | Evidence to locate | If missing |
|---|---|---|
| Was the facility registered? | Official registration acknowledgement | Ask for setup status |
| Was this instalment due? | Schedule and calendar | Mark “not established” |
| What NAV was applied? | Official transaction row or statement | Do not infer from a chart |
| How many units changed? | Source folio transaction row | Request transaction detail |
| What amount was paid? | Transaction record and bank statement | Reconcile the references |
| Was it completed or rejected? | Status and official ticket | Treat as pending/unknown |
The amount can differ from a household’s expectation because the event may use a different applicable NAV date, a non-processing day, or a transaction condition stated in the documents. This is not a conclusion about any specific facility. It is a reason to read the official record rather than calculate backward from a bank credit alone.
STP: follow both legs, not just the destination
For an STP, build two linked rows for each instalment: the source-side debit or switch-out and the destination-side purchase or switch-in. Note the source scheme, destination scheme, plan and option exactly as shown. Keep the source and destination transaction references if the system provides them.
A destination holding appearing later does not answer every question. It may not show when the source request was received, which NAV was applied to the source leg, whether the instruction was processed on a holiday-adjusted date, or whether the two legs use separate records. Read the current SID, KIM, addenda and transaction confirmation together. If the service route displays only a summary, request the detailed official statement or ticket instead of filling gaps with assumptions.
Do not treat an STP as a guarantee that one destination value will offset a source movement. Units, NAVs and market values are separate concepts. The facility’s operational path can be documented; future outcomes cannot be promised.
A seven-step household audit
1. Freeze the original instruction
Save the confirmation PDF or email and write down when it was received. Preserve the frequency, dates, amount or units and source/destination names. Mask PAN, folio numbers, bank details and authentication information when sharing an ordinary working copy.
2. Mark the due event
Make a simple calendar row for each expected instalment. Label it “due,” not “completed.” This prevents a missed or rejected event from disappearing inside an automated schedule.
3. Retrieve the official event record
Use the AMC, registrar, recognised consolidated statement or another official authenticated servicing route. Record the transaction date, applicable NAV, units, amount, destination and status as displayed. Do not turn a blank or pending field into zero.
4. Match the source leg
For SWP, compare the source units before and after the event. For STP, identify the switch-out or source-side row. Preserve the scheme identity and plan/option wording. If the source record does not contain the expected row, ask for an official ticket.
5. Match the money or destination leg
For SWP, compare the official proceeds with the bank’s posting date and reference. For STP, match the destination transaction row to the same scheduled event. Different dates can be normal operational fields; they should be explained, not silently collapsed.
6. Classify exceptions
Use four labels: completed, pending, rejected/skipped, or unclear. “I did not see it” is not the same as “rejected.” Seek the exact status wording and reason from the official route. Do not create a duplicate instruction merely to test what happened.
7. Ask one narrow question
A useful query includes the masked reference, scheduled date, facility, source scheme and the missing field: “Please confirm the status, applicable NAV date, units and transaction reference for the instalment scheduled on [date].” Use secure channels for full identifiers. Keep the ticket with the event record.
What the interaction teaches—and cannot decide
Use the accompanying checklist to choose the record you are trying to reconcile: registration, SWP event, STP source leg, STP destination leg or bank posting. It will show the next document to retrieve. It cannot determine whether a real transaction is correct, access an account, calculate a future value, or establish suitability. Those questions belong to the official record and, where needed, a qualified professional’s separately governed process.
FAQs
Ques : Is an SWP just a monthly bank transfer?
Ans : No. The facility involves a scheduled redemption from a mutual-fund holding and a payment to the registered bank account. Keep the fund transaction record and bank record together; one does not replace the other.
Ques : Does an STP guarantee the same date for both schemes?
Ans : Do not assume that. The source and destination legs may be represented as separate transaction records and can have their own processing conditions. Check the current scheme documents and confirmation.
Ques : What if the bank credit arrived but the statement is missing?
Ans : Record the bank reference and date, label the fund event unconfirmed, and obtain the official transaction statement or ticket. A credit alone does not establish the NAV or units.
Ques : Can I rely on the original SWP or STP email for all instalments?
Ans : Use it to prove the registered terms, not each completed event. Retrieve the individual official record for every instalment you need to reconcile.
Ques : What should a household do when an instalment is rejected?
Ans : Preserve the rejection wording, avoid duplicating the instruction without understanding the cause, and ask the responsible official servicing route what status and next document apply. Do not share OTPs or passwords in ordinary correspondence.
Ques : Is this a calculation tool for deciding whether to start an SWP or STP?
Ans : No. It is an operational document checklist. It does not compare schemes, forecast returns, prescribe withdrawals or decide whether a facility suits a household.
Disclaimer:
This is written for educational and informational purposes only. Nothing here constitutes investment advice or a recommendation to buy or sell securities. All data is sourced from publicly available information. Investments in securities markets are subject to market risks — please read all offer documents carefully before investing.