Financial Management

BC-200 Level 1 Cross-Industry 6 providers 16 API surfaces 4 rated strong or better

Accounting, controlling, statutory and management reporting, budgeting.

Financial Management (BC-200) is a level-1 business capability in the Cross-Industry model. The catalog holds 16 API surface(s) from 6 provider(s) that can perform some part of it, 4 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

General Ledger Management BC-200.10

Chart of accounts, journals, period close.

2 providers, 3 API surfaces

Accounts Payable Management BC-200.20

Invoice processing, payments, vendor accounting.

1 provider, 1 API surface

Accounts Receivable Management BC-200.30

Customer invoicing, collections, cash application.

3 providers, 10 API surfaces

Fixed Asset Accounting BC-200.40

Asset registers, depreciation, impairment.

no catalog coverage

Cost Accounting Management BC-200.50

Cost objects, cost allocations, standard costing.

no catalog coverage

Financial Reporting Management BC-200.60

Internal financial reporting and consolidation.

no catalog coverage

Statutory & Regulatory Reporting BC-200.70

Statutory accounts, regulatory financial submissions.

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
Strong 3 Solid coverage with minor gaps
Developing 1 Usable, with meaningful gaps to close
Emerging 1 Early or largely undocumented

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.

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 Financial 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 →