पाठशाला Pathshala · संचालन Sanchālan, Operations · Lesson 19 · Build

Vendors, procurement and the contracts you keep renewing

Most vendor spend in a young company was approved once and then renewed by default. A register, an approval rule and a renewal calendar turn it back into a decision.

Pathshala, The Founder Library · 11 October 2026 · 7 min read

Stacked sacks of grain filling a storeroom, in black and white. — Photograph: Swastik Arora · Pexels

Nobody in a young company decides to spend ₹40 lakh a year on software nobody opens. It happens one card swipe at a time, each sensible when it was made, and then the contracts renew themselves every year while the people who signed them move on to other work. Procurement is the discipline of making every renewal a fresh decision.

This lesson sets out the vendor register, the approval rule, the renewal calendar, how to benchmark a price, how to pay small vendors on time, and the quarterly review that ties them together. It is written for a company of thirty to a hundred and fifty people with no procurement function, which is where the waste grows fastest and where a founder or finance head can fix it in a quarter.

Why vendor spend drifts

Vendor spend drifts for three reasons, and none of them is carelessness. The buyer and the payer are different people. A team lead signs up for a design tool on a company card; finance sees the charge each month and has no way to know whether it is used. Contracts renew by default. Most software and many service contracts carry an automatic renewal clause with a notice period, often thirty to ninety days before the anniversary, and a renewal nobody objected to is a renewal that happened. Prices rise at renewal. A vendor that discounted heavily to win the first year has every reason to restore list price in the second, and a company that does not ask will pay it.

The result in most companies past forty people is the same: a long tail of small subscriptions, a few large contracts that nobody has benchmarked since signing, two or three tools doing the same job, and seats assigned to people who left. Each item is small. Together they are often one of the largest lines in the P&L after salaries, and the only large one that nobody owns.

The vendor register

Start with a list, because nothing else works without it. Pull twelve months of payments from the bank, the company cards and the payables ledger, and group them by payee. For every vendor record eight fields: name, what it supplies, the internal owner who answers for it, annual value, contract start and renewal date, notice period, payment terms, and whether the vendor is registered as a micro or small enterprise. The owner is the most important field. A vendor with no owner is cancelled at the next renewal unless somebody claims it.

A company of eighty people is usually surprised by the count. Sort by annual value. The top fifteen or so will be most of the money and deserve a contract on file, a named owner and a benchmark. The rest deserve a yes or no once a year. The register lives where finance already works, in the accounting system’s vendor master or a shared sheet beside it, and it is updated every time a new vendor is paid for the first time.

Approvals by value, not by habit

An approval rule exists to put the right amount of friction in front of each amount of money. A workable rule for a company spending ₹10 crore a year: a budget owner may commit up to ₹1 lakh a year within an approved budget line; finance must approve anything from ₹1 lakh to ₹10 lakh and confirm the budget exists; a founder approves anything above ₹10 lakh and anything with a term longer than a year; and anything above ₹5 lakh needs two quotes or a written reason why only one vendor can do the job. Write the limits on one page, publish them, and route requests through a single form so there is a record.

The rule should also say what is never allowed: no contract signed by someone without authority, no new vendor paid before it is in the register with its GST and bank details verified, no auto-renewal clause accepted without a calendar entry for the notice date. The [internal controls lesson](/library/internal-controls-and-fraud-you-did-not-expect) explains why the second rule matters: a new vendor whose bank details nobody checked is the most common route for an invented invoice.

The renewal calendar

Every contract in the register gets two dates in a shared calendar: its notice date, the last day the company can cancel or change terms without being bound for another year, and a review date ninety days before that. The review date belongs to the owner. On it they answer three questions in writing, in a few lines each. Is it used, measured by logins, seats assigned, calls made or output delivered? Is there a cheaper equal, including a tool the company already pays for? And what does the market pay for this, today, for a company this size?

Ninety days is not caution for its own sake. A vendor negotiates seriously only when it believes the company might leave, and that belief needs time: a trial of an alternative, a quote from a competitor, a conversation with the account manager’s manager. A renewal reviewed in the last week is a renewal accepted. The founders see the calendar once a month, and every contract above the founder’s approval limit comes to them with the owner’s three answers attached before the review date passes.

Benchmarks and the negotiation

A benchmark is what other companies of the same size pay for the same thing. Get it from three places. Competing quotes: ask two alternatives for a written price for the same scope, even when switching is unlikely. Peers: founders and finance heads in the same stage swap prices freely, and one message to five of them usually returns three numbers. The vendor’s own price book: list price, the published discounts for annual payment or for volume, and the price on the page for new customers this month, which is often lower than what an existing customer is being renewed at.

Spices and dry goods heaped in sacks and trays at a market stall in New Delhi. — No trader in a Delhi spice market pays last year’s price without asking what the next stall charges. A software renewal deserves the same question. Photograph: Patricia Luquet · Pexels

Then negotiate in a fixed order. Cut first: remove the seats, modules and service hours nobody uses, because a discount on waste is still waste. Consolidate second: two tools doing one job become one, and the vendor that keeps the business usually pays for it in price. Negotiate the remainder third, with the benchmark in hand: a lower unit price, a price cap on the next renewal, a longer notice period, or annual payment in exchange for a discount if the company has the cash. Never accept an uncapped renewal increase; ask for a ceiling written into the order form.

Read the figure as the order of work. With ₹10 crore of opex, forty per cent paid to vendors, a tenth of it idle and twelve per cent negotiated off what survives, the company saves about ₹83 lakh a year, a little over eight per cent of opex, and nearly half of it comes from cutting rather than haggling. Move the idle slider to zero and the saving falls to about ₹48 lakh. That is why the review begins with usage data and not with the vendor’s account manager.

A contract that renews without a decision is a decision made by the vendor.

Paying the vendors who cannot wait

Procurement in India has a payment side that is also law. A buyer must pay a micro or small enterprise within the time agreed and never later than forty-five days, under section 15 of the MSMED Act 2006, and a company that pays later loses the tax deduction for that expense until the year it actually pays. That rule, introduced as section 43B(h) of the Income-tax Act 1961, carries over as section 37(2)(g) of the Income-tax Act 2025, as the Finance Ministry confirmed in a Rajya Sabha reply of 21 July 2026. The register’s eighth field exists for this. Ask every vendor for its Udyam registration, the free Aadhaar-based registration run by the Ministry of MSME; since 1 April 2025 a micro enterprise is one with investment up to ₹2.5 crore and turnover up to ₹10 crore, and a small one up to ₹25 crore and ₹100 crore. Flag every registered vendor, and let the payment run pay flagged invoices first. The [section 43B(h) lesson](/library/section-43b-h-paying-msme-vendors-on-time) sets out the mechanics in full.

Vendor contracts in India are governed by the Indian Contract Act 1872, and the clauses that matter at renewal are few: the term, the renewal mechanism and its notice period, the price change clause, termination for convenience, and what happens to the company’s data when it leaves. Read those five before signing anything above the founder’s limit, and record the notice period in the register on the day of signature.

The quarterly vendor review

Run it in the first week of each quarter, ninety minutes, with the finance head and every vendor owner whose contracts fall due in the next six months. Before the meeting: finance refreshes the register from the last quarter’s payments, flags every new vendor and every vendor with no owner, and pulls usage data for the top fifteen. In the meeting: each owner gives the three answers for each upcoming renewal; anything unused is cancelled on the spot; anything over the limit gets a benchmark task with a date. After the meeting: the notice dates are confirmed in the calendar, cancellations are sent in writing, and the saving is logged against the budget line.

Once a year, before the [annual plan](/library/forecasting-and-annual-operating-plan), finance sums the year’s savings and sets next year’s vendor budget from the register rather than from last year’s spend plus inflation. The first review in a company that has never run one usually finds the most; after that the work is keeping the register true and the renewals visible, which takes an hour a month.

Nothing here is legal, tax or investment advice. The approval limits and the figure are illustrative; set your own against your budget and your articles. Tax provisions checked on 10 October 2026.