Generate your eBRC
without the chase.

An Electronic Bank Realisation Certificate (eBRC) is a digital document issued through the DGFT that certifies your export payment was received and realised in India. Exporters need it to claim incentives such as RoDTEP and duty drawback, and for FEMA compliance. It replaced the old paper Bank Realisation Certificate that banks issued by hand.

A managed workspace such as ebrc.in: connect your DGFT account once and your remittances arrive on their own. You supply only the invoice or shipping bill details; validation, error checks, duplicate protection, and the status-chasing are handled for you, and the certificate is usually back in about two hours. The DGFT portal route works too; it asks you to do everything yourself.

Connect your DGFT account once, from Settings. Your inward remittances then appear in the app, and you map each one to its invoice or shipping bill and submit; upload the shipping bill PDF and the mapping fields fill themselves for you to confirm. You can file one certificate at a time in a short wizard, or a whole spreadsheet at once.

How to generate an eBRC on the DGFT portal, step by step

Yes. In the eBRC exporter app every IRM is auto-mapped to the shipping bill and invoice it paid for, so the filing record arrives with every field filled in. You look the match over and file; nothing reaches the DGFT until you click. In the guided wizard the same fields fill themselves from a shipping bill PDF, and Use Full maps the whole remittance amount in one click.

How auto-mapping works

Yes. The free shipping bill extractor on ebrc.in reads every field out of an ICEGATE shipping bill PDF, from the number, date and port code to each invoice and item line, into a CSV that opens in Excel or as JSON, free, with no sign-up. The file is kept so the extractor can be improved against real documents. In the eBRC exporter app the same read fills the mapping fields from the shipping bill you upload, for you to confirm.

Try the free shipping bill extractor

Your part takes minutes: choosing the remittance, mapping the invoice, and submitting. The certificate is usually back in about two hours, once the DGFT has processed the request. Resubmitting never creates a duplicate filing.

Yes. Download a pre-filled Excel template, add your invoice details, and upload it back. Every row is checked before anything is filed, and errors come back row by row so you know exactly what to fix, and resubmitting never creates a duplicate filing.

Nothing, ever. The eBRC exporter app on ebrc.in is free at any volume, and sign-up collects no card. There is no certificate limit and no paid tier for exporters, whether you file one certificate a year or hundreds a month. The eBRC API is a separate product for platforms and enterprises, with its own published limits.

Exporters have pulled Rs 4,000 crore and more of inward remittances into the eBRC app and the eBRC API to map to their shipping bills, some mapped and some still waiting on a bill, each converted to rupees at one standard rate. The figure is indicative, not audited, and is updated about once a month. It counts what came in, not certificates issued; the homepage says so in a note titled How we count this.

Yes, on Android. The eBRC exporter app is live on Google Play, free, listed as eBRC Exporter App by Eximfiles under the package in.ebrc.app. It does on a phone what the eBRC exporter app does on the web: connect a DGFT account once, see inward remittances as they arrive, map each one to its shipping bill or invoice, generate the certificate, and keep every eBRC and the ledger to hand. The iOS version is not released yet and is coming to the App Store; until it is, an iPhone runs the same exporter app in the phone's browser. The listing, the code that opens it and the details are on ebrc.in/mobile-app, and the terms are the same on a phone as on the web: free at any volume, no certificate limit, no card.

The eBRC API is ebrc.in's REST interface for platforms and enterprises that generate DGFT-issued certificates from their own systems. You submit filings as JSON or Excel, get a request ID, and poll for status. One account can hold many exporter entities, each with its own DGFT connection. It is a separate product from the eBRC exporter app: the API is free for general use within published limits of 250 production certificates a month and up to 10 exporter entities in either environment, with sandbox filing not metered, while the eBRC exporter app stays free at any volume, with no certificate limit and no paid tier for exporters. Beyond the free allowance, plans and your usage for the month sit together in the console under Billing.

Yes. Every workspace has a Test mode and a Live mode. Test submits to a sandbox, so you can check your format and mapping without creating a real certificate. Nothing is legally binding until you explicitly switch to Live, and the switch asks you to confirm.

Electronic Bank Realisation Certificate. Electronic because it is issued digitally, Bank because your bank reports the incoming payment, Realisation because the money actually reached India, and Certificate because the DGFT issues it as formal proof.

Every certificate generated from the app stays in your reports, where you can download it as a PDF and copy its eBRC number whenever a bank, an auditor, or a claim needs it. On the DGFT portal, certificates sit under Repositories, in Bank Realisations.

The status view in the app shows where every request is, live, with no portal session. On the DGFT portal the same answer lives under Repositories, in Bank Realisations, once you sign in.