Uploading Your Portfolio to Strise

You can upload your existing portfolio to Strise using a CSV file. This is the fastest way to get started if you already have a list of companies or private persons to monitor. Companies and private persons are uploaded separately, each from its own portfolio tab, with its own file format. If you integrate with the Connect API, you can also sync your customer list programmatically.

How to Upload

1. Open the portfolio view and select the Companies or Private persons tab, depending on what you're uploading.
2. Open the ⋯ menu in the portfolio header and click Upload portfolio. The same menu holds Download portfolio, which exports the entities already in that tab as a CSV.
3. On the File step, browse for your CSV file or drag and drop it into the upload area. Once the file has been read, the step reports how many of its rows matched a company in Strise, and then either lists what the steps after it will cover — a count per concern — or tells you that nothing needs your attention.
4. Click Next through the steps the file called for. Each concern gets its own step, and each of those steps is there only when the file you uploaded has something of that kind in it.
5. On the Import step, review the preview, tick the monitoring checkbox if you want it, and click Upload. The dialog then reports how many rows were queued for import, how many rows in the file were not imported, and — rarer — how many were accepted but could not be queued, and stays open until you click Close.

The steps, in the order you meet them:

So a clean file is just File followed by Import. What the middle steps ask of you is described in Handling Duplicates, Errors and Warnings, When one number matches several companies and Creating a custom company for an unresolved row. The dialog header shows the steps your file calls for and which one you're on; its footer holds Back and Next. Choosing a different file, or closing and reopening the dialog, starts again at File and puts your choices on the Resolve step, and the ticks on the Create step, back to their defaults. If nothing in the file could be read, the File step says so and asks you to fix the file and replace it.

File Format

The upload accepts CSV files only. If your data is in Excel format, convert it to CSV first:

1. Open the file in Excel.
2. Go to File > Save As.
3. Select CSV (Comma delimited) as the file type.
4. Save and upload the resulting .csv file.

One file may carry at most 1000 data rows; a header row doesn't count towards that. A larger file is refused — both when it's read and again if you submit it — with a message naming your file's row count and the limit. Split it into files of 1000 rows or fewer and upload them one after the other.

Companies

Every row must have exactly six columns, in this order:

Example (comma-delimited, with a header row):

Name,Organization number,Country,Assignee emails,Tags,Status
Nordfjord Fisheries,123456789,NO,anna@yourcompany.com,New customer,In Review
Lindqvist Consulting,5566778899,SE,"anna@yourcompany.com, jon@yourcompany.com","High risk, Retail",Account
,12345678,DK,,,Following
Thames Consulting Limited,01234567,GB,,Retail,Following
Shannon Logistics Ltd,196234,IE,anna@yourcompany.com,,In Review
Ridgeline Analytics Inc,4562893,US,,Tech,Prospect

The Download template button on the File step always emits the current column order, so use it if you're unsure.

Countries and organization number formats

Norway, Sweden, Denmark, Finland and the United Kingdom are looked up directly against the national business registry. Every other country is looked up against Strise's global company data, which covers a company only if a registry, VAT or other identifier for it is present there. A company registered outside the five registry countries may therefore report Company not found even though the number is correct.

Where the registry has a single canonical format, Strise checks the number's shape before searching and tells you what it expected instead of reporting the company as missing:

A UK number is always 8 characters, and a spreadsheet drops the leading zeros from an all-digit column, so 01234567 saves as 1234567. Strise searches the number as you wrote it and then, if that finds nothing, again with the zeros put back — so you don't have to reformat the column. Numbers for the other four countries are never padded.

These are the five countries looked up against a national registry, so a shape check is meaningful. Numbers for every other country are accepted as written and searched as-is — those companies are matched on any identifier Strise holds for them, which may be a registry number, a VAT number or another registration, and those have no single format to check against.

Country codes are ISO 3166-1 alpha-2, not the country's own abbreviation. GE is Georgia, so a German company must use DE; AT is Austria, not Australia (AU). A row with the wrong code is searched in the wrong country and reports Company not found.

When one number matches several companies

Occasionally one organization number is held by more than one company in Strise's data — a registry number that should be unique but appears on two records, or a number that is a registry number for one company and a VAT or other identifier for another. Strise never picks one silently: it puts every candidate in front of you on the Resolve step and lets you choose.

The candidates are ranked by how closely each company's name matches your file's Name cell, best first, and the best-scoring one is pre-selected — so the common case is a single confirmation rather than a comparison. Every row also carries a None of these option, always available, for when the right company isn't among the candidates. Choosing a candidate imports the row as that company. Choosing None of these sends the row on to the Create step instead, in the same position as a row nothing matched — see Creating a custom company for an unresolved row.

If your file's Name cell was empty, Strise has nothing to rank the candidates by, so nothing is pre-selected — you have to make a choice yourself before the row can import.

When the number matches exactly one company, that company is always used and the row never reaches the Resolve step; a name that disagrees with it does not stop the row from importing, and the row is listed under Warnings instead so you can see which company it actually resolved to.

Creating a custom company for an unresolved row

This option requires the Custom Entities module and the permission to create custom entities. Ask your CSM to enable Custom Entities for your team if you don't see it. Without it, every unresolved row is a hard error.

When a row reports Company not found, Strise first searches its own data by your file's Name cell and country, and offers whatever it finds as suggestions on the Resolve step, ranked the same way as the several-companies case above and with the same None of these option. An organization number that finds nothing is often mistyped, transposed, or from the wrong registry, and the company is frequently in Strise's data under the name you wrote — so a suggestion here is worth checking before you resort to creating a new company.

If a search by name and country finds nothing, Strise drops the country and searches the name alone across every country it holds data for. A result from this wider search is labelled Name match only and shows the candidate's own country rather than the one your file named — check that country before accepting, since the match rests on the name alone and your file's country cell could just as easily be the one that's wrong. Strise offers at most five candidates for a row, best first.

A row whose Name cell was left empty has nothing for either search to run on, so both are skipped and the row goes straight to the Create step below.

A row with no suggestions from either search, or whose suggestions you reject, continues to the Create step below — as does a row several companies matched, once you choose None of these for it. The name search runs regardless of country, so a row in Norway, Sweden, Denmark, Finland or the United Kingdom can still reach the Resolve step and be imported as a suggested company. What's gated by country is creating a new one: inside those five countries Strise syncs the registry directly, so a number that doesn't match there is almost always wrong, and the Create step is never offered for it — choosing None of these on such a row is a hard error.

The offer lives on its own Create step, headed Companies not found. That step lists every row that reaches it — one no company matched at all, or one whose Resolve step suggestions you rejected — with no cap on how many it shows, so a row far down a long file is as easy to find as the first one. The Import step's preview then shows the rows you left ticked alongside the rows that matched or were resolved to a company, capped at the first 20 between them, so you can see everything the upload will do before you run it. If a row was neither resolved, created nor matched, the Import step tells you how many such rows there are before you upload.

• It's per row, and ticked by default. Every offered row your file gave a name is already ticked to be created. Untick the ones you don't want; there's no control to untick them all at once.
• The step shows the country's flag and name, not just its code, so a typo like GE (Georgia) where DE (Germany) was meant is visible before you create anything. Each row also shows its line number, its organization number, and the assignees, tags and status your file gave it.
• An organization number is required. A row with no usable organization number is never offered for creation; add that company to your portfolio by hand instead.
• A name is required, but your file doesn't have to supply it. A row whose Name cell was left empty is offered too: instead of a name, it shows a Company name input, and its tick stays disabled until you type one. Typing a name ticks the row for you, and the company is created under the name you typed. Clear the name again and the row is unticked and its tick disabled. A row whose file did supply a name shows that name as text — the input appears only where the file left the name out, and a name that came from the file can't be changed here.
• Created companies have no registry data behind them. They're custom companies: they appear in the portfolio, are screened for sanctions, PEP and adverse media, are monitored, and can be reviewed, tagged, assigned and given a status. Nothing backs them from an official business registry, and their details are exactly what was in your CSV file. If the company later appears in Strise's registry data, your team can connect the custom company to the registered one.
• Status, tags and assignees come from the CSV row, same as any other row. Whether the new company is added to monitoring follows the Add uploaded companies to monitoring checkbox described under Monitoring below — not the default used when you create a custom company by hand elsewhere in Strise, which monitors it and sets its status to Following automatically.
• Re-uploading the same file doesn't create duplicates. A row whose custom company already exists for your team, its country and its organization number reuses that company instead of creating another one.
• Creation happens in the background, like the rest of the upload, so a created company doesn't appear in your portfolio immediately.

Private persons

Every row must have exactly seven columns, in this order:

Example (comma-delimited, with a header row):

Name,National identity number,Country,Birth date,Assignee emails,Tags,Status
Kari Nordmann,01019012345,NO,1990-01-01,anna@yourcompany.com,Onboarding,In Review
Jens Jensen,,DK,,,"Onboarding, VIP",Following

Formatting notes

• Header row — optional. Strise detects and skips it automatically.
• Delimiter — detected automatically. Semicolon, comma, tab, and pipe all work.
• Optional cells — leave them empty, but keep the delimiters so the row still has the full column count.
• Quoting — in a comma-delimited file, wrap cells that contain commas (multiple assignee emails or tags) in double quotes. Excel and the downloadable template do this automatically.

Handling Duplicates, Errors and Warnings

Strise validates the file before anything is imported. Each of the three gets its own step in the dialog, and every flagged row is shown with the line number it occupies in the file, counting the header row if there is one. A flagged row is presented the same way as a row that matched: the company it resolved to, or — where none did — the name, organization number and country your file gave it, alongside the assignees, tags and status from the file. A line Strise could not read at all has no columns to show, so that line falls back to its raw text from the file:

• Duplicates — companies are matched by the company the organization number resolves to, and private persons by national identity number, in both cases against what your team already holds and against other rows in the same file. A row that does not resolve to a company, or that has no national identity number, is never flagged. The step lists each duplicated row with the company it resolves to — for private persons, the name and birth date the row carries — alongside the assignees, tags and status from your file. Those columns are labelled "in file" because they're what the row proposes, not what your portfolio currently holds, and the choice below decides their fate. Choose how to handle them: Merge (the default — data from the file and data in the portfolio are merged), Overwrite (data from the file overwrites the existing portfolio data), or Ignore (duplicate rows in the file are skipped and the portfolio data is retained). Download duplicates gives you those rows as a CSV.

• Errors — rows that fail validation are listed with the reason they failed. A row reports at most one problem with its organization number and country, so you fix the actual cause rather than a knock-on error:

  Error	Cause
  Invalid organization number '…'	The organization number cell is empty, or holds something that isn't a number.
  Invalid country '…'	The country cell isn't a two-letter ISO 3166-1 alpha-2 code.
  Invalid organization number '…'. Expected …	The number doesn't match that country's registry format. The message names the format expected.
  Several companies match the organization number …	More than one company holds the number and the Name column didn't settle it. The message lists them. The row is resolved on the Resolve step later in the wizard — see When one number matches several companies.
  Company not found for the organization number …	The number and country are well-formed, but no matching company exists in Strise. This row is resolved later in the wizard: Strise searches its own data by name, and offers what it finds on the Resolve step, or the Create step for a row outside Norway, Sweden, Denmark, Finland and the United Kingdom — see Creating a custom company for an unresolved row.
  Invalid company status '…'	The status cell doesn't match one of the recognized status names.
  Invalid assignee email '…'	An assignee email doesn't match a user on your team.

  The last two apply to a private person row as well, and a private person row can also fail on a missing name or an invalid birth date. Where a message shows a quoted value, that's the cell exactly as your file held it; a cell that was empty is reported without one, as just Invalid organization number, Invalid country or Invalid company status. Download errors gives you the failing rows as a CSV, so you can fix them and replace the file.

  A failing row is skipped on import; the rest of the file goes in regardless, so an error never blocks Upload. The step is there to tell you which rows didn't make it and why. To bring one in, either fix it in your file and replace the file, or — where the row named a company or matched nothing — resolve it on the Resolve step, or create a company for it on the Create step.

• Warnings — rows that are imported, but where something is worth a look. A warning never blocks the upload and never keeps a row out of it; the step is there to tell you what the import decided, not to ask you for anything.

  Warning	Cause
  Name in file (…) does not match the company found (…)	The organization number resolved to exactly one company, and its name disagrees with the Name cell. The number decides which company is imported, so the row still imports.

  The message names both the name you wrote and the company the number resolved to, so you can tell a harmless spelling drift from the wrong number. Download warnings gives you those rows as a CSV; Download errors includes them too, so one fix-and-replace round covers everything the file was flagged for. Re-uploading a row that already imported is safe — it is caught by the duplicate handling above.

Monitoring

The Import step of the upload dialog has an Add uploaded companies to monitoring (or Add uploaded persons to monitoring) checkbox, ticked by default. Untick it to import entities without putting them under monitoring.

Rows uploaded with the Ignored status are never added to monitoring, even when the checkbox is ticked.

A company created from an unresolved row follows this same checkbox rather than the default used when creating a custom company by hand elsewhere in Strise, which monitors it automatically.

After you confirm the upload, entities are imported in the background, so it can take some time before they all appear in your portfolio.