Importing expenses
Rather than typing every expense in, upload a CSV from your bank or payment provider.
The flow
- Upload the CSV. CoreX detects the delimiter itself and copes with files that carry a byte-order mark, so an export straight from a bank usually just works.
- Review the preview: the columns it found, the rows it parsed, and the column mapping it suggests.
- Adjust the mapping and set any defaults, such as the category to apply.
- Run a dry run to get a validation report without saving anything, or import for real.
Wise exports
A Wise transactions export is recognised automatically, with its columns mapped for you. Only outgoing transactions are imported, since money coming in is revenue, not an expense.
Importing twice is safe
Each imported row carries a reference back to its source transaction, and that reference is unique per workspace. Re-importing an overlapping file updates rather than duplicates, so you can re-run last month's export without double-counting. Expenses you typed in by hand have no reference and are never touched by an import.
Re-running an import
A recent upload is kept, so you can go back, change the mapping, and run it again without finding the original file. The raw file is stored privately, not on any public disk.