eBRCs in minutes of your time, not a day of chasing.
Connect your DGFT account once and your inward remittances show up on their own. Map them to invoices and shipping bills, submit, and we bring your certificate back, usually in about two hours.
The certificate chase, retired.
An Electronic Bank Realisation Certificate proves your export payment was realised. Getting one used to mean branch visits, portal sessions, and follow-up calls. Now it means this.
Connect DGFT once and every inward remittance appears in the app with a status you can trust: Fresh, Amended, or Cancelled. Nothing to fetch, nothing to re-key.
Map a remittance to its invoice or shipping bill and submit. The certificate is usually back in about two hours, ready for RoDTEP, duty drawback, and GST refund claims.
Every certificate keeps its realised value, GST detail, status, and utilisation. Download the PDF or export the whole ledger to Excel when the auditor calls.
Four steps to a
filed certificate.
One filing at a time, with the typing taken out wherever the details are already known.
Basic Details
Branch, export type, and the particulars every certificate needs. Your two most-used setups save as presets, so repeat filings start pre-filled.
Direct · Softex · Service · DeemedIRM Selection
Pick the inward remittance you are realising against, with its status and available balance in front of you before you commit to anything.
Fresh · Amended · CancelledMapping
Match the remittance to its invoice or shipping bill. Upload a PDF shipping bill and the fields fill themselves, or map the full amount in one click. Deductions, Vostro accounts, third-party exports, and GST fields all live here.
Use Full · PDF auto-fillSummary
Everything on one screen before you submit, with the workspace mode always visible. Submit, and the certificate is usually back in about two hours.
Test or Live · always shownEverything an export desk needs. Nothing it doesn't.
Dashboard, IRM Repository, Generate eBRC, eBRC Reports, Support, and Settings. A tour of the four you will live in.
The IRM Repository: every inward remittance, accounted for
Each Inward Remittance Message lives here with a status you can trust, searchable the way DGFT actually allows.
- Search by IRM number any time, or by date range in windows of up to three months, DGFT's own rule.
- The full record on open. Remitter, country, remittance date, purpose code, PAN, IEC, AD code, IFSC, and currency, with a utilisation bar showing remitted, available, and utilised.
- Refresh on demand to pull your latest remittances, and print any single remittance for the file.
- Export to Excel two ways: a pre-filled bulk template, or raw IRM data.
Bulk eBRC filing, one spreadsheet at a time
Download the template, add your invoice columns, upload it back. Volume without drama.
- Start from your own data. Export remittances straight into the template with export type and branch already filled in; your team only adds the invoice columns.
- .xlsx or .xls, up to 5 MB per file.
- Every row checked before anything is filed. Errors name the row and the field, in plain terms.
- Fix and upload again. Resubmitting never creates a duplicate filing.
billNo: this field is required
currency: use the ISO code, e.g. USD
eBRC Reports: certificates that leave with you
Every certificate listed with its realised value, GST detail, status, and utilisation, and yours to take whenever you want.
- Download the PDF, or copy the eBRC number for bank and DGFT portals.
- GST on every certificate: availed or not availed, with GSTIN and the invoice number and date.
- Five analytics tiles: total realised value, active eBRCs, available balance, utilised, and cancelled.
- Export everything to Excel when the auditor calls.
The Dashboard: realisation at a glance
The state of your export realisation before you open a single certificate.
- Lifetime eBRC totals broken into Active, Available, Utilised, and Cancelled.
- Total realised value across all your certificates.
- Weekly IRM inflow: the remittances that arrived each day this week, by status.
- Recent activity: your latest filings and where each one stands.
Set once. Supported always.
The last two screens do their work quietly: one holds your DGFT connection, the other holds a human who replies.
Link your account a single time, from Settings. The state is always visible: Connected, Action needed, or Not connected. Update your password any time; the stored one is replaced immediately and never shown back to you.
Your two most-used branch and export type setups save as profiles, so repeat filings start pre-filled instead of blank.
File a bug, a feature request, or a question with up to four screenshots attached. A confirmation lands in your inbox, the ticket reference is copyable, and your ticket history stays visible in the app.
Remittances, bulk templates, and the full certificate ledger all export to Excel whenever you want them. Nothing about your records is stuck here.
Practise on a real form before you file for real.
Every workspace has Test and Live. Test submits to a sandbox: same form, same validations, same feedback, and nothing that comes back is legally binding. Switch to Live only when you are ready, and the switch asks you to confirm.
Doing it yourself, or letting the workspace do it.
The certificate is identical either way: a DGFT-issued eBRC against your IEC. The routes differ in whose hands do the routine.
- Sign in for every filing session
- Find each IRM in the repositories by hand
- Check your own entries and chase status yourself
- Keep your own record of what is filed
- Connect DGFT once; no sessions afterwards
- Remittances arrive on their own, with statuses
- Validation, row-level errors, and status-chasing handled
- A ledger that exports to Excel, any time
Weighing the API as well? The full comparison of all three routes is in the easiest way to generate an eBRC.
Trust, stated plainly.
Your DGFT password is never shown back to you, and when you update it, the stored one is replaced immediately. You can change it any time from Settings.
Every row is checked before anything is filed, and errors name the row and the field. Resubmitting never creates a duplicate filing.
PDF downloads, copyable certificate numbers, and full Excel export of the ledger, whenever you want. Your data leaves with you.
You file in minutes. We bring your certificate back, usually in about two hours. We will never tell you otherwise.
File a bug, a feature request, or a question from inside the app, with up to four screenshots attached. A confirmation lands in your inbox, and a real human replies, usually within a day.
Every workspace shows its mode, the switch to Live asks you to confirm, and every certificate records which environment produced it.
Asked, answered.
No. You connect your DGFT account once, from Settings, and from then on your remittances arrive in the app on their own. Filing happens from the guided workspace, and the certificate is still a DGFT-issued eBRC against your IEC.
Your DGFT login and the invoice or shipping bill the payment belongs to. Connect your DGFT account once, from Settings, and your inward remittances arrive on their own. From there, every certificate is a short submission away.
Direct Export, Softex, Service (Non-IT), and Deemed Export. Deductions for commission, discount, insurance, freight, and other charges are supported, along with Vostro account cases and third-party exports. GST invoice fields are captured where applicable.
Search by IRM number any time, or by date range in windows of up to three months, which is DGFT's own rule. A refresh pulls your latest inward remittances on demand.
Yes. Every certificate in eBRC Reports downloads as a PDF, the eBRC number is copyable for bank and DGFT portals, and the whole ledger exports to Excel. Your certificates leave with you whenever you want them to.
One account links one DGFT login. If you run subsidiaries or divisions that each file as themselves, ebrc.in's eBRC API holds many exporter entities under one account. See the Enterprise page for how that fits.
Nothing, ever. The exporter app is free forever, at any volume, and sign-up collects no card. You connect DGFT, file, and download certificates without a bill arriving. The API for enterprises and platforms is a separate product with its own terms.
Your DGFT password is never shown back to you, and when you update it, the stored one is replaced immediately. The connection state is always visible in Settings: Connected, Action needed, or Not connected.
Filing at scale, or for others?
Your export desk, filing at scale
JSON or Excel in, certificates out. Subsidiaries and divisions live as separate entities under one account, each with its own DGFT connection.
See how it fits →The API · For PlatformsCertificates as a feature of your product
Your customers get their certificates. You never touch the portal. One account holds many exporter entities, each filing as themselves.
Read the lifecycle →Guides · ResourcesThe eBRC, explained in plain English
Playbooks and guides on eBRCs, inward remittances, DGFT compliance, and the incentives that depend on realisation.
Read the guides →
Ready to file your next eBRC from here?
Connect DGFT once. Your remittances are already on their way.