← All posts

eBRC vs EDPMS — the difference every Indian FBA exporter should know

By XPortKnock team · Published 2026-07-20 · 7 min read

If you've spent any time on an Indian export compliance forum, you've seen this confusion: someone asks about "eBRC" when they mean "EDPMS", or vice versa. It happens because the two systems are close cousins — same source data, adjacent purposes, overlapping stakeholders. But they are distinct systems, and mixing them up will cost you either a rejected DGFT claim or a caution-list warning from your AD Bank.

This post lays out exactly what each system is, how they interact, and where FBA sellers specifically get tripped up. Read the complete EDPMS closure guide first if you need a refresher on EDPMS mechanics.

The short definitions

EDPMS and eBRC — how they relate Diagram showing that a single shipping bill flows into both EDPMS (bank closure) and eBRC (DGFT scheme claim), with the AD Bank issuing both. One shipping bill → two downstream systems Shipping Bill filed at customs AD Bank receives foreign exchange EDPMS closure RBI monitoring (mandatory) eBRC on DGFT for scheme claims (optional)
Figure 1: EDPMS and eBRC are downstream of the same event — foreign-exchange realization — but serve different purposes.

The clearest way to think about it

EDPMS is the compliance obligation. eBRC is the benefit claim.

You must close a shipping bill in EDPMS or RBI caution-lists you. You may obtain an eBRC for that shipping bill to claim DGFT scheme benefits. The same realization event triggers both — the money arriving at your AD Bank — but the downstream consequence is different.

If you never claim any DGFT scheme benefit, you can technically operate without ever pulling an eBRC. You cannot operate without EDPMS closure. That said, most FBA exporters do claim RoDTEP (the successor to MEIS), and RoDTEP requires eBRC evidence. So in practice, both matter.

Where FBA sellers actually get tripped up

Trap 1: assuming eBRC is auto-issued the moment money arrives

For a traditional B2B exporter, the AD Bank typically issues an eBRC on the same day it closes the shipping bill in EDPMS. Both happen when the buyer's wire lands and matches the invoice.

For an FBA exporter, the AD Bank cannot close the shipping bill on any single settlement — the shipping bill only fully closes when the last unit sells (or when the exporter files a partial-closure request). Because the AD Bank is holding off on EDPMS closure, it is also holding off on eBRC issuance. The seller assumes eBRCs are being generated silently in the background and only discovers otherwise months later when a DGFT scheme claim gets rejected for missing eBRC evidence.

How to avoid this: request partial eBRCs proactively. Under RBI's post-2015 framework, partial realizations are recognized, and your AD Bank can issue partial eBRCs against a shipping bill that has not fully closed. You have to ask — most banks won't do it on autopilot.

Trap 2: submitting settlement statements to DGFT instead of eBRCs

An Amazon settlement report from Seller Central is not an eBRC. It is not even a substitute. DGFT accepts eBRCs from AD Banks (via the DGFT portal) or physical BRCs on bank letterhead — nothing else. Sellers who submit their Amazon settlement TXT files to DGFT get their claims rejected with terse notices.

The right sequence is: settlement → bank credit → AD Bank issues eBRC → eBRC uploaded (or auto-pushed) to DGFT → DGFT scheme claim submitted with eBRC reference.

Trap 3: eBRC value not matching claimed scheme benefit

DGFT scheme benefits (RoDTEP rate × FOB value) require the eBRC to certify a realized value at least equal to the FOB value on which the scheme benefit was calculated. If your FBA settlements produce less realized foreign exchange than the FOB you declared (because Amazon's fees ate into the gross), DGFT will haircut the scheme benefit proportionally.

This is one of the most misunderstood parts of FBA export economics: your realized foreign exchange is always lower than your FOB value, by exactly the sum of Amazon's platform fees. Plan for this in your scheme-benefit modelling.

When the two systems disagree

Occasionally, EDPMS and eBRC data don't line up — the AD Bank has reported a partial realization to RBI but has not issued a matching eBRC, or vice versa. When this happens:

The fix is almost always a re-issue by the AD Bank. RBI does not adjudicate eBRC issuance; DGFT does not adjudicate EDPMS closure. Your bank is the shared upstream.

What FBA exporters should actually do

IDPMS — one line, for completeness

Import Data Processing and Monitoring System is the mirror of EDPMS for imports. If you import any inputs (packaging, raw materials, components) for the products you eventually export via FBA, IDPMS entries get created for each import and closed against your outward remittances to overseas suppliers. Non-closure of IDPMS entries has its own caution-list mechanism — separate from EDPMS but administratively similar.

Most pure-play FBA sellers (Indian-manufactured goods, exported directly) don't touch IDPMS. If your supply chain involves imported inputs, treat IDPMS with the same seriousness as EDPMS.

The short version

XPortKnock produces the per-shipping-bill realization detail your AD Bank needs to issue both accurate EDPMS closures and eBRCs. If you want to see the reconciliation output end-to-end, start a 14-day trial.