There is usually one person in a household who does the money. They have a spreadsheet, a rough sense of what groceries cost, and \u2014 somewhere in a notes app or the back of their head \u2014 their partner’s banking password.<\/p>\n
Nobody planned it that way. It happened because the tool needed one login and one set of accounts, so one person did the setup and the other person handed over credentials to be included. Now the admin is a single point of failure for two people’s finances, and the other person has no visibility at all unless they ask.<\/p>\n
That trade \u2014 visibility in exchange for passwords \u2014 is not actually necessary. A shared view can be assembled from two separate data paths that each person controls independently.<\/p>\n
Most expense tools are built around one account holder. The data model assumes one person, one email, one pile of transactions. If a second person’s spending needs to appear in the same picture, the only route in is through the first person’s setup.<\/p>\n
So the second person gives up their login, or their spending simply is not in the picture. Both outcomes are bad. In the first, one person now holds credentials they should not hold. In the second, the household budget is missing whichever chunk of the month happened on the other card \u2014 which, in a household with five to eight accounts between two people, is most of it.<\/p>\n
The fix is not a better spreadsheet. It is a structure where each person’s data enters on their own terms and lands in a shared view.<\/p>\n
PennySlice household sharing puts multiple people, shared accounts and shared budgets into one view. What matters here is how the data gets into that view: each person chooses their own path, separately.<\/p>\n
There are two paths, and they carry equal weight.<\/p>\n
Link a bank.<\/strong> Linking runs on OAuth through Plaid. The login is entered at the bank’s own site, not at PennySlice. What comes back is a read-only token for transactions and balances \u2014 no credential ever reaches us, and nothing about the process requires your partner to tell you anything. They do their own link. You do yours. Bank linking is available on paid tiers, in the US and Canada.<\/p>\n Import your own exports.<\/strong> CSV, Excel, OFX, PDF, a forwarded email, or a photo of a receipt. No standing connection to any account. The AI reads the file and works out its structure, so there is no template to pick and no columns to map. If your partner would rather not link anything at all \u2014 or banks somewhere linking does not reach \u2014 this is a complete path, not a fallback. Our guides for exporting from Canadian banks<\/a> show what that file actually looks like coming out of RBC, TD, Scotiabank, BMO, CIBC or National Bank.<\/p>\n You can mix the two freely. One partner links, the other imports. Both link. Both import. The household view does not care which route each account arrived by.<\/p>\n Separate accounts are the normal case, not the awkward exception. Two salaries, two current accounts, one or two joint accounts, a couple of credit cards, maybe some freelance income on one side.<\/p>\n A shared household setup treats those as one financial picture with shared budgets across all of them. The grocery budget is the grocery budget, whether the shop happened on your card or theirs. Penny Spotter’s budget pace detector runs against the household total, so a category tracking toward overspend gets flagged once, for both of you, rather than each person separately discovering it late.<\/p>\n The same applies to the other detectors running in the background: recurring cost creep, category anomalies, predicted expenses, merchant concentration. A subscription that quietly rose is a household cost even if it sits on one person’s card. Splitting the accounts across two apps hides exactly the patterns that are worth seeing.<\/p>\n Households generate a specific kind of mess: one transaction that is genuinely several categories. A single big-box run is groceries, clothing and household supplies in one line on the statement. Assigning it to “groceries” makes the grocery budget look absurd and the clothing budget look untouched.<\/p>\n Sub-transaction categorization splits one purchase across several categories at the line-item level, automatically. Photograph the receipt and the OCR itemizes it, with each line categorized on its own. We wrote about how a single Costco trip gets split at the line level<\/a> if you want the mechanics.<\/p>\n For a two-person household this matters more than it does for one person, because the receipts are bigger and there are more of them.<\/p>\n The part that makes the password handoff genuinely uncomfortable is that it is hard to undo. Changing a password to revoke someone’s access is a blunt instrument, and it usually breaks something else.<\/p>\n A linked account works differently. The token is revocable at any time, from either side \u2014 from PennySlice, or from the bank. If someone wants their account out of the shared view, they remove it themselves. They do not need to ask the household admin, and the admin does not need to do anything on their behalf.<\/p>\n Imported data has an even smaller footprint: there is no standing access to revoke, because there was never a connection. A file was read, and that is the whole relationship with the account.<\/p>\n A few facts worth stating plainly, because privacy claims in this category are usually vaguer than they should be. Bank passwords are never stored \u2014 the login is entered at the bank. We never sell your data, to advertisers or anyone else. There are no ads. Personal identifiers like names, emails and account numbers are not sent to the AI provider. Financial data itself \u2014 merchant names, amounts, categories \u2014 is processed by a third-party LLM provider and discarded, not retained for training. Plaid is a disclosed processor for linked accounts.<\/p>\nA household budget with separate accounts, still counted once<\/h2>\n
The Costco problem, which households have worse than anyone<\/h2>\n
Give your partner access to spending data without giving up control<\/h2>\n
One view means you can both ask it things<\/h2>\n