On Thursday, June 10, 2021 at 10:59:31 AM UTC-7 [email protected] wrote: > > I am less than enthusiastic about using the ISO8601 date format because > it is different from the records on my bank, credit, and debit card > statements. When I get a statement and attempt to reconcile my ledger > against the bank records, if an error should exist in my records, going > through hundreds of transactions trying to find the missing or erroneous > record is already a tedious process > > Reconcilation is tedious for sure. > 1) Balance assertions can really help, it lets you binary search postings > for the error. If your bank for example gives a balance on every > transaction, you can add balance assertions in a few strategic spots and > see which ones are failing. It'll let you quickly narrow down the range > where the error might be (the first spot the balances start failing). Those > also are "known good" starting points if you ever have a balance failing in > the future. >
+1. I'd go so far as to say if you're spending any significant amount of time reconciling in beancount, your process can likely be improved. Importing data often along with balance assertions is key. Related: writeup I recently did of automated balance assertions while importing data: http://reds-rants.netlify.app/personal-finance/automating-balance-assertions/ -- 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/f774ebf7-789d-4727-91ba-11393a2b8c2fn%40googlegroups.com.
