Skip to content
Resources · Blog

How to Share Household Costs in a Joint Family 

In a joint family, money is shared but rarely pooled. How to split bills, record who paid and settle up monthly without exposing anyone's own accounts.

November 12, 2026 5 min read
Family FinanceHousehold BudgetPakistanMoneyTig

In a joint family, money is shared but rarely pooled. The brothers split the electricity and the gas, the ration is bought by whoever passes the shop, the parents' medicines come from one son's salary this month and another's the next, and everyone keeps their own salary account, savings and side income to themselves. That arrangement is reasonable, and it can run smoothly for years. The arguments, when they come, are seldom about the amounts. They come from not knowing: who paid the last gas bill, whether the grocery split was equal, how much one household still owes another after three months of small favors. We build software for Pakistani households, including MoneyTig, and the pattern we designed around is this one: shared costs need a shared record, and personal money needs to stay personal. Here is a method that works on paper, in a spreadsheet or in an app.

Agree on What Is Shared, and How It Splits

Before you track anything, write down which costs are shared. In many joint households the list includes rent or house maintenance, electricity, gas and water, the monthly ration and groceries, household help, and the parents' medical costs. Some families also share school fees or a car; many do not. Then agree on a split rule for each cost. Equal shares are simplest. Some families split by household unit, so each brother's family pays one share and the parents pay none. Others split certain costs by income, or let one earner carry a cost entirely as his or her contribution to the parents. Any of these can work. What causes friction is a rule that nobody stated, or one that changes without anyone saying so. Put the list and the rules on one page that every adult has seen, and revisit it when circumstances change: a marriage, a new baby, a job loss, a brother moving out.

Record Each Cost Once, Then Track Who Owes Whom

The core habit is to record every shared cost once, at the moment it is paid, with three facts: who paid, how much, and how it splits. Suppose the electricity bill is Rs 18,000 and the eldest brother pays it from his account, split equally between three households. The record shows Rs 18,000 paid by him, and each of the other two households owing him Rs 6,000. The following week the middle brother's wife buys the month's ration for Rs 24,000, split the same way, so each of the other two owes her Rs 8,000. Over a month these small positions build up into a simple table of who owes whom, and many of them offset each other. You do not need to settle after every bill. When money does change hands, record that too, as a settlement against the balance, not as a new expense. The common failure is recording the same bill twice, once in the payer's notebook as spending and once in someone else's as money owed, so that nobody's totals agree. One shared record, written once, avoids it.

Keep Personal Money Out of the Shared Record

A shared record does not require shared accounts. The household needs to know that the eldest brother paid Rs 18,000 for electricity. It does not need to see his salary account, his savings or what else he spent that month. The fastest way to make a family resist tracking is to make it feel like surveillance. Record only the household's side of each shared cost: the amount, the payer and the split. Leave each person's own accounts, side income and private commitments, such as a loan to a friend or support sent to a wife's parents, in their own records. When people know the shared record shows the shared costs and nothing more, they are more willing to keep it current. If you use software for this, check what other members can see by default. A good tool lets you decide account by account, rather than assuming that being family means seeing everything.

Put the Bills Where Everyone Can See Them

Many household arguments start with a surprise: the winter gas bill, school fees due for every child in the same month, an annual payment nobody remembered. Shared bills should be visible before they fall due, not after. List every recurring household bill with its usual amount, its due date and the person responsible for paying it. For bills that vary, record an estimate and correct it when the real figure arrives. Then look ahead a month at a time: the cash the household can call on, less the bills due in the next thirty days, is the money that is free to spend. That single figure prevents more friction than any split rule, because it turns "why didn't anyone tell me" into a number everyone saw two weeks earlier.

A Monthly Settling Routine

  • Pick one fixed date each month, such as the first Sunday, and keep to it
  • Go through every shared cost recorded since the last settling
  • Confirm each household's balance and agree on it before anyone pays
  • Record each settlement as it happens, in cash or by transfer, against the balance it clears
  • Look at the next thirty days of bills and confirm who pays which
  • Write down any change to the split rules, with the date it starts

Where MoneyTig Fits

MoneyTig is built around this way of sharing. Each adult has a personal space that nobody reaches by being family; a family relationship grants no access on its own. A household space holds the shared costs and bills, and each member gets only the access you grant, per space or per account, with a preview of what they will see before it applies. Shared costs are recorded once with their split, balances are kept per person, and settlements are recorded when they are paid; a settlement larger than what is owed is refused. Bills and budgets show what remains after the next thirty days of recorded bills. MoneyTig records the money and never moves it, so settling still happens between people, in cash or by transfer, as it does today. Our MoneyTig case study explains why we chose private spaces and explicit grants over a single shared view, and what that choice cost us in setup.

Have a project that needs this kind of thinking applied to it?