Documents and Records to Organize When Your Bank Account Is Restricted
Build a usable record of what you know, what you possess, what the bank requested and what you actually intend to submit.
Account Freeze Navigator · Updated 10 October 2026
Make an inventory before assembling a submission
This is a suggested record-keeping structure, not a universal list of documents required by law or by every bank. Start with what you actually know and possess. Add a bank requirement only when it appears in the bank’s request; an empty folder is not evidence that a document is legally mandatory.
| Part | What to keep distinct |
|---|---|
| Part:Restriction information | What to keep distinct:Reported reason, date, authority state, instruction or complaint reference, disputed amount and the source of each detail. Use a separate entry for each restriction. |
| Part:Transaction record | What to keep distinct:Payment date, actual amount, counterparty as shown, payment reference and your description. Keep a sale price or expected payment separate from money actually received. |
| Part:Correspondence | What to keep distinct:What you sent, when, to whom and through which channel; the actual reply and any acknowledgement. An unknown reply status stays unknown. |
| Part:Documents possessed | What to keep distinct:A short label, the record it relates to and whether you have it. Do not mark a requested document as in hand merely because it appears on a request list. |
| Part:Bank request | What to keep distinct:The request date, channel, reference if known, wording and specific items requested. Preserve a phone request as a phone request. |
| Part:This submission | What to keep distinct:The specific documents selected to accompany this cover note, followed separately by what you actually sent and any receipt. |
A simple filename or local label can help you locate an item. Keep that label visibly separate from a reference issued by a bank, payment system or authority.
Worked example: five amounts, with different meanings
| Amount | Meaning in this fictional example |
|---|---|
| Amount:₹86,500 | Meaning in this fictional example:Account-level amount Aarav recorded as inaccessible. |
| Amount:₹4,000 disputed | Meaning in this fictional example:The amount the branch identified for the reported Karnataka restriction. |
| Amount:₹4,000 received | Meaning in this fictional example:The UPI payment received on 3 September 2026 for a used monitor. It happens to equal the disputed figure; it remains a separate transaction fact. |
| Amount:₹12,000 agreed price | Meaning in this fictional example:The recorded price of the monitor, not the amount received. |
| Amount:₹8,000 not received | Meaning in this fictional example:The remaining price in this example. It is not an additional receipt, a refund or a bank-confirmed disputed amount. |
The payment date is 3 September. Outgoing payments stopped on 18 September, and Aarav recorded the branch’s explanation from a visit on 19 September. Do not give all three events the same date. The example records that the monitor was not shipped and the ₹4,000 was not refunded; those statements are example facts, not advice about what someone else should do.
The figures do not establish how much must be released or who is liable. If an amount is unknown in your own records, retain that uncertainty instead of copying the sample or inserting zero.
One document can have three different statuses
| Document | Requested | In hand | Selected here |
|---|---|---|---|
| Document:Signed explanation of the ₹4,000 payment | Requested:Yes | In hand:Yes | Selected here:Yes |
| Document:UPI payment record for 3 September | Requested:Yes | In hand:Yes | Selected here:Yes |
| Document:Bank statement | Requested:Not in this recorded request | In hand:Yes | Selected here:No |
| Document:Used-monitor messages | Requested:Not in this recorded request | In hand:Yes | Selected here:No |
All four items are recorded as possessed, but only two are selected for the sample submission. A cover note must not call the other two enclosures. The corrected cover-letter example shows the resulting list.
Keep the record useful as replies arrive
Retain the original message or document and use a separate working note for your summary. Mark the source and actual date beside an update. If a later reply corrects a figure or reference, preserve the earlier communication so the sequence remains understandable.
Before sharing a working copy, check which identifiers and attachments the verified recipient needs. A public example or a message asking someone to explain a label need not expose a full statement. The record you keep of a submission should identify what was actually sent, not merely what was available in your folder.
For a reply, use the communication-log and follow-up guide. For several reported complaints or instructions, the multiple-restriction register keeps updates from being assigned to the wrong entry.