Decree No. 10 / 2019 Coll.
Ordinance on reporting in gambling
Valid
Effective from 01.06.2019
Zobrazeno prvních 200 z celkem 3476 ustanovení tohoto předpisu.
Zobrazit celý předpis →
Pro stažení celého znění použijte tlačítko Stáhnout výše.
10
DECLARATION
of 15 January 2019
on reporting in gambling
The Ministry of Finance provides, pursuant to § 133 (1) (a) of Act No. 186 / 2016 Coll., on gambling:
GENERAL PROVISIONS
BASIC PROVISIONS
Subject matter
This decree regulates the manner, content and deadline for the transmission of data by the operator to the supervisory authorities under the Gaming Act, the scope of data transferred and other technical parameters of reporting, in the form of:
(a) daily game reporting in the case of live games other than as an internet game;
(b) a daily game entry in the case of bingo operated differently than as an internet game;
(c) remote access in the case of gambling other than those referred to in (a) and (b).
GENERAL REQUIREMENTS FOR AUTOMATISED OUTPUT
Registration
(1) The operator shall notify the surveillance authority of the data necessary for the technical security of the provision of automated output so that such communication is made to the surveillance authority not later than 30 days before the date on which the automated output is to be provided for the first time. The operator shall also indicate in the communication, in addition to the general particulars of the submission:
(a) the operator's qualified certificate for the recognised electronic seal used in accordance with the Annex to this Regulation for sealing the file;
(b) the operator's public key certificate used in accordance with the Annex to this Decree for the purposes of:
1. file encryption,
2. Authentication for encrypted authentication,
(c) part of the address of the operator's website used in accordance with the annex to this decree to compile the address used for:
1. the provision of automated output,
2. sending a confirmation package where the automated output provided is formally correct; and
3. sending a confirmation package where the automated output provided is not formally correct;
(d) other information necessary for technical security of the provision of automated output by the operator in accordance with the Annex to this Decree.
(2) The supervising authority shall notify the operator of:
(a) a qualified certificate from the supervising authority for a qualified electronic seal used in accordance with the Annex to this Regulation for sealing the file;
(b) the public key certificate of the supervisory authority used in accordance with the Annex to this Decree for the purposes of:
1. file encryption,
2. Authentication for encrypted authentication,
(c) the address of the website of the supervisory authority used in accordance with the Annex to this Decision for the provision of a confirmation package; and
(d) other information necessary for technical security of the provision of automated output by the supervisory authority in accordance with the Annex to this Decree.
(3) The operator shall notify the supervisory authority of the change in the data referred to in paragraph 1 (a) to (d) and the date from which the modified data are to be used for the provision of automated output, so that such communication takes place to that authority no later than 5 working days before that date.
(4) The supervisory authority shall notify the operator of the change in the data referred to in paragraph 2 and the date from which the modified data shall be used when providing the automated output, so that such communication takes place not later than 5 working days before that date.
Method of providing automated output
(1) The automated output is provided in accordance with the annex to this decree.
(2) The supervisory authority shall access the website used to provide automated output no later than 7 days from the date on which the automated output is to be provided. This does not apply in the event of a natural disaster or other emergency.
(3) The supervisory authority shall establish and transmit to the operator a confirmation package containing information on whether the automated output provided is formally correct. The supervisory authority shall not take into account the automated output provided which is not formally correct.
(4) An operator shall provide an individual automated output until it has been transmitted to the supervising authority a confirmation package concerning that automated output.
(5) Paragraphs 1 to 4 shall apply mutatis mutandis to the re-provided automated output in which errors have been corrected.
(6) For the purpose of providing automated output, automated output shall be formally correct if:
(a) is in the prescribed format and structure;
(b) the operator's recognised electronic seal is sealed;
(c) it is encrypted using the public key of the supervisory authority; and
(d) does not contain game data and financial data which clearly do not belong to it.
Method of correcting the formal errors provided by the automated output
(1) An operator shall correct the formal errors expressed in the validation package concerning the automatic output provided, which is not formally correct, within 2 working days of the date on which the validation package was transmitted to it.
(2) The formal errors in the automated output are corrected by the operator reproviding the automated output in which to remove those errors.
(3) If the first automated output provided is formally correct, it shall be viewed as if it had been formally correct when provided.
Method of correcting material errors provided by automated output
(1) An operator may, in cases of due regard, correct such errors within 14 days of the date on which it formally provided the correct automated output containing non-formal errors.
(2) Non-formal errors in the automated output shall be corrected by the operator reproviding the automated output in which to remove those errors and by communicating to the supervisory authority:
(a) data to determine the correct automated output; and
(b) the reason for the repair of the automated output.
(3) The time limit for loading the address used to provide the automated output shall begin to run on the date on which the supervisory authority receives the notification referred to in paragraph 2. The date on which the communication was made to the supervising authority or the date on which the automated output was actually provided shall be deemed to be the date on which the communication was made to the supervising authority, with the decision being given at a later date.
(4) The corrected automated output is also not formally correct if, as a result of its acceptance, one of the previously provided automated outputs would be formally no longer correct. The operator shall indicate in the communication referred to in paragraph 2 the data to be used to determine this previously provided automated output and correct the formal errors that would arise in the event of receiving the corrected automated output in accordance with the first sentence.
INTERNAL ACCESS
Form of remote access
Where an operator is obliged to provide and transmit remote access to the supervisory authorities, it shall provide remote access in the form of an automated output.
Requirements for remote access
(1) When providing remote access, game data and financial data shall be provided in a manner, to the extent, format and structure specified in the Annex to this Decree.
(2) Remote access shall be provided by the operator three times per calendar day for a period of 8 hours starting at:
(a) 00: 00,
(b) 08: 00, and
(c) 4: 00.
(3) If, during the period referred to in paragraph 2 (a), the following occurs:
(a) introduction of summer time, the period shall be seven hours long; and
(b) end of summer time, this period shall be of nine hours.
(4) An operator shall provide remote access no later than 8 hours after the end of the period for which remote access is provided.
DAY-DAY HERO REPORTING AND DAY-DAY HERO NOTE
Form of daily game reporting and daily game recording
The operator provides daily game reporting and daily game writing in the form of an automated output.
Requirements for the provision of daily game reporting
(1) In the daily game reporting, the game and financial data shall be provided in a manner, to the extent, whether basic or extended, the format and structure as specified in the Annex to this Decree.
(2) An operator shall provide game and financial data to at least the basic extent in daily reporting. Unless otherwise specified in the Annex to this Order, the game and financial data shall constitute the basic range of daily reporting.
(3) An operator may provide game and financial data in daily reporting to an extended extent, which, in addition to game and financial data in the basic range of daily reporting, also constitute game and financial data on each live game game game that is not operated as an internet game or as a tournament.
Requirements for the provision of daily game registration
In the daily game log, the game and financial data shall be provided in a manner, to the extent, format and structure specified in the annex to this decree.
Operating day
(1) Daily game reporting and daily game writing contain data for each operating day.
(2) For the purposes of the provision of automated output, the operating day means the time period during which the operator operates in the gambling area, starting in a given calendar day and defined by:
(a) operating hours; or
(b) by any other appropriate means not exceeding 24 hours, in the case of continuous operation.
(3) Every moment of operation falls within just one operating day.
(4) In the daily game reporting and daily game recording the operator for the operating day started in
(a) the first calendar day of the gambling tax period shall indicate all the data from which the movement of value chips and cash in connection with the operation of casino games and the course of the game and the movement of cash in connection with the operation of bingo not operating as an internet game on that calendar day is evident, even if such data would otherwise belong to the daily reporting or daily entry for the previous operating day; and
(b) the last calendar day of the gambling tax period shall indicate only those data showing the movement of value chips and cash in connection with the operation of casino games and the course of the game and the movement of cash in connection with the operation of bingo not operating as an internet game on that calendar day.
FINAL PROVISIONS
Notification
This Decree was notified in accordance with Directive (EU) 2015 / 1535 of the European Parliament and of the Council of 9 September 2015 on the procedure for the provision of information in the field of technical and information society services, as amended.
Efficacy
This Regulation shall enter into force on 1 June 2019, with the exception of Article 2, which shall take effect on 1 April 2019.
Minister of Finance:
JUDr. Schiller, Ph.D., v. r.
Annex to Decree No 10 / 2019 Coll.
Automated output
Data package containing automated output
Data package name
I. Name of data package for remote access
The data package containing the automated remote access output has a name in the form of:
< Operator ID > - < Model > - < Reporting period > - < Game type > - < Data package version >
The individual parts of the data package name are separated by a dash (character with decadic code 45).
II. Name of the data package for daily game reporting and daily game writing
A data package containing an automated output for daily game reporting or daily game writing has a name in the form of:
< Operator ID > - < Model > - < Reporting period > - < Game type > - < Casino > - < Data package version >
The individual parts of the data package name are separated by a dash (character with decadic code 45).
III. Content of individual parts of the data package name
| Část názvu datového balíčku | Obsah části názvu datového balíčku |
|---|---|
| <ID Provozovatele> | Identifikace provozovatele poskytujícího datový balíček Identifikační číslo provozovatele, nebo, nebylo-li identifikační číslo provozovateli přiděleno, vlastní číslo provozovatele, jež bylo provozovateli přiděleno v souvislosti s vydáním základního povolení. |
| <Model> | Datový model Jednopísmenné označení datového modelu pro automatizovaný výstup. Uvede se: M - denní herní výkaznictví nebo denní herní zápis. V - vzdálený přístup. |
| <Vykazované období> | Označení vykazovaného období U datového balíčku pro vzdálený přístup se uvede: Určení kalendářního dne a hodiny počátku vykazovaného období, za které datový balíček obsahuje data, ve formátu RRRRMMDDHH, kde: RRRR je čtyřciferné označení kalendářního roku. MM je dvouciferné označení kalendářního měsíce (01 až 12). DD je dvouciferné označení dne v měsíci (01 až 31). HH je dvouciferné označení první hodiny vykazovaného období, za které datový balíček obsahuje data (00, 08 nebo 16). U datového balíčku pro denní herní výkaznictví nebo denní herní zápis se uvede: Určení kalendářního měsíce, ze kterého datový balíček obsahuje data, ve formátu RRRRMM, kde: RRRR je čtyřciferné označení kalendářního roku. MM je dvouciferné označení kalendářního měsíce (01 až 12). |
| <Druh hry> | Druh Jednopísmenné označení druhu Uvede se: L - K - kursová sázka. R - totalizátorová hra. B - bingo. T - Z - živá hra. |
| < | Jedinečný identifikátor Část položky IDMisto za pomlčkou (identifikátor |
| <Verze datového balíčku> | Dvouciferné číslo verze datového balíčku Číslo verze datového balíčku tvoří souvislou číselnou řadu. Jednociferné číslo verze se zleva doplní nulou. Při prvním poskytnutí datového balíčku s automatizovaným výstupem má číslo jeho verze hodnotu 01. Při každém opětovném poskytnutí datového balíčku s tímto automatizovaným výstupem se číslo verze zvýší. Číslo verze datového balíčku se nesmí opakovat mezi jednotlivými datovými balíčky, jejichž název má stejné ostatní části. |
Requirements for data files constituting the data package
I. General requirements for the data file
The data file has a csv format with the following characteristics:
1. UTF-8 coding according to RFC 3629 is used.
2. The lines are separated by a pair of CR characters (decadic code character 13) and LF (decadic code character 10).
3. The data file contains metadata on the first line, header on the second line and other rows of individual records so that there is one record on each line.
4. An empty data file, which is a data file with no records, contains only metadata and header.
5. The line with metadata has a cross sign at the first position (character with decadic code 35) followed by its own data file metadata. The actual metadata of the data file are composed of the following items in that order, separated by a semicolon character (character with decadic code 59):
| Obsah položky metadat | Datový typ položky metadat |
|---|---|
| Název datového balíčku | Text |
| Název datového souboru | Text |
| Datum a čas vytvoření datového souboru | Datum a čas |
| Verze rozhraní Uvede se verze rozhraní automatizovaného výstupu. | Text |
6. File header and record are made up of items that are separated from each other by a semicolon symbol (character with decadic code 59). Items are arranged in the order specified in the specification of individual data files.
7. The header item contains the machine name of the item according to the specification of the individual data files.
8. The entry item contains the item value for the entry.
9. The item containing the semicolon character (character with decadic code 59) shall be supplemented from left and right by the quotation mark (character with decadic code 34). The use of the LF character (decadic code character 10), the CR character (decadic code character 13) and the quotation character (decadic code character 34) within the item values is not allowed.
10. Unless expressly stated otherwise, each entry must have a value. The entry item without value (NULL) shall be entered as an empty string.
11. Unless explicitly stated otherwise, the previously provided alert referred to by reference link shall not be included again in the automated output data package for another period. Such a record shall be viewed as being shown in an automated output.
12. The currency code shall always be entered in the form of the three-letter alphabetical currency code according to ISO 4217: 2015, even if it is to be included in the item in which the additional data are also entered.
II. Data types used in data files
| Název | Upřesnění |
|---|---|
| Celé číslo | Celé číslo v rozsahu -2 147 483 648 až 2 147 483 647. Oddělovače řádů se nepoužívají. V případě kladného čísla se znaménko neuvádí. V případě záporného čísla se uvádí znaménko minus (znak s dekadickým kódem 45). Číslo se zapisuje v desítkové soustavě tak, že každá platná číslice tvoří samostatný znak (znaky s dekadickým kódem 48 - 57). Úvodní nuly se neuvádějí. |
| Desetinné číslo | Desetinné číslo v rozsahu 3,4x10-38 až 3,4x1038. Pro desetinná čísla se použijí pravidla pro celá čísla obdobně. Desetinným oddělovačem je znak čárky (znak s dekadickým kódem 44). Nejvyšší počet desetinných míst je 2, není-li dále uvedeno jinak. |
| Binární hodnota | Číslice 0 a 1 (znaky s dekadickým kódem 48 a 49). |
| Text | Řetězec znaků v českém jazyce za použití latinky, není-li výslovně uvedeno jinak. Maximální délka řetězce může být v definici položky omezena. Není-li výslovně uvedeno jinak, nedoplňuje se kratší řetězec do maximální délky. |
| Datum a čas | Datum a čas spolu s uvedením časového pásma strukturované podle standardu RFC 3339. Datum se od času vždy odděluje znakem T a čas se uvede s přesností na desetiny sekund. |
| Datum | Datum strukturované podle standardu RFC 3339. |
| Identifikátor | Řetězec znaků obsahující pouze číslice 0 až 9 (znaky s dekadickým kódem 48 - 57), velká písmena bez diakritiky (znaky s dekadickým kódem 65 - 90), malá písmena bez diakritiky (znaky s dekadickým kódem 97 - 122), pomlčku (znak s dekadickým kódem 45) nebo podtržítko (znak s dekadickým kódem 95). Pokud se identifikátor člení na části, oddělují se tyto části od sebe pomlčkou (znak s dekadickým kódem 45). Řetězcem určeným provozovatelem se pro účely definice položky s datovým typem identifikátor rozumí řetězec znaků o délce nejméně jednoho znaku, jehož obsah určí provozovatel v souladu s ostatními požadavky na danou položku záznamu. Maximální celková délka řetězce znaků může být v definici položky omezena. Není-li výslovně uvedeno jinak, nedoplňuje se kratší řetězec do maximální délky. Nejsou-li pro položku záznamu s datovým typem identifikátor stanoveny jiné požadavky na jedinečnost, musí hodnota této položky jednoznačným způsobem identifikovat záznam, kdykoliv je poskytnut v automatizovaném výstupu. Pro dva různé záznamy uvedené v daném datovém souboru se nesmí použít stejná hodnota této položky, a to ani v případě, kdy jsou poskytnuty v automatizovaném výstupu za jiné období nebo za jiný druh hry. V případě opětovného poskytnutí záznamu v automatizovaném výstupu za jiné období se pro položku tohoto záznamu s datovým typem identifikátor vždy použije stejná hodnota, jako při jeho prvním poskytnutí. |
| Referenční vazba | Odkaz na jiný záznam identifikovaný prostřednictvím jeho identifikátoru. Záznam, na který odkazuje referenční vazba, je v popisu položky s referenční vazbou určen pomocí názvu datového souboru, označeného jako vzdálený datový soubor, a strojového názvu položky, označeného jako vzdálená položka. Požadavky na datový typ referenční vazba jsou stejné jako na datový typ identifikátor. |
Automated output content for remote access
The operator shall enter the game and financial data in the automated output for remote access in the data package.
The automated remote access output contains game and financial data only for the operator, reporting period and type of gambling that are listed in the name of the data package with this output.
In the data files of the automated remote access output, the interface version is given in the metadata item: 1.0
The data package contains the following data files:
Data file I
Operator data
Data file name:
the operator. csv
Data file content:
The data file contains just one record with data identifying the operator, which provides an automated remote access output, regardless of whether these data have already been provided in the data package containing automated output for another period.
Conditions for entering the data file in the data package:
The data file is always included.
Record items:
Item 1
Operator identifier
Engine item name:
IDOperator
Data type:
Identifier with a maximum length of 20 characters
Item description:
The operator identification number, which provides an automated remote access output, or, if the operator identification number has not been allocated, the operator's own number allocated to the operator in connection with the issue of the basic authorisation, shall be provided. The initial zeros shall also be reported if they are contained in the operator identification number or in the operator's own number.
Item 2
Name or business name of the operator
Engine item name:
Operator
Data type:
Text with a maximum length of 250 characters
Item description:
The name or business name of the operator listed in the commercial register or other similar register of the State in which the operator is established shall be indicated.
Data file II
Data on the user account of the gambling participant
Data file name:
konto.csv
Data file content:
The data set shall contain data on the user account of a gambling participant established under the Gaming Act as a permanent or temporary user account through which participation in a gambling game for which an automated remote access output is provided, whether or not these data have already been provided in a data package containing automated output for another period.
Only one entry shall be entered for each user account.
Conditions for entering the data file in the data package:
The data file is always included.
Record items:
Item 1
User account identifier
Engine item name:
IDUVKonto
Sign in for notes, favorites and notifications
Regulation Information
| Citation | Decree No. 10 / 2019 Coll., on reporting in gambling |
|---|---|
| Regulation Type | - |
| Author | - |
| Collection | Code of Laws |
| Date of Promulgation | 18.01.2019 |
|---|---|
| Effective from | 01.06.2019 |
| Effective until | - |
| Status | Valid |
The regulation text is for informational purposes only.
Comments 0