Schedule FA example: Table A2 and A3, filled in

Below is a complete Schedule FA report for a sample Interactive Brokers account — the statement that went in, the tables that came out, and the exchange rate behind every rupee figure. Nothing here is a mock-up: it was produced by running the sample file through this tool.

The button generates the report live, in your browser, from the sample statement — the same code path your own file goes through. You can print it or save it as a PDF from there. Prefer to run it yourself? Download the sample statement (XML) and drop it into the generator; historical prices and published rates do not change, so you will get exactly the figures below.

The account in the sample

A fictional resident individual, Aarav Sharma, holding two US securities through Interactive Brokers LLC during calendar year 2025:

• Apple Inc. (AAPL) — 100 shares carried in from March 2024, 50 more bought in the April 2025 dip at $172.42, and 30 sold in September at $236.70. Year-end holding: 120 shares, across two tax lots.
• Vanguard S&P 500 ETF (VOO) — 20 shares bought once in February 2025 at $556.15 and held to the year end.
• Four Apple dividends and two VOO dividends, each with 25% US tax withheld, plus $18.40 of broker interest and $8,973.60 of cash sitting in the account on 31 December.
• Every recommended Flex section is enabled, including Cash Report and NAV in Base — so the account peak comes from IBKR's own daily balance rather than being reconstructed, and the tool can check its arithmetic against it.

The share prices are the real closing prices for those dates. The account number, name and address are invented.

Table A2 — Foreign Custodial Account

One row for the broker account itself. This is where the account peak and closing balances go, not the individual securities.

What the report says about these figures — verbatim: peak balance is the account's true daily maximum on 2025-12-03, including cash, taken from IBKR's own daily NAV; closing balance includes ₹8,02,867.99 of cash; gross credited includes ₹1,622.88 of interest (1 credit); cross-checked against IBKR's own daily valuation: the peak and closing dates agree within 0.00%.

That last clause is the part worth pausing on. The tool values your holdings independently, from daily market prices and daily exchange rates, and then compares its own answer against the balance your broker recorded on the same day. Here the two agree exactly. A wrong ticker, a stale price series or a listing quoted in the wrong currency would show up as a percentage gap, and the report would say so instead of quietly reporting a plausible-looking wrong number.

Table A3 — Foreign Equity and Debt Interest

One row per security held at any point in the year — including anything sold before 31 December, which is why the Apple row shows sale proceeds and the closing value still stands.

All figures in INR. Nothing is flagged for review here because both issuers' addresses are known. When an address is missing the tool flags the row rather than inventing one — Schedule FA requires it, and a confidently wrong address is worse than a blank you can see.

Reading the Apple row

Acquired 2024-03-12 is the earliest lot still held, not the 2025 purchase — the date the interest was first acquired. Initial value is the cost of every lot, each converted at the rate on its own acquisition date, which is why a share bought in 2024 and one bought in 2025 contribute at different rates.

Sale proceeds of ₹6,23,822.85 come from the 30 shares sold in September, converted at that day's rate. The shares sold still appear in this table because they were held during the year.

Why the account peak is not the sum of the security peaks

This sample demonstrates the point precisely. The two securities hit their highs three months apart, and the account hit its own high on a third date:

Adding the two individual highs gives ₹42,94,963.92 — but that is a portfolio that never existed, because Apple peaked in September and VOO peaked three months later. No single day in 2025 saw both at their best. A tool that reports the sum is reporting a balance you never held.

The A2 figure above is a different thing entirely: a real end-of-day account balance that IBKR itself recorded on 3 December, cash included. That is why it is larger than the sum here — the account was carrying roughly ₹8 lakh of cash — and why it is the defensible number to file.

How the peak value is worked out

This is the figure people most often get wrong, and the reason is currency. The tool rebuilds your holding for every day of the year, values it at that day's closing price, converts at that day's SBI TT buying rate, and takes the maximum in rupees.

Maximising in rupees is not the same as maximising in dollars. The rupee moves independently of the share price, so the highest dollar value and the highest rupee value routinely fall on different dates — and it is the rupee figure that goes on the return. A tool that takes the dollar high and converts it, or that simply uses the 31 December value, will report the wrong number.

The audit trail

Every rupee figure in the report is backed by the source amount, the exact rate applied, and the date that rate was published. This is what makes a figure defensible if it is ever questioned:

This is the complete audit trail for the Apple entry, exactly as the report prints it. Note the two initial-value lines: the 2024 lot converts at 82.33 and the 2025 lot at 85.70, because each is valued at the rate on its own acquisition date.

Reconciliation

The A3 closing total (₹40,40,984.13) is lower than the A2 closing balance (₹48,43,852.12) by exactly the ₹8,02,867.99 of cash. Securities belong in A3; the account balance, cash included, belongs in A2. If your A2 closing figure equals the sum of your A3 rows, your cash has gone missing.

Where the exchange rate comes from

Schedule FA is converted at the SBI TT buying rate for the relevant date. SBI does not publish on weekends, holidays, or occasionally at all — so when a rate is missing for a valuation date, the nearest preceding published day is used, and the report records which date it actually used. You can see that in the audit trail above: the rate date is shown next to every figure rather than assumed.

The calendar-year trap

Schedule FA runs on the calendar year — 1 January to 31 December — not the April-to-March financial year the rest of your return uses. For the return you file in 2026 (AY 2026-27), the Schedule FA period is calendar year 2025. Exporting an April-to-March statement is the single most common mistake, and the figures it produces will be wrong in a way that is hard to spot. This tool takes the year as an explicit input and constrains every record to it.

Try it with your own statement

Your statement is parsed in your own browser — it is never uploaded. Only ticker symbols are sent out, to fetch public exchange rates and share prices.

Not tax advice. This example is illustrative. The output of the tool is a working draft to verify — ideally with a chartered accountant — before filing. You remain responsible for what you file.