Skip to content
ContractSpec
Start here

Area guide · 10 packages · Inspect quote-to-cash state

Billing, finance and economic evidence

Model commercial lifecycles, exact money and reviewable financial handoffs with provider and country boundaries kept explicit.

What are you trying to do?

  • Where do country-neutral billing contracts stop?
  • How do billing facts become a FinanceOS handoff?
  • Which operations require a concrete adapter and approval?

Why start with these packages

Suggested entry point

@lssm-tech/lib.billing-spec

Begin with country-neutral quote-to-cash contracts, lifecycle evidence and operation descriptions.

Read package manual →

Suggested entry point

@lssm-tech/lib.billing-runtime

Use deterministic lifecycle projections, supplied persistence ports and economic-truth helpers.

Read package manual →

Suggested entry point

@lssm-tech/lib.finance-os-runtime

Inspect exact-money, budget, posting and consolidation projections.

Read package manual →

Suggested entry point

@lssm-tech/lib.billing-france

Inspect the separate France-specific package when a selected composition needs that country layer.

Read package manual →

Practical steps

Step 01

Trace one commercial transition

Start with a quote or invoice reference and follow the declared operation, lifecycle projection and evidence event. Identify the exact money representation, tenant/company scope and persistence port involved.

Step 02

Inspect a correction and handoff

Follow a superseding correction into the resulting finance proposal. Check balanced units, required evidence and the Connect authorization reference before considering the handoff eligible for a host executor.

Step 03

Choose the external boundary

Locate the country and provider adapter used by the intended product. Review its credential, submission, reconciliation and failure responsibilities separately from the portable runtime; qualify that composition in its owning environment.

Choose the correct domain boundary

BillingSpec models commercial parties, catalog/pricing, quotes, orders, invoices, credit notes, payments, reconciliation and related evidence. BillingRuntime supplies deterministic projections over those contracts with an injected tax-calculation port and backend-neutral persistence interfaces. The separate country package and provider integrations handle their specific responsibilities. Start by identifying the exact lifecycle and jurisdictional composition required by the host; a country-neutral operation declaration is not proof of configured production invoicing or payment execution.

Preserve economic history

The billing truth surface normalizes facts into an append-only evidence lifecycle with revision and idempotency checks. Corrections supersede earlier facts while retaining history. FinanceOS validates exact money, entity/tenant isolation, balanced postings, segregation of duties and budget freshness. Consequential work becomes a digest-bound handoff for host approval and execution. This division makes an accounting review reproducible: the reviewer can follow the original fact, its correction lineage and the proposed posting instead of trusting a mutable total.

Respect unit and execution constraints

Finance consolidation is holding-bound and homogeneous in currency and scale. Mixed units need governed conversion evidence and are denied by default in the documented runtime. BillingRuntime defines invoice, credit-note, event-log and invoice-chain ports rather than selecting a database or payment provider. Keep a proposed handoff, an authorized action and a confirmed external effect distinct in product copy and telemetry. Adapter qualification should address replay and ambiguous provider outcomes as well as the successful path.

Follow a practical path.

Trace one commercial transition

Start with a quote or invoice reference and follow the declared operation, lifecycle projection and evidence event. Identify the exact money representation, tenant/company scope and persistence port involved.

Inspect a correction and handoff

Follow a superseding correction into the resulting finance proposal. Check balanced units, required evidence and the Connect authorization reference before considering the handoff eligible for a host executor.

Choose the external boundary

Locate the country and provider adapter used by the intended product. Review its credential, submission, reconciliation and failure responsibilities separately from the portable runtime; qualify that composition in its owning environment.

Packages in this area (10)

10 of 10 shown

  • lib.billing-franceSuggested entry pointdomainsnode

    France-specific BillingOS readiness contracts and deterministic e-invoicing/e-reporting checks.

    Inspect the separate France-specific package when a selected composition needs that country layer.

    Open manual →
  • lib.billing-runtimeSuggested entry pointdomainsnode

    Pure backend-neutral BillingOS runtime helpers for deterministic quote-to-cash lifecycle projections.

    Use deterministic lifecycle projections, supplied persistence ports and economic-truth helpers.

    Open manual →
  • lib.billing-specSuggested entry pointdomainsnode

    Country-neutral BillingOS quote-to-cash contracts, invariants, and agent action governance types.

    Begin with country-neutral quote-to-cash contracts, lifecycle evidence and operation descriptions.

    Open manual →
  • lib.cost-trackingplatformnode

    API cost tracking and budgeting

    Open manual →
  • Provider-neutral crypto wallet governance and HTTP-native agent payment protocol contracts.

    Open manual →
  • Provider-neutral internal finance operations contracts beyond BillingOS quote-to-cash.

    Open manual →
  • lib.finance-os-runtimeSuggested entry pointdomainsnode

    Deterministic provider-neutral FinanceOS planning, budget, posting, and evidence runtime.

    Inspect exact-money, budget, posting and consolidation projections.

    Open manual →
  • lib.meteringdomainsnode

    Usage metering and billing core module for ContractSpec applications

    Open manual →
  • CompanyOS composition module for governed BillingOS action plans, authority checks, autonomy classification, and operator inbox routing.

    Open manual →
  • Governed FinanceOS application services producing Connect-authorized effect handoffs.

    Open manual →