> 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/sales-data/flow/flow-for-confirming-a-day.md).
# Flow for confirming a day
You can use this flow if you need to confirm sales data on a given day using the API. You can confirm a day regardless of whether the week is approved. After a day is confirmed, week approval is updated automatically.
Procedure:
* If not, then check if the day has been confirmed.
* If not, confirm the day.
You will receive an error if:
* A mandatory field is not present on the day.
* A comment must be filled in the weekly balance cash difference. Cash difference is detected, but no comment is present.
* The day has been confirmed by an administrator in the UI.
{% hint style="warning" %}
**Notice:**
You will not be able to unconfirm the day if the date has been confirmed by an admin in the UI.\
Regular-confirmed days can be unconfirmed, but admin-confirmed days can not be unconfirmed.
{% endhint %}
---
# 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/sales-data/flow/flow-for-confirming-a-day.md?ask=&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.
