Import files without damaging your books
Import files safely without creating duplicates, wrong categories, bad mappings, or damaged books.
How to use this
Choose the right lane
Select money, trade, price, billing, inventory, or another supported import lane.
Pick the file
Choose CSV, Excel, PDF, or supported file from device/import originals.
Map columns
Match file columns to app fields before review.
Review rows
Fix categories, sources, duplicates, dates, and amounts before posting.
Post clean rows
Post only ready rows; keep warning rows for correction.
Check target module
Review Entries, Investments, Billing, or Inventory after posting.
Guided walkthrough
Import file walkthrough
Open app to use guided helpDetailed guide
Do not use the wrong lane
Bank statements should not go through trade import, and contract notes should not become normal expenses.
Review mapping every time it changes
Profiles can save time, but review mapped columns before trusting auto-detection.
Treat warnings seriously
Duplicates, missing categories, missing sources, amount-sign issues, and blocked rows should be fixed before posting.
Check after posting
Open the target module and confirm records were created in the right place.
Before you finish, check this
- File lane is correct.
- Date and amount signs are correct.
- Duplicates are not posted twice.
- Categories/sources are reviewed.
- Import batch is traceable after posting.
Common mistakes to avoid
- Importing the same statement twice without duplicate review.
- Posting every suggested row blindly.
- Using the wrong lane for investment trades.
- Deleting originals before confirming posted results.
Related articles
Open this in the app
After the Flutter Web app is deployed, this article can deep-link to /import-center or to the matching in-app help topic.
Tags and coverage
Group: Import. This article is public help and does not access account data.