Cross-Border Outward Remittance for Indian SaaS Exporters: LRS vs FEMA Business Channel (2026)
SaaS founders cannot pay AWS bills under personal LRS — it is a FEMA violation. Full guide to FEMA purpose codes, Form A2 / 15CA-CB, Section 195 TDS, 18% GST RCM on imported SaaS, SOFTEX reconciliation, and founder dividend repatriation.
- SaaS founders cannot pay AWS bills under personal LRS — it is a FEMA violation. Full guide to FEMA purpose codes, Form A2 / 15CA-CB, Section 195 TDS, 18% GST RCM on imported SaaS, SOFTEX reconciliation, and founder dividend repatriation.
- Use this as a gst & finance updates checklist for cross-border outward remittance for indian saas exporters, not as a substitute for checking current official or platform rules.
- Confirm thresholds, filing dates, forms, documents, and portal guidance against the source links before filing, buying software, changing campaigns, or changing a workflow.
Indian SaaS exporters earn in dollars, euros, and pounds — but their cost base is mostly INR. Once a quarter, every founder asks the same question: how do I move 60-80% of US revenue back to my AWS bill in Mumbai, pay my Slack and HubSpot subscriptions, and remit founder dividends — without tripping RBI's outward remittance limits or the new TCS regime? The 2026 framework changed three things at once: a tightened Liberalised Remittance Scheme (LRS) per-individual cap, a revised Tax Collected at Source (TCS) slab structure under the Income-tax Act, 2025, and a new reconciliation requirement for SOFTEX-linked inflows against outward expense remittances. This guide walks SaaS founders through the legal pathways, the FEMA purpose codes that matter, and the single biggest mistake — co-mingling personal LRS with business outward remittance.
- LRS is personal, not business. Founders cannot use the ₹2.5 lakh-equivalent LRS per-individual cap to pay company SaaS bills — that's a FEMA violation.
- Business outward remittances for legitimate purposes (cloud hosting, software subscriptions, marketing, professional fees) flow via Authorised Dealer Category-I banks under Form A2 with specific FEMA purpose codes.
- TCS on foreign remittance is collected by the AD bank at 20% above ₹7 lakh for most LRS purposes (5% for education and medical) — adjustable as advance tax on ITR filing.
- GST on import of services applies at 18% under reverse charge on SaaS subscriptions (Slack, HubSpot, Notion, Figma, AWS). ITC is fully available if the business is on the regular regime.
- Equalisation Levy was abolished from 1 August 2024, but TDS under Section 195 may apply at 10-20% on royalty / fees for technical services depending on the recipient's tax residency and applicable DTAA.
- SOFTEX reconciliation: software export receipts must be matched against outward remittances — mismatch triggers an Authorised Dealer query and can delay the next inbound credit.
- Founder dividend repatriation goes through a separate route — DDT was abolished from FY 2020-21, but TDS on dividends + LRS limits apply to founder personal accounts.
The Two Channels: Business Remittance vs Personal LRS
The single biggest compliance mistake at Indian SaaS startups is paying for company tools through the founder's personal credit card under LRS. The Liberalised Remittance Scheme exists for resident individuals to remit up to USD 2.5 lakh (~₹2 crore-equivalent) per financial year for personal purposes — overseas travel, education, medical treatment, gifts, investments in foreign securities. It is not a corporate expense channel.
A Private Limited Company or LLP making outward payments for legitimate business purposes must route through an Authorised Dealer Category-I bank with Form A2 (or its simplified online equivalent) declaring the FEMA purpose code, the beneficiary, and the underlying contract. The remittance is reported by the AD bank to RBI under the Single Master Form (SMF) or the relevant FETERS return.
What counts as a legitimate business outward remittance?
- Cloud infrastructure — AWS, GCP, Azure, DigitalOcean, Cloudflare.
- Software subscriptions — GitHub, Slack, Notion, Figma, HubSpot, Salesforce, Atlassian, Linear, Vercel.
- Marketing — Google Ads, Meta Ads, LinkedIn Ads, programmatic platforms.
- Professional fees — overseas consultants, audit, legal, tax advisory.
- Royalty / licence fees — to overseas IP holders.
- Trade payables — import of goods or services not separately classified.
- Reimbursements to overseas subsidiaries / branches under inter-company agreements.
FEMA Purpose Codes a SaaS CFO Should Memorise
The AD bank requires a purpose code on every outward remittance — these flow into RBI's FETERS database. The wrong code triggers a query, delays the remittance, and creates a reconciliation problem at the next inbound credit. The codes most relevant to SaaS exporters:
| Purpose code | Description | Typical SaaS use case |
|---|---|---|
| S0202 / S0203 | Computer services — hardware / software consultancy | Overseas dev contractors, technical consultancy |
| S0205 | Computer software — non-customised packaged software | SaaS subscriptions (GitHub, Slack, Notion) |
| S0306 | Royalty on intellectual property | Licence fees to overseas IP holders |
| S0212 | Information services | Database / market research subscriptions |
| S0301 | Charges for use of intellectual property n.i.e. | Trademark / patent licence payments |
| S1002 | Advertising / market research | Google / Meta / LinkedIn Ads |
| S1006 | Other professional, technical and management consultancy | Overseas consultants, audit, legal, tax |
| S0901 | Repatriation of profits / dividends | Dividend to overseas parent / shareholders |
TCS on Foreign Remittance: The 2026 Slab Structure
Tax Collected at Source on foreign remittance under Section 206C(1G) of the Income-tax Act applies to specified categories of outward remittance. The AD bank collects TCS at the point of remittance and deposits it against the remitter's PAN. The amount is claimable as advance tax against final ITR liability.
| Purpose | Threshold (per FY) | TCS rate | Applies to |
|---|---|---|---|
| Education (loan-funded) | Above ₹7 lakh | 0.5% | Individuals (LRS) |
| Education (self-funded) | Above ₹7 lakh | 5% | Individuals (LRS) |
| Medical treatment | Above ₹7 lakh | 5% | Individuals (LRS) |
| Overseas tour package | Below ₹7 lakh | 5% | Individuals (LRS) |
| Overseas tour package | Above ₹7 lakh | 20% | Individuals (LRS) |
| Any other LRS purpose | Above ₹7 lakh | 20% | Individuals (LRS) |
| Business outward remittance | Not LRS — under FEMA business channel | No TCS u/s 206C(1G) | Companies / LLPs |
The corollary: business outward remittances by a company or LLP under FEMA do not attract Section 206C(1G) TCS. They may, however, attract Section 195 TDS where the payment is income taxable in India in the hands of the non-resident recipient — the most common scenario being royalty and fees for technical services (FTS).
Section 195 TDS: When Your AWS Bill Triggers Indian Withholding Tax
Section 195 requires deduction of tax at source on payments to non-residents where the payment is chargeable to tax in India. The rate depends on the nature of the payment and the applicable Double Taxation Avoidance Agreement (DTAA). For SaaS exporters paying overseas vendors, the typical scenarios:
- Pure SaaS subscription (use of software, no source code access) — historically debated whether classifiable as royalty. The Supreme Court in Engineering Analysis Centre (2021) held that payments for use of off-the-shelf software are not royalty if no copyright is transferred. Most off-the-shelf SaaS today escapes Section 195. AD banks generally accept a no-PE / no-royalty declaration plus Form 15CA-CB for sums above ₹5 lakh per remittance.
- Customised software development / consultancy — FTS under most DTAAs. TDS at 10% (DTAA rate, with valid TRC) or 20% (Section 195 base rate, without TRC).
- Royalty for use of IP — typically 10% under most DTAAs (US, UK, Singapore, Netherlands), 15-20% otherwise. Requires Form 10F + TRC from the recipient.
- Equipment / cloud infrastructure (AWS, GCP) — generally not FTS or royalty post-Engineering Analysis. AD bank accepts a no-PE declaration. Form 15CA-CB still required for amounts above the threshold.
The Forms: 15CA, 15CB, A2, and How They Stack
Every outward remittance above ₹5 lakh in a financial year (per remitter, per remittee, cumulative) needs Form 15CA. Where the remittance is chargeable to tax in India, Form 15CB (a chartered accountant's certificate) is also required. The AD bank cannot release the remittance without these.
- Form A2 — remitter's declaration to the AD bank stating purpose code, beneficiary, amount, and an undertaking on FEMA compliance. Submitted with every outward remittance.
- Form 15CA (Part A) — for remittances below ₹5 lakh / FY cumulative or in the statutory exempt list. Self-declaration filed on the income-tax portal before the remittance.
- Form 15CA (Part B) — where a lower-deduction certificate under Section 195(2) or Section 197 has been obtained.
- Form 15CA (Part C) — where the remittance exceeds ₹5 lakh / FY cumulative and is chargeable to tax. Requires Form 15CB.
- Form 15CA (Part D) — where the remittance is not chargeable to tax (most SaaS subscriptions post-Engineering Analysis). Self-declared on the portal.
- Form 15CB — CA certificate certifying the chargeability assessment and TDS rate. Required only for Part C remittances.
GST on Import of Services: The 18% RCM Trap
Import of services into India is taxable under GST as a "supply" under Section 7(1)(b) read with Schedule I of the CGST Act. The Indian recipient discharges the tax under Reverse Charge Mechanism (RCM) at the time of payment or invoice (whichever is earlier). The standard rate is 18%.
So your ₹2 lakh AWS bill triggers ₹36,000 of GST under RCM. The good news: if your business is registered under regular GST and the input is used for taxable outward supplies, the ₹36,000 is fully available as Input Tax Credit. Net cash impact is timing-only — you pay GST in cash in month M, claim ITC in month M+1.
RCM on imports — common SaaS line items
| Service | Vendor location | RCM applicable? | Rate |
|---|---|---|---|
| AWS / GCP / Azure | USA | Yes | 18% |
| Slack / Notion / Figma / HubSpot | USA | Yes | 18% |
| Cloudflare | USA | Yes | 18% |
| Google Ads | Google India Pvt Ltd (often) | Forward charge by Google India | 18% |
| Meta Ads | Meta India / Ireland | Depends on contracting entity | 18% |
| LinkedIn Ads | Microsoft Ireland | RCM | 18% |
| Consultancy fees to overseas firm | Any non-India | Yes | 18% |
Common error: SaaS exporters under the LUT / Bond regime treat their outward export of services as zero-rated and incorrectly assume the import side is also exempt. It is not. RCM applies on every overseas SaaS payment. Input tax credit rules cover the reclaim workflow.
SOFTEX and the Inflow-Outflow Reconciliation
Indian software exporters declare each export contract via the SOFTEX form filed with STPI or SEZ authority. The form generates a SOFTEX reference number that must be quoted on every inward remittance from the foreign customer. The AD bank reconciles SOFTEX-declared exports against actual realisation; outstanding receivables beyond 9 months require RBI extension.
The 2026 update tightened the reconciliation. AD banks now match aggregate SOFTEX inflows against outward remittance pattern at quarterly intervals. Anomalies — large outward remittances to related parties without commensurate inflows, or sudden spike in advertising / consultancy remittance not aligned with revenue scale — trigger compliance queries.
- Maintain a quarterly tracker: SOFTEX filed value, actual inward realisation, outward remittance by purpose code.
- Tag every outward remittance with the SaaS product, the cost centre, and the contract reference.
- Run a quarterly review against revenue — outward as % of inward by category.
- Flag related-party remittances (to subsidiaries, founders' overseas entities) separately for transfer pricing review.
- Retain Form A2, 15CA/CB, invoice, contract, and bank advice for at least 6 financial years.
Founder Dividend Repatriation
Indian SaaS founders with overseas shareholders or holding-company structures eventually face the question: how do we repatriate profits to the parent? Dividend Distribution Tax was abolished from FY 2020-21 — but TDS on dividends under Section 194 / 195 applies at the time of payment.
- Dividend to resident shareholder — TDS at 10% above ₹5,000 / FY.
- Dividend to non-resident shareholder — TDS at 20% (Section 195) or DTAA rate (typically 10-15%) on production of TRC.
- Remittance route — AD bank, Form A2 with purpose code S0901, Form 15CA-CB if chargeable to tax.
- RBI approval — generally automatic for paid-up capital + free reserves; specific approval needed for buy-back beyond limits.
Founders with personal LRS exposure (overseas property, foreign equity investments) need to keep personal and business channels strictly separate — the income-tax portal now cross-references LRS utilisation reported by AD banks with the dividend / salary income declared in ITR.
Common Mistakes That Cost SaaS Startups Time
- Paying company SaaS bills via founder's personal card under LRS. FEMA violation. Penalties + retrospective compliance burden.
- Mis-coding purpose codes — using S0205 (software) when the actual contract is S1006 (consultancy). AD bank query, remittance delay.
- Missing GST RCM on imports — biggest assessment risk at first GST audit. Interest + penalty stack quickly.
- No 15CB for taxable remittances — AD bank refuses release; payment fails customer expectation.
- Ignoring the no-PE declaration requirement — without it, AD bank applies the higher 20% Section 195 rate by default.
- Stale SOFTEX filings — outstanding software exports beyond 9 months without extension triggers RBI compliance query.
- Co-mingling related-party remittances with arm's-length vendor payments — transfer pricing exposure.
How Bizeract Helps Indian SaaS Exporters
Our team works with SaaS founders to map outward remittance flows, set up correct purpose codes, automate Form 15CA filings via the income-tax portal, and reconcile SOFTEX inflows against expense outflows. We also configure GST RCM workflows in Tally and Zoho Books so monthly imports auto-trigger the right tax entry. Get in touch if you're scaling past $1M ARR and need a CFO-grade cross-border compliance set-up.
Frequently Asked Questions
Can I pay my company's AWS bill from my personal credit card under LRS?
No. LRS is a personal remittance scheme for resident individuals. Paying corporate expenses via LRS is a FEMA violation. Company expenses must route through an Authorised Dealer Category-I bank with Form A2 under the relevant business purpose code (S0205 for SaaS, S0202/S0203 for computer services, S1002 for advertising).
Do I deduct TDS under Section 195 on my Slack and HubSpot subscription?
Generally no. The Supreme Court in Engineering Analysis Centre (2021) held that payments for use of off-the-shelf packaged software without source-code access are not royalty under Section 9(1)(vi). Most SaaS subscriptions today fall outside the Section 195 net. File Form 15CA Part D with a no-PE declaration. For customised consultancy or development work, FTS / royalty TDS at the DTAA rate applies.
What is the TCS rate on outward remittance for a company?
TCS under Section 206C(1G) does not apply to business outward remittance by a company or LLP under FEMA. The 20% TCS slab (above ₹7 lakh) applies to individuals remitting under LRS. Companies route through the FEMA business channel where Section 195 TDS (if applicable) is the relevant withholding, not TCS.
Is the 18% GST on imported SaaS recoverable as input tax credit?
Yes, if the business is on the regular GST regime and the input is used for taxable outward supplies (including zero-rated exports under LUT). Pay GST in cash under RCM at the time of import, claim ITC in the next return. Net cash impact is timing-only. Composition-scheme taxpayers cannot claim ITC and absorb the 18% as cost.
What is the SOFTEX form and when do I need to file it?
SOFTEX is the declaration form filed by Indian software exporters with STPI (Software Technology Parks of India) or the SEZ Development Commissioner for every export contract. It generates a SOFTEX reference number quoted on inward remittances. Mandatory for all software exports irrespective of value; the AD bank cannot credit foreign realisation without it.
Does the Equalisation Levy still apply on Google Ads and Meta Ads?
The 2% Equalisation Levy on e-commerce supply / services was abolished with effect from 1 August 2024 under the Finance (No. 2) Act, 2024. The 6% Equalisation Levy on online advertisement payments to non-residents was abolished even earlier. Today, ads spend on Google / Meta / LinkedIn is subject only to GST under RCM (where applicable) and Section 195 TDS rarely applies to ad-spend payments to platform entities.
How do I repatriate profits to my overseas holding company without losing money to tax?
Dividend repatriation route: AD bank with purpose code S0901, Form A2, Form 15CA-CB. TDS at the applicable DTAA rate (typically 10-15%) on production of Tax Residency Certificate (TRC) and Form 10F from the parent. Alternative routes — share buy-back, royalty under licence agreement, management fee under service agreement — each has transfer pricing and tax-residency considerations. Plan with a cross-border tax advisor before scaling.
What should you verify before using this GST & Finance Updates guide?
Before acting on cross-border outward remittance for indian saas exporters, verify the current rules or platform behavior with the GST Portal. The practical answer depends on your business model, state, turnover, documents, software stack, and whether the decision affects tax, customer data, paid media spend, or a production workflow.
Use this article as a working checklist, then confirm thresholds, registration status, return forms, document rules, and portal notices. In our audits, most expensive mistakes do not come from ignoring the whole process. They come from one stale assumption, one mismatched address, one missing event, or one automation path that nobody tested after launch.
| Checkpoint | Why it matters | Where to confirm |
|---|---|---|
| Current rule or platform status | Limits, forms, policies, and APIs can change after a blog update. | GST Portal |
| Your exact business case | A local shop, freelancer, D2C store, agency, and SaaS team rarely need the same next step. | Documents, invoices, campaign data, analytics setup, or workflow logs |
| Implementation evidence | The safest GST decision is backed by proof, not memory or screenshots from an old setup. | Portal acknowledgement, dashboard export, invoice sample, test lead, or error log |
How do we apply this in real business work?
We start with the smallest decision that can be verified. For compliance work, that means matching PAN, address, bank, invoices, and portal status before filing. For websites, marketing, analytics, and automation, it means testing the real user path from first click to final record. The boring checks catch the costly failures.
A useful rule: if a claim changes money, tax, reporting, or customer communication, keep evidence for it. Save the acknowledgement, export the report, test the form, and note the date you verified the source. That gives you a clean trail when a client, officer, platform, or internal team asks why the setup was done that way.
When should you get expert review?
Get expert review when the next action can create tax exposure, lost reporting data, ad waste, broken customer communication, or production downtime. A simple self-check is enough for low-risk learning. A filed return, new registration, tracking migration, paid campaign restructure, or live automation deserves a second set of eyes before it affects customers or records.
How often should this be rechecked?
Recheck the decision whenever your turnover, state, product mix, campaign budget, website stack, analytics property, or workflow ownership changes. Also recheck it after major portal updates, platform policy changes, annual filing deadlines, and vendor migrations. The guide is useful today only if the facts behind it still match your business.
What is the fastest safe way to decide?
Write the decision in one sentence, list the proof needed for that sentence, and verify only those items first. This keeps the work focused. If the proof confirms the decision, proceed. If one item is unclear, pause and resolve that point before changing filings, campaigns, tracking, website code, or automation logic.
What can go wrong if you skip verification?
The usual failure is not dramatic at first. It looks like a rejected application, a wrong tax invoice, a missing conversion, a duplicate lead, a broken report, or a workflow that silently stops. Those small failures become expensive when nobody notices them until month-end reporting, filing day, or a customer escalation.
What evidence should you keep after making the change?
Keep enough evidence to reconstruct the decision later. For a compliance topic, that usually means the application reference number, registration certificate, invoice sample, return acknowledgement, payment challan, notice reply, or source link checked on the day of filing. For a website, campaign, analytics setup, or automation, keep the before-and-after screenshot, test submission, dashboard export, webhook log, and the exact setting that changed.
This matters because most business fixes are revisited months later, when nobody remembers the original reason. A short evidence trail makes audits faster, handovers cleaner, and vendor conversations more precise. It also keeps the advice in this guide tied to your real operating context instead of becoming a generic checklist that gets copied without review.
- Date checked: record when the official source, dashboard, or portal screen was reviewed.
- Business context: note the entity, state, product, campaign, property, or workflow affected.
- Proof of action: save the acknowledgement, report export, test result, or live URL.
- Owner: assign one person to re-check the item when rules, tools, or business volume change.
Which next step should you take after reading this?
Turn the article into one action list. Mark what is already true, what needs proof, and what needs expert review. If you want to go deeper, compare this guide with Input Tax Credit (ITC) Rules in GST: Full Guide for 2026, RBI New Rules April 2026: 2FA Mandate, NBFC TDS & Cash Reporting — A Business Guide, and TDS on NBFC Interest: Section 194A Rules, 10% Rate & Section 40(a)(ia) Disallowance (2026). Then update the decision only after the official source and your own records agree.
Frequently asked questions
Can I pay my company AWS bill from my personal credit card under LRS?
No. LRS is a personal remittance scheme for resident individuals up to USD 2.5 lakh per financial year for personal purposes — overseas travel, education, medical, investments. Paying corporate expenses via LRS is a FEMA violation. Company expenses must route through an Authorised Dealer Category-I bank with Form A2 under the relevant business purpose code (S0205 for SaaS, S0202/S0203 for computer services, S1002 for advertising).
Do I deduct TDS under Section 195 on Slack and HubSpot subscriptions?
Generally no. The Supreme Court in Engineering Analysis Centre (2021) held that payments for use of off-the-shelf packaged software without source-code access are not royalty under Section 9(1)(vi). Most SaaS subscriptions today fall outside the Section 195 net. File Form 15CA Part D with a no-PE declaration. For customised consultancy or development work, FTS/royalty TDS at the DTAA rate applies (typically 10% with valid TRC, 20% without).
What is the TCS rate on outward remittance for a company?
TCS under Section 206C(1G) does not apply to business outward remittance by a company or LLP under FEMA. The 20% TCS slab (above ₹7 lakh) applies to individuals remitting under LRS — 5% for education and medical. Companies route through the FEMA business channel where Section 195 TDS, if applicable on the underlying income, is the relevant withholding instead of TCS.
Is 18% GST on imported SaaS recoverable as input tax credit?
Yes, if the business is on the regular GST regime and the input is used for taxable outward supplies (including zero-rated exports under LUT). Pay GST in cash under RCM at the time of import, claim ITC in the next return. Net cash impact is timing-only. Composition-scheme taxpayers cannot claim ITC and absorb the 18% as cost.
What is the SOFTEX form and when do I need to file it?
SOFTEX is the declaration form filed by Indian software exporters with STPI (Software Technology Parks of India) or the SEZ Development Commissioner for every export contract. It generates a SOFTEX reference number quoted on inward remittances. Mandatory for all software exports irrespective of value; the AD bank cannot credit foreign realisation without it. Outstanding software exports beyond 9 months require RBI extension.
Does the Equalisation Levy still apply on Google Ads and Meta Ads?
No. The 2% Equalisation Levy on e-commerce supply and services was abolished from 1 August 2024 under the Finance (No. 2) Act, 2024. The 6% Equalisation Levy on online advertisement payments to non-residents was abolished earlier. Today, ads spend on Google/Meta/LinkedIn is subject only to GST under RCM where applicable; Section 195 TDS rarely applies to ad-spend payments to platform entities.
How do I repatriate profits to my overseas holding company?
Dividend repatriation route: AD Category-I bank with purpose code S0901, Form A2, Form 15CA-CB. TDS at the applicable DTAA rate (typically 10-15%) on production of Tax Residency Certificate (TRC) and Form 10F from the parent. Alternative routes — share buy-back, royalty under licence agreement, management fee under service agreement — each has transfer pricing and tax-residency considerations. Plan with a cross-border tax advisor before scaling.
Let's talk about your business.
Tell us what you're working on and where you want to go. We'll put together a plan. No obligation, no sales pitch.
- Free 30-minute call
- A plan built around your goals
- No obligation, no pressure
- Your own account manager