RBI Compliance

EDPMS Complete Guide. RBI's Export Reporting System Explained

EDPMS lifecycle, entry statuses, 9-month rule, caution listing, write-off, e-commerce challenges, automation, and monthly checklist.

By Aaryan Kakani · · 15 min read

What Is EDPMS

The Export Data Processing and Monitoring System (EDPMS) is the RBI's centralized electronic platform for tracking every export transaction originating from India. It monitors the entire arc of an export. From the moment a shipping bill is filed with customs to the point where export proceeds are realized in foreign exchange and reported by the exporter's bank.

Before EDPMS, export monitoring relied on a paper-based system of declaration forms: GR forms (for exports through sea and air cargo), SDF forms (for exports through ports with Electronic Data Interchange), PP forms (for exports by post), and SOFTEX forms (for software and IT service exports). Exporters would fill these physical forms in duplicate, submit one copy to customs and the other to their Authorised Dealer (AD) bank, which would then manually report realization to RBI. The system was slow, error-prone, and created massive backlogs of unmatched export declarations.

EDPMS went live in 2013-14, progressively replacing the paper forms. RBI's Master Direction on Export of Goods and Services now governs the system. Its companion for imports is IDPMS (Import Data Processing and Monitoring System). Together, they give RBI a real-time view of India's trade payment flows.

What EDPMS replaced

Old FormUsed ForEDPMS Equivalent
GR FormSea/air cargo exports at non-EDI portsAuto-populated EDPMS entry
SDF FormExports through EDI-enabled portsAuto-populated EDPMS entry
PP FormExports by post parcelAuto-populated EDPMS entry
SOFTEX FormSoftware/IT service exportsSOFTEX module in EDPMS

EDPMS Data Flow. The Complete Lifecycle

Understanding the EDPMS data flow is critical because every compliance issue (mismatches, caution listing, penalties) originates from a breakdown at one of these stages.

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

))}

How EDPMS Entries Get Created

EDPMS entries are not created manually by the exporter. They are auto-populated from customs data. Understanding the creation mechanism helps diagnose why entries sometimes go missing or appear with incorrect data.

Goods exports (standard)

When the exporter files a shipping bill on ICEGATE , the system captures all declaration details. Once customs grants LEO, the ICES (Indian Customs Electronic System) transmits the data to EDPMS via the customs-RBI interface. The entry is typically visible in the AD bank's EDPMS view within 24-72 hours of LEO.

Key data transmitted: shipping bill number and date, LEO date, port code, IEC, AD bank code, FOB value in foreign currency, FOB value in INR, HS codes, consignee name and country, and the RBI purpose code .

Exports via post (e-commerce/samples)

Exports sent through postal channels should also generate EDPMS entries when a shipping bill is filed. However, small parcels shipped without a formal shipping bill (under the postal export exemption for values below Rs 25,000) do not create EDPMS entries. E-commerce exporters using postal channels for higher-value shipments must ensure a shipping bill is filed. Otherwise there is no EDPMS entry to close, but the inward remittance still needs FEMA reporting.

SOFTEX (software and IT services)

Software exports do not have a physical shipping bill. Instead, the exporter files a SOFTEX form with their STPI/SEZ authority, which certifies it and forwards the data to RBI for EDPMS entry creation. The AD bank then handles the entry like any other EDPMS record. Matching inward remittances and reporting closure. SOFTEX filing is required for software exports exceeding the threshold prescribed by RBI.

EDPMS Entry Statuses

Every EDPMS entry carries a status that determines what action is required. Understanding these statuses is the foundation of EDPMS compliance.

StatusWhat It MeansAction RequiredRisk Level
OpenShipping bill filed, payment not yet realized or matched by AD bankEnsure export proceeds are received within 9 months and bank matches payment to entryNormal (within 9 months)
ClosedExport proceeds fully realized and matched; BRC issued by AD bankNo action needed; retain BRC and supporting documents for 5 yearsNone
Caution ListedEntry open beyond 2 years from shipping bill date without closureImmediate action: realize payment, obtain write-off, or provide closure documents to AD bankHigh
Written OffEntry closed without full payment realization using RBI write-off provisionsMaintain documentation of write-off basis; may need to report in annual returnsLow (if properly documented)

In practice, most compliance problems stem from entries sitting in "Open" status for too long. The clock starts ticking from the shipping bill date, and the 9-month repatriation deadline under FEMA is the first critical milestone. The 2-year caution listing threshold is the point of no return for many exporters.

The 9-Month Repatriation Rule

This is the most critical deadline in EDPMS compliance. Under FEMA Section 10 and the RBI Master Direction on Export of Goods and Services , export proceeds must be realized and repatriated to India within 9 months from the date of export.

Key aspects of the 9-month rule

  • 01 Starting date: The 9-month clock starts from the date of export, which is the date of the shipping bill or the LEO date (whichever is applicable per the Master Direction).
  • 02 What counts as realization: The proceeds must be received in India in the designated currency (or any freely convertible currency) and credited through the banking channel. Direct receipt abroad (e.g., foreign bank account not routed through AD bank) does not count.
  • 03 Extension provisions: RBI has delegated authority to AD banks to extend the repatriation period in certain cases. Units in SEZs may have different timelines. The exporter must apply to the AD bank before the 9-month deadline with reasons for the delay.
  • 04 Consequence of breach: Failure to repatriate within 9 months is a contravention of FEMA. It triggers potential penalties under FEMA Section 13 , compounding proceedings, and eventual caution listing if the entry remains open.

For a detailed breakdown of the repatriation deadline including sector-specific exceptions, extension procedures, and how to handle delayed payments, see our dedicated guide on the FEMA 9-month repatriation deadline .

The AD Bank's Role in EDPMS

Your Authorised Dealer bank is the operational backbone of EDPMS compliance. They are the intermediary between the exporter and RBI, responsible for matching payments, reporting realizations, and issuing closure documents. For a comprehensive overview, see our guide on the AD bank's role in export compliance .

Payment matching

When an inward remittance arrives, the AD bank must match it to the correct EDPMS entry. This involves verifying the shipping bill number (often referenced in the SWIFT message), the remitter (buyer) name, the amount, and the currency. For multiple shipments to the same buyer, the bank must allocate the payment across the correct entries. Poor matching is the single biggest source of EDPMS compliance failures.

BRC issuance

Once payment is matched and reported in EDPMS, the AD bank issues a Bank Realization Certificate (BRC). This is a critical document for claiming export incentives like RoDTEP , Duty Drawback, and for meeting EPCG export obligations . Without a BRC, the exporter cannot prove realization to DGFT or other authorities.

FETERS reporting to RBI

AD banks report all foreign exchange transactions to RBI through the Foreign Exchange Transactions Electronic Reporting System (FETERS), accessible via RBI's reporting platform at BS_Listofallreturns.aspx. FETERS captures the purpose code, amount, currency, country, and the linked EDPMS/IDPMS entry number. Banks file FETERS returns on a daily and monthly basis. The data flows from FETERS into RBI's Balance of Payments statistics.

Regulatory forms

AD banks submit various regulatory returns using forms prescribed by RBI, including SCH-3, SCH-4, SCH-5, and SCH-6 (available at BS_ViewForms.aspx on RBI's website). These schedules cover different categories of foreign exchange transactions and feed into RBI's aggregate monitoring of capital flows and trade balances.

Common EDPMS Mismatches

Mismatches between what customs recorded and what the bank sees are the most frequent operational headache in EDPMS. Here are the scenarios that cause the most trouble.

Mismatch TypeRoot CauseResolution
Amount mismatch (SB vs payment)Buyer deducts bank charges, agent commission, or claims quality deductions before payingBank can close with adjustment up to 5% variance; larger gaps need documentary evidence (credit note, debit note, correspondence)
Multiple payments against one SBBuyer pays in installments or milestone paymentsBank reports each partial realization in EDPMS; entry closes only when cumulative amount matches
One payment against multiple SBsBuyer sends consolidated payment covering several shipmentsBank must split and allocate the remittance across individual EDPMS entries. Requires exporter to provide SB-wise breakup
Wrong AD code on SBCustoms broker entered incorrect bank AD code while filing shipping billFile customs amendment to correct the AD code; until corrected, the entry sits with the wrong bank
Currency mismatchSB filed in USD but payment received in EUR or via cross-currency settlementBank must convert and report with explanation; may require exporter's letter clarifying the currency change
Duplicate EDPMS entriesSystem glitch or duplicate SB transmission from customsAD bank raises request with RBI EDPMS cell to cancel the duplicate entry

Caution Listing

Caution listing is the most serious consequence of neglecting EDPMS entries. When an entry remains open beyond 2 years from the shipping bill date, the system automatically flags the exporter. For a step-by-step remediation plan, see our dedicated guide on how to get off the EDPMS caution list .

Caution listing triggers

  • · EDPMS entry open for more than 2 years from shipping bill date without any realization reported
  • · Partial realization reported but significant outstanding balance remaining beyond 2 years
  • · Multiple EDPMS entries in Open status across different shipping bills for the same IEC, indicating a pattern of non-repatriation

Consequences of caution listing

  • · IEC deactivation risk: DGFT may suspend or deactivate the IEC based on RBI's caution list data, blocking all future import-export activity
  • · Enhanced bank scrutiny: AD banks apply heightened due diligence on all new export transactions, potentially delaying shipping bill endorsements and LC issuance
  • · Credit facility impact: Banks may tighten or revoke export credit facilities (packing credit, post-shipment finance) for caution-listed exporters
  • · FEMA proceedings: Caution listing is often the precursor to RBI initiating formal FEMA contravention proceedings

Write-Off Provisions

Not every export transaction results in full payment. Buyers default, quality disputes arise, and goods get damaged in transit. RBI recognizes this through a tiered write-off framework that allows EDPMS entries to be closed even when full proceeds are not realized.

Write-Off CategoryLimitWho ApprovesConditions
Self write-off by exporter5% of total export proceeds realized in previous calendar year, or USD 10,000, whichever is higherExporter (with AD bank documentation)Exporter must have realized at least the invoice value minus the write-off amount; must not be on caution list; must file a declaration with AD bank
AD bank write-off10% of total export proceeds realized in previous calendar yearAD bankBank must be satisfied that the exporter made reasonable efforts to realize payment; documentary evidence required (buyer correspondence, legal notice, insolvency declaration, etc.)
RBI approval write-offAmounts exceeding the above limitsRBI (via application through AD bank)Formal application with full case history, evidence of recovery efforts, ECGC claim status if applicable, and AD bank's recommendation

Write-offs are cumulative within a calendar year. If an exporter realized million in export proceeds in the previous calendar year, their self-write-off limit is $50,000 (5%) for the current year. Each write-off reduces the available limit until the next calendar year resets it.

E-Commerce and Aggregator Challenges

E-commerce exports create a unique reconciliation nightmare in EDPMS. The fundamental problem: EDPMS tracks individual shipping bills, but marketplace aggregators and payment processors pay in bulk. For platform-specific compliance, see our guides on e-commerce export compliance and Shopify export compliance .

Amazon/eBay/Flipkart payout mismatch

When an Indian exporter sells on Amazon Global Selling, Amazon aggregates multiple orders into a single payout cycle (typically bi-weekly). One payout might cover 50 separate orders, each with its own shipping bill. Amazon also deducts its commission, referral fees, and FBA charges before remitting. The net amount the exporter receives bears no obvious relationship to any individual shipping bill's FOB value. The AD bank sees one inward remittance from "Amazon.com Services LLC" but needs to close 50 separate EDPMS entries.

Payoneer/Wise bulk payments

Many e-commerce exporters receive marketplace payouts via Payoneer or Wise , which adds another aggregation layer. Payoneer receives the marketplace payout into a virtual receiving account, then transfers to the exporter's Indian bank account. The SWIFT message shows Payoneer as the remitter, not the actual buyer or marketplace. Banks frequently struggle to match these payments against EDPMS entries because the remitter name, reference number, and amount do not correspond to any shipping bill data.

How to handle it

  1. Maintain a detailed reconciliation sheet mapping each shipping bill to the specific marketplace payout cycle it falls in. Include the order ID, shipping bill number, FOB value, and the payout date/amount.
  2. Download and preserve marketplace settlement reports (Amazon Transaction Report, eBay Seller Hub payments) for every payout cycle. These are your documentary evidence for the AD bank.
  3. Work with your AD bank to establish a standing process for bulk matching. Some banks accept a monthly reconciliation statement signed by the exporter in lieu of per-transaction matching.
  4. Use purpose code P0103 (Export of goods through e-commerce) consistently so the bank can identify these transactions correctly.
  5. Consider the Rs 10 lakh simplified closure route (Section 11 below) for individual low-value e-commerce shipments.

EDPMS Entries Under Rs 10 Lakh. Simplified Closure

In a significant relief for small-value exporters and e-commerce sellers, RBI A.P. (DIR Series) Circular No. 12 (RBI/2025-26/89) dated 1 October 2025 allows simplified closure of EDPMS entries where the shipping bill value is Rs 10 lakh or below.

What the simplified closure allows

  • · AD bank can close the EDPMS entry based on a self-declaration from the exporter, without requiring full documentary evidence of payment matching
  • · The exporter declares that payment has been received (or provides a valid reason for non-receipt, such as buyer default on a small order)
  • · The bank is not required to match the payment to the exact shipping bill amount if the variance is within reasonable limits and the overall inflow pattern supports the exporter's claim
  • · The exporter must still maintain records and produce them on demand during RBI inspection or audit

This provision is particularly valuable for e-commerce exporters who ship dozens or hundreds of small-value parcels per month. Before this circular, each parcel's EDPMS entry required individual matching. An operationally impossible task when marketplace payouts aggregate hundreds of orders.

Common Errors and Fixes

These are the errors that trip up exporters most often. For a more detailed troubleshooting guide, see EDPMS common errors and solutions .

Wrong purpose code

Problem: The AD bank reports the inward remittance under an incorrect purpose code (e.g., P0102 for general goods export instead of P0103 for e-commerce, or using a services code for goods).

Fix: The bank must amend the FETERS reporting with the correct purpose code. This requires a letter from the exporter specifying the correct code and the reason for correction. Persistent wrong coding can trigger RBI queries during inspection.

Amount mismatch beyond tolerance

Problem: The realized amount differs from the shipping bill FOB value by more than what the bank considers acceptable (typically beyond 5%). Causes include freight deductions by the buyer (on CIF vs FOB confusion), bank charges deducted at source, or genuine price renegotiations post-shipment.

Fix: Provide the AD bank with supporting documents: a credit note issued to the buyer, amended invoice, correspondence showing price renegotiation, or bank charge certificates. The bank can then close the EDPMS entry with the variance documented.

Missing shipping bill linkage

Problem: Payment received but the bank cannot link it to any EDPMS entry. This happens when the buyer's SWIFT message does not reference the shipping bill number, or references it in a format the bank's system does not recognize.

Fix: Proactively share the shipping bill number with your buyer and request they include it in the payment instruction to their bank. When the payment arrives, immediately inform your AD bank of the linkage. Some banks accept a simple email from the exporter mapping the SWIFT reference to the shipping bill number.

Duplicate EDPMS entries

Problem: The same shipping bill creates two EDPMS entries, either due to a system glitch in the customs-to-RBI transmission or because the shipping bill was amended and retransmitted.

Fix: The AD bank must raise a formal request with RBI's EDPMS cell (accessible via the FED Portal at ReportingPlaform.aspx) to cancel the duplicate entry. Provide the bank with both entry numbers and the shipping bill details to expedite the request.

RBI Reporting Platforms

Multiple RBI platforms interact with EDPMS. Understanding which platform does what helps when you need to trace an issue or when your bank asks for specific data.

PlatformRBI ReferencePurposeWho Uses It
FED PortalReportingPlaform.aspxCentral reporting platform for foreign exchange data; provides EDPMS/IDPMS access, entry status queries, and communication with RBI EDPMS cellAD banks (primary); exporters can request access through their bank
FETERSBS_Listofallreturns.aspxForeign Exchange Transactions Electronic Reporting System; daily/monthly reporting of all forex transactions by AD banks with purpose codes and EDPMS linkageAD banks
Regulatory Forms (SCH-3/4/5/6)BS_ViewForms.aspxPrescribed forms for reporting different categories of foreign exchange transactions; feed into RBI's aggregate monitoringAD banks
EDPMS/IDPMS FAQReportingFAQ.aspxOfficial FAQ for common EDPMS and IDPMS queries including entry creation, status changes, and closure proceduresAD banks, exporters, compliance teams

Penalties for Non-Compliance

EDPMS non-compliance is ultimately a FEMA violation. The penalty framework is more severe than most exporters realize. For the full picture, see our guide on common FEMA violations for exporters .

FEMA Section 13 penalties

For contravention of Section 10 (non-repatriation of export proceeds), the penalty can be up to three times the amount involved . Where the amount is not quantifiable, the penalty can be up to Rs 2 lakh. These are civil penalties imposed through adjudication proceedings, not criminal prosecution.

RBI compounding process

Before adjudication, RBI offers compounding as a settlement route. The exporter admits the contravention and pays a compounding fee (typically 5% to 300% of the contravention amount, depending on the period of delay, the amount involved, and whether the exporter has a history of violations). Compounding is voluntary but practical. It settles the matter without formal adjudication and the associated reputational damage.

AD bank penalties

AD banks themselves face penalties for delayed or incorrect EDPMS reporting. RBI can impose fines on banks for non-reporting, delayed matching, and failure to follow up on open entries. This is why banks are increasingly strict about EDPMS compliance. Their own regulatory standing is at stake.

EDPMS Automation and Tools

Manual EDPMS reconciliation is the default for most Indian exporters. And it is deeply inefficient. For a detailed look at automation approaches, see our guide on EDPMS closure automation .

AspectManual ProcessAutomated Process
SB-to-payment matchingExport team manually maps each inward remittance to shipping bills using Excel; 2-4 hours per week for mid-size exporterSystem auto-matches based on SB number, buyer, amount, and date proximity; alerts on unmatched entries
Open entry trackingMonthly review of bank-provided EDPMS statement; entries often missed until they hit caution list thresholdReal-time dashboard showing all open entries with aging, color-coded by risk (green < 6 months, amber 6-9 months, red > 9 months)
Deadline alertsCalendar reminders set manually, if at all; missed deadlines discovered during annual auditAutomated alerts at 6 months, 8 months, and 9 months from SB date; escalation to management if no action taken
Bank communicationEmail chains with bank's trade finance team; documents shared as attachments; no audit trailStructured reconciliation files generated automatically; shared with bank via portal or API; full audit trail
E-commerce reconciliationManual download of marketplace settlement reports, cross-referencing with SB data; extremely time-consuming for high volumesMarketplace API integration auto-maps orders to SBs; payout reconciliation generated per cycle

For a mid-size exporter filing 50-100 shipping bills per month, manual EDPMS management typically consumes 10-15 hours of staff time per month. Automated reconciliation reduces this to 1-2 hours of exception handling, while dramatically reducing the risk of entries slipping through to caution listing.

Exporter Checklist. EDPMS Health Check

Use this checklist monthly and quarterly to stay on top of EDPMS compliance. For a broader compliance framework, see our export compliance audit checklist .

Monthly checks

  • Request EDPMS open entry statement from your AD bank for your IEC. Verify entry count matches your shipping bill records
  • Review all entries older than 6 months. Flag any where payment has not yet been received and initiate follow-up with the buyer
  • Cross-check recent inward remittances against the EDPMS statement to confirm the bank has matched and reported them
  • For e-commerce exports, reconcile the latest marketplace payout reports against open EDPMS entries and share the mapping with your bank
  • Verify that the AD code on all recent shipping bills is correct to avoid entries going to the wrong bank

Quarterly checks

  • Generate an aging analysis of all open EDPMS entries. Categorize by 0-3 months, 3-6 months, 6-9 months, 9-12 months, and beyond 12 months
  • For entries approaching the 9-month deadline without payment, initiate extension requests with the AD bank with supporting documentation
  • Review write-off utilization. Calculate remaining self-write-off limit for the calendar year and plan any needed write-off applications
  • Check for any entries approaching the 2-year caution listing threshold and take closure action (payment realization, write-off, or documentary evidence for adjustment)
  • Reconcile BRC status with DGFT incentive claims. Ensure every incentive claim (RoDTEP, Duty Drawback, EPCG obligation) has a corresponding closed EDPMS entry and BRC
  • Review the FEMA compliance rules for any changes to EDPMS reporting requirements, write-off limits, or closure procedures

Related resources

Get Off the EDPMS Caution List

Step-by-step guide to remediating caution-listed entries and restoring your compliance status.

EDPMS Closure Automation

Automate shipping bill to payment matching and eliminate manual reconciliation.

FEMA 9-Month Repatriation Guide

Understand the repatriation deadline, extension procedures, and consequences of missing it.

Seasaw for Indian Exporters

Automate Your EDPMS Reconciliation

Seasaw automatically matches shipping bills to bank payments, tracks open EDPMS entries with aging alerts, and generates bank-ready reconciliation files. So you never hit the caution list.

Learn more about Seasaw

Update history

  • First published.