IRM Not Showing on DGFT? Why Remittances Go Missing, and the Fix
You cannot certify a certificate against a remittance that is not there. When the money has arrived but the IRM has not, the gap is almost always somewhere on a short, checkable list.
How an IRM is supposed to appear
Since the November 2023 revamp, the flow is bank first: your buyer pays, your AD bank receives and accounts for the money, and the bank transmits an Inward Remittance Message to DGFT electronically. Only then does the remittance appear in your repository, ready to be mapped and certified. If it is not showing, one link in that chain has not done its part yet.
The usual reasons, in the order to check them
1. The bank has not transmitted it yet
Transmission is the bank's action, not yours. Money can sit fully realised in your account while the IRM has not yet been sent to DGFT. This is the most common cause, and the fix is a precise request to your AD bank: please transmit the IRM for this remittance to DGFT.
2. It was reported against the wrong identifiers
The repository shows remittances reported against your identity. A remittance recorded by the bank against a different PAN or account relationship will not surface where you are looking. When you write to the bank, include your IEC and PAN and the remittance reference, so they can check what the IRM was reported against.
3. The remittance went to a different AD bank or branch
Desks that bank with more than one AD, or that changed banks mid-year, sometimes search the wrong place. Confirm which bank actually received the money before assuming the IRM is missing.
4. It is older than the electronic flow
Remittances handled before the revamp lived in a different world. If you are reconciling old realisations, talk to the bank about how those records were carried across rather than expecting them in the new repository.
5. It simply has not landed yet
There is processing time between the bank's transmission and the repository reflecting it. If the bank confirms it has transmitted, search again with a wider date range before escalating.
While you wait: keep the ledger honest
A missing IRM blocks one certificate, not your whole desk. Keep the rest of the repository moving: statuses checked, fresh remittances mapped, and the ledger export current, so the catch-up is one certificate rather than a quarter. The habits are in IRM housekeeping, and the filing flow itself is in how to generate an eBRC, step by step.
In the eBRC workspace, remittances appear on their own once the bank transmits them, each with its status, and you can refresh on demand. What the app cannot do is transmit on the bank's behalf; nobody can. The fix for a missing IRM always runs through your AD bank. Once the remittance lands, mapping and filing take minutes without another portal login; start free whenever you are ready.
Frequently asked questions
Why is my inward remittance not showing on DGFT?
Most often because the AD bank has not yet transmitted the IRM to DGFT. Other causes: the remittance was reported against different identifiers, it sits with a different AD bank, it predates the electronic flow, or it is still in processing. Check with the receiving bank first.
Can I generate an eBRC without the IRM?
No. The certificate is a mapping against a transmitted remittance. Until the IRM exists in the repository, there is nothing to certify against.
What should I ask my bank exactly?
Ask them to transmit the IRM for the specific remittance to DGFT, and give them the remittance date, amount, currency, remitter, and your IEC and PAN so they can locate and report it correctly.
