When you already keep a customer, supplier, or provider list in a spreadsheet, import it instead of typing each party. The import matches rows against the register so a re-import never creates duplicates, and a merge tool cleans up any that slipped in by hand.
Before you start
- You need the Contributor, Editor, or Workspace Admin role.
- Export the list as CSV with a header row. Files up to 5 MB and 2,000 rows are accepted; larger files are cut at 2,000.
- Every row in one import relates to the same entity in the same default role, unless the file has a role column.
Import a file
- Open Relationships and click Import CSV.
- Drop the file or choose it. The first row is read as the header.
- Pick the entity the parties relate to and the default role (Customer, Supplier, PSP, and so on).
- Click Map columns. Columns are matched to fields automatically by their header (a column called "Company" or "Merchant" maps to Party name, "Reg no" to Registration no., and so on); adjust any that were missed. One column must map to Party name. Available fields:
| Field | Notes |
|---|---|
| Party name | Required |
| Legal name | |
| Jurisdiction | Country name or ISO code |
| Registration no. | Used first when matching |
| Website | |
| Account reference | Stored on the relationship |
| Since | The relationship's start date |
| Role | Overrides the default role for that row |
| Notes | Appended to the party's notes |
- Click Preview. The plan shows how many parties will be created, how many match existing parties (the relationship is added, nothing overwritten), how many rows are duplicates inside the file (merged on import), and how many rows have no name (skipped).
- Click Import. The result repeats the counts.
The file is read in your browser; only the mapped rows are sent to the workspace.
How matching works
A row matches an existing party when the registration number is the same, or, failing that, when the name and jurisdiction are the same, ignoring case and spacing. A matched party gains the relationship and any blank fields the row can fill; values already recorded are never overwritten. Running the same import twice is a no-op.
Merge duplicates
If two records turn out to be the same party (one typed as "Jeton" and one as "Jeton Payments UK Ltd", say):
- Open Relationships and click Merge, or open the party you want to keep and click Merge into….
- Pick the duplicate (the record that goes away) and the party to keep.
- Confirm. Every relationship, document, and screening reference on the duplicate moves to the kept party; the duplicate's notes are appended and its registration number and website fill blanks. The duplicate is archived, and the merge is recorded in the workspace audit trail.
When both records relate to the same entity in the same role, the two relationships fold into one and the documents follow.
Related articles
- The Relationships register: parties, groups, and the party page
- Add a relationship: one at a time, from the KYB Manager or the party page
- The audit log: where merges and imports are recorded