Room for what matters.

Spending periods default to calendar months and are independent of salary or payment dates. Set a custom start date, end date, and total spending cap on the Home tab under “Set your plan”. You can edit an existing period’s dates or cap anytime without resetting or exporting your data. When modifying the cap, you can record a reason that is saved with a timestamp in your audit history. If you adjust dates, Finmonk previews which transactions and commitments fall into the updated window before you confirm.

Finmonk currently supports manual entry for spending and commitments, plus bank statement imports via CSV files with customizable column mapping and a preview review step. Automatic SMS reading, open banking aggregation, and live bank connections are not yet supported (planned for future stages). All files are parsed entirely in your browser before saving to your cloud account.

No. Finmonk is strictly a budgeting and decision-support companion. It never moves money, initiates bank transfers, connects to payment gateways, or offers financial or investment advice. You remain in complete control of your money in your bank accounts.

Your bank balance shows the total cash present in your account right now. Finmonk’s available allowance is a planning estimate: it takes your overall spending cap, reserves money for upcoming unpaid commitments (rent, EMIs, utility bills), and subtracts what you have already spent. Allowance is a safe-spending benchmark, not a guarantee of liquid cash in any bank account.

Upcoming commitments due in the current cycle are set aside upfront so you don’t accidentally spend that money. When marked paid, they move from unpaid commitments to spent, keeping your allowance accurate without double counting. Credit card purchases reduce your allowance immediately on the day you make the purchase, reflecting your spending commitment.

When you pay off your credit card bill or transfer funds between your own accounts, money is simply moving between accounts. The actual spending was already deducted from your allowance when the card transactions occurred. Counting repayments or internal transfers as new spending would deduct the same expense twice.

You can record cash transactions directly by selecting “Cash” as the payment method when adding spending. Refunds and credits offset your total spent amount or appear as credits. During CSV import, Finmonk checks transaction references, amounts, and dates to flag potential duplicates during the review step so you can exclude them before confirming.

The daily planning guide divides your remaining available allowance by the number of days left in the selected spending period. It gives you a pacing benchmark for how much you can spend each day without exceeding your cap. If you spend less today, the daily allowance increases for subsequent days; if you spend more, it automatically recalculates downward.

Planned saving is expected income minus your cap. The current saving estimate uses recorded income, spending and unpaid bills; missing records can change it. Retained saving records money you confirm you set aside. Unused allowance and postponed purchases do not prove money was saved.

You can download a complete JSON export of all your cycles, commitments, transactions, and audit history anytime under Settings, or use “Backup data” to create a versioned backup with preview and restore. Under Account $\rightarrow$ Data controls, you also have “Export for spreadsheet” to download clean, formula-protected CSV files. You can also permanently wipe all stored data using “Delete cloud account & data”. All data is strictly protected by Supabase Row Level Security (RLS) tied to your authenticated user ID; no other user can access your records. While communication uses encrypted HTTPS and authenticated tokens, no system can claim absolute security.

If a cloud save fails, Finmonk displays “Your latest changes haven’t saved. Try again” and keeps your form entries safely on screen so you can tap Retry without losing data. Technical details are kept in developer diagnostics. If records appear missing or stale, verify your network connection, refresh the browser session, or confirm you are signed into the correct account.