Event · 8 Oct

bizSupply Upside 2026 Held in Portuguese.

Save my seat

Ontologies

An ontology describes what kinds of documents exist in your organisation and which fields bizSupply should extract from each. The platform ships two of them, Contracts and Invoices, and every document you ingest is classified against one of the two. You extend them with your own categories when your documents need finer classification or extra fields — for example a software subscription category under Contracts, or a fuel category under Invoices.

Last updated:

An ontology describes what kinds of documents exist in your organisation and which fields bizSupply should extract from each. The platform ships two of them, Contracts and Invoices, and every document you ingest is classified against one of the two. You extend them with your own categories when your documents need finer classification or extra fields — for example a software subscription category under Contracts, or a fuel category under Invoices.

The Ontologies page

The page shows the category tree for one base at a time. Switch between Contracts and Invoices at the top, and filter by who owns a category:

FilterWhat it shows
AllThe platform categories plus every extension in your organisation
GlobalOnly the platform categories. These cannot be edited or deleted
OrganizationExtensions visible to everyone in your organisation
PersonalExtensions only you can see

Each extension row has a menu with View, Run on existing documents and Delete. Only organisation owners and admins can create, rerun or delete extensions.

Creating an extension

Click Create and follow the four steps.

  1. Describe. Pick the base you are extending (Contracts or Invoices),

describe the category or fields you need in plain language, and choose whether the result is visible to the whole organisation or only to you. bizSupply drafts a new category for you.

  1. Review. Check the proposed category and its fields in the context of

the full tree. Go back and rephrase if it is not what you meant.

  1. Apply to pipelines. Choose which of your sources should classify

their documents with the new category. Sources are grouped by the pipeline each one runs, and every pipeline is selected by default. Untick a pipeline to leave its sources on the platform categories only.

  1. Result. The category is either ready to use straight away, or held

for a quality review when the draft looks too close to an existing category. Reviewed categories appear on the page once approved.

Custom categories must extend Contracts or Invoices. Any other base is rejected, whether you create the category here, upload a definition file, or use the MCP tools.

What "apply to pipelines" means

A source runs one pipeline, and the pipeline decides which categories its documents are classified against. Attaching your extension to a pipeline means every source on that pipeline picks it up from the next sync onward, with no further action from you. Sources you connect later inherit every extension your organisation already has.

Sources still on the platform default pipeline are not listed in this step, because that pipeline is shared and cannot be changed for one organisation. Give the source its own pipeline on the Pipelines page and create the category again.

Two sources that share a pipeline are selected together. If you want them to diverge, give one of them its own pipeline first.

Applying an extension to documents you already have

A sync only picks up documents bizSupply has not seen before, so a new category has no effect on documents already in the platform until you ask for it. Choose Run on existing documents from the result step or from the row menu:

  1. bizSupply lists the sources whose pipeline includes the category and

how many documents they hold.

  1. Untick any source you want to leave as it is.
  2. Click Run. One processing job is created per source and progress

appears in the processing panel at the bottom of the app, exactly like a sync. See Jobs and syncs.

Reprocessing uses credits like any other processing job. Very large selections are refused with a message asking you to narrow them; run the sources in smaller groups instead.

Deleting an extension

Deleting an extension removes it from every pipeline it was attached to. Documents already classified under it keep their existing classification until they are processed again.

  • Sources — connecting the inboxes and drives

your pipelines read from.

sync or a rerun starts.

are consumed.