Procurement Management

BC-500 Level 1 Cross-Industry 4 providers 8 API surfaces 1 rated strong or better

Sourcing, contracting, purchasing, P2P operations.

Procurement Management (BC-500) is a level-1 business capability in the Cross-Industry model. The catalog holds 8 API surface(s) from 4 provider(s) that can perform some part of it, 1 of them rated strong or better. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.

Where this capability definition comes from. This capability is part of a published business-architecture model that API Evangelist did not author. It is redistributed here under CC-BY-4.0. Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented. Source repository · NOTICE and third-party framework attributions

Sub-capabilities

Sourcing Management BC-500.10

Strategic sourcing, RFx, supplier selection.

1 provider, 1 API surface

Procurement Contract Management BC-500.20

Procurement contracts, terms, lifecycle.

no catalog coverage

Purchase Order Management BC-500.30

PO creation, approval, execution.

3 providers, 5 API surfaces

Procure-to-Pay Operations Management BC-500.40

Day-to-day P2P operations, requisitions, receipts.

1 provider, 2 API surfaces

Procurement Category Management BC-500.50

Category strategy, spend analysis per category.

no catalog coverage

Procurement Spend Analysis Management BC-500.60

Spend visibility, reporting, savings tracking.

no catalog coverage

Providers that reach this capability

Ordered by rating band. Reach means a provider publishes an API surface that can perform some part of this capability — it is not a claim that any particular organisation has deployed it.

Exemplar 1 Complete, well-documented, and agent-ready

Lightspeed CommercePurchase Orders1 API83.7

Developing 1 Usable, with meaningful gaps to close

PartsTechcustom-cartorderspartner-orderspunchout-cart5 APIs50.9

Thin 2 Limited public surface area

Happy Cabbage AnalyticsOrders1 API36.0 NooshRfq1 API34.5

Workflows that realise this capability

Arazzo workflows whose own sourceDescriptions call APIs that carry this capability. The link is derived, not asserted: each workflow declares x-realizes-capability-ids with the spec and confidence behind it.

Business Central Create a Purchase Order for a Vendor — navision · Purchase Order Management BC-500.30
Oracle EBS EDI Outbound Purchase Order — oracle-e-business-suite · Purchase Order Management BC-500.30
Oracle EBS Procure-to-Pay — oracle-e-business-suite · Purchase Order Management BC-500.30
Oracle EBS Purchase Order Amendment — oracle-e-business-suite · Purchase Order Management BC-500.30
Oracle EBS Requisition-to-Purchase-Order — oracle-e-business-suite · Purchase Order Management BC-500.30
Workday Review Supplier Spend — workday · Purchase Order Management BC-500.30

This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.

The edge table is a Pro feature. This page shows which providers and tags reach Procurement Management. The underlying tag → capability edges — each with the quoted fragment of the provider's own OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate it passed — are available through the API, along with company-level capability maps. Only edges at confidence ≥ 0.7 with evidence found verbatim in the source contract are published at all.

See plans → · How the edges are graded →