Extract 11 commercial terms from vendor PDFs & flag playbook deviations — MSA contract review automation in under 2 minutes per document.
| Counterparty | Acme Corp Pvt Ltd |
| Effective Date | 2026-01-15 |
| Term (Months) | 24 |
| Payment Terms (Net Days) | 30 |
| Late Payment Interest (% p.a.) | 12 |
| Liability Cap (Rs) | 50,00,000 |
| Indemnity Scope | Mutual — IP, confidentiality, third-party claims |
| Governing Law | India |
| Dispute Venue | Bengaluru, Karnataka |
| Termination Notice (Days) | 60 |
| Confidentiality Term (Years) | 5 |
Manual MSA contract review is one of the most time-consuming tasks a procurement or in-house legal team faces during the vendor onboarding cycle — and the one most likely to let critical deviations slip through to execution.
A paralegal or senior finance team member reads the executed MSA PDF, notes payment terms, liability cap, governing law and termination provisions, then cross-references each clause against the approved playbook. Across 20–50 vendor contracts per quarter, that adds up to 40–200 hours of professional time diverted from higher-value work.
A liability cap quietly reduced from Rs 50,00,000 to Rs 5,00,000 — a 90% shortfall — appears on page 18 of a 40-page document. Reviewers working under deadline pressure miss these clauses or fail to record the deviation in the legal team's review log, leaving the company exposed under the Indian Contract Act, 1872 provisions on limitation of liability.
A vendor contract specifying Singapore or England & Wales as governing law means disputes must be litigated or arbitrated outside India, increasing legal spend and rendering Indian court judgments unenforceable — a consequence rarely surfaced until a dispute arises, and a direct violation of most mid-market legal policies under the Arbitration and Conciliation Act, 1996.
Without a structured extraction tool, the legal team's review log — often a shared spreadsheet — is inconsistently maintained. External auditors requesting contract management evidence during year-end fieldwork find gaps that constitute a deficiency in internal controls under ICAI SA 265, creating board-level governance exposure.
The typical manual review time per vendor MSA, including cross-referencing each clause against the playbook and recording the result in the legal team's log. For a company processing 30 contracts per quarter, that is 60–120 hours of senior finance or paralegal time per quarter — and the deviations that matter most (liability cap, governing law, payment terms) are still missed in roughly 1 in 5 reviews.
Each playbook rule in this workflow maps to a specific legal or financial obligation. These are not arbitrary preferences — every threshold has a statutory or commercial consequence if breached by an executed contract.
A limitation-of-liability clause set below the company's actual remediation cost in a vendor failure scenario may be challenged as unconscionable or against public policy under Section 23 of the Indian Contract Act. The playbook floor of Rs 50,00,000 is calibrated to cover the company's expected loss in a data breach or service-failure scenario, making enforceability defensible.
For a domestic arbitration agreement to be valid and enforceable in India, the arbitration clause must designate an Indian seat and be governed by Indian law. A foreign governing law clause — Singapore, England & Wales, or New York — can invalidate the domestic dispute resolution mechanism entirely, leaving Indian court enforcement uncertain under Section 7 of the Act.
Where a buyer contracts with an MSME supplier, Section 15 of the MSMED Act requires payment within 45 days of acceptance of goods or services. Payment terms stretched beyond Net 45 in the executed contract expose the buyer to compound interest at three times the RBI bank rate under Section 16, and the liability is non-compoundable — it cannot be contractually waived. The playbook Net 45 ceiling aligns with this statutory cap.
Section 43A of the IT Act imposes liability on any body corporate that handles sensitive personal data without reasonable security practices. A confidentiality clause with a post-termination duration shorter than 3 years may expose the company to claims that it failed to maintain reasonable safeguards for data exchanged during the vendor engagement, particularly where the contract covers software access, payroll data, or financial information.
Seven deterministic steps from MSA PDF upload to a validated, audit-ready deviation report — in under two minutes per contract, with zero manual clause reading.
Accepts one or more executed vendor MSA PDFs dropped into the Inbox or arriving by email. Cadel classifies each file as an MSA automatically based on document structure (presence of a Key Commercial Terms table, numbered clause body, and signature block) without requiring pre-tagging, cover sheets, or template-level setup per vendor.
Reads the contract's Schedule A — Key Commercial Terms table deterministically, extracting eleven structured fields: counterparty, effective_date, term_months, payment_terms_days, late_payment_interest_pct, liability_cap, indemnity_scope, governing_law, dispute_venue, termination_notice_days, and confidentiality_term_years.
Each extracted field is normalised to a typed value: numeric amounts are stripped of currency symbols and commas (Rs 50,00,000 → 5000000), dates are converted to ISO 8601, strings are trimmed and lowercased for comparison. Downstream playbook rules operate on clean, typed data regardless of how the counterparty's counsel formatted the clause body.
Six deterministic rules from the approved template playbook are applied in sequence: liability_cap_floor (≥ Rs 50,00,000, FAIL), governing_law_india (must equal "India", FAIL), payment_terms_ceiling (≤ Net 45 days, FAIL), termination_notice_floor (≥ 30 days, WARNING), confidentiality_min_term (≥ 3 years, WARNING), and late_payment_interest_min (≥ 9% p.a., WARNING). All six run independently; a FAIL on one rule does not suppress subsequent checks.
Each contract receives a status badge: green PASS (zero deviations), amber WARNING (one or more WARNING-only deviations), or red FAIL (at least one FAIL-severity deviation). Contracts with FAIL deviations are routed to the exception queue automatically; PASS contracts are filed without manual intervention.
Every deviation is written into the Exceptions view with the rule that tripped, the extracted contract value, the required playbook value, and the deviation description — so the reviewing controller can act on it without re-reading the source PDF. The exception row for a liability cap breach records "extracted Rs 5,00,000 vs. required ≥ Rs 50,00,000" in a single line.
A one-click Excel export produces one row per contract containing all eleven extracted fields, each of the six validation results (PASS / FAIL / WARNING), the deviation count, and the overall status — ready to attach to the vendor onboarding file and to the legal team's contract management system as a timestamped audit record satisfying ICAI SA 265 documentation requirements.
Five synthetic MSA scenarios that exercise every playbook failure mode observed in real vendor contract data. Each produces a deterministic outcome an auditor can verify in seconds.
liability_cap_floor fires as FAIL; contract routed to the exception queue; Excel export records "Rs 5,00,000 vs. required ≥ Rs 50,00,000" in the deviation row.governing_law_india fires as FAIL; inbox badge shows RED; both governing law and dispute venue fields flagged non-compliant in the redline summary.payment_terms_ceiling fires as FAIL, rule late_payment_interest_min fires as WARNING; inbox shows 2 exceptions for this contract.termination_notice_floor and confidentiality_min_term both fire as WARNING; contract flagged for legal review but not hard-blocked from the inbox.liability_cap_floor and governing_law_india simultaneously, plus WARNING on confidentiality_min_term — three rule violations across two severity levels.Five full, multi-page vendor MSAs are seeded for this workflow — each a complete six-page contract (recitals, fifteen numbered clauses, Schedules A–F and a signature block) for the same procurement entity, Acme Corp Pvt Ltd, run against the same template playbook.
Liability cap Rs 50,00,000, governing law India, payment terms Net 30, termination notice 60 days, confidentiality 5 years, late payment interest 12% p.a. All six validation checks pass — demonstrates full 11-field extraction and a zero-deviation result.
Rs 5,00,000 is a number that reads plausibly in isolation but is a ten-times shortfall from the playbook minimum — precisely the kind of deviation a time-pressed reviewer can overlook on page 18 of a 40-page document.
Both governing law and dispute venue fields flagged non-compliant in the redline summary. Demonstrates FAIL-severity detection of a jurisdiction policy breach that would otherwise invalidate the domestic arbitration clause.
Demonstrates simultaneous FAIL and WARNING flags on two related commercial terms. Net 90 also breaches the MSMED Act statutory cap for MSME suppliers.
Running the workflow against the five demo MSA files produced the following results. The clean baseline contract passed all six validation checks: liability cap Rs 50,00,000 confirmed at floor, governing law India confirmed, payment terms Net 30 within the Net 45 ceiling, termination notice 60 days above the 30-day floor, confidentiality 5 years above the 3-year minimum, late payment interest 12% p.a. above the 9% floor.
The foreign governing law contract triggered a FAIL on governing_law_india, with the extracted value "Singapore" and dispute venue "Singapore International Arbitration Centre" both recorded in the redline summary. The liability cap breach contract triggered a FAIL on liability_cap_floor, with the extracted cap of Rs 5,00,000 against the required Rs 50,00,000 — a ten-times shortfall that manual review missed in its initial pass.
Across all five contracts, the workflow extracted 55 field values (11 fields × 5 contracts) with no extraction errors on typed fields. The payment terms stretched contract produced two simultaneous deviations — FAIL on Net 90 payment terms and WARNING on 6% p.a. late payment interest — demonstrating that the workflow applies all six rules independently rather than stopping at the first failure. The short termination notice contract triggered two WARNING-severity deviations: termination notice 15 days against the 30-day floor, and confidentiality term 2 years against the 3-year minimum.
The most operationally significant exception class caught was the liability cap breach: a number that appears plausible in isolation (Rs 5,00,000 is a common round amount in Indian vendor contracts) but represents a 90% reduction from the playbook minimum — precisely the kind of deviation a time-pressed reviewer scanning a 40-page PDF for "Rs" amounts can overlook.
For a mid-market legal or procurement team processing 30 vendor contracts per quarter, this MSA contract review automation replaces 60–120 hours of paralegal and senior finance time with a two-minute automated extraction and rule-based comparison — with zero deviation slippage on the six playbook rules.
FAIL-severity deviations (liability cap below floor, foreign governing law, payment terms over Net 45) are surfaced before execution — not during a vendor dispute six months later. The three FAIL-class rules cover the deviation types that legal teams report most frequently finding only after contracts have already been signed. Under the Indian Contract Act, 1872, renegotiating an executed contract is materially harder than refusing to sign a non-compliant one.
The Excel export — one row per contract, all eleven extracted fields, each of the six validation results, deviation count, overall status — satisfies the contract review log documentation requirements that external auditors request during year-end fieldwork under ICAI SA 265. Any reviewer, including an auditor who did not run the workflow, can independently verify every pass and every deviation without re-reading the source PDF.
The six playbook thresholds (liability cap floor, governing law jurisdiction list, payment terms ceiling, termination notice floor, confidentiality minimum, late payment interest minimum) are configured in the workflow's playbook settings and can be adjusted per entity, vendor tier, or spend category. A strategic partner might receive a relaxed payment terms ceiling; an MSME supplier might trigger a tighter Net 30 enforcement aligned with MSMED Act Section 15 obligations.
The questions legal, procurement, and finance controllers ask most often before deploying vendor contract review automation.
Upload the executed vendor MSA PDFs — drop them into the Inbox together and Cadel classifies each file as an MSA automatically. No template, cover sheet or pre-tagging is needed.
Eleven fields per MSA: counterparty name, effective date, term length (months), payment terms (net days), late payment interest (% p.a.), liability cap (Rs), indemnity scope, governing law, dispute resolution venue, termination notice period (days), and confidentiality term (years). Values are read deterministically from the contract's Schedule A — Key Commercial Terms table and the matching clause body.
A FAIL is a hard playbook breach — a liability cap below Rs 50,00,000, a governing law other than India, or payment terms over Net 45 — that should be renegotiated before execution. A WARNING covers softer limits: a termination notice below 30 days, a confidentiality term under 3 years, or a late payment interest rate below 9% p.a. Both appear in the Exceptions view and the one-click Excel export.
Yes. The governing-law field is extracted regardless of its value and compared against the company's approved jurisdiction list. The playbook requires Indian governing law, so any non-India jurisdiction — including Singapore, England & Wales, or New York — triggers a FAIL. Foreign-counterparty contracts process identically; only the comparison outcome differs.
Each MSA runs through the six playbook checks. Anything that fails is surfaced in the Exceptions view with the rule that tripped, the extracted value and the required playbook value, so you can act on it without re-reading the PDF. Clean contracts pass straight through.
Yes. The six validation rules (liability_cap_floor, governing_law_india, payment_terms_ceiling, termination_notice_floor, confidentiality_min_term, late_payment_interest_min) are configured in the workflow's playbook settings and can be adjusted per entity, vendor tier or spend category without code changes. Strategic partners with higher credit standing can receive relaxed thresholds; MSME suppliers can be enforced more strictly to align with MSMED Act payment obligations.
Yes — export the processed contracts and their validation results to Excel from the Inbox toolbar. The export has one row per contract with all extracted fields, each check result, the deviation count and the overall status, ready for the legal team's review log and for year-end audit evidence under ICAI SA 265.
No. Your contracts are processed only to produce this workflow's results and are not used to train any model.