https://bugs.kde.org/show_bug.cgi?id=390681
--- Comment #3 from Thomas Baumgart <tbaumg...@kde.org> --- >From (an older version of) the OFX specifications: ---8<--- An FI (or its Service Provider) assigns an <FITID> to uniquely identify a financial transaction that can appear in an account statement. Its primary purpose is to allow a client to detect duplicate responses. Open Financial Exchange intends <FITID> for use in statement download applications, where every transaction (not just those that are client-originated or server-originated) requires a unique ID. An <FITID> also uniquely identifies the closing statement in <CLOSINGRS> and <CCCLOSINGRS>. Again, the OFX client should detect repeated closing statements (duplicate downloads) using these identifiers. FITIDs must be unique within the scope of an account but need not be sequential or even increasing. Clients should be aware that FITIDs are not unique across FIs. If a client performs the same type of request within the same scope at two different FIs, clients will need to use FI + <ACCTID> + <FITID> as a globally unique key in a client database. That is, the <FITID> value must be unique within the account and Financial Institution (independent of the service provider). ---8<--- You may want to get in touch with your bank to get this fixed. -- You are receiving this mail because: You are the assignee for the bug.
