> For the complete documentation index, see [llms.txt](https://docs.valohai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.valohai.com/user-and-organization-management/getting-started/billing.md).

# Billing & Payment

Organization administrators manage billing addresses and payment methods in the organization settings. Keep your billing information current to ensure uninterrupted service.

## Update Billing Information

1. Click **Hi, \<username>** in the top-right corner
2. Select **Manage \<organization>**
3. Open the **Billing** tab
4. Click **Billing details**
5. Update your billing address or payment method
6. Click **Save**

## Payment Methods

Valohai accepts major credit cards for payment. Update your card information anytime without service interruption.

When changing payment methods:

* New card is validated immediately
* Old card remains active until validation succeeds
* Failed validations preserve your current payment method

## Billing Cycles

Billing occurs monthly based on your usage:

* **Compute costs:** Machine hours across all environments (cloud instances, on-premises allocations)
* **Storage costs:** Data stored in Valohai-managed stores
* **Platform fees:** Base subscription costs (if applicable)

Invoices are available in the **Billing** tab after each billing period.

## View Usage and Costs

Track spending in the **Billing** tab:

* **Current month:** Running total of costs before the billing cycle closes
* **Past invoices:** Historical bills with detailed breakdowns
* **Usage by project:** See which projects consume the most resources

Use [Productivity Dashboard](/observability/productivity-dashboard.md) to analyze resource usage patterns and identify optimization opportunities.

## Billing Contacts

Add multiple email addresses to receive invoices:

1. Go to **Billing** tab
2. Click **Billing contacts**
3. Add email addresses for accounting or finance teams
4. Save changes

All listed contacts receive invoice emails automatically.

## Billing Address Requirements

Provide accurate billing information for tax and accounting purposes:

* Company name
* Street address
* City, state/province, postal code
* Country
* Tax ID (if applicable in your jurisdiction)

## Related Topics

* [Productivity Dashboard](/observability/productivity-dashboard.md) — Analyze resource usage and costs
* [Team Quotas](/user-and-organization-management/environments-and-access-control/team-quotas.md) — Control spending by limiting resource usage
* [Track Underutilization](/observability/resource-monitoring/track-underutilization.md) — Identify wasted compute resources


---

# 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://docs.valohai.com/user-and-organization-management/getting-started/billing.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.