Freight Billing & Settlement Management

BC-2530 Level 1 Transportation & Logistics 1 providers 12 API surfaces 1 rated strong or better

Issuance of freight invoices, audit and payment of carrier invoices, interline and pool settlement, cargo claims, and freight revenue accounting.

Freight Billing & Settlement Management (BC-2530) is a level-1 business capability in the Transportation & Logistics model. The catalog holds 12 API surface(s) from 1 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

Freight Invoicing Management BC-2530.10

Generation and distribution of freight, accessorial, and self-billing invoices to customers.

no catalog coverage

Freight Audit and Payment Management BC-2530.20

Audit of carrier invoices and execution of carrier payments by shippers and forwarders.

1 provider, 12 API surfaces

Interline and Multi-Carrier Settlement Management BC-2530.30

Settlement of revenue and cost across interline partners, alliances, and forwarder offices.

no catalog coverage

Cargo Claims Management BC-2530.40

Intake, assessment, and settlement of cargo claims under transport liability conventions.

no catalog coverage

Freight Revenue Accounting Management BC-2530.50

Recognition, tracking, and reporting of freight revenue including unbilled and deferred positions.

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.

Strong 1 Solid coverage with minor gaps

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 Freight Billing & Settlement 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 →