Foreign Investment Reporting: FC-GPR and FLA

Quick View

Why It Matters

Before receiving funds, verify investor residence, instrument, sector, entry route, pricing, beneficial ownership and company authority.

After lawful receipt and allotment, the company should complete applicable RBI reporting such as FC-GPR through the current reporting system and authorised dealer process.

RBI’s FLA FAQ updated on 25 March 2026 requires applicable resident entities with outstanding FDI or ODI to file the annual return by 15 July, using audited or provisional figures and later revision when needed.

Control Framework

Action Checklist

1. Create an FDI transaction checklist.
2. Pre-clear documents with the AD bank.
3. Reconcile inward remittance and allotment.
4. File event-based reporting promptly.
5. Prepare FLA from entity and counterparty data.
6. Track late-submission or compounding remedies.

Practical Example

Evidence to Keep

• Investor and beneficial-owner documents.
• Valuation and pricing support.
• Bank remittance evidence.
• Allotment approvals and filings.
• FC-GPR acknowledgement.
• FLA working and submission.

Warning Signs

Management Decision

Maintain one FEMA register for every inward investment, share transfer, downstream investment and annual return.

Where delay or contravention exists, complete pending compliance and obtain advice on late submission or compounding rather than hiding the event.

Record the decision, owner, due date and evidence expected. A verbal explanation should become an approved working, board note, contract amendment, statutory filing or reconciliation before the item is treated as closed.

Rules, forms, thresholds and procedures can change. Use the latest official source and the actual company facts rather than copying a prior-year control or another entity’s legal position.

Exception Review

Classify every exception as a timing difference, data error, missing document, legal non-compliance, control-design gap or control-operating failure. This prevents management from treating fundamentally different problems as one ageing list.

The exception file should show amount or exposure, root cause, immediate correction, preventive action, owner and board-escalation threshold. Repeated low-value issues can become material when they reveal weak systems or management override.

Close the item only after the evidence agrees across source documents, books, portal data and management reporting. A screenshot or email promise is not equivalent to a completed filing, lender waiver, signed contract or reconciled ledger.

Board Escalation

The control should operate across the full transaction population, not only the samples management expects a reviewer to inspect. For this topic, the key stages are pre-receipt, allotment, event reporting, annual reporting. Each stage should identify the source system, preparer, reviewer, deadline and evidence retained.

A useful management review asks whether the legal document, accounting entry, bank movement, tax treatment and public filing describe the same event. Differences may be valid, but they should be reconciled through a dated working rather than explained from memory during audit or diligence.

Materiality should determine escalation, not whether the company keeps a record. Repeated small exceptions can show weak master data, unclear authority, system bypass or management override. Root cause and preventive action should therefore be documented separately from the immediate correction.

Tag every working with the legal entity, counterparty residence, transaction date, reporting period and governing law. During the 2026 income-tax transition, the date income arose can be more important than the date a form or payment is submitted.

Cross-border and tax records should reconcile to the general ledger, bank statement, contract, invoice and statutory return. Filing one correct form does not cure a different missing event report, withholding obligation or corporate approval.