Today I tracked down a problem I've had with OFX import from Citi CC
(Costco).
I did a partial month import a couple weeks ago. Today I imported the
entire statement period (so had several transactions already present).
The import "lost" a new entry and "duplicated" an entry already imported.
The import bypassed the first fourteen (14) IDs in the file. However,
the 14th transaction had not been previously loaded. The 15th
transaction (which it loaded) was already loaded by the prior import.
Starting with the 16th transaction all the remainder loaded correctly.
Looking at the FTID numbers, I suspect that Citi assigns them by
YYYYMMDDxxxx where the YYYYMMDD is the transaction date and xxxx is a
sequential number for this file.
I've seen transactions for the same date appearing in random order (not
the order in which I remember the charges happening).
In this particular case, a couple more transactions for the last date
previously downloaded (partial statement period) appeared and were
assigned numbers earlier in the file than transactions already downloaded.
Hence, Citi assigned FTIDs do not stay with the transaction but are
assigned at download time.
The lesson for me is to not download a partial statement period.
The implication is that the FTID from Citi is not trustworthy for match
purposes.
--Steve
--
Stephen M Butler, PMP, PSM
stephen.m.butle...@gmail.com
kg...@arrl.net
253-350-0166
-------------------------------------------
GnuPG Fingerprint: 8A25 9726 D439 758D D846 E5D4 282A 5477 0385 81D8
_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
