Welcome To Dwarkadhish Overseas Private Limited
DGFT, Customs and Export Compliance Support Across India
Manage export realisations from inward remittance to correctly generated and reconciled electronic Bank Realisation Certificates.
Dwarkadhish Overseas assists exporters with IRM tracking, Shipping Bill and invoice mapping, single and bulk eBRC generation, service and SOFTEX export reporting, deductions, cancellation, bank coordination, DGFT authorisation reconciliation and pending export-receivable monitoring.
Process
The current workflow places responsibility for eBRC generation on the exporter for IRMs covered by the revamped system.
Banks may continue to handle legacy eBRCs relating to remittances before their applicable cut-off date, while exporters self-generate certificates for remittances covered by the new workflow.
eBRC stands for electronic Bank Realisation Certificate. It is a system-generated electronic record confirming the value realised against an export transaction based on remittance information reported by the bank and export information declared or mapped by the exporter. Under the revamped process, banks transmit Inward Remittance Messages to DGFT, and exporters use those IRMs to self-generate eBRCs by mapping the remittance against the relevant Shipping Bill, SOFTEX form or service invoice.
update
DGFT amended Appendix 2U of the Handbook of Procedures through Public Notice No. 42/2025-26.
The revised format became operational from 13 January 2026 and introduced or separated fields including:
The revised statement also clarifies that realised value can be denominated in foreign currency or INR and can reflect the applicable commercial terms agreed between the exporter and buyer
Exporters should ensure that the following information is consistent:
Incorrect invoice-level GST information can create difficulty when using the eBRC in subsequent compliance or reconciliation work.
EBRC types
The revamped system supports different export categories.
IRM stands for Inward Remittance Message.
It is the electronic remittance record transmitted by the bank to DGFT when an inward payment is received.
An IRM can include:
An exporter cannot self-generate an eBRC without an eligible IRM being available in the DGFT system.
ORM refers to an outward-remittance message linked to an inward remittance where an amount has been paid outward or adjusted.
It may be relevant in cases involving:
The amount available for eBRC generation can be affected by the IRM amount and the applicable ORM amount reported by the bank. DGFT’s current technical specifications calculate the available remittance using the inward amount less related outward-remittance amounts.
Different
A DGFT electronic certificate or statement confirming export realisation based on the IRM and export information.
A bank-issued inward-remittance record containing details of a foreign remittance.
The Reserve Bank of India’s Export Data Processing and Monitoring System used by banks for monitoring export documents and realisation. The DGFT FAQ expressly states that eBRC and EDPMS are separate systems. Generating an eBRC should therefore not be described as automatically closing an EDPMS entry.
For goods exports, the generation process can require:
The exporter should reconcile the Shipping Bill and invoice rather than relying only on the total inward payment.
For non-IT service exports, the IRM is mapped against the relevant export invoice.
Information may include:
The purpose code reported by the bank should align with the nature of the exported service and the permitted SAC-code mapping.
The revamped eBRC format captures the applicable mode of service export.
softex
Software exporters can generate eBRCs by mapping IRMs against approved SOFTEX information.
The process may involve:
Where a transaction is a non-IT service export but was incorrectly reported using a SOFTEX-related purpose code, the exporter may need the bank to amend the IRM purpose code before generating the correct service-export eBRC.
For eligible deemed exports, the exporter should maintain:
The eBRC category selected should reflect the nature of the underlying transaction.
DGFT’s current FAQ states that the Bill ID is the invoice number.
This makes invoice-level consistency important, especially after the introduction of separate GST invoice fields in the revised eBRC format.
We assist exporters with individual realisation records involving:
DGFT allows exporters to bulk-generate eBRCs by uploading the prescribed Excel file through:
The bulk file requires structured information such as branch, bank IFSC, AD Code, IRM, purpose code, Shipping Bill or invoice information, mapped amounts and deduction values.
We compare:
We map:
We review:
Where an invoice or Shipping Bill is realised in instalments, we track:
DGFT permits separate eBRCs where part payments against one export are received through different banks.
Where payment is received before shipment:
DGFT permits exporters to select advance IRMs against a later Shipping Bill for eBRC generation.
The currency of the Shipping Bill or invoice can differ from the IRM currency.
DGFT permits generation based on the IRM currency, subject to correct mapping and value information.
The currency of the Shipping Bill or invoice can differ from the IRM currency.
DGFT permits generation based on the IRM currency, subject to correct mapping and value information.
We assist with identifying:
Where payment is received through platforms such as PayPal, Wise or another intermediary, the exporter should coordinate with its bank so the eligible inward remittance is reported as an IRM to DGFT.
The eBRC can then be self-generated using the reported IRM.
For eligible netting-off arrangements, the bank may need to report:
The exporter then generates the eBRC using the eligible IRM and mapped export information.
We assist with correctly classifying:
DGFT provides separate fields for values that must reduce net realised value and values reported for information only.
We review whether an incorrectly generated eBRC can be cancelled and generated again. IRM utilisation reporting DGFT provides an IRM Utilisation Report that can be generated using portal filters and downloaded as an Excel report after processing.
The report helps exporters analyse IRM usage and remaining realisation balances.
We maintain invoice-wise information showing:
We link:
We assist with:
We prepare:
Process
We verify: IRM number, IRM date, Bank, IFSC, AD Code, Currency, Amount, Purpose code, Remitter details.
The transaction is classified as: Goods, SOFTEX, Non-IT services, Deemed exports.
The IRM is mapped against: Shipping Bill, SOFTEX, Service invoice, Deemed-export invoice.
Information is entered or verified for: GSTIN, GST invoice number, GST invoice date, Bill ID, Invoice value, Export currency.
Applicable commission, freight, insurance, discount and other deduction values are recorded.
The mapped amount and the deductions are reviewed before submission.
The exporter confirms that the information furnished is correct.
After generation, the certificate is reviewed and downloaded from the DGFT Bills Repository.
Bulk Process
Always use the latest Excel sample from the DGFT bulk-generation service.
Such data can include: Serial number, IEC branch, IFSC, AD Code, IRM number, IRM date, IRM currency, Purpose code, Available remittance, Shipping Bill, SOFTEX or invoice number, Export-document date, Port code, Invoice value, Mapped amount, Deductions, GST informationl Service-export mode.
We check: Mandatory fields, Date format, Currency format, Port code, Amount totals, IRM availability, Duplicate invoices, Purpose-code consistency.
The completed file is uploaded through the Bulk Generate eBRC service.
Any records that have failed are checked with the error details provided by the system.
Only corrected records should be re-uploaded to prevent duplicate generation.
Support
DGFT provides technical specifications for IEC holders or their authorised systems to integrate with the eBRC generation APIs.
API functionality can support:
API integration is most suitable for exporters handling high monthly transaction volumes and maintaining an internal ERP or export-management system.
Software development and direct API implementation require a separately agreed technical scope.
Checklist
The checklist depends on the application route.
Purpose
Exporter identification
Branch and GST invoice mapping
Bill ID and value reconciliation
Goods-export mapping
Shipment verification where needed
Software-export mapping
Service-export verification
Remittance availability
Remittance verification
Bank remittance evidence
Receipt confirmation
Reconciliation
Service or export classification
Deduction review
Net-realised-value review
Invoice adjustment
Deduction or adjustment
Outward-remittance adjustment
Benefit-use review
AA or EPCG reconciliation
Troubleshooting
Our Process
We collect: Export documents, IRM data, Bank realisation, Existing eBRCs, DGFT requirements.
We match: Shipping Bill or invoice, Buyer, Currency, Export value, IRM, Amount mapped, Balance outstanding.
The transactions are classified as: Ready for generation, IRM missing, Purpose code incorrect, The mismatch of invoice, The partial payment, Cross-currency case, Cancellation required, Bank action required.
The agreed scope may include: Single generation, Bulk upload, Bank follow-up, Cancellation, Fresh generation, DGFT correction.
The client receives: Generated eBRC list, Pending eBRC list, Missing IRM list, Bank-action list, Outstanding-realisation report, Authorisation-wise reconciliation, Monthly MIS.
Dashboard
Our recurring management dashboard can track:
rules
Troubleshooting
The purpose code is reported through the bank’s IRM data. Where the purpose code is incorrect, the exporter should approach the bank for amendment. DGFT’s current FAQ confirms that banks have the ability to amend IRM information and communicate the updated details to DGFT.
Possible reasons include: Bank has not transmitted the IRM, Bank’s API cut-off process is incomplete, IEC or PAN mapping is incorrect, Purpose code is not eligible, Payment was received through an intermediary, Remittance is with another bank, Bank reported the transaction under another account, IRM was amended or cancelled, Portal processing is pending.
Our approach: We compare: Bank credit date, Bank advice, FIRC, IEC, PAN, Account number, Purpose code, Bank cut-off date, DGFT repository. The bank remains responsible for reporting the IRM to DGFT.
DGFT currently permits exporters to add Shipping Bill metadata where the Shipping Bill is not otherwise available for eBRC generation. This does not remove the need for accurate Customs and export documentation.
Our review includes: Shipping Bill number, Shipping Bill date, Port code, Invoice, Currency, FOB value, IEC, GSTIN, Export type.
This can arise where:
Separate eBRCs may be generated against individual payments, subject to correct mapping and remaining invoice value.
One inward remittance may relate to several invoices or Shipping Bills.
The exporter should allocate the available IRM value carefully so that:
DGFT distinguishes between:
Use where the amount is part of the IRM but must reduce the net export realisation shown.
Use where the value is relevant to the commercial transaction but should not be deducted again from the IRM amount.
Incorrect classification can cause an understated or overstated net realised value.
Why Dwarkadhish overseas
We reconcile each invoice, Shipping Bill and remittance instead of checking only total bank receipts.
Our service covers goods, SOFTEX, non-IT services and deemed exports.
We prepare bulk files and exception reports for exporters handling large volumes.
We identify whether corrective action is required from the exporter, bank or DGFT portal.
eBRC records are mapped to Advance Authorisation, EPCG and Status Holder requirements.
Monthly eBRC management can be included in Export Compliance Outsourcing.
Client Experiences
Service: Advance License
Service: IGST Refund Support
Service: Export Compliance Support
Pan India
Dwarkadhish Overseas provides remote eBRC generation and reconciliation support to exporters across India.
FAQ
eBRC stands for electronic Bank Realisation Certificate.
Exporters generate eBRCs on the DGFT portal using IRMs reported by their banks.
No. An eBRC can be generated only if an eligible IRM is available in the DGFT system.
IRM is the electronic inward-remittance record transmitted by the bank to DGFT.
No. FIRC is a bank remittance document. eBRC is generated through the DGFT system after mapping the realisation to export records.
Yes. The IRM is mapped against the Shipping Bill and invoice.
Yes. Non-IT service exports are mapped using the service invoice and the relevant service information.
It can be found through the DGFT Bills Repository under Bank Realisations or eBRC.
An exporter can currently cancel an eligible exporter-generated eBRC within 120 days, subject to utilisation restrictions.
eBRC or other accepted realisation evidence is commonly used when reconciling physical exports for export-obligation closure.
Fill in your details and our team will contact you regarding your requirement.
Your information will only be used to respond to your service enquiry.