> ## Documentation Index > Fetch the complete documentation index at: https://aidocs.ethanbragdon.icu/llms.txt > Use this file to discover all available pages before exploring further. # Billing Administration > Operate Starfire AI customers, subscriptions, plans, credits, usage, invoices, failed payments, costs, and reconciliation from Control Center. # Billing administration Control Center Billing is the platform-operator view of Starfire's Billing 4.0 system. It connects Starfire billing accounts and entitlements with Stripe customer/subscription state and usage metering. ## Billing domains The administration model can span: * billing accounts * customers * subscriptions * plans and price mappings * seats * credits * usage * overage policy where supported * invoices * failed payments * provider cost * revenue/margin reporting * reconciliation Not every operator should receive access to every billing function. ## Diagnose from the chain When access does not match payment state, investigate the full chain: ```text theme={null} User / Organization ↓ BillingAccount ↓ Stripe Customer ↓ Subscription + Price ↓ Starfire Plan ↓ Entitlements + Credits ``` A mismatch at any layer can produce symptoms that look like a simple “plan not attached” problem. ## Reconciliation Use reconciliation state to compare Starfire records with Stripe before manually changing entitlements. Manual access grants can make a billing incident harder to fix if they create a second source of truth. ## Plans Control Center's plan architecture is intended to make product limits configurable rather than hardcoded. Plan configuration can include concepts such as: * display price * monthly credits * storage * upload limits * FORGE access and build limits * research access/source limits * artifact retention * model availability * business seat rules * associated Stripe price identifiers Production values should be changed carefully because they affect both product economics and user expectations. ## Credit adjustments Authorized operators can inspect usage and, where permitted, apply credit adjustments. Every sensitive adjustment should be attributable and should not be used to conceal a broken metering or subscription path. ## Failed payments and billing holds A billing problem can affect account or organization state according to configured policy. Use billing-specific status and reason information rather than converting every payment problem into an unrelated suspension. ## Provider cost Provider cost reporting helps operators understand the economics behind models and workloads. It belongs in privileged administration and can inform routing, plan design, or feature limits. Review the user-facing Billing 4.0 model. Follow the support checklist for mismatched plan or subscription state.