Ways to bring vendors in
- Bulk import a CSV. On the Vendors tab, click Import vendors to upload a CSV. Dash.fi reads your file’s column headers, lets you map them to vendor fields, and then creates the vendors. Row-by-row validation happens automatically as part of processing. This is the fastest way to load a list exported from another system.
- Sync from a connected accounting integration. If Dash.fi integrates with your accounting system — QuickBooks Online, QuickBooks Desktop, Xero, NetSuite, or Sage Intacct — connecting it syncs your vendors automatically. See Accounting integrations.
- Send your list to Dash.fi. Prefer not to do it yourself? Send your exported file to support@dash.fi or your account executive and the team will import it for you.
Bulk import a CSV
1
Click Import vendors
On the Vendors tab, click Import vendors to open the import wizard.
2
Get the template
Download the CSV template to see the exact columns Dash.fi expects. Fill in the template, or upload your own export and map its columns in a later step.
3
Upload your file
Upload your vendor file. Only
.csv files are supported.4
Map columns
Match your file’s columns to Dash.fi’s vendor fields (listed below). Dash.fi detects your file’s headers to make this easier.
5
Review and fix rows
Dash.fi opens the review table with a row per vendor. Any row that can’t be imported as-is is flagged with the reason (for example, an invalid currency code or email). Fix flagged rows inline, or use Bulk actions to update, skip, or re-enable many rows at once (see Bulk actions).
6
Process
Click Import all vendors. Dash.fi validates each row as it processes it, creates the vendors that pass, and leaves the rest flagged for you to fix and retry. The import continues in the background — you can leave the page and come back later.
Bulk actions
The review table lets you apply the same change to many rows at once instead of editing each row by hand. It’s useful when a whole batch is missing the same field, when you want to skip a subset, or when you want to standardize a value across every row that matches a pattern. Open Bulk actions on the review table. You can target rows two ways:- By manual selection. Tick the checkbox on each row you want to change. Selection carries across pages of the table.
- By criteria. Leave the row checkboxes alone and instead describe the rows you want to hit. Dash.fi finds every unimported row that matches.
Match rows by criteria
In the Bulk edit sheet, use the Match items section to narrow the rows the actions will run on. You can combine any of these filters (they’re joined with AND):- Row status. Pick any of Ready, Skipped, or Failed to include rows in those states.
- Validation status. Pick any of Pending, Valid, or Needs attention.
- Field match. Pick a field and a match type, then enter a value. Match types are:
equals— exact match, case-sensitive.equals (ignore case)— exact match, case-insensitive.contains— substring match, case-sensitive.contains (ignore case)— substring match, case-insensitive.is empty— the field has no value. No value input needed.
If one of your actions changes row status,
Failed is disabled as a status criterion — you can only set status on rows that are currently Ready or Skipped, so a Failed criterion combined with a set-status action would match nothing.Apply an action
Below the criteria, add one or more actions. Each action is one of:- Set field — write a value into a field on every matching row. For example, set Currency code to
USD. - Clear field — unset a field on every matching row.
- Set status — mark matching rows Ready to include them in the next import, or Skipped to exclude them.
Examples
- Set Currency code to
USDon every row where Currency codeis empty. - Mark every row where Vendor
contains (ignore case)"acme"as Skipped. - Clear External ID on every row with validation status Needs attention.
Who can act on a vendor import
A vendor bulk import is scoped to the person who started it. Only that user can Validate, Process, or Delete the import, edit rows, or run Bulk actions — the API rejects the same actions from anyone else with a 403 Forbidden, and the buttons are hidden or disabled in the UI. Other members of the account can still open the import and read every row, its status, and its errors, so a colleague can help you diagnose a failed row even though the creator is the only one who can move the import forward. If the original creator is unavailable, delete the import and re-run it from your own account.Vendor fields
The import supports these fields per vendor:Your export from another system won’t match these columns exactly — that’s fine. Map whatever columns you have during import. Anything you can’t provide now can be added to each vendor later.