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

# Uploading Error Reports

> Upload carrier EDI error reports and create Issues—one, standard error format across all carriers.

## Process

<Steps>
  <Step title="Upload document">
    Upload the document to Noyo
  </Step>

  <Step title="Select or create a Document Stream">
    Tell Noyo which series of reports i.e. [document stream](#document-streams) the report belongs to.
  </Step>

  <Step title="Create or update Issues">
    Noyo compares the document with previous documents in the same stream to create or update [Issues](https://docs.noyo.com/docs/members/issues/overview).
  </Step>
</Steps>

## Supported file types

Carrier error reports are not standardized and come in a variety of formats. Noyo supports all carriers and most file types, including **PDFs**, **Excel** files (`xlx`, `xlsx`), text-based files (`csv`, `json`, `txt`), and images (`png`, `jpg`).

## Document streams

A **document stream** is a series of related EDI error reports for a carrier connection. Noyo compares each new report with previous ones in that stream to create and resolve Issues.

### **Why streams matter**

Most carriers provide one, weekly error report file for a given feed. However, some split errors across multiple types of reports—for example, by line of coverage, population, or error type.

Streams tell Noyo which types of reports should be compared. For example, a dental error report should not be compared with a medical error report. Keeping them in separate streams prevents Issues from being incorrectly created or resolved.

### **When you need more than one stream**

In most cases, a connection only needs **one stream**. Create additional streams when a carrier provides a separate, recurring series of report files that should be evaluated independently.

Common examples include:

* **By line of coverage** — e.g. separate error files for medical vs. dental
* **By error type** — e.g. different categories of errors in separate reports
* **By population** — e.g. separate error files for active employees vs. COBRA

**Example**<br />A carrier sends one medical error report and one dental error report each week. Create two streams, such as **“Cigna Med Errors”** and **“Cigna Dental Errors.”**

Noyo will compare each new medical report only with previous medical reports, and each dental report only with previous dental reports.

If the carrier includes **all coverages in a single report**, one stream is sufficient.

### **How to set up a stream**

1. Upload an error report.
2. Select "create stream" for that report series and give it a clear name, such as **“Cigna Med Errors.”**
3. For future reports in the same series, select the existing stream. If only one stream exists, Noyo will automatically select it.
4. Complete the upload to generate  Issues

## Retrieving issues

<Note>
  Issues can be retrieved via the API, but uploads are only available in-app.
</Note>

See [this page](/docs/members/issues/overview) for more information on managing and retrieving issues.

<CardGroup cols={3}>
  <Card title="Issues" href="/docs/members/issues/overview">
    Overview
  </Card>

  <Card title="List all issues" href="/api-reference/issues/list-issues">
    `GET issues`
  </Card>

  <Card title="Get single issue" href="/api-reference/issues/get-issue">
    `GET issues/{issue_id}`
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.