CSV transaction import for checked finance records

Vardon Bulk Import moves through Header Mapping, Merchant and Category Mapping, and Review Imported Transactions. Header Mapping decides where each CSV column, IF rule, or fixed label should land inside Vardon. Merchant and Category Mapping resolves merchant values and the categories they should use. Review Imported Transactions shows the final rows before upload.

This structure exists because CSV files are inconsistent. One bank might call a column Description, another might call it Details, and a spreadsheet might split money in and money out into separate fields. A useful import tool needs explicit mapping rather than assumptions hidden in the background.

When a CSV is loaded, Vardon reads usable headers and builds a mapping canvas. CSV headers can connect directly to Vardon attributes such as Merchant, Amount, and Date. Before moving forward, Vardon expects usable mappings for key fields such as merchant, amount, date, region, card type, and one ledger branch. Description is optional, and categories are resolved in the next step because they depend on merchant and ledger mode.

Fixed labels help when the CSV does not contain a value you still want on every row, such as a default region or card type. IF blocks let one imported column drive conditional values, for example when an amount or transaction type decides whether a row belongs in spending, income, or credit repayment.

Vardon validates each stage before allowing you forward. Missing mappings, incomplete IF rules, invalid dates, invalid amounts, and missing categories are caught before upload. That matters because a finance ledger becomes harder to trust when bad import assumptions are mixed into history.

Before uploading, you should check that preview and review rows match the real transaction direction, date, merchant, ledger, region, category, and card. Credit repayments are treated as their own ledger branch, so they should be mapped deliberately rather than mixed into ordinary spending.

CSV import sits alongside manual entry and fetched bank activity. It is especially useful for historical backfills, providers without a direct connection, older accounts, statement cleanup, and spreadsheet migration. Once rows are uploaded, Vardon refreshes transaction and financial caches so imported activity appears across the ledger, financial overview, and recent changes areas.

If you are choosing personal finance software because your data is already in exports, the import workflow is one of the most important checks to make. Vardon is designed to make that cleanup explicit, visible, and repeatable on desktop.

Next, use the related links on this page to move from overview to implementation: read the csv import help guide, explore transaction features, download vardon. 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.