Category: PennySlice

You have a CSV of eighteen months of transactions and a vague sense that something in there is leaking. You open a chat box and type “analyze my spending”, and you get back a paragraph that could have been written about anyone. That is not the AI failing. That is a question with no edges.

A conversational tool grounded in your own data answers narrow questions well and broad ones badly. So the useful skill is knowing where the edges are. In PennySlice, there are eight areas a question can land in: transactions, accounts, categories, budgets, imports, receipts, predictions and what-if scenarios. Here is what each one actually answers, and what comes back.

Transactions: the questions with a row number attached

This is the area most people underuse, because they assume search is all it does. It is not search — it is filtering, summing and sorting in plain English.

Things that land here:

• “What did I spend at hardware stores in March?”
• “Show me every transaction over $200 in the last 90 days.”
• “How many times did I pay for parking last month, and what was the total?”
• “Did I get charged twice by anyone in February?”

The answer shape is a figure plus the rows behind it. Twelve parking charges, $186. You can see the twelve. That matters more than it sounds, because the moment an AI gives you a number you cannot trace, you have to take it on faith — and financial numbers you cannot check are not worth much.

Accounts: where the money sits, not just where it went

Account-level questions are about distribution. Balances, transfers between your own accounts, which card carries which kind of spending.

• “What’s the current balance across all my accounts?”
• “How much moved from checking to savings this year?”
• “Which account do most of my subscriptions hit?”

That last one is quietly useful. Subscriptions scattered across three cards are the ones nobody audits.

Categories: including the ones a single purchase belongs to at once

Category questions are the standard “where is my money going” question, made answerable.

• “What are my top five categories this quarter?”
• “Is groceries up or down compared to the same period last year?”
• “What percentage of my spending is discretionary?”

The part that changes the answers here is sub-transaction categorization. One purchase can be split across several categories at the line-item level, so a warehouse-store run becomes groceries plus household plus clothing rather than a single lump filed under whichever label loses the least information. If you have ever looked at a category report and thought “most of that groceries number is not groceries”, that is the reason — and splitting a Costco receipt at the line level is the fix.

Ask a category question against split data and the answer is a different number. Usually a more uncomfortable one.

Budgets: pace, not just totals

Budget questions are about position in a period, which is the thing a monthly statement is worst at telling you.

• “How much of my dining budget is left?”
• “Which categories am I on track to go over this month?”
• “Was I under on transport in any month last year?”

The answer comes back as a figure and a pace — spent to date, days remaining, projected end-of-month. Penny Spotter also runs budget pace as a background detector, so the flag arrives before you thought to ask.

Imports: asking the AI to analyze my bank statements right after the file lands

This is the area nobody expects to be conversational, and the one that removes most of the setup friction. When you drop a file in — CSV, Excel, OFX, PDF, a forwarded email, or a photo — the AI reads it and detects its structure. There is no template to pick and no column-mapping screen.

So the questions are about the file itself:

• “Did anything fail to import from that statement?”
• “Are there duplicates between this file and what I already had?”
• “What date range does this import cover?”

If your bank’s export is the part you are stuck on, the guides cover that separately — there are 104 bank export guides across 14 countries, including a walkthrough of exporting transactions from Canadian banks. Import works wherever you are. Bank linking through Plaid is a separate capability, available in the US and Canada, on paid tiers.

Receipts: line items a statement cannot show you

A bank statement gives you a merchant and a total. A receipt gives you what was in the bag. Photograph one and OCR pulls the itemized lines, each categorized individually.

• “What did I actually buy on that $214 supermarket charge?”
• “How much of my grocery spending is pet food?”

That second question is unanswerable from statement data alone, at any level of AI sophistication, because the information is not in the file. This is the honest limit: the AI can only analyze what your data contains. If you want line-level answers, categorizing a receipt line by line is the step that puts them there.

Predictions: bills that have not arrived yet

Prediction questions project your own patterns forward. They are not forecasts of the economy or of your income prospects — they are extrapolations of what has recurred.

• “What bills are due in the next two weeks?”
• “What does a normal month cost me?”
• “Have any of my recurring charges gone up?”

Recurring cost creep is one of the seven Penny Spotter detectors, alongside category anomalies, income changes and merchant concentration. Those run in the background whether or not you ask, which covers the questions you would never think to type.

What-if scenarios: a number instead of a maxim

Pulse Check answers hypotheticals against your real balances and history.

• “Can I afford a $1,400 laptop next month?”
• “What happens to my monthly total if I drop three subscriptions?”
• “If income drops 15%, what does that do to my normal month?”

What comes back is arithmetic on your data: your projected balance, your committed bills, the gap. It will not tell you whether to buy the laptop. It tells you what the month looks like on either side of the decision, and you make the call.

How to ask a question that gets a real answer

The pattern across all eight areas is the same. Name a thing, name a window, and the answer has a figure in it. “Analyze my spending” has neither. “What did I spend on food delivery in the last three months, and is it rising?” has both, and lands in categories and predictions at once — which is fine, because you are not required to know which of the eight you are in.

Start with one question you have genuinely wondered about and could not answer from a statement. Import a file, ask it, and see whether the number surprises you. Track is free forever; paid plans come with a 30-day trial and no card required.

PennySlice provides spending information, not financial advice.

You spent $214.37 at a warehouse store on Saturday. The card statement shows one merchant, one amount, one date. Your expense tracker files it under Groceries, because that is the closest single label available.

But the cart held $86 of food, a $54 winter coat, $38 of paper towels and detergent, a $24 tire rotation, and $12 of over-the-counter medicine. Exactly none of that is a grocery problem. And when you look at your grocery spending three months later and it says $1,340, you will believe a number that is off by hundreds of dollars in a direction you cannot see.

This is the quietest failure mode in personal expense tracking. It does not look like an error. It looks like data.

Why whole-receipt categories go wrong

A category is only useful if it answers a question. “Am I spending more on food than I think?” is a real question. It stops being answerable the moment your food category is also absorbing clothing, car maintenance and cleaning supplies.

The distortion runs in both directions at once. Groceries look inflated, so you conclude food is your problem area. Household and clothing look artificially low, so they never surface as anything at all. If you set a grocery budget against that inflated baseline, the budget is built on a number that was never about groceries.

It also gets worse the more you consolidate your shopping. Warehouse stores, big-box retailers, pharmacies that sell milk, hardware stores with a snack aisle, online marketplaces that ship four unrelated things in one charge — the merchant tells you almost nothing about what the money bought. A $60 charge at a pharmacy could be a prescription, a birthday gift, or three weeks of shampoo. The merchant name is the label, and the label is wrong.

Most people handle this one of two ways. They pick the dominant category and accept the noise, or they manually split transactions and stop doing it after about two weeks because the process is tedious and nothing bad happens when you skip a day. Neither produces data you would want to make a decision on.

How to categorize a receipt line by line

The fix is not more discipline. It is getting the line items into the system at all.

Your bank does not have them. A bank feed carries merchant, amount, date and sometimes a payment channel. It never carries the contents of the basket, because the bank was never told what was in the basket — it was told the total. That limit applies whether you link an account or import a statement file yourself, and it is the reason a linked bank feed alone will never fix this particular problem.

The only place the itemization exists is the receipt. So the sequence looks like this:

1. Capture the receipt itself, not the statement line. Photograph it at the till or when you unpack the bags. A paper receipt that goes into a coat pocket is data you have already lost.
2. Read the lines, not the total. Each row on the receipt is its own small expense with its own amount, and it needs its own category.
3. Assign categories per line. Coat to clothing. Detergent to household. Tire rotation to auto. Food to groceries.
4. Reconcile against the total. The line items plus tax should add back up to the charge on your account, or something got missed.
5. Keep the split attached to the original purchase. You want one transaction with four category components, not four invented transactions that no longer match your statement.

That last step is the one people get wrong when they do this by hand in a spreadsheet. Splitting a purchase into four separate rows breaks reconciliation — your ledger no longer lines up with your account, and now you have two problems.

What receipt OCR and sub-transaction categorization actually do

In PennySlice, this runs as two connected pieces.

Receipt OCR handles capture. You take a photo of a receipt and the itemized lines are read out of it, then categorized individually rather than dumped under the merchant. The $54 coat lands in clothing on its own. You are not typing rows into a form.

Sub-transaction categorization handles the structure. One purchase can carry several categories at once, at the line-item level, while staying a single transaction tied to the single charge on your account. The warehouse run becomes groceries plus household plus clothing plus auto — and your grocery total stops carrying $128 that was never food.

Corrections you make feed back in. If a line gets categorized in a way that does not match how you think about it, fixing it improves categorization across the platform, so the accuracy compounds with use rather than staying wherever it started.

And because the categories are now honest, the background detectors have something real to work with. Penny Spotter runs seven detectors without being asked — including budget pace, which flags a category tracking toward blowing its budget before the month ends, and category anomalies, which flag spending that breaks your own established pattern. A budget-pace alert on groceries is only worth reading if groceries means groceries. Feed it a category that absorbs coats and tire rotations and every alert is a coin flip.

Receipts are not the only path in

Photos are the right tool for itemization, but they are one of several ways to get data in. You can also import CSV, Excel, OFX or PDF files, or forward receipts by email. The AI reads the file and works out its structure — there is no template to choose and no column-mapping step to fight through.

If you would rather start from your account history and add receipts on top, statement exports are the usual starting point, and the process differs by institution — our walkthrough for exporting transactions from Canadian banks covers the main ones step by step. Bank linking through Plaid is also available on paid tiers in the US and Canada, where your login is entered at your bank rather than at PennySlice. Whichever route you use, the receipt is still the only source of line items.

This matters most in a household, where the mixed-basket problem multiplies. Two adults, five to eight accounts, and a weekend where both of them did a run that was half food and half everything else. Household sharing puts those accounts and budgets in one view, and line-item splitting is what stops that shared view from being a pile of transactions labelled with store names.

Start with one receipt

Pick the messiest receipt in your wallet right now — the one with the widest spread of unrelated items — photograph it, and look at what the split says your categories actually were. Then compare that to what a single label would have claimed. The gap is the size of the error you have been budgeting against.

PennySlice provides spending information, not financial advice.

Your bank statement says COSTCO WHOLESALE #1042, $341.86. Your expense app files it under Groceries. It is now the biggest grocery charge of the month, and it is wrong.

In that $341.86 there were rotisserie chickens and a case of olive oil, yes. There were also two pairs of kids’ jeans, a 30-pack of paper towels, printer ink, a tire rotation and a bag of dog food. Maybe $180 of it was actually food. The rest was clothing, household supplies, office, vehicle and pet — five categories that will now show $0 for the month, while Groceries carries their weight silently.

Do that four times a month and the distortion is not a rounding error. It is the reason your grocery number looks unmanageable and every other category looks suspiciously well behaved.

Why the bank feed can never fix this on its own

A bank transaction has three useful fields: date, merchant, amount. That is the whole payload. Whether the money came in through a linked account or a CSV you exported yourself, the bank does not know what was in the cart — the merchant’s payment terminal sent a total, not a manifest.

So every tool that categorizes from the bank feed alone is doing the only thing it can do: assign one merchant to one category and move on. Costco becomes Groceries. Target becomes Household. Amazon becomes whatever you told it Amazon is, which for most people is a shrug in category form.

This is fine for a coffee shop. It falls apart precisely at the merchants where you spend the most, because big box stores are cross-category by design. The whole retail model is that you came for milk and left with a lawn chair.

The line item is where the truth lives

The receipt has what the bank feed does not. Every line is a product, a quantity and a price, and the sum of the lines is the transaction. If you can read the lines, you can reconstruct exactly what that $341.86 was.

PennySlice does this with receipt OCR: photograph the receipt, and each line is read and categorized individually rather than the total being categorized as a block. One purchase becomes multiple categories, with the amounts adding back up to what actually hit the account.

The practical output is that the $341.86 stops being a mystery and becomes a breakdown — groceries, clothing, household, and the rest, each landing in the category it belongs to. Nothing has been estimated or apportioned by percentage. The numbers come from the receipt.

How to split a Costco receipt between categories

The mechanics are short, which is the point.

1. Keep the receipt. This is the only step that requires a habit. The warehouse receipt is long and your instinct is to bin it at the door. Photograph it in the parking lot instead.
2. Photograph the whole thing. Flatten it, get the full column of line items in frame. Receipt OCR reads the itemized lines, so a shot that clips the bottom third clips the bottom third of your data.
3. Let the lines categorize. Each item is assigned on its own. Food goes to groceries, the jeans go to clothing, the paper towels go to household. You are not picking a template or mapping columns.
4. Correct what it got wrong. It will not be perfect on every obscure product code. Fix the ones that matter. Corrections feed back into the shared model, so the same product is more likely to be right next time — for you and for everyone else using PennySlice.
5. Check the split matches the charge. The lines should reconcile to the transaction on your statement. If they do, that one purchase is now correctly spread across multiple categories instead of inflating one.

The same applies to any big box store purchase. Costco is the sharpest example because the basket sizes are large and the category spread is wide, but a $90 Target run has the same problem in miniature, and it happens more often.

What changes downstream

Splitting is not tidiness for its own sake. It is what makes every number built on top of the data mean something.

Budgets stop lying. If your grocery budget is $600 and it is silently absorbing clothing and motor oil, you will blow it every month and conclude you are bad at food shopping. Split the lines and you may find groceries were $420 and the overspend was somewhere else entirely.

Anomaly detection gets a real baseline. Penny Spotter watches for category spending that breaks your own pattern. A category that is actually five categories in a trench coat has no stable pattern to break — the signal drowns in the mixing. Clean categories give the detectors something to detect.

Household spending becomes attributable. When two people shop at the same warehouse and one trip is kids’ clothes and the other is a month of food, a single Groceries line for both tells the household nothing. With shared accounts and budgets in one view, the split is what makes the shared view worth looking at.

Recurring cost creep is visible. The seven Spotter detectors include one for recurring costs that quietly rose. If the food portion of your warehouse runs has climbed 18% over six months, that is only visible once the food portion exists as a number.

When you do not have the receipt

You will not always have it. For past months the receipts are gone, and OCR cannot recover what you did not keep.

What you can do is work from the transaction history you already have. Pull your statements in as CSV, Excel, OFX or PDF — the file is read and its structure detected, with no template to pick and no column mapping — and then ask about the merchant directly. “How much did I spend at Costco in the last six months, and how does it compare to the six before?” gives you a figure to work with even without line detail. If you need to get those statements out of your bank first, the export guides for Canadian banks cover the click path for RBC, TD, Scotiabank, BMO, CIBC and National Bank.

From there the sensible move is not to backfill a year of splits by hand. It is to start splitting the trips from today forward, so that three months from now you have a real grocery number instead of a merchant total wearing a category label.

Ask what your groceries actually cost

The question worth asking is not “how much did I spend at Costco” — you know that, it is on your statement. It is “how much of that was food”. Photograph your next warehouse receipt and let the lines answer it.

PennySlice provides spending information, not financial advice.

Every Canadian bank lets you download your transaction history as a file, and most people never do it. That file is the difference between guessing at your spending and reading it: a dated, itemized record of every debit and credit in a range you choose, in a format a tool can actually parse.

Below is the path for the six largest Canadian banks, in the order most people bank with them. Interfaces change, so where a bank’s exact wording moves around, the general route is given instead of a button label that may already be wrong.

One note before you start: online banking usually keeps a limited window of history available for download — often somewhere between three and eighteen months depending on the bank and account type. If you want a longer run, export in chunks going back as far as the date picker allows, and pull older periods from PDF statements.

RBC Royal Bank

RBC’s online banking exposes download options from the account activity view rather than from a central export screen. You pick the account first, then the range, then the format. Both spreadsheet and accounting formats are offered.

1. Sign in to RBC Online Banking on desktop. The download options are more complete on the web than in the mobile app.
2. From your accounts summary, select the chequing, savings or credit card account you want.
3. Open the account activity or transaction history view for that account.
4. Look for a download or export control on that page.
5. Choose your date range. If you want everything available, set the start date as early as the picker allows.
6. Choose CSV for a spreadsheet-friendly file, or OFX/QFX if you prefer the accounting format.
7. Confirm the download and note where your browser saved the file.
8. Repeat for each account. Credit cards export separately from chequing.

TD Canada Trust

TD splits things between EasyWeb on desktop and the mobile app, and the export controls live on desktop. Each account is downloaded on its own, and TD offers both spreadsheet and accounting formats.

1. Sign in to TD EasyWeb in a browser.
2. Select the account you want from your accounts list.
3. Open the transaction or account activity view.
4. Find the download or export option on the activity page.
5. Select the date range you want. Check the earliest date the picker will accept before you commit — it may be shorter than you expect.
6. Choose CSV, Excel, or OFX/QFX depending on what you plan to do with the file.
7. Download, then confirm the file opened with the right account’s transactions in it.
8. Repeat per account, including each credit card.

Scotiabank

Scotiabank’s download is reached through the account details view. As with the others, the desktop site gives you the full set of format options while the app is mostly read-only.

1. Sign in to Scotiabank online banking on desktop.
2. Click into the account you want from your accounts overview.
3. Open the transaction history or account activity for that account.
4. Locate the download or export control.
5. Set the from and to dates for the period you need.
6. Choose CSV, Excel, or OFX/QFX.
7. Save the file.
8. Repeat for any other chequing, savings or credit card accounts.

BMO Bank of Montreal

BMO groups downloads under its own section of online banking rather than only on the account page, so you may be able to select the account and the range in one place. If you cannot find it there, the per-account activity view has the same option.

1. Sign in to BMO Online Banking on desktop.
2. Look for a transaction download or export area in the account services or account activity navigation.
3. Select the account you want to export.
4. Choose the date range. BMO’s available window varies by account type, so check the earliest selectable date.
5. Choose CSV, Excel, or OFX/QFX.
6. Download the file.
7. Repeat for each remaining account.

CIBC

CIBC exposes downloads from the account activity page, one account at a time. The spreadsheet option is the simplest if you plan to open the file yourself first.

1. Sign in to CIBC Online Banking in a browser.
2. Select the account you want from your accounts list.
3. Open the account details or transaction history view.
4. Find the download or export transactions option on that page.
5. Set the date range.
6. Choose CSV, or OFX/QFX if you want the accounting format.
7. Save the file and check that the date range in it matches what you asked for.
8. Repeat for other accounts and credit cards.

National Bank of Canada

National Bank’s online banking is available in French and English, and the export control may be labelled with the French term depending on your language setting. The route is the same either way: account, then history, then download.

1. Sign in to National Bank online banking on desktop.
2. Select the account you want.
3. Open the transaction history or account statement view.
4. Find the download or export option on that page.
5. Choose the date range you need.
6. Choose CSV, Excel, or OFX/QFX.
7. Download and confirm the file contents.
8. Repeat for each account.

Which format to pick

If you are only going to hand the file to a tool, any of the three works. If you want to open it yourself and look at it first, take CSV — it opens in any spreadsheet application and in a plain text editor, and you can see immediately whether the dates, descriptions and amounts came through the way you expected.

OFX/QFX carries a little more structure, including account identifiers and cleaner transaction typing, which can help when you are merging several accounts. Some banks label this option after the accounting software it was originally designed for rather than after the format. It is the same file.

Excel files are fine too, but they occasionally arrive with header rows, logos or summary blocks above the actual transaction table. That is not a problem for import, just something to be aware of if you open one and wonder why row one is blank.

Once you have the file

Drop it into PennySlice. There is no template to choose and no column-mapping step — the AI reads the file, works out which column is the date, which is the description and which is the amount, and handles the rest. CSV, Excel, OFX and PDF all go through the same path, as do forwarded emails and a photo of a paper receipt.

If you exported six files from six accounts, import all six. PennySlice treats them as one picture rather than six silos, which matters if your groceries land on a credit card and your rent leaves a chequing account.

What happens next is where the file stops being a spreadsheet. Categorization runs at the line-item level, so a single warehouse-store trip can split across groceries, clothing and household rather than being flattened into one category that is wrong for most of the total. Penny Spotter runs seven background detectors over the imported history — budget pace, category anomalies, recurring cost creep, predicted expenses, savings opportunities, income changes and merchant concentration — and surfaces what it finds without being asked.

Then you can just ask. Plain English, across transactions, accounts, categories, budgets, imports, receipts, predictions and what-if scenarios. “What did I spend at restaurants in Q1?” returns a figure from your own data, not a general observation about restaurant spending.

Importing a file requires no standing connection to your bank. If you would rather not repeat the export every month, linking is available on paid tiers in Canada and the US through Plaid — you enter your login at your own bank, and PennySlice receives a read-only token you can revoke at any time from either side. You can mix both: link one account, import the rest.

The Track tier is free forever and handles imports. Paid plans include a 30-day trial with no card required. Either way, start with one file — export a single account for the last three months and ask it one question. That is a two-minute test of whether the data tells you anything you did not already know.

PennySlice provides spending information, not financial advice.