Skip to content

Loss Event

ERM Core captures operational losses to the standard regulators and auditors expect — from a single loss event, through validation and its materiality tier, to each entity’s monthly loss report.

IDPageFor
B3.1Recording a loss event — four dates, Basel event type, near miss; the system-issued event codeReporter, Risk Champion
B3.2Amounts, currencies and FX — gross, recovered, net; original currency; conversion to THBReporter, Entity Risk Manager
B3.3Materiality tiers — computed from the group’s thresholds; routing; restatementsEntity Risk Manager, Executive
B3.4Validation and visibility — Draft → Submitted → Under review → Validated / Rejected / Returned → Closed; Reported-Then-Visible; sensitive eventsEntity Risk Manager
B3.5Loss data set and regulatory watchlist — the period-frozen data set; events nearing a reporting threshold; audit overlapEntity Risk Manager, Compliance
B3.6Monthly loss report and nil return — filing the month; the period freezes on RMC acceptanceEntity Risk Manager, RMC
  1. A reporter records the event with its dates, cause and Basel event type (B3.1), and its amounts in the original currency (B3.2).
  2. The system computes the materiality tier and routes the event (B3.3).
  3. The entity’s own Entity Risk Manager validates or rejects it. Only a validated event becomes visible to the parent (B3.4).
  4. Recoveries and revaluations are added as the position changes; the latest position drives the tier.
  5. The entity files its monthly loss report, or a nil return; the period freezes when the RMC accepts it (B3.6) and feeds the loss data set (B3.5).