Module
Contracts
Every contract on one register, and the date each one needs a decision — before silence renews it or lets it lapse.
What it produces
- The register: counterparty, kind, term, notice period, renewal, value, payment terms, Incoterm, price validity, exclusivity, governing law, who signed
- The decision date per contract — expiry less notice — and a calendar of what needs one in the next ninety days
- Notice passed: contracts that will renew or lapse by silence; expired contracts still being traded on; prices past their validity
- Obligations each contract imposes, with owners and due dates, recurring ones re-raised when closed
- Renew, terminate and close as a named person's act, audited
A worked example
38 active · 4 decisions in 90 days · 2 notice passed · 3 obligations overdue
SC-2024-011 Resin Ltd: notice date 2026-08-20 has passed — renews itself on 2026-11-18 for 12 months
SC-2023-004 Pigment Co expired 2026-06-30 and 7 purchase orders carry a later date — trading without a contract
FR-2025-002 Ocean Line: prices valid until 2026-08-31 — bookings since are at a rate nobody re-agreed
SA-2025-009 Gumi: quarterly rebate statement due 2026-08-31, 4 days ago (A. Shah)
Illustrative figures. On your tenant the same page shows yours.
Why it is hard
The part that is not a report.
A contract renews itself on the day nobody was watching, or lapses while purchase orders keep going out under it. The register holds what the signed document says — term, notice, renewal, prices, obligations — and subtracts the notice period so the decision date is on a calendar ninety days out, not in a drawer.
Opened by the procurement lead, the sales manager and the supply chain manager — what each of them sees first.
Said before you ask
What is not finished.
A register, not a document system. Dates and terms are typed from the signed document or imported from the legal team's sheet; nothing here reads a clause from a PDF, and no contract is marked renewed or terminated except by a named person.
Where this sits
One of 23 modules, on one engine.
Contracts reads the same reconciled data as everything else SIAARU runs — connected read-only to your ERP, scored on the way in, measured in SQL. How that engine works is a page of its own. The other 22 modules, each with the state it is really in and the reason where it is not switched on, are on the module list; what this one costs, and what it costs beside the rest, is on the pricing page.