Procura

Procurement scenarios

4 interactive scenarios: HR single source, office call-offs, contractors and AV sourcing to catalog. Try Procura on fictional data. Start with the core P2P flow. Click a step to open the matching role.

Role legend

  • Requester

    Raises catalog and off-catalog requests.

  • Approver

    Approves requests, invoices and timesheets.

  • Buyer

    Sourcing, contracts, orders and invoice matching.

  • Supplier

    Bids and PO fulfillment.

  • Contractor

    Reports MD on projects.

  • Controller

    Budgets, cost centers and incoming-invoice matching.

Glossary

  • Požadavek

    Order request — internal purchase ask before a PO exists.

  • Podnět

    Proposal to purchasing (new supplier, catalog item, RFI) — not yet an order request.

  • Sourcing

    Supplier selection: RFI, RFP, RFQ or e-auction before contract / PO.

  • Single source

    Only one viable supplier — no competition; full approval always.

  • P2P

    From order request to payment (procure-to-pay).

  • PO

    Purchase order.

  • GR

    Goods receipt — the requester confirms the goods or service actually arrived.

  • MATCHED

    Matched invoice — aligns with the PO and is approved for payment.

  • Award

    Awarding the deal to the Sourcing winner.

  • RFI

    Market check without a price (request for information).

  • RFQ

    Price request (request for quotation).

  • RFP

    Sourcing with a solution proposal (request for proposal).

  • MD

    Man-day — 8 hours of contractor work.

  • NDA

    Non-disclosure agreement before portal access.

Core P2P flow

Four scenarios from request to payment — HR single source, framework call-off, contractor and AV sourcing to catalog.

Single supplier (single source) — recruitment services

7 steps

Workflow · 7 tiles in a row

Framework call-off

9 steps

Workflow · 9 tiles in a row

Contractor order and timesheets

7 steps

Workflow · 7 tiles in a row

From request to catalog (RFI → RFP → auction)

6 steps

Workflow · 6 tiles in a row