Feature · Debt merge
A couple, one balance. One more simplification.
Debt merge
In a flatshare or on a trip, a couple often prefers making a single transfer at the end. CountClub lets the admin transfer one member's balance into another's: both members stay visible in the count, but only one pays or receives at settlement time.
How it works
Merging is a deliberate, documented transfer: the admin declares that a secondary member's balance is absorbed by a primary member. Full history is preserved — only the final settlement plan is simplified.
Admin opens merge settings
Dedicated section in count settings, accessible only to the admin. Only that person can set, change or undo a merge.
Pick a primary and a secondary member
The primary is the one who'll pay or receive at settlement. The secondary's balance transfers into the primary's.
Balances combine automatically
The secondary goes to zero, the primary receives their debt or credit. Expenses stay attributed to their original author in the history — only the final balance changes.
Settlement plan shows only the primary
At settlement time, the simplification algorithm treats the pair as a single entity. One transfer for the two instead of two separate ones.
Honestly
What you should also know.
No overblown promises. Here are the real limits of the feature, to avoid surprises.
Only the count admin can configure or undo a merge. The two members involved are informed but don't validate.
Merging only works within a single count — no cross-count merges.
No circular merges: if A is merged with B, you can't then merge B with C. You have to unmerge first.
FAQ
Frequently asked questions.
Related use cases
See how to use it.
Try CountClub in two minutes.
Download the app, create your first count, share the link. That's it.