Skip to content
Ayush Agro Foods

Free guide · 12 chapters

The SaaS Spend Playbook for Indian companies

How to find every software subscription you pay for, give each one an owner, cut the seats nobody uses, catch renewals before they charge, and hand your CA clean facts on GST reverse charge and foreign payments.

Chapters
12
Reading time
25 min
Updated
13 Nov 2026
Price
Free

Contents

Four parts, in the order you'll need them.

Read it start to finish once, then come back to the chapter you need at renewal time, at an exit, or when your CA asks about a foreign bill.

Chapter 01

Why software spend grows faster than headcount, and where it hides

Software is bought by whoever needs it, on whatever card is nearest, and renewed by default. That is why nobody has the full list.

Ask a finance controller at a 150-person company how much the company spends on software and you will usually get one of two answers: the ledger total for "software subscriptions", or a shrug. The ledger number is almost always too low, because a large share of software is not booked to that ledger at all. It sits in card spends booked to "miscellaneous", in employee reimbursements, in forex charges, and in annual plans paid once and forgotten.

Software spend grows faster than headcount for a simple reason: buying a tool costs one person five minutes and a card. Nobody needs a purchase order to start a free trial, and the trial turns into a paid plan the day a team starts relying on it. Each new joiner adds a seat to several tools at once. Each new project adds a tool or two. Very little of this passes finance before the first charge.

The six places software spend hides

Where software charges sit in an Indian company's books
WhereWhat it looks likeWhy it is missed
Company cardsA USD charge with a merchant name like "FIGMA SAN FRANCISCO" and a separate forex markup lineBooked to the card holder's department or to a suspense head, rarely tagged as software
Founders' and team leads' cardsThe same, on four or five different cardsEach card holder sees only their slice; nobody sees the total
Reimbursements"Monthly subscription" claims in the expense tool, every month, by the same personThe claim is approved as an expense, not reviewed as a recurring purchase
Bank transfersAnnual invoices from Indian vendors paid by NEFT or RTGSPaid once a year, so they are invisible for eleven months
Marketplace and cloud billsAdd-ons bought through a cloud provider's marketplaceThey appear inside a larger infrastructure bill
Free tiers that turned paidA small charge that grows each month as usage risesNobody decided to buy it; it just started charging

Why it matters more in India

Indian companies pay a large share of their software bill to vendors outside India, in dollars, on cards. That adds three costs a US company does not see: the bank's foreign currency markup on each card charge, GST on the currency conversion, and the GST reverse-charge liability on imported services that someone has to work out and pay each month. A tool you did not know you had is also a reverse-charge entry nobody made. Chapters 8 and 9 cover these in detail.

What "under control" looks like

You do not need a procurement department. A company has its software spend under control when it can answer five questions on any given day:

  1. What tools do we pay for, from which card or account, and how much a year in rupees?
  2. Who owns each tool, meaning who decides whether it renews?
  3. How many seats do we pay for, and how many people actually signed in during the last 60 days?
  4. What renews in the next 90 days, and what is the notice period for each?
  5. For every foreign bill, has the reverse charge been worked out, and do we hold an invoice?

The rest of this playbook works through those questions in order. Chapter 2 builds the list. Chapters 3 to 7 put owners, seats, renewals, overlaps and leavers under control. Chapters 8 to 10 cover payments, GST and income tax. Chapters 11 and 12 give you a policy and a tracker you can adopt this week.

Throughout this playbook, figures for "Neelgiri Labs" are a worked example about a fictional 120-person company. They show the arithmetic, not an industry average.

Chapter 02

Building the first complete list: statements, ledgers, reimbursements and SSO

Work backwards from the money. Every tool you pay for has left a trace in a statement, a ledger or a claim.

The first list should be built from the money, not from memory. Asking team leads "what tools do you use?" gets you the tools they think about, which is a fraction of what the company pays for. Charges do not forget. Start with twelve months of data, because annual plans charge only once a year.

Step 1: Collect twelve months of statements

  • Every company credit card and debit card statement, including cards held by founders and team leads.
  • The current account statements for every bank account that pays vendors.
  • The reimbursement export from your expense tool, filtered to anything described as subscription, software, licence, plan or app.
  • If any employee pays for a tool on a personal card and claims it, those claims are in the reimbursement export.

Step 2: Pull the ledger

Export the ledgers your accountant uses for software from Tally Prime or Zoho Books: software subscriptions, IT expenses, internet and communication, and any suspense or miscellaneous head where card charges land. The ledger catches Indian vendors paid by bank transfer, which statements alone will show only as a payee name.

Step 3: Find the recurring charges

A software subscription has a pattern: the same merchant, a similar amount, at a regular interval (monthly, quarterly or annual). Sort each source by merchant name and look for repeats. Merchant names on card statements are messy, so group variants together: "GOOGLE*WORKSPACE", "GOOGLE *GSUITE" and "Google Cloud India" may be one tool or three. Write each tool once with its cycle and its annual cost in rupees.

Step 4: Add the sign-in view

If the company uses Google Workspace or Microsoft 365 sign-in for other tools, the admin console lists which third-party apps people sign into. This catches tools on free plans and tools paid by someone outside the company (a client, a parent entity) that still hold company data. They cost nothing today, but they are where the next paid plan comes from.

What each row needs

Minimum fields for each tool on the first list
FieldExampleWhere it comes from
Tool and vendorDesign tool, vendor in the USStatement merchant name, invoice
Paid fromCard ··4417, marketing headStatement
Currency and amount per cycleUSD 450 a monthStatement or invoice
Annual cost in INR₹4,60,000 (approx.)Amount × cycles × rate actually debited
Billing cycle and next renewalAnnual, 14 Feb 2027Invoice or vendor admin page
Seats paid40Vendor admin page or invoice
Invoice held?Yes / NoMailbox, vendor portal

Expect the first pass to find more tools than anyone guessed. That is normal, and it is the point. Do not cancel anything in the first week. The list is a map; decisions come once each tool has an owner.

Ayush Agro Foods' free Spend Scan does Steps 1 and 3 from uploaded statements, and the software register template gives you the columns for the rest.

Chapter 03

Owners: giving every tool a person who answers for it

A tool without an owner renews because nobody said no. One named person per tool fixes most of the problem.

Most unwanted renewals are not anyone's mistake. They happen because nobody was asked. The finance team cannot judge whether the design team still needs forty seats of a design tool, and the design team never sees the card charge. An owner is the person who sits between the two: close enough to the work to know whether the tool is needed, and accountable to finance for what it costs.

Who should own a tool

  • The person whose team gets the most use from it, usually a team lead or department head. Not the person who happened to pay for it.
  • For company-wide tools (email, chat, video meetings, password manager), the IT or workplace admin.
  • For tools shared by two departments, one owner from the heavier user, with the other department named as a stakeholder.
  • Never "finance" by default. Finance approves the money; it should not decide whether the sales team needs a CRM add-on.

What the owner answers for

Owner responsibilities
ResponsibilityWhenEffort
Decide at each renewal: renew, reduce seats, switch cycle or cancel30 days before renewal5 minutes per tool
Confirm the seat count matches the people who use itQuarterly, and at renewalA quick review of the seat list
Approve new seats and new usersAs requestedOne click
Remove leavers' seats or reassign themOn the leaver's last dayMinutes
Make sure the invoice reaches financeEach billing cycleForward an email, or set the vendor's billing email to finance

Assigning owners for the first time

Send each department head their slice of the list from Chapter 2, sorted by annual cost, and ask them to name an owner for every row within a week. Anything nobody claims after two reminders goes on a "no owner" list. Those tools are your first cancellation candidates: if nobody will answer for a tool, check the sign-in data (Chapter 4), and if nobody uses it, cancel it at the next renewal.

Keeping owners current

Owners leave and change roles. Add one line to your exit checklist: "Does this person own any tools? Reassign them." A tool whose owner left is an orphan again, and orphans renew.

Worked example: at Neelgiri Labs, Priya in finance sent each department head a list sorted by annual cost. Eighteen of 64 tools had no obvious owner. Within two weeks, eleven were claimed, and seven went on the cancellation shortlist.

Owners also handle purchase requests for their area. When someone asks for a new tool, the owner of the nearest existing tool is the first person to ask "can we do this with what we already pay for?" Chapter 6 and the purchase request form cover that check.

Chapter 04

Seats and usage: what "unused" should mean for different tools

A seat nobody signed into for 60 days is usually the cheapest thing to cut. But "unused" depends on the tool.

Reducing seats is almost always easier than cancelling tools. Nobody's work breaks when you remove a seat held by someone who has not signed in for three months. The hard part is defining "unused" fairly, because different tools have different rhythms of use.

Where usage data comes from

  • Single sign-on logs. If a tool signs in through Google Workspace, Microsoft 365 or Okta, the identity provider records each person's last sign-in. This is the most reliable source and covers many tools at once.
  • The vendor's admin panel. Most per-seat tools show a member list with "last active" dates. Some offer an admin API that can be read automatically.
  • Asking the owner. For tools with neither, a short quarterly check: "Here are the 12 people with seats. Who still needs one?"

A sensible threshold by tool type

Suggested unused thresholds by tool type
Tool typeNormal rhythmTreat as unused after
Chat, email, project trackerDaily30 days without a sign-in
Design, documentation, CRMSeveral times a week60 days
Screen recording, survey, webinarOccasional90 days
Finance close, payroll, audit toolsMonthly or quarterlyOne full cycle plus a month
Seasonal tools (appraisals, events)A few weeks a yearReview at renewal only

These are starting points, not rules. The owner can override them for a reason ("she's on maternity leave and back in February"). The point is to have a default that turns the list into a short set of named seats to check.

When you can actually remove a seat

Vendors differ on this, and it changes what you should do today:

  • Monthly plans: seats can usually be removed at any time and the next bill is lower.
  • Annual plans: many vendors let you add seats any time (charged pro rata) but only reduce them at renewal. Removing a user mid-term frees the seat for a new joiner, but does not lower the bill until renewal.
  • True-ups: some vendors count the highest number of seats used during the term and bill the difference at a true-up date. Removing unused users before that date can lower the true-up.

So the action for an unused seat on an annual plan is often "reassign it to the next joiner instead of buying a new one", and "reduce the count at renewal". Check each vendor's own help pages; our tool guides note what each vendor says, with the date checked.

Working out what unused seats cost

Multiply unused seats by the per-seat price and by the number of cycles in a year. For a USD plan, use the rupee amount your card was actually debited, not the list price, since that includes the bank's markup. The unused seat cost calculator does this for a set of tools at once.

Worked example: a design tool with 40 paid seats on an annual plan at USD 15 per seat per month, and 23 people signed in during the last 60 days. 17 unused seats × USD 15 × 12 months = USD 3,060 a year, about ₹2.7 lakh at a debit rate near ₹88 per dollar.

Employee sign-in dates are personal data. Collect only what you need (last sign-in date and seat assignment), use it for managing tools and access, and tell employees in your IT or acceptable-use policy that you do this. This is general information about the DPDP Act, 2023, not legal advice.

Chapter 05

Renewals: annual vs monthly, notice periods, price increases and auto-renew

One missed renewal locks in a year. Put every renewal in front of its owner 30 days early, with a decision to make.

Annual renewals are where most avoidable software spend goes. A monthly tool you stop needing costs you one more month. An annual tool that renews unnoticed costs you twelve. Most SaaS plans renew automatically by default, and the vendor has no reason to remind you.

Annual or monthly?

Vendors usually discount annual plans against paying monthly. The discount is worth taking only if you are confident you will use the tool, at roughly the same seat count, for most of the year. Work out the break-even: if the annual price equals ten months of the monthly price, annual pays off only if you would have kept the tool for more than ten months.

When each billing cycle makes sense
Choose monthly whenChoose annual when
The tool is new and the team is still decidingThe tool is core and has been used for a year or more
Seat count will change a lot (hiring, project ends)Seat count is stable or growing slowly
A competing tool is being evaluatedThe annual discount is large and you would keep it anyway
The project the tool serves has an end dateThe vendor offers price protection for the term

The annual vs monthly calculator gives you the break-even month and the cheaper option for a seat change you expect.

Notice periods

Self-serve plans usually let you cancel or downgrade any time before the renewal date. Contracts signed with a sales team often carry a notice period: 30, 60 or even 90 days before renewal, in writing. Miss it, and the contract renews at the existing terms. Read the order form or master agreement for each annual contract and write the notice date, not just the renewal date, on your tracker.

Price increases

Vendors change list prices, retire plans and move features between tiers. An annual renewal is when these changes reach you. Ask the vendor for the renewal quote 45 to 60 days early, compare it with last year's invoice per seat, and check whether the plan you are on still exists. If the price has gone up, that is the moment to reduce seats, change plans or negotiate.

A renewal routine that works

  1. 90 days out: the renewal appears on the finance calendar. For contracts with a notice period, the owner is asked now.
  2. 30 days out: the owner gets the seat count, sign-ins in the last 60 days, the expected renewal amount and four choices: renew as is, reduce seats, switch to monthly, or cancel.
  3. 14 days out: a reminder if the owner has not decided.
  4. 3 days out: finance is told if there is still no decision, and decides by default.
  5. After the charge: check the statement to confirm the amount matches the decision.

Worked example: at Neelgiri Labs, a CRM renews on 29 December for ₹4,86,000 with 30 seats paid, 19 people active in 60 days and 3 seats held by people who have left. The owner, Karthik, reduces to 22 seats at renewal, keeping a small buffer for hiring.

Whatever the decision, record who made it, when, and the expected difference a year. That record is what you show the board when it asks how the software line came down.

Chapter 06

Overlap: one tool per job, and when two are justified

Overlapping tools are rarely a mistake when they are bought. They become waste when nobody revisits the choice.

It is common for a growing company to pay for two tools that do the same job: two video meeting tools, two project trackers, two places where documents live. Each was a reasonable choice when a team bought it. Overlap becomes waste when both renew year after year and nobody asks why.

Common overlaps

Categories where overlap is common
CategoryHow the second tool arrives
Video meetingsOne comes bundled with the email suite; another is bought by sales for webinars
Project managementEngineering picks one, marketing and operations pick another
Documentation and wikisA wiki from the project tool, plus a separate notes tool a team preferred
DesignA design tool for product, a template tool for marketing, an older suite for one designer
Screen recordingFree tiers that became paid seats for a few people each
AI assistantsSeveral team plans bought by different teams in the same quarter

Our category guides cover each of these, with questions to decide which tool to keep.

How to decide which to keep

  1. Count real users of each. Sign-in data from Chapter 4. The tool with twice the active users usually wins.
  2. List what only one tool does. If the second tool does one thing the first cannot, check whether a cheaper add-on or a few seats would cover it.
  3. Check what's already in a bundle. Your email suite may already include video meetings, storage and forms. You are paying for those whether you use them or not.
  4. Check data and integrations. Moving years of documents or projects has a real cost. Plan the move for after the next renewal of the tool you keep, and before the renewal of the one you drop.
  5. Ask the owners, together. A decision imposed by finance tends not to stick. A decision the two owners make together does.

When two tools are justified

  • A client requires a specific tool for their projects, and you re-bill it or it is part of the deal.
  • One tool is used by a small, specialist group for a capability the main tool genuinely lacks.
  • A migration is under way with a fixed end date, and both are needed until then.
  • A regulatory or data residency requirement applies to one part of the business only.

Write the reason on the tracker next to both tools, with a review date. "Justified" without a review date tends to become permanent.

Stopping the next overlap

The cheapest overlap to fix is the one that never starts. A short purchase request (Chapter 11) with one question, "Which tool we already pay for did you consider?", catches most of them. The purchase request form includes it.

Chapter 07

Offboarding: removing access and seats on the last day

Unless someone revokes them, a leaver's paid seats renew with everyone else's, and their access to company data stays open.

When someone leaves, HR collects the laptop and IT suspends the email account. What usually does not happen is a check of every tool the person had a seat in. Seats in tools that do not sign in through the company's identity provider stay paid and, worse, stay active: a former employee can still sign in with a password to the design tool, the CRM or the shared drive of a vendor.

Why this is both a cost and a security problem

  • Cost: the seat keeps billing until someone removes it, often until the next annual renewal or longer.
  • Access: tools with separate passwords are not closed by suspending the email account. Customer data, designs and code may still be reachable.
  • Ownership: files, boards and automations the leaver created may be deleted or orphaned if the account is removed carelessly.

A last-day routine

  1. Before the last day: HR tells IT and the leaver's manager the exit date. IT pulls the list of every tool the person has a seat in, from the software register and identity provider.
  2. Transfer ownership: the manager names who takes over files, projects and any tool the leaver owned (Chapter 3).
  3. On the last day: suspend the identity provider account first, then remove or reassign the seat in each tool that does not sign in through it.
  4. Record each removal: tool, action (removed, reassigned to whom, kept for handover until a date), who did it, when.
  5. Next billing cycle: check the statement to confirm the seat count went down where the plan allows it.

The offboarding access checklist gives you this as a sheet with one row per tool.

Reassign before you remove

On an annual plan, a removed seat often does not reduce the bill until renewal (Chapter 4). If a joiner starts soon, reassigning the seat saves you buying a new one. Track reassigned seats on the register so they are not counted twice.

Shared and admin accounts

Leavers who were admins of a tool are the highest risk. Before they go, add a second admin and change any shared passwords they knew. If a tool is billed to the leaver's personal card or their name is on the vendor account, move billing and ownership to a company account before the exit, not after.

Worked example: at Neelgiri Labs, Meera in HR records an exit for 30 November. The leaver held seats in eleven tools, four of which do not sign in through Google Workspace. Faisal in IT removes the four by hand on the last day and reassigns the design seat to a joiner starting in December.

Chapter 08

Paying for foreign SaaS from India: cards, forex charges and RBI rules on recurring payments

Card payments to foreign vendors carry a markup, GST on currency conversion and RBI's e-mandate rules. Know what you are actually paying.

Most foreign software is paid on company credit cards. The price on the vendor's pricing page is not what leaves your account. This chapter covers what is added on the way, and the RBI rules that shape how recurring card charges work. It is general information about the rules as we understand them; confirm details with your bank and your CA.

What you actually pay on a USD card charge

Components of a foreign card charge
ComponentWhat it isWhere you see it
Vendor priceThe amount in USD (or EUR, GBP) on the vendor's invoiceInvoice, statement
ConversionThe card network and bank's exchange rate on the processing dateStatement, as the INR amount
Foreign currency markupA percentage the bank adds to international transactions. It varies by card and bank. Check your card's schedule of chargesOften a separate line on the statement
GST on currency conversionGST charged by the bank on the conversion serviceA separate line, sometimes days later

Because the markup varies by card, the same tool can cost noticeably more on one card than another. Compare the INR debited with the vendor's USD price and a reference rate to see your effective rate. The forex markup calculator does this from one statement line.

RBI's e-mandate rules for recurring card payments

RBI's framework for processing e-mandates on cards for recurring transactions shapes how subscriptions charge an Indian card:

  • A recurring charge needs a registered e-mandate on the card.
  • The card holder gets a pre-debit notification at least 24 hours before each charge.
  • Charges above a limit need additional factor authentication each time. RBI has set this limit at ₹15,000 for most categories.

In practice, a recurring charge can fail when no mandate is registered for it, or wait for the card holder to authenticate it. A failed renewal can lock the team out of a tool. A large annual renewal above the limit may need the card holder present on the day. Keep a list of which card pays for which tool, and make sure the card holder is not the person on leave that week.

Use pre-debit notifications as a control

The pre-debit notification is a free renewal warning. Ask card holders to forward each one for software to a shared finance inbox, or check them against your renewal tracker. A notice for a tool nobody recognises is a tool to investigate before it charges.

Personal cards and reimbursements

When an employee pays for a company tool on a personal card, the company loses visibility, the invoice is often in the employee's name without the company's GSTIN, and the tool leaves with the employee. Move recurring tools from personal cards to company payment methods as soon as you find them.

This chapter is general information about RBI rules and card charges, not legal or financial advice. RBI updates its circulars on card payments; check the current circular and your bank's terms.

General information about RBI rules and card charges. Check the current RBI circular and your card issuer's schedule of charges.

Chapter 09

GST on software: Indian vendors, OIDAR vendors, reverse charge on imported services and input tax credit

Indian invoices need your GSTIN for credit. Foreign bills with no GST may mean IGST to pay under reverse charge, in cash, each month.

General information, not tax advice. Confirm with your chartered accountant. GST rules change with CBIC notifications and GST Council decisions. This chapter describes the rules as commonly applied; your CA decides how they apply to your bills.

Every software bill a GST-registered company pays falls into one of three cases. Sorting each tool on your list into the right case is most of the work.

Three GST cases for a software bill
CaseWhat the invoice showsWhat generally follows
Indian vendorCGST and SGST, or IGST, usually at 18%, with the vendor's GSTINYou can generally claim input tax credit if the conditions in Section 16 of the CGST Act are met
Foreign vendor, no GST chargedA USD, EUR or GBP amount with no Indian GSTGenerally import of services: you pay IGST under reverse charge
Foreign vendor charging Indian GSTIGST shown, sometimes with a foreign vendor's Indian registrationCheck with your CA whether reverse charge still applies, and whether the vendor should have your GSTIN

Indian vendors: the invoice is the credit

Software subscriptions from Indian vendors are generally taxed as services at 18% GST. To claim input tax credit, Section 16 of the CGST Act sets conditions, among them: you hold a valid tax invoice showing your GSTIN, the supplier has filed its return, and the invoice appears in your GSTR-2B. An invoice made out to an employee's name, or to the wrong GSTIN of a multi-state company, usually means credit you cannot take. Give vendors the right GSTIN and legal name when you sign up, and check the first invoice.

Foreign vendors: reverse charge on import of services

When a GST-registered business receives services from a supplier outside India, the recipient generally pays IGST under reverse charge (Section 5(3) of the IGST Act read with Notification No. 10/2017-Integrated Tax (Rate)). Key points:

  • Paid in cash. Reverse-charge tax is paid through the electronic cash ledger with your GSTR-3B, not from your input tax credit balance.
  • Generally claimable as credit. The same amount is generally available as input tax credit, subject to the usual conditions. Paid correctly, the net cost is often a timing cost, not a permanent one.
  • Time of supply. For services under reverse charge, generally the earlier of the date of payment or 60 days after the date of the supplier's invoice (Section 13(3) of the CGST Act). That decides which month's return the tax belongs in.
  • Exchange rate. The value in rupees is worked out using the exchange rate under Rule 34 of the CGST Rules, not the rate your card was debited at. Ask your CA which reference rate they use.

A worked example

A design tool bills USD 1,000 for the month. The vendor has no Indian GST registration and charges no GST. Your CA applies a Rule 34 rate of ₹84.60, so the taxable value is ₹84,600. IGST at 18% under reverse charge is ₹15,228, paid in cash with that month's GSTR-3B. The same ₹15,228 is generally available as input tax credit, subject to conditions. The card was debited ₹87,400 including the bank's markup; the markup and the bank's GST on conversion are separate costs (Chapter 8).

Try your own numbers in the RCM calculator.

OIDAR vendors

Foreign suppliers of online information and database access or retrieval (OIDAR) services to unregistered recipients in India register under a simplified scheme and charge IGST themselves. Many SaaS vendors fall into this group for their consumer and small-business customers. Some foreign vendors also charge GST to registered businesses, or ask for your GSTIN so that they do not charge it. That is why the same tool can arrive with GST one month and without it after someone adds the GSTIN to the billing profile. Check each invoice, and tell your CA which foreign bills carry GST and which do not.

What to give your CA every month

  1. A list of every foreign software bill paid or invoiced in the month: vendor, invoice date, payment date, currency, amount, and whether GST was charged.
  2. The invoice PDF for each, with your company's name and GSTIN where the vendor allows it.
  3. Indian vendor invoices that do not show your GSTIN, so they can be corrected before the GSTR-2B cut-off.
The reverse-charge flow on one USD bill. Worked example, using a Rule 34 rate of ₹84.60.
  1. 01

    Invoice

    $1,000 from a vendor with no Indian GSTIN

    No GST on the invoice

  2. 02

    Payment

    ₹87,400 debited on the company card

    Card markup and conversion GST are separate

  3. 03

    IGST in cash

    ₹15,228 at 18% on ₹84,600

    Paid in cash with GSTR-3B, not from credit

  4. 04

    Credit

    ₹15,228 claimed as input tax credit

    Subject to the usual ITC conditions

General information, not tax advice. Confirm with your chartered accountant. GST and income-tax positions on cross-border software change with CBIC notifications, Finance Acts and court rulings.

Work out your own bill in the RCM calculator

Chapter 10

TDS on payments to foreign software vendors: what to ask your CA

Whether tax must be withheld on a payment to a foreign software vendor is a question for your CA. Here is what to bring them.

General information, not tax advice. Confirm with your chartered accountant. This chapter takes no position on whether tax must be deducted on any payment. It sets out the rules your CA is likely to consider and the questions to ask.

Finance teams often ask whether tax has to be deducted at source before paying a foreign SaaS vendor. The answer depends on the nature of the payment, the vendor's country, the tax treaty, and how the payment is made, and practice has shifted over the years. This is your CA's call. What you can do is give them clean facts and ask the right questions.

The rules your CA will look at

  • Section 195 of the Income-tax Act, 1961 requires a person paying a non-resident a sum chargeable to tax in India to deduct tax. Whether a software subscription payment is "chargeable" is the central question.
  • Forms 15CA and 15CB under Rule 37BB apply to remittances to non-residents. Your CA will tell you when each is needed.
  • The Income-tax Act, 2025 is in force from 1 April 2026. Section and form numbers may differ under it. Ask your CA which provisions apply to payments made from that date.
  • Engineering Analysis Centre of Excellence v. CIT (2021): the Supreme Court held that payments for off-the-shelf software were not royalty under the relevant tax treaties. Ask your CA how they apply this to SaaS subscriptions.
  • Equalisation levy: the 2% levy on e-commerce operators was withdrawn from 1 August 2024, and the 6% levy on online advertising from 1 April 2025.

Questions to ask your CA

  1. For each foreign software vendor we pay, do we need to deduct tax before paying? Does the answer change if we pay by card rather than by bank transfer?
  2. Which of our vendors' countries have a tax treaty with India that you rely on, and do we need a tax residency certificate or other documents from the vendor?
  3. When do we need Form 15CA, Form 15CB, both or neither, and who prepares them?
  4. From 1 April 2026, which sections and forms of the Income-tax Act, 2025 replace the ones we used before?
  5. How do you treat payments to foreign vendors made by employees on personal cards and reimbursed?
  6. Is any of our software spend, such as advertising tools or marketplace purchases, treated differently?
  7. What records should we keep for each payment, and for how long?

What to bring to the conversation

Facts your CA needs for each foreign vendor
FactWhy it matters
Vendor legal name and countryTreaty position, residency
What the tool doesNature of the payment
Amounts paid in the year, by monthThresholds and reporting
How it was paid (card, bank transfer, reimbursement)Mechanics of deduction and remittance forms
Invoices and the vendor's terms of serviceWhat exactly is being bought

Ayush Agro Foods never states whether tax should be deducted on a payment. It lists foreign software payments with the facts above so your CA can decide.

General information, not tax advice. Confirm with your chartered accountant. GST and income-tax positions on cross-border software change with CBIC notifications, Finance Acts and court rulings.

Chapter 11

A simple SaaS policy for a 50 to 300 person company

One page, five rules. Enough to stop the next unowned tool without slowing anyone down.

A software policy for a company of this size should fit on one page and be read in three minutes. Its job is not to stop people buying tools. It is to make sure every tool has an owner, a company payment method, an invoice in the company's name, and a renewal date someone will see. Below is a policy you can adapt. A full version is in the SaaS purchase policy template.

1. Scope

This policy covers any software, app, plugin or online service paid for by the company or reimbursed to an employee, including free plans that hold company data.

2. Before buying

  • Check the software register for a tool that already does the job. Ask its owner first.
  • Submit a purchase request: what the tool is for, who will use it, expected seats, monthly and annual cost, and which existing tool you considered.
  • Tools under a set amount a month (for example ₹5,000) need only the department head's approval. Above it, finance approves too. Tools that will hold customer or employee personal data also need IT's review.

3. Paying for it

  • Pay with a company card or by bank transfer. Recurring tools on personal cards are not reimbursed after the first month.
  • Bill to the company's legal name, with the company's GSTIN on the billing profile where the vendor allows it.
  • Set the vendor's billing email to the finance inbox, so invoices arrive without anyone forwarding them.
  • Start on monthly billing. Move to annual only after three months of use and the owner's confirmation.

4. Owning it

  • Every tool has one named owner, recorded in the register.
  • The owner decides at each renewal, reviews seats each quarter, and removes or reassigns leavers' seats on their last day.
  • If the owner leaves or changes role, their manager names a new owner before the exit.

5. Renewing or cancelling it

  • Finance sends each owner the renewal 30 days before it charges, with seat count and usage.
  • If the owner does not decide by 3 days before renewal, finance decides.
  • Cancellations and seat reductions are made by the owner or IT in the vendor's admin panel and recorded in the register.

Making it stick

Announce the policy with the first complete list (Chapter 2) so people see why it exists. Keep the approval quick: a request answered in a day is followed; one that waits a week is bypassed with a personal card. Review the policy once a year with the department heads.

Who does what under the policy
RoleDoes
RequesterChecks the register, submits the request
Department headApproves within budget, names the owner
FinanceApproves above the limit, pays, keeps the register and invoices, sends renewal notices
ITReviews data access, connects sign-in, runs offboarding
OwnerDecides renewals, manages seats

Chapter 12

Downloadable software register and renewal tracker (Excel and Google Sheets)

One sheet, one row per tool. The columns that make renewals, seats, owners and GST visible in one place.

Everything in this playbook comes back to one list. If you are starting without software for it, a well-built sheet will carry a company of up to a few dozen tools. This chapter explains the columns of our software register and renewal tracker, and how to keep it current.

The columns

Software register columns
ColumnWhat to put in it
ToolThe product name as your team knows it
Vendor and countryLegal name from the invoice, and where the vendor is based
Department and ownerFrom Chapter 3
Paid fromCard last four digits or bank account, never the full number
Currency, amount per cycle, cycleUSD 450, monthly
Annual cost (INR)From actual debits, including markup
Seats paid / active in 60 daysFrom Chapter 4
Renewal date and notice dateFrom Chapter 5
GST treatmentIndian GST on invoice / Foreign, no GST (RCM to check) / Foreign, GST charged
Invoice heldYes or No, and where it is filed
Decision and dateRenew, reduce, monthly, cancel, with who decided

The views that matter

Keep the register as one flat table and build views on top of it with filters, rather than separate sheets that drift apart. Four views cover most needs: renewals in the next 90 days sorted by notice date, seats paid against seats active sorted by unused cost, foreign bills with no GST for the monthly reverse-charge check, and tools with no owner or no invoice.

Keeping it current

  • Monthly: match the month's card and bank statements against the register. New recurring charges get a row and an owner. Mark which foreign bills need the reverse-charge check.
  • Quarterly: send each owner their rows and ask them to confirm seats and the next renewal.
  • On each exit: filter by the leaver's name in the seat lists and work through the offboarding checklist.
  • At year end: total the annual cost column by department for the budget.

Get the tracker as a CSV straight from the renewal tracker template, or ask for the Excel and Google Sheets versions by email there.

When the sheet stops working

Sheets break down when nobody has time to match statements each month, when seat counts need sign-in data from several systems, or when renewals arrive faster than anyone can send reminders. That is the work Ayush Agro Foods does: it reads the statements and ledger, matches the charges, reads sign-ins and sends owners their renewal decisions. Start with the free Spend Scan to see your list from one statement.

Take it with you

Get the playbook as a PDF.

All 12 chapters in one file to share with your finance team, your IT admin and your CA, plus the software register in Excel and Google Sheets.

  • The full playbook12 chapters, with the worked examples and tables.
  • The software registerOwners, seats, renewals, notice dates and GST treatment per tool.
  • Links to the calculatorsRCM, unused seats, annual vs monthly and forex markup.

We send the PDF to this address and a short series on software spend. Unsubscribe from any email. Questions: hello@ayushagrofoods.com

Rather see your own list than build it by hand?

Upload one card statement to the free Spend Scan, or book a demo and we'll walk through your software list, unused seats and next renewals on the call.

  • Read-only access
  • Data hosted in India
  • Priced in rupees
  • 14-day trial on your data