One register for every contract you’ve signed
Customer, vendor, lease, AMC and service contracts in a single registry-of-record — with a clause library, deterministic document assembly, obligations that raise the invoice, a renewal runway and a 0–100 health score. Enabled as a cloud marketplace pack.
A registry-of-record, not another folder
Every contract type lands in one register with folders, a related-contract graph and a timeline. Search is server-side and ranked — name and number weighted above party, above type and department, above notes — with per-user saved and recent searches. Contracts that other modules already own get indexed here while staying billed by their source module, so the register is complete without becoming a second set of books.
Author from clauses, not copy-paste
The clause library is the master: every edit to a clause body snapshots the previous version immutably and bumps the number. A template is a preamble carrying {{merge_fields}} plus an ordered clause set, each clause optionally conditional on contract facts, and the builder dry-runs the assembly against sample facts before you commit. The assembly engine is deterministic and returns an unresolved-fields report, so an incomplete document can be blocked rather than shipped.
Sign, amend, redline
Signatures are collected in an enforced signing order; amendments are first-class; and Redline & Review does a word-level diff between two version snapshots with reviewer assignment and a suggested-change accept/reject flow. All of it works with AI turned off.
Obligations that actually bill
The obligation desk is a book-wide calendar bucketed overdue / due-soon / breached / upcoming / met / undated. Mark an obligation met, or mark it breached and let the server compute the penalty from days late — or, for a monetary customer obligation, raise the invoice straight through the normal sales spine. That bridge is idempotent, so an obligation bills once no matter how many times the button is pressed.
Renewals, risk and the money
The renewal pipeline puts the contracts whose notice window is slipping first, over a month-by-month strip, with schedule-a-reminder and renew-now on each row. A likelihood × impact risk matrix and a compliance calendar sit beside it. Financials give portfolio budget-vs-actual and, per contract, planned gross profit and margin in basis points plus a holds register for retention, security deposits, bank guarantees and advances. The health score itself is deterministic — missing standard-clause coverage, obligation-breach rate, renewal slack and value exposure, 0–100, with the drivers listed most-negative first.
What’s included
- One register for every contract type, with folders & a related graph
- Ranked full-text contract search + saved and recent searches
- Clause library with immutable version history
- Templates: a {{merge_field}} preamble + conditional clause sets
- Deterministic assembly with an unresolved-fields report
- Signing-order-enforced signatures & amendments
- Word-level redline with reviewer assignment and accept/reject
- Obligation desk — overdue / due-soon / breached / upcoming buckets
- Idempotent obligation → sales invoice billing bridge
- Renewal pipeline, risk matrix & compliance calendar
- Financial holds register + deterministic 0–100 contract health
Frequently asked
Is contract management part of the offline desktop app?
No — it’s a cloud marketplace pack. Enable it and a Contracts group appears with the dashboard, register, search, clause library, templates, obligations, financials, redline, renewals, risk and insights. It does not run in, or sync to, the offline desktop edition.
What happens to contracts my other modules already own?
They’re indexed into the register rather than moved. The vertical module that created a contract keeps its own money math; the register is where you find it, search it and watch its obligations and renewal.
Is the health score AI?
It’s deterministic. The as-of date is passed in rather than read from a clock, money is integer paise, and the score comes out of clause coverage, breach rate, renewal slack and value exposure with its drivers listed. An LLM narration can layer on top of the same snapshot — it never replaces the number.
Can it generate the contract document itself?
Yes — pick a template, and its preamble and ordered clause set assemble against the contract’s facts, with conditional clauses included or dropped by rule. Anything the merge could not resolve is reported back so you can fix it before the document goes out.
What exactly is included in Contract Lifecycle Management · Cloud pack?
one register for every contract type, with folders & a related graph, ranked full-text contract search + saved and recent searches, clause library with immutable version history, templates: a {{merge_field}} preamble + conditional clause sets, deterministic assembly with an unresolved-fields report and signing-order-enforced signatures & amendments, and 5 more. Every item on that list is a working screen you can open in the trial rather than a capability described in the abstract.
How is contract lifecycle management · cloud pack handled differently here?
It rests on a registry-of-record, not another folder, author from clauses, not copy-paste, sign, amend, redline, obligations that actually bill and renewals, risk and the money. The distinction that matters is that these are structural rather than cosmetic — the behaviour is built into how records are posted, not layered on as a report you have to remember to run.
Does Contract Lifecycle Management · Cloud pack post to the real books?
Yes, and that is the whole reason it lives in this product rather than beside it. What a registry-of-record, not another folder records lands in the same posted double-entry ledger the Trial Balance, P&L and GST returns are built from — so there is no second set of contract lifecycle management · cloud pack numbers to reconcile against the first.
How does Contract Lifecycle Management · Cloud pack affect my GST?
It feeds it directly rather than sitting alongside it. CGST/SGST and IGST are split from HSN or SAC and place of supply as each document is raised, so whatever contract lifecycle management · cloud pack produces is already correct when GSTR-1, 3B and 2B reconciliation are drawn off the same books. The return matches the accounts because it was never a separate exercise.
Does Contract Lifecycle Management · Cloud pack cost extra?
No. Contract Lifecycle Management · Cloud pack is part of the accounting core rather than a paid add-on, so author from clauses, not copy-paste is there on the entry tier exactly as it is on the highest one. What the tiers change is reach and depth — devices, multi-branch and multi-warehouse reporting, and whether the conversational AI copilots are switched on.
Can I try Contract Lifecycle Management · Cloud pack before committing?
Yes — 14 days, no card. Test contract lifecycle management · cloud pack against your own masters and your own transactions rather than sample data: the questions worth answering here are about your business's edge cases, and a demo dataset is built not to have any.