> For the complete documentation index, see [llms.txt](https://help.pump.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pump.co/pump-view/budget-alerts.md).

# Budget Alerts

Learn how to set budgets and get alerted when spend nears or exceeds them.

Budgets let you set a monthly spend cap for specific accounts or services and get notified when spend approaches or exceeds that cap.

{% embed url="<https://youtu.be/7USH4Kx0igA>" %}

## Creating a budget

Navigate to [**View**](https://app.pump.co/view) **>** [**Budgets**](https://app.pump.co/view/budgets) in the left sidebar, then click **New budget**.

| Field               | Description                                                                                                                                                                                                   |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Name                | A label for this budget (e.g., "Data platform monthly budget"). Optional. Defaults to the scope if left blank.                                                                                                |
| Scope               | Which accounts and services this budget watches. Use the Account and Service dropdowns to narrow the scope, or leave both set to "All" for a company-wide budget.                                             |
| Budget              | The monthly dollar amount this budget tracks against. The dialog shows last month's spend for the selected scope as a reference point. Click "Set as budget" to use last month's spend as the starting value. |
| Thresholds & alerts | One or more percentage thresholds that trigger notifications. Each threshold has its own recipient list.                                                                                                      |
| Approval policy     | Optional. Require sign-off before changes or breach-driven raises take effect.                                                                                                                                |

## How thresholds work

Each budget supports multiple thresholds. A common setup:

| Threshold | Purpose                                                                                                     |
| --------- | ----------------------------------------------------------------------------------------------------------- |
| 75%       | Early warning. Notify the engineering lead so the team can investigate before the budget is fully consumed. |
| 100%      | Budget reached. Notify finance and leadership.                                                              |

Each threshold tier alerts only its own tagged recipients. If no recipients are tagged for a threshold, the alert goes to everyone in your company.

## Alert channels

Budget alerts can be delivered via email and Slack. Recipients must have an active Pump account.

To compare budget alerts with anomaly alerts, see [Budget Alerts vs. Anomaly Alerts](https://help.pump.co/pump-view/anomalies-and-budget-alerts.md) on the Anomalies page.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.pump.co/pump-view/budget-alerts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
