A register of every contract
Leases, service, maintenance, cleaning, insurance, management and sale contracts, each with its own type, numbering and rules.
Leases, service agreements, maintenance and insurance contracts in one register, linked to the assets they cover. Approvals, renewals, invoices, payments and statements follow the contract, and alerts warn you before anything lapses.
Contracts are usually kept in folders, with the money in a separate system and the assets in a third. Here the contract, its assets, its approvals and its finance are one record.
Leases, service, maintenance, cleaning, insurance, management and sale contracts, each with its own type, numbering and rules.
A contract covers no asset, one or many, and an asset can have many contracts. Each asset shows its contracts, and conflicts are flagged.
Approval workflows with stages and deciders, with rejection and return rules and a time limit, so nothing waits unseen.
Automatic renewal, new periods, and amendments that are approved before the values change. Previous values stay on record.
Payment schedules, invoices from the dues, payments allocated in order, and deposits and guarantees with expiry alerts.
Expiry, notice deadlines, dues, missing documents, ending coverage and expiring guarantees reach the right person on time.
Follow a contract through its life. Click a step, or let it play.
A lease is created from the lease type, with its required parties, documents and the assets it covers.
The contract goes to its first stage, then to the next, each decided by the people assigned to it.
The contract becomes active. Notice and expiry dates are tracked, and alerts are ready.
Three monthly dues are invoiced together. A payment settles the oldest dues first.
The statement of account shows every charge and payment with a running balance, ready to print.
Illustrative example on sample data.
Each type carries its numbering, parties, documents, assets and approval workflow.
Approval stages decide the contract. Without a workflow it is approved when submitted.
Renew, amend, suspend or terminate with a reason, and keep every previous value.
Invoice the dues, record payments and print the statement of account.
Required parties, documents and assets are checked before a contract is submitted or activated. Dates must make sense, and an empty contract cannot go live.
Contract value, scheduled dues, invoiced, collected and outstanding are shown apart. Totals are per direction and currency, so a lease you receive is never added to a service you pay.
Alerts ride on the communication engine: expiry, notice deadlines, dues soon and overdue, missing documents, ending coverage and guarantees about to expire.
Every contract has an owner organisation. Registers, reports, pickers, prints and approvals show only what the user is allowed to see, and every change is recorded.
The cost of contracts is rarely in the signing. It is in the notice period nobody saw, the invoice sent late and the guarantee that expired.
Notice and expiry alerts reach the responsible person before the date, not after.
Invoices come straight from the schedule, and every payment lands on the right due.
Approvals, amendments and terminations keep their reasons and their history.
See every contract that covers an asset, and every asset a contract covers.
Have a question that is specific to your organisation? A solution engineer will answer it against your own assets, processes and data.
Yes. A contract covers no asset, one asset or many, and an asset can have many contracts. Each asset has a Contracts tab, and a conflict warning appears when contracts of the same type overlap on one asset.
Leases, service, maintenance, cleaning, insurance, management and sale contracts come ready, and you can add your own types with their own fields, documents and approval workflow.
Each type points at an approval workflow with stages. Every stage has deciders, a time limit and rules for approval, rejection and return. A type without a workflow is approved on submission.
Yes. Plan a payment schedule, issue numbered invoices from the dues, record payments that settle dues in order, hold deposits and guarantees, and print a statement of account. It does not post accounting entries.
Yes. Every contract has an owner organisation, and users see only the contracts of the organisations in their scope.
Bring a lease or a service agreement. We will set up its type, approval stages and payment schedule during the call.