Skip to content

Supplier register: Kbis and certificates with expiry

Suppliers send their Kbis extract or vigilance certificate. The AI reads the document type, company, registration number and issue date, a validity end date is computed (6 months), and your suppliers table is updated (columns: company, siren, document, issued_on, expires_on). Filter this table by expiry to chase renewals in time.

By
Loop & Roll team · Official
Copied
0 times
Steps
5
Version
1 · 18 October 2026
Requires
Loop & Roll 1.0.0 or later

Workflow graph

Supplier register: Kbis and certificates with expiry Hover a node to see its role · Drag to move the graph
Certificate received — Email receivedCertificate receivedEmail receivedRead the document — Read attachmentsRead the documentRead attachmentsIdentify the document — ExtractIdentify the documentExtractModelCompute the expiry date — Compute a dateCompute the expiry…Compute a dateUpdate the register — Table — insert or updateUpdate the registerTable — insert or updateOpenAI — OpenAI (GPT)OpenAIgpt-5-mini
Supplier register: Kbis and certificates with expiry

How it works

  1. 1

    Certificate received

    trigger.email

  2. 2

    Read the document

    attachment.extract_text

  3. 3

    Identify the document

    ai.extract

  4. 4

    Compute the expiry date

    date.compute

  5. 5

    Update the register

    table.upsert

What you will fill in after import

Nothing personal travels with a template: connections, mailboxes, tables and recipients are left blank for you to pick in your instance.

Tables to choose
Update the register · table
Connections to choose
OpenAI · connection (llm_provider)