A practical FLA-return workflow covering applicability, 15 July filing, provisional figures, valuation, reconciliation and revised submission.
The FLA return is a balance-sheet disclosure to RBI, not an income-tax return or an MCA annual form. A company can have no fresh foreign transaction in the year and still remain within the filing requirement because an outstanding foreign liability or asset continues.
The annual FLA return applies to Indian companies, LLPs and other covered entities that have received foreign direct investment or made overseas direct investment and have outstanding positions at the reporting date.
The normal filing date is 15 July for positions as at 31 March.
If audited accounts are unavailable by the due date, the RBI framework permits filing from unaudited or provisional figures followed by a revised return after audit within the prescribed revision process.
Foreign liabilities and assets are classified and valued under the return instructions; share capital, reserves, debt, trade credit and overseas investment should not be combined casually.
| Check | What to examine |
|---|---|
| Applicability | Outstanding foreign liability or overseas asset at 31 March, including earlier-year investment. |
| Entity details | CIN/LLPIN, contact, financial year and FLAIR registration. |
| Balance sheet | Paid-up capital, reserves, debt, trade credit and retained earnings. |
| Counterparty | Country, direct investor relationship and percentage ownership. |
| Reconciliation | FC-GPR/FC-TRS, APR, bank records, cap table and audited accounts. |
A startup received foreign investment three years ago and had no new inflow this year. The investor still owns 18% on 31 March. The company cannot skip FLA merely because no transaction occurred during the year; the outstanding foreign liability remains reportable.
Build the FLA workbook before the statutory audit closes. Start from the previous return, roll forward share issuances, transfers, conversions, dividends and valuation movements, and then reconcile the closing cap table. For overseas subsidiaries, use the entity-wise investment and financial information that also supports ODI reporting.
Do not wait for 14 July to resolve portal access. Confirm the authorised user, email and entity registration early. Where the audited numbers later change the reported figures, preserve both submissions and the audit bridge rather than overwriting the original evidence.
Prepare a written status and transaction note. Identify the person or entity, tax residence, FEMA residence, source of funds, beneficial owner, counterparty, purpose and the official form or bank route. Review applicability, entity details and balance sheet together. A bank account label, portal dropdown or adviser email should not be treated as the governing rule.
Reconcile the bank entry to the contract, form, asset or expense and preserve the official acknowledgement. Confirm that the same names, amounts, dates, currency and ownership appear in the tax return, FEMA report, demat or folio statement and financial statements where relevant. Correct discrepancies while the counterparty and bank can still reproduce the records.
At each year end, update the travel and residence memo, foreign-asset register, remittance register, tax-credit file and regulatory filing calendar. Review nominees, authorised signatories, tax IDs and portal access. A cross-border position should remain understandable to a successor professional without relying on the memory of the person who executed it.
Cross-border compliance is strongest when legal status, banking route, beneficial ownership, tax treatment and official reporting all tell the same story. Do not move money first and design the explanation later.
Use the current official instrument, portal or regulator publication before acting. This panel separates the category authority from page-specific references.