Discuss your project
← All use cases

Use case · Procurement

Three quotes.
One clear comparison.
A sound decision.

We start from your procurement policy, framework contracts and past awards. Together with procurement, business units and IT we clarify which criteria count, who may see quotes and where procurement decides. The result is your workflow for quote comparison and supplier evaluation.

CORAProcess assistant

Your team

“Use our procurement policy, the framework contracts and the supplier ratings. Create a workflow for new quotes: read the quotes, capture prices, delivery times and terms and compare them with contracts and previous purchase prices. Check whether the suppliers are approved. Summarise deviations from contracts and show savings potential. Procurement decides on the award; above the value limit a second approval is required.”

CORA is drafting the process …

The description becomes the workflow

Describe once.
Run every time.

Your description becomes a workflow for every request: from the incoming quote to a prepared award decision.

CORA builds the process. Your team reviews the test cases and approves it. Only then does it run for every matching event – with your permissions.

Capture quotes · Compare terms · Prepare award

  1. Quotes
  2. Capture data
  3. Compare
  4. Decision template
  5. Award
Discuss your project

One run in detail

How CORA compares three quotes.

A request in procurement: from three incoming PDF quotes to a documented award.

All names, numbers and values in this example are fictitious.

  1. TriggerThree quotes for request AF-209 have arrived.
  2. AICapture quotes

    Captured from three differently structured PDFs: prices, quantities, delivery times, payment terms and warranty.

  3. CodeCompare total cost
    SupplierTotal costDelivery time
    Supplier A€48,2003 weeks
    Supplier B€45,9006 weeks
    Supplier C€47,1004 weeks
  4. RuleCheck status

    Supplier B is not approved and goes to review. The order value is above the value limit: a second approval is required.

  5. AISummarise deviations
    Supplier A deviates from the framework contract on payment terms (14 instead of 30 days). Supplier C is 2 % above the last purchase price but meets all contract terms. Savings potential: renegotiate payment terms with A.
  6. HumanAward

    Procurement awards to supplier C; the head of procurement approves as the second person.

  7. IntegrationDocument

    Purchase requisition created in the ERP, award reasoning attached to the request.

From existing documents to a tested workflow

From existing documents
to a tested workflow

1Your documents and example cases

RecordQuote AN-3310 (fictitious)
  • Price
  • Delivery time
  • Terms
DocumentFramework contract RV-12 (fictitious)
  • Agreed prices
DocumentProcurement policy
  • Value limits

2Business systems and data

SystemERP
  • Purchase prices
  • Supplier master
SystemContract repository
  • Framework contracts
RuleValue limit
  • Defines the approval path

3People, roles and rights

Role cardProcurement
Prepare award
Role cardBusiness unit
Technical assessment
Place orderBlocked
Only after approval
  1. Build process
  2. Test
  3. Approve

Running process

  1. Quote received
  2. Capture data
Below value limit
  1. Comparison
  2. Procurement decision
Above value limit
  1. Comparison
  2. Second approval
Not approved
  1. Procurement review

Process steps in detail

What AI does – and what rules, code and integrations handle.

CORA uses AI where language, context or unstructured information needs to be understood. Calculations run as tested code, limits and responsibilities as rules, system access through defined integrations. Approvals stay with people.

  • AILanguage model: understands, summarises, drafts2×
  • RuleFixed conditions, thresholds, responsibilities1×
  • CodeCalculations and models, versioned and testable2×
  • IntegrationRead and write access via MCP servers or interfaces2×
  • HumanReview, approval and decision1×
  1. 01

    Capture quotes

    Prices, quantities, delivery times and terms are captured in structured form – even from different formats.

    AI

    Implementation: Language model reads PDF quotes and emails

  2. 02

    Check data

    Calculation errors and missing mandatory details are detected.

    Code

    Implementation: Plausibility checks: units, currencies, totals

  3. 03

    Read master data and contracts

    CORA reads supplier status, previous prices and agreed terms.

    Integration

    Implementation: MCP servers for ERP and contract repository

  4. 04

    Compare total cost

    Quotes are brought to a comparable basis against contract and price history.

    Code

    Implementation: Total cost calculation from price, freight and payment terms

  5. 05

    Check supplier status

    Status and order value define the approval path.

    Rule

    Implementation: Approval status, certificates, value limits

  6. 06

    Summarise deviations

    The AI names contract deviations and risks and explains savings potential with reference to the relevant passages in the quote.

    AI

    Implementation: Language model with framework contract and procurement policy

  7. 07

    Decide on award

    Procurement selects the supplier and records the reasons.

    Human

    Implementation: Procurement, second approval above the value limit

  8. 08

    Document award

    The purchase requisition is only created after approval.

    Integration

    Implementation: Write access to the purchase requisition in the ERP

Connected systems

  • Mailbox or supplier portalreads incoming quotesvia interface (API)
  • ERPreads prices and supplier master, writes the purchase requisition after approvalvia MCP server
  • Contract repositoryreads framework contractsvia MCP server
  • Company sign-inchecks identity and rolevia single sign-on

How we work

We start with your
actual work.

  1. 01

    Understand existing documents

    Procurement policy, framework contracts, evaluation criteria and past awards show us how quotes are compared today. From them we derive comparison fields, minimum requirements and value limits. We clarify deviating practice with procurement.

  2. 02

    Connect data and business systems

    With your IT we connect the mailbox or supplier portal, ERP and contract repository. Supplier number, commodity group and request number link the data. We define where data is read and where comparisons are stored.

  3. 03

    Assign identities, rights and roles

    Identity comes from your company sign-in. Procurement sees all quotes for its commodity groups, business units only the technical assessment. The AI applies these rights; it never triggers orders.

  4. 04

    Test together and go live

    From the description, documents and clarified system access, CORA drafts the process. Together with your business unit we select test cases and expected results. Testing runs without write access. Example tests: Comparable quotes, deviating payment terms, supplier not approved, quote above the value limit.

Your team decides on rules, AI steps and approvals. We activate the tested workflow, compare effort and results and practise the next changes in the skill workshop. Integrations, knowledge and reusable building blocks remain as the foundation for further processes.

Discuss your project

How the case
runs

CORA captures incoming quotes, checks the data and compares total cost against framework contracts and price history. Supplier status and value limits define the approval path; procurement receives a decision template.

What it
produces

Structured quote data, total cost comparison, list of contract deviations, savings potential and a documented award decision, linked to the request.

Where your team
decides

Procurement decides on the award, with a second approval above the value limit. CORA does not place orders or negotiate with suppliers. Suppliers that are not approved go to review.

More use cases

We show you where AI can take work off your hands right away.

Discuss your project