# Document Status

The **Document Status** page (DXP eInv Document Status) shows the live processing state of every document that has been picked up by the eInvoice Sender. Each row is one queued document and reflects where that document currently stands in the sending pipeline, together with any error that occurred and where the finished e-invoice was sent.

{add screenshot of Document Status here}

## Per-entry information

- **Status** - the current processing state of the entry (see the lifecycle below).
- **Processing DateTime** - when the entry was last processed.
- **Sent To** - the recipient e-mail address the released e-invoice was transmitted to, once transmission has completed (resolved from the override e-mail, the document e-mail, or the customer/vendor card).
- **Error Message** - the last error reported for the entry. Populated when the status is Error or Failed; empty otherwise.

## Status lifecycle

An entry moves through the following states as the pipeline processes it:

- **Pending** - queued and waiting to be picked up by the Job Queue.
- **Processing** - currently being worked on by the pipeline.
- **Validated** - the source data, business and invoice-model validations have passed.
- **Generated** - the e-invoice artifact (XML/PDF) has been generated.
- **Sent** - the e-invoice has been released and transmitted to the recipient. An entry that is still Pending, Error or Failed is also set to Sent when the document is sent by email outside the queue with the standard **Email** action, so the Job Queue does not send the document a second time.
- **Error** - processing stopped on a recoverable error; the entry will be retried according to the backoff schedule.
- **Failed** - the entry has exhausted its retries (or hit a permanent/authentication error) and has been moved to the **dead-letter** state. It is not retried on the backoff schedule. An entry that was rejected for its content (by the checks before generation or by KoSIT) within the last 30 days is re-queued automatically once the corrected document produces a different e-invoice; every other Failed entry needs a manual **Re-queue**.

<p class="callout info">Validated and Generated are intermediate milestones within a single run. A healthy document typically progresses Pending → Processing → Validated → Generated → Sent.</p>

## Actions

- **Reset Status** - resets an entry that is stuck in **Processing** back to **Pending** (it can only be used from Processing). It does not clear the retry counter - use Re-queue for that.
- **Re-queue** - moves an **Error** or **Failed** entry back to **Pending**, clears the retry counter, clears the error, and shows a confirmation notification so the entry is processed again on the next Job Queue run. Use this after you have corrected the underlying data problem. The document queue page offers the same action for several selected entries at once.
- **Download Diagnostic Bundle** - collects the status, retry state, artifact metadata (hashes, not content) and recent process-log rows into a text file for troubleshooting.
- **View Process Log** - opens the process log for the entry, showing the step-by-step trace of the exchange with the Digivoice system.
- **View Validation Findings** - opens the persisted [Validation Findings](https://docs.squeeze.one/books/einvoice-sender-for-microsoft-dynamics-365-bc-en-us/page/validation-findings) from the last validation run.
- **Show KoSIT Report** / **Download KoSIT Report** - opens the official [KoSIT report](https://docs.squeeze.one/books/einvoice-sender-for-microsoft-dynamics-365-bc-en-us/page/kosit-report) in the viewer, or downloads it as a file.

<p class="callout warning">A **Failed** entry is a dead-letter. Only content rejections of the last 30 days are picked up again on their own, and only once the document produces a different e-invoice; with automatic sending switched on, such an entry is then sent to the recipient in the same Job Queue run. Every other Failed entry stays put until someone fixes the cause and uses **Re-queue**.</p>