Daily work
The kundetiltak wizard
Kundetiltak ("customer measures", the onboarding cycle) is the wizard that takes a newly created company from prospect to classified customer in five steps: pick the services, read the screening, send the KYC form, assess the answers, and conclude with a risk class or a rejection. The wizard freezes the risk model when it starts, saves everything automatically, and reopens where you stopped.
Every step has one gate — what has to be in place before you can move on. The gate does not physically stop you: «Neste» is never disabled, and a missing gate appears as a blocker list.
- Step 1 · Tjenester ("services") — pick the service areas your firm will provide, and set the reporting-duty flag. The gate onwards is at least one service.
- Step 2 · Screening — read the lookups against Stø (the external screening and monitoring provider) and BRREG. The step is read-only and has no gate.
- Step 3 · Utsendelse ("dispatch") — prepare the beneficial owners, the questions and the context, and send the KYC form to the recipient. The gate onwards is that the form has been sent.
- Step 4 · Vurdering ("assessment") — assess the customer's answers, the beneficial owners and the signing, and answer the internal questions. The gate onwards is that the assessment is complete.
- Step 5 · Konklusjon ("conclusion") — settle the class, collect the approvals, and choose «Opprett kunde» ("create customer") or «Avslå» ("reject"). The server rechecks every gate when you conclude.
Every step in detail — the cards, the fields, the messages and the verdicts — is covered in The five steps. This page is about the cycle around them: how you start one, how the frame behaves, and how you move an open cycle to a newer model version.
Entry: the banner on the company card
The wizard has no menu entry. You get in from the banner on the company card, and the banner appears only when the feature is enabled for the instance and the company's company template has «Skal risikovurderes?» ("is it to be risk assessed?").
- Not started: «Kundetiltak ikke gjennomført» ("customer measures not carried out") with the button «Start kundetiltak».
- In progress: «Kundetiltak under arbeid» ("customer measures in progress") with the step badge «X/5 steg», a progress bar and the button «Fortsett wizard» ("continue the wizard").
- Unhandled alerts: an already classified company with open alerts gets a red alert line instead, carrying the provisional recalculated class and the button «Til AML-risiko», which opens the company card's AML-risiko tab. Alerts are handled there or in an operational cycle — see Risk classification.
- Both kundetiltak variants show «Frist <dato> (N dager)» ("deadline <date>"), and the colour turns from orange to red when seven days or fewer are left. The deadline is the company's creation date plus 30 days, and can be configured per instance.
- «Skjul» ("hide") hides the banner for the rest of the browser session, and works per state: hiding the kundetiltak variant does not hide the alert variant. The kundetiltak banner disappears permanently once a class is recorded, the risk value is set, or a rejection has been concluded.
- The page itself lives at
/company/{id}/onboarding-cycle(«Kundetiltak»), is hidden from the menus, and is reached from the banner. It answers "not found" if the company is missing, is private to someone else, or its company template is not to be risk assessed. - «Start kundetiltak» on the start screen creates the cycle and freezes the published risk model version in force at that moment. A second attempt answers «Selskapet har allerede et aktivt kundetiltak» ("the company already has an active kundetiltak").
- Deep links: the address carries
?cycle=…&step=services|screening|dispatch|assessment|conclusionand updates quietly as you navigate. Browser back and forward restore the step, and a deep link to a step you have not reached is rounded down to the furthest one you have.
The wizard frame
The top and bottom bars are sticky and stay put on all five steps while the content scrolls, so the step title and the action row are always visible.
- The top bar: the step title, the trigger badge (the wizard is always ONB), the company line «<Firma> • Steg N av 5: <tittel>», the autosave indicator, «Avbryt kundetiltak» ("cancel the customer measures") and «Tilbake til firmakort» ("back to the company card").
- The autosave indicator is one field for the whole wizard: «Lagret automatisk» ("saved automatically") blinks for 2.5 seconds after each save, while a red «Kunne ikke lagre» ("could not save") stays up until a save succeeds.
- «Avbryt kundetiltak» exists only while the cycle is open, and is confirmed: «Avbryte kundetiltaket? Syklusen avbrytes uten konklusjon og lagrede utkast forkastes.» A pending approval request is cancelled automatically.
- The step rail: five numbered circles on a connecting line — complete is a green check, current is blue. It is clickable backwards only. The position is saved, so the wizard reopens where you stopped.
- The bottom bar: «Forrige» ("previous"), on steps 2–4 the red shortcut «Avslå prospekt» ("reject the prospect", which jumps to Konklusjon with Avslå preselected), the score counter and «Neste».
- The score counter shows the «AML-konfig vN» chip for the frozen model version, a class pill with a shield if the company already has a recorded class, and the live pill «<poeng> poeng | <Foreløpig klasse> FORELØPIG» ("points | provisional class") without a shield — the shield is reserved for a recorded class.
- «Foreløpig poenggrunnlag» ("provisional score basis") opens on hover or keyboard focus on the counter. The factor lines («Faktor · Utfall +N») are grouped under the model's categories — Kunde, Screening, Tjeneste, Transaksjon and Annet — with the server's subtotal per group. Lines from the customer's form answers carry the badge «fra skjema: sp. N» ("from the form: question N"), and a group whose total is not the sum of its rows carries the badge maks, because Transaksjon and Annet aggregate with MAX. «Manuell justering» ("manual adjustment") sits outside the groups with its own subtotal.
- A soft block: click «Neste» with an incomplete step and a blocker list opens in two colours — orange for what you can act on now, blue for what is waiting on the customer. Step 1 says «Velg minst én tjeneste …» ("pick at least one service"), step 2 has no block, step 3 says «Send KYC-skjemaet til mottakeren.» ("send the KYC form to the recipient"), step 4 shows the whole completeness list, and step 5 is checked by the server as you conclude.
- Autosave everywhere: every change — from service picks and context notes to assessments, adjustment and rejection fields — is written after about half a second. There is no save button.
The frozen model version. The whole cycle is scored against the model version frozen when it started, and the chip «AML-konfig vN» names it. If someone publishes a newer risk model while the cycle is open, the cycle is unaffected until you update it yourself — see Update to the newest model version.
Update to the newest model version
- When a newer model version has been published than the one the cycle was frozen against, the score counter shows the button «Oppdater til vX» ("update to vX") beside the «AML-konfig vN» chip. The same button sits in the top line of the operational «Vurder syklusen» surface.
- The click is confirmed: «Kundetiltaket scores i dag mot AML-konfig vN. Oppdateringen fryser syklusen mot vX og beregner poeng, foreslått klasse og kontrolltiltak på nytt. Byttet loggføres.» Confirm and the cycle is re-frozen against the newest published model, and points, proposed class, four-eyes requirement and conditional steps are recalculated at once.
- The switch is logged and appears in the company card's history card as the row «Modellversjon oppdatert vN → vX · dato · av hvem» ("model version updated · date · by whom").
- An update is refused while an approval request is pending, on closed cycles, and when the cycle is already on the newest version. The server's message appears next to the button.
- After the update, the «Betingede steg» card in step 4 is reloaded automatically, so steps the new model derives — or no longer derives — appear at once. Update from another step and the card is fetched fresh when you open step 4.