> 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/global-settings/document-types/script/scripting-in-docbits/sample-scripts/compliance-text-search.md).

# Compliance Text Search

{% hint style="info" %}
**Available from version 11.48.0** — Requires `OPENSEARCH_ENABLED` license.
{% endhint %}

## What does this script do?

Searches for compliance-relevant text like "REVERSE CHARGE" in the document archive. If matching documents exist, the tax code is automatically set. Supports both exact phrase matching and fuzzy search (typo-tolerant for OCR errors).

## Trigger

`AFTER_FORMATTING` on document type **INVOICE**

## Full Script

```python
# Search for "REVERSE CHARGE" in the organization's document archive
rc_docs = fulltext_search(
    "REVERSE CHARGE",
    search_type="match_phrase",
    doc_type="INVOICE",
    size=5
)

if rc_docs:
    set_field_value(document_data, "tax_code", "RC")
```

## Variant: Fuzzy Search (OCR Error Tolerant)

```python
# Fuzzy search tolerates OCR errors like "REVERS CHARG" or "REVERSE GHARGE"
rc_fuzzy = fulltext_search(
    "REVERSE CHARGE",
    search_type="fuzzy",
    vendor_name="ACME Corp"
)

if rc_fuzzy:
    set_field_value(document_data, "tax_code", "RC")
```

## Step-by-Step Explanation

1. **Search the archive** for the exact phrase "REVERSE CHARGE" using `fulltext_search()`
2. **Filter by document type** to only search invoices
3. **If found**: Automatically set the tax code field to "RC"
4. **Fuzzy variant**: Use `search_type="fuzzy"` to catch OCR misreads (up to 2 character differences)

## Functions Used

* [fulltext\_search()](/administration-and-setup/settings/global-settings/document-types/script/scripting-in-docbits/fulltext-search-functions.md#fulltext_search) — Search OCR text across all documents
* [set\_field\_value()](/administration-and-setup/settings/global-settings/document-types/script/scripting-in-docbits/field-functions.md#set_field_value) — Write field value


---

# 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/global-settings/document-types/script/scripting-in-docbits/sample-scripts/compliance-text-search.md?ask=<question>&goal=<endgoal>
```

`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.