How to Build a Finance Tracker with Notion | Manage your finances with ease! ✨

TL;DR

Tracking spending helps identify unnecessary expenses, improves budget planning, and supports long-term financial goals.

Briefing Cornell Notes

Briefing

A Notion-based finance tracker can turn messy month-to-month spending into a structured system—by linking an income/expenses database to monthly report pages and using formulas to calculate balances and spending progress automatically. The core payoff is a dashboard that shows starting balance, total income, total expenses, current balance, and “percent used” for each month, plus breakdowns by category and by income vs. expense type.

The session starts with why tracking matters: monitoring spending helps people spot unnecessary expenses, understand spending behavior, and improve budget planning. With clearer visibility into money coming in and going out, it becomes easier to set realistic goals (like saving for a phone or vacation), identify excessive spending (coffee is given as a personal example), and reduce it. The guidance emphasizes tracking everything—even small purchases like gum—because small costs compound over time. It also recommends categorizing expenses (food, transportation, entertainment, etc.) and reviewing those categories regularly (weekly, monthly, or quarterly). Finally, it suggests using rewards to stay motivated when savings goals are hit.

From there, the focus shifts to why Notion works well for finance tracking: it’s flexible enough to customize formulas, categories, and database structures instead of forcing users into a fixed app layout. The tracker design uses multiple linked databases: one for monthly reports (built as a gallery of months) and another for income and expenses (built as a table). The income/expenses database includes properties like type (income vs. expense), date, category, optional files for receipts, and an amount field. A crucial modeling choice is to store expenses as negative numbers and income as positive numbers, so totals and “money left” can be computed cleanly without splitting into separate databases.

The build process then walks through creating views that make the data usable: a “view all” table sorted by date, a “this month” filtered view grouped by type, and a “by month” view grouped by month. The monthly report pages pull everything together using Notion formulas—most importantly a mapped conditional sum that totals income or expenses related to that specific month. Additional formulas calculate current balance as starting balance + income + expense, and a progress-bar-style metric that estimates how much of available funds has been used (derived from expense divided by income plus starting balance, then rounded).

To make the system repeatable, the template adds monthly report templates that automatically include linked views for income/expenses by type and by category, filtered to the selected month. The final dashboard page arranges linked views into a two-column layout so users can click a month and instantly see balances, totals, and category breakdowns.

The session also promotes a more feature-rich “Ultimate Personal Finance Checker” template with added capabilities like budgets, due vs. paid expenses, transfer tracking, account tracking (savings, checking, cash, credit cards, investments), recurring costs, and debt tracking. A Q&A addresses category strategy (broader categories tend to be easier), charting limitations in Notion (suggesting third-party chart methods), and goal/reward tracking (often better handled with lighter, manual properties unless it’s debt/loans).

Cornell Notes

The finance tracker is built by linking an income/expenses database to monthly report pages in Notion, then using formulas to compute totals and balances automatically. Expenses are stored as negative numbers and income as positive numbers, making it straightforward to sum everything into a “current balance” per month. Monthly report pages use linked data plus mapped conditional formulas to calculate income, expenses, and current balance, along with a percent-used progress indicator. Linked views provide breakdowns by type (income vs. expense) and by category, filtered to the selected month. The result is a dashboard that updates as new transactions are added, without manual recalculation.

Why are expenses entered as negative numbers in this template, and what benefit does that create?

Expenses are stored as negative values (e.g., groceries as -100, rent as -800). Income is entered as positive (e.g., salary as 2000). This lets the template sum amounts directly to compute remaining funds and current balance without needing separate income and expense databases or extra cross-database math. The monthly report formulas then add starting balance + total income + total expenses to get the current balance.

How does a monthly report page know which transactions belong to it?

Each income/expense entry is related to the monthly reports database via a relation property. When creating transactions, the user tags them to the correct month (e.g., March 2024). The monthly report formulas then map over the related income/expense items for that specific month, so totals like income and expenses reflect only the transactions linked to that month.

What formula pattern is used to calculate monthly income and expenses?

The template uses a mapped conditional sum. It maps over the related income/expense items, checks the item’s type using an if condition (type equals “income” or “expense”), returns the item’s amount when the condition is true, otherwise returns 0, and then sums the results. This produces the correct monthly total for income and separately for expenses.

How is the “percent used” progress metric calculated?

The progress metric is derived from expenses relative to available funds. It divides expense by (income + starting balance), takes the absolute value to keep the result positive, multiplies by 100, rounds, and then divides by 100 to produce a usable percentage. The template then displays it as a bar/percent-style visualization.

What views make the tracker practical for day-to-day use?

The income/expenses database includes a “view all” table sorted by date, a “this month” filtered view grouped by type (income vs. expense) with sums, and a “by month” view grouped by month (with empty groups optionally hidden). These views help users validate entries and see trends, while the monthly report dashboard provides the month-specific totals and category breakdowns.

How should categories be chosen to keep the system understandable?

The guidance favors broader categories (e.g., rent, utilities, food) to avoid overwhelming detail. If someone’s spending naturally splits further (like groceries vs. dining out), that extra granularity can work—but too many categories can make it harder to interpret where money is going. The recommendation is to try categories and keep what matches real spending behavior.

Review Questions

In this template, what changes if expenses are entered as positive numbers instead of negative numbers?
Describe how the relation between transactions and monthly reports enables the monthly formulas to work.
What are the three main Notion views created from the income/expenses database, and what purpose does each serve?

Key Points

1
Tracking spending helps identify unnecessary expenses, improves budget planning, and supports long-term financial goals.
2
Set realistic, motivating goals and break large targets into smaller milestones to stay consistent.
3
Categorize expenses (broad categories first) and review them on a regular cadence to spot patterns and cut back.
4
In the Notion finance tracker, store income as positive and expenses as negative to simplify totals and balance calculations.
5
Link each income/expense entry to a specific monthly report so formulas can compute month-specific income, expenses, and current balance.
6
Use mapped conditional formulas (with if conditions) to sum only income or only expenses for the selected month.
7
Add linked views and templates so each new month automatically generates filtered dashboards by type and by category.

Highlights

The tracker’s automation hinges on a relation: every transaction is tagged to a month, and monthly report formulas sum only the linked items.

Storing expenses as negative numbers makes “money left” and current balance calculations straightforward without extra database splits.

A mapped conditional sum (map + if + sum) calculates monthly income and expenses from related transactions.

The percent-used indicator is computed from expenses divided by (income + starting balance), then rounded for a clean progress bar.

Monthly report templates use linked views filtered to the selected month, so category and type breakdowns appear automatically.

Topics

Mentioned

Sarah
an