> 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/workflow/cards-overview/when/document-type-one-of.md).
# Document Type One of
## **Purpose:**
This DocBits card ensures the correct classification of a document by verifying if it matches any of the specified document types. This is useful for situations where a document could belong to more than one category, allowing for broader validation and automated handling.
## **Functionality:**
* **Multiple Document Type Validation:** This card allows users to check if a document matches any of a set of specified document types, ensuring flexible categorization for more complex document workflows.
* **Operator:** Users can define conditions to validate the document against multiple types. Available operators include:
* **Is:** Confirms that the document matches one of the specified document types.
* **Is Not:** Ensures that the document does not match any of the selected document types.
* **Document Types:** Users can select from multiple supported document types, including:
* **Invoice:** Financial records submitted for payment.
* **Debit Note:** Documents indicating an adjustment that increases the amount owed.
* **Credit Note:** Documents indicating a reduction in the amount owed.
* **Purchase Order:** Documents detailing a buyer’s order.
* **Order Confirmation:** Documents that confirm an order has been accepted.
* **Advance Shipment Notice:** Documents notifying of an upcoming shipment.
## **Usage:**
This card is ideal for document managers and administrators who need to ensure that documents are categorized into one of several types. It is especially useful for document workflows where a document may be classified under multiple categories, improving automation and classification accuracy.
## **Example Scenario:**
* A user uploads a document that could be either an "Invoice" or "Debit Note." Using the "Is" operator, the card confirms that the document matches one of the selected types, allowing the system to apply the appropriate rules and categorization.
By using the "Multiple Document Type Validation" card, organizations can enhance workflow flexibility, automate categorization, and ensure that documents are properly handled even when multiple types are applicable.
---
# 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/administration-and-setup/workflow/cards-overview/when/document-type-one-of.md?ask=&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.
