> 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/review-quote-details.md).

# Review quote details and line prices

Use **Quote Details** for a document configured for quote processing. Its document type, layout, permissions and workflow determine available fields and actions. This view is separate from purchase-order matching.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-7e4a2e5aa04feb74f0ac4af8b7f02b3895224530%2Fguide-screenshots-20261027-quote-header-en.png?alt=media" alt="Header of a fictional three-page US quotation in DocBits: supplier, reference, date, currency and total. This crop shows the first six header fields."><figcaption><p>Header of a fictional three-page US quotation in DocBits: supplier, reference, date, currency and total. This crop shows the first six header fields.</p></figcaption></figure>

Download the fictional three-page quotation (PDF)

{% file src="/files/T89Mk8tVYnCwokwGekcr" %}

## Review and correct lines

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-c98f1e927a120b9ccdf4838f0fad09de6628db96%2Fguide-screenshots-20261027-quote-line-editor-en.png?alt=media" alt="Description and unit price of the selected first line. No values have been changed or saved."><figcaption><p>Description and unit price of the selected first line. No values have been changed or saved.</p></figcaption></figure>

1. Open the intended quote. Compare supplier, reference, date and currency with the original.
2. Compare line-item numbers, descriptions, quantities, units, prices and amounts with the original. An item-number match does not establish a price or unit match.
3. Select a line to display its details below the table.
4. Use the configured master-data lookup where available. Check the selected item and any populated values; investigate lookup warnings.
5. Correct the line and choose **Save**, or **Save & Next** to continue. **Cancel** leaves the line editor without submitting that line's changes.
6. Use **Save & Next — Copy Defaults** only when the defaults fit the next line. Review copied values.
7. Reopen the document and line to verify stored values. For a rejected line, inspect its note where available and resolve the business reason.

## Special cases

**Add line row** creates a manually entered position when editing is allowed. Compare it with the original and complete required fields. Removing a manually created row is a separate action; do not remove a real position to make totals agree.

For read-only documents, check permissions, lock and processing stage. For missing line items, inspect the source, extraction and layout.

Automatic managed/last/contracted-price checks use [Quote comparison cards](https://docs.docbits.com/administration-and-setup/workflow/cards-overview/quote-comparison-guide.md). Saving a line does not establish that these checks ran, approval was granted or ERP export completed.


---

# 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/review-quote-details.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.
