The stamp duty on works contract agreements is set by state law, and the spread is wider than most contractors expect. On the same Rs 1 crore contract the Karnataka Schedule charges Rs 1,000, the Maharashtra Schedule Rs 9,100 and the Rajasthan Schedule Rs 25,000. The payer differs too: Karnataka puts the duty on the person entrusting the work, Rajasthan on the contractor, and both say so only in the absence of an agreement to the contrary.

Stamping is the cheapest line item on a works contract and the one most often handled by whoever happens to be at the registrar’s office that morning. It stays cheap right up until someone has to produce the agreement, and then it stops being about a few thousand rupees.

Three State Stamp Acts, read side by side, show how little of this is uniform.

What a works contract is, in the Acts’ own words

The definition is remarkably consistent, which makes the divergence everywhere else more surprising.

Article 63 of Schedule I to the Maharashtra Stamp Act, 1958, inserted by Maharashtra Act 12 of 2006 with effect from 1 May 2006, defines it as “a contract for works and labour or services involving transfer of property in goods (whether as goods or in some other form) in its execution and includes a sub-contract”.

Article 58 of the Schedule to the Rajasthan Stamp Act, 1998, as substituted by Rajasthan Act No. 5 of 2016, uses the same formula. The Karnataka Stamp Act, 1957 describes its entry at Article 5(i-d) as an agreement “relating to building works or labour or services (works contracts)”.

Two things follow. Transfer of property in goods is what separates a works contract from a pure service agreement, so a labour-only arrangement sits in a different article. And a sub-contract is inside the definition, which means a back-to-back arrangement is a chargeable instrument in its own right rather than something riding on the main contract’s stamp.

What the stamp duty on works contract agreements actually costs

Each state builds its charge differently. Maharashtra steps the duty every lakh, Karnataka every ten lakh, and Rajasthan runs a straight percentage.

Maharashtra’s Article 63 charges Rs 100 where the amount does not exceed Rs 10 lakh, and above that, Rs 100 plus Rs 100 for every Rs 1,00,000 or part thereof above Rs 10 lakh, subject to a maximum of Rs 5 lakh. That clause was substituted by the Maharashtra Tax Laws (Levy, Amendment and Validation) Act, 2012 with effect from 25 April 2012.

Karnataka’s Article 5(i-d) also charges Rs 100 up to Rs 10 lakh, then Rs 100 plus Rs 100 for every Rs 10,00,000 or part thereof in excess of Rs 10 lakh, subject to a maximum of Rs 5 lakh. The step is ten times wider than Maharashtra’s, and that single difference drives most of the gap.

Rajasthan’s Article 58 charges 0.25 per cent of the amount or value set forth in the contract. It used to be subject to a maximum of Rs 15,000, and that cap was deleted by Rajasthan Act No. 20 of 2019 dated 20 August 2019. Since then the percentage runs uncapped.

Contract value Maharashtra Karnataka Rajasthan
Rs 10 lakh Rs 100 Rs 100 Rs 2,500
Rs 50 lakh Rs 4,100 Rs 500 Rs 12,500
Rs 1 crore Rs 9,100 Rs 1,000 Rs 25,000
Rs 5 crore Rs 49,100 Rs 5,000 Rs 1,25,000

Every figure above is worked from the article itself, not from a rate card. At Rs 5 crore the same contract costs twenty-five times more to stamp in Rajasthan than in Karnataka, and the Rajasthan number keeps climbing because nothing caps it. The Maharashtra and Karnataka ceilings of Rs 5 lakh exist, but a contract would have to run into hundreds or thousands of crores to reach them, so for working purposes they are theoretical.

Who pays, and why the answer changes at the state border

This is the part that actually gets argued on site, and two of the three Acts answer it in terms.

Section 30 of the Karnataka Stamp Act, 1957 works through the Schedule article by article. Clause (x) covers an agreement relating to building works or labour or services, that is Article 5(i-d), and places the expense of providing the proper stamp on “the person entrusting the works or availing the services”. In Karnataka the default sits with the client.

Section 29 of the Rajasthan Stamp Act, 1998 goes the other way. Clause (ff), inserted by Rajasthan Act 7 of 2004 with effect from 27 May 2004, says that in the case of a works contract or a sub-contract the duty falls on “the contractor or sub-contractor, as the case may be”. In Rajasthan the default sits with you.

Maharashtra does not list works contracts in section 30 at all, so the instrument falls into the residual clause (g), added by Maharashtra Act 27 of 1985, under which the expense is borne in any other case by the person executing the instrument. For a bilateral agreement that resolves nothing by itself, which is precisely why the next point matters.

The clause that overrides all of it

Section 30 of the Karnataka Act, section 29 of the Rajasthan Act and section 30 of the Maharashtra Act all open with the same six words: in the absence of an agreement to the contrary.

The statutory payer is a default, not a mandate. A single line in the contract settles it, and that line costs nothing to insert and is worth real money when a Rajasthan contract runs to several crores. If your agreement is silent, the state’s default applies, and you may be paying a bill the other side would have accepted had anyone raised it.

Put the stamp allocation in the same part of the agreement that carries the rest of the commercial machinery, alongside the payment terms and the performance security. A contract that already names who pays for the guarantee can name who pays for the stamp in the same sentence.

What an unstamped agreement costs you later

The duty is small. The consequence of getting it wrong is not, and it arrives at the worst possible moment.

Section 34 of the Maharashtra Stamp Act, 1958 provides that no instrument chargeable with duty shall be admitted in evidence by any person having authority to receive evidence, and shall not be “acted upon, registered or authenticated” by any such person or public officer, unless it is duly stamped. The phrase “acted upon” reaches well beyond a courtroom.

Section 33 makes it worse by making it automatic. Every person having authority to receive evidence, and every person in charge of a public office, before whom a chargeable instrument is produced must impound it if it appears not to be duly stamped, and the section adds that this applies “irrespective whether the instrument is or is not valid in law”. It is not a discretion anyone is doing you a favour by exercising.

There is a cure. The proviso to section 34 admits the instrument on payment of the duty, or the amount needed to make it up, together with a penalty of 2 per cent of the deficient portion for every month or part of a month from the date of execution, with a further proviso capping the penalty at double the deficient duty.

Work that through on a real timeline. A deficit discovered four years after execution has long since passed the point where the 2 per cent monthly accrual hits the ceiling, so what you pay is the deficit plus twice the deficit. On a Rajasthan contract where the deficit is itself a lakh or more, that is a three-lakh problem created by a decision nobody remembers making.

How to work out your own state’s figure

Three steps, and none of them requires a consultant.

Find the works contract entry in your state’s Stamp Act Schedule, which may be headed works contract, or may sit as a sub-clause under the general agreement article as it does in Karnataka. Read the payer provision, usually section 29 or section 30, and check whether your article is named there or falls into the residual clause. Then read the amendment notes attached to both, because the live number is frequently a substitution and the superseded text sits right next to it on the page.

That last step is what catches people. Rajasthan’s Rs 15,000 cap is still printed in plenty of secondary sources years after it was deleted in 2019, and quoting it would understate the duty on a large contract by a factor of ten or more.

We have deliberately not published a national rate table. The three states here are the ones whose Schedules were read in full for this piece, and a fourth state’s figure invented by analogy would be worth nothing. Read your own Schedule, or have your counsel read it.

Where this sits in the contract

Stamping belongs to the same stage as the rest of the pre-start paperwork, which means it belongs in the same checklist as the work order review rather than in a later clean-up. On government work the agreement is executed on the department’s standard form, so the stamp question is usually settled by the tender conditions rather than negotiated, which makes it something to read rather than to argue about: see how government construction tenders get bid. And every variation order that materially changes the contract value is worth a second look, because the amount set forth in the instrument is what the duty is calculated on.

Write one line to settle who pays stamp duty

Stamp duty on a works contract is a state subject with no national answer, the spread across states is wide enough to matter on a large contract, and the default payer flips depending on which side of a state line you signed. All of it yields to a single line in the agreement. Write that line, stamp the sub-contracts separately, and read your Schedule’s amendment notes before you trust any figure.

Contractors carrying large receivables while a dispute runs are the ones for whom an unstamped agreement hurts most. If working capital is the constraint, our equipment and working capital finance options set out what is available, and live tenders and project opportunities are listed as they open.

Duties, articles and payer provisions are quoted from the Maharashtra Stamp Act, 1958, the Karnataka Stamp Act, 1957 and the Rajasthan Stamp Act, 1998 as amended, and apply only in those states. Stamp law is amended frequently and the worked figures are illustrative arithmetic from the Schedules, not a quotation. Confirm the current duty and the payer for your own instrument with the registering authority or your legal adviser before executing it. DesiMachines is not liable for decisions taken on the basis of information that may have changed after publication.