[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 #9 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'
> 

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

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