Re: ofx max_date correct?

In case you guys were not aware, there is an effort to compare notes and experiences (including a forum), as well as a database of connection parameters over at OFXHome.[0] In fact many of the various OFX projects actually pull their particular connection information from there. But my

Re: ofx max_date correct?

Ditto, banks don't seem to be fully consistent on these. FWIW, for my importers , I use the following dates via ofxparse : - date of last transaction, used for filing via bean-file: I use

Re: ofx max_date correct?

I also noticed that balance statements have the wrong date with some (but not all) banks when using the beancount OFX, which matches exactly what you describe. * Frederick Noon [2020-10-21 11:38]: > Will-do. I found that my change matched the usage of at least 3 of the > institutions I was

Re: ofx max_date correct?

Will-do. I found that my change matched the usage of at least 3 of the institutions I was using, but didn't know how representative my sample was. On Wednesday, October 21, 2020 at 7:13:28 AM UTC-7 bl...@furius.ca wrote: > These importers are intended merely as examples and aren't supported as

Re: ofx max_date correct?

These importers are intended merely as examples and aren't supported as general importers. The OFX importer, in particular, is based on a particular use case and is not a general purpose thing that would work in every case. I suggest you use one of the OFX libraries on github to build yourself an

ofx max_date correct?

Advice requested... The off-the-shelf v2 *ingest/importers/ofx.py* uses the *DTASOF* value of the *LEDGERBAL* section as the file date. However, I find that this date is consistently the date I downloaded the data from my bank, not the closing date of the period I asked for. So if, in April,