Contracts Through a Tax Lens: Clauses That Create Hidden Costs

Most tax disputes that reach my desk did not start in an audit. They started in a few lines of contract wording signed a year earlier without a financial read-through. This note is for managers who see contracts before they are signed and want to know which clauses generate hidden cost, and what to write instead.

A contract is a tax document

In an Iranian tax audit, the contract is the first document an assessor asks for. The nature of the income, the timing of recognition, the withholding duty, VAT treatment and even whether an expense is deductible are all inferred from that text. At the moment of signature you lock in a large part of your tax position on that transaction, and no amount of later argument fully unlocks it.

A financial read-through takes a few hours. Its impact is sometimes worth several percent of contract value. Nothing else in a finance function has that return ratio.

The price clause and VAT

The most common error is stating a price without deciding VAT treatment. Silence tends to be read against the supplier, who nonetheless remains legally responsible for collecting and remitting the tax. Registration and filing mechanics are covered in the VAT guide; here the point is purely the wording.

Suggested text: the contract price excludes value added tax and duties; the tax is added to each invoice at the statutory rate in force and settled together with each payment. If the counterparty is outside the VAT system, say so explicitly and state why, so it cannot become a dispute later.

The deductions clause

The second common source of leakage is failing to say who bears statutory deductions and on what base.

Wording never removes the legal obligation to withhold; it only decides who carries the economic burden. The list of payments that attract deduction is in the note on withholding tax.

The invoicing clause

Until a few years ago this was boilerplate. It is now critical. If the seller does not register an electronic invoice in the taxpayer portal, the buyer faces two exposures at once: loss of input credit and disallowance of the expense in the income tax audit. The full mechanism is in the taxpayer system guide.

Suggested text: the seller shall register the electronic invoice for each payment in the taxpayer system within the statutory window, and payment is conditional on that invoice appearing in the buyer's portal.

Guarantees and stamp duty

There is a persistent belief that every contract carries stamp duty. It is not accurate. The Direct Taxes Act imposes no general stamp duty on contracts, but promissory notes, bills and company shares are subject to it. Because contract guarantees are typically taken as promissory notes, that cost belongs in the project estimate. For current rates and scope, check the latest circular from the tax administration.

Social security clearance

In contracting work, the assessment of social security contributions on the contract is one of the largest settlement risks. Until clearance is obtained, the employer remains exposed.

A workable clause does three things: names who must obtain the clearance, makes the final payment or release of retention conditional on producing it, and gives the employer the right to settle directly from amounts owed if the contractor misses a stated deadline.

Timing, advances and revenue recognition

Invoice timing and revenue recognition are separate questions and the contract should address both. An advance is not revenue in itself, but if an invoice is issued against it a VAT obligation arises. In long-term contracts, the basis for progress certificates should be written so that it matches the revenue recognition method used in the books; a mismatch between the two is one of the first things an assessor notices.

Escalation and late payment clauses

In an inflationary economy an escalation clause is necessary, but its drafting has tax consequences. Written as an increase in contract price, it is simply more revenue and is easy to document. Written as compensation for damages, it becomes harder to defend in an audit. My preference is always a formula that increases the contract price. The same logic applies to late payment charges.

A pre-signature checklist

1. Decide VAT treatment and refer to the statutory rate in force, not a fixed number.
2. State the deduction base and who bears it.
3. Add the e-invoicing obligation and tie payment to it.
4. Include guarantee instruments and their stamp cost in the estimate.
5. Make the final payment conditional on social security clearance.
6. Align invoicing milestones with the revenue recognition basis.
7. For non-resident payees, check the applicable double tax treaty before agreeing a net figure.
8. Add a mutual undertaking to exchange the data each side needs for quarterly reporting.

When the contract is already signed

Amendment is possible but limited. An addendum can fix future clauses and usually works for payments not yet made. What is generally not recoverable is a duty whose deadline has passed — a deduction that should have been made, or an invoice not registered in time. At that point, shift the goal from correcting the past to documenting a defence.

Key takeaways

• The contract is the first document read in an audit, so treat it as a tax document.
• Never leave VAT treatment or the deduction base to silence.
• Tie payment to registration of the electronic invoice.
• Final payment should be held against social security clearance, not released before it.
• A pre-signature financial read-through is the cheapest tax control available.