Does bank close eBRC on behalf of exporter? The answer is a big NO. Banks were closing eBRC for exporter but not now, banks stopped generating new eBRCs between 15 November 2023 and 31 January 2024, depending on each bank’s cut-off date. Exporters must maintain control over the complete chain: Inward Payment received → IRM reported by Bank → EDPMS reconciled by bank→ eBRC generated by exporter→ documents stored into Shipzy.
As we all know, technically, eBRC generation and EDPMS closure are two separate processes managed through different systems.
DGFT manages the eBRC system, while the exporter’s Authorised Dealer bank is responsible for updating and closing entries in RBI’s Export Data Processing and Monitoring System, or EDPMS. DGFT has also specifically clarified that eBRC and EDPMS operate as distinct systems.
What is an eBRC?
An Electronic Bank Realisation Certificate, or eBRC, is the digital record of export proceeds received against the export of goods or services.
Under DGFT’s revamped system, exporters can generate eBRCs through self-declaration after their bank reports the relevant Inward Remittance Message, or IRM, to DGFT.
The revamped process was introduced to reduce bank visits, physical documents and manual eBRC charges. Exporters can generate eBRCs using shipping bill, SOFTEX or invoice details available in the DGFT system.
What is EDPMS closure?
EDPMS is RBI’s system for monitoring export transactions and outstanding export proceeds.
The exporter’s AD bank is responsible for reconciling the export payment against the relevant shipping bill or service invoice and closing or updating the entry in EDPMS.
Therefore:
- DGFT eBRC: Generated by the exporter or an authorised API integration like Shipzy.
- EDPMS entry: Closed or updated by the exporter’s AD bank.
- Shipzy: Automates eBRC generation, reconciliation, document storage and bank-closure tracking.
- AD bank: Remains responsible for regulatory EDPMS closure.
How the complete eBRC and EDPMS process works
Step 1: Export payment is received
The foreign payment is credited to the exporter’s bank account.
The bank generates an IRM containing information such as:
- IRM number
- Remittance date
- Currency
- Remittance amount
- Purpose code
- Exporter IEC
- Account and bank details
DGFT defines an IRM as the bank-generated notification confirming receipt of funds from a foreign source.
Step 2: The bank sends the IRM to DGFT
Banks are required to report foreign remittance IRMs to DGFT on an account-credit basis. The reporting of an IRM is not dependent on the exporter submitting shipping documents to the bank.
Where two banks are involved, the bank in which the exporter’s account is finally credited is responsible for reporting the IRM to DGFT for remittances received on or after January 31, 2024.
Step 3: The exporter generates the eBRC
Once the IRM is visible, the exporter maps it with the relevant:
- Shipping bill for goods
- SOFTEX details for applicable software exports
- Invoice for other service exports
The exporter can then submit and generate the eBRC through the DGFT portal.
DGFT also permits bulk eBRC generation and eBRC generation through API integration like through Shipzy software.
Step 4: The AD bank closes or updates EDPMS
The AD bank verifies the transaction and reconciles the payment with the relevant export entry.
The bank then updates or closes the shipping bill or invoice entry in EDPMS. Generating an eBRC does not remove the bank’s responsibility for EDPMS reconciliation.
Latest eBRC and EDPMS Rules Exporters Should Know
1. ₹10 lakh EDPMS closure rule
RBI introduced an important relaxation from October 1, 2025.
For an export entry, shipping bill or invoice valued at ₹10 lakh or less, including old outstanding entries, the AD bank can reconcile and close the EDPMS entry based on a declaration from the exporter confirming that the amount has been realised.
The exporter may also submit one consolidated declaration every quarter covering multiple eligible bills.
RBI has additionally allowed banks to accept a reduction in the declared or invoice value based on the exporter’s declaration for these transactions. Banks have been instructed to keep their charges proportionate and not impose penal charges for regulatory delays.
What exporters should understand
The ₹10 lakh rule:
- Applies per shipping bill, invoice or EDPMS entry.
- Includes outstanding entries.
- Simplifies EDPMS reconciliation.
- Permits quarterly bulk declarations.
- Is handled by the AD bank.
- Does not mean every eBRC below ₹10 lakh is automatically generated or closed.
2. GSTIN and GST invoice details in eBRC
DGFT Public Notice No. 42/2025-26, dated January 9, 2026, amended the eBRC format under Appendix 2U to include:
- GSTIN
- GST Invoice Number
- GST Invoice Date
The change became operational in January 2026.
However, it is not correct to say that GSTIN is mandatory for every eBRC.
In the current DGFT workflow, the exporter must answer the mandatory question:
“Whether you want to avail GSTIN benefit?”
When the exporter selects Yes, the following become mandatory:
- GSTIN of the branch
- GST Invoice Number
- GST Invoice Date
When the exporter selects No, these fields are filled with “NA” and disabled.
Therefore, the correct statement is:
GST-related information is mandatory when the exporter chooses to avail GSTIN-linked benefits through that eBRC. The Yes or No declaration itself is mandatory.
3. Mode of Export of Services is mandatory
For service-export eBRCs, DGFT has introduced a mandatory field called Mode of Export of Services.
Service exporters must classify the transaction under one of the four GATS modes:
- Mode 1 - Cross-Border Supply: Services delivered remotely from India.
- Mode 2 - Consumption Abroad: The overseas customer travels to India to receive the service.
- Mode 3 - Commercial Presence: Services provided through a foreign branch, subsidiary or commercial establishment.
- Mode 4 - Presence of Natural Persons: An individual travels abroad temporarily to provide the service.
The requirement applies to individual eBRC generation as well as bulk uploads.
When one IRM covers services falling under different modes, separate eBRCs must be generated for each service-export mode.
4. Current export realisation timeline
As of July 24, 2026, RBI’s current Master Direction provides a general period of nine months from the date of export for realisation and repatriation of export proceeds.
For goods exported to a warehouse outside India, the current period is generally 15 months from the date of shipment.
Exporters should not confuse this current rule with the new RBI regulations that will become effective from October 1, 2026.
5. New realisation timelines from October 1, 2026
RBI has notified the Foreign Exchange Management (Export and Import of Goods and Services) Regulations, 2026. These regulations will come into force on October 1, 2026.
From that date, the general realisation periods will be:
- Goods: 15 months from the date of shipment.
- Services: 15 months from the invoice date.
- Goods exported to an overseas warehouse: 15 months from the date of sale from the warehouse.
- Project exports: As per the payment terms of the contract.
- Exports invoiced or settled in Indian rupees: 18 months.
The AD bank may grant additional time where the exporter provides valid reasons and the bank is satisfied with the request.
Therefore, articles should not presently state that the 15-month rule is already applicable to all exports. It becomes effective only from October 1, 2026.
6. Multiple IRMs and shipping bills
DGFT permits multiple IRMs to be used for generating an eBRC, subject to prescribed conditions.
Important rules include:
- Only IRMs of the same currency can be clubbed.
- Clubbed IRMs must relate to the same bank and bank account.
- One shipping bill may be used for two or more eBRCs where payments were received through different banks.
- Advance remittance purpose code P0103 can be used subject to DGFT’s prescribed conditions.
- Different-purpose-code IRMs generally cannot be clubbed, except where DGFT specifically permits it.
7. Cross-currency eBRC generation
The shipping bill currency and IRM currency do not always have to be the same.
DGFT allows an exporter to generate an eBRC even where the shipping bill currency differs from the IRM currency, based on the IRM currency and the transaction details entered by the exporter.
8. PayPal, Wise and e-commerce export payments
Exporters receiving payments through platforms such as PayPal, Wise or other payment intermediaries can self-generate eBRCs.
The exporter must first approach the bank and ensure the corresponding IRM is reported to DGFT. Once the IRM is available, the exporter can generate the eBRC.
9. Netting-off transactions
Where export receivables are adjusted against permitted outward payments, the bank should report:
- An IRM based on the gross export value.
- The relevant ORM for the outward adjustment.
The exporter can then generate the eBRC using the reported IRM and ORM information.
10. eBRC cancellation timeline
An exporter can independently cancel a self-generated eBRC within 120 days from the date of generation.
After 120 days, the exporter must approach the relevant bank. The bank flags the eBRC, after which the exporter submits the cancellation response and the bank processes the cancellation.
An exporter cannot independently cancel an eBRC that was originally issued by a bank under the legacy system.
How Shipzy Automates eBRC Management
With authorised DGFT integration, Shipzy helps exporters automate the following activities.
Automatic eBRC generation
Shipzy matches eligible IRMs with export invoices, shipping bills and related records.
Based on configured validations and exporter authorisation, Shipzy can automatically complete the eBRC generation workflow instead of requiring the export team to manually prepare every record on the DGFT portal.
Complete IRM visibility
For every IRM record, Shipzy displays important information such as:
- IRM Number
- Bank and account
- Remittance date
- Currency
- Remittance Amount
- Adjustment amount
- Available Amount for generating a fresh eBRC
- Remaining IRM balance
These values follow the calculation structure used in DGFT’s eBRC system, where the available amount is derived after considering amounts already attached to other eBRCs and applicable ORM amounts.
“Last updated” DGFT status
Shipzy shows a Last updated date and time for the eBRC data.
This timestamp represents when the information was last successfully fetched from DGFT. It helps the export team understand whether they are viewing recently synced data or whether another refresh is required.
eBRC file storage and retrieval
After an eBRC is generated, Shipzy stores the eBRC file against the relevant export transaction.
Users can retrieve the eBRC on demand without repeatedly logging in to DGFT or searching through local folders, emails and employee computers.
The document remains linked with the relevant:
- Invoice
- Shipping bill
- Shipment
- IRM
- Bank realisation record
Automatic reconciliation
Shipzy can identify situations such as:
- Payment received but IRM not available.
- IRM available but eBRC not generated.
- Part payment received.
- One payment covering multiple invoices.
- Multiple payments against one invoice.
- IRM balance still available.
- Currency or amount mismatch.
- eBRC generated but EDPMS closure pending.
This creates one exception-based worklist instead of requiring the export team to check every transaction manually.
Practical Checklist for Exporters
For every export payment, verify that:
- The payment is credited to the correct bank account.
- The bank has reported the correct IRM to DGFT.
- The purpose code is correct.
- The IRM is mapped with the correct invoice, SOFTEX or shipping bill.
- GST details are entered where GSTIN benefit is being claimed.
- Service-export mode is selected where applicable.
- Deductions such as commission, freight, insurance or discount are correctly recorded.
- The eBRC has been generated and stored.
- The bank has updated or closed the related EDPMS entry.
- Outstanding transactions are followed up before the applicable RBI deadline.
Frequently Asked Questions
Is GSTIN mandatory for every eBRC?
Yes. As per new rule, GST Invoice Number and GST Invoice Date is mandatory for every eBRC.
Is the ₹10 lakh rule related to eBRC generation?
No. It primarily simplifies EDPMS reconciliation and closure by the AD bank for entries of ₹10 lakh or less. eBRC generation remains a separate DGFT process.
Does generating an eBRC automatically close EDPMS?
Not necessarily. The AD bank must still reconcile and close or update the relevant EDPMS entry.
Can an eBRC be generated automatically through software?
Yes. DGFT authorise through APIs that can be used by the IEC holder or an authorised technical partner. The exporter must grant the required DGFT access using the prescribed authorisation process.
Can multiple IRMs be used for one eBRC?
Yes, subject to DGFT rules relating to currency, bank account and purpose codes.
What is the current realisation period?
As of July 24, 2026, the general current period is nine months from the date of export. The new 15-month framework becomes effective from October 1, 2026.
Notes from Shipzy
Shipzy brings many manual activities into one system by automatically fetching DGFT data, showing IRM utilisation and balances, generating eBRCs and storing certificates.
This reduces repetitive portal work while giving exporters and management a clear view of every outstanding export realisation.
Regulatory processes may vary depending on the transaction, purpose code, bank and applicable FEMA provisions. Exporters should review the latest DGFT and RBI instructions and consult their AD bank for transaction-specific cases.
Official links for eBRC
-
DGFT – eBRC landing: dgft.gov.in/CP/?opt=eBRC
-
DGFT – Generate e-BRC: dgft.gov.in/CP/?opt=eBRCRules (rules/notes; e.g., one SB can map to multiple eBRCs; multiple IRMs can be added) (DGFT)
-
DGFT – eBRC User Guide (PDF): self-generation flow, login → Services → eBRC → Generate e-BRC. (DGFT Content)
-
DGFT – eBRC FAQs (PDF): confirms banks stop issuing eBRC once they are API-integrated; exporters download from DGFT after IRM. (DGFT Content)
-
ICEGATE – SB-EDPMS Enquiry Advisory: track/rectification pointers. (Icegate)
-
ICEGATE – SB Track (ICES): quick status check by SB no./date. (ICEGATE Enquiry)
