When reconnecting an account, the Earliest Import Date is currently determined by the date of the transaction farthest in the future on the account, regardless of whether that transaction was imported via sync or entered manually.

This can lead to unexpected behavior. For example, if a user manually enters a future-dated transaction or splits a transaction across future periods, the Earliest Import Date is set to that farthest future date, potentially preventing expected historical imports.

For synced accounts, it would be more intuitive if the Earliest Import Date were based on the date of the most recent successfully imported transaction instead of the most recent transaction overall. Since imported transactions cannot exist in the future, this would ensure the date is always on or before the current date.