> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/end-user-and-partner-section/end-user-section/dashboard/document-status.md).

# Document Status

Processing statuses show steps such as OCR, classification or export. **Ready for validation** means the document is ready for review; approval statuses indicate that an approval step is pending. **Exported** means the document’s export has completed. For **Error**, click the error status to inspect the available error details.

If processing times are available, hover over a status to see the phases and their durations. A duplicate icon appears for documents with possible duplicates; open it to compare the related documents.

Open a document row to work in the validation screen. Use the row's **Actions** menu for the operations allowed for that document, such as assignment, download, history or restarting processing. Available download variants depend on the document and can include annotations or electronic invoice formats.

Select the checkboxes for several documents and open the menu in the table header for permitted bulk actions, such as assignment, merging, restart, restart export or deletion. Check the selection and confirmation carefully. These actions can change documents; saving a view only changes how the worklist is displayed.

For searching, document actions and saved views, return to the [dashboard guide](/end-user-and-partner-section/end-user-section/dashboard.md).

## Video tutorial: Resolve blocked invoices

The presenter and voice are synthetic. The recording shows the actual DocBits test interface with synthetic training invoices.

{% embed url="<https://docbits-videos.fra1.cdn.digitaloceanspaces.com/settings-assistant/blocked-invoices-customer/v1/en.mp4>" %}
Resolve blocked invoices
{% endembed %}

[Watch with subtitles and chapter navigation](https://docbits-videos.fra1.cdn.digitaloceanspaces.com/settings-assistant/blocked-invoices-customer/v1/en.html)

Some native product labels may remain in another language. Technical field IDs are preserved.

I open the invoice in the field validation. In this example, the invoice number is missing. The other values are already filled out. I compare them with the original before I change anything.

Now I enter the invoice number and leave the field. After that, I save the invoice. I wait for the feedback and reload the document. This way I can see if the correction really persists.

The number is still there after opening it again. The required field error is resolved. However, saving does not mean that the invoice has been approved or exported to the ERP.

For a second invoice, the list shows an export error. I open the status and read the details. The test receiver rejected the submitted data with error code 422. The technical mapping needs to be checked here. I do not just restart the export multiple times.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-bd479c2959a25212a0003ab7c3dd17658759c621%2Fcustomer-error-en-recovery-export-v1.png?alt=media" alt="Export error and the receiver’s response"><figcaption><p>Export error and the receiver’s response</p></figcaption></figure>

In the document tasks, I create a clear handoff task for our test administrator. I include the error code and ask them to check the invoice number in the mapping. For this training, I switch email off.

After reloading, I verify that the task is saved and assigned to the right person. The task remains open until the cause is clarified. Creating a task is not yet a successful export.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-f28853e7009967f9d4839c4e0fc3736ba7923809%2Fcustomer-verify-en-recovery-export-v1.png?alt=media" alt="Saved handoff assigned to the administrator"><figcaption><p>Saved handoff assigned to the administrator</p></figcaption></figure>


---

# 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.docbits.com/end-user-and-partner-section/end-user-section/dashboard/document-status.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.