Payment Platforms and Indian GST LUT Compliance
Why the exact settlement mechanisms of a payment gateway dictate the ease of proving export status and executing GST zero-rating compliance for Indian IT firms.
The Letter of Undertaking (LUT) is a crucial mechanism for Indian software exporters to execute exports without paying Integrated Goods and Services Tax (IGST) and then claiming a refund. Compliance with LUT requires meticulous documentation of foreign exchange realization and export activities. B2B payment platforms play a pivotal role in facilitating this compliance through their API architectures, MoR logistics, settlement processes, and FIRC generation capabilities.
API Architecture for LUT Documentation
The efficacy of a payment platform for LUT compliance begins with its API architecture. For Indian software exporters, the ability to programmatically retrieve comprehensive transaction data is paramount for GST reporting. Platforms typically offer APIs that provide granular details such as:
- Unique transaction identifiers
- Customer (importer) details including country and company name
- Invoice numbers associated with the export of services
- Foreign currency amounts and the equivalent INR realized
- Date of transaction and date of settlement
- Applicable tax codes or indicators for export of services
An optimally designed API Gateway allows seamless integration with an exporter's Enterprise Resource Planning (ERP) or accounting systems. This automates the aggregation of data necessary for filing GST returns (e.g., GSTR-1 and GSTR-3B), where details of zero-rated supplies under LUT are declared. Platforms with robust webhook functionalities can also push real-time transaction data, reducing manual data entry and potential errors, thereby strengthening the audit trail required for LUT substantiation. The architectural choice for data provision directly impacts the efficiency of reconciliation processes essential for demonstrating LUT adherence.
Merchant of Record (MoR) Logistics and LUT Implications
The choice between a direct Online Payment Gateway Service Provider (OPGSP) and a Merchant of Record (MoR) solution has distinct implications for LUT logistics.
Direct OPGSP Model: In this model, the Indian software exporter remains the legal exporter of record. The OPGSP facilitates the collection of foreign currency and its remittance to the exporter's Authorized Dealer (AD) bank account in India. Here, the exporter is directly responsible for filing the LUT, generating export invoices that clearly state "Supply meant for Export under LUT without payment of IGST," and ensuring all GST compliance. The API architecture provides the data directly related to these export transactions.
Merchant of Record (MoR) Model: With an MoR solution, the foreign MoR entity typically becomes the legal exporter of record. The Indian software entity provides services to the MoR, which then resells these services to the end customers globally. From an Indian GST perspective, the transaction between the Indian entity and the foreign MoR can be treated as an export of services, provided the place of supply is outside India, and consideration is received in convertible foreign exchange. The Indian entity would still leverage an LUT for this service provided to the MoR. The MoR platform's logistics involve managing the end-customer invoicing and tax compliance in multiple jurisdictions. The MoR's API provides payout data to the Indian entity, often consolidating transactions. The challenge for the Indian exporter is to correctly classify the service provided to the MoR for GST purposes and ensure the MoR's documentation (e.g., settlement reports) supports the "export of service" classification for LUT purposes. Platforms vary in the level of detail provided regarding the end-customer transaction versus the consolidated payout to the Indian exporter.
Settlement Timelines and FIRC Generation for LUT
Settlement timelines directly influence the realization of foreign exchange, a core condition for availing LUT benefits. Faster and predictable settlement cycles improve cash flow and simplify reconciliation with FIRC (Foreign Inward Remittance Certificate) generation.
OPGSP Settlement: Direct OPGSPs typically settle funds into the exporter's Indian AD bank account within a few business days post-transaction, adhering to Reserve Bank of India (RBI) guidelines. This direct channel often streamlines FIRC generation, as the AD bank automatically generates the FIRC upon receipt of the foreign inward remittance. Platforms with advanced features may offer automated FIRC generation through their banking partners or provide standardized remittance advice that facilitates FIRC issuance by the exporter's AD bank. The FIRC is a critical document for proving export proceeds realization under the LUT framework.
MoR Settlement: MoR platforms generally operate on a payout schedule (e.g., weekly, bi-weekly, monthly) to the Indian service provider. Payouts might involve a foreign currency balance held by the MoR before conversion and remittance. The settlement timeframe can be longer due to this aggregation and transfer process. For LUT purposes, the FIRC generated by the Indian AD bank upon receiving the MoR's remittance is the primary proof of foreign exchange realization. Platforms differ in how they support this. Some MoR solutions provide consolidated remittance advice that assists the AD bank in generating a single FIRC for multiple underlying transactions. This requires clear mapping in the exporter's accounting records to reconcile the single FIRC against various service invoices issued to the MoR. Challenges can arise if the MoR's documentation lacks sufficient detail for the AD bank to accurately describe the nature of remittance for FIRC.
For both models, the platform's ability to furnish clear, auditable records linking individual transactions or aggregated payouts to the corresponding FIRC is essential for GST audits and maintaining LUT compliance. This includes providing details such as the Unique Transaction Reference (UTR) number, the remitter's name (OPGSP or MoR), the remitted amount, and the purpose code of remittance, which should align with software export services (e.g., P0803 - Computer Services).