On a lay ticket, "stake" can describe somebody else's bet. If the field means the backer's stake, a displayed 10 can expose the person laying it to a 70-unit loss at decimal odds of 8.0. Lay liability is the possible losing payment before fees, not necessarily the number entered into the stake field.
Backing supports a specified outcome. Laying takes the other side: the layer loses if that outcome happens and wins the backer's stake if it does not, before charges. Our comparison of sportsbooks and exchange products explains the counterparty distinction. Here, the concern is how much that opposing bet puts at risk.
The field can measure two different things
Smarkets' lay-liability explanation uses this calculation when the amount is the backer's stake: liability = backer's stake × (decimal lay odds − 1). The subtraction removes the returned stake from the backer's winning return. What remains is the profit the layer would have to pay.
These invented examples use currency units with two decimal places, one fully matched lay position and ordinary win-or-lose settlement. They exclude commission and other charges. Both rows accept the same backer's stake; changing the odds changes the loss amount.
| Decimal lay odds | Backer's stake | Losing lay liability |
|---|---|---|
| 3.0 | 10.00 units | 20.00 units: 10 × (3 − 1) |
| 8.0 | 10.00 units | 70.00 units: 10 × (8 − 1) |
If the laid outcome does not happen, the gross profit on either lay is 10 units before fees. That is profit from the other person's stake, not a stake-inclusive return of 10. The possible gain and possible loss therefore differ even though the stake label stays the same.
The help page also describes a liability display. In that mode, the entered stake is already the liability; multiplying it again by odds minus one would misread the field. These are Smarkets' documented display options, not settings we have verified in a customer's account. Read the current ticket's labels and selected mode before using either interpretation.
A partial match changes the calculation
An amount requested is not an amount fully accepted. Smarkets' Your Bets guide describes showing how much of a stake has been matched, alongside the odds and liability. It also says bets on the same selection can be grouped, with individual bets available separately.
Suppose only 4 units of a requested 10-unit backer's stake match at decimal odds of 3.0. The matched portion has an 8-unit liability: 4 × (3 − 1). The remaining 6 units are still an offer. If they later match at the same price, they add another 12 units of liability. Calling the whole position an 8-unit risk while leaving that offer open would omit its possible later acceptance.
Different actual fill prices need separate arithmetic. In another invented example, a 4-unit backer's stake matched at 3.0 creates 8 units of liability, and a separate 6-unit stake matched at 4.0 creates 18. Together they create 26 units for those matched positions. The quantities here are the actual specified fills, not a promise that an original request executes unchanged.
Smarkets' terms, clause 6.14, distinguish unmatched offers from portions already matched. Cancelling an unmatched remainder does not cancel the matched bet. A cancellation request also needs a confirmed outcome; the terms warn that amendment, withdrawal or cancellation cannot be guaranteed after placement. A visible quote and an accepted record ask different questions, as our accepted-odds guide shows for sportsbooks.
One market can have a smaller worst case
Adding each individual liability can overstate a market's loss if those bets cannot all lose together. Smarkets' net-liability example demonstrates this with lays against both teams in one football match-result market. Home win, away win and draw are mutually exclusive outcomes in that example. Net liability follows the worst combined result, which may include a winning bet.
Consider our own fictional Team A and Team B in that same three-outcome model. Lay A for a 10-unit backer's stake at 3.0: its individual loss liability is 20. Lay B for a 10-unit stake at 2.0: its liability is 10. Both positions are fully matched in one market. Ignore fees, voids and any other positions.
| Match-result outcome | Combined profit or loss | Results of the two lays |
|---|---|---|
| Team A wins | −10.00 units | Lose 20 on A; win 10 on B |
| Team B wins | 0.00 units | Win 10 on A; lose 10 on B |
| Draw | +20.00 units | Win 10 on A; win 10 on B |
The largest loss in this model is 10 units, not the 30 obtained by adding the two standalone liabilities. The result depends on accounting for every possible outcome and combining both payoffs within the same market. It is a loss-exposure illustration, not a recommendation to place either position.
A pair of bets merely relating to the same sporting event does not establish that condition. Different market definitions can permit both positions to lose. The cited example also does not establish shared collateral between markets or providers. Use the venue's applicable exposure rules, rather than treating a similar event name as proof that it will net the positions.
An account reserve is not a settled loss
Smarkets' bet-liability page says liability is deducted from available balance when a bet is placed and returned if the bet is cancelled. That is an available-funds state. A reduction in money available to use does not, by itself, show that a bet has lost. The matched record, any open remainder and the provider's reserved-balance calculation need separate identification.
Fees sit outside the examples above. Some commission structures charge losing bets as well as winning ones. Our exchange-commission explainer follows those charging bases; the base bet liability alone cannot describe the complete result after every applicable fee.
These provider descriptions come from Smarkets' English (United Kingdom) documents checked on 9 October 2026. The linked terms are version 4.14, modified 14 August 2026. They restrict registration by country and describe percentage-odds conversion that can round stakes or liabilities. The exact arithmetic here is not a claim about worldwide access, every current interface or a universal rounding policy.
A ticket's display mode, individual matched amounts and prices, any remaining offers and exact market definition belong in the same record. If netting reduces the reserve, the outcome breakdown should explain which positions reduce the worst loss. An exposure number should lead back to those entries, rather than make the customer infer a loss from an unlabelled amount.
