How to find spending leaks, the small charges that add up

A spending leak is a small charge that repeats without a decision, and it hides because each instance is too small to notice and the category it lands in is too broad to show it. Sort ninety days of transactions by merchant instead of by category, and the leaks appear as single lines with a count and a total: thirty-eight visits to one coffee shop, twenty-two delivery orders with their fees, nineteen stops at the convenience store. Four such lines in the worked example come to $214 a month. Each is stopped not by resolving to be careful, which fails by the second week, but by a rule about how often, which needs no willpower once it is set.

Why leaks are invisible in a category budget

A category budget shows dining out at $380 for the month, which is a number about a category. It does not show that $71 of it was one coffee shop, thirty-eight times, or that $70 was fees and tips on delivery orders whose food was another $140. The category is the sum of decisions and non-decisions together, and the leak is the non-decisions.

Sorting by merchant separates them. A merchant with thirty-eight transactions in ninety days is a habit, and a habit's total is a number that can be compared with what the habit is worth. Most leaks survive because their per-visit cost is small and their count was never seen.

Find them by merchant

1. Take ninety days of transactions from every card and account, with transfers removed.
2. Group them by merchant, and for each merchant note the count and the total.
3. Sort by count. The leaks are the merchants with the most transactions, not the largest totals; a large total with three transactions is a purchase, and a modest total with thirty is a leak.
4. Divide each total by three for the monthly figure, and ask of each whether the count is a decision you made or a habit you drifted into.
5. Separate the fees from the goods where a merchant charges both, delivery and rideshare especially. The fee line is often the leak even when the order is not.

A worked example, four leaks in ninety days

Two hundred and fourteen dollars a month, none of it decided. The coffee is a workday habit at three times a week, the delivery fees are the cost of not planning dinner, the convenience stops are the second grocery trip in miniature, and the app purchases are a tap each. The category budget showed dining at $380 and shopping at $310 and none of this.

Stop each one with a rule about frequency

A resolution to spend less on coffee lasts until the second Tuesday. A rule about frequency lasts, because it can be counted and it requires no judgment at the moment of the purchase.

• Coffee: bought twice a week, brought from home the other days. The count falls from thirty-eight to about twenty-six, and the monthly figure from $71 to about $49.
• Delivery: twice a month, planned, instead of twice a week, unplanned. The fees fall from $70 to about $19, and the food that would have been delivered is cooked or picked up.
• Convenience stops: the weekly grocery list gets a line for snacks and drinks, and the stops end. Fifty dollars to about $10 for the occasional one.
• App purchases: a monthly cap of $10, checked once at month end. Twenty-three to $10.

The rules recover $126 a month, about $1,510 a year, and none of them removes anything entirely; the coffee is still bought and the delivery still happens, at a frequency that was chosen. See How to cut spending without a budget for the same rule applied to the largest categories rather than the most frequent merchants.

Check the count next quarter

A leak returns when the rule is forgotten, and the merchant view is how it is caught: the same ninety-day sort, once a quarter, reading the counts. Coffee at thirty-five again is a rule that lapsed, and it is reset the same way it was set. New leaks appear in the same view, usually as a new merchant with a count above ten, and they get a rule when they are found.

Common mistakes

• Looking for leaks by category. The category shows the sum, not the count; the merchant view shows the habit.
• Sorting by total instead of count. The largest totals are rent and groceries, which are not leaks.
• Resolving to be careful. A resolution is tested at every purchase and loses; a frequency rule is set once.
• Cutting the leak to zero. The habit returns in a month; a frequency that was chosen holds.
• Missing the fees inside an order. The delivery fee and tip are a leak on top of a meal that may be a fine decision.
• Never rechecking. Leaks regrow; the quarterly count is the maintenance.

Common questions

What is a spending leak? A small charge that repeats without a decision: a daily coffee, a delivery fee, a convenience store stop, an app purchase. Each is small and the count is what makes it large, and the count is visible only when transactions are sorted by merchant rather than by category.

How much do small purchases really add up to? In the worked example, four habits came to $214 a month, or about $2,570 a year, from purchases averaging under $10. The figure is different in every household, and the merchant sort is how you find yours; there is no average worth quoting.

Should I cut out coffee entirely? No, unless you want to. Set the frequency you would choose on purpose, twice a week rather than five times, and keep it. Cutting to zero fails and takes the tracking with it; a frequency you chose holds because it was chosen.

How do I stop delivery fees without giving up delivery? Decide the number of orders a month in advance, and plan the other dinners. The fees are the cost of the unplanned order, and the planned ones are a choice that costs what it costs.

Is a subscription a spending leak? It is the same thing in a different shape: a charge that repeats without a decision. It is found by interval rather than by count, and it is stopped by cancelling rather than by a frequency rule; see How to find every subscription you're paying for.

How Zypper handles this

Zypper's cash flow page has the merchant view built in. Pick any period, the last quarter for the ninety-day sort, and group by merchant to see who you are giving money to, with each row opening into its own chart and the transactions behind it, which is the count and the total on one line; group by category to see the sums the merchants roll into. Transactions are categorized automatically as they arrive, a merchant can be renamed once so its thirty-eight visits read as one name, and a rule can add a tag to every transaction from that merchant, so the leak's total is a filter on the transactions page from then on. See Cash flow, Managing and reviewing transactions, and Transaction rules for the details, or get started with Zypper to see your own counts.