Here are the basics about the importers. I'd previously posted a quick
version here
<https://groups.google.com/g/beancount/c/JtE9JLQY3Og/m/OGvAQf2pAAAJ>.
The *investment importer* solves a number of issues including:
- stock and fund transactions including buys and sells (lot matching,
however, is left to the user)
- handles commissions, fees
- money market transactions are detected and use price conversions
instead of being held at cost, for simplicity
- balance assertions are extracted from the source when they exist. most
ofx files contain these. these are critical to ensuring integrity of the
import with no manual effort
- available cash computation
- produces price entries (many brokerages include ticker prices of all
active tickers in the account on the date of download, in addition to of
course, the prices gleaned from transactions)
- cusip to fund matching from user-supplied database (some brokerage
houses identify funds only by cusip or other custom tickers in the ofx)
The code is *designed to minimize the importer code necessary* to account
for variances in ofx format across brokerage houses
The *banking importer* is pretty basic. Currently, it produces only a
single posting per account, with the assumption that the other posting(s)
will be automatically filled in by smart_importer.
*Readers include ofx and csv*. Either importer can mixed and matched with
either source. Readers:
- use filename extension and filename matching to quickly identify
mismatches to speed up bean-identify and bean-extract
--
You received this message because you are subscribed to the Google Groups
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/beancount/0de19d89-b252-4576-a608-1e0542a0766an%40googlegroups.com.
