A Sales Contracting Playbook: From Quote to Signed Contract to Invoice Without Losing the Deal
A sales contracting playbook for Indian companies: the quote-to-contract flow, an approval matrix that keeps legal out of standard deals, the GST e-invoicing tie-in, and the three metrics that show whether contracts are slowing revenue.
Sales teams do not dislike contracts; they dislike waiting. Most of the waiting comes from three places: the contract starts from scratch instead of the quote, every deal goes to legal regardless of risk, and nobody knows where the document is. This playbook fixes the flow for an Indian company and connects it to invoicing so the deal closes in the books as well as in the CRM. Position as of October 2026.
The flow
- Quote in the CRM with product, price, term and payment terms from an approved price book.
- Contract generated from the quote: the CRM record populates the customer agreement template (parties, scope, fees, term). No re-typing.
- Risk-band check against the approval matrix; standard deals skip legal.
- Negotiation in redline with the fallback positions sales is allowed to offer.
- Stamp and sign: e-stamp if chargeable, then e-signature by the customer and the company signatory.
- Obligations extracted: renewal date, notice window, payment milestones, SLAs, into the register.
- Invoice: the signed contract triggers the first invoice in the accounting system, e-invoice generated where the company's aggregate turnover exceeded Rs 5 crore in any financial year from 2017-18 (Notification No. 10/2023-Central Tax, effective 1 August 2023).
The approval matrix for sales
| Band | Criteria | Approver | Turnaround target |
|---|---|---|---|
| Standard | On template, list price or approved discount, standard payment terms, no personal-data processing | Sales manager | Same day |
| Variation | Discount beyond threshold, payment terms beyond 60 days, minor clause changes from fallback list | Sales head + finance | 2 days |
| Non-standard | Liability cap change, indemnity, exclusivity, customer paper, personal-data processing | Legal + CFO | 5 days |
Two Indian points to build into the bands. First, if the customer is itself a micro or small enterprise supplier to you in another relationship, nothing changes; but if you are the MSE supplier, your own invoice terms are capped at 45 days under section 15 of the MSMED Act, 2006, and your customer's deduction depends on paying you in time under section 43B(h) of the Income-tax Act, 1961; sales should know this is a selling point. Second, if the deal involves processing customers' personal data (a SaaS deal with user data), the contract needs processor terms under section 8(2) of the DPDP Act, 2023 and belongs in the non-standard band.
Fallback positions sales can offer without asking
Write them down. Examples:
- Payment terms: 30 days standard; 45 days for annual prepaid; 60 days needs finance.
- Liability cap: 12 months' fees standard; 24 months with finance approval; never unlimited.
- Termination for convenience by customer: 90 days' notice after a 12-month minimum.
- Non-compete requested by customer: refuse post-term restrictions (void under section 27 of the Indian Contract Act, 1872); offer confidentiality and non-solicit.
- Governing law: Indian law, arbitration seat in your city; foreign law only for non-standard band.
Execution details sales gets wrong
- Signing before stamping (section 17 of the Indian Stamp Act, 1899 requires stamping before or at execution).
- Letting the customer sign on its own paper and losing the audit trail.
- Accepting a PO "subject to our terms" that conflicts with the signed agreement; state in the agreement which document prevails.
Three metrics
- Quote-to-signature days by band. The standard band should be under three days; if it is not, the template or the matrix is wrong.
- Share of deals in the standard band. Above 70% means the fallbacks are doing their job.
- Signed-to-invoiced days. If the contract is signed and the invoice lags a week, the integration is missing.
CRM-CLM-accounting: what to connect
- CRM to CLM: opportunity fields populate the template; contract status returns to the opportunity.
- CLM to accounting: signed contract creates the customer and the first invoice; payment terms and milestones flow to receivables; e-invoice generated if applicable.
- CLM to obligation register: renewal, notice and SLA dates with the account owner as the alert recipient.
Where Legatio fits. Legatio generates the contract from CRM data, applies the band and fallback rules, stamps and signs, extracts the obligations and hands the signed record to accounting. The price book, the matrix and the fallbacks are your commercial policy.
Position stated as of October 2026. General information, not legal or tax advice.