I might be missing something, but why not simply import it from your institution?
Else, doesn't it seem like a lot of trouble to insert a transaction when the date and amount are likely incorrect? On Monday, January 13, 2025 at 7:02:52 AM UTC-8 Brian Lalor wrote: > How do folks manage recurring transactions? I have written a Python > script that processes a recurring.beancount file with entries like > > 2024-05-30 R "Dividend Paid" "Interest" > rrule: "RRULE:FREQ=MONTHLY;BYMONTHDAY=-1" > Assets:Bank:Checking > 0.01 USD > Income:Bank:Checking:Interest > > I run that script with a target month and output the result to a per-month > ledger file that’s included in my main ledger: > > python ../../hacks/generate_recurring.py recurring.beancount 2025-01 > > 2025-01.beancount > > The result is an entry that looks like > > 2025-01-31 R "Dividend Paid" "Interest" > Assets:Bank:Checking > 0.01 USD > Income:Bank:Checking:Interest > > When I get confirmation of the date and amount of a transaction (which may > not be exactly on schedule or the same amount every instance), I update the > date, amount, and flag. When the transaction clears my bank, I mark it as > cleared with the * flag. > > This works, but feels kind of clunky. Although I don’t really love the > beangulp importer workflow, it’d be nice to have recurring transactions > “imported” as part of that process. > > — > Brian Lalor (he/him) > bla...@bravo5.org > > -- 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/b7c54c7c-788c-437e-89a9-12c09d89556cn%40googlegroups.com.
