The year, not the transfer

The threshold is cumulative over the financial year and not per transfer. A reader who sends money twice can cross the threshold without noticing, because the bank adds up all remittances in the year and the collection begins on the rupee that crosses it.

Two transfers can cross a line neither one reaches

The same year, counted in dollars: what was sent against what was left to invest.

Read at: 12.11.2026 14:25

The threshold is for the year

The threshold applies to the financial year as a whole, not to each transfer. A reader who sends a small amount in April and another in May may cross the threshold in May, even though neither transfer alone would have crossed it.

The bank adds up all remittances in the year, and the collection begins on the rupee that crosses the threshold. The second transfer may be partly or wholly above the threshold, and the collection is calculated on the part above it.

Two transfers can cross it

Two modest transfers can cross the threshold when neither would alone. A reader who sends half the threshold in one month and half again in the next has crossed the threshold, and the collection begins on the second transfer.

The collection is not on the whole second transfer; it is on the part that exceeds the threshold. But the reader may be surprised, because each transfer looked small and the threshold seemed far away.

The same year, counted in dollars

The table above shows the same ladder in dollars: what was sent and what was left to invest. One column is the year's total remittance; another is the amount collected; a third is the amount that reaches the account abroad.

The table is built on the year's total rather than on one remittance, because the threshold is cumulative. A reader who has sent earlier money must add it to the table's rows to see the collection on the next transfer.

The collection begins on the rupee

The collection begins on the rupee that crosses the threshold, not on the transfer that contains it. A reader who sends an amount just over the threshold will have a small collection, not a collection on the whole transfer.

The fixed share applies only to the part above the threshold. The part under the threshold is never collected, no matter how many transfers it took to reach it.

Across purposes, not just shares

The threshold is cumulative across purposes. Money sent for a share, a fund, a foreign account, or any other purpose under the scheme all counts towards the same yearly threshold. A reader who sends money for two different purposes may cross the threshold without realising it.

The bank does not reset the threshold for a different purpose, and the collection is the same. The reader should keep a running total of all remittances in the year.

What a reader should track

A reader should track the year's total remittances, not the individual transfers. The bank will ask for the purpose of each transfer, but the threshold is on the total. A reader who loses track may be surprised by the collection on a later transfer.

The financial year runs from April to March, not the calendar year. A reader who thinks in calendar years may cross the threshold in January and again in April, because the year resets in April.

The bank counts what you have sent, not what you remember

A reader who sends money for a child's tuition in April and then for a US brokerage account in September may think of them as separate events. The bank does not. Its system adds every outward remittance under the scheme for the same person across the financial year, whatever the stated purpose. The threshold is not a per-purpose allowance, and no fresh start is given because the second transfer is labelled differently on the form.

The practical consequence is that the second transfer can be taxed at source even when the first was small and the reader believed the limit was far away. The collection happens at the bank's counter before the money moves, so the reader learns of it only when the debit is larger than expected. By then the transfer is already in motion and the amount withheld is no longer under the reader's control.

What makes this hard to track is that the bank's own records are not visible to the reader in real time. A person may keep a mental note of what was sent, but the bank's cumulative figure is what decides the collection. A reader who wants to avoid an unwelcome surprise must ask the bank for the year-to-date remittance before authorising a new one, not after the amount is frozen.

A transfer made in March can be more expensive than the same transfer in April

The financial year ends on the last day of March, and the counter resets the next morning. A reader who sends money in late March has already accumulated all the remittances since the previous April, so the share above the threshold may be large. The same amount sent a week later, in early April, starts the new year with the counter at zero and may attract no collection at all.

This timing effect is not a matter of tax planning but of cash flow. The money collected in March will be credited back only when the return for that financial year is filed and processed, which can be many months later. The same sum sent in April, if it stays below the threshold, leaves the reader's account in full and is never held by the government.

The difference is not in the exchange rate or the investment but in the calendar. A reader who can choose the date of a remittance should know which side of the year-end it falls on. The bank will not advise on this, because the collection is not the bank's cost and the timing is the reader's own decision. The desk does not suggest timing the market; it notes that timing the year is arithmetic.

The second transfer can cross the line even when the first was below it

A reader who sends a small amount in July, well below the yearly threshold, may assume the limit is still mostly available. Then a larger amount in January pushes the combined total over the line. The collection applies to the portion above the threshold on the January transfer, not to the July transfer, which was legal and untaxed at the time.

This is the most common way a reader is caught: not by a single large remittance that obviously crosses the threshold, but by the accumulation of ordinary amounts. The bank's system does not warn before the second transfer that the threshold has been crossed; it simply collects the fifth on the excess and shows the debit. The reader's own calculation is the only safeguard.

The arithmetic is not complicated, but it requires the reader to know the total sent so far in the financial year. That total includes every remittance under the scheme, whether for shares, education, travel, or a gift. A reader who keeps a running total in a note on their phone is better placed than one who relies on memory, because the bank's counter is the one that decides what is collected.

The threshold does not reset when the purpose changes

The scheme does not ask what the money is for. It asks only how much has left the country in the reader's name during the financial year. A transfer for a US share purchase and a transfer for a relative's hospital bill are added together. The bank does not separate them into different buckets, because the law does not.

This means a reader cannot avoid the collection by labelling a remittance as something other than an investment. The form may ask for a purpose code, but that code does not change the cumulative total. A transfer for travel in October can push a share purchase in February over the threshold, even though the share purchase was the only one the reader thought of as part of the investment.

The practical consequence is that a reader who remits for multiple purposes must track them all as one number. A household with two earners who each remit under the scheme must track each person's own total, because the threshold is per person, not per family. The bank will not consolidate across family members, and the reader should not assume it will.

The bank's counter is the only one that matters, and it is invisible

A reader may have a spreadsheet with every transfer, the date, the amount, and the purpose. That spreadsheet is useful, but it is not the record the bank uses. The bank's own system keeps a running total for the financial year, and that total is what triggers the collection on the next transfer. The reader cannot see that total unless they ask.

The bank is not required to show the year-to-date remittance before a new transfer is authorised. The reader can ask for it, and the bank may provide it, but the request must be made before the transfer is booked. Once the transfer is authorised, the collection is already calculated and the reader's chance to adjust the amount is gone.

The invisibility of the counter is a failure mode, not a design flaw the desk is criticising. It simply is. A reader who wants to stay below the threshold must ask the bank for the cumulative figure each time, or maintain their own total and assume the bank's matches. If the two differ, the bank's figure wins, and the reader's own record is only a check.

A transfer that is reversed still counts toward the threshold

If a remittance is sent and then returned by the receiving bank, the reader may think the amount is no longer part of the year's total. The scheme's rules do not work that way. The outward transfer was made, and the threshold is based on the amount sent, not the amount that ultimately stayed abroad. The collection, if any, was already made at the time of the original transfer.

The reversal of the funds does not automatically reverse the collection. The reader must claim the credit when filing the return, just as if the transfer had succeeded. The bank will not refund the collected amount at the time of reversal, because the collection is with the government, not the bank. The reader's own money is still frozen until the return is processed.

This is a practical consequence that few readers anticipate. A failed transfer, a wrong account number, or a rejected payment can still reduce the reader's available threshold for the rest of the financial year. The desk does not advise avoiding transfers for fear of reversal, but it does advise readers to know that the counter does not move backward.