RBI Compliance

RBI Reporting Portals. What Exporters Need to Know

All 9 RBI digital portals explained. FED Portal for EDPMS, FLAIR for FLA, BOP for FETERS, FIRMS for FDI, CIMS Sankalan.

By Aaryan Kakani · · 9 min read

Overview. RBI's 9 Reporting Portals

The Reserve Bank of India maintains nine separate digital reporting portals to collect foreign exchange data from banks, companies, and financial institutions. Each portal serves a specific regulatory function under FEMA (Foreign Exchange Management Act, 1999) and related regulations.

For goods exporters, the critical insight is this: you rarely log into these portals yourself. Your Authorised Dealer (AD) bank is the primary user. But the data your bank submits (or fails to submit) on these portals directly determines whether your EDPMS entries get closed, whether your BRC is issued, and whether you end up on the EDPMS caution list.

PortalFull NamePrimary UsersExporter Impact
FED PortalForeign Exchange Dept PortalAD BanksHigh
FLAIRForeign Liabilities & Assets Info ReportingCompanies with FDI/ODIMedium
BOP PortalBalance of Payments PortalAD BanksHigh
FIRMSForeign Investment Reporting & Mgmt SystemCompanies, CS firmsMedium
CIMSCentralized Info Mgmt SystemAD Banks, NBFCsGrowing
Data CollectorSurvey & Data Collection PortalSelected entitiesLow
SMS PortalSupervisory Monitoring SystemBanks, NBFCsLow
XBRL PortalFinancial Reporting (XBRL)Banks, NBFCsNone
NDS-OMNegotiated Dealing SystemBanks, PDsNone

FED Portal (Foreign Exchange Department)

The FED Portal is the single most important RBI reporting system for exporters, even though you never log into it yourself. It is where your AD bank files EDPMS entries, reports ECB (External Commercial Borrowing) transactions, and submits FDI-related data to RBI.

What it does

  • · EDPMS filings. Every shipping bill creates an EDPMS entry. Your AD bank reports the realisation (payment receipt) against each entry on the FED Portal, and closes it when funds are matched. This is the backbone of EDPMS reporting.
  • · ECB reporting. Banks report all External Commercial Borrowing drawdowns, repayments, and interest payments. Exporters with trade credits beyond 1 year or ECB-funded working capital are affected.
  • · FDI reporting. Inward remittances for foreign direct investment are reported here before flowing into the FIRMS portal for detailed compliance.

How EDPMS entries flow through the FED Portal

  1. Customs files your shipping bill on ICEGATE. The shipping bill data is transmitted to RBI and creates an EDPMS entry automatically.
  2. When your buyer pays, the remittance arrives at your AD bank. The bank credits your account and reports the receipt on the FED Portal.
  3. The bank matches the remittance to the correct EDPMS entry (by shipping bill number, amount, and buyer details) and submits the matching on the FED Portal.
  4. Once matched and verified, the bank closes the EDPMS entry on the portal. Only after closure can your bank issue a BRC (Bank Realisation Certificate).

Exporter impact

Your bank's speed and accuracy on the FED Portal directly determine your EDPMS health. If the bank delays closing entries, you appear as a defaulter in RBI's data even if your buyer paid on time. This can land you on the EDPMS caution list, blocking your DGFT benefits including Advance Authorisation, EPCG, and RoDTEP scrip transfers.

FLAIR (Foreign Liabilities & Assets Information Reporting)

FLAIR is one of the few RBI portals where exporters may need to file directly. It handles the annual FLA (Foreign Liabilities and Assets) Return. A mandatory filing for any Indian company that has received foreign direct investment or has made overseas investments.

FLA Return filing

  • · Who must file: Any Indian company or LLP that has received FDI or has made overseas direct investment (ODI) in the previous or any earlier year, and where the investment is still outstanding.
  • · Deadline: 15 July every year, based on the previous financial year's data (31 March balance sheet).
  • · What it covers: Outstanding foreign equity, foreign debt, overseas branch/subsidiary assets and liabilities, and reinvested earnings.

When exporters must file directly

You need to file the FLA Return on FLAIR if your export company:

  • · Has overseas subsidiaries or branch offices (common for exporters with warehousing or distribution abroad)
  • · Has received foreign equity investment (even a small stake from a foreign buyer or PE fund)
  • · Has made overseas investments under the Liberalised Remittance Scheme (LRS) or ODI route

BOP Portal (Balance of Payments)

The BOP Portal captures all foreign exchange transactions flowing through Indian banks via the FETERS (Foreign Exchange Transactions Electronic Reporting System). For exporters, this is where your purpose codes live.

FETERS reporting

Every inward or outward foreign exchange transaction processed by your AD bank gets reported to RBI through FETERS on the BOP Portal. This includes your export proceeds, advance remittances, buyer commission payments, and freight reimbursements. The data feeds into India's official Balance of Payments statistics and also cross-references with EDPMS on the FED Portal.

Purpose codes. The coding system

Every foreign exchange transaction must carry a purpose code that categorises it. For goods exporters, the key codes are:

Purpose CodeDescription
P0101Export of goods. Against shipping bills
P0102Realisation of export bills (advance remittance)
P0103Export of goods. Postal/courier
P0107Export of goods. Software (non-physical)
P0802Commission on exports
P1007Freight. Exports

Common purpose code issues for exporters

  • · Wrong code on remittance: If your bank tags an export receipt with a non-export purpose code (e.g., P0801 instead of P0101), the EDPMS entry cannot be matched automatically. You need to request a purpose code amendment.
  • · Split remittances: When a buyer pays multiple invoices in a single wire transfer, the bank must split the purpose coding to match individual shipping bills. This is where most matching delays occur.
  • · Advance payments: Export advances (P0102) must be linked to future shipping bills. If the advance is not properly tagged, it cannot be adjusted against EDPMS entries when goods are shipped.

FIRMS (Foreign Investment Reporting & Management System)

FIRMS handles the reporting of all foreign investment transactions in India. Most goods exporters encounter FIRMS only when their company receives foreign equity investment or when shares are transferred to a foreign buyer.

When exporters interact with FIRMS

  • · Receiving foreign investment (FC-GPR): If a foreign buyer, PE fund, or strategic partner invests in your export company, you must file Form FC-GPR on FIRMS within 30 days of share allotment. The form captures share details, pricing, valuation, and KYC of the foreign investor.
  • · Transfer of shares to foreign buyers (FC-TRS): When an Indian resident transfers shares of an Indian company to a non-resident (or vice versa), Form FC-TRS must be filed within 60 days. This applies to export companies doing JVs, buybacks, or cross-border M&A.
  • · Convertible instruments: If you issue convertible notes, compulsorily convertible debentures, or preference shares to foreign investors, the issuance must be reported on FIRMS.

Who handles the filing

FIRMS filings are typically handled by the company's company secretary or CS firm, with inputs from the AD bank (which must verify the underlying foreign exchange transaction). As the exporter, your role is to ensure the underlying data (share price, valuation report, foreign investor KYC, and remittance details) is accurate and provided to the CS/bank on time. Delays in FIRMS filing can trigger FEMA violation notices and compounding proceedings from RBI.

CIMS (Centralized Information Management System)

CIMS is RBI's next-generation unified reporting platform, designed to consolidate data collection across multiple legacy portals into a single system. It represents a major modernisation of how RBI collects and processes regulatory data.

DRM (Data Returns Management). Sankalan

The data returns module within CIMS, known as Sankalan, is gradually replacing the individual data submission processes across older portals. Banks that previously submitted returns through multiple separate portals are now migrating to a unified submission workflow through Sankalan. The system handles automated validation, version control, and audit trails for all regulatory returns.

How CIMS affects exporters

Exporters do not interact with CIMS directly. However, as banks migrate their reporting to CIMS, the backend processing of EDPMS data, FETERS submissions, and ECB reporting is shifting to the new platform. In theory, this should lead to faster data reconciliation, fewer duplicate entries, and quicker turnaround on EDPMS closures. In practice, the migration period can cause temporary disruptions as bank staff adapt to new workflows and data formats.

Data Collector Portal

The Data Collector Portal is RBI's platform for conducting surveys and collecting ad-hoc data from selected entities. It is used for periodic surveys on software and IT-enabled services (ITES) exports, banking services, and other specific data collection exercises.

Most goods exporters will never encounter this portal. However, if your company also provides IT or ITES services alongside goods exports, you may receive a survey invitation from RBI through this portal. These surveys are typically sample-based. RBI selects specific companies rather than requiring universal filing.

If you receive a survey request, treat it seriously. While not a statutory filing like the FLA Return, non-response can draw follow-up queries from RBI and is not a good look for your compliance record.

SMS Portal (Supervisory Monitoring System)

The SMS Portal is used for supervisory reporting by banks and non-banking financial companies (NBFCs). It handles returns related to prudential norms, asset classification, and risk management submissions that RBI uses for banking supervision.

This portal has no direct interaction with exporters. However, the supervisory data submitted here can indirectly affect you. When RBI reviews a bank's supervisory returns and identifies foreign exchange compliance gaps, the bank may tighten its internal processes for EDPMS and forex transactions. Which can mean more documentation requests and slower processing for your export remittances.

How These Portals Connect. Data Flow

Understanding how data flows between you, your bank, and RBI's portals clarifies why certain delays happen and where things can break.

Export Transaction Data Flow

Exporter

ships goods

→

Customs / ICEGATE

shipping bill data

→

EDPMS (auto-created)

Foreign Buyer

sends payment

→

AD Bank

reports via FETERS

→

BOP Portal

AD Bank

matches payment to shipping bill

→

FED Portal (EDPMS closure)

FED Portal

closure status feeds

→

DGFT

caution list / benefit eligibility

All portals

migrating to

→

CIMS (unified platform)

Common Exporter Pain Points

These are the portal-related issues that cause the most delays and compliance headaches for exporters. Each traces back to a specific portal.

Pain PointPortal InvolvedConsequenceFix
Delayed EDPMS closureFED PortalCaution list, DGFT benefits blockedWeekly follow-up with AD bank forex desk
Wrong purpose code on remittanceBOP PortalEDPMS matching failureCheck FIRA immediately, request amendment
Missed FLA Return deadlineFLAIRRBI compliance noticeFile late with explanation letter
Delayed FC-GPR after receiving FDIFIRMSFEMA compounding proceedingsFile within 30 days of allotment
Duplicate EDPMS entriesFED PortalInflated outstanding balanceRequest bank to merge/cancel duplicates
Advance remittance not linkedBOP / FEDEDPMS shows payment pendingProvide shipping bill details to bank for linking

For a detailed walkthrough of EDPMS-specific errors, see our EDPMS common errors and solutions guide. For FEMA violation risks, read common FEMA violations for exporters.

Tips for Working with Your AD Bank on Portal Filings

Since your AD bank is the primary user of most RBI portals, your compliance depends on their efficiency. Here is how to stay on top of it.

  • Establish a single point of contact at your bank's forex desk. Branch-level staff often route forex queries to a centralised processing cell. Get the direct contact for the person handling your EDPMS files.
  • Send a monthly EDPMS reconciliation request. Ask your bank for a list of all open EDPMS entries against your IEC. Compare it against your own shipping bill records. Flag discrepancies immediately.
  • Provide clean documentation upfront. When a remittance arrives, proactively send your bank the matching shipping bill number, invoice number, buyer name, and expected amount. This speeds up the matching process on the FED Portal.
  • Confirm the purpose code on every FIRA. Do not assume your bank assigned the correct purpose code. Wrong codes are the second most common cause of EDPMS matching delays.
  • Escalate systematically. If your forex desk is unresponsive, escalate to the branch manager, then to the bank's zonal forex cell, then to RBI's regional office if necessary. Document every follow-up in writing.
  • Track the [9-month FEMA deadline](/resources/fema-9-month-repatriation-deadline-guide) independently. Do not rely on your bank to alert you when a shipping bill is approaching the 9-month repatriation deadline. Maintain your own tracker and raise red flags at the 6-month mark.
  • Consider a bank with a dedicated export cell. If your current AD bank is consistently slow on FED Portal filings, evaluate banks that have specialised export banking teams. The difference in EDPMS processing speed between banks can be weeks.

Frequently Asked Questions

, , , , , , , , ].map(() => (

Track Your EDPMS Status Automatically

Seasaw monitors your EDPMS entries, alerts you when closures are delayed, flags purpose code mismatches, and gives you a single dashboard to track everything your AD bank does on RBI portals. So you catch problems before they become caution list entries.

Learn more about Seasaw

Update history

  • First published.