> ## Documentation Index > Fetch the complete documentation index at: https://docs.kordless.ai/llms.txt > Use this file to discover all available pages before exploring further. # Billing responsibility > Who pays for what when an Account is connected. Every connected Account has one explicit billing responsibility: either your workspace pays for the connected Account's active Book use, or the connected Account pays for its own. Billing responsibility is set when the connection is created and is separate from access level. ## Exact definitions | Billing responsibility | What it means | | ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- | | **This workspace pays** | Your workspace is billed for the connected Account's active Books. The connected Account's Live Book usage is attributed to your workspace's billing. | | **The connected Account pays** | The connected Account is billed for its own active Book use. Your workspace gains access but does not receive the bill. | ## How billing works Kordless uses one natural billing unit: the active Book. An active Book is a verified Live Book used to quote an identified customer during the billing month. Reads, simulations, quotes, Test mode, and non-ready outcomes are not metered. Usage is attributed once to the Account whose Live environment performed the work, then charged to its effective billing Account. Connections never duplicate usage. ```text theme={null} Connected Account's Live Book performs work → usage attributed to that Account → charged to the effective billing Account → either your workspace or the connected Account itself ``` ## What billing responsibility is not Billing responsibility is never inferred from access. A workspace with Full access is not necessarily the billing Account. A workspace that pays is not necessarily the owner. * **Billing is not access.** A workspace can have Full access while the connected Account pays its own bill. Or a workspace can have View only access and still be the billing Account. * **Billing is not ownership.** The connected Account owns its Book, environments, and history regardless of who pays. * **Billing is not permanent.** Billing responsibility is set per connection and can be reviewed. Revoking a connection removes billing responsibility for future use. ## Rules and boundaries * Billing responsibility is explicit and chosen at connection creation — never assumed from access level or ownership. * Usage is attributed exactly once. No duplicate charges across the controller and connected Account. * An independently operated connected Account that pays for its own use is billed through its own subscription. * Test mode activity is never metered, regardless of billing responsibility. * Revoking a connection stops future billing responsibility. Existing usage that was already attributed remains on the effective billing Account's record. ## Where to see billing responsibility Open a connected Account's drill-down page to see its billing responsibility in the Account context section: * If your workspace pays, it reads: *"\[Your workspace] pays for active Book use."* * If the connected Account pays, it reads: *"This Account pays for its own active Book use."* See [Usage and billing](/product/workspace/usage-and-billing) for consolidated billing across connected Accounts. ## Related tasks What view, integration, and full access mean for a connected Account. Create a new third-party Account and choose billing responsibility. Connect an existing Account and choose billing responsibility. Workspace-level usage and plan management.