> For the complete documentation index, see [llms.txt](https://engyon.gitbook.io/engyon/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://engyon.gitbook.io/engyon/en/frequently-asked-questions/sources/importing-an-excel-source-list-into-engyon.md).

# Loading Excel source list into Engyon

Question: Can I import an Excel source list into Engyon?

Answer: No, it is not possible to import source requests from an Excel list. The reasons for this are as follows:<br>

1. In Engyon, all source requests are linked to one or more procedures. The benefits of this are:

   1. When performing procedures, references can be made directly from the documents linked to the procedure, without having to drag them to the procedure first;
   2. Teams are forced to only request documents/sources for which procedures are also present. This prevents teams from requesting documents that are not actually needed. This is a risk when starting with a long generic (Excel) list and omitting items that are not applicable.
   3. Because procedures are linked to audit units (group components), source requests are also directly linked to audit units (which means, for example, you only see the source requests of a specific audit unit when filtering on it).

   If Excel lists could be imported, they would need to contain a 'linked procedure(s)' column, where at least 1 procedure must be entered for each source request, which exactly matches the description in Engyon. Names of procedures are long and therefore error-prone, making an Excel import option undesirable.<br>
2. The strength of Engyon is working with a shared list by the firms that use Engyon. Firms can provide input, after which we determine whether it will be processed. This ensures that it takes firms and teams as little time as possible to arrive at a source list. If every firm uses its own Excel list as a basis, this principle is lost.

{% hint style="info" %}
Source requests can be made client-specific in the tool (using the <kbd>adjust</kbd> button); when rolling forward the audit to the following year, this adjustment is also included.
{% endhint %}