Contract Register
Where do all our contracts live, and what does the record actually enforce?
The register holds every contract as a validated record: unique contract number and external reference, lookup-driven classification, the contracted party plus additional partner members, direction flags for purchase, sale, and project, the settlement account, the execution period, and the agreed value.
Referenced across5 other parts of continON
How it works
A contract’s identity is enforced on save. The contract number must be unique in the organization, as must the external reference; the execution period start must not follow its end; and the register refuses a second open contract with the same contracted party over an overlapping execution period — a guard against parallel agreements nobody intended. Classification is lookup-driven: contract type, classification and level, procedure type, size, and partnership type all come from your organization’s reference data.
Contracts are multi-party where reality is: beyond the contracted party, additional partners can be recorded as members of the agreement. Each contract can link the chart-of-accounts entry it settles against and, for delivery agreements, carries order delivery days and a multiple-delivery flag that downstream ordering reads. A project contract links its project, and projects declare whether they allow more than one contract — the register enforces that too.
Documents attach directly to the record — the signed agreement, annexes, correspondence — stored through the platform’s file service with its permissions, so who can open the contract file is controlled like any other document. The lifecycle closes explicitly: a contract is marked completed or failed, and closed contracts stop being offered anywhere new transactions are created.
What the register holds
6 on the record- Validated identity
- Unique contract number and external reference per organization, with an ordered execution period, checked at save.
- Overlap protection
- A second open contract with the same party over an overlapping period is refused — parallel agreements must be deliberate.
- Multi-party membership
- The contracted party plus additional partner members are recorded on the agreement itself.
- Direction and account
- Purchase, sale, and project flags say what the contract governs; a chart-of-accounts link says where it settles.
- Documents with permissions
- Contract files attach through the platform document service, carrying its access control.
- Explicit closure
- Completed and failed states end the contract’s active window and remove it from transaction pickers.
What this touches
- Contract lots & items
The priced substance underneath the register header. - Contract activity
The transactions that ran under each registered agreement. - Chart of accounts
The settlement account each contract links to. - Project management
Project contracts link their project, with multi-contract control enforced. - Document management
Attached contract files are stored with the platform’s file permissions.
See contract register running in continON.
A guided walkthrough on a sanitized demo tenant — this capability inside its module, on the shared platform.