Whenever I import an OFX bank file, it makes me approve the warning for every transaction! Where do change the setting that verifies a post date? Reproducible: Always Steps to Reproduce: 1. File, Import, OFX, 2. Choose account 3. (here you must click 'Continue' for every transaction!) Actual Results: Transactions were imported with the correct date from the bank. Expected Results: Transaction would have posted without any warning. Windows v7, Pro, all updates have been installed.
When I check with the bank that generates the OFX file, they feel it is the KMyMoney application causing this warning to appear. Can your team address this bug tomorrow, 6/14/13? Please reply as soon as possible. Thanks.
Can you provide a sample ofx file, devoid of any personal data?
Thank you sir - let me check with the bank. I doubt that I could just edit the file and save it because that may corrupt the structure. ** Have you or your staff imported an OFX file into your KMyMoney without this warning? **
I'll check with the bank. Thanks for the follow up! Dale On Fri, Jun 14, 2013 at 4:46 AM, Alvaro Soliverez <asoliverez@kde.org>wrote: > https://bugs.kde.org/show_bug.cgi?id=320928 > > --- Comment #2 from Alvaro Soliverez <asoliverez@kde.org> --- > Can you provide a sample ofx file, devoid of any personal data? > > -- > You are receiving this mail because: > You reported the bug. >
Hello support - I never received a reply to my question on your import of the OFX file - see below: ** Have you or your staff imported an OFX file into your KMyMoney without this warning? ** I suspect you are getting this same warning. It is very irritating! I don't believe my bank will strip out all confidential data, and I cannot because I'll corrupt the file! Please reply with your results so that I may continue to work with the bank.
I import lots of OFX, both files and direct connect, and I have never seen this warning. Please confirm the exact wording of the message. An OFX file is plain text. You only need to replace account numbers and change amounts if you care. You will not corrupt the file. I would be surprised if the bank will do anything for you, since KMM is probably not "supported" software. Also, please specify whether you are trying to import a file you have downloaded or are using OFX direct connect (mapping to the online account). Finally, please remember that all the people who might help you here are volunteers. We all want to help, but right now, we need a sample transaction. One more question - after you acknowledge the message, does the transaction import ok? Is all the data as you expect?
Jack has made the main points I was going to make. With free software like KMyMoney, there are no "staff', there is no income to pay them. It's a bit like a cooperative. - everyone plays a part, and that includes you. If you search these lists you will find advice on extracting helpful information. Above all, ensure you make a backup of any file you intend to edit. Allan On Jun 18, 2013 3:16 AM, "Jack" <ostroffjh@users.sourceforge.net> wrote: > https://bugs.kde.org/show_bug.cgi?id=320928 > > Jack <ostroffjh@users.sourceforge.net> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| > |ostroffjh@users.sourceforge > | |.net > > --- Comment #6 from Jack <ostroffjh@users.sourceforge.net> --- > I import lots of OFX, both files and direct connect, and I have never seen > this > warning. > Please confirm the exact wording of the message. > An OFX file is plain text. You only need to replace account numbers and > change > amounts if you care. You will not corrupt the file. I would be surprised > if > the bank will do anything for you, since KMM is probably not "supported" > software. > Also, please specify whether you are trying to import a file you have > downloaded or are using OFX direct connect (mapping to the online account). > Finally, please remember that all the people who might help you here are > volunteers. We all want to help, but right now, we need a sample > transaction. > One more question - after you acknowledge the message, does the transaction > import ok? Is all the data as you expect? > > -- > You are receiving this mail because: > You are the assignee for the bug. > _______________________________________________ > KMyMoney-devel mailing list > KMyMoney-devel@kde.org > https://mail.kde.org/mailman/listinfo/kmymoney-devel >
Thanks for the follow up. The exact message I encounter during my manual import is: 'Problem adding or matching imported transaction with id '': Unable to add transaction with invalid postdate' My bank offers 3 formats during the manual download: "QIF", "OFC", or a "CSV". It sounds like the OF? format is the richest so I have trying to import that one into KMyMoney, but would go with either of the others if it would be reliable. Regarding the test file, the bank will not change the data for a test file. I did spend some time with the Notepad text editor, and saved it as a text file, ANSI encoding, as well as Unicode encoding and it appears to work with Unicode. Still, I am not comfortable sending you a test file, so that is not an option. The best news: I did find some documentation on modifying the QIF Profile (Tools || QIF Profile Editor || Date tab) and I spotted a setup issue with the Date format. I changed it to match my QIF file (mm/dd/yyyy), and it appears to solve the invalid postdate warning on the QIF import. The OFX import is still a warning. Is there an OFX (OFC) Profile equivalent like the QIF I found? Thank you!
On Wed, 19 Jun 2013 04:02:42 +0000 <mdaleknochenmus@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=320928 > > --- Comment #8 from mdaleknochenmus@gmail.com --- > Thanks for the follow up. > > The exact message I encounter during my manual import is: > > 'Problem adding or matching imported transaction with id '': Unable > to add transaction with invalid postdate' > Ah, now we're getting somewhere! Your subject refers to 'valid postdate', but now we see it is 'invalid postdate'. > My bank offers 3 formats during the manual download: "QIF", "OFC", > or a "CSV". It sounds like the OF? format is the richest so I have > trying to import that one into KMyMoney, but would go with either of > the others if it would be reliable. Yes,for OFX, that is probably the case, but sometimes an institution does not implement it correctly, so it can be more tricky to diagnose. Also, some are dropping support since IBM dropped MsMoney. QIF is a simple format, and usually pretty straight-forward for statement import. KMM does support CSV import, which is a fairly recent addition. This needs a little more in the way of initial set-up, identifying which columns contain which fields, but the settings are retained. > Regarding the test file, the bank will not change the data for a test > file. I did spend some time with the Notepad text editor, and saved > it as a text file, ANSI encoding, as well as Unicode encoding and it > appears to work with Unicode. Still, I am not comfortable sending you > a test file, so that is not an option. > What might be worth trying is to create an empty file, named ofxlog.txt in your home directory, and try the download again. Then look in the file and see what dates it shows, You can also post it here but be sure to remove account numbers and passwords first. Leave those lines in place, but identify them, like 'password removed', etc. > The best news: I did find some documentation on modifying the QIF > Profile (Tools || QIF Profile Editor || Date tab) and I spotted a > setup issue with the Date format. I changed it to match my QIF file > (mm/dd/yyyy), and it appears to solve the invalid postdate warning > on the QIF import. The OFX import is still a warning. That shouldn't be necessary as KMM now attempts to identify the format. If there is any ambiguity, it outputs the relevant formats to allow you to select the correct one for that file. > Is there an OFX (OFC) Profile equivalent like the QIF I found? I believe not, as, I understand, the standard specifies the date format to be used. > Thank you! > Allan
First, please confirm that you are downloading an OFX file and then doing File/Import in KMM. If that is correct, then Alan's suggestion regarding the file ofxlog.txt will not help. In that case, one thing you might do is look into the OFX file for the ID listed in the error message. If you find that, look for any tag (something within <>) that mentions date or post-date, and post here that date. However - what is the date of a transaction getting the error message? What is the opening date of the account you set up in KMM? I'm not certain, but you might get that error if the transaction is earlier than the account opening date. Also - it is not clear to me if the date itself is somehow invalid, or if the date format is invalid. It would help if we could figure out which.
On Wed, 19 Jun 2013 13:25:01 +0000 Jack <ostroffjh@users.sourceforge.net> wrote: > https://bugs.kde.org/show_bug.cgi?id=320928 > > --- Comment #10 from Jack <ostroffjh@users.sourceforge.net> --- > First, please confirm that you are downloading an OFX file and then > doing File/Import in KMM. If that is correct, then Alan's suggestion > regarding the file ofxlog.txt will not help. Apologies for that. I realised that a day or so ago, and then unrealised it. > In that case, one thing > you might do is look into the OFX file for the ID listed in the error > message. If you find that, look for any tag (something within <>) > that mentions date or post-date, and post here that date. > I read the ID as '', ie. empty, which probably because the error has already been discovered by KMM - that is , the date problem. > However - what is the date of a transaction getting the error > message? What is the opening date of the account you set up in KMM? > I'm not certain, but you might get that error if the transaction is > earlier than the account opening date. > > Also - it is not clear to me if the date itself is somehow invalid, > or if the date format is invalid. It would help if we could figure > out which. >
On Wed, 19 Jun 2013 13:25:01 +0000 Jack <ostroffjh@users.sourceforge.net> wrote: > https://bugs.kde.org/show_bug.cgi?id=320928 > > --- Comment #10 from Jack <ostroffjh@users.sourceforge.net> --- > First, please confirm that you are downloading an OFX file and then > doing File/Import in KMM. If that is correct, then Alan's suggestion > regarding the file ofxlog.txt will not help. In that case, one thing > you might do is look into the OFX file for the ID listed in the error > message. If you find that, look for any tag (something within <>) > that mentions date or post-date, and post here that date. > > However - what is the date of a transaction getting the error > message? What is the opening date of the account you set up in KMM? > I'm not certain, but you might get that error if the transaction is > earlier than the account opening date. > It seems possible to import a file with a pre-account-opening date without any error, but the file may not then be edited. > Also - it is not clear to me if the date itself is somehow invalid, > or if the date format is invalid. It would help if we could figure > out which. >
> I read the ID as '', ie. empty, which probably because the error has already been discovered by KMM - that is , the date problem. I can't imagine KMM would omit the ID of the transaction, since that would be the only way to find the error. We also still don't know whether the problem is with the date format or with the actual date. mdaleknochenmus - Is the transaction id empty in the error message, or did you drop it for security? Can you find the transaction in question in the OFX file and post the date it seems to be complaining about? Is it before the account opening date?
> It seems possible to import a file with a pre-account-opening date without any error, but the file may not then be edited. Which file, or do you mean the transaction? mdaleknochenmus - can you tell us which bank this is so perhaps other users of that bank can say whether they are having any similar problems?
On Wed, 19 Jun 2013 04:02:42 +0000 <mdaleknochenmus@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=320928 > > --- Comment #8 from mdaleknochenmus@gmail.com --- > Thanks for the follow up. > > The exact message I encounter during my manual import is: > > 'Problem adding or matching imported transaction with id '': Unable > to add transaction with invalid postdate' > > My bank offers 3 formats during the manual download: "QIF", "OFC", > or a "CSV". It sounds like the OF? format is the richest so I have > trying to import that one into KMyMoney, but would go with either of > the others if it would be reliable. > "OFC" is not "OFX", and that might have a bearing on the problem. According to http://money.mvps.org/faq/article/373.aspx - "OFC Specification Although OFC is no longer used in Microsoft Money, the specification can be downloaded from this website. [900kB Word Document] " I suspect that you will not succeed with that format, but it might be worth comparing the two. If, as it seems, you are actually downloading the file for import, could you show us the date format in it? Lines like <DTSERVER>20081114000026 or <DTACCTUP>20081114120027, if they exist. > Regarding the test file, the bank will not change the data for a test > file. I did spend some time with the Notepad text editor, and saved > it as a text file, ANSI encoding, as well as Unicode encoding and it > appears to work with Unicode. Still, I am not comfortable sending you > a test file, so that is not an option. > > The best news: I did find some documentation on modifying the QIF > Profile (Tools || QIF Profile Editor || Date tab) and I spotted a > setup issue with the Date format. I changed it to match my QIF file > (mm/dd/yyyy), and it appears to solve the invalid postdate warning > on the QIF import. The OFX import is still a warning. > > Is there an OFX (OFC) Profile equivalent like the QIF I found? > > Thank you! > Allan
On Wed, 19 Jun 2013 17:35:11 +0000 allan <agander93@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=320928 > > --- Comment #15 from allan <agander93@gmail.com> --- > On Wed, 19 Jun 2013 04:02:42 +0000 > <mdaleknochenmus@gmail.com> wrote: > > > https://bugs.kde.org/show_bug.cgi?id=320928 > > > > --- Comment #8 from mdaleknochenmus@gmail.com --- > > Thanks for the follow up. > > > > The exact message I encounter during my manual import is: > > > > 'Problem adding or matching imported transaction with id '': Unable > > to add transaction with invalid postdate' > > > > My bank offers 3 formats during the manual download: "QIF", "OFC", > > or a "CSV". It sounds like the OF? format is the richest so I have > > trying to import that one into KMyMoney, but would go with either of > > the others if it would be reliable. > > > > "OFC" is not "OFX", and that might have a bearing on the problem. > > According to http://money.mvps.org/faq/article/373.aspx - > "OFC Specification > > Although OFC is no longer used in Microsoft Money, the specification > can be downloaded from this website. [900kB Word Document] > " > > I suspect that you will not succeed with that format, but it might be > worth comparing the two. > > If, as it seems, you are actually downloading the file for import, > could you show us the date format in it? Lines like > <DTSERVER>20081114000026 or <DTACCTUP>20081114120027, if they exist. The date line in QFC files is like - " <DTCLIENT> and <DTSERVER> are used to specify date and time values. " > > > Regarding the test file, the bank will not change the data for a > > test file. I did spend some time with the Notepad text editor, and > > saved it as a text file, ANSI encoding, as well as Unicode encoding > > and it appears to work with Unicode. Still, I am not comfortable > > sending you a test file, so that is not an option. > > > > The best news: I did find some documentation on modifying the QIF > > Profile (Tools || QIF Profile Editor || Date tab) and I spotted a > > setup issue with the Date format. I changed it to match my QIF file > > (mm/dd/yyyy), and it appears to solve the invalid postdate warning > > on the QIF import. The OFX import is still a warning. > > > > Is there an OFX (OFC) Profile equivalent like the QIF I found? > > > > Thank you! > > > > Allan >
On Wed, 19 Jun 2013 04:02:42 +0000 <mdaleknochenmus@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=320928 > > --- Comment #8 from mdaleknochenmus@gmail.com --- > Thanks for the follow up. > > The exact message I encounter during my manual import is: > > 'Problem adding or matching imported transaction with id '': Unable > to add transaction with invalid postdate' > > My bank offers 3 formats during the manual download: "QIF", "OFC", > or a "CSV". It sounds like the OF? format is the richest so I have > trying to import that one into KMyMoney, but would go with either of > the others if it would be reliable. > > Regarding the test file, the bank will not change the data for a test > file. I did spend some time with the Notepad text editor, and saved > it as a text file, ANSI encoding, as well as Unicode encoding and it > appears to work with Unicode. Still, I am not comfortable sending you > a test file, so that is not an option. > > The best news: I did find some documentation on modifying the QIF > Profile (Tools || QIF Profile Editor || Date tab) and I spotted a > setup issue with the Date format. I changed it to match my QIF file > (mm/dd/yyyy), and it appears to solve the invalid postdate warning > on the QIF import. The OFX import is still a warning. > > Is there an OFX (OFC) Profile equivalent like the QIF I found? > > Thank you! > According to - http://support.microsoft.com/kb/890400 "The OFC format was replaced by the OFX format in 1997. The OFC format is supported by versions of Microsoft Money up to and including Microsoft Money 2004..." It might be worth asking your bank why they are so behind the times. Allan
On Wed, 19 Jun 2013 17:27:37 +0000 Jack <ostroffjh@users.sourceforge.net> wrote: > https://bugs.kde.org/show_bug.cgi?id=320928 > > --- Comment #13 from Jack <ostroffjh@users.sourceforge.net> --- > > I read the ID as '', ie. empty, which probably because the error > > has already been discovered by KMM - that is , the date problem. > > I can't imagine KMM would omit the ID of the transaction, since that > would be the only way to find the error. We also still don't know > whether the problem is with the date format or with the actual date. It hasn't yet got to the point of adding an ID as the checks are not yet complete. Near the beginning of MyMoneySeqAccessMgr::addTransaction(MyMoneyTransaction& transaction, const bool skipAccountUpdate) { // perform some checks to see that the transaction stuff is OK. For // now we assume that // * no ids are assigned // * the date valid (must not be empty) // * the referenced accounts in the splits exist // first perform all the checks if (!transaction.id().isEmpty()) throw new MYMONEYEXCEPTION("transaction already contains an id"); if (!transaction.postDate().isValid()) throw new MYMONEYEXCEPTION("invalid post date"); The failure occurs on the date check, so the ID has been checked and found to be empty, as expected. Had the date been correct, the ID would have been added later. Allan
Thanks for the update on the OFX v.s. OFC. I agree that the bank is behind on their coding, however, your PlugIn window shows "ofc" as a valid file type, so I felt it fair to use that option! Also, I did check the (open) Date for the account on it's General tab, and it was prior to the transactions I am attempting to import, so that is not the issue. Assuming that I do want to import an OFC file type, will there be a fix for this issue? It isn't clear what the status is for my request. It isn't clear to me if this is going to be programmed or not. Thank you.
I suspect not. If it were a new format, then it would be more likely, but it appears to be obsolete, MS having dropped it I'm favour of OFX nine years ago. I did find reference to a converter, but that indicated that as it didn't include a couple of needed. OFX fields, editing would be needed, and you didn't sound too confident in your ability. I think your best bet is one of the other formats. Allan On Jun 21, 2013 3:56 AM, <mdaleknochenmus@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=320928 > > --- Comment #19 from mdaleknochenmus@gmail.com --- > Thanks for the update on the OFX v.s. OFC. I agree that the bank is > behind on > their coding, however, your PlugIn window shows "ofc" as a valid file > type, so > I felt it fair to use that option! > > Also, I did check the (open) Date for the account on it's General tab, and > it > was prior to the transactions I am attempting to import, so that is not the > issue. > > Assuming that I do want to import an OFC file type, will there be a fix for > this issue? It isn't clear what the status is for my request. It isn't > clear > to me if this is going to be programmed or not. > > Thank you. > > -- > You are receiving this mail because: > You are the assignee for the bug. > _______________________________________________ > KMyMoney-devel mailing list > KMyMoney-devel@kde.org > https://mail.kde.org/mailman/listinfo/kmymoney-devel >
OK, thanks. Let's just drop it and I'll move on. On Thu, Jun 20, 2013 at 9:32 PM, allan <agander93@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=320928 > > --- Comment #20 from allan <agander93@gmail.com> --- > I suspect not. If it were a new format, then it would be more likely, but > it appears to be obsolete, MS having dropped it I'm favour of OFX nine > years ago. > I did find reference to a converter, but that indicated that as it didn't > include a couple of needed. OFX fields, editing would be needed, and you > didn't sound too confident in your ability. > I think your best bet is one of the other formats. > Allan > On Jun 21, 2013 3:56 AM, <mdaleknochenmus@gmail.com> wrote: > > > https://bugs.kde.org/show_bug.cgi?id=320928 > > > > --- Comment #19 from mdaleknochenmus@gmail.com --- > > Thanks for the update on the OFX v.s. OFC. I agree that the bank is > > behind on > > their coding, however, your PlugIn window shows "ofc" as a valid file > > type, so > > I felt it fair to use that option! > > > > Also, I did check the (open) Date for the account on it's General tab, > and > > it > > was prior to the transactions I am attempting to import, so that is not > the > > issue. > > > > Assuming that I do want to import an OFC file type, will there be a fix > for > > this issue? It isn't clear what the status is for my request. It isn't > > clear > > to me if this is going to be programmed or not. > > > > Thank you. > > > > -- > > You are receiving this mail because: > > You are the assignee for the bug. > > _______________________________________________ > > KMyMoney-devel mailing list > > KMyMoney-devel@kde.org > > https://mail.kde.org/mailman/listinfo/kmymoney-devel > > > > -- > You are receiving this mail because: > You reported the bug. >
On Fri, 21 Jun 2013 04:09:29 +0000 <mdaleknochenmus@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=320928 > > --- Comment #21 from mdaleknochenmus@gmail.com --- > OK, thanks. Let's just drop it and I'll move on. Just before that, there is just one point that puzzle me a bit. The file had been imported by libOFX, then the importer plugin without any objection to the date. It was only when the transaction was being added to the statement that it was noticed. I would be interested in taking a look at that, but would need your file, or an extract from it. You would need to disguise your account number and anything else of a sensitive nature. You'd need to take a backup first, of course, and then if a mistake is made, there's no harm done. I've also got hold of a routine to convert OFC to OFX, but again would need a file to test. Allan > On Thu, Jun 20, 2013 at 9:32 PM, allan <agander93@gmail.com> wrote: > > > https://bugs.kde.org/show_bug.cgi?id=320928 > > > > --- Comment #20 from allan <agander93@gmail.com> --- > > I suspect not. If it were a new format, then it would be more > > likely, but it appears to be obsolete, MS having dropped it I'm > > favour of OFX nine years ago. > > I did find reference to a converter, but that indicated that as it > > didn't include a couple of needed. OFX fields, editing would be > > needed, and you didn't sound too confident in your ability. > > I think your best bet is one of the other formats. > > Allan > > On Jun 21, 2013 3:56 AM, <mdaleknochenmus@gmail.com> wrote: > > > > > https://bugs.kde.org/show_bug.cgi?id=320928 > > > > > > --- Comment #19 from mdaleknochenmus@gmail.com --- > > > Thanks for the update on the OFX v.s. OFC. I agree that the bank > > > is behind on > > > their coding, however, your PlugIn window shows "ofc" as a valid > > > file type, so > > > I felt it fair to use that option! > > > > > > Also, I did check the (open) Date for the account on it's General > > > tab, > > and > > > it > > > was prior to the transactions I am attempting to import, so that > > > is not > > the > > > issue. > > > > > > Assuming that I do want to import an OFC file type, will there be > > > a fix > > for > > > this issue? It isn't clear what the status is for my request. > > > It isn't clear > > > to me if this is going to be programmed or not. > > > > > > Thank you.
The name of the bank is "FirstBank of Colorado". Please contact them to proceed. I apologize for sounding difficult, but I will not send you my file. Thank you for your efforts!
Just close the bug then. On Jun 22, 2013 1:15 AM, <mdaleknochenmus@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=320928 > > --- Comment #23 from mdaleknochenmus@gmail.com --- > The name of the bank is "FirstBank of Colorado". Please contact them to > proceed. I apologize for sounding difficult, but I will not send you my > file. > > Thank you for your efforts! > > -- > You are receiving this mail because: > You are the assignee for the bug. > _______________________________________________ > KMyMoney-devel mailing list > KMyMoney-devel@kde.org > https://mail.kde.org/mailman/listinfo/kmymoney-devel >
Allan, Searched for the ability to "Close" as you requested, but couldn't find it! I changed the Status to something reasonable, so you'll have to take it from here. Dale