The signed version, found in seconds.
Numbering that follows your own rules. Approval chains that follow the value. One current version with a readable history behind it, and an archive that respects who is allowed to see what.
What it does
The problem
Sound familiar?The numbering rule lives in somebody's habit. The register is a spreadsheet, the archive is a folder tree, and the approval threshold is remembered rather than enforced. Finding the signed version of a contract annex depends on who is in the office that day.
None of it feels broken enough to fix, until an auditor asks for the complete file of one project.
The rule decides the route
A document type and a value are enough for the system to know who has to sign, in what order, and what number it carries.
One document, mid-approval
Two signatures required: the value is above the 50,000 EUR threshold for this document type. The rule put Finance in the chain, not a person's judgement.
What the module does
Numbering by your rules
A pattern per document type, set and changed by your own people. The number is assigned by the system, so two documents never carry the same one.
Approval that follows the value
Chains per document type and per threshold, with parallel approvers and conditional steps. The threshold is enforced, not remembered.
One current version
With the full history behind it, readable and marked. Nobody has to guess which file in the folder is the one that was signed.
Search that respects permissions
Across metadata and the text inside documents, filtered to what the person searching is allowed to see. No results they cannot open.
Retention applied, not remembered
Rules per document class decide what is archived and what is kept how long, without anyone filing by hand.
Correspondence registers
Incoming and outgoing, linked to the projects and contracts they belong to, so a project's whole file is a filter rather than a search party.
What changes
Month-end stops being typing
The registers the organization has to produce come out of the record. Nobody rebuilds them in a spreadsheet from the folder tree.
The threshold is enforced
An approval that needed two signatures gets two signatures, because the rule routes it. Not because somebody remembered the policy.
One project, one file
Contracts, annexes, correspondence and approvals for one project are one filter away, in the order they happened.
New document types are configuration
A new type with its own numbering, its own chain and its own retention is a setup task, not a development request.
The parts that are not specific to this module. Sign-in, access rules, the audit trail, workflow and storage belong to the core underneath. This module adds numbering, thresholds, registers and retention.
Inside OmnicornQuestions we hear
Can we keep our numbering format?
Yes. The pattern per document type is yours to define and to change later, without us in the loop.
What happens to the archive we already have?
It comes in with its metadata, so the register does not start empty. What cannot be mapped automatically is listed rather than guessed.
Does it talk to our accounting system?
Through a connector, so a financial record is entered once. Credentials for that connector stay in a vault and never reach a browser or a log.
Who can see which documents?
Access rules per role, per unit and per project. Search results never include a document the person could not open.
Is the signed file still the source of truth?
The signed file is kept, and so is every version before it. The record adds who approved it, when, and under which rule.
Bring one document type and its approval rule.
The numbering pattern, the threshold, and the register it belongs to. We will set it up and you will see your own document move through the chain.
Let's meet