> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/developer-resources/rest-api/billing-api/journal/state-diagram.md).

# State diagram

The following diagram shows the state (or status) transition process of a billing journal. 

<figure><img src="/files/h6D1TPR50K7GmJR6xoBl" alt=""><figcaption><p>Journal state transition</p></figcaption></figure>

<table data-full-width="false"><thead><tr><th width="152">State</th><th>Definition</th></tr></thead><tbody><tr><td><strong>New</strong></td><td>This is an initial status for a journal.</td></tr><tr><td><strong>Draft</strong></td><td>The vendor has created the journal.</td></tr><tr><td><strong>Validating</strong></td><td>The vendor has submitted the journal data for processing.</td></tr><tr><td><strong>Validated</strong></td><td>The data has been validated.</td></tr><tr><td><strong>Error</strong></td><td>An error occurred due to missing records on the platform.</td></tr><tr><td><strong>Review</strong></td><td>SoftwareOne is reviewing the contents of the journal.</td></tr><tr><td><strong>Enquiring</strong></td><td>The journal has been returned to the vendor for corrections and resubmission.</td></tr><tr><td><strong>Generating</strong></td><td>The journal has been accepted and is being processed by SoftwareOne.</td></tr><tr><td><strong>Ledger</strong></td><td>The platform has created a ledger file in the scope of the given seller.</td></tr><tr><td><strong>Generated</strong></td><td>The statements have been generated.</td></tr><tr><td><strong>Accepted</strong></td><td>The journal has been accepted. </td></tr><tr><td><strong>Completed</strong></td><td>The journal is now complete. This occurs when all ledgers have been marked as completed.</td></tr></tbody></table>


---

# 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://docs.platform.softwareone.com/developer-resources/rest-api/billing-api/journal/state-diagram.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.