Field Mapping and File Configuration

Once the internal bank account is confirmed, the system directs the user to the Field Mapping Interface. This stage ensures that the structure of the uploaded file aligns correctly with RunSensible’s internal transaction fields. The interface is divided into two coordinated steps.

On the left side, users define the file format. The system first asks whether the first row of the file contains column headers. If the first row includes labels such as Date, Amount, or Description, the user should select Yes from the “Is the first row in your file a header?” dropdown menu, which is the default option. If the file starts directly with transaction data and does not include headers, the user must select No from the same dropdown menu. This selection determines how the system interprets the first row when processing the file.

Next, users must specify how transaction amounts are organized in the file. Some bank statements use a single column for amounts, where positive values indicate deposits and negative values indicate withdrawals. In this case, select one column from the “How many columns show amounts?” dropdown menu, which is the default option. Other statements use two separate columns, one for money received and another for money spent. In that case, select Two columns from the same dropdown menu. Choosing the correct option is important because it determines how the system identifies and categorizes deposits and withdrawals during the import process.

Users must also select the correct date format used in the file, such as MM/DD/YYYY or DD/MM/YYYY. This ensures that transaction dates are interpreted accurately and prevents formatting errors that could affect record accuracy.

On the right side of the interface, users map each column from the uploaded file to the corresponding system field in RunSensible. Required fields typically include Date, Amount, and Description. If the file uses a single amount column, that column must be mapped to the Amount field, and the system will rely on positive and negative values to determine transaction type. If the file uses two amount columns, each must be mapped separately to the Money Received and Money Spent fields. Completing this mapping process correctly ensures that all imported transactions are properly classified and recorded within the system.