There are two ways in. Both end in the same place: confirmed fields that Glimps can match on.
Upload the document
Choose the supplier, give the contract a reference, and drop the file. PDF or plain text, up to 18 MB.
Glimps reads the document and fills in draft values. Reading takes less than a minute.
A draft value is a proposal, nothing more. Glimps does not match on anything a person has not confirmed.
Fill it in yourself
No document to hand, or the agreement lives in a mail thread? Choose Fill it in yourself and type the terms. The contract is created from what you type.
The fields
Needed for matching
Six fields must be confirmed before Glimps holds the contract against invoices:
Processing
These decide how strict matching is, and what invoices under this contract get by default: allowed deviation, expected day of the period, and the default ledger account, VAT code, and cost center.
Term end, renewal date, notice period, tariff structure, and indexation clause. These are taken from the contract text for reference. They change nothing about matching, but they are what you want to see three months before the notice deadline.
Confirming
Confirm each field once you have checked it against the document.
Confirmed values are permanent. You cannot edit them afterwards. If the terms change, record a new version. This is what makes the register worth trusting: a confirmed value is what somebody actually agreed to, not what somebody typed last.
New versions
Terms change. Prices go up, periods get extended.
- Upload a changed contract with the same reference, and it becomes a new version.
- Record the change by typing the new terms yourself.
The new version takes over. Earlier versions and their confirmed values are kept and stay readable. A field you leave empty in the new version is no longer part of the contract.
Expiring contracts
A contract close to its end date carries a notice, with the notice deadline next to it. An expired contract says so too. Nobody has to keep a spreadsheet of notice periods. 