> ## Documentation Index > Fetch the complete documentation index at: /docs/llms.txt > Use this file to discover all available pages before exploring further. # Billing > How Data Labeling pipeline runs and Training Runs share your team's balance, reserve funds, charge for work, and respond to insufficient funds. Each team has one balance shared by every project in that team. Data Labeling pipeline runs and Training Runs both use it, but they estimate and settle costs differently. For the calculations behind a product's estimate, see [Pipeline pricing](/docs/data/concepts/pricing.md) or [Training cost](/docs/train/concepts/cost.md). > [!WARNING] > > Starting paid work can reserve or charge your team's balance. Review the product's estimate before you start. A pipeline's **Maximum** forecast and a Training Run's maximum charge are not the same billing rule. ## Balance and pauses The sidebar shows the selected team's balance in US dollars. All projects in that team draw from the same balance. Switching projects does not create a separate pool of funds. * A Data Labeling pipeline run can pause automatically when it cannot reserve the next node's cost. After the balance covers the remainder, resume it from the run. * A Training Run can enter a funds block before training starts when the balance cannot cover its maximum charge. Top up, then resume or cancel it. * A Training Run can also be blocked after training if the final charge cannot be collected. Its product-specific payment window and controls are documented under [Training cost](/docs/train/concepts/cost.md). [Manage your team and balance](/docs/core/teams-and-balance.md#top-up) explains how to add funds. The platform links to the Business Console for payments; it does not contain a payment form. ## Pipeline runs A Data Labeling pipeline shows a **Cost breakdown (forecast)** before deployment. Its **Expected** total is the likely cost and its **Maximum** total is the forecast ceiling if every item triggers every billable event. Pipeline billing is pay-as-you-go for work actually processed. A pipeline can deploy with a balance of at least `$0.01`; covering its entire **Maximum** is advice rather than a deployment requirement. When the balance is below the maximum, the deploy window can show **Min**, **Expected**, and **Max** funding levels. Deploying freezes the pipeline run's per-item prices in its contract. The run then reserves and settles funds as items move through billable nodes. If an item cannot reserve its next node's cost while deployment is still creating items, the run records the funding pause; the top-up banner and run controls remain hidden during deployment or if deployment fails. After a successful deployment finishes, top up and use **Resume** when the run says the balance covers the remainder. Canceling a pipeline run still charges for work performed before each item ends on its node. The unused reserved amount returns to your balance. If an item fails on a node, its reserved amount returns in full, but recorded Human QA and one-time per-expert charges still apply. See [What a canceled or failed item costs](/docs/data/concepts/pricing.md#what-a-canceled-or-failed-item-costs) for the rules by cost line. See [Pipeline pricing](/docs/data/concepts/pricing.md) for every cost line, the Expected and Maximum calculations, and the contract freeze. See [Resume or cancel a pipeline run](/docs/data/guides/pause-resume-cancel.md#when-a-run-pauses-itself-for-funds) for the run controls. ## Training Runs A Training cost estimate reports one maximum charge. Starting the Training Run places a hold for that amount on the team balance. The maximum charge is based on the estimate's maximum GPU seconds, is rounded up to the cent, and has a minimum of \$1 per GPU. The ready estimate shows the authoritative amount. A completed Training Run, or one canceled after training starts, is charged for GPU seconds used, subject to the \$1-per-GPU minimum for a nonzero charge and the approved maximum. The unused part of the hold returns to the team balance. No charge applies when training never starts or when a platform failure prevents a successful output; the product page lists the complete no-charge cases. See [Training cost](/docs/train/concepts/cost.md) for the inputs to the maximum charge, cancellation behavior, payment blocks, and no-charge cases. ## Top up and billing history Open **Balance** in the sidebar: * **Top up** opens the Business Console billing page in a new tab. * **Billing history** opens the same external billing area and remains available to read-only team members. * **Apply promocode** adds credit to the selected team's balance when the code is valid. The platform reads the resulting balance. Payments, invoices, payment methods, and billing history remain in the Business Console. See [Teams, access, and balance](/docs/core/teams-and-balance.md) for the exact controls and team-access rules. ## Related * [Pipeline pricing](/docs/data/concepts/pricing.md) — forecast and contract mechanics for Data Labeling * [Training cost](/docs/train/concepts/cost.md) — estimates, holds, and settlement for Training * [Teams, access, and balance](/docs/core/teams-and-balance.md) — switch teams, add credit, and open billing history This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.