> On Jan 15, 2025, at 3:22 AM, Red S <redstre...@gmail.com> wrote: > > I might be missing something, but why not simply import it from your > institution?
I use my ledger for planning and some amount of budgeting, not just recording what my bank thinks has happened. > Else, doesn't it seem like a lot of trouble to insert a transaction when the > date and amount are likely incorrect? My current process isn’t ideal, which is why I’m asking what others are doing. Last week got a utility bill with a payment due date of mid-February. Because I use a tool to bulk-generate recurring transactions for a target month, I now have a couple dozen projected transactions for the next 45ish days in my ledger that I don’t want to see when I look in Fava. Yes, I can apply date filters to limit the range, but those transactions are still going to show in other queries unless I limit the end date. It’s just working around those future entries that I’d like to avoid. Rather than bulk-generating recurring transactions once a month or so, I’d like to import them closer to when they’re projected to land, and avoid duplicates. This probably means working with beangulp, and I’m looking for existing tools or prior art for this type of thing. -- 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 visit https://groups.google.com/d/msgid/beancount/97F3246E-8E03-41CB-8003-338FB99C1B2D%40bravo5.org.
