How to Use:
Import Your Bank Statement via CSV
Get 6 months of financial history into Fin OS in one session — no manual entry required. Here's exactly how to download, map, and import your bank statement from any major Indian bank.
What You'll Learn
- How to download a CSV statement from HDFC, SBI, ICICI, Axis, and Kotak net banking
- How the AI column mapper handles messy bank export formats automatically
- What to do in the 5-minute review after import to fix the 10–15% of transactions the engine can't auto-categorize
What It Does
You do not need to manually enter a single historical transaction. Every major Indian bank exports statements as CSV or Excel files, and Fin OS's Universal CSV Intel engine can read them all. This guide gets you from zero to a fully populated 6-month financial history in under 15 minutes.
Who This Guide Is For
You want to populate Fin OS with historical transaction data rather than starting from scratch, or you want to regularly import bank statements instead of logging manually.
Download Your Bank Statement
Log in to your bank's net banking portal. Navigate to Account Statements or Transaction History. Select the last 6 months as your date range. Download as CSV format. If your bank only offers PDF, check whether they have a separate 'Export' option — most do. Banks confirmed to support direct CSV export: HDFC Bank, SBI, ICICI Bank, Axis Bank, Kotak Mahindra Bank, Yes Bank, IndusInd Bank.
For credit cards, download separately from your savings account. They are different accounts in Fin OS. Credit card statements often have a different CSV format than savings account statements — the app handles both.
Open the CSV Import Screen
In Fin OS, navigate to Accounts → [Account Name] → Import → CSV. Tap 'Select File' and choose the CSV file you downloaded. The Universal CSV Intel engine will immediately attempt to auto-detect the format. For most major Indian banks, it will identify the Date, Description, Debit, and Credit columns automatically within 2–3 seconds.
If you're importing a credit card statement, make sure you've already created the credit card as a separate account in Fin OS before importing. The import attaches to whichever account you launch it from.
Verify or Correct the Column Mapping
After the auto-detection attempt, you'll see a column mapping preview showing which column in your CSV maps to which field in Fin OS. Check: Date (should be transaction date, not posting date), Description (the merchant name column), Debit Amount (money out), Credit Amount (money in). If any column is wrong, tap it and select the correct mapping from the dropdown. The preview table updates live so you can verify the mapping is correct before importing.
Some bank exports combine Debit and Credit into a single 'Amount' column with a sign (negative = debit). If you see this, map it to the 'Amount (signed)' option instead of separate Debit/Credit fields.
Review the AI Categorization Preview
After mapping, tap 'Preview Import.' The AI Pattern Recognition engine will have already categorized most transactions using merchant keyword matching. You'll see each transaction with its suggested category and a confidence indicator. Green = high confidence auto-categorized. Yellow = categorized but verify. Red = could not determine, needs manual category. Review all yellow and red items — this typically takes 3–5 minutes for 6 months of data.
You can tap any transaction in the preview to change its category before importing. Changes you make here also train the engine — next time it sees the same merchant name, it will use your choice automatically.
Complete the Import and Review Your Analytics
Tap 'Import [N] Transactions.' The import runs instantly. You'll see a summary: total transactions imported, categories assigned, and any duplicates detected and skipped (the Smart Merge engine prevents double-counting if you've already logged some of these transactions manually). After import, navigate to Insights → Account X-Ray for that account to immediately see your 6-month spending breakdown.
If you see a 'Possible Duplicates' warning, review each one. The engine is conservative — it flags potential duplicates rather than silently deleting them. You confirm which ones to skip.
Pro Tip
Import one account at a time rather than all at once. After each import, spend 5 minutes in Account X-Ray reviewing what the engine found. This incremental review is faster and more accurate than trying to fix all categorization errors across 6 accounts simultaneously.
Most Indian banks support CSV or Excel export through net banking. If yours only offers PDF, check if they have a separate 'Download' or 'Export' button in the statements section — it's often separate from the 'Print' button. If genuinely unavailable, you can still use Fin OS by logging transactions manually going forward, and entering your current balance as your baseline.
The Smart Merge Engine detects potential duplicates by matching date, amount, and description. Any transaction already in your account with a matching signature will be flagged as a possible duplicate and skipped by default. You can review and confirm each skip before the import finalizes.
Yes. You can import a new monthly statement at the end of each month to supplement your manual logging, or use it as a reconciliation check. Each import runs the duplicate detection so there's no risk of double-counting transactions you've already logged.
Ready to try it?
Download Fin OS Pro and put this guide into practice. Everything runs locally — private by design.
Get Fin OS Pro