Stripe settlements for Indian SaaS and export businesses arrive as inward remittances in USD or EUR, converted to INR at Stripe’s prevailing rate. The reconciliation task is not just matching the payment — it is reconciling the forex conversion rate, generating the FIRC for FEMA compliance, and accounting for the exchange rate difference between the invoice date and the settlement date. This article is for finance teams at Indian businesses — SaaS companies, consultancies, software exporters — that receive international payments via Stripe.
What Stripe India Settlement Involves
Stripe does not hold a payment aggregator licence in India for domestic card processing. Indian businesses use Stripe to accept international card payments in USD, EUR, GBP, and other foreign currencies — primarily for export services such as SaaS subscriptions, software development, and consulting.
Stripe settles payouts to Indian bank accounts as inward remittances via SWIFT. The bank receives the credit in INR after Stripe’s internal conversion, or in some configurations receives USD which the bank converts at its internal rate. The settlement typically takes T+2 to T+7 from Stripe’s payout schedule, depending on the configured payout frequency. Each payout carries a unique payout_id in Stripe’s dashboard, which should be the primary match key for bank reconciliation.
Unlike domestic payment gateways where the primary reconciliation challenge is volume, the stripe india settlement reconciliation challenge is currency. The same transaction is recorded at three potentially different exchange rates: the rate on the invoice date, the rate Stripe uses for conversion at payout time, and the rate the Indian bank applies if the credit arrives in foreign currency before domestic conversion. All three can differ.
How Stripe India Settlement Reconciliation Works
Matching Payout ID to Bank Credit
The first reconciliation step is establishing a one-to-one match between each Stripe payout_id and a bank statement credit line. Stripe’s payout report, downloadable from the Stripe dashboard or via API, lists each payout with its ID, amount in source currency, converted INR amount, and settlement date. The bank statement narration for incoming SWIFT credits includes a reference field where the payout_id, or a truncated version of it, typically appears.
For businesses receiving daily or weekly Stripe payouts, the payout_id match is straightforward. For businesses on monthly payout schedules, the bank statement may show a single large credit that aggregates multiple Stripe charges — in which case the Stripe balance transaction report, which lists all charges included in a payout, is required to tie individual invoices to the bank credit.
Reconciling Forex Rate Differences
The forex rate difference is the most consequential variance in Stripe India settlement reconciliation. The sequence is: (1) invoice issued to international customer in USD at the rate on invoice date; (2) customer pays Stripe in USD; (3) Stripe converts the USD payout to INR at its prevailing rate, which is updated periodically; (4) INR credit arrives in the Indian bank account. Steps 1 and 4 almost never use the same exchange rate.
The difference must be classified as a foreign exchange gain (if Stripe’s rate is higher than the booked rate) or a foreign exchange loss (if lower). This cannot be written off as an unreconciled difference or lumped into fees. Under Indian accounting standards, exchange differences on foreign currency receivables are recognised in profit and loss for the period in which the settlement occurs. Misclassifying forex variance as FEE_DEDUCTION inflates fee expense and understates forex gain or loss.
Generating and Matching FIRC for FEMA Compliance
The Foreign Inward Remittance Certificate is issued by the receiving bank — not Stripe — upon receipt of an inward foreign currency remittance. Indian businesses that export services must obtain FIRC for each inward remittance and maintain it as documentary proof of export proceeds under FEMA. This is particularly important for GST zero-rated export service providers who claim a refund of input tax credit — the FIRC is required documentation in the refund application.
FIRC reconciliation requires matching the FIRC reference number to the corresponding Stripe payout and to the underlying invoices. Banks typically issue FIRC within two to five working days of the credit. Delays in obtaining FIRC create a timing gap in the compliance documentation trail.
Stripe India Settlement: Data Sources and Match Keys
| Data Source | Match Key | Information Provided | Use in Reconciliation |
|---|---|---|---|
| Stripe payout report | payout_id | Payout amount (USD/EUR), converted INR, settlement date | Primary match to bank credit |
| Stripe balance transaction report | charge_id, payout_id | Individual charges aggregated into each payout | Tie invoices to payout |
| Bank statement (SWIFT credit) | payout_id in narration, UTR | INR credit amount, value date | Confirm bank receipt amount |
| FIRC (from receiving bank) | FIRC number, remittance amount | Proof of inward remittance for FEMA | Export compliance documentation |
| Invoice (ERP/billing system) | Invoice number, customer | USD/EUR amount, invoice date rate | Calculate expected forex gain/loss |
India-Specific Compliance Angle
Stripe India settlements fall under FEMA as export proceeds for service exporters. The Reserve Bank of India mandates that export proceeds be realised and repatriated within the prescribed period — typically 15 months from the date of export for software and service exporters, though specific timelines and conditions apply. FIRC from the receiving bank is the accepted documentary proof that proceeds have been realised.
Additionally, if an Indian business makes payments to Stripe for platform fees or other charges, TDS under Section 195 may apply to those outward payments if Stripe is treated as a non-resident payee and the applicable DTAA rate does not exempt the payment. The TDS analysis on outward Stripe fee payments is separate from the reconciliation of inbound Stripe payouts and requires review under the relevant DTAA.
For teams handling multiple international payment channels alongside Stripe, structured payment gateway reconciliation processes that accommodate multi-currency payout matching reduce the risk of forex misclassification. Reconciliation software India finance teams use for export businesses can automate payout_id matching, calculate expected forex gain or loss per payout, and flag missing FIRC documentation. The Reserve Bank of India governs inward remittance compliance and FEMA requirements for export proceeds, including the documentation standards that apply to each Stripe settlement.
Finance teams that have moved to automated Stripe payout reconciliation report improving match rates from 51% to 88%, with deployment in 2–4 weeks through configuration only. Full audit trail functionality — with every match, exception, and manual override time-stamped — supports FEMA documentation requirements and provides evidence for GST zero-rated export refund applications.
The following questions address the compliance and matching issues most frequently encountered in Stripe India settlement reconciliation.