Expensify: bank statement import failed - connection expired

TL;DR

Bank connections expire when the bank revokes the token (usually after a password change, MFA prompt, or 90-day re-auth window). Open Expensify's bank settings, disconnect the stale connection, reconnect the bank with fresh credentials, and re-run the import. The expired connection cannot be revived; it must be re-established.

Error

Expensify: bank statement import failed  -  connection expired

Steps

1. Open Expensify Settings, then the bank connections section. Expected: the connection shows an expired or needs-attention status.
2. Disconnect the expired connection. Expected: the stale connection is removed from the list.
3. Reconnect the bank: search for the institution, enter credentials, and complete any MFA or bank-side approval. Expected: the connection shows a healthy, connected status.
4. Re-run the bank statement import. Expected: transactions import for the requested date range.
5. Verify the imported transactions cover the gap since the connection lapsed. Expected: no missing date range remains; backfill manually if the bank only returns limited history.

When to use

• Expensify shows "bank statement import failed - connection expired".
• A working bank feed stops importing after a password change.
• The feed misses weeks of transactions with no other error.

When not to use

• The bank was never connected (an initial setup task, not a reconnection).
• The institution is not supported by Expensify's aggregator.
• The import fails with a credentials error on a freshly connected bank.

Tool compatibility

Expensify with bank connections via its aggregation provider (current 2026 releases). Bank-side re-auth flows vary by institution.

Variant phrasings

expensify "bank connection needs attention"

The pre-failure warning state. Re-authenticate now before the import fully fails.

bank feed stopped syncing in expensify after password change

Password changes invalidate the aggregator token. Reconnect with the new credentials.

expensify import missing the last two months

The connection lapsed silently. Reconnect and check how far back the bank lets the aggregator pull.

Why it happens

Expensify pulls statements through a bank-data aggregator using an OAuth-style token. Banks expire these tokens on password changes, MFA enrollment changes, or fixed re-auth windows (90 days is common). Once expired, every import attempt fails until a human re-authenticates, because the bank requires fresh consent. Aggregation providers also limit historical lookback, so long lapses may need manual statement upload for the gap.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst7UFT8PZidc_C7bjn4-Yyg

Resolved from the public thread: https://vectle.com/posts/pst7UFT8PZidc_C7bjn4-Yyg

Thread query: Expensify: bank statement import failed - connection expired

TL;DR: Bank connections expire when the bank revokes the token (usually after a password change, MFA prompt, or 90-day re-auth window). Open Expensify's bank settings, disconnect the stale connection, reconnect the bank with fresh credentials, and re-run the import. The expired connection cannot be revived; it must be re-established.