SWIFT OUR vs SHA vs BEN: Who Pays the Wire Transfer Fees?

Navigating SWIFT Payment Mandates: 'OUR' and 'SHA' in Cross-Border Transactions

For Indian software exporters and IT service agencies, optimizing inward remittances is paramount for revenue realization and compliance. A critical element in this process involves understanding and negotiating the SWIFT payment charge mandates: 'OUR' and 'SHA'. These designations dictate the allocation of bank fees during international wire transfers and significantly impact the net INR equivalent received from foreign clients.

The Society for Worldwide Interbank Financial Telecommunication (SWIFT) network facilitates secure messaging for financial transactions globally. When a foreign client initiates a payment to an Indian beneficiary via SWIFT, the payer's bank typically offers three options for charges:

• 'OUR' (Payer Bears All Costs): Under this mandate, the remitting foreign client explicitly instructs their bank to deduct all associated SWIFT transaction fees, including those levied by intermediary banks and the beneficiary's bank, from the payer's account. The Indian beneficiary is expected to receive the full invoice value, undiminished by bank charges.
• 'SHA' (Shared Costs): This is the most common default mandate. The remitting client covers the charges of their own bank, while the beneficiary (the Indian exporter) is responsible for the charges levied by their receiving bank in India and any fees imposed by intermediary correspondent banks involved in the transaction route.
• 'BEN' (Beneficiary Bears All Costs): In this less common scenario for B2B IT exports, the beneficiary would incur all charges, including those of the remitting bank. For maximizing realization, this mandate is generally unacceptable.

The choice between 'OUR' and 'SHA' directly impacts the gross realization for Indian exporters. Under 'SHA', deductions by correspondent banks (often Nostro account holders for the Indian bank) are unpredictable and can erode profit margins, especially for smaller invoice values.

Commercial Implications for Indian IT Service Exporters

The distinction between 'OUR' and 'SHA' extends beyond mere transaction costs, bearing significant implications for financial compliance, revenue recognition, and administrative efficiency for Indian businesses.

Revenue Realization and Profitability

When an inward remittance is processed under the 'SHA' mandate, the net amount credited to the Indian exporter's designated INR or EEFC (Exchange Earners' Foreign Currency) account is less than the invoiced amount. This direct reduction in received funds impacts the effective hourly rate or project fee, thereby diminishing the profitability of the software export engagement. For businesses operating on tight margins, these deductions can be substantial.

FIRC Acquisition and Compliance Adherence

The Foreign Inward Remittance Certificate (FIRC) is a crucial document for Indian exporters, serving as proof of foreign exchange inflow against export of goods or services. Regulatory bodies, including the Reserve Bank of India (RBI) and tax authorities (for GST purposes), rely on FIRC for verification. If the invoice amount is, for instance, USD 10,000, but due to 'SHA' charges, only USD 9,900 is credited, the FIRC issued by the authorized dealer bank will reflect USD 9,900. This discrepancy between the invoice value and the FIRC value complicates accounting reconciliation and can create ambiguities during audits. For zero-rated supplies under a Letter of Undertaking (LUT), claiming GST refunds or input tax credit requires aligning the export proceeds with the invoice value. A lower FIRC amount necessitates careful documentation to explain the variance.

Administrative Overhead and Reconciliation Challenges

'SHA' transactions introduce an administrative burden. Exporters must meticulously reconcile bank statements with invoices, tracking the exact amount of deductions. This process can be time-consuming, requiring communication with their bank to ascertain intermediary bank charges, which are often not itemized explicitly in the initial credit advice. Such reconciliation efforts divert valuable resources from core business activities.

Strategic Negotiation Framework for the 'OUR' Mandate

Securing an 'OUR' mandate from foreign clients should be a foundational aspect of payment term negotiations for Indian IT exporters.

Proactive Communication in Service Agreements

Integrate explicit clauses regarding payment terms into all service agreements and Statements of Work (SOWs) from the outset. This ensures clarity and mutual understanding before services commence and invoices are generated. A standard clause might stipulate: "All bank charges, including those of intermediary banks and the beneficiary's bank, shall be borne by the client (OUR mandate)."

Articulating the Value Proposition of 'OUR'

Frame the 'OUR' mandate as a standard commercial practice for B2B professional services, particularly in the high-value IT export sector. Explain that the predictability of receiving the full invoiced amount simplifies the beneficiary's accounting, tax compliance (especially for GST under LUT), and ensures transparent billing for services rendered. This is not merely about cost shifting but about establishing clear, predictable financial flows for an international engagement.

Explaining the Opaque Nature of 'SHA' Deductions

Educate foreign clients about the inherent unpredictability of 'SHA' charges. Highlight that intermediary bank fees can vary and are often not transparent to either the payer or the beneficiary at the time of initiation, leading to potential disputes or unexpected shortfalls. Emphasize that 'OUR' eliminates this ambiguity, ensuring the client's payment fully covers the agreed-upon service fee.

Incorporating Clear Payment Instructions on Invoices

Beyond contractual agreements, reinforce the 'OUR' mandate directly on commercial invoices. This can be done through a prominent note: "Payment Terms: All bank charges are to be borne by the sender (OUR). Full invoice value to be credited to the beneficiary account." Providing comprehensive banking details, including SWIFT/BIC code, account number, and bank name, with this instruction reinforces the expectation.

Integrating B2B API Payment Gateways for Optimized Inward Remittances

When securing a direct SWIFT 'OUR' mandate proves challenging or when dealing with clients who prefer alternative payment channels, leveraging specialized B2B API payment gateways can offer a viable alternative for optimizing inbound IT remittances and minimizing overall transaction costs. These platforms often aggregate payments or utilize local payment rails in the client's geography, subsequently disbursing funds to India.

Analyzing Gateway Fee Structures vs. SWIFT Charges

Unlike SWIFT's often opaque intermediary deductions under 'SHA', API gateways typically operate on transparent, percentage-based transaction fees or flat per-transaction charges, coupled with a defined foreign exchange (FX) spread for conversion to INR. For high-volume IT exports, a thorough analysis might reveal that these aggregate gateway fees are lower or, crucially, more predictable than the cumulative charges under an 'SHA' SWIFT transfer. Exporters must scrutinize the total cost of realization, encompassing both the base transaction fee and the FX spread applied by the gateway.

Strategic Client Payment Options and Cost Allocation

Many B2B payment gateways (e.g., those offering virtual local bank accounts in USD, EUR, GBP) enable foreign clients to pay via local bank transfers (like ACH in the US or SEPA in Europe) rather than initiating an international SWIFT transfer. This eliminates the 'OUR' vs 'SHA' discussion for the initial payment leg, as local transfers typically have lower or no fees for the payer. The subsequent SWIFT transfer from the gateway to the Indian beneficiary, or the direct payout via local rails, will then incur the gateway's predetermined fees. The critical negotiation point with the foreign client then shifts from 'OUR' vs 'SHA' to who bears the B2B payment gateway fees. Ideally, the service agreement should stipulate that the client covers all associated gateway fees until the net invoice value is realized in the Indian beneficiary's designated bank account or EEFC account. This ensures consistency in FIRC acquisition for the full invoice value, as the gateway effectively acts as an intermediary, presenting a single, clear deduction on their statement.

Negotiating Preferred Gateway Rates and FX Spreads

Indian exporters, especially those with significant inward remittance volumes, should actively engage in negotiating payout rates and FX spreads with preferred B2B payment gateway providers. Many gateways offer tiered pricing models or custom commercial terms for enterprises, which can substantially reduce per-transaction costs. Diligence in comparing multiple gateway providers based on their API integration capabilities, regulatory compliance, transaction limits, and overall cost structure is essential. This proactive negotiation is key to minimizing the payment gateway fees that ultimately impact the net realization in INR.

Ensuring Robust Banking Compliance and Accounting Accuracy

Effective management of inward remittances necessitates stringent adherence to banking compliance and meticulous accounting practices, particularly when navigating 'OUR' vs 'SHA' mandates or utilizing B2B payment gateways.

FIRC Reconciliation with Invoice Values

Regardless of the payment channel, the FIRC issued by the Authorized Dealer Category-I (AD Cat-I) bank remains the primary document for proof of export earnings. When deductions occur (either due to 'SHA' or payment gateway fees), the FIRC will reflect the net amount credited. Indian exporters must maintain a clear audit trail documenting any deductions from the gross invoice value to the net amount realized. This includes obtaining credit advice from their bank for SWIFT transfers or detailed transaction reports from B2B payment gateways that itemize fees. This robust documentation is crucial for reconciling financial statements and justifying any discrepancies between the invoice amount and the FIRC value for regulatory scrutiny.

GST and LUT Compliance

For IT services categorized as zero-rated supplies under a Letter of Undertaking (LUT), the ability to claim Input Tax Credit (ITC) or GST refunds is contingent on the realization of export proceeds within the stipulated timeframe. If the amount realized (as per FIRC) is consistently lower than the invoice value due to deductions, it can complicate GST compliance and potentially lead to questions during assessments. Maintaining detailed reconciliation statements that explain these variances is vital for demonstrating compliance with GST regulations and substantiating claims.

RBI Reporting and Foreign Exchange Management

RBI guidelines mandate timely reporting of export proceeds. Any variance between the declared export value and the realized amount must be adequately explained and documented. Furthermore, Indian businesses operating EEFC accounts must ensure that the debits for any charges are clearly segregated from the principal amount credited. All foreign exchange transactions must comply with the Foreign Exchange Management Act (FEMA) regulations. Banks, acting as AD Cat-I, play a pivotal role in ensuring this compliance. Exporters should liaise proactively with their bank's trade finance desk for any queries regarding reporting or reconciliation of inward remittances that have undergone deductions.