> 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/approve-or-reject-invoices.md).

# Approve or reject an invoice

## What follows a business approval decision

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-d7a7b86d33b967dab0ff32812159eceadfd3fe6c%2Fprocess-approval-en-20261028.png?alt=media" alt="Approve or reject invoice: Distinguish between examination, decision and subsequent handover."><figcaption><p>Distinguish between examination, decision and subsequent handover. The diagram is schematic; the active settings of your organization determine the actual behavior.</p></figcaption></figure>

Technical validation checks document data; approval records the business decision of an authorized reviewer. Even a technically valid invoice may still require one or more approvals.

1. **Check responsibility:** Open the assigned invoice and check which approval level you are allowed to decide on.
2. **Review the invoice:** Compare header values, line items and tax with the original document and your company requirements.
3. **Document decision:** Approve a correct invoice or reject it with a specific reason. Wait for the response and then check the approval history.
4. **Identify the next step:** If additional approval stages are configured, the invoice awaits their decisions. After rejection, clarification, correction and any resubmission follow your configured process. The separate export process determines whether data has reached the target system.

### Three statements that don't mean the same thing

| statement                          | What it does not automatically prove                         |
| ---------------------------------- | ------------------------------------------------------------ |
| **The data is validated.**         | That an authorized business reviewer has approved it.        |
| **A reviewer approved.**           | That all required approval stages have been completed.       |
| **Approvals have been completed.** | That the invoice has already been exported or posted in ERP. |

Use [Document tasks](https://docs.docbits.com/end-user-and-partner-section/end-user-section/tasks.md) to process assigned work and [Document status](https://docs.docbits.com/end-user-and-partner-section/end-user-section/dashboard/document-status.md) to classify current status.

Follow an ordinary reviewer checking an invoice, recording a decision and verifying the saved result.

{% embed url="<https://docbits-videos.fra1.cdn.digitaloceanspaces.com/settings-assistant/invoice-approval-customer/v1/en.mp4>" %}
Approve or reject an invoice
{% endembed %}

[Watch with subtitles](https://docbits-videos.fra1.cdn.digitaloceanspaces.com/settings-assistant/invoice-approval-customer/v1/en.html)

The recording shows the real application. Option wording may vary with the deployed version.

Use approval to record your business decision on an invoice that has already been validated. You need access to the document and permission for its current approval stage. The video uses an ordinary reviewer account.

## Review and decide

1. Open the invoice assigned to you and check the current approval stage.
2. Compare the invoice number, supplier, dates and total with the original. Review the line items and tax as well. Technical validation does not replace your business review.
3. Record a clear review note. Approve a correct invoice, or reject it with a specific reason when it needs clarification. Wait for the operation to complete.
4. Reopen the document and inspect its approval history. Check the reviewer, time, decision and full note against what you intended.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-565ee8ae570f2ac217037dfdd92ae6602a9084e3%2Fcustomer-check-en-a48081418929.png?alt=media" alt="Populated invoice values compared with the original before approval."><figcaption><p>Populated invoice values compared with the original before approval.</p></figcaption></figure>

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-920f0aae64006dfec14b9a78fe1693da55ee130b%2Fcustomer-rejected-en-a48081418929.png?alt=media" alt="Saved rejection and its recorded reason after reopening the invoice."><figcaption><p>Saved rejection and its recorded reason after reopening the invoice.</p></figcaption></figure>

### Download the original file

The uppercase **DOWNLOAD** link at the right of the document panel header saves the imported file to your computer. On small screens the link is hidden and the status bar is the way to download. In the status bar at the bottom, the download icon next to the file name does the same.

The saved file keeps the name and format it had when it arrived. An XML invoice stays an XML file, a PDF stays a PDF. Download the file when the preview is not enough, for example to read the original electronic invoice structure, raw tax lines, or a value that the preview shows differently.

A download changes neither the document nor its approval stage.

## Check the next stage

When a second approval is configured, your first approval leaves the invoice waiting for another authorized reviewer. It is not yet fully approved. A rejection needs business clarification; correction and resubmission follow your configured process.

An approval-history entry does not prove that data reached an ERP system. In this isolated example, the retrieval channel has no external ERP target. The technical status `pending_data_fetch`, when displayed, means that the document is waiting for data retrieval.

## Related pages

* [Validation screen](https://docs.docbits.com/end-user-and-partner-section/end-user-section/validation-screen.md)
* [Document tasks](https://docs.docbits.com/end-user-and-partner-section/end-user-section/tasks.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.docbits.com/end-user-and-partner-section/end-user-section/approve-or-reject-invoices.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.
