When is the round closure official?
A lottery round closes officially at the system-confirmed point when ticket acceptance ends, and ซื้อหวยลาว draw cycle transitions from an open sales state to a locked pre-draw state. This transition is not a manual administrative action. It is a scheduled system event written into the cycle record during configuration, executed automatically when the designated close timestamp is reached. The official closing moment is therefore defined before the round opens, not determined at the point of closure.
Official closure and draw execution are two distinct events. The round closes officially when ticket acceptance ends. The draw executes at a separate configured point after closure, during which the platform completes pool finalisation and result preparation procedures. The gap between these two events is an operational interval, not an extension of the sales window.
What confirms official closure?
Official round closure is confirmed through a system-generated close event entry written into the cycle record at the moment ticket acceptance ends. This entry carries a timestamp, a pool lock confirmation, and a status indicator that transitions the cycle record from open to closed state. Once written, this entry cannot be altered, and no further ticket issuance is possible against that cycle reference.
The close event entry serves as the administrative boundary between the sales period and the pre-draw period. All pool documentation entries written before this event belong to the active sales record. All subsequent process records belong to the pre-draw operational sequence. The close event entry is the single point that separates these two phases within the cycle’s complete documentation.
How participants identify the close point?
Participants can identify a round’s official close point through the cycle reference data available on the platform’s draw schedule. Each scheduled round carries a published close timestamp that corresponds to the configured close event within the cycle record. This timestamp is accessible before the round opens, allowing participants to confirm the close point in advance rather than estimating it during the active sales window.
Discrepancies between a published close timestamp and the actual system-recorded close event are captured in the cycle log as configuration variance entries. These entries are accessible to administrators during post-cycle review and serve as the reference point for any participant query regarding whether a ticket submission fell within or outside the official sales window.
Late submissions and closure records
Ticket submissions attempted after the official close point are rejected by the system without generating a pool documentation entry. The rejection is recorded as a failed issuance attempt within the cycle log, timestamped at the point of submission. This record confirms both that the submission occurred after official closure and that no pool entry was created for it.
Late submission records are retained within the cycle log alongside the official close event entry, allowing administrators to verify the sequence of events if a participant disputes whether their submission was received before or after the official close point. The timestamp comparison between the close event entry and the failed issuance record provides a definitive administrative determination without requiring further investigation.
An online lottery round closes officially at the system-executed close event timestamp configured during cycle setup, confirmed by a locked pool record entry that marks the precise boundary between the sales period and the pre-draw operational sequence.