> For the complete documentation index, see [llms.txt](https://docs.aquiladynamics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aquiladynamics.com/aquila-store-user-manual/system-basics/document-and-record-statuses.md).

# Document and record statuses

## Document and record statuses

Status defines what can be done with a document or record. In practice, users recognise status mainly through available operations such as save, edit, confirm, preview and print.

### Key terms

| Term               | Meaning                                                                                                                       |
| ------------------ | ----------------------------------------------------------------------------------------------------------------------------- |
| Saved record       | Data has been stored in the system. Depending on the screen, it may still be editable.                                        |
| Saved document     | A document is stored and may be available for further editing if it has not been confirmed.                                   |
| Confirmed document | A document has been finally accepted. After confirmation, it usually cannot be modified unless the process allows correction. |
| Preview            | Opens data without the ability to modify it.                                                                                  |
| Printout           | Makes a document or report available for printing or file preview.                                                            |

### How to work safely

1. If you want to return to a document later, save it if the process allows it.
2. Before confirmation, check the header, items, quantities, prices, business partner and location.
3. After confirmation, treat the document as non-editable unless the process allows correction.
4. To find a saved or confirmed document, use the document list available in the system.

### What to watch for

* Availability of statuses and buttons depends on document type.
* User permissions may limit saving, editing or confirmation.
* If a document cannot be edited, check its status and relations.

### Related pages

* [Working with tables](/aquila-store-user-manual/system-basics/working-with-tables.md)
* [Adding, editing and deleting records](/aquila-store-user-manual/system-basics/adding-editing-and-deleting-records.md)


---

# 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.aquiladynamics.com/aquila-store-user-manual/system-basics/document-and-record-statuses.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.