Ready answers to the most frequent GLOSS how-to questions. Check here before escalating to L2.
Instruction search screen → key by trade reference or ISIN + settlement date. The status history tab shows every sese.024 update received from the CSD with timestamps; the latest reason code tells you why an instruction is pending or failing (see the settlement runbook for code meanings).
Reconciliation module → statement inventory screen: expected vs received MT535/MT536 per custodian and business date. Green = loaded, amber = partial, red = missing. No need to read batch logs for this.
Almost always the position basis: screens default to the settled view, most client reports run on the traded view (or the reverse depending on the template). Check the view selector and the report definition before raising a data incident.
Daily LMFP/SEFP penalties are computed by the CSD and imported into GLOSS; the penalties screen shows the detail per instruction. The monthly reconciliation and the appeals process are described in the settlement runbook. Documentation: wiki page "CSDR penalties in GLOSS".
Ex-date: from this date the buyer trades without the right. Record date: positions at close of this date define entitlements. Payment date: cash/securities move. GLOSS calculates entitlements on the settled position at record date — pending trades over the record date generate market claims.
Raise a "Data Extraction & Reporting" request with the checklist from the extraction guide (perimeter, position basis, valuation, format, delivery, frequency). Recurring manual extractions should be converted to scheduled reports.
Raise an "Access & Security" request with manager approval, the role profile, market scope and start date. See the access management page — "same as colleague" is always mapped to a named profile.
Screen name, exact action, time, error code (GL-xxxx) if any, whether colleagues are affected, and your site. This halves triage time. Do not kill the process before support has checked for record locks.
UAT is refreshed from production (anonymised) the first weekend of each month. Refresh freeze requests must be raised one week ahead. Training is refreshed monthly with fictitious data.
/logs/gloss/batch/ per step and business date, kept 90 days. The batch monitor shows the last runs with per-step status — check the monitor before requesting a log extraction.
L1 service desk: triage, known errors, access requests, report reruns. L2 GLOSS application support: configuration, data corrections, replays. L3 SS&C: product defects, via a case with environment, version and reproduction steps.