Third Party Payment for Exports RBI: Rules & Compliance
TL;DR - Summary
- What is a third-party payment for exports? - A third-party payment for exports is a payment where the entity that remits money to the Indian exporter is different from the entity named on the export invoice.
- Does RBI allow a third-party payment for exports? - Yes, RBI permits a third-party payment for exports, and a payer name on the SWIFT that differs from the invoice buyer is not automatically a compliance violation.
- What conditions and documentation apply to a third-party payment for exports under RBI rules? - A third-party payment for exports is acceptable when the relationship between the payer and the buyer is properly documented, and you submit a relationship letter, SWIFT confirmation and a written explanation of the payer arrangement to your AD bank.
- How do you stay FEMA-compliant when a third-party payment for exports comes from a payer who is not the buyer? - To stay FEMA-compliant when the payer is not the buyer, contact your AD bank ideally before the wire is sent, submit the payer documentation, and notify the bank on the day the payment arrives, or at the latest the following business day.
What Is Third-Party Payment for Exports?
A third-party payment for exports happens when the entity that remits money to the Indian exporter is different from the entity named on the export invoice. You invoiced one company, and the payment arrived from another.
This situation is commercially normal for Indian exporters dealing with multinational groups, where a group treasury entity centralizes outward payments on behalf of the actual buyer.
For example, a Pune-based IT services firm invoices its US client for $5,000, but the wire arrives from the client's Singapore-based group treasury. The payer name on the SWIFT does not match the invoice buyer, which creates a name mismatch that requires documentation under Indian foreign exchange law.
Does RBI Actually Allow Third-Party Export Payments?
Yes, RBI permits third-party payments for exports, subject to specific conditions and supporting documentation. A name mismatch between the payer on the SWIFT and the buyer on the invoice is not automatically a compliance violation.
When the payer's name differs from the invoice buyer, the payment isn't illegal. Documentation is what's required. Under RBI Master Direction, a remitter name that does not match the invoice buyer is acceptable when the relationship between the payer and the buyer is properly documented.
If you receive international payments in India from a payer other than the invoiced buyer, that payer's relationship to the buyer is what you document.
The permission has limits. Third-party payments are not permitted if the payer's country is on the RBI sanctions list, or if the arrangement is structured to obscure the ultimate beneficiary.
What Conditions Must Be Met Under RBI Master Direction?
Under RBI Master Direction, a third-party payment for exports is acceptable when the relationship between the payer and the buyer is properly documented, and the documents go to your AD bank. It is not permitted if the payer's country is on the RBI sanctions list or if the arrangement is structured to obscure the ultimate beneficiary.
The core documents are:
- Relationship or declaration letter: from the overseas buyer, confirming the third-party payer's authority
- Export invoice: for the shipment or service being paid
- SWIFT confirmation: showing the remitter's details
- Written explanation: of the payer arrangement, submitted to your AD bank
Before you accept the payment, verify the payer's country and the arrangement itself. Contact your AD bank's trade finance or foreign exchange desk proactively, ideally before the wire is sent.
If a group entity will pay on the buyer's behalf, settle that alongside your payment terms in export.
✅ PRO TIP
Always get a signed declaration from both the overseas buyer and the third-party payer before the payment is sent. Retrofitting this documentation after the wire lands is difficult and can delay settlement.
Direct Buyer Payment vs. Third-Party Payment: What Changes?
In a direct buyer payment, the remitter name on the incoming SWIFT matches the buyer named on the export invoice, so you need no documentation beyond your standard export paperwork. In a third-party payment, the names don't match, which triggers a documentation requirement under Indian foreign exchange law to explain and evidence the payer relationship. Bank scrutiny is higher, EDPMS closure needs explicit invoice-to-remittance mapping, and timeline risk is higher if documents are delayed.
| Parameter | Direct Buyer Payment | Third-Party Payment |
|---|---|---|
| Remitter name vs. invoice buyer | Match | Mismatch |
| Additional documentation required | No | Yes - relationship letter, SWIFT, written explanation |
| Bank scrutiny level | Standard | Higher |
| EDPMS closure complexity | Straightforward | Requires explicit invoice-to-remittance mapping |
| Timeline risk | Lower | Higher if docs are delayed |
| Foreign Inward Remittance Certificate (FIRC) naming | Reflects buyer/remitter (same entity) | Reflects third-party remitter - must be reconciled to buyer invoice |
Who will actually send the money is worth settling when you agree international payment terms with a buyer.
- Bank scrutiny: Scrutiny is higher for third-party payments. Contact your AD bank's trade finance or foreign exchange desk, ideally before the wire is sent, and submit a relationship letter, SWIFT confirmation and a written explanation of the payer arrangement.
- EDPMS closure: The bank must link the inward remittance to a specific invoice. With a direct payment this is straightforward. With a third-party payment, you provide the invoice number, export date and supporting references to help the bank complete the match.
- Service exports: A service export has no shipping bill number, so the invoice reference becomes even more critical when the payer is a third party.
- Timeline: Delays occur if documentation is not submitted promptly. Notify the bank on the day the payment arrives, or at the latest the following business day.
💡 QUICK INSIGHT
Banks handle proactive disclosures far more smoothly than reactive ones, so reach out before the wire.
How Should the FIRC Be Handled When the Payer Is Not the Buyer?
When the payer is not the buyer, the FIRC carries the third-party remitter's name, and RBI Master Direction accepts this when the relationship between the payer and the buyer is properly documented. You document and retain the link between the FIRC and the correct buyer invoice, and you request the e-FIRC only after the bank has closed the EDPMS entry.
Keep the reconciliation link between the FIRC and the correct buyer invoice documented and retained. You need that documentation for compliance and GST refund purposes.
An e-FIRC (electronic Foreign Inward Remittance Certificate) is the digital proof that export proceeds were received. It is issued after the bank processes the payment and closes the EDPMS entry. Request it only after EDPMS closure, so the certificate correctly references the matched invoice.
Many exporters assume that if the remitter name on the SWIFT does not match the invoice buyer, the FIRC is non-compliant. Under RBI Master Direction, this is acceptable when the relationship between payer and buyer is properly documented.
How Does Skydo Handle Third-Party Export Payments Compliantly?
Third-party export payments create a documentation and reconciliation burden that traditionally requires multiple rounds of communication with an AD bank's RM. That burden lands on you at the moment a payment arrives from a payer who isn't the invoiced buyer.
Skydo is one of the cross-border payment companies in India and a SWIFT payment alternative that removes this operational friction by handling compliance documentation digitally.
- Free FIRC: Skydo issues a free FIRC for every transaction. There are no bank RM calls and no chasing a SWIFT copy, even when the payer structure is non-standard.
- Free FIRA: Skydo provides free FIRA certificates for every transaction, giving you verifiable proof of receipt that links the inward remittance to the correct export invoice.
- EDPMS closure assistance: EDPMS closure is a common pain point when the payer is not the buyer. Skydo offers EDPMS closure assistance, so you don't need to coordinate manually with a bank to match remittances to shipping bills or invoices.
- eBRC closure assistance: Link your DGFT account as a one-time activity, then bulk upload shipping bills to auto-map IRMs and generate eBRC in a click. No manual follow-up is required.
- Free virtual accounts: Skydo offers free virtual accounts in USD, EUR, GBP, SGD, AUD and CAD, so you can receive payments from overseas buyers or their third-party payers into a dedicated account without a new bank relationship.
- Setup: Setup takes 10–15 minutes.
- Support: Support is India-based and available over WhatsApp, call and text. There is no global queue and no waiting on an international helpdesk when a non-standard payment arrives.
Pricing is transaction-based, with no monthly fees. You pay only when you transact.
| Payment Amount | Skydo Fee |
|---|---|
| Under $2,000 | $19 flat |
| $2,000–$10,000 | $29 flat |
| Over $10,000 | 0.3% |
What is a third-party payment in export under FEMA?
A third-party export payment under FEMA occurs when the remitter of export proceeds is an entity different from the overseas buyer named on the invoice. It is permissible under specific RBI conditions with supporting documentation.
What documentation must an Indian exporter keep for a third-party payment?
Does the FIRC name the actual buyer or the third-party payer?
What happens if I don't inform my bank before a third-party payment arrives?
Are third-party export payments allowed from any country?
How does EDPMS closure work when the payer is not the buyer?
What is an e-FIRC and when should I request it?
Can I use a payment aggregator like Skydo for third-party export payments?
