How CSV import works in Vardon

Bulk Import turns CSV rows into Vardon transactions without sending them straight into the ledger unchecked. It is useful when a bank export uses unusual column names, mixes spending and income in one file, or needs fixed values such as region, card, or description added during import. You can open it from the ledger controls or through the Bulk Import keyboard shortcut described in the in-app shortcut guide.

The workflow is especially helpful for historical backfills. If you are moving away from spreadsheets or importing old statement data, you can map the structure once, review the rows, and upload checked transaction data into the workspace.

The first stage is Header Mapping. You choose or drop a CSV file, and Vardon reads usable headers before building a mapping canvas. Imported headers can connect to Vardon attributes such as Merchant, Amount, and Date. The importer can also use fixed labels for values that are not present in the file, such as default region, card type, or description.

Vardon expects important mappings before it lets you continue. Merchant, amount, date, region, card type, and one ledger branch all need clear treatment. Description is optional. Category is resolved later because category choices depend on the merchant and ledger mode. If a condition or label is incomplete, the importer blocks the next step instead of guessing.

The second stage resolves merchants and categories. That is where plain or inconsistent merchant values can be cleaned up and connected to the categories Vardon should use. The third stage is Review Imported Transactions. This is the last checkpoint before upload, showing the transaction rows that will be created.

Before uploading, check direction, date, merchant, ledger, region, category, and card. Credit repayments should be mapped deliberately as their own branch rather than mixed into ordinary spending. If dates, amounts, or categories are wrong at this point, fix the mapping before upload so the ledger history stays clean.

Once rows are uploaded, Vardon refreshes transaction and financial caches so imported activity appears across the transaction ledger, financial overview, and recent changes. Recent Changes can then help confirm that the import was recorded as a money-affecting action.

CSV import is not the only entry path. You can still use manual entry or linked-bank fetch review. The shared principle is the same: imported data should be inspected and corrected before it becomes part of your long-term financial record.

Next, use the related links on this page to move from overview to implementation: read the csv import landing page, explore transaction features, compare bank fetch review. Start with the page that matches your current job, then return to Features if you need wider product context. When comparing Vardon, remember that the marketing site is mobile-readable but the product remains a desktop app. Review pricing and the privacy policy before downloading, especially if you plan to import CSV files, connect a bank account, or keep long-term financial history in the workspace. Vardon is best evaluated as a system of records: each workflow becomes more valuable when transactions, budgets, funds, loans, and reports are kept current. If you only need a quick mobile balance glance, it may be more product than you need.