Data Verification Before Import

After completing the field mapping configuration, the system displays the Data Verification Interface. This final stage allows users to review all extracted transactions before they are permanently added to the internal ledger.

At the top of the screen, the system provides a reminder that income transactions are generally represented as positive values and expenses as negative values. Because banks may format exports differently, users must carefully verify that each transaction reflects the correct type and amount.

The interface presents a detailed table listing all transactions from the uploaded file. Each row represents a single transaction and includes the transaction date, the amount received or spent, and a description. Users should review this table carefully to confirm that amounts, dates, and descriptions match the original bank statement and that deposits and withdrawals have been interpreted correctly.

Each transaction includes a checkbox that allows users to control which entries will be imported. Users may select individual transactions or use the master checkbox at the top of the column to select or deselect all entries at once.

This selective control allows irrelevant or duplicate transactions to be excluded from the import.

When the review is complete, clicking the Import button at the bottom right of the screen finalizes the process and adds all selected transactions to the designated internal bank account. If adjustments are required, users may click the Previous button to return to earlier steps and modify file format settings or field mappings. This structured verification process ensures that only validated and approved transaction data becomes part of the organization’s financial records within RunSensible.