> ## 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 structured issues

## Process

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

  <Step title="Document parsing">
    Noyo parses the document into a structured format
  </Step>

  <Step title="Issue matching">
    [Issues](/docs/members/issues/overview) are created and matched to previous issues.
  </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 sources (streams)

In order to create issues or resolve existing issues, the document needs to be associated with a document source (sometimes referred to as a "stream"). A source defines rules for recognizing partner documents and most importantly, enabling the tracking of recurring issues within document streams and automating their resolution when fixed.

For example, a carrier may deliver their error reports for all lines of coverage in a single file. In this case, you would create a single document source for all lines of coverage.

Alternatively, a carrier may deliver a separate file for each line of coverage. In this case, you would create a separate document source for each line of coverage– indicating that if the medical file doesn't include a dental issue, that should not be taken as indication that the issue has been resolved.

No issues will be created for an uploaded document if it isn't associated with a document source.

## 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>