Expense categories

Couples: merging Zomato and Swiggy rows across two statements

When two partners order food from different cards, the same app shows up under many names. See how couples merge merchant variants without double counting.

Editorial illustration for Couples: merging Zomato and Swiggy rows across two statements

Two people, two cards and a UPI account each means the same delivery app can show up under a different label on every statement. Couples need both a clean merchant name and a clear account for each row, so a household total of Zomato, Swiggy and membership charges is correct and nobody is counted twice. Merge the labels first, then use the account to see who paid.

What goes wrong when two statements meet?

Three things, usually. The same app appears under different narrations on each person's card. A membership may be bought by one partner but used by both. And when one partner orders on behalf of the other and gets repaid, the repayment looks like income while the order sits in the first partner's spending.

Worked example: one household month

Say Partner A pays for 8 orders at about ₹350 each on a credit card and Partner B pays for 6 orders at about ₹300 each from a bank account. A ₹299 membership is paid from A's card.

LineCalculationAmount
Partner A's orders8 times 350₹2,800
Partner B's orders6 times 300₹1,800
Membershipone charge on A's card₹299
Household total2,800 plus 1,800 plus 299₹4,899

If each partner only looks at their own statement, A sees ₹3,099 and B sees ₹1,800. Neither number is the household figure, and neither person knows the membership serves both.

How do you keep the account visible?

Each transaction should keep its account. In SpendixAI you pick the account, whether a bank, card or wallet, before importing, and each transaction keeps it. Then a merchant report can be filtered by account, so the household total and each person's share come from the same data. A merchant alias maps the different narrations to one name, and your history and rules apply after that.

  1. Import Partner A's card statement into A's card account.
  2. Import Partner B's bank statement into B's account.
  3. Add aliases so every narration for each app maps to one clean name.
  4. Run the merchant report for the whole household, then once per account.

What about repayments between partners?

If A orders dinner on A's card for both of you and B sends A ₹350 later, that credit is not income. Treat it as a transfer or offset it against the order. If you do neither, A's income looks higher and B's spending is recorded nowhere. Decide one convention, write it down and use it every time.

Who is the membership for?

Decide whose account carries it and keep it in a shared Subscriptions category. If one partner uses it far more, you can still compare their order counts: if the high-use partner placed 11 of 14 orders in the month, the fee is effectively mostly theirs. That is a conversation, not a tracker feature, but the numbers make it a short one.

Think about timing as well. A credit-card order made on the 28th may be billed in the next cycle, and the card bill itself is a separate payment from the bank account. Record the order from the card statement, and treat the card bill payment as a transfer, otherwise the same dinner counts once as an order and again as a payment. Couples who both use cards should check this once, because the error repeats quietly every month.

Checklist before closing the month

  • Every narration for each app is an alias of one name.
  • Each row sits in the right account.
  • The membership is in Subscriptions and visible.
  • Repayments between partners are offsets or transfers, not income.
  • No order was entered twice.
SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports