GUIDES · BETSLIP DOCTOR
Why can a late-night ticket belong to a different calendar day in a summary?
A timestamp marks an instant; a calendar day depends on the timezone used to read that instant. BSD History's Today and Yesterday views classify settled records using settlement time in the summary's timezone. A late-night settlement in one timezone may fall on the previous or next date in another.
For Bettors comparing a late-night settlement with a BSD History day summary · Updated
One settlement instant can have two local dates
A stored timestamp identifies a point in time. To place it on a calendar, a viewer applies a timezone. Near midnight, the resulting date can differ across timezones even though the underlying instant is the same.
In BSD History, the Today and Yesterday views use the summary's timezone when they group saved settled records by settlement time. The account's History data carries its timezone, and the app uses that timezone for the day boundary. The display date is therefore a calendar grouping, not a change to the settlement event.
Illustrative boundary: UTC and a fixed UTC−5 offset
Suppose a hypothetical ticket settles at 01:30 UTC on May 8. In a hypothetical timezone kept at a fixed UTC−5 offset for this example, that same instant is 20:30 on May 7. A day summary using the latter calendar will place it on May 7; a UTC calendar will show May 8.
The two dates do not describe different settlement events. They are two ways to express one instant. The example uses an artificial fixed offset so the arithmetic stays clear; it does not represent a particular user's timezone setting or a real ticket.
Check the timezone and the timestamp you are comparing
When a summary day looks different from a sportsbook screen or another report, compare the underlying settlement timestamp and the timezone each display uses. Confirm you are comparing settlement time with settlement time; placement time and the date a record was stored answer different questions.
If the record has only a settlement date and no settlement time, the exact instant cannot be converted into another timezone. The history record may also lack its placement time. Keep those fields unknown instead of estimating the time from the day label.
A day summary has a defined scope
The Today and Yesterday grouping uses the settled records available in the History view's day window. It is based on settlement time and the summary timezone; a record without a settlement timestamp cannot be assigned to that day by this rule. A list can also be marked partial when the read reaches its cap.
If a record remains absent after comparing its timestamp, source and timezone, check the History data coverage or contact BSD Support with the discrepancy. Do not assume that every provider supplies every timestamp or that a summary proves an event's local date at the sportsbook.
Illustrative two-calendar comparison
Hypothetically, the single instant May 8 at 01:30 UTC is May 7 at 20:30 under a fixed UTC−5 offset. If a History day view applies the latter timezone, the settlement falls under May 7. No user timezone, actual bet, sportsbook record or account setting is represented.
Related questions
Did the settlement itself move to another day?
No. The instant stays the same. Converting it to a different timezone can change the displayed calendar date.
Can a date-only settlement be reliably assigned to a timezone day?
Not to an exact instant. When a source supplies a date without a settlement time, the record cannot establish which side of a timezone boundary that instant fell on.