Enclessa Contracts is the module that produces the document an organisation sends a customer: what is being agreed, what recurs, what it includes, what exceeding it costs and what the total is. A contract is filled from the customer record rather than from a form, built out of typed blocks over a clause library so a shared paragraph is written once and referenced, checked by a readiness report before it may leave, and issued as a deterministic PDF signed with the organisation’s own certificate and frozen against further change.
Open betaThe platform is being built in the open, so parts of it are not there yet, behaviour changes between releases, and no availability figure is committed while it is in beta. What is still being built.
At a glance
- Availability
- Module, off by default
- Requires
- Customers. A contract with no counterparty is not a document
- Signing
- PAdES with the organisation’s own PKCS#12, optional RFC 3161 timestamp
- Retention
- Eight years, set by AO §147 and HGB §257 rather than by us
Where does the text come from?
From templates made of typed blocks over a closed set of variables, started from the ones shipped with the product and then owned by the organisation — five starter templates per language, in German and English. Shared paragraphs live in a clause library and are referenced rather than copied, so changing one changes it once. The parties block prints from the customer record, which is why the module requires Customers rather than merely preferring it.
- A thirteen-block document model over a closed variable set
- A clause library, so a shared paragraph is written once and referenced
- Starter templates in both languages, then owned by the organisation
- The parties block prints from the record, not from a form
What stops a document leaving half-finished?
A readiness report of around twenty checks that names the field behind each one and disclaims itself rather than pretending to be legal advice. It blocks on a variable with nothing behind it — an organisation with no IBAN cannot issue a document whose payment paragraph prints one. Issuing allocates a number under a lock and freezes what was signed: the arithmetic is integer cents with per-position VAT, and two renders of the same contract are byte-identical.
- A readiness report naming the field behind every check
- A number allocated under a lock, and never reused
- Integer-cent arithmetic with VAT per position
- Versions, amendments, sending, countersigning and ending
What this does not do
- Contracts is off until an operator enables the module, and requires the Customers module.
- Annex upload, a consumption statement against the hours Time recorded, and .docx import are deferred: the block type exists for the first, the route does not.
- There is no signing ceremony for the counterparty and no qualified electronic signature. What the module produces is a PDF the organisation has sealed, not a two-sided signing flow.
Related
Where this shows up
Contracts: common questions
Does Enclessa do contract management?
How is an Enclessa contract signed?
Can a contract be changed after it is issued?
Encrypted collaboration, hosted in Europe.
Create a workspace in a couple of minutes. It is yours at your-team.enclessa.app, hosted in the European Union, with encrypted direct messages from the first one you send.
Open beta. Free plan, no payment card to start.