Player transfers in Vodkabet cashback: follow both entries

Transfers and the balance belong in the same calculation

The observed Vodkabet cashback card describes accounting over the account's lifetime. Its order is:

Deposits and transfers received have plus signs. Withdrawals, transfers sent and the balance have minus signs. Previously received cashback is a separate deduction after multiplication; it is not another outgoing transfer or a reduction of the loss base.

Consider an otherwise unchanged account receiving EUR 120. The received-transfer total rises by EUR 120, but so does the balance being subtracted. Their effects cancel. Sending EUR 50 reduces the balance by EUR 50 while increasing the outgoing-transfer total by EUR 50; those effects also cancel. That explains the paired entries, without treating a transfer as a wager, win or loss.

Seven movements, with every transfer paired to its balance

This is an invented EUR ledger using the observed formula's signs. Assume every listed movement belongs to the named category and posts in full to the same balance. There are no fees, currency conversion, pending transactions, reversals or other adjustments. The settled EUR 160 loss is assumed eligible and changes only that balance. These assumptions do not fill gaps in Vodkabet's actual ledger definitions.

The opening base is EUR 800 + 0 - 200 - 0 - 300 = EUR 300. The EUR 12 is an assumed historical received-cashback total, already recorded before this snapshot. No new cashback is credited during the seven movements below; that total stays EUR 12 throughout.

The first incoming transfer gives EUR 800 + 120 - 200 - 0 - 420 = EUR 300. The first outgoing transfer gives EUR 800 + 120 - 200 - 50 - 370 = EUR 300. The deposit and withdrawal likewise leave the base unchanged under these assumptions. It is the settled loss in row 5 that increases the base by EUR 160.

The final transfers do not add a further loss. After row 7, the complete base is EUR 1,000 + 150 - 290 - 70 - 330 = EUR 460. Using only the net EUR 80 received from players would miss the balance movement that offsets it.

EUR 460 is the base; EUR 12 comes off after the rate

Use an assumed constant 8% solely to finish this illustration. It is not an observed account rate or an entry entitlement. The example supplies no cap, minimum or redemption calculation, and its exact arithmetic does not establish an operator's rounding rule.

Deducting prior cashback inside the base would instead give (EUR 460 - 12) × 8% = EUR 35.84. Omitting it would give EUR 36.80. Neither follows the observed order. The EUR 24.80 is a calculation from the invented inputs, not credited cash or a claim that it can be withdrawn.

Stopping after the opening snapshot would give EUR 300 × 8% - 12 = EUR 12 under the same illustration. That is an intermediate calculation, not a second paid award. Do not add it to the prior-cashback total merely because you calculated it; doing so would change the closing inputs without a corresponding payment.

If a signed result becomes negative, the formula alone does not tell you whether the operator applies a floor, carries an offset forward or has another treatment. None is assumed here. The guide to bonus and previous-reward deductions examines the separate question of which credits a programme subtracts and at which stage.

Match the actual category and cutoff before using the numbers

1. Keep four transaction totals separate. Record lifetime deposits, withdrawals, received player transfers and transfers sent. A player transfer is not automatically a deposit, a cashout or a game result. A signed activity total alone loses that distinction.
2. Match the balance to the same snapshot. A transfer recorded before its matching balance update can make an unchanged base appear to rise or fall. Check timestamps and settlement state rather than joining lifetime totals to a balance from another moment.
3. Verify what each balance and transfer field includes. The programme card does not fully define pending or reversed transfers, fees, currency conversion, bonus balances or every eligible game contribution. A real mismatch needs those definitions; this example's full-value EUR assumptions cannot settle it.
4. Keep received cashback and the applicable rate separate. Identify what the programme counts as received, rather than treating a displayed or unclaimed amount as already paid. A changed VIP rate also requires its actual application rule; this example holds the rate constant.

The weekly wording on the public VIP page describes payment, while the observed card uses lifetime inputs. The lifetime versus period cashback guide explains that history-window distinction. The separate Daily Rebate Plus product uses bets less wins over the previous 24 hours; this transfer ledger does not calculate that reward.

Read the cumulative programme with its remaining conditions

Vodkabet publishes eleven VIP levels with a 5-15% cashback range. The percentage applicable to the account is still needed. The cumulative reward has x3 wagering; its exact wagering base and treatment of the reward principal on withdrawal are not established. Automatic credit does not establish a universal recurring time or timezone.

Return to cashback guides for a different calculation or collection question.

Questions about player-transfer records