[Kmymoney-devel] [kmymoney4] [Bug 320928] Warning of ": Unable to add transaction with valid postdate" during OFX import

[allan]

https://bugs.kde.org/show_bug.cgi?id=320928

--- Comment #16 from allan <agander93 at gmail.com> ---
On Wed, 19 Jun 2013 17:35:11 +0000
allan <agander93 at gmail.com> wrote:

> https://bugs.kde.org/show_bug.cgi?id=320928
> 
> --- Comment #15 from allan <agander93 at gmail.com> ---
> On Wed, 19 Jun 2013 04:02:42 +0000
> <mdaleknochenmus at gmail.com> wrote:
> 
> > https://bugs.kde.org/show_bug.cgi?id=320928
> > 
> > --- Comment #8 from mdaleknochenmus at 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
>

-- 
You are receiving this mail because:
You are the assignee for the bug.