Import wizard's "Smartness"

[Christopher Singley]

On Tue, Oct 12, 2010 at 9:26 AM, Oliver Schinagl <oliver at schinagl.nl> wrote:
> well the csv file from my bank is pretty basic, date, myacct#,
> theiracct#, name, memo, credit/debit, amount (from the top of my head) I
> briefly checked chapter 12, but it mentions a lot about payments etc.
> Not sure what exactly you mean with this. So modifying the previously
> stated, I modified it to:
>
> <BANKACCTTO>
> <ACCTID>theiracct#</ACCTID>
> <ACCTTYPE>
> CHECKING
> </ACCTTYPE>
> </BANKACCTTO>

I just looked more closely at your original msg.  If the transaction
type is POS, i.e. point of sale, then really you shouldn't need
BANKACCTO (which would be used for e.g. an electronic funds transfer).
 Anyway this information would only be useful if you also owned the
target BANKACCTTO & had it set up in your software, which I'm guessing
is not the case here, since you said the transaction involved your
paying a 3rd party.

So ignore BANKACCTTO then & don't waste your time.  Sorry for the confusion.

For payments, as opposed to transfers, the targets are matched by
<NAME> or <PAYEE>.  You don't have enough data to construct a <PAYEE>,
and it's not necessary anyway.

The transformation you're doing now ought to be sufficient, I'd
suppose.  If the import blows up, then try deleting the whole
BANKACCTTO aggregate (which, if present, strictly speaking ought to
have a BANKID, even if it's blank)

Just keep an eye on the results of your Perl script, because it's
outputting invalid OFX.