> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/dashboard/billing/usage-and-spend-control.md). # Usage & Spend Control The **Billing & Usage** view is accessible by navigating to the organization management menu and clicking on your **Organization Name > Billing & Usage** on the **left-hand menu.** Within the Billing & Usage view, you can explore the organization's usage and plan limits, and manage the subscription and billing email recipients.

Billing & Usage - Organization Menu

### Billing Emails You can add recipients for billing-related notifications: * notification about successful payments * alerts about non-successful payments * invoices and receipts Please note, that billing notifications are different from operational notifications (by default operations notifications are being sent to all the members with Admin rol) In order to add additional recipients, navigate to **Organization > Billing & Usage.** Then add a new email in the **Billing Emails** section:

Adding additional recipients for Billing Emails

### Usage Information The Billing & Usage view displays the Usage section with a daily/monthly breakdown of the recorded tests. The usage includes a [**Failed**](/dashboard/tests/test-status.md) or [**Passed** ](/dashboard/tests/test-status.md)test recorded to Currents Dashboard. Retries of the same test are considered a single test result, therefore, a [**Flaky Test**](/dashboard/tests/test-status.md) counts as one record, regardless of the number of attempts. {% hint style="info" %} Skipped tests `it.skip` do **not** count towards usage for billing purposes {% endhint %} **How to estimate your test usage** To estimate your test volume, count all your `it` statements and multiply by your provider's average number of CI runs. The usage is aggregated **hourly** to allow precise reporting and calculation of recorded tests. #### Usage Information filters You can filter usage by period and view all past billing cycles. Moreover, you can filter by **tests** or **runs**. Most customer contracts are metered by **runs**.

Example - Usage history chart and filters

#### Usage details If you click **Show Usage Details**, you can see a breakdown of all recorded tests and runs per project created within your organization account.

Usage Details

#### Usage cycle types * **Scale /** **Business Plans:** The usage cycle follows the billing cycle chosen. Monthly plans will have monthly usage cycle, while annual plans (discounted at 20%) will have annual usage cycles. * **Enterprise Plans:** An **annual usage cycle** is available, with monthly cycle is also supported.\ The annual cycle is recommended for teams with **seasonal usage patterns** or **peaks in usage** during certain times of the year. More details on [Plans & Pricing](/dashboard/billing/plans-and-pricing.md) ### Extra Usage Plans If you are still determining how many tests you need per month or if your usage is seasonal, Currents offers extra usage plans in addition to your test package. These extra usage plans offer customers more flexibility to run tests when needed. When you reach the test limits, Currents will send you an email notification informing you of the activation of the extra usage plan. You also can see the extra recordings progress on the **Usage Information**:

Example - Extra usage activated

At the end of the monthly cycle, the billing will include the additional usage recorded. In the case of annual plans, Currents will send a separate bill with the extra tests. The cost for extra recordings ranges and depends on your plan. For detailed pricing information, please check our [**pricing page**](https://currents.dev/#pricing). If you have any questions or concerns, please don't hesitate to contact us via ** or our in-app support chat. To limit how much extra usage can accrue, see [Usage Alerts and Spend Control](#usage-alerts-and-spend-control) below. ### Usage Alerts and Spend Control The **Usage Alerts** section of **Billing & Usage** lets organization admins configure usage notifications and cap extra usage spend: * **Usage Alert Threshold %** — Currents sends an email to organization admins when usage exceeds this percentage of the plan limit. The default threshold is 90%. * **Limit extra usage** — stops recording new results when extra usage beyond the plan limit reaches a cap. The cap is set as **Extra usage cap %** — a percentage of the plan limit. For example, with a plan limit of 10,000 tests and a cap of 50%, recording stops after 15,000 tests. Setting the cap to 0% stops recording as soon as the plan limit is reached. See [Capping Extra Usage](/dashboard/billing/plans-and-pricing.md#capping-extra-usage) for details. When the cap is reached, Currents emails organization admins and pauses recording. CI pipelines and test runners keep running — Currents resumes recording when the usage cycle resets, the cap is increased or removed, or the plan is upgraded. ### Legacy Plans Our legacy plans (created before April 2023) do not have extra usage enabled. When legacy plan subscribers reach the usage limits, our system automatically increases the quota by **10%** to safeguard your usage. Then, you will get emails from our automated system with warnings, asking you to upgrade your subscription or activate an extra usage plan. You can activate an extra-usage or upgrade the plan in **Billing & Usage** section:

Enabling Extra Usage for Legacy Plans

If upgrading is not an option, you can contact us via ** or our in-app support chat to activate an extra usage plan to accommodate your increased usage needs. Please remember that if you surpass your usage limits, Currents will cease recording tests on your organization dashboard. To avoid service interruption, don't hesitate to contact us to activate an extra usage plan or explore subscription upgrades. We're always here to help! --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.currents.dev/dashboard/billing/usage-and-spend-control.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.