Skip to content
Docs

Importing data

A company rarely starts from zero. Historical loss events, existing risk registers, KRI observations and BIA activities are loaded from the standard workbooks. Every row is checked and shown in a validation report before anything is saved, and every imported row is stamped as imported, with who and when.

Who may do it: the Entity Risk Manager, into their own entity; the administrator. The organisation structure and the staff register are loaded through Organisation structure. See Roles and permissions.

What can be imported

Section titled “What can be imported”
DataGoes intoPage
Historical loss eventsthe loss event registerRecording a loss event
Existing risk registersthe RCSA risk register, with controlsRisk register
KRI observationseach KRI’s observationsObservations and breaches
BIA activitiescritical activities and their dependenciesCritical activities
Importing dataDownload the standard workbook for the data type, fill it in and upload it into your own entity. The system checks every row and shows a validation report; nothing is saved yet. If there are errors, fix them and upload again. Commit is possible only with zero errors. Imported rows are stamped as imported, with who and when; scores, tiers, bands and codes are computed or issued by the system.ERRORS: FIX AND UPLOAD AGAINStandard workbookone per data typeUploadinto your own entityValidation reportevery row checkednothing saved yetCommitonly with zero errorsImported rowsstamped as importedwho · whenComputed valuesscores · tiers · bands · codesderived, never importedLEGENDSourceStepSystem checkRecordFix path
Upload, read the validation report, fix and upload again until there are no errors, then commit. Imported rows are stamped; computed values come from the system.

Import a workbook

Section titled “Import a workbook”
  1. Open Import and choose the data type.
  2. Download the standard workbook for that type and fill it in, one row per record.
  3. Upload it. The rows go into the entity you are working in.
  4. Read the validation report: each row is shown as ready or with its error and the reason.
  5. If there are errors, fix them in the workbook and upload it again.
  6. When the report shows no errors, choose Commit.

What the system does on commit

Section titled “What the system does on commit”
  • Stamps every row as imported, with who imported it and when. The stamp stays on the record.
  • Computes what is computed. Inherent and residual scores, tiers and bands, loss materiality tiers, KRI bands and BIA criticality tiers are derived by the system from the imported inputs. The workbooks have no column for them.
  • Issues the codes — CM-RISK-2026-001, LE-2026-0001, KRI-CM-001 — as for any new record.
  • Applies the FX policy to loss amounts in other currencies.
  • Records the import in the audit log.

What the system refuses

Section titled “What the system refuses”
  • Nothing is saved before commit, and commit is refused while the report shows an error.
  • An amount whose rate basis is unknown is refused, as for any loss event (Amounts, currencies and FX).
  • A row for another company is refused: an import goes into your own entity only.
  • A typed score, tier or band is not accepted (Computed, never typed).
Section titled “Related”