Bank statements

Couples: import a year of joint and personal statements cleanly

Two salary accounts, a joint account and shared bills: how couples can avoid duplicate transactions when importing bank statements into one set of books.

Editorial illustration for Couples: import a year of joint and personal statements cleanly

Across a shared household, the same rupee appears in several statements: it leaves one partner's account, lands in the joint account and then leaves again for the landlord. To avoid duplicate transactions when importing bank statements, give each account exactly one importer and decide how transfers between your own accounts are treated.

Where couples get double counts

Take a month where each partner moves ₹30,000 into a joint account, and the joint account pays ₹52,000 for rent and society maintenance. If both partners' statements and the joint statement are imported, a naive total of outflows looks like ₹30,000 + ₹30,000 + ₹52,000 = ₹1,12,000, but only ₹52,000 of that left your household. The other ₹60,000 only moved between your own accounts.

RowAmountWhat it is
Partner 1 to joint account₹30,000Transfer between your accounts
Partner 2 to joint account₹30,000Transfer between your accounts
Joint account to landlord and society₹52,000Real spending

The ₹60,000 is not a duplicate in the file-import sense, but it behaves like one in your totals, so decide a label for it before you import.

Give each account one owner

  1. List every account: each partner's salary account, the joint account, each card.
  2. Assign one person to import each one. The joint account goes to whoever handles the household bills.
  3. Agree a start and end date for the year and download the same windows for all accounts.
  4. Never let both partners upload the joint statement 'just in case'.

This is the single biggest cause of doubled rows in a household: two people, one joint file, two uploads.

How should we handle transfers between our own accounts?

Pick a single approach and stick to it. One way is to leave a category called something like Own transfers, assign those rows to it, and exclude it when you read spending. Another is to import only the joint account for household bills and skip personal accounts for those months. Either works. The mistake is mixing the two halfway through the year.

What SpendixAI can and cannot do here

You pick the account before each import, rows are reviewed before saving, and possible duplicate imports are flagged. Pro covers one personal workspace, so it is not a shared-books or approval tool. In practice that means one of you keeps the records and the other reads the totals, and you agree on who adds cash spends by hand. The Possible duplicate charges report can also show the same amount to the same merchant within two days, which helps spot a bill paid from both accounts by mistake.

A real-life repeat to look for

Say the broadband bill of ₹1,179 is paid from the joint account on the third and then again from a partner's card on the fourth because each thought the other had not done it. That is a genuine double payment, and the app's report will surface it. A duplicate import hides inside one file; a double payment shows up as two different accounts.

How do we reconcile at the end?

Once everything is imported, pick one month and do a quick three-way check. Add up what left each partner's account, what arrived in the joint account, and what the joint account paid out. If the transfers in equal the transfers out, the household picture is consistent. In the earlier example, ₹60,000 went in and ₹52,000 went out, so ₹8,000 stayed behind as a balance. If the balances in your records do not move by that amount, a row is missing or doubled. Do this for one month first. If it balances, the other eleven are far more likely to be right.

  • Sit down together once, with both statements open.
  • Write the three totals on paper.
  • Fix differences before importing further months.

Checklist for the weekend you do it

  • One importer per account.
  • Same date windows everywhere.
  • Transfers labelled, not deleted.
  • Monthly debits in the app match each statement's debit total.
  • Review flagged rows together rather than approving them all.
SPENDIXAI JOURNAL

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

Explore your reports