What is Merry-Go-Round (Table Banking) and How Does it Work?

Merry-go-round savings, often called table banking, is one of the simplest group-finance ideas there is: a fixed group of members each contributes the same amount at every meeting, and the entire pooled contribution for that round goes to one member — not split among everyone, but paid out in full to whoever's turn it is. The rotation continues, one member per round, until everyone in the group has received a payout exactly once, at which point the cycle either ends or restarts. The appeal is obvious — it turns small, regular contributions into one meaningful lump sum for each member in turn, without any interest or lending involved. A group of twenty members each contributing KES 1,000 per round means every member eventually receives KES 20,000 in one payout, in exchange for having contributed KES 1,000 twenty times. The mechanics that actually make it work are the part people underestimate. Positions in the rotation need to be assigned fairly — usually by a random draw the group agrees to and ratifies together, rather than whoever asks loudest. Once assigned, the order needs to be tracked precisely: a manual system can lose track of whose turn is next, especially across several concurrent rotations in a larger group, or fail to notice that a member who already received an early or emergency payout shouldn't be paid again when their original turn comes around — a real and surprisingly common source of disputes in manually-run merry-go-rounds. Some groups also allow an early or emergency payout — advancing a member's turn if they have a genuine urgent need, funded from the pool's accumulated balance rather than a not-yet-collected future round. Handled properly, this is a real flexibility benefit of the model; handled sloppily, it's exactly the kind of thing that erodes trust in the rotation. pawa Loans's merry-go-round tools handle position assignment (with group ratification), automatic round generation, and early-payout requests — including guarding against the exact double-payment mistake described above, so the mechanics stay fair without anyone needing to track it by memory.