Foreign SaaS Payments from India: TDS, 15CA/15CB and GST RCM Checklist

Indian startups often treat foreign SaaS payments as normal operating expenses: AWS, Google, Microsoft, Notion, HubSpot, Stripe tools, GitHub, analytics software, design subscriptions, overseas consultants, ad platforms, cloud hosting, app stores, and marketplace vendors.

Operationally, that is true. Compliance-wise, it is not always simple.

The pain usually appears at the worst time. A bank asks for Form 15CA, a CA certificate, a tax invoice, a purpose code, or proof of tax deduction before releasing a remittance. The accounts team then discovers that some invoices were paid by credit card, some were booked net of tax, some have no Tax Residency Certificate, and some have never been reviewed for GST reverse charge.

This is why foreign vendor payment cleanup is a commercial-intent problem, not just a compliance problem. A company that pays overseas vendors every month needs a repeatable process before the next payment, not a one-time scramble.

The Risk: One Missed Step Can Create Four Different Problems

Foreign SaaS and overseas service payments can create issues under multiple tracks at once:

• Income-tax TDS under payments to non-residents
• Form 15CA and Form 15CB documentation for remittances
• GST reverse charge on import of services
• Accounting classification and audit trail issues
• Bank documentation delays during outward remittance
• Withholding tax gross-up disputes with vendors

The cost is rarely limited to the tax amount. The real cost is friction. A delayed cloud or software payment can affect business continuity. A missed TDS review can become an assessment exposure. Missing GST RCM can distort ITC and expense numbers. Weak documentation can slow down audit, due diligence, and investor reporting.

For a foreign-owned Indian subsidiary, this also reflects badly on the first-year India setup. The parent company may assume the Indian entity is "fully operational" after incorporation, GST registration, and bank account opening. In reality, overseas payment compliance needs its own workflow.

Step 1: Classify the Payment Before Paying

Do not start with the invoice amount. Start with the nature of payment.

For every overseas vendor, identify:

• What is being purchased: software access, cloud hosting, royalty, technical service, consultancy, marketing service, subscription, data, license, reimbursement, or goods
• Who is the payee: foreign company, non-resident individual, group entity, marketplace, or payment aggregator
• Where the service is used: India, outside India, or mixed use
• Whether the vendor has an Indian GST registration or local invoicing entity
• Whether the payment is made by bank remittance, card, platform deduction, or group recharge
• Whether the contract says payment is net of withholding tax or tax must be borne by the Indian payer

This classification drives the next three decisions: TDS, Form 15CA/15CB, and GST RCM. If the classification is wrong, every later step becomes weak.

Step 2: Check TDS and Treaty Documents

Section 195 broadly requires tax deduction when a payment to a non-resident or foreign company is chargeable to tax in India. The practical question is not "Is this foreign?" The practical question is: is the income chargeable in India, and if yes, at what rate?

For SaaS and software payments, teams often jump to a blanket answer. That is risky. Depending on facts, contracts, treaty position, and the nature of rights granted, the payment may need review as royalty, fees for technical services, business income, reimbursement, or another category.

Before payment, collect and review:

• Vendor legal name, country, and registered address
• Invoice and contract or online terms
• Tax Residency Certificate, where treaty benefit is claimed
• Form 10F and no-PE declaration, where relevant
• PAN, if available
• Nature of service and usage notes
• Whether payment terms include gross-up

If TDS applies and the company does not deduct it correctly, the exposure can include tax, interest, disallowance risk, and follow-up notices. If the company deducts tax unnecessarily, the vendor may dispute the short payment or block service renewal. Both outcomes are avoidable if the review happens before payment.

Step 3: Decide Whether Form 15CA/15CB Is Needed

Form 15CA is an information statement for certain payments to non-residents or foreign companies. Form 15CB is a CA certificate used in relevant cases to support the tax position for remittance.

The important point is that Form 15CA/15CB is not a cosmetic bank form. It connects the remittance, nature of payment, taxability position, TDS rate, treaty claim, and supporting documents. Banks may ask for it before processing outward remittance, and weak preparation can delay payment.

For each payment, check:

• Is the payment chargeable to tax in India?
• Is the payment covered by an exemption category under the applicable rules?
• Has TDS been deducted, or is the position that no tax is deductible?
• Is aggregate payment to the vendor crossing the threshold where a CA certificate is needed?
• Are invoice, agreement, TRC, Form 10F, and no-PE declaration available?
• Does the remittance purpose code match the actual nature of payment?

For recurring SaaS vendors, build a vendor-wise file. Reusing the same analysis every month is faster than recreating it during every bank remittance.

Step 4: Review GST RCM and Accounting Entries

Overseas service payments may also trigger GST reverse charge if they qualify as import of services. The fact that the vendor is outside India does not automatically close the GST question. You need to review place of supply, recipient location, business use, and whether the vendor has an Indian GST registration.

For accounting cleanup, check:

• Was GST RCM booked on import of services where applicable?
• Was RCM paid through cash ledger and then claimed as ITC, where eligible?
• Was the expense booked gross or net of TDS?
• Was TDS payable recorded separately?
• Were foreign exchange differences captured correctly?
• Were card payments and platform deductions recorded with invoice-level detail?
• Were vendor ledgers reconciled with bank/card statements?

This matters because GST, TDS, and accounting entries should tell the same story. If books show a software expense, the bank file says technical services, TDS was not reviewed, and GST RCM is missing, the file is not audit-ready.

Practical Cleanup Checklist

• Create a list of all foreign vendors paid in the last 12 months.
• Separate SaaS subscriptions, cloud hosting, software licenses, consultants, marketing platforms, group recharges, and reimbursements.
• Mark payment mode: bank remittance, credit card, debit card, platform deduction, or intercompany adjustment.
• Collect invoices, contracts, online terms, TRC, Form 10F, and no-PE declarations where treaty benefit is considered.
• Review whether each payment is chargeable to tax in India.
• Decide TDS section, rate, treaty position, surcharge/cess impact, and gross-up treatment.
• Check whether Form 15CA and/or Form 15CB was filed where required.
• Match Form 15CA/15CB details with bank remittance purpose codes.
• Review GST RCM applicability for import of services.
• Reconcile RCM payment and ITC claim in GSTR-3B and books.
• Check whether expenses were booked net or gross of TDS.
• Reconcile vendor ledgers with bank, card, and payment gateway statements.
• Prepare a standard approval note for recurring vendors.
• Build a monthly overseas payment control sheet before the next remittance.

Want to clean up foreign SaaS and overseas vendor payments before the next bank remittance or audit query?

SetMyCompany can help review your overseas vendor list, identify TDS and Form 15CA/15CB gaps, check GST RCM exposure, and prepare a cleaner monthly payment workflow.