> 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/administration-and-setup/settings/document-processing/module/barcode-assignment.md). # Barcode Assignment ### Overview The **Barcode Assignment** setting adds a barcode tool to the **document validation screen**. It reads the barcodes and QR codes DocBits found in a document and lets you **assign their values to the document’s fields** — for example, filling a purchase-order, reference or delivery-note number from a barcode instead of typing it. This setting is **disabled by default**. ### What You Get When You Enable It Once the setting is on, a new **barcode button** (a QR-code icon) appears in the toolbar on the right-hand side of the **validation screen** (`/field_validation_v1/…`). This is the entry point to the whole feature — without the setting, the icon is hidden.

The barcode (QR-code) icon in the validation toolbar — When the setting is enabled, the barcode icon appears in the validation toolbar.

Here is the icon in context on the validation screen, next to the document being reviewed:

Validation screen with the barcode icon available — The validation screen — the barcode icon (highlighted, right toolbar) is only shown when Barcode Assignment is enabled.

### How Barcodes Are Read DocBits detects the barcodes during document processing and offers their decoded values for assignment. A single document can carry several barcode types — for instance a **QR code**, a **Code 128** and an **EAN-13** — each encoding a different value such as a purchase order, an invoice number or a supplier GLN.

Demo invoice carrying several barcode types — Example DocBits demo invoice carrying three barcode types (QR code → purchase order, Code 128 → invoice number, EAN-13 → supplier GLN), each encoding a value you can map to a field.

{% hint style="info" %} Which barcode types are detected is controlled by the **Bar-Code / QR Code Extraction** setting (`Barcode Extraction Types`). If the dialog shows *“no barcodes extracted found”*, make sure barcode extraction is enabled and that the expected types (e.g. `QRCODE`, `CODE128`, `EAN13`) are selected. See [Bar-Code / QR Code Extraction](/administration-and-setup/settings/document-processing/module/bar-code-qr-code-extraction.md). {% endhint %} ### Using the Barcode Assignment Dialog 1. Open a document on the **validation screen**. 2. Click the **barcode icon** in the right-hand toolbar. 3. The **Barcode Assignment** dialog lists every barcode DocBits detected in the document, shown as `Barcode : `.

Barcode Assignment dialog listing the detected barcodes — The Barcode Assignment dialog lists each detected barcode with a dropdown to choose the target field.

4. For each barcode, open its dropdown and pick the field the value should go into.

Choosing the target field for a barcode — Each barcode can be mapped to any document field — e.g. Purchase Order, Invoice number, Supplier ID.

5. As soon as you select a field, that field is filled with the barcode’s value.

Barcode mapped to the Purchase Order field — After selecting a field (here Purchase Order), the field is populated with the barcode value.

### How to Enable 1. Go to **Settings**. 2. Select **Document Processing**. 3. Select **Module**. 4. Open the **Document Type** section. 5. Find **Barcode Assignment** and switch the toggle on.

The Barcode Assignment toggle in Settings → Document Processing → Module.

### Benefits * **Faster, error-free entry**: Take values straight from a barcode instead of reading and typing them by hand. * **Fewer typos**: A scanned value is exactly what is encoded in the barcode. * **Stays in control**: You decide which barcode goes into which field during validation. ### When to Use This Feature * **Documents with barcodes**: When your documents carry barcodes/QR codes whose values belong in specific fields (e.g. order or reference numbers). * **Manual validation workflows**: When a person reviews documents and wants to fill fields quickly from barcodes. * **Leave it off** if your documents have no usable barcodes, or if you only need automatic barcode/QR **extraction** — see [Bar-Code / QR Code Extraction](/administration-and-setup/settings/document-processing/module/bar-code-qr-code-extraction.md). {% hint style="info" %} **This feature is for reading a barcode/QR value and assigning it to a field during validation.** Automatically extracting structured data from payment codes (such as Swiss QR Bill or GiroCode) — and splitting a multi-page file at barcode separator pages — are handled by a **different** setting: [Bar-Code / QR Code Extraction](/administration-and-setup/settings/document-processing/module/bar-code-qr-code-extraction.md). {% endhint %} --- # 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.docbits.com/administration-and-setup/settings/document-processing/module/barcode-assignment.md?ask=&goal= ``` `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.