A reconnected bank feed imported dates you already reconciled

Before reviewing a reconnected feed, record the last reconciled statement date and balance. Identify the date range the new connection downloaded. Keep the old and new connection references so the reviewer knows whether two feeds point to the same real account.

Do not create a second ledger bank account merely because the connection was renewed. Confirm the software's supported reconnection process and the intended mapping. An account can appear twice in the interface while representing only one bank balance in the real world.

Intuit distinguishes matching a bank transaction to an existing record from categorizing it as a new record. Review which action applies before posting overlapping downloads. A suggested match still needs confirmation that it represents the same actual payment or receipt.

Use bank references, dates, amounts, and the existing payment trail. A recurring $500 charge can occur legitimately every month. Similar amounts alone are not enough to exclude a transaction, especially if the new download includes both historical overlap and genuinely new activity.

An item already recorded and reconciled may need to be handled as a duplicate download through the platform's appropriate workflow, not deleted from the ledger. Ask the accounting owner to approve any change affecting a completed reconciliation. Preserve the statement and original reconciliation report.

For an illustrative overlap covering September 25 through October 5, separate September's previously reconciled records from October's new transactions. Review transfers and card payments on both sides so a duplicate is not removed from one feed while the corresponding record is recreated from another.

Reconcile the next statement and inspect the transition period for missing dates and duplicated amounts. A clean duplicate list does not prove the feed downloaded every legitimate transaction. Compare with bank-issued statements rather than relying only on the feed's success indicator.

Record the reconnection date, affected range, and approved handling. Review any automatic posting rules that ran during the overlap and correct their effects where needed. Keep the account mapping stable so the next reconnect does not repeat the same migration problem.