Guides / How to build

How to Build a Budget App: Categories, Transactions, Imports and Reports

Build a personal or household budget app: budgeting methods, transactions, CSV imports vs bank connections, handling money correctly, and privacy.

Mythex Team · 2026-09-29 · 5 min read

A budget app tells you how much you planned to spend in each category, how much you've actually spent, and what's left. To build one you need accounts, categories, a monthly budget per category, transactions, and a few clear reports. The two decisions that shape everything are your budgeting method and how transactions get into the app — typed in, imported from a bank's CSV file, or pulled through a bank connection. Start with CSV import; it gets you most of the value for a fraction of the work and risk.

This guide covers the software. It isn't financial advice.

Pick a budgeting method first

Your method decides the screens and the maths, so choose it before prompting.

Category limits are the easiest to build and understand. Zero-based and envelope budgeting need rollover logic: what happens to money left in a category at month end, and what happens when a category goes over.

What a budget app needs

Pages

• This month — each category with budgeted, spent and remaining; total income and total spent.
• Transactions — a list with date, payee, amount, category and account; filters and search; quick re-categorising.
• Import — upload a CSV, map its columns, preview, confirm.
• Budget setup — categories, groups (Housing, Food, Transport) and amounts per month.
• Accounts — current account, savings, credit card, cash, with balances.
• Reports — spending by category over time, income vs spending, month-to-month comparison. See how to build a dashboard for chart choices.

Data

• Accounts — name, type, currency, opening balance.
• Categories — name, group, sort order, archived.
• Budgets — category, month, amount.
• Transactions — account, date, payee, amount, category, note, import ID, cleared.
• Rules — "payee contains TESCO → Groceries", applied on import.
• Transfers — a pair of linked transactions between two of your own accounts, so moving money to savings isn't counted as spending.

Permissions

A personal budget has one owner. A household budget needs a shared household that owns the data, with each partner logging in separately. Either way, nobody outside that household may ever see a row. Test by signing in as a second, unrelated user.

Getting money right

Finance apps fail in small, embarrassing ways. Put these rules in your prompt:

• Store amounts as integers of the smallest unit (cents, pence) plus a currency code. Floating-point numbers produce totals like 0.30000000000000004.
• Signs are consistent. Spending is negative, income positive, or use a separate direction field — but never both.
• Transfers aren't spending. Link both sides of a transfer and exclude them from category totals.
• Refunds reduce spending in the original category rather than counting as income.
• Months follow the user's time zone, so a transaction at 11 pm on the 31st doesn't land in the next month.
• One currency per budget for the first version. Multi-currency needs exchange rates and a decision about which rate to use.

Getting transactions in

With CSV import, prevent duplicates: store an import ID or a fingerprint of date, amount and description, and skip rows already seen. Apply categorisation rules on import so most rows arrive categorised.

If you do add a bank connection later, the provider's API keys must stay on the server, and you should never ask users for their bank passwords. See how to keep API keys safe.

Example first prompt

Build a household budget web app for two people. We use category limits: categories are grouped (Housing, Food, Transport, Fun, Savings), each with a monthly budget amount. The home screen shows this month: budgeted, spent and remaining per category with progress bars, plus total income and total spending. We have several accounts (current, savings, credit card). Transactions have date, payee, amount, account, category and note. Store amounts as integer cents with a currency code. Transfers between our own accounts are linked pairs and don't count as spending; refunds reduce spending in their category. Add CSV import: upload, map columns once per bank and remember the mapping, preview, skip duplicates, and apply payee rules like "contains TESCO → Groceries". Reports: spending by category per month and income vs spending for the last 12 months. We each log in with email and password and share one household; no one else can see our data. Database-backed, phone-friendly.

Build steps

1. Categories and this-month view with sample data. Check the maths by hand on a small set.
2. Transactions list and quick categorising. Make changing a category a single tap.
3. CSV import. Try real exports from your own bank. Import the same file twice and confirm nothing duplicates.
4. Rules. Add the ten payees that cover most of your spending.
5. Transfers and refunds. Test both and check category totals.
6. Login and household. See how to add login to your app.
7. Reports. Once there's a few months of data.
8. Security review. Run through the security checklist for AI-built apps before trusting it with real data.

Common mistakes

• Floating-point money. Use integer cents.
• Counting transfers as spending. Your savings contributions will look like overspending.
• Duplicate imports. Every re-import doubles your spending without a duplicate check.
• Starting with bank connections. A lot of work and risk before you know the app is useful.
• Storing bank passwords or card numbers. Never.
• No export. People want their data in a spreadsheet; add a CSV export.
• Too many categories. Twenty is plenty; three hundred is a spreadsheet.

When a ready-made budgeting app is better

Established budgeting apps offer secure bank connections across many institutions, mobile apps, and years of edge-case handling. If automatic bank sync matters most to you, one of them is the practical choice.

Build your own when your method doesn't fit their model, when you don't want your financial data held by another company, when a CSV import a couple of times a month is enough, or when you're building a budgeting tool for a specific group — a club's treasurer, a small charity, a coaching programme. If your budget currently lives in a spreadsheet, how to turn a spreadsheet into an app covers the move. For tracking business or team spending rather than a household budget, see how to build an expense tracker.

Building it with Mythex

Mythex can build this budget app from the prompt above: you describe it in chat, check it in the live preview, and publish it. It adds a dedicated Postgres database when the app needs one. Login is bring-your-own, and so is any bank-data provider: you'd store its keys as project secrets and the agent wires them in on the server. Mythex has no built-in bank connections. For a starting point, the budget dashboard template is built around CSV import and variance reporting.