Introduction
Whether youre paying a foreign vendor for software, consulting, marketing, cloud services, or group-company support, cross-border remittances from India are not just a bank transfer.
They sit at the intersection of:
- Income-tax withholding (TDS)
- documentation and CA certification (Form 15CA/15CB)
- FEMA purpose codes and remittance rules
When teams treat this as an operations task, the same issues repeat:
- remittance stuck at bank due to missing documents
- wrong withholding leading to interest/penalty exposure
- future scrutiny during audit or due diligence
Perfect Accounting supports businesses on tax and regulatory compliance through our Regulatory Approvals practice: https://perfectaccounting.in/our-services/atlantas-financial-services-team-handles-gst-and-income-tax-with-exceptional-accuracy/
What counts as a foreign remittance (common examples)
Typical cross-border payments include:
- SaaS subscriptions and cloud services
- foreign consultants / freelancers
- marketing and advertising services
- royalty / license fees
- import of services
- group-company management fees
- reimbursements (often wrongly assumed to be no tax)
Each category can have different tax treatment depending on facts.
The 3 questions you must answer before remitting
1) What is the nature of payment?
You need a clear classification backed by:
- contract / PO
- invoice description
- scope of work
- deliverables and location of service
2) Is TDS applicable? At what rate?
Withholding depends on:
- whether the payment is taxable in India
- the relevant section and characterization (fees for technical services, royalty, business income, etc.)
- DTAA (treaty) applicability and documentation
3) What documentation is required for the bank?
Banks typically ask for:
- Form 15CA (and Form 15CB where applicable)
- invoice and agreement
- purpose code and FEMA declarations
- sometimes additional clarifications depending on amount and category
TDS on foreign remittances (practical overview)
Why this is sensitive
Unlike domestic payments, foreign remittances can trigger scrutiny because:
- the payee is outside India
- the payment may be characterized as royalty/FTS
- treaty benefits may be claimed
Common operational mistakes
- assuming no TDS because vendor is outside India
- not collecting payee details and tax residency documents
- relying on invoice wording instead of contract scope
- missing internal approvals and documentation trail
Best practice:
- create a standard internal foreign remittance pack for every payment.
Form 15CA and 15CB (what they are, in simple terms)
Form 15CA
A declaration filed online for certain foreign remittances.
Form 15CB
A CA certificate that is required in specified cases, based on nature of remittance and thresholds.
Practical point:
- the biggest delays happen when the finance team starts documentation after the bank asks for it. Build the pack before initiating the transfer.
FEMA considerations (what founders and finance teams should track)
FEMA compliance typically involves:
- selecting the correct purpose code
- ensuring the remittance is permitted under the category
- maintaining documentation to support the transaction
- ensuring approvals/limits are respected (as applicable)
Common FEMA-related issues:
- wrong purpose code selection
- weak documentation for reimbursement claims
- group-company payments without clear agreements
If your business has ongoing cross-border structures (subsidiaries, group entities, inbound/outbound investments), its smart to align remittance documentation with your broader compliance framework.
A practical workflow for cross-border payments (copy-paste SOP)
Step 1: Collect documents upfront
- signed agreement / PO
- invoice
- scope of work and deliverables
- vendor details (name, address, country)
Step 2: Tax analysis and withholding decision
- classify nature of payment
- evaluate taxability and DTAA position (as applicable)
- compute withholding and gross-up (if contract requires)
Step 3: Prepare 15CA/15CB (where required)
- compile remittance details
- prepare CA working papers
- file forms and keep acknowledgements
Step 4: FEMA purpose code and bank submission
- select correct purpose code
- submit remittance pack to bank
- maintain evidence of remittance and approvals
Step 5: Accounting and compliance closure
- book expense and TDS correctly
- deposit TDS (if applicable)
- maintain a remittance register for audit readiness
For clean accounting records and reconciliations, see Accounting and Compliance: https://perfectaccounting.in/our-services/europes-top-firms-trust-our-tax-management-services-for-accurate-tax-returns-and-bank-reconciliations/
Documentation checklist (foreign remittance pack)
Maintain a single PDF folder per remittance:
- invoice
- agreement/PO
- email approvals / internal note on nature of payment
- withholding computation working
- DTAA documents (if claimed)
- Form 15CA acknowledgement
- Form 15CB (if applicable)
- bank advice / remittance confirmation
- purpose code and FEMA declarations
Common scenarios that need extra care
- software and SaaS payments (license vs service characterization)
- marketing and ad spends paid to foreign platforms
- group-company management fees
- reimbursements (ensure pure reimbursement with evidence)
- payments split into multiple invoices (avoid threshold confusion)
How Perfect Accounting can help (soft CTA)
We help businesses execute cross-border payments with a clean compliance trail:
- withholding tax evaluation and documentation
- Form 15CA/15CB support
- FEMA purpose code and remittance pack preparation
- remittance register and audit-ready documentation
Explore our support via Regulatory Approvals: https://perfectaccounting.in/our-services/atlantas-financial-services-team-handles-gst-and-income-tax-with-exceptional-accuracy/
Final thought
Cross-border payments become simple when you standardize the workflow: classify the payment, document the basis, decide withholding correctly, file 15CA/15CB where required, and maintain a remittance pack. Thats how you reduce bank delays today and notice risk later.