> 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/getting-started/billing-and-payments/billing-process.md).

# Billing Process

## **How Billing Works** <a href="#undefined" id="undefined"></a>

Pump acts as a licensed solutions provider for AWS, GCP, and Azure. Instead of paying your cloud provider directly, you pay Pump. Your cloud usage, credits, and commitments all flow through a single billing relationship per provider.

### **The solutions provider model**&#x20;

When you connect a cloud account to Pump, your account moves under Pump's solutions provider umbrella:

| Provider | How billing works                                                                                                                 |
| -------- | --------------------------------------------------------------------------------------------------------------------------------- |
| AWS      | Your account joins a Pump-managed AWS Organization. Pump becomes the payer account.                                               |
| GCP      | Your billing account becomes a sub-account under Pump's solutions provider billing.                                               |
| Azure    | Pump operates through Ingram Micro as a Microsoft CSP indirect solutions provider. Your subscription billing routes through Pump. |

You receive a separate invoice for each cloud provider. If you use AWS and GCP through Pump, you will receive two invoices.

### Invoice timing

Invoices are published on the 5th **of each month** for the prior month's usage. Two days later, if you are on autopay, Pump charges your preferred payment method. Payment terms are **net 7**.

### What your invoice includes

Each invoice shows your cloud usage for the billing period, including any savings Pump generated on your behalf. The invoice reflects your actual cloud costs after Pump-attributed savings (commitment management, optimized rates) have been applied.

### Viewing invoices

Navigate to **Settings > Billing** or go directly to [app.pump.co/invoices](https://app.pump.co/invoices). Select any invoice and click **View PDF** to download it.

### Cloud credits

If you have existing AWS, GCP, or Azure credits, Pump can typically work with you to ensure those credits are honored. Pump generally onboards customers whose credits are near exhaustion or already used. If you have a significant credit balance remaining, reach out to the Pump team to discuss timing before connecting your account.

***

## &#x20;<a href="#undefined" id="undefined"></a>


---

# 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://help.pump.co/getting-started/billing-and-payments/billing-process.md?ask=<question>&goal=<endgoal>
```

`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.