Contracts
The Contracts page (sidebar → Navigation → Contracts) is the source of truth for every contract bizSupply has found in your connected sources.
The Contracts page (sidebar → Navigation → Contracts) is the source of truth for every contract bizSupply has found in your connected sources.
The list page
Each row is one contract. Columns shown:
| Column | Meaning |
|---|---|
| Supplier | The counterparty extracted from the contract. |
| Region | Geographic scope (if the ontology defines a region field). |
| Start / End / Renewal date | Dates extracted from the contract body. |
| Status | Derived from the dates — see below. |
| Actions | A shortcut to the detail page. |
Contract status
| Status | Meaning |
|---|---|
| Active | Today is between the start and end dates, and the contract has no renewal alert. |
| Upcoming renewal | The renewal or end date falls within the configured alert window (defaults to 30 days). |
| Expired | The end date is in the past. |
| Awaiting review | The contract was extracted but some key field is missing or low-confidence — a human should confirm it. |
Status is computed on the fly from the extracted dates — it's not something you edit directly. If a contract's dates look wrong, fix them on the detail page and the status will update.
Filtering and searching
The top of the list has filters for Supplier, Region, and Status, and a Search box that matches against filename and supplier.
If you can't find a contract you expect to see:
- Check the filters aren't hiding it.
- Check Sources — was the document in a folder you're scanning?
- Check the document wasn't classified as something other than a contract
(e.g. an invoice). bizAssistant can look this up with list_documents.
The detail page
Click any row to open /contracts/<id> — the detail view.
Left: extracted fields
Every field defined by the ontology this contract matches — supplier, region, start date, end date, renewal date, amounts, category, custom fields. Each field shows:
- The extracted value.
- A confidence indicator (high / medium / low).
- An Edit pencil so you can correct or override.
Low-confidence fields are highlighted. Correcting them trains nothing automatically — bizSupply doesn't fine-tune on your edits — but the corrected value is what every other page (dashboard, renewals, benchmarks) uses from that point on.
Right: document viewer
The original document — PDF, email body, or attachment — is shown on the right. Click Download original to get the file as-is.
Bottom: related documents
Documents bizSupply has linked to this contract — typically invoices that reference the same supplier and overlap the contract's date range. Relationships are detected by pipeline rules, not guessed by an LLM.
Where the data comes from
- A source (Gmail, Drive, etc.) delivers a document to bizSupply.
- A pipeline runs — a series of plugins that classify the document as
a contract (or not) and extract fields based on an ontology.
- A job represents one pipeline run on one document. Jobs can
succeed, fail, or land in "awaiting review". See the Jobs and syncs page for more.
- Successful contracts show up here.
If a contract you expect isn't here, the most common reasons are:
- The source sync hasn't run yet (check Sources page).
- The document was classified as something else (ask bizAssistant to look
up recent documents).
- A job failed on that document (ask bizAssistant "Why did my last job
fail?").
Exporting
To export contracts, open the API Keys page, create a key, and use the Plugin Service API to list contracts. A one-click CSV export is on the roadmap, not yet available in the UI.