Supporting files are reference lists, such as price lists, product catalogs or approved cost centers, that Transformation and Rejection rules look values up in while documents are processed. You upload a list once as a CSV file and link it to your rules. When the reference data changes, you update the list instead of the rules.

You can update a list by editing its rows in Docupath or by uploading a newer CSV file. Every change is saved as a new version, and earlier versions stay available to download or use again.

Rules always read the version of the file that is in use. Saving edited rows, or using an earlier version again, creates a new version that comes into use at once. An uploaded file comes into use once Docupath has finished checking it. Documents processed from then on use the new version, and documents that were already processed keep the version they were processed with until they are processed again.

Open the main menu with the dropdown arrow (▾) next to your user avatar, click Supporting files, and click Add New to upload a CSV file. Docupath checks the file in the background, and the Status column shows Processing until the file is ready. The status then changes to Processed, or to Failed if the file could not be read. A status with an info icon, such as an amber Processed, means there is something to check: hover over the icon to see what.

To update a file with a newer CSV, open the file and click Replace. The new file must keep every column of the current version, and it can add new columns. The current version stays in use until the replacement is ready, and it stays in use if the replacement fails.

Click Edit in the ⋮ menu of a file's row to change its values, add or remove rows, or rename it. Your changes stay a draft until you save them, and rules keep using the version in use until then. Saving creates the next version.

While you edit, Docupath checks the rows you add or change against the columns that the file's rules look values up in. A row with nothing in those columns cannot be saved, because no rule could find it. A value that is already on another row gets a warning, because rules use the first matching row. Warnings do not stop you from saving.

The file's page lists every version under Version history, with when it was created, who created it, and how many rows it added, changed and removed. Open a version to see the rows it changed and the note saved with it. Use this version again brings back the rows of an earlier version as a new version. Nothing is deleted.

If your access is limited to some organizations, the files you upload belong to those organizations. Users of those organizations and users with access to all organizations can see them. A file uploaded by a user with access to all organizations can be seen by everyone who can open Supporting files.

Deleting a file removes it and all its versions. You cannot delete a file while a Transformation or Rejection rule is linked to it, even a rule in an organization you do not have access to.

The Admin and Manager roles have all four levels by default. For a custom role, set them on the Supporting Files row of the role builder. Some workspaces show Read and Write columns instead, and there Write covers adding, editing and deleting.