A third-party payer or payee needs a bank-supported transaction explanation
From 1 October 2026, Regulation 8 of the FEMA Export and Import of Goods and Services Regulations, 2026 allows an Authorised Dealer to permit third-party export/import receipts and payments when satisfied about the transaction’s bona fides. The permission is not automatic because the overseas entities share a parent, an invoice contains a different payee or money has arrived. Identify the actual buyer/seller, the third party, why that party pays or receives, and which commercial obligation the payment discharges.
Use the effective 2026 framework, not superseded checklist text
The primary sources are the 2026 Regulations, amended up to 22 September 2026 and A.P. (DIR Series) Circular No. 20 dated 16 January 2026, both operative from 1 October 2026. Regulation 4(2) requires the AD to be satisfied of genuineness before crediting or debiting the exporter’s or importer’s account and to update or close the corresponding EDPMS/IDPMS entry simultaneously, subject to its specified declaration-based facilities. Regulation 8 supplies the third-party permission. The circular supersedes the listed earlier directions and circulars from that effective date. Do not present an old circular’s documentation checklist as an unchanged universal current requirement without checking its legal status.
A tripartite instruction, group treasury agreement, collection mandate, correspondence or other commercial evidence may help the AD assess the actual arrangement. Which documents are sufficient depends on the transaction and the AD’s current requirements; a document’s title is not a guarantee of acceptance. Regulation 4 also preserves the separate manner-of-receipt/payment framework, while other applicable law and regulatory approvals remain relevant. This article does not turn third-party permission into an exemption from those requirements.
| Identity or amount | What to establish | Record to reconcile |
|---|---|---|
| Contractual buyer/seller | Who owes or is owed the underlying amount | Contract, invoice and trade declaration identifiers |
| Third-party remitter/recipient | Why this person pays or receives for the trade party | Authority, relationship/purpose evidence and AD assessment |
| Receipt/payment | Which invoice portions are settled | Bank references and invoice-currency allocations |
| Remaining balance | What is still unpaid, unexplained or unaccepted | Debtor/creditor ledger and EDPMS/IDPMS status |
Allocate first; do not rename the trade party to match the bank message
Use one invoice-level reconciliation with both the contractual party and actual remitter/payee. A parent-company payment does not require the exporter to pretend that the parent bought the goods. A supplier’s collection agent is not automatically the contractual seller. Obtain confirmation of the commercial discharge and the bank’s required acceptance before treating a payment to another entity as completed trade settlement.
For a pooled remittance, record the invoice number, original currency, gross amount, allocation, bank reference and residual for every invoice. If a receipt can be matched only partly, preserve the unresolved portion instead of closing all invoices by proportion merely to make totals agree. A receipt in a different currency needs an evidenced conversion/allocation basis. Book-currency exchange differences should not be confused with unpaid invoice currency.
Separate money received, commercial discharge and bank reporting
These are three facts to reconcile. Regulation 4(2) requires the AD’s genuineness assessment before account credit/debit and simultaneous reporting update or closure. If the exporter’s records show cash but lack the corresponding bank-accepted allocation or reporting evidence, investigate that discrepancy with the AD; it is not a permitted exception to that requirement. Conversely, a short net credit can reflect charges, an actual short payment or another deduction; investigate its gross-to-net trail. Regulation 6 provides a separate AD process for reduced export realisation. Do not silently label every difference “bank charges” or assume third-party permission itself writes off a residual.
An excess receipt is also not permission to raise a fictitious export invoice or close unrelated entries. Establish whether it is an error, a supported separate payment or another properly documented transaction before allocating or returning it through the appropriate route. For advances, Regulation 10’s routing requirements still need attention. Merchanting trade has its own Regulation 16 conditions; do not apply the ordinary examples as a complete merchanting checklist. The examples assume valid underlying exports/imports and expressly given AD acceptance where stated.
Worked illustrations
These illustrations use fictional facts and expressly stated assumptions. Amounts are Indian rupees unless a different currency or unit is specified. They are independent examples, not findings about any actual client.
Illustrative example 1: A buyer’s parent pays the whole invoice
An exporter invoices Buyer A for USD 60,000. Parent P remits USD 60,000 on A’s behalf. Assume documentary evidence establishes discharge of A’s debt and the AD permits the third-party receipt and accepts the allocation. Allocated realisation is USD 60,000 and the invoice balance is USD 0. Keep A as contractual buyer and P as remitter; do not create a second USD 60,000 sale.
Illustrative example 2: Buyer and third party pay different portions
An USD 80,000 export invoice receives USD 30,000 from the buyer and USD 35,000 from an AD-accepted third party. The accepted total is USD 65,000 and the residual is USD 15,000. A full-settlement label in the sender’s email does not change that arithmetic; resolve any actual reduction separately.
Illustrative example 3: One remittance settles two invoices
Two invoices for the same supported arrangement are USD 45,000 and USD 55,000. A third party sends USD 100,000 and the AD accepts the documented allocations. Allocate USD 45,000 and USD 55,000 separately, leaving each at zero. A single USD 100,000 bank reference can appear on two allocation rows, but it must not be counted as USD 100,000 against each invoice.
Illustrative example 4: An import payee is a supplier’s authorised agent
An importer owes an overseas supplier USD 50,000. With supported seller instructions and AD permission, USD 20,000 is paid to the supplier’s agent and USD 30,000 directly to the supplier. Assume the seller confirms both payments discharge the invoice and the bank accepts the matching. Total accepted settlement is USD 50,000 and the residual is zero; payment evidence must identify both recipients.
Illustrative example 5: A net credit needs gross-to-net evidence
An export invoice is USD 10,000, but the exporter’s bank credit is USD 9,975. The USD 25 difference may be a charge or a short payment; the credit alone does not settle that question. Keep invoice, gross remittance, charges and accepted realisation in separate fields. Until the bank/document review establishes the treatment, do not automatically enter USD 10,000 as accepted full realisation.
Illustrative example 6: An excess receipt is not an additional export
A third party sends USD 7,000 for an invoice of USD 6,000. The excess is USD 1,000. Once the supported USD 6,000 invoice allocation is accepted, keep the USD 1,000 separately unresolved pending its proper treatment. Do not make up a sale or allocate it to another customer’s invoice merely to clear the bank line.
Illustrative example 7: Cross-currency allocation versus INR reconciliation
A supported EUR 25,000 invoice is settled by a third party in USD 27,500. Assume the agreed and bank-accepted conversion basis is USD 1.10 per EUR and no charges arise: USD 27,500 ÷ 1.10 = EUR 25,000, so the invoice-currency balance is zero. For a separate illustrative INR reconciliation, EUR 25,000 at assumed ₹90 and ₹92 gives ₹22,50,000 and ₹23,00,000, a ₹50,000 difference. These are assumed rates, not prescribed rates; that difference does not mean another EUR 25,000 remains unpaid.
Ten-step verification table
| Step | Verification | Evidence to retain |
|---|---|---|
| 1 | Identify the effective framework | Transaction date and current 2026 regulations/directions |
| 2 | Identify the contractual trade parties | Contract, invoice and trade documents |
| 3 | Identify the actual third party | Remitter/payee identity and commercial explanation |
| 4 | Document authority and discharge | Relevant instructions, confirmations and supporting agreement |
| 5 | Obtain the AD’s required assessment/permission | Bank correspondence and accepted conditions |
| 6 | Verify the permitted receipt/payment route | Currency, routing and other applicable requirements |
| 7 | Allocate every accepted amount by invoice | Original-currency allocation and bank-reference bridge |
| 8 | Investigate charges, differences and excesses | Gross-to-net and residual reconciliation |
| 9 | Verify bank reporting status | EDPMS/IDPMS update or closure evidence |
| 10 | Close only supported items and retain exceptions | Ledger reconciliation, unresolved list and follow-up owner |
Sixteen practitioner FAQs
1. Are third-party receipts restricted by Regulation 8 to group companies?
The provision is framed by third-party status and AD satisfaction about bona fides. A group relationship can be evidence but is not automatic permission.
2. Does a common parent remove the documentation need?
No. Explain the actual payment arrangement and establish the relevant commercial discharge.
3. Should the exporter change the invoice buyer to the payer?
Keep the contractual buyer and actual remitter separately identified. Do not rewrite a genuine trade history simply to match a bank name.
4. Is a supplier’s payee-change email enough by itself?
Verify authority, authenticity, commercial discharge and the AD’s required checks before treating the new payee as accepted.
5. Is a tripartite agreement always a statutory guarantee of approval?
No. A document can support the enquiry, but the AD must be satisfied with the actual transaction.
6. Can an old circular checklist be copied into a post-October 2026 file?
Check the supersession and current requirements first. Retain genuinely useful evidence without mislabelling an old condition as current law.
7. Can one remittance be allocated to several invoices?
Use a supported invoice-by-invoice schedule and reconcile its total once to the bank reference.
8. Can the same bank reference be counted in full on each row?
No. The sum of allocations must reconcile to the supported amount available for allocation.
9. Does cash receipt mean every reporting entry can be closed?
The bank’s acceptance and invoice/reporting reconciliation need their own evidence.
10. How should a partial third-party payment be tracked?
Record accepted realisation and residual separately, retaining payer identity for each allocation.
11. Is every short bank credit a permitted reduction?
No. Establish whether it represents charges, short payment or another item and use the applicable bank process.
12. Does third-party permission automatically extend realisation time?
No. Assess any timing extension separately under the applicable provision.
13. Can an overpayment be used to invent a fresh invoice?
No. Preserve the excess as a separately explained item pending proper treatment.
14. What if payment arrives in a different currency?
Keep the original invoice currency, evidenced conversion basis and accepted allocation; reconcile book-currency differences separately.
15. Do these examples establish GST export status or tax treatment?
No. Those have their own statutory conditions and evidence. FEMA bank acceptance alone does not decide them.
16. What proves the file is complete?
A chain from contract and third-party authority to cash, invoice allocation, bank acceptance and reporting status, with all residuals explained or tracked.
Conclusion
A defensible file preserves the contractual parties, actual payment parties and accepted allocation as separate facts. Close the invoice and reporting entry only to the extent the supporting evidence and bank acceptance permit.