Why wasn’t a transaction linked to a journal entry updated?

Records already linked to a journal entry are automatically protected from any update through the AI bank statement import feature, even if you enabled the “Update Existing Records” option and the reference ID exactly matched a transaction in the uploaded file.

Why: once a transaction record is linked to a journal entry, the system considers it a final, accounting-complete record, so modifying it later could disrupt the accuracy of its related journal entries. Instead of updating it automatically, this row is classified on the review screen as “Invalid,” with the sub-classification: “Already matched to a journal entry.”

How to handle it:

• This type of invalid row can be inserted as a separate new record via the “Insert All Invalid Items as New Items” option on the review screen or ignored entirely via “Ignore All Invalid Items.”