> 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/edi/edi/troubleshooting-5.md).

# Troubleshooting

## Here is some advice on troubleshooting common problems:

**Data formatting errors:**

* Carefully review the EDI structure and format of your messages to ensure they comply with standards and specifications.
* Validate data fields for correct syntax and formatting according to agreed standards such as ANSI X12 or EDIFACT.
* Make sure the transformations and templates used are correctly configured to properly format and interpret the data.

**Partner compatibility issues:**

* Review your business partner's configurations and specifications to ensure they match your own.
* Communicate with your partner to identify any discrepancies or incompatibilities and work together to find solutions.
* Implement adjustments in your EDI configurations if necessary to improve compatibility with your partner.

**Handling transmission errors:**

* Monitor your EDI transmissions regularly to identify potential errors or failures early.
* Implement mechanisms for error detection and remediation, such as automated notifications of transmission errors or setting up retry mechanisms for failed transmissions.
* Perform regular tests of your transmission processes to ensure they work reliably and without errors.

**Documentation and logging of errors:**

* Keep detailed logging of all errors and problems in EDI transactions, including causes and actions taken.
* Document solutions to recurring problems to resolve and prevent future errors more quickly.

**Involve subject matter experts:**

* When necessary, bring in subject matter experts or EDI consultants to solve complex problems or address specific challenges.
* Use resources such as forums, training, or support from EDI providers for additional assistance with troubleshooting.

By systematically applying these tips, you can effectively troubleshoot EDI transactions and ensure the reliability of your electronic business communications.

## Effective rules and activation

If an electronic credit note appears as Invoice, follow the [classification troubleshooting guide](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/edi/credit-note-recognized-as-invoice.md). It covers the effective custom/default source, type codes, Extraction Paths and safe activation.


---

# 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/global-settings/document-types/edi/edi/troubleshooting-5.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.
