Generate your eBRC
without the chase.
We took the bank visits, portal sessions, and paperwork out of eBRC generation. Your part takes minutes; the certificate is usually back in about two hours, ready for audits and incentive claims.
Three separate systems demand this certificate.
The eBRC is proof that your export payment was received and realised. Without it, money you have already earned stays out of reach.
RoDTEP and duty drawback are claimed against realised export proceeds. The eBRC is the evidence, and claim windows close on fixed calendar dates.
Export proceeds must be realised within prescribed periods, and inward remittances matched to the exports they pay for. The certificate closes that loop.
Realisation and utilisation records are standard asks in customs and statutory audits. A clean ledger makes audits boring.
You file in minutes.
We do the chasing.
Everything after the connection happens from one workspace. No branch visits, no portal sessions, no follow-up calls.
Connect once
Link your DGFT account a single time, from Settings. The connection state is always visible: Connected, Action needed, or Not connected.
Remittances arrive on their own
Your inward remittances show up in the app without you fetching anything, each with a status: Fresh, Amended, or Cancelled. Refresh on demand.
Map and submit
Match each remittance to its invoice or shipping bill. One certificate at a time, or a whole spreadsheet at once, with every row checked before anything is filed.
Your certificate comes back
You submit in minutes. We return your certificate, usually in about two hours, filed with DGFT and ready to download, with the eBRC number a click away.
Every remittance, accounted for.
Six screens, one job: certificates in hand and claims unblocked.
Your ledger, searchable and statused
The IRM Repository is where every inward remittance lives: searchable by date range or IRM number, opened for full detail, and exported whenever you want it.
- Status on every remittance. Fresh, Amended, or Cancelled, so you always know what is usable.
- Full detail on open. Remitter, country, purpose code, PAN, IEC, AD code, currency, and a utilisation bar.
- Export to Excel as a pre-filled bulk template or as raw IRM data.
One certificate, or a whole spreadsheet
A four-step wizard for single filings. A template for volume. Both end the same way: a certificate.
- Less typing. Mapping fields arrive pre-filled wherever the details are already known.
- Use Full. One click maps the entire remittance amount to the invoice.
- Four export types. Direct Export, Softex, Service (Non-IT), and Deemed Export, with deductions, Vostro, and third-party cases handled where they belong.
- Row-level checks on bulk. Errors come back per row, in plain terms. Fix the file, upload again. Resubmitting never creates a duplicate filing.
billNo: this field is required
currency: use the ISO code, e.g. USD
Your certificates, yours to take
Every eBRC arrives with its realised value, GST detail, status and utilisation, and leaves with you whenever you want it to.
- Download the PDF. Copy the eBRC number for bank and DGFT portals.
- Export the full ledger to Excel when the auditor calls.
- Analytics on top. Total realised value, active eBRCs, available balance ready to utilise, utilised, and cancelled.
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. Nothing is legally binding until you say so, and every certificate records the environment it was filed in.
Three ways in.
File your own, in minutes of your time
Remittances arrive on their own and every certificate is a short submission away, with a Test mode so nothing is legally binding until you say so.
Get started →The API · For EnterprisesYour 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 →Submit once, get a request ID, poll for status.
That is the real contract, and it is a dependable one. The whole certificate lifecycle over REST, built against a real sandbox by default.
Build against a real sandbox. Nothing is legally binding until you switch, and every certificate records which environment produced it.
Production access follows a signed NDA and production agreement, e-signed in the console. Rigour, not friction.
Published per-endpoint rate limits, a request ID on every call, OpenAPI plus cURL for every endpoint, and full DGFT annexures.
Many exporter entities under one account, each with its own DGFT connection. Every customer files as themselves.
Trust, stated plainly.
Link your DGFT account a single time, from Settings. The connection state is always visible: Connected, Action needed, or Not connected.
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. 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.
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. You can file one certificate at a time in a short wizard, or a whole spreadsheet at once.
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.
The eBRC API is ebrc.in's REST interface for platforms and high-volume exporters who 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 free for general use: 250 production certificates a month and up to 10 exporter entities, with sandbox use not metered. For committed volume or customisation, reach us through the contact form for a quote.
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.
Talk to a human.
A question about certificates, the API, or a filing that will not behave: write to us and a real person replies, usually within a day.
- Exporters: stuck filings, missing IRMs, bulk uploads.
- Platforms and enterprises: API access, sandbox keys, and volume or customisation quotes.
- Anything else: we read everything that arrives.
Prefer email? amin@eximfiles.io
Ready to file your next eBRC from here?
Connect DGFT once. File certificates forever after.