| 1-CORE | Qirin X’s back office for institutions with anti-money-laundering duties: KYC CORE, CDD CORE and AGENT CORE under one sign-in |
| Activation | The BCP head’s act that puts a named operator on duty; an operator acts only once activated, and both acts are recorded |
| AERS | AMLO’s electronic reporting system |
| AGENT CORE | 1-CORE’s commission and retention module: calculates upfront and retention for each selling agent and shows it in the Agent Portal |
| Authenticator | An app on the user’s phone that gives the 6-digit code (TOTP) for the second sign-in step |
| Basel event type | One of the seven Level-1 operational-loss types, EL01–EL07, recorded on every loss event |
| BCP Core | Risk Core’s business-continuity module for people and premises, used on every employee’s phone |
| BCP level | Normal · Standby · Activated · Closed: ordered by the BCP head, and every change is pushed to every staff phone |
| BIA | Business impact analysis: the annual analysis of critical activities with MTPD, RTO and RPO; held in ERM Core and read by BCP Core |
| Call tree | Who calls whom in an incident, built from the organisation structure |
| CDD / EDD | Customer Due Diligence / Enhanced CDD |
| CDD CORE | 1-CORE’s officers’ console for customer due diligence |
| Check-in | A staff member’s report during an incident: Safe, Affected or Need help, with an optional location, note and photo |
| Criteria set | The group’s scales for likelihood and for each impact dimension, against which every risk is scored |
| Critical activity | An activity the company cannot leave disrupted beyond its MTPD; recorded in the BIA with RTO, RPO and minimum staff |
| Criticality tier | A critical activity’s tier, computed by the system from the group’s MTPD bands |
| DA Dealer | A digital asset dealer licensed by the SEC |
| Dependency | What a critical activity relies on: people, a site, a system, a supplier or data |
| ERM Core | Risk Core’s ERM module for the risk desk: RCSA, loss events, KRIs, BIA and dashboards |
| Escalation | Notifying the head, then the next level up, about someone who has not reported |
| Exit-Only | A restriction under which the customer can only sell or withdraw |
| Four legs | Deposit, withdraw, buy and sell: the units of restriction and release |
| FundConnext | The fund industry’s central platform, which sends customer, account and statement files |
| Group advisory | A notice from the parent company shown beside a subsidiary’s own BCP level; it never changes that level and never pushes to its staff |
| Index, not master | CDD CORE keeps the results of CDD work; customer particulars stay in the source system |
| Inherent / residual risk | A risk’s score before controls, and after the effect of its controls; residual can never be higher than inherent |
| KRI | Key risk indicator, with green / amber / red threshold bands |
| KYC CORE | 1-CORE’s applicant app for online account opening |
| Loss Event | An operational loss, recorded against a Basel event type |
| Maker / Checker / Approver | The person who proposes, the person who signs, and senior approval where required |
| Materiality tier | A loss event’s tier, assigned by the system from the group’s thresholds and used to route it |
| MTPD | Maximum tolerable period of disruption: how long an activity can be down before the impact becomes unacceptable |
| Name pair | A customer name and a list name whose similarity reaches the threshold |
| Nil return | An entity’s formal monthly filing that it had no loss events, so silence is never read as a clean month |
| Operator | A named person to whom the BCP head delegates the right to operate BCP Core; acts only once activated and cannot edit the staff list |
| PEP | Politically exposed person |
| Platform operator | QX as the operator of the installation: accounts, list loads and platform-wide values |
| Public window | BCP Core’s service for the general public; collects no personal data |
| RCSA | Risk & Control Self-Assessment: each company assesses its risks and controls each cycle |
| Re-KYC | Periodic customer review |
| Remember this device | A sign-in choice that skips the authenticator code on that device for the number of days the client sets |
| Report-up | The only link between companies in a group: each subsidiary sends upward what it has validated or approved; the parent reads it and cannot change it |
| Retain-until | The date a record’s retention period ends |
| Risk Champion | The person in a team who drafts the team’s risks and RCSA filing, and reports loss events |
| Risk Core | QX’s risk platform with two modules, ERM Core and BCP Core, on one shared core; each company’s data is kept separate |
| RLS | Row-level security: the database rule that limits which rows each user can read |
| Roles panel | The read-only view where a user sees every role they hold, where it is granted and since when |
| RPO | Recovery point objective: how much data, measured in time, an activity can afford to lose |
| RTO | Recovery time objective: how fast an activity must be running again |
| SA | Selling agent: the individual who sells, employee or freelance, whose earnings AGENT CORE calculates |
| Single point of failure (SPOF) | A dependency with no alternative; a SPOF with no workaround creates an action item |
| STR | Suspicious transaction report (AMLO form 1-03) |
| Subsidiary-Independence | A parent may read a subsidiary’s records but never create, edit, approve or close them |
| Team room | The group chat for a team, and for the incident, where staff report in when the plan is activated |
| TMS | Transaction Monitoring |
| TRADE CORE | Qirin X’s trading and settlement platform for licensed digital-asset businesses, which exchanges data with CDD CORE. See TRADE CORE |
| Upfront / Retention | Upfront is earned once, when a subscription or switch-in is allotted; Retention (trailer) is earned every day the customer holds units |
| Work status | A staff member’s working state for the day: In office, Working from home, Unable to work or On leave |