Importing copies your bank statement into FINUXI so you can review it. It does not change your reports until entries are posted.
The import wizard reads a CSV or Excel file (or a connected Google Sheet), maps its columns, validates every row, checks for duplicates and shows a normalized preview. Nothing is written until you confirm, and importing never posts a journal entry.
Steps
- Choose the file (up to 8 MB) and the bank account it belongs to.
- Check the column mapping: either one signed Amount column, or separate Debit and Credit columns.
- Read the preview: ready rows, invalid rows with the reason, and duplicate signals.
- Fix invalid rows in the source file and re-upload, or continue without them.
- Confirm the import. The source file is kept for audit under Import history.
What you get
Valid rows arrive in Transactions for categorization and review; invalid rows are reported, not guessed.
Who can do this
Owners, admins, accountants and bookkeepers can make changes; managers and viewers can only view.
If something goes wrong
- Dates are rejected.
- Use YYYY-MM-DD or an unambiguous US date such as MM/DD/YYYY.
- Amounts are rejected.
- Amounts may contain only digits, separators and a decimal point; remove currency words or notes.
- Every row is invalid.
- Check the column mapping; the Date, Description and Amount columns may be assigned to the wrong headers.
Terms used here
- Duplicate signal
- Two imported rows that look like the same activity. Exact duplicates are skipped on import; possible duplicates are kept for a person to decide.