Thanks. I was afraid of that. But the first month shows me at least part of what's probably going on: The PDF credit-card statement lists some transactions as, for example, Feb. 3 -- but the downloaded transactions show it as Feb. 2. Some months that doesn't make a difference; but in others, it crosses the statement-end line.
I assume the only solution is to manually change the downloaded-transaction date to match the PDF statement? Or is there a more elegant solution? Thanks! On Saturday, January 19, 2019 at 10:41:50 AM UTC-5, Martin Michlmayr wrote: > > * TF <[email protected] <javascript:>> [2019-01-19 07:32]: > > I kind of assume the problem is some mismatch between the dates on > > the downloaded transactions and the statement date (e.g., perhaps > > some charges posted on 1/31/2018 but after the statement was > > generated?). > > > > Anyway, hoping there's a simpler way of zeroing in on the problem > > than going through all the PDFs for the year... > > I think that's exactly what you have to do for the months where it > doesn't match. Take a the PDF statement, your beancount entries and > perform a reconciliation... > -- > Martin Michlmayr > https://www.cyrius.com/ > -- 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 post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/86b1f33d-6f8a-478a-a6f9-fab068949791%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
