D G F T

FAQs on revised process for e-BRC Issuance

What is an e-BRC?

What is a Bank Realization Certificate (BRC)? Bank Realisation Certificate, also known as eBRC (electronic Bank Realisation Certificate), is a digital certificate issued by the bank to confirm that the exporter has received payment from the importer for a set of export goods.

How will the customer get e-BRCs in the revised process rolled out by DGFT?
Answer – As per the revised process, customers will be able to see IRMs uploaded by banks in the logged-in section of the DGFT website. Exporters will have to map the shipping details/documents for the pre-populated Inward Remittance Messages (IRMs)* received against their IEC and generate e-BRCs on a Suo Moto basis against those IRMs.

What is a bank’s role in the revised process of e-BRC generation?
Answer – Banks will report IRMs received for all exporters to DGFT post February 1, 2024. These IRMs will be utilised by exporters for e-BRC generation.

If the exporter doesn’t want to generate the e-BRC at their end, can a bank continue to generate e-BRCs for such exporters?
Answer – Banks will not issue any e-BRCs for IRMs received post February 1, 2024.

If the exporter has obtained e-BRC from DGFT, are they still required to submit export documents to banks?
Answer – Yes. FEMA/RBI guidelines regarding the submission of export documents to banks, has not undergone any change. FEMA/RBI regulations require every exporter to submit export documents within 21 days of shipment to their AD (Authorised Dealers) category bank. Regulatory pendency will still reflect in EDPMS (Export Data Processing and Monitoring System) for exporters who have not submitted their export documents in the mentioned timeframe.

How to map the Shipping Bills against IRMs with different AD Codes for e-BRC generation?
Answer – Shipping Bills (SB) and IRMs with different AD Codes cannot be mapped. Exporters need to approach their AD for initiating AD Code transfer in EDPMS, post which the exporter can match SBs with IRMs to proceed for e-BRC generation.

The following are the two scenarios:

  • Scenario 1: IRM settled with AD bank 1 & Bill regularised with AD bank 2 – AD bank 1 will report the IRM to DGFT; the respective IRM is to be used for self-generation of e-BRC by the exporter. AD bank 1 will issue the e-FIRC in EDPMS. Exporters need to approach their AD for initiating AD Code transfer in EDPMS, for closure of SB in EDPMS by AD bank 2.
  • Scenario 2: IRM settled with AD bank 1 & Bill regularised with AD bank 1 whereas funds received with AD bank 2 – AD bank 2 is to transfer the funds to AD bank 1. AD bank 1 will settle the IRM & report it to DGFT. Exporters need to approach their AD for initiating the AD Code transfer in EDPMS, for closure of SB in EDPMS by AD bank 1 in case the SB is issued to AD bank 2.

Should the SB utilised against a particular IRM be the same at DGFT and the AD bank?
Answer – Yes. There should be no difference in the IRM utilisation at DGFT & the AD bank.

Which additional points need to be checked before generating e-BRC for Advance Payment cases (P0103 Purpose Code)?
Answer – To generate e-BRC for Advance Payment cases (P0103 Purpose Code) either with standalone or with clubbed IRMs, the shipping bill/invoice date should be greater than or equal to the remittance date. No e-BRC generation is allowed for Advance Payment cases where the shipping bill/invoice date is before the advance payment date.

Can customers club IRMs with different currencies to generate e-BRC?
Answer – IRMs of different currencies cannot be clubbed to generate e-BRC.

What are the general guidelines regarding Purpose Code for generating e-BRC?
Answer – The following are the general guidelines, issued by DGFT for generation of e-BRCs:

  • Customers cannot generate e-BRC for Purpose Codes P0101 and P0108
  • P0103 can be used as a standalone code to generate e-BRC
  • P0103 can be clubbed with P0807 in the case of Services > IT
  • P0103 can be clubbed with any of the 01 Product Groups except P0101 and P0108
  • P0103 can be clubbed with P1505 to generate e-BRC
  • For Services > IT, only these four Purpose Codes are applicable – P0802, P0803, P0807 and P0103
  • No two Purpose Codes can be clubbed to generate a single e-BRC except P0103 (Advance Payment), which can be clubbed with any other Purpose Code for Inward Remittance
  • For deemed exports, P1505 can be used to generate e-BRC
  • In the case of refund/reversal, ORM Purpose Code S1501/S1502/S1504 can be used for offsetting.

How to raise an issue with DGFT?
Answer – A ticket needs to be raised through the following path, on the DGFT portal: DGFT > My Dashboard > Helpdesk Service > Create New Request

To check the status of the raised request, use the following path on the DGFT portal: DGFT > My Dashboard > Helpdesk Service > View Request Status

What if the e-BRC is generated incorrectly?
Answer – The e-BRC needs to be cancelled on the DGFT portal as per the following path: DGFT > My Dashboard > Repository > Self Certification of e-BRC > Cancel e-BRC.

Shares: