What Is a Foreign Inward Remittance Certificate (FIRC)?

What the document proves#

A Foreign Inward Remittance Certificate, usually shortened to FIRC, records a foreign inward remittance to India. Businesses and freelancers use inward-remittance evidence to explain where an overseas receipt came from and connect it to the underlying transaction. The issuer, document name and route matter when that evidence is used for an export or other filing.

Do not treat “FIRC” as a universal attachment automatically available for every international payment. A processing bank may provide inward-remittance advice, a certificate or an electronic document for a supported route. The institution reviewing your export or other transaction determines the evidence it accepts.

FIRC, FIRA and eBRC serve different jobs#

An electronic PDF is a delivery format, not proof that two document types have identical acceptance. If a filing asks for eBRC, obtaining a FIRA does not complete that separate process. If a bank asks for a particular remittance certificate, provide the document for that route and confirm whether an advice or supporting record is acceptable.

Find the institution that processed the foreign leg#

A client’s payment can arrive as INR through a payment provider’s Indian partner bank. Your statement then shows a domestic credit, even though the underlying customer payment originated overseas. Ask the provider for the foreign processing bank, remittance reference and document request path before asking your own bank to issue a certificate it cannot trace.

For direct bank export receipts, use the bank’s trade or export-remittance channel. ICICI’s export services describe remittance linking and an e-FIRC facility. That is an example of a bank workflow, not a promise that every bank uses the same portal, fee or turnaround.

Two Wise routes illustrate why the distinction matters#

Wise’s FIRC help page distinguishes business INR transfers from receipts through Wise Business account details. For the business INR transfer route, the sender can obtain a No Objection Certificate identifying the partner bank; the recipient uses it when requesting FIRA from that bank.

For qualifying receipts through Wise Business account details, the same guidance describes automatic e-FIRC delivery within three business days of processing. It says e-FIRCs are unavailable for other INR transfer types. Indian-business receiving guidance also describes automatic conversion and payout to the verified INR bank account. Apply that timing to the supported product route, rather than all foreign payments to India.

Prepare a request the issuer can match#

• Beneficiary legal name, account and relevant business identifiers.
• Sender name, original amount and currency, receipt date and payment purpose.
• Provider transfer ID and the processing bank’s remittance reference.
• Invoice or contract reference explaining the receipt.
• The document requested and its intended export, bank or filing use.

Use the actual service description and the purpose code applicable to it. A wrong code can create a mismatch in downstream export records; choosing a code merely to obtain a document can make the records less reliable. Ask the processing institution to correct an error at source.

Use DGFT eBRC for the export-realisation workflow#

The enhanced eBRC guide describes banks sending Inward Remittance Messages to DGFT, followed by exporter self-certification against those messages. It includes IRM search, eBRC generation and utilisation records connecting remittances to shipping bills or invoices.

DGFT FAQs distinguish an IRM number from the bank reference and describe eBRC as export-payment confirmation. They also address payments received through platforms such as PayPal or Wise: the exporter can approach the bank for IRM reporting before generating eBRC. That reporting step cannot be replaced by renaming a provider PDF.

For a missing or incorrect IRM, first reconcile the bank reference, beneficiary identifiers, purpose and amount with the bank. For a portal or generation problem after the message is available, use the DGFT support path. Keep document issuance and portal generation as separate exception categories.

Reconcile one receipt without hiding fees or partial payment#

Illustrative receipt: a client pays a $1,000 invoice, and $20 of agreed fees are deducted before $980 is converted to INR. Preserve the gross $1,000, the documented $20 fee, the $980 conversion amount, exchange rate and actual INR credit. Do not invent a gross amount from the final bank credit if the provider does not supply the foreign receipt details.

If one receipt covers several invoices, retain an allocation record showing the amount applied to each. If an invoice is paid in instalments, retain each receipt separately. The bank or DGFT workflow must support the allocation you submit; an accounting spreadsheet alone does not change the issuer’s message.

Keep a retrievable evidence pack#

Store the issuer’s original certificate or advice, payment and bank references, invoice, allocation record and any eBRC alongside the accounting receipt. Keep correction correspondence linked to the original transaction. A payment can be received while documentary follow-up remains open; show those as separate statuses.

Use the retention periods applicable to your tax, export, foreign-exchange and contractual records, plus any active review or dispute hold. There is no single FIRC retention period established here for every transaction. A useful operating policy ensures the evidence remains accessible for the actual obligations it supports.