How bank connections work in Vardon

This workspace acts as a review area between your bank feed and your ledgers. Instead of sending imported activity straight into Vardon without checking it, you can inspect each row first. That gives you a chance to confirm the merchant, choose the correct ledger, and correct supporting details before adding the row to your records.

The workflow is useful when imported bank names are unclear, categories need adjusting, or a payment could otherwise end up in the wrong place. It is also useful when you want to keep bank activity separate from ledger history until you have reviewed it.

First, choose the connected account you want to work from. Then set a From and To date to define the sync window. When you press Sync, Vardon pulls activity from that account and shows fetched rows in the results panel. Each row can be expanded for review and adjustment.

The sync window can cover up to 90 days at a time. If the selected range is too wide, Vardon stops the sync and asks you to shorten it. If there is no activity in the chosen period, Vardon shows an empty result state for that window rather than adding anything automatically.

Fetched rows are not fixed. Before adding one to a ledger, you can review merchant name, destination ledger, and supporting details such as category, card, and region where they apply. The available fields change with the ledger you choose. Spending, Income, and Credit Repayment do not always need the same supporting details.

When a row looks correct, use the action button to send it into the chosen ledger. The button label updates to match the destination, such as Add To Spending, Add To Income, or Add To Credit. Check merchant name, amount direction, and ledger choice carefully before adding rows.

If no usable linked account is available, Vardon shows an empty state explaining whether you need to connect a bank, finish a pending approval, or fix a connection that needs attention. Where needed, it routes you back to Settings to reconnect or resolve access issues.

Open banking data is only accessed where you choose to connect an account. The available data depends on the permissions, provider, and bank connection you approve. The Privacy Policy names open banking providers such as GoCardless as one category of provider used when you choose to connect a bank account.

Next, use the related links on this page to move from overview to implementation: read the privacy and security guide, compare csv import, explore transaction tools. 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.