GUIDES · BETSLIP DOCTOR
Why can two History date filters show different records for the same account?
Two date-based History views can use different dates for the same ticket. The History record-list window is based on actual placement time, while settlement summaries can group a settled ticket by its settlement timestamp in the relevant time zone. A ticket placed in one period and settled in another can therefore appear in one result set but not the other. Compare the date basis before treating the difference as a missing record.
For Bettors comparing dated History records and summaries · Updated
Placement date and settlement date answer different questions
Placement time answers when the wager was recorded as placed. Settlement time answers when its result was recorded as settled. BSD's History record keeps these as separate timestamps, and its list-window contract names actual placement time as the range basis. Some day totals instead group settled records by settlement time.
The same ticket can cross a date boundary: it may be placed before a range starts and settle during it, or be placed during the range and settle afterward. Views using those two dates can legitimately count different records without either changing the ticket.
Use a short checklist to compare two results
Before investigating a count mismatch, compare the date basis and the record itself. Do not assume every History view applies its range to the same timestamp, or that a date-only provider value represents an exact time.
- Open the same ticket in both views and compare its placement and settlement dates.
- Check whether the result is a settled-ticket list or a settled-day summary.
- Check the time zone used to turn a timestamp into a calendar day; an event near midnight can fall on different local dates in different zones.
- Look for source limitations such as missing placement time, missing settlement time or a date without an exact settlement instant.
- If the ticket identity or source record differs, compare the record references before concluding that a date range removed it.
A missing timestamp leaves the date question unresolved
An imported record can lack a placement time or settlement time. BSD marks those gaps rather than inventing an instant from a date alone. Provider history can also change when refreshed, and a source may not supply every detail. Treat a missing timestamp as unknown and check the sportsbook record if the exact day matters.
This explanation describes date bases and record fields. It does not claim a particular filter button, control label or that every provider supplies complete timestamps.
Hypothetical: one ticket crosses a date boundary
Suppose a wager is placed late on the final day of one date range and the sportsbook settles it the next day. A placement-time list for the first range can include the ticket; a settlement-day total for the following day can count it there. Compare the same ticket's two timestamps and the time zone used by the summary before diagnosing a mismatch. If either timestamp is missing, the exact day comparison remains unresolved.
Related questions
Does a settlement date mean the bet was placed that day?
No. Placement and settlement are separate History fields and can fall on different dates. Check which date a particular list or summary uses.
Can I assume a provider's date-only field means midnight in my time zone?
No. A date without an exact settlement instant does not establish a time of day or local time zone. History marks a missing settlement instant as a limitation.