Import an account statement while skipping its trailing summary rows

User intention

Import transactions from a CSV file into my account.

The intention is included in the agent’s input prompt alongside environment details and task instructions.

What breaks, and what should happen

Play Both

BeforeThe defect at the parent commit

0:00.00 / 0:00.00Frame 0 · Review the configured CSV preview

Watch the import mappings and transaction preview when Skip end lines becomes 2. The footer disappears, but the existing date and amount settings reset.

AfterThe same script once the merged fix is applied

0:00.00 / 0:00.00Frame 0 · Review the configured CSV preview

Skipping the two footer rows preserves the chosen field mappings, date format, Flip amount, and the three interpreted transactions.

How is it judged?

01 · Given

Restore the data and starting state.

In the CSV import modal for a semicolon-delimited statement, five preview rows are visible: three transactions followed by two invalid summary rows. The configured options map Posting to Date and Value to Amount, use DD.MM.YYYY, and have Flip amount checked.

02 · When

Perform the interaction.

The person changes `Skip end lines` from 0 to 2 to exclude the two summary rows.

03 · Judge

Rationale: Field mappings, date formats, and amount options determine how the statement's transactions are interpreted. Keeping those settings when trailing rows are skipped preserves the user's work on the same import.

Require

Changing Skip end lines removes the specified trailing rows from the preview while preserving the current field mappings, date format, and amount options. The remaining transactions retain their correctly interpreted values.