In plugins/imexporters/ofx/ofx.c there are the cases:
case OFX_BUYSTOCK:
AB_Transaction_SetTransactionKey(t, "BUY");
AB_Transaction_SetTransactionText(t, "Buy stocks or alike");
AB_Transaction_SetSubType(t, AB_Transaction_SubTypeBuy);
break;
case OFX_SELLSTOCK:
AB_Transaction_SetTransactionKey(t, "BUY");
AB_Transaction_SetTransactionText(t, "Buy stocks or alike");
AB_Transaction_SetSubType(t, AB_Transaction_SubTypeSell);
break;
Shouldn't the second Key and Text be SELL and Sell...?
Currently there doesn't seem to be anywhere in aqbanking that saves
the identity of a stock or mutual fund involved in a transaction
retrieved via ofx. In libofx, the security information is stored in
data.unique_id, data.unique_id_type, data.secname, data.ticker. There
are a few more fields described in ofx_container_security.cpp, but
they seem less important to me.
In order for gnucash to properly import a stock trade, it will need
at least one field that differentiates the security involved from the
account supplying the funds. Using data.unique_id should be enough,
but I'd also like to see data.ticker made available downstream of
aqbanking.
Also, I submitted a patch that was added to CVS for libofx this past
week that adds data.newunits and data.oldunits to the libofx
transaction data collection. These fields will make it possible to
deal with stock splits reported in an ofx data stream. I would really
appreciate these fields also being added to the appropriate places in
aqbanking.
Dave
--
David Reiser
[EMAIL PROTECTED]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Aqbanking-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/aqbanking-devel
