> 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/export.md).

# Export

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-4e08eafe6e09ecb07743474571aa9aee0ec9b88e%2Fprior-t006-en.png?alt=media" alt="Unsaved Webhook export configuration."><figcaption><p>Unsaved Webhook export configuration.</p></figcaption></figure>

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-df922f11ed9320b65806902f241a1eda3157a46c%2Fprior-u019-en.png?alt=media" alt="Unsaved Infor IDM export configuration."><figcaption><p>Unsaved Infor IDM export configuration.</p></figcaption></figure>

## Overview

The Export page displays all configured export setups, including whether they are active or inactive. From here, users can:

* View and manage existing export configurations
* Create new export connections (e.g., to **Infor**, **Infor & IDM**, **Webhook**, or **SFTP**)
* Edit or delete existing export configurations

## Where to Find It

You can find it under: **Settings** → **Document Processing** → **Export**

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-233fde99cf3dba5bd6fa7ddaf53ae60c097cec55%2Fs150-export_settings_menu_access.png?alt=media" alt="Open export configuration from the English settings."><figcaption><p>Open export configuration from the English settings.</p></figcaption></figure>

## **Using the Export Page**

When you open the Export page, you’ll see a list of all existing export configurations.

Each row in the list shows:

* **Status Indicator**
  * **Green** means the export is active
  * **Red** means the export is deactivated
* **Name** – the name of the export configuration
* **Document Type** – the type of document the export is configured for
* **Sub-Organization** – if the export is limited to a specific sub-organization
* **Export Method** – where the document will be sent (e.g., Infor, IDM, SFTP)
* **Actions** – buttons to **edit, delete** or **activate/deactivate** the configuration

#### **Important Rules for Export Configuration**

For each **document type** **within a given organization or sub-organization**, the following rules apply:

* You can have **only one active Infor export**
* You can have **only one active non-Infor export** (e.g., Webhook, SFTP)

However, it is possible to have:

* **One active Infor export** *and* **one active non-Infor export** at the same time for the same document type
* **Different export configurations for different sub-organizations** — for example, one Infor export for Sub-Org A and another Infor export for Sub-Org B

## **Creating a New Export**

To create a new export:

1. Click on the **“New”** button.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-65bb5dbab5ab07cb1abbb603cfabfe921e30a785%2Fs150-export_create_new_button.png?alt=media" alt="Unsaved new export configuration showing its basic information."><figcaption><p>Unsaved new export configuration showing its basic information.</p></figcaption></figure>

2\. Select the \*\*Export Type\*\* you want to configure (e.g., Infor, IDM, SFTP). 3. Fill in the required fields based on the export type. 4. Save the configuration.

## Export Options

#### Webhook

<details>

<summary>Webhook</summary>

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-ee19f2992d519d2bd544dad1bc3c66bb59263001%2Fimage%20(11).png?alt=media" alt="Export Webhook Configuration"><figcaption></figcaption></figure>

**Field Descriptions**

* **Title** The name of the export configuration. This will appear in the export list.
* **Sub-Organization** *(optional)* A dropdown with all available sub-organizations.
  * If left empty: applies to the main organization.
  * If selected: the export will only apply to the chosen sub-organization.
* **Document Type** Dropdown listing all available document types. This determines which type of document this export configuration applies to.
* **Export URL** The destination URL where the document should be exported.

</details>

#### SFTP

<details>

<summary>SFTP</summary>

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-328db5f240811603a21258069396cfb366f32e64%2Fprior-t007-en.png?alt=media" alt="Unsaved SFTP export configuration."><figcaption><p>Unsaved SFTP export configuration.</p></figcaption></figure>

**Field Descriptions**

* **Title** The name of the export configuration. This will appear in the export list.
* **Sub-Organization** *(optional)* A dropdown with all available sub-organizations.
  * If left empty: applies to the main organization.
  * If selected: the export will only apply to the chosen sub-organization.
* **Document Type** Dropdown listing all available document types. This determines which type of document this export configuration applies to.
* **Username** The username used to authenticate against the SFTP server.
* **Password** The corresponding password for the SFTP account. Ensure the account has write access to the specified folder.
* **Server URL** The hostname or IP address of the target SFTP server.
* **Port** The port used to connect to the SFTP server.
* **Folder** The path on the SFTP server where documents should be uploaded (e.g., `/incoming/invoices/`). Must exist and be writable.
* **XSLT File (Optional)**

  The **XSLT file** allows for transformation of the default DocBits export format.

  * **When to use:** Only if the receiving system requires a different structure or specific formatting that differs from the DocBits default.
  * **Leave it empty** if the default export format meets the requirements.

**Advanced Settings:**

* **Filename Export Mode** Specifies whether the exported file retains its original filename or is renamed using the DocBits document ID.
* **Include Document History** When enabled, the exported file will include the document history based on the logs available on the dashboard.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-497801f4c6938e1fe4050271a6d73c77d08e8f7e%2Fexport_sftp_2.png?alt=media" alt="Dashboard row actions menu with the Document Logs entry highlighted by an arrow" width="316"><figcaption></figcaption></figure>

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-8347f32f2bf767f0204e4e2487468aa68f79897b%2Fprior-u016-en.png?alt=media" alt="Unsaved advanced SFTP export options."><figcaption><p>Unsaved advanced SFTP export options.</p></figcaption></figure>

</details>

#### Infor Export to SFTP

<details>

<summary>Infor Export to SFTP</summary>

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-75bf2e0092036ea27e00c2847ce5a9b5262cfa27%2Fprior-u017-en.png?alt=media" alt="Unsaved Infor SFTP export configuration."><figcaption><p>Unsaved Infor SFTP export configuration.</p></figcaption></figure>

**Field Descriptions**

* **Title** The name of the export configuration. This will appear in the export list.
* **Sub-Organization** *(optional)* A dropdown with all available sub-organizations.
  * If left empty: applies to the main organization.
  * If selected: the export will only apply to the chosen sub-organization.
* **Document Type** Dropdown listing all available document types. This determines which type of document this export configuration applies to.
* **IDM Mapping File** Select a mapping file from the file manager. [Need help creating one? View the IDM Mapping Guide](https://docs.docbits.com/infor-integration-and-configuration/exporting-to-infor/creating-an-idm-mapping-file.md)
* **BOD Mapping File** Select a mapping file from the file manager. [Need help creating one? View the BOD Mapping Guide](https://docs.docbits.com/infor-integration-and-configuration/exporting-to-infor/creating-a-bod-mapping-file.md)
* **Folder** The path on the SFTP server where documents should be uploaded (e.g., `/incoming/invoices/`). Must exist and be writable.

</details>

#### **SMB**

<details>

<summary>SMB</summary>

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-a42daa924f1ce1a586b90ac307bc01552f5ee0ad%2Fprior-u018-en.png?alt=media" alt="Unsaved SMB export configuration."><figcaption><p>Unsaved SMB export configuration.</p></figcaption></figure>

**Field Descriptions**

* **Title** The name of the export configuration. This will appear in the export list.
* **Sub-Organization** *(optional)* A dropdown with all available sub-organizations.
  * If left empty: applies to the main organization.
  * If selected: the export will only apply to the chosen sub-organization.
* **Document Type** Dropdown listing all available document types. This determines which type of document this export configuration applies to.
* **Username** The username used to connect to the SMB share.
* **Password** The corresponding password for SMB authentication.
* **Server URL** The address of the SMB server.
* **Port** Port number used to access the SMB share.
* **Folder** The folder path within the SMB share where documents should be saved (e.g. `/incoming/invoices/`). Must exist and be writable.
* **JPL Mapping File (Optional)**

  The **JPL file** is used to define a transformation of the exported data before it is written to the SMB share.

  * **When to use:** Only when the exported document data needs to be adjusted to match external formatting or system expectations.
  * **Leave it empty** if no transformation is necessary.

</details>

#### **Infor IDM**

<details>

<summary>Infor IDM</summary>

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-2fefee6058a7ca75a41f8373d3892a20a354ffb9%2Fimage%20(10).png?alt=media" alt="Export Infor IDM Configuration"><figcaption></figcaption></figure>

**Field Descriptions**

* **Title** The name of the export configuration. This will appear in the export list.
* **Sub-Organization** *(optional)* A dropdown with all available sub-organizations.
  * If left empty: applies to the main organization.
  * If selected: the export will only apply to the chosen sub-organization.
* **Document Type** Dropdown listing all available document types. This determines which type of document this export configuration applies to.
* **ION Mapping File** Select a mapping file from the file manager.
* **IDM Mapping File** Select a mapping file from the file manager. [Need help creating one? View the IDM Mapping Guide](https://docs.docbits.com/infor-integration-and-configuration/exporting-to-infor/creating-an-idm-mapping-file.md)
* **Cloud / On-Prem Toggle** A switch to indicate the Infor deployment type:
  * **Cloud**: Select this if Infor CloudSuite customer.
  * **On-Prem**: Select this if Infor is self-hosted.

</details>

#### **Infor ION**

<details>

<summary>Infor ION</summary>

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-f8d2abacef8f9905cef316bf55cbd52f88d007ac%2Fprior-u020-en.png?alt=media" alt="Unsaved Infor ION export configuration."><figcaption><p>Unsaved Infor ION export configuration.</p></figcaption></figure>

**Field Descriptions**

* **Title** The name of the export configuration. This will appear in the export list.
* **Sub-Organization** *(optional)* A dropdown with all available sub-organizations.
  * If left empty: applies to the main organization.
  * If selected: the export will only apply to the chosen sub-organization.
* **Document Type** Dropdown listing all available document types. This determines which type of document this export configuration applies to.
* **ION Mapping File** Select a mapping file from the file manager.
* **BOD Mapping File** Select a mapping file from the file manager. [Need help creating one? View the BOD Mapping Guide](https://docs.docbits.com/infor-integration-and-configuration/exporting-to-infor/creating-a-bod-mapping-file.md)
* **Cloud / On-Prem Toggle** A switch to indicate the Infor deployment type:
  * **Cloud**: Select this if Infor CloudSuite customer.
  * **On-Prem**: Select this if Infor is self-hosted.

</details>

#### Infor IDM + ION BOD

<details>

<summary>Infor IDM + ION BOD</summary>

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-b4fd72f1d08a5a6179060ba96a0f54991812f38d%2Fprior-u021-en.png?alt=media" alt="Unsaved Infor IDM ION BOD export configuration."><figcaption><p>Unsaved Infor IDM ION BOD export configuration.</p></figcaption></figure>

**Field Descriptions**

* **Title** The name of the export configuration. This will appear in the export list.
* **Sub-Organization** *(optional)* A dropdown with all available sub-organizations.
  * If left empty: applies to the main organization.
  * If selected: the export will only apply to the chosen sub-organization.
* **Document Type** Dropdown listing all available document types. This determines which type of document this export configuration applies to.
* **ION Mapping File** Select a mapping file from the file manager.
* **IDM Mapping File** Select a mapping file from the file manager. [Need help creating one? View the IDM Mapping Guide](https://docs.docbits.com/infor-integration-and-configuration/exporting-to-infor/creating-an-idm-mapping-file.md)
* **BOD Mapping File** Select a mapping file from the file manager. [Need help creating one? View the BOD Mapping Guide](https://docs.docbits.com/infor-integration-and-configuration/exporting-to-infor/creating-a-bod-mapping-file.md)
* **Cloud / On-Prem Toggle** A switch to indicate the Infor deployment type:
  * **Cloud**: Select this if Infor CloudSuite customer.
  * **On-Prem**: Select this if Infor is self-hosted.

</details>

### For Infor CloudSuite customers

#### Infor IDM + LN

<details>

<summary>Infor IDM + LN</summary>

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-f63e7cd34e0eedb58ef14a98611994785ea522b4%2Fprior-u022-en.png?alt=media" alt="Unsaved Infor IDM LN export configuration."><figcaption><p>Unsaved Infor IDM LN export configuration.</p></figcaption></figure>

**Field Descriptions**

* **Title** The name of the export configuration. This will appear in the export list.
* **Sub-Organization** *(optional)* A dropdown with all available sub-organizations.
  * If left empty: applies to the main organization.
  * If selected: the export will only apply to the chosen sub-organization.
* **Document Type** Dropdown listing all available document types. This determines which type of document this export configuration applies to.
* **ION Mapping File** Select a mapping file from the file manager.
* **IDM Mapping File** Select a mapping file from the file manager. [Need help creating one? View the IDM Mapping Guide](https://docs.docbits.com/infor-integration-and-configuration/exporting-to-infor/creating-an-idm-mapping-file.md)
* **LN Mapping File** Select a mapping file from the file manager. [Need help creating one? View the LN Mapping Example](https://docs.docbits.com/infor-integration-and-configuration/exporting-to-infor/ln/example-export-ln.md)

</details>

#### Infor IDM + M3

<details>

<summary>Infor IDM + M3</summary>

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-6b88554641599d1153956b7bd176e43818d7158a%2Fprior-u023-en.png?alt=media" alt="Unsaved Infor IDM M3 export configuration."><figcaption><p>Unsaved Infor IDM M3 export configuration.</p></figcaption></figure>

**Field Descriptions**

* **Title** The name of the export configuration. This will appear in the export list.
* **Sub-Organization** *(optional)* A dropdown with all available sub-organizations.
  * If left empty: applies to the main organization.
  * If selected: the export will only apply to the chosen sub-organization.
* **Document Type** Dropdown listing all available document types. This determines which type of document this export configuration applies to.
* **ION Mapping File** Select a mapping file from the file manager.
* **IDM Mapping File** Select a mapping file from the file manager. [Need help creating one? View the IDM Mapping Guide](https://docs.docbits.com/infor-integration-and-configuration/exporting-to-infor/creating-an-idm-mapping-file.md)
* **M3 Mapping File** Select a mapping file from the file manager. [Need help creating one? View the M3 Mapping Example](https://docs.docbits.com/infor-integration-and-configuration/exporting-to-infor/m3/example-export-m3.md)

</details>

#### Infor IDM + M3 (toml)

<details>

<summary>Infor IDM + M3 (toml)</summary>

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-c987e89c808d8c10934784f9ae7e983454645153%2Fprior-u024-en.png?alt=media" alt="Unsaved Infor IDM M3 export configuration with TOML."><figcaption><p>Unsaved Infor IDM M3 export configuration with TOML.</p></figcaption></figure>

**Field Descriptions**

* **Title** The name of the export configuration. This will appear in the export list.
* **Sub-Organization** *(optional)* A dropdown with all available sub-organizations.
  * If left empty: applies to the main organization.
  * If selected: the export will only apply to the chosen sub-organization.
* **Document Type** Dropdown listing all available document types. This determines which type of document this export configuration applies to.
* **ION Mapping File** Select a mapping file from the file manager.
* **IDM Mapping File** Select a mapping file from the file manager. [Need help creating one? View the IDM Mapping Guide](https://docs.docbits.com/infor-integration-and-configuration/exporting-to-infor/creating-an-idm-mapping-file.md)
* **M3 toml Mapping File** Select a mapping file from the file manager or use the Select TOML option to use a TOML file created with the rule manager. [Need help creating one? View the Rule Manager Guide](https://docs.docbits.com/administration-and-setup/settings/document-processing/rule-manager.md)

</details>

## Video tutorial: Configure and test an ERP export

{% embed url="<https://docbits-videos.fra1.cdn.digitaloceanspaces.com/settings-assistant/erp-export-admin/v1/en.mp4>" %}
Configure and test an ERP export
{% endembed %}

[Watch with subtitles and chapter navigation](https://docbits-videos.fra1.cdn.digitaloceanspaces.com/settings-assistant/erp-export-admin/v1/en.html)

Some native product labels may remain in another language. Technical field IDs are preserved.

I use a dedicated test configuration and document type. These invoices are synthetic. Our test receiver checks data transmission and makes no postings in a production ERP. I leave the other integrations alone.

In the export configuration, I check the document type, the organization, and the export type. This example uses Generic API in the cloud. Credentials JSON and TOML field mapping are separate files. In real projects, the target system, permissions, and sub-organization must match the intended process.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-4acd9f251c957045fee7adc9ee64ed572efd6994%2Fadmin-configuration-en-recovery-export-v1.png?alt=media" alt="Export configuration scoped to the training document type"><figcaption><p>Export configuration scoped to the training document type</p></figcaption></figure>

In the corrected mapping, the DocBits field invoice\_id supplies the invoice number sent to our test receiver. Supplier, total amount and currency are mapped too. This test covers header data. Line items and ERP postings need their own business checks for each project.

I upload the corrected TOML file and save the configuration. Then I reopen it and check that the change was saved. I keep the prepared test credentials; production credentials must stay out of the recording.

Now I return to the invoice with the failed export and restart the export exactly once. I wait for processing to finish. An accepted request alone would not prove a successful transfer.

DocBits now shows the invoice as finished. I also check the receipt from our test receiver. The invoice number, supplier, amount and currency match the test invoice. Authentication and transfer succeeded. The test receiver does not confirm an ERP posting.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-20afe8efa7a79b6206e84097cf45d4de8c636c58%2Fadmin-receipt-en-recovery-export-v1.png?alt=media" alt="Actual receipt at the test receiver; no ERP posting"><figcaption><p>Actual receipt at the test receiver; no ERP posting</p></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/administration-and-setup/settings/document-processing/export.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.
