> 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/infor-integration-and-configuration/exporting-in-docbits.md).

# Exporting in DocBits

## From the checked document to the target system

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-5185441bfd08dd0f005c183d1aa32b844b90fbc4%2Fprocess-export-en-20261028.png?alt=media" alt="Export from DocBits: Check preparation, transmission and feedback separately."><figcaption><p>Check preparation, transmission and feedback separately. The diagram is schematic; the active settings of your organization determine the actual behavior.</p></figcaption></figure>

When exporting, DocBits transfers documents and data to an established connection. Whether an export is offered or triggered automatically depends on the document type, status, workflow and export configuration.

1. **Check prerequisites:** Review the document data, open tasks and approvals required by your process. Successful PO matching does not replace these steps.
2. **Clarify export destination:** Check which configuration applies to the document type and organization or sub-organization. The export management supports Infor, Infor & IDM, Webhook and SFTP, among others. The actual scope of delivery depends on the connection set up.
3. **Trigger Transfer:** Use the intended document action or configured workflow. An alternative export is set up separately; its availability status is not the status to be set after export.
4. **Check feedback:** Check document status and available recipient responses. For an end-to-end check, you also check the associated process in the target system. For Infor, further processing steps can follow in ION and ERP.

### If export fails

Open the error details before exporting again. Repeated sending will not resolve an incorrect mapping or a rejection by the recipient. Use the response to check document values, mapping and target configuration, and check whether a transaction has already been created in the target system.

### Further instructions

* [Export module](https://docs.docbits.com/infor-integration-and-configuration/exporting-in-docbits/export-module.md): Getting started with administration.
* [Export configuration](https://docs.docbits.com/administration-and-setup/settings/document-processing/export.md): Connections and scopes.
* [Alternative export](https://docs.docbits.com/infor-integration-and-configuration/exporting-in-docbits/alternate-export.md): separate export path per document type and status.
* [Export to Infor](https://docs.docbits.com/infor-integration-and-configuration/exporting-to-infor.md): downstream Infor processing.

A guide to exporting documents in DocBits.


---

# 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/infor-integration-and-configuration/exporting-in-docbits.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.
