# General Translation Platform: Managing billing URL: https://generaltranslation.com/en-GB/docs/platform/dashboard/guides/managing-billing.mdx --- title: Managing billing description: How to manage plans, usage-based pricing, prepaid credits, and auto-reload. related: links: - /docs/platform/dashboard/guides/reviewing-translations - /docs/platform/dashboard/guides/defining-context-for-translations - /docs/platform/dashboard/guides/adding-annotations - /docs/platform/dashboard/guides/using-ask-ai --- Usage records and spend estimates are available in **Organisation > Usage**. Compare plans under **Organisation > Settings > Plans**. Credit balances, reload settings, and invoices are available in **Organisation > Settings > Billing**. ## Plans [#plans] Start for free. Add a payment method to enable usage-based billing: * **Starter — $0/month.** For individuals and small teams. There is no monthly fee; you pay only for what you use. Includes unlimited users, projects, and languages, plus the [Translation Editor](/docs/platform/dashboard/guides/reviewing-translations), GitHub integration, and the [Locadex](/docs/platform/locadex/quickstart) AI agent. * **Enterprise — custom.** For larger teams with complex localisation needs. Everything in Starter, plus forward-deployed localisation engineers, custom workflows for any file format or framework, shared context across every Project, and enterprise-grade security, SLAs, and support. Each free Organisation gets 5M platform credits over a rolling 30-day window. You will be rate-limited until you add a payment method. When an eligible Organisation adds its first payment method, it receives a one-off sign-up credit grant. **Y Combinator founders:** Verify eligibility and request startup credits through the [YC credits offer](https://generaltranslation.com/enterprise/contact/yc). ## Usage-based billing [#usage] You pay per workflow: cost is based on the number of input tokens, workflow type (build time, runtime, or development), file format, and any context you provide. Google Slides also has a separate **Layout Processing** charge for each completed slide. Review consumption under **Organisation > Usage**. Switch between **Tokens** and **Agent**. If your role can view billing, **Cost** is also available. The page opens to the current billing period when one is available, or the last 30 days otherwise. You can also select the last 7 days or a custom date range of up to 100 days. * **Tokens** shows total and daily input tokens with breakdowns by target locale and service type. * **Agent** shows total and daily Organisation-wide LCU usage. * **Cost** shows Organisation-wide spend after contract pricing, custom discounts, and applied credits. Amounts can change until the billing period is invoiced. The page also lists recent translation records with input and output token counts and recent Agent workflow records with trace IDs. When the Organisation has multiple Projects, the Project selector filters token metrics and translation records; Agent and Cost totals remain Organisation-wide. ### How usage is metered [#usage-metering] * **Translation workflows** are metered by input tokens, workflow type, and file format. * **Ask AI** is measured at the model provider's list-price token cost and converted to **Locadex Compute Units (LCUs)** when an Organisation has a billing account. A free Organisation without a billing account draws from the same rolling allowance as free translations. * **Google Slides** adds a per-slide **Layout Processing** charge to its translation workflow. This charge has no context surcharge. * **Platform Context** adds a surcharge based on input tokens and the amount of context provided. * **Locadex** agent runs are metered in **Locadex Compute Units (LCUs)**. An LCU measures the resources an agent uses to run end to end. See the [usage rates](https://generaltranslation.com/pricing/usage) page for current rates and calculation examples. ## Invoice history [#invoices] When available, invoices are listed in **Organization > Settings > Billing** with their date, description, status and amount. Select **Breakdown** to review line items and quantities, or **View** to open the hosted invoice. **Enterprise-managed Organisations:** Cost and invoice data are managed at Enterprise scope. Open **Enterprise > Billing** to review them. ## How the credit balance works [#credits] Your **credit balance** is a prepaid wallet for platform usage, shown on **Organisation > Settings > Billing** and denominated in dollars ($1 = 1M credits). The balance is split into buckets: * **Purchased** — credits you purchased. * **Granted** — any one-off sign-up credit. * **Included** — any credits included with your plan. Before a billable workflow starts, the platform checks that enough credits are available. It then charges for the metered usage; some workflows reserve an estimate and reconcile it after completion. Purchased credits are non-refundable and expire one year from the purchase date. ### Buying credits [#buying-credits] Choose **Buy Credits** on **Organisation > Settings > Billing** and enter an **Amount** to charge to your default payment method. The dialogue shows the allowed range for your plan (the Starter minimum is $10). ### Auto-reload [#auto-reload] Auto-reload keeps your balance topped up automatically when your balance falls below a certain threshold. It is off by default. To turn it on, choose **Auto Reload** on **Organisation > Settings > Billing**, turn on **Enable Auto Reload**, and set: * **Minimum Balance** — when your balance goes below this, a reload is triggered. * **Reload to** — the target balance to top your credits back up to. * **Usage Limit** (optional) — a hard cap on total usage spend per billing period. When usage reaches the limit you've set, billing is blocked even with auto-reload on. ### Billing alerts The billing contact receives email alerts before usage is paused: * **Auto-reload off:** a balance warning after 80% of the loaded credit balance has been used, followed by a depleted-balance alert at $0. * **Auto-reload on with a Usage Limit:** a warning at 80% of the limit, followed by a limit-reached alert at 100%. Balance alerts link to **Organization > Settings > Billing**, where you can buy credits or turn on auto-reload. Usage Limit alerts show the cap and billing-period reset date, and link to the setting so you can raise or remove it. ### When your balance runs out [#running-out] What happens at $0 depends on auto-reload: * **Auto-reload off (default):** API access is blocked until you buy more credits, and requests are rejected as soon as the estimated cost exceeds your available balance. Your card is never charged on its own. * **Auto-reload on:** your card is charged automatically to top up to your Reload to target amount. A Usage Limit, if set, still applies as a hard cap. ## Upgrading your plan [#upgrading] ### Upgrade to Starter [#to-starter] Because Starter has no monthly fee, upgrading simply means adding a payment method. On **Organisation > Settings > Billing**, choose **Manage Billing** and add a card and billing address. Upgrading removes your rate limit and also unlocks features including: Locadex, team invites, auto-reload, the Translation Editor, version branching, and unlimited Projects. ### Upgrade to Enterprise [#to-enterprise] Enterprise plans include custom pricing and terms for larger teams, including: custom integrations, a custom SLA, forward-deployed engineers, and enterprise security and support. Join teams like Ramp, Cursor, and Profound. [Contact](https://generaltranslation.com/en-US/enterprise) the General Translation team to set up an Enterprise plan. ## Next steps - /docs/platform/dashboard/guides/reviewing-translations - /docs/platform/dashboard/guides/defining-context-for-translations - /docs/platform/dashboard/guides/adding-annotations - /docs/platform/dashboard/guides/using-ask-ai