> 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/overview-and-basics/architecture.md).

# Architecture

## The architecture as three separate data paths

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-5ccf07340ad4cf38466b1f00ce3c18300063b804%2Fprocess-architecture-en-20261028.png?alt=media" alt="Three data paths between DocBits and Infor: Read document receipt, master data supply and export separately."><figcaption><p>Read document receipt, master data supply and export separately. The diagram is schematic; the active settings of your organization determine the actual behavior.</p></figcaption></figure>

The architecture contains several data flows with different purposes. Documents are imported for processing; master data comes from the ERP integration; recognized and reviewed results are returned through the configured export path. These paths are separate connections and should be traced separately during diagnosis.

| Data path              | Direction and purpose                                                                                                       | Checkpoint                                                                |
| ---------------------- | --------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
| **Document receipt**   | Email, upload or interface → DocBits. Documents are sent to the intended processing process.                                | Did the right document reach the right organization?                      |
| **Master data supply** | LN/M3 → BODs and ION data flow → DocBits. Suppliers and orders are made available for identification and reconciliation.    | Has the required data set been transferred and accepted by DocBits?       |
| **Result export**      | DocBits → configured Infor connection → IDM or ION and ERP. Document and business data can take different downstream paths. | Are the transfer and the respective processing in the destination proven? |

In the Infor export described here, the PDF and its attributes are sent to IDM, and `Sync.CaptureDocument` is sent to ION Desk. ION transforms it into the required target BODs according to the document type. Acceptance by LN or M3 must be verified in the respective target system; a DocBits step alone does not prove every downstream processing step.

**Use the overview to investigate errors:** If a document is missing, start with import. If suppliers or purchase order lines are missing, follow the master data path. If the return transfer fails, check the export configuration, recipient response and ION/ERP processing. The architecture diagrams below add deployment and component details to this process overview.

Further: [Import documents](https://docs.docbits.com/end-user-and-partner-section/end-user-section/how-to-import-documents.md), [Import customer master data](https://docs.docbits.com/infor-integration-and-configuration/importing-customer-master-data.md) and [Export from DocBits](https://docs.docbits.com/infor-integration-and-configuration/exporting-in-docbits.md).

## **DocBits Cloud customer**

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-84a4ad8ff56a4779e5f4cee37b01d1fbe29077a7%2Fdocbits_cloud_customer_architecture.png?alt=media" alt="DocBits Cloud Customer Architecture"><figcaption></figcaption></figure>

## DocBits On premise

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-eb8289d0d7c4f9781ae16960e0ec3bef975e76b3%2Fdocbits_on_premise_architecture.png?alt=media" alt="DocBits On Premise Architecture"><figcaption></figcaption></figure>

Doc**Bits** seamlessly integrates with Infor LN/M3 through ION API, ION Desk, and Infor Standard BODs. Our API integration allows us to export data to Infor and perform master data validation in Doc**Bits**.

## **DocBits Operator Architecture**

All connections between components are secured using industry-standard encryption protocols. SSH, HTTPS, and other secure channels ensure data integrity and confidentiality throughout the system.

**On Premise:**

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-47863c6c69d2efe6ed657b55ea2058b9f90315f1%2FOperator_On-Prem.png?alt=media" alt="DocAgent on-premises architecture diagram with Doc2API, DocFlow, Prefect API work pool and a client machine worker running browsers"><figcaption></figcaption></figure>

{% content-ref url="/pages/22Msant1byxv36JnwHgM" %}
[Prefect Local Setup Requirements](https://docs.docbits.com/overview-and-basics/architecture/prefect-local-setup-requirements.md)
{% endcontent-ref %}

**Cloud**:

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-3eaf3a85aa3cd96829d617b37268edc45ae2263c%2FOperator%20Cloud%20.png?alt=media" alt="Cloud architecture diagram of DocFlow, DocBits Operator, Operator AI with cloud Chrome and the user with Chrome extension"><figcaption></figcaption></figure>

## Exporting Data to Infor

We use the ION API to send the PDF with attributes to IDM and the BOD Sync.CaptureDocument to ION Desk. In ION Desk, we transform the [Sync.CaptureDocument](https://docs.docbits.com/infor-integration-and-configuration/exporting-in-docbits.md) to the desired target BODs based on the document type being processed. These transformed Infor BODs are then automatically imported to LN or M3.

{% hint style="info" %}
Export to [Infor](https://docs.docbits.com/infor-integration-and-configuration/exporting-to-infor.md)
{% endhint %}

## Master Data Validation in DocBits

To identify the supplier or compare/match purchase order lines, we activate a trigger in LN/M3 that sends the Sync.RemitToPartyMaster, Sync.SupplierPartyMaster, and Sync.PurchaseOrder BODs to Doc**Bits**. We configure this process in ION Desk by defining the dataflow to a specific connection point to Doc**Bits**.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-347f504c6a34003468369c3fab9e6e2ab3fa9292%2Fdocbits_architecture%20(1).png?alt=media" alt="DocBits infrastructure diagram: user, load balancer, Kubernetes cluster, and Spaces, Redis and PostgreSQL storage"><figcaption></figcaption></figure>

{% hint style="info" %}
[Master Data Validation](https://docs.docbits.com/infor-integration-and-configuration/importing-customer-master-data.md)
{% endhint %}

## Email Import OAuth Office365

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-cfd8be409f7999b310d33eb698f4613a9a3f1511%2Fo365_architecture.png?alt=media" alt="O365 mail import diagram with the app, DocBits Mail-Service, Microsoft Graph API, database and main system"><figcaption></figcaption></figure>


---

# 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/overview-and-basics/architecture.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.
