How to Avoid Correspondent Bank Fees on Small Invoices

Navigating Correspondent Bank Fee Erosion on Small B2B Invoices

Cross-border B2B payments for Indian software exporters, particularly those dealing with smaller invoice values typical in freelance or project-based IT engagements, are frequently burdened by opaque and significant correspondent bank fees. These deductions can disproportionately erode margins, complicate FIRC acquisition, and introduce reconciliation challenges for GST and export compliance. Understanding the underlying mechanisms and employing strategic payment architecture are critical for operational efficiency and profitability.

The Anatomy of SWIFT Remittances and Correspondent Fees

International wire transfers, predominantly facilitated via the SWIFT network, rely on a chain of financial institutions. When an overseas client initiates a payment to an Indian exporter's INR account, the funds often traverse one or more intermediary banks, known as correspondent banks. These banks maintain Nostro accounts with each other to settle transactions in various currencies. Each correspondent bank in the payment chain may levy a charge for its service, leading to multiple deductions before the funds reach the beneficiary's bank in India.

The instruction types for fee allocation are critical:

• OUR (Sender Pays All): The sender bears all charges, ensuring the beneficiary receives the full invoiced amount. This is ideal but often resisted by foreign clients due to higher outbound costs.
• SHA (Shared): Sender pays their bank's charges, and the beneficiary pays the correspondent and beneficiary bank charges. This is the default and most common setting, leading to unpredictable deductions.
• BEN (Beneficiary Pays All): The beneficiary absorbs all fees. Rarely used as it places the entire burden on the recipient.

For small B2B invoices (e.g., under $1,000 USD), the fixed component of correspondent bank fees, sometimes augmented by a percentage, can represent a substantial portion of the payment, significantly reducing the effective realization for the Indian exporter. This poses a direct challenge to maintaining competitive pricing and healthy margins.

Impact on Indian Exporters and Compliance

The receipt of an amount less than the invoiced value due to correspondent bank deductions creates several operational and compliance hurdles:

1. FIRC Discrepancies: Acquiring an FIRC for the full invoiced amount becomes complex when the actual inward remittance is lower. Exporters need clear remittance advice detailing all deductions, which is not always readily provided by the sending bank or easily parsed by the receiving bank. This impacts the proof of export realization for various incentives and regulatory filings.
2. GST and LUT Compliance: Under an LUT (Letter of Undertaking), exporters typically supply services without charging IGST. However, the export turnover needs to be accurately reported. If the exporter raises an invoice for, say, ₹80,000 but receives only ₹75,000 after deductions, reconciling this for GST purposes and ensuring proper forex realization reporting becomes cumbersome. The declared export value must align with the received value, or deductions must be transparently accounted for.
3. Profitability Erosion: For high-volume, low-value software export services, these fees cumulatively eat into the bottom line, rendering some projects less viable.

Strategic Mitigation via B2B Payment Architecture

To counter these challenges, Indian software exporters can adopt a multi-pronged approach leveraging modern B2B payment architecture.

1. Payment Aggregation Platforms

FinTech payment aggregators have emerged as a robust solution. These platforms operate by providing virtual local collection accounts (e.g., a USD account in the USA, a EUR account in the Eurozone) to Indian exporters. Foreign clients pay into these local accounts, avoiding the SWIFT network's correspondent bank charges for the initial leg. The platform then aggregates these payments and repatriates them to India in bulk via a single, larger SWIFT transfer to its own Nostro account, or through other optimized channels.

• Cost Efficiency: By aggregating numerous small payments into a single larger transfer, the per-transaction correspondent bank fee burden is significantly reduced. The platform typically charges a transparent, often lower, percentage-based fee on the total repatriation amount, sometimes with a fixed component.
• Simplified FIRC: Many such platforms, especially those integrated with Indian banking partners, can provide consolidated FIRC for the net amount received or detailed reports that help beneficiaries obtain FIRC for the gross invoiced amount with clear deduction breakdowns.
• Streamlined Reconciliation: API-driven payment gateways offered by these platforms can integrate directly with accounting software, automating the reconciliation process and providing clear remittance advice. This eases GST and FEMA reporting.
• Faster Realization: Payments often clear faster than traditional SWIFT transfers, reducing working capital cycles.

2. Batching Invoices and Consolidating Payments

Where feasible, negotiating with clients to consolidate multiple small invoices into a single larger monthly or quarterly payment can dramatically reduce transaction costs. This moves the payment frequency from per-invoice to periodic, effectively mimicking an internal aggregation strategy. While requiring client cooperation, the mutual benefit of reduced transaction costs can be a strong motivator.

3. Advocating for 'OUR' Instruction

For larger clients or projects, explicitly requesting clients to initiate payments with the 'OUR' instruction ensures they cover all intermediary bank charges. While this might slightly increase their outbound cost, it guarantees the Indian exporter receives the full invoiced amount, simplifying FIRC and accounting. This requires clear communication and often negotiation during contract finalisation.

4. Leveraging EEFC Accounts (Limited Scope)

While not directly addressing correspondent bank fees, maintaining an Exchange Earners' Foreign Currency (EEFC) account can help in managing foreign currency receipts. Funds received into an EEFC account can be held in foreign currency, mitigating conversion losses if immediate INR conversion is not required. This is particularly useful for exporters who have foreign currency denominated expenses or wish to hedge against INR volatility. However, the initial SWIFT transfer into the EEFC account is still subject to correspondent bank fees if not routed via an aggregator.

5. API-Driven Bank Integrations

Some Indian banks are enhancing their API capabilities for inward remittances. Exporters can explore integrating their accounting systems directly with their bank's payment APIs to receive granular detail on deductions and faster processing. While traditional SWIFT fees persist, API integration can improve transparency and automated reconciliation, reducing manual effort and errors in FIRC and GST reporting. This infrastructure also lays the groundwork for seamless integration with payment aggregators that often interface with Indian banking APIs for final settlement in INR.

The selection of the optimal payment architecture hinges on transaction volume, average invoice value, client relationships, and internal accounting capabilities. By strategically employing payment aggregators, optimizing payment terms, and leveraging API-driven solutions, Indian software exporters can significantly mitigate correspondent bank fee erosion, enhancing profitability and ensuring robust compliance with Indian foreign exchange and taxation regulations.