How Sportsbook Bet Settlement Works: Results, Voids and Corrections

A sportsbook settles a bet by applying the accepted bet terms and its published market rules to an event result, then recording the resulting payment or refund in the customer's account. A score on a screen is not, by itself, a settlement decision. The operator first needs to identify the accepted selection, price, stake and applicable rules; determine the result using the specified source; grade the market; and post the correct account transaction. An error can require a later correction.

This is a practical explanation for sportsbook product and compliance teams and for readers checking a disputed bet. The regulatory examples come from Great Britain and were reviewed on 29 September 2026. A named data supplier illustrates one possible feed implementation, not a universal sportsbook architecture. The actual contract, market rules and local law matter in each case.

Step 1: Fix the bet that was actually accepted

Before the event result matters, the system has to establish what the customer committed to and what the operator accepted. The UK Gambling Commission's RTS 2 requires clear information about the financial commitment and the content of a remote gamble before commitment. Its guidance identifies the selection, bet type and accepted odds as relevant betting-slip information. It also says the rules must identify which odds format takes precedence when a bet is settled.

An offered price is not always an accepted price. RTS 2 requires customers to be able to choose whether to accept price fluctuations after a bet is requested. If a customer has not opted into automatic acceptance of a changed price, the changed bet must be reoffered before acceptance. That distinction matters most in fast-moving in-play markets: a screenshot of the offer is weaker evidence than the final acceptance record. See our odds-feed and managed-trading guide for the upstream price workflow; this article begins at the accepted ticket.

For covered British betting licences, LCCP 4.2.6 requires the operator to issue a betting slip or electronic acknowledgement for each transaction, apart from telephone betting. It must identify the operator and give the equivalent of an acknowledgement that bets are accepted under its rules. Special terms agreed for a particular bet cannot be displaced by conflicting general rules or subsequent rule changes. A later web-page edit therefore cannot simply rewrite the special terms of an already accepted bet.

From accepted slip to account entry

The exact system design varies, but the control sequence is reasonably consistent. This table is an editorial model, not a regulator-prescribed software diagram.

The record column is a practical evidence recommendation. It should not be read as a claim that the British regulator mandates every named database field. The obligation that does matter is to accept, process and settle bets in line with published rules, and to handle technical errors fairly under RTS 5.

Step 2: Determine which result counts

A final score can be a poor shortcut. Markets may ask different questions about the same fixture: full-time result, a period, a player event, a handicap or a proposition. They can also define abandoned fixtures, official corrections, postponements and withdrawals differently. The relevant market wording and the operator's published rules determine the answer, not a generic sports-news headline.

British LCCP 4.2.6 specifically requires the full rules to cover the means or medium by which the outcome of an event will be determined. The same provision requires rules for voids, late bets and errors, treatment of withdrawals and non-runners, and maximum payout. The Commission's settlement guidance says market displays and receipts should be consistent with the published rules and that rule changes should be published when they take effect.

For example, imagine a bet on a match's 90-minute result. A score after extra time would not automatically answer that market's question. Conversely, if a market explicitly includes extra time, stopping at the 90-minute score would be wrong. Those are illustrations of why the market definition must travel with the accepted ticket; they are not a statement about the rules of any named bookmaker or sport.

Step 3: Translate a result into a settlement decision

Sportsbooks commonly receive event and market information from specialist suppliers. A supplier message can help the operator identify a provisional or confirmed outcome, but it does not replace the operator's own obligations to apply the accepted terms, calculate the return and update the customer account.

One concrete example is Sportradar's Unified Odds Feed bet-settlement message. Its documentation describes outcome values for win, loss and undecided, and a `void_factor` field that can indicate a fully or partly voided outcome. It explicitly leaves evaluation of the bet outcome to the client system. The feed documentation also distinguishes the certainty of a message from whether every market in an event has been resolved. These are Sportradar message semantics, not industry-wide legal definitions or a promise that every operator uses that feed.

Consider a simple, deliberately illustrative single at decimal odds of 2.50 with a £10 stake. If its accepted selection wins and no other rule or deduction applies, the gross return is £25, including the £10 stake; the profit is £15. If the selection is fully void under the applicable rules, the stake is normally returned rather than counted as a £25 win. An each-way, multiple, free-bet or partly voided ticket needs a different calculation. The example is arithmetic, not a prediction or betting recommendation.

The operator's ledger should distinguish those outcomes. The customer sees a balance, but a reliable audit trail needs to connect it to the ticket, grading decision and transaction. RTS 1 on customer-account information requires covered remote operators to make at least three months of account and gambling history available through self-service and 12 months on request, including bets placed, results and winnings paid. That history is the natural first place to investigate an unexpected settlement.

Void is a rule outcome, not a synonym for losing

A void bet generally means the relevant stake or stake component is returned under the bookmaker's rules. But why it is void, whether only one leg of a multiple is affected, and what happens to related selections depend on the accepted market and published rules. Abandoned events, non-runners, late bets and pricing errors cannot be collapsed into a single universal rule. British operators must set out their treatment of these categories in the full rules under LCCP 4.2.6.

An undecided result is different again: the market may remain open because the official event condition has not yet been determined. Nor should a technical feed's partly voided outcome be confused with a general right to half a stake back. The Sportradar example has a `void_factor` that can represent a partial refund, but a customer's entitlement depends on the bet type and the operator's terms. Where several selections combine into one ticket, the settlement engine must apply the actual multiple or each-way rules; it cannot treat each leg as an unrelated single.

This is also why the terms shown at acceptance matter. If a displayed market condition and the general rulebook conflict, the operator should investigate the discrepancy against the accepted transaction rather than rely on a later generic explanation. The Commission's published-rules guidance puts consistency of the displayed information and rules at the centre of fair settlement.

What if the score or settlement was wrong?

There are two separate failure modes. First, an event result or supplier message may be corrected. Second, the operator may have applied the right result to the wrong market rule, stake, price or account. A visible change in the ticket status does not explain which happened. A defensible correction identifies the earlier decision, the new evidence or rule application, and the account adjustment.

Sportradar documents a rollback-bet-settlements message for a previously sent settlement that was wrong. This shows a technical path by which a supplier can withdraw an earlier message at market or outcome level. It does not mean every customer bet should automatically be reversed: the bookmaker still needs to evaluate the changed message against its accepted terms and rules.

Under British RTS 5, operators must take reasonable steps to ensure gambling is accepted, processed and settled in accordance with published and event-specific rules. Technical errors must be remedied promptly and customers treated fairly; the guidance includes notifying customers about incorrectly settled bets as soon as practicable and gives manual account adjustment as a possible remedy. The Commission's bet-settlement guidance says money accrued contrary to published rules should be divested to affected customers, or addressed with the Commission if those customers cannot readily be identified.

Neither a feed rollback nor a bookmaker's claim of “palpable error” by itself settles a disputed account entry. The relevant evidence is the accepted ticket, the rule that applied at the time, the result source specified by that rule and the sequence of account transactions. A later score correction can matter, but only to the extent the applicable market terms make it matter.

How to check a disputed sportsbook settlement

Use a short evidence trail before arguing from a headline score or a screenshot of live odds. The following is an editorial checklist, not legal advice.

1. Save the accepted ticket. Record its identifier, selection, market wording, stake, accepted price, timestamp and any special terms. Keep the acknowledgement rather than only the bet-slip preview.
2. Read the relevant market rule. Look for result source, regulation-time or overtime wording, postponement and void rules, non-runner treatment, deductions and payout caps. Record which version was available when the bet was accepted.
3. Compare the specified result with the grading. A feed, league page or broadcaster may show different stages of an event. Ask which result the operator used and why it answers this particular market.
4. Reconcile the account. Check the stake debit, return or refund, and any later adjustment. The customer-account history requirements provide a starting point for covered British remote products.
5. Ask for a reasoned correction if entries disagree. Supply the ticket and rule evidence to the operator's complaints route. For eligible unresolved British transaction disputes, our complaints and ADR guide explains the subsequent independent process.

For operators, the same chain is a design test: can support staff reproduce the amount on the customer's screen from a retained acceptance record and rules version without guessing which supplier message was “final”? This is where player account management and settlement controls meet. The broader financial reporting effect is different again: sportsbook hold is an aggregate ratio, not the settlement status of an individual ticket, as explained in our hold-versus-margin guide.

Bottom line

Sportsbook settlement is a rule-governed account decision, not a direct copy of a live score. The accepted ticket defines the wager; the published market rules define the relevant result and exceptional cases; a source or feed supplies outcome information; and the operator grades, calculates and posts the transaction. When a result or system error is corrected, the reason and account impact should be explainable from that same evidence chain. British regulatory requirements cited here are jurisdiction-specific; readers should check the current rules of the operator and market involved.

Frequently asked questions

When is a sports bet considered settled?

A bet is settled when the operator has applied the accepted bet terms and relevant market rules to the qualifying result, calculated the return or refund and recorded the outcome in the customer account. A live score or supplier result message alone is not the customer-account settlement. The status may later be corrected if an error is found.

Does a void sports bet return the stake?

Usually a fully void single results in the stake being returned, but the exact treatment of a partly voided selection, multiple, each-way bet or promotion depends on the accepted terms and operator rules. British betting rules must explain when bets are void and how related contingencies are handled; a void should not be assumed merely because an event changed.

Can a sportsbook change a settled bet after payout?

A previous settlement can need correction after an erroneous result or technical mistake. That is not a blanket permission to change any payout: the operator must evaluate the accepted ticket and published rules, treat the customer fairly and explain an incorrect settlement. Keep both the original and corrective account entries when questioning the change.

Does the data provider decide whether I win?

Not necessarily. A data provider can transmit an event or market outcome, but the bookmaker is responsible for evaluating the accepted wager under its rules and posting the account transaction. Sportradar's Unified Odds Feed documentation explicitly assigns bet-outcome evaluation to the client system. Other suppliers and integrations may use different message formats.

What evidence should I keep for a settlement dispute?

Keep the accepted bet acknowledgement, ticket identifier, stake, accepted odds, market wording, special terms, account history and the result source specified in the rules. A screenshot of an offered price or live score may help but does not replace the accepted ticket. Ask the operator to identify the applicable rule and explain any later adjustment.