> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useglimps.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Contract register

> Record what you agreed, and hold every recurring invoice against it.

Rent, leases, subscriptions, cleaning, service agreements. These invoices have no purchase order, so nothing holds them against anything. They get paid because they always get paid.

The contract register fixes that. You record what was agreed, and Glimps holds every invoice from that supplier against it.

The contract register is not available for every company yet. If it is for yours, switch on **Use the contract register** under **Settings > Booking defaults**. Then open **Contracts** in the sidebar. No switch there? Ask Glimps to turn the register on.

## What it gives you

* An invoice that matches the agreement is recognised as such, and can skip the approval step.
* An invoice that deviates from the agreed tariff says so, before it is booked.
* A second invoice for the same period is caught.
* An invoice that never arrived is noticed, because Glimps knows one was due.
* Notice periods and end dates are visible before they pass.

## How a contract works

<Steps>
  <Step title="Record it">
    Upload the contract, or fill the terms in yourself. See [Recording a contract](/contracts/record).
  </Step>

  <Step title="Confirm the fields">
    A person confirms each field. Glimps never matches on a value it extracted but nobody checked.
  </Step>

  <Step title="Matching starts">
    Once the six required fields are confirmed, incoming invoices are held against the contract.
  </Step>

  <Step title="Periods are tracked">
    Glimps works out which invoices it expects, and which have arrived. See [Expected invoices](/contracts/expected-invoices).
  </Step>
</Steps>

## What you see on an invoice

| Notice | Meaning |
| - | - |
| Matches the contract | Amount and period fit the agreement |
| Tariff differs from the agreement | The amount is outside the allowed deviation, with the expected value next to it |
| Second invoice for this contract period | An invoice for this period already arrived |

Every notice links to the contract, so you can read the terms without leaving the invoice.

## Skipping approval

A contract you already approved when you signed it does not need approving every month. On the contract you can switch on **Skip authorization**, either until the contract ends or until you turn it off.

Glimps records who switched it on, when, and how many open invoices it applies to.

<Warning>
  This applies to invoices that fit the contract. An invoice that deviates still goes the normal route, which is the whole point of recording the terms.
</Warning>

## Archiving

Archive a contract that has ended. It stops matching and stops expecting invoices, its history stays readable, and you can restore it.

## Two contracts with the same supplier

If a supplier has two running contracts in the same period, Glimps assigns invoices by amount. If the amounts are too close to tell apart, contract automation is switched off for that supplier and the invoices take the normal route.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.