---
title: "Identify EDI Import Errors"
slug: "identify-edi-import-errors-1"
updated: 2026-06-15T19:51:19Z
published: 2026-06-15T19:51:19Z
canonical: "docs.restaurant365.com/identify-edi-import-errors-1"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.restaurant365.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Identify EDI Import Errors

Use the [Docs to process Log](/doc/docs/documents-to-process-log-and-errors) to identify and troubleshoot EDI import errors. Before reviewing error messages, first confirm that the vendor's file arrived in R365 at all.

---

## How To Identify the Most Common Errors With EDI Imports - Video

[Embedded content](https://player.vimeo.com/video/1012834976?h=839391ac3d&badge=0&autopause=0&player_id=0&app_id=58479" frameborder="0" allow="autoplay; fullscreen; picture-in-picture; clipboard-write; encrypted-media" style="position:absolute;top:0;left:0;width:100%;height:100%;" title="How To Identify the Most Common Errors With EDI Imports)

---

## Locate EDI Import Error Messages

To find EDI import error messages, follow these steps:

*Click steps to expand for additional information and images.*

****1 )** Navigate to the **Docs to process log**.**

1. Open the **Admin** application from the left navigation rail
2. Expand the **Accounting** folder
3. Select **Docs to Process Log.**

![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-BG0I18N4.png)

****2)** Filter the log by **Type = FTP****

Click the **filter** action and set

1. Column to **Type**
2. Filter to **Equal to**
3. Value to **FTP.**
4. Click **Apply** to set the filter.

![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-E1427BJM.png)

EDI files are labeled FTP in R365 because they are delivered via FTP/SFTP. This filter shows only EDI imports.

![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-UT1V3HW8.png)

****3)** Locate the entry for the file that needs to be reviewed.**

![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-CSV1QZUH.png)

****4)** Review the **Message** column for the file entry.**

- If the message is **File Found** with no duplicate entry directly above it, the file imported successfully.
- If the message is **Importing** with a duplicate entry directly above it, the file encountered an error and was not imported. The duplicate entry shows an **Error** status with a message explaining the failure.

![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-J743NO56.png)

****5)** Review the message on the **duplicate entry** to identify the import error.**

In the example below, the import had an error with the location entered on the detail line.

![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-VN8SWU5C.png)

---

## Understand Error Messages

Each error message contains up to three parts:

![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-PQKW0JMQ.png)

|  | Part | Description | Example |
| --- | --- | --- | --- |
| **1** | Status | The import result. Possible values are: - Importing - Duplicate - Found File - Failed | Failed |
| **2** | Reason | Why the import failed. Only appears when an error occurred. | Missing Vendor |
| **3** | Additional Information | Supplemental detail about the failure, such as the missing vendor name. | Acme Foods |

### Common Import Errors

Some of the common import errors include the following:

| Message | Error Description |
| --- | --- |
| Failed \| Missing Vendor \| (Vendor) | The vendor name within the invoice file does not match the Vendor Record name in R365 or the vendor has not yet been created in R365. Verify that the vendor name in R365 matches exactly what appears in the invoice file. |
| Failed \| Missing Vendor \| Company | The vendor is sending the file in an unsupported format (not CSV). Contact the vendor to correct the file format. |
| Failed \| Invalid | The location on the invoice does not have access to the appropriate vendor record. Verify that the location is linked to the correct vendor in R365. |
| Duplicate \| (#) Success | The file contained duplicate invoices. Duplicate invoices were not imported; unique invoices were processed. Review the file to determine which invoices need to be entered manually. |

---

## When to Contact the Vendor vs. R365 Support

| Situation | Who to contact |
| --- | --- |
| No entries appear in the Docs to Process Log for an expected vendor | Contact **R365 Support** first to confirm whether R365 received the file |
| Error involves a missing vendor, location, or account | Fix the record in **R365**, then ask Support to reprocess the file if needed |
| Error is "Missing Vendor — Company" | Contact the **vendor** — the file is being sent in an unsupported format |
| R365 Support confirms the file was never received | Contact the **vendor** to resend and check their EDI configuration |
| Error persists after applying the fix | Contact **R365 Support** to manually reprocess the file |

For a full list of error types and resolutions, learn more about [Troubleshooting EDI Imports](https://docs.restaurant365.com/docs/en/troubleshooting-edi-imports).

Restaurant365