On Sunday, May 8, 2016 at 9:01:03 PM UTC-7 xen…@gmail.com wrote:
*The problem is that postings are inserted before the statement end in the next billing cycle (because of random delays in the charge processing systems) so the balance assertion can't be against any given date.* Necroing this thread: I fixed this annoyance in beancount_reds_importers <https://github.com/redstreet/beancount_reds_importers> (see README.md). Also see this article <https://reds-rants.netlify.app/personal-finance/automating-balance-assertions/>. Extract: The Balance Assertion Date The date of the balance assertion matters. Consider this example of an OFX file for a credit card: - posting date of first/last transactions: Jan 1 — Jan 31 - statement download date: Feb 8 Is Feb 8 a good choice to to assert balance? Typically not. subsequent OFX download might include currently uncleared transactions for Feb 6, which would invalidate and trip up the Feb 8 assertion, requiring manual intervention. smart dates: To attempt to avoid this, a good idea is to set the balance assertion date to either two days (fudge factor to account for pending transactions) before the statement’s end date or the last transaction’s date, whichever is later. beancount_reds_importers offers several choices for balance assertions, as a part of the importer configuration: - smart: smart date (default; see below). To choose a different fudge factor for smart dates, simply set balance_assertion_date_fudge in your config. - ofx_date: date specified in ofx file - last_transaction: max transaction date - today: today’s date If you want something else, simply override this method in individual importer. I use the smart option, and it has been consistent and dependable for me. -- 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 beancount+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/39972d1e-5475-4d9b-96d1-9a1d43cc9878n%40googlegroups.com.
