Expenses
Income
Statement period
Used for the report title. Defaults to the min/max transaction dates once you import.
Bring in transactions
Choose how your bank statement gets in. All parsing happens locally in your browser.
Paste raw lines copied from your e-statement (any order of date / description / amount per line is fine — the parser looks for a date and an amount on each line). Review and fix the parsed table below afterwards.
Upload a CSV/TSV export from your bank. Pick which column is which after uploading.
Upload one or more PDF e-statements at once — mix banks freely, some locked and some not. Decryption happens locally via pdf.js; nothing leaves your browser.
Type and category are auto-suggested from your keyword rules (edit rules in Settings). Click a row's category to override, or use "Review uncategorized" to go through unmatched ones one at a time.
Categories, budgets & keyword rules
These map to the category rows in your iSaveMoneyGo CSV. Starter list & keywords are pre-filled from your example export — edit freely, changes are saved in this browser automatically.
Always ask for these merchants
Some merchants (e.g. Fliptech) get used for genuinely different things each time — no keyword can guess right. Transactions matching these terms are never auto-categorized; instead they're queued up in a popup right after import so you decide each one. One term per line, case-insensitive.
Exclude transfers to these people (shared expense tracking)
If someone else in your household (e.g. your spouse) tracks their own spending in a separate iSaveMoneyGo, money you transfer to them would get counted twice: once here as your expense, again when they log what they actually bought. Outgoing transfer transactions whose description contains one of these names are dropped from the import entirely, across any bank. One name per line, case-insensitive.
Bank Jago: exclude these "Transfer Masuk" sources
For Bank Jago statements specifically, incoming transfers ("Transfer Masuk") whose Sumber/Tujuan contains one of these terms are dropped from the import entirely — they never show up, not even as uncategorized. Use this for money moving in from your own other accounts (e.g. Fliptech) that isn't real income. Doesn't affect other banks. One term per line, case-insensitive.
Description cleanup (export only)
These phrases are stripped out of transaction descriptions only when writing the final CSV — the table on the Import page always keeps the full original text. One phrase per line, case-insensitive.
Merchant name shortcuts (export only)
If a description contains one of these (case-insensitive), the whole description is replaced with the short name — e.g. any description containing "google play" becomes just "Google Play". Runs before all other cleanup, and only affects the exported CSV. One per line, formatted as match text=>Short Name.
Monthly report
Incomes
Expenditures
Summary
Importing into iSaveMoneyGo
This file has 5 columns and no header row. When iSaveMoneyGo's "Assign Columns" screen asks what each column is, match them in this order:
Column 1 = Date · Column 2 = Description/Title · Column 3 = Withdrawals · Column 4 = Deposits · Column 5 = Categories
Two things worth testing on a small import before trusting this for everything: whether iSaveMoneyGo expects amounts as plain numbers like "50000.00" (what this file uses) vs. a different format, and whether the Categories column needs to already exist by that exact name inside iSaveMoneyGo or gets created automatically.
Preview
This is exactly what will be written to the CSV file.
Account
This data lives on your server's database now and is shared live between every account with access — there's no manual sync step anymore. If your spouse made a change on their device, just hit Refresh.