GUIDES · BETSLIP DOCTOR
What should I check before deleting an apparent duplicate manual bet record?
Do not decide from the selection label alone. Compare the manual row with the imported record: the record type and ID, ticket and leg details, sportsbook, placement time and any available original reference. BSD keeps manual and imported rows as distinct records; an overlap is marked only by a user-confirmed link for the same placement. Without that confirmation, similar rows remain unverified overlap.
For Bettors comparing a self-reported manual history entry with a similar imported record · Updated
Compare the whole ticket, not just a matching selection
A player or team name can appear on multiple tickets. Before you treat two rows as the same wager, compare the event, market and selection details that are present, plus the other legs on a multi-selection ticket. Check the sportsbook, placement time, ticket details and stake where available. Similar wording is a useful reason to look closer, not proof that two records represent one placement.
Use the record's original details when available. Imported rows retain provider ticket information and an import record identity. Manual rows refer to a saved BSD ticket and carry their own record identity. The different sources can help explain why rows are separate even when part of their displayed text matches.
Check which source created each row
An imported row comes from sportsbook history made available by the provider. A manual row is self-reported: its placement and financial result were entered by the bettor, not confirmed by a sportsbook. Check the source label before deciding how much authority to give its placement, outcome or amounts.
Then compare the exact record IDs and revisions, not just the row titles. A changed import or changed manual entry can have a new revision while still referring to its record. When a provider original reference, ticket ID, source digest or timestamp is unavailable, treat that part of the comparison as unknown rather than filling it in.
An overlap link is a specific confirmation
BSD's history model keeps a manual-to-import overlap link with the manual record ID and revision, imported record ID and revision, and imported source digest. The link is labeled user-confirmed. Its confirmation means the bettor identified those records as the same placement; it is not an automatic finding based on similar selections.
If the manual row changed after the link was confirmed, its current revision no longer matches the one recorded in the confirmation. Recheck the underlying ticket before relying on that old match. An unlinked manual row can still overlap an import, but the system leaves that possible overlap unverified.
Know what a confirmed link changes before taking action
A confirmed linked manual duplicate is excluded from default history lists and financial totals so the same placement is not counted twice there. The manual record still has its own source and details. Removing an overlap link and deleting a history record are different operations; an unlink command does not itself establish that the record was deleted.
If the two rows may represent separate placements, do not rely on resemblance or an old link to collapse them. Verify the underlying source and placement first. This guide explains how to assess the records; it does not promise that a delete control or recovery option is available for every entry.
Illustrative example: same leg, different placement question
In a fictional account, a manual row and an imported row both name the same player market. The reader compares the full ticket, sportsbook, placement times and original source details. They find that the manual row refers to a separately saved ticket and there is no user-confirmed same-placement link. The matching selection alone cannot settle the question, so the reader leaves the possible overlap unresolved until they can verify the original placement. No real record or account is shown.
Related questions
Does BSD automatically identify every duplicate manual entry?
No such automatic determination is established by the record source. The explicit overlap relationship is created with a user confirmation for the same placement. Unlinked entries may still overlap imports.
Does unlinking a manual row remove the bet record?
No. The overlap link records whether the manual and imported rows represent the same placement. Removing that link and deleting the manual history record are separate actions.