1) Purpose and scope

• Report catalog and schedule
• Data formats and schemas
• validation and quality control rules;
• transmission and acknowledgement channels;
• roles and RACI, artifact log, and retention.

2) Roles and RACI

Owner: Head of Compliance - approves versions, priorities (A).
Schema Steward (DWH Lead) - support for schemas and mappings (R).
Producers: AML/RG/Payments/Game Ops - data sources (R).
QA/DQ: Data Quality Team - validations, test kits (R).
Legal: interpretation of norms, approval of changes (C).
Security/DPO: PII/Aliasing, Delivery Channels (C).
Reporting Ops: upload, sign, send, confirm (R).

3) Report catalog (classes)

1. Game reports - bets/wins/balances/sessions, RTP, honesty.
2. Financial - deposit/withdrawal, deductions, taxes, GGR/NGR, chargebacks.
3. AML/CFT - suspicious transactions, PEP/sanctions, risk aggregates.
4. Responsible play (RG) - self-exclusions, limits, interventions.
5. Incident - availability, leaks, notifications and deadlines.
6. Marketing/affiliates - sources of traffic, advertising restrictions (if required by license).
7. Technical - uptime, RNG versions, build/configuration hashes, audit log.

Each report is described by a card (§ 4).

4) Report card (template)

ID: REP- <code >/Version: v <MAJOR. MINOR >/Owner: <role>
Jurisdiction/License: <e.g. MT/MGA B2C, GB/UKGC, SE/Spelinspektionen>

5) Data formats: standards

5. 1 CSV/TSV

Encoding: UTF-8 without BOM.
Delimiter: ',' (CSV), or '\t '(TSV).
Escape '' around delimited/line feed fields.
Decimal separator: '.'; Date/Time - ISO-8601 'YYYY-MM-DDThh: mm: ssZ'.

Example (CSV, rates):

report_date,player_id_hash,game_code,currency,stake,win,round_id,session_id,geo,ts_utc

2025-10-31,4b1c...a9,EGT_40SUPERC,EUR,1. 00,0. 00,rd_789,ss_123,DE,2025-10-31T15: 02:11Z

5. 2 XML

Namespace fixed; XSD validation.
Null values as empty element with'nil = "true" 'attribute.

5. 3 JSON

JSON Lines for large offloads; JSON Schema v2020-12.
Timezones - UTC; sums - decimal with string representation.

5. 4 XLSX

Used only if prescribed by the regulator. The sheet template and column names are fixed.

6) Core dictionaries

6. 1 Common fields

'report _ date '(DATE, UTC) - key date (aggregation window).
'operator _ id '(STRING) - ID of the license/operator.
'player _ id _ hash '(STRING) - hashed player ID (salt per jurisdiction).
'geo '(STRING, ISO-3166-1 alpha-2) is the country of the player/session.
`currency` (STRING, ISO-4217).
'ts _ utc '(TIMESTAMP) is the moment of the event.

6. 2 Gaming

`game_code`, `provider_code`, `round_id`, `session_id`, `stake`, `win`, `bonus_flag`, `rtn_balance_before/after`, `rake`.

6. 3 Payments

`txn_id`, `method_code`, `psp_id`, `amount`, `fee`, `status`, `decline_reason`, `kya_level`, `chargeback_flag`.

6. 4 AML/RG

`risk_score`, `peps_hit`, `sanctions_hit`, `sar_id`, `rg_limit_type`, `rg_breach`, `self_exclusion`.

7) Jurisdictional features (examples)

MT (MGA): monthly gaming aggregates: bets/winnings/RTP by title and provider; CSV/XLSX format currency code, split into "cash/bonus."
GB (UKGC): reports on RG (self-exclusion), marketing (channel compliance), incident notifications; CSV/XML preference, portal.
NL (KSA): detailed game events (often JSON/XML), strict time synchronization and fields for CRUKS (self-exclusion register).
SE (Spelinspektionen): Spelpaus integration, reports on RG interventions; CSV format, SFTP.
DE (GlüStV): rate/deposit limits and compliance, RG events; locale DE, but the numbers are '.'.
ES/PT/IT: monthly GGR aggregates/taxes/active players, XLSX/CSV; separate report on bonuses and advertising.

> The register for all markets is kept in Git/Confluence; any changes are recorded by the changelog.

8) Transmission channels and security

Regulator portals: downloading a file, obtaining a registry ID.
API: OAuth2/MTLS, quota, retray with idempotency.
SFTP: encryption in transit, PGP file signature, atomic calculation ('.part' → '.csv').
Mail (secure): only on demand, encrypted/signed.

Artifacts: receipts/receipt ID, checksums (SHA256), send logs.

9) Data quality control (DQ) and validation

9. 1 Check layers

1. Schema validation: types, mandatory, value domains.
2. Business rules: balanced identities ('opening + deposit − within − bet + win = closing ± adj'), valid RTP ranges.
3. Cross-source reconciliation: PSP vs. wallet vs. GL (general ledger).
4. Freshness: SLA window display updates; late events are marked and loaded.
5. Uniqueness: 'txn _ id', 'round _ id' are unique within the window.

9. 2 Model rules

`stake ≥ 0`, `win ≥ 0`; when 'bonus _ flag = 1' - a separate bucket.
`currency ∈ ISO-4217`; `geo ∈ ISO-3166-1`.
'ts _ utc'inside the report window; time zone - UTC only.
For returns, separate records with'amount <0'and'status = REFUND'.

10) Liniage and circuit versioning

Lineage: for each field - source (table/column), transformation (SQL/udf), owner.
Semantic Versioning:
MAJOR - incompatible changes (deleting/renaming fields).
MINOR - Add optional fields.
PATCH - Description/Validation Corrections.
Deviation Policy: double unloading period (old + new format) ≥ 1 reporting cycle.
Change Log: date, author, reason, jurisdictions affected.

11) Aliasing and PII

Hashing 'player _ id' with salt on jurisdiction; salt is stored in a secret storage.
Masking e-mail/phone, if required.
Access Profiles: PII only sees DPOs/Commissioners; export to portals - already with hashes.

12) Mapping Examples (DWH → Report)

Game unit (day, title, currency):

sql

SELECT

DATE_TRUNC('day', ts_utc) AS report_date,

game_code,

currency,

SUM(stake) AS stake_sum,

SUM(win) AS win_sum,

SAFE_DIVIDE(SUM(win), NULLIF(SUM(stake),0)) AS rtp

FROM fact_game_rounds

WHERE ts_utc >=: from AND ts_utc <:to

GROUP BY 1,2,3;

Payments (deposits/withdrawals/fees):

sql

SELECT

DATE_TRUNC('day', ts_utc) AS report_date,

method_code, psp_id, currency,

SUM(CASE WHEN type='DEPOSIT' THEN amount ELSE 0 END) AS deposits,

SUM(CASE WHEN type='WITHDRAWAL' THEN amount ELSE 0 END) AS withdrawals,

SUM(fee) AS fees

FROM fact_payments

WHERE ts_utc BETWEEN: from AND:to

GROUP BY 1,2,3,4;

13) Sample files

13. 1 Gaming Unit (CSV)

report_date,operator_id,game_code,currency,stake_sum,win_sum,rtp

2025-10-31,OP123,NET_STARBURST,EUR,125000. 50,119800. 00,0. 9585

13. 2 RG Events (JSON Lines)

{"report_date": "2025-10-31","player_id_hash":"b93e...","rg_event":"SELF_EXCLUSION","duration_days":180,"ts_utc":"2025-10-31T09:11:02Z"}

{"report_date": "2025-10-31","player_id_hash":"c01a...","rg_event":"LIMIT_BREACH","limit_type":"LOSS_DAILY","amount":"200. 00","ts_utc":"2025-10-31T13:45:22Z"}

13. 3 AML aggregate (XML, fragment)

xml

14) Operational turnover process

1. Window preparation: freeze, calculation of aggregates, reloading of late events.
2. Validations: schema + business rules + reconciliation.
3. File generation: schema version in name ('REP-GB-GAME-v1. 3_2025-10-31. csv`).
4. Signature/hash: PGP + SHA256.
5. Delivery: portal/API/SFTP; reception log (ID/receipt).
6. Archiving: original + signature + receipt in the report store.
7. Monitoring: dashboard "Regulatory Reporting" - status "ready/sent/accepted/error."
8. Retro: error/deviation analysis, CAPA.

15) Checklists

Before sending

[] Window and timezone date confirmed.
[] All validations are green, reported amounts are reconciled with GL/PSP.
[] Schema version matches registry.
[] PII masked/aliased.
[] File signed/checked, hash committed.
[] The regulator's contact is up-to-date (the portal is available).

After sending

[] Receipt/ID received, archived.
[] Status updated in dashboard.
[] Update plan in case of validator error is agreed.

16) Metrics and SLO

Timeliness:% of reports submitted on time.
First-Try Acceptance:% accepted without corrections.
DQ Score: percentage of entries with no errors (schema/business).
Reconciliation Gap: absolute/percentage discrepancy with GL/PSP.
Lead Time to Report: the time from closing the window to submitting.
Change Failure Rate (formats): share of schema releases with rollbacks.

17) Governance

Quarterly review of claims by jurisdiction; unscheduled - during regulator updates.
RFC for schema changes: impact analysis, interoperability, sandbox pilot.
Double unloading at MAJOR ≥ 1 cycle.
Training teams on releases, updating playbooks and FAQs.

18) Frequent mistakes and how to avoid them

Incorrect timezone: always consolidate in UTC, store the locale separately.
Rounding: use decimal, uniform bank rounding rules.
Inconsistency of identifiers: single registers' game _ code ',' method _ code ',' psp _ id '.
Localization of numbers/dates: only ISO-8601 and period as decimal separator.
PII in clear: checking masks in pre-commit and CI.

19) Embedding in the ecosystem

Communication with sections: Compliance dashboard, Notifications and deadlines, Incident playbooks, Crisis management, Audit logs.
In the incident bot: command '/report <jurisdiction> <report_id>' - get the scheme and deadlines.
Exporting snapshots on S1/S2 is added to the artifact package.

20) Implementation plan (30 days)

Week 1

1. Inventory of all license regulatory reports.
2. Create cards (§ 4) and code dictionaries.
3. Approval of transmission formats and channels.

Week 2
4. Building DWH and lineage showcases; primary validations.
5. Generation of pilot files (one market/class).
6. Configuring signature/hashes and archive.

Week 3
7. Integration with the sandbox portal/API/SFTP.
8. Dashboard statuses and alerts by deadlines.
9. Reporting Ops training and checklists.

Week 4
10. Pilot delivery of 2-3 reports; collection of feedback.
11. CAPA for DQ/validations; adjustments of schemes.
12. Release v1. 0; revision schedule and a single deadline calendar.

Related sections:
Notices of Violations and Reporting Deadlines
Compliance dashboard and monitoring
Incident playbooks and scripts
Crisis management and communications
Business Continuity Plan (BCP )/DRP
Transaction Audit Logs