Contract Management

A contract in continON is a structured record, not a filed PDF. It holds a unique contract number and external reference, a title, lookup-driven type, classification, procedure type, and size, the contracted party plus any additional partner members, its direction — purchase, sale, project, or a combination — the account it settles against, the execution period, the agreed value, and delivery terms. The register validates as it saves: duplicate numbers and references are rejected, the execution period must be ordered, and a second open contract with the same party over an overlapping period is refused.

Underneath the header, the agreement’s substance is modeled. Lots split the contract into named parts, each with its own execution period or the contract’s, a contracted quantity, a flexible-price flag, a lot price capped by the contract value, and recorded price justifications. Contract articles price the actual items — quantity, price per unit, and a remaining quantity that counts down as orders and sales consume the agreement, with line totals capped by their lot’s price.

The register is where the rest of the platform looks before it transacts. Active purchase contracts appear in supplier order building with their delivery days; active sale contracts drive contracted sales and contract-linked customer orders at locked prices; projects link to the contract they deliver, with a control over whether a project may carry more than one. The activity view unions those sales, purchases, and projects into one history per contract, until the record is closed as completed or failed.