Skip to main content
IronKernel
Products Solutions For Customers About FAQ Contact
IronKernel Platform

Tower: Earnings, Settlement, and Expense Operations

Delivers settlement, expense, and dispute state surfaces for fleet-level financial follow-up.

Problem

Delivers settlement, expense, and dispute state surfaces for fleet-level financial follow-up.

Capability

Delivers settlement, expense, and dispute state surfaces for fleet-level financial follow-up.

How it works

  1. 1 Settlement summary cards (total earned, miles, $/mile, loads).
  2. 2 Settlement list with dispute initiation modal.
  3. 3 Expense list and expense creation workflow linked to assigned loads.
  4. 4 Settlement dispute submission surface.

Operational outcomes

  • Settlement summary cards (total earned, miles, $/mile, loads).
  • Settlement list with dispute initiation modal.
  • Expense list and expense creation workflow linked to assigned loads.

Integration boundaries

  • TMS (Primary Runtime Source)
  • CMMS (Embedded Health Context)
  • YMS (Task Execution Context)

Proof model

Feature-level proof

  • Earnings, Settlement, and Expense Operations scope is defined in product module catalog.

    verified

    docs/products/tower/product.md · Module Catalog > Earnings, Settlement, and Expense Operations

  • Tower driver oversight and cockpit workflows are implemented in dedicated portal pages and hooks.

    verified

    docs/products/tower/product.md · Module Catalog > Driver Cockpit Dashboard

    Code: frontend/apps/portal/src/products/tower/pages

    Contract: proto/tms/loads/v1

  • Tower oversight surfaces are implemented in portal product modules.

    verified

    docs/products/tower/product.md · Module Catalog > Load and Stop Oversight

    Code: frontend/apps/portal/src/products/tower

    Contract: proto/tms/loads/v1

Solution routes that reuse this feature

Open these solution and feature-map routes to test this behavior in end-to-end buyer workflows (0).

This feature is currently not linked to a named solution route. Review this behavior directly, then validate continuity through adjacent solution and feature-map routes.

Continuity routes for this capability

Route-level continuity checks where this feature appears in product-pair workflows.

This capability is currently mapped in adjacent solution and continuity routes. Browse linked solution routes first, then return here when cross-route continuity is expanded.