> For the complete documentation index, see [llms.txt](https://docs.unimarket.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unimarket.com/documentation/file-automation-sftp/supplier-master-data-uploads-via-sftp.md).

# Supplier Master Data Uploads via sFTP

Suppliers and their related details can be created and updated efficiently, using the bulk community Supplier Upload function. This service allows you to use a CSV template to synchronize Unimarket with your Finance ERP system, manage bulk updates, or connect/disconnect suppliers in volume.

{% hint style="info" %}
**Note:** This functionality is only available to be completed via **sFTP**.
{% endhint %}

## Intent

* **ERP Synchronization**: Reflect changes from your ERP back into Unimarket, such as a daily feed of new, removed, or updated supplier records.
* **Bulk Updates**: Efficiently update specific fields like Supplier Tags, Vendor IDs, or Buyer Groups across multiple records.
* **Connection Management**: Connect or disconnect suppliers in bulk without manual entry.

## Prerequisites

* **Role**: You must have the **Community Administrator** or **Create Invoices** role.
* **Setup**: Ensure **File Automation** is enabled by your Customer Success Manager and your sFTP connection is established. See [sFTP Setup for File Automation](/documentation/file-automation-sftp/sftp-setup-for-file-automation.md).

## File Format and Logic

The supplier upload mechanism is designed for flexibility:

* **Optional Columns**: Most columns in the template are optional.
* **Column Order**: The order of columns does not matter (e.g., a file could contain only an ID in column A and Supplier Tags in column B).
* **Identification Logic**: The system must find either a **Community Supplier ID** or a **Supplier ID**. If neither ID is found, Unimarket will create a new **Lite Supplier**.

### Important Business Logic

* **Lite Supplier Creation**: If neither the Community Supplier ID nor the Supplier ID is found in the file, Unimarket will attempt to create a new Lite Supplier. The **Company or Trading Name** is the only required field for this action.
* **Email Logic**: If **Remittance Email** or **Order Email** fields are left blank but a **Default Email Address** is provided, the system will automatically use the default address for those roles.
* **US Tax Identification**: When using the **Tax Identification Type** column (US only), the **Tax Number** must follow strict formatting (e.g., EIN must be `99-9999999`).
* **Sequence**: To ensure data processes correctly, always upload the **Supplier Master** file before uploading the **Supplier Addresses** file.

## Supplier CSV Field Definitions

The table below details the specific formatting and logic required for the Supplier CSV template.

| Column Name                 | Description                                                                                       | Format       | Mandatory?                      |
| --------------------------- | ------------------------------------------------------------------------------------------------- | ------------ | ------------------------------- |
| **Community Supplier ID**   | The Unimarket-assigned ID for the supplier in your community.                                     | Alphanumeric | Mandatory (if no Supplier ID)   |
| **Supplier ID**             | Your internal ERP ID for this supplier.                                                           | Alphanumeric | Mandatory (if no Community ID)  |
| **Profile Type**            | Individual, Company/Organization (US), or Company/Organisation (AU/NZ).                           | Alphanumeric | Optional (defaults to Company)  |
| **Company or Trading Name** | The display name of the supplier. Required for creating new "Lite" suppliers.                     | Alphanumeric | Mandatory for new suppliers     |
| **Default Email Address**   | The primary email used for most system notifications.                                             | Valid Email  | Optional                        |
| **Payment Term**            | Must match an existing individual Payment Term Code in your community.                            | Alphanumeric | Optional                        |
| **Connection State**        | Set to **Connected** or **Disconnected**.                                                         | Fixed Value  | Optional                        |
| **Tax Number**              | Format varies by region (e.g., 11 digits for AU, 8-9 for NZ and EIN must be `99-9999999` for US). | Number       | Mandatory if Tax Registered = Y |

## Troubleshooting

If you receive a **"Problem Processing File"** email notification:

1. Go to the **Administration** module and select **File Processing**.
2. Locate the failed file and hover over the **"i" icon** to view the specific error pertaining to the data.
3. Correct the CSV file and re-upload to the sFTP inbound folder.

See [sFTP File Error: Problem Processing File](/documentation/file-automation-sftp/sftp-file-error-problem-processing-file.md) for more detail.

* [Supplier Upload - Template.csv](https://help.unimarket.com/hc/en-us/article_attachments/45852041811609) (377 Bytes)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.unimarket.com/documentation/file-automation-sftp/supplier-master-data-uploads-via-sftp.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
