> For the complete documentation index, see [llms.txt](https://docs.samesystem.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samesystem.dev/business-guides/sales-and-budget-data/budget-data/send-budget-data.md).

# Send budget data

You can use our API to send both sales budgets or salary budgets.

### Sales budgets

You can send the daily sales budget (turnover numbers) for a given year and month or you can send data for a whole month in one request.

[Send daily sales budget](/api-v1-reference/sales-budgets/send-daily-sales-budgets.md)

[Send monthly sales budget](/api-v1-reference/sales-budgets/get-monthly-sales-budgets.md)

There will be one object per month for the whole year, but you do not have to send a whole year in one call. If you include a month that has been transferred before, it will overwrite existing data.

### Salary budgets

You can send the monthly salary budget a given year. You can send data for a whole year in one request.

[Send monthly salary budget](/api-v1-reference/sales-budgets/send-daily-sales-budgets.md)

There will be one object per month for the whole year, but you do not have to send a whole year in one call. If you include a month that has been transferred before, it will overwrite existing data.


---

# 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.samesystem.dev/business-guides/sales-and-budget-data/budget-data/send-budget-data.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.