There's a ton of documentation on the importers, but it doesn't say much about how data actually gets from the extractor into beancount. The only thing I can find is a sentence that mentions that bean-extract "produces some Beancount input text to be moved to your input file".
Is the process of adding data to your Beancount input file intended to be a manual copy/paste one? If for some reason you need to re-import some data that you'd already imported and added to your beancount input file, is it your responsibility to manually go find the records in the input file that came from that import, remove them, and replace them with the new import data? Is there some method or tool for tracking or managing how the beancount input file is composed from all the sources? Let's say you run Beancount and it makes some decisions for you -- for example, matching asset sales with corresponding lots for cap gains computation. You use these to file your taxes. How do you make a record of those decisions and enforce that a later run of Beancount doesn't change them (e.g., if next tax year you switch to a different booking method)? Do my questions suggest I have the wrong mental model for using Beancount? 😬 thanks, eric -- 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/CAFXPr0uxo_V1NsjKJXHEUp0gXUroaQBhMSxxLuq6UGCJBg0YMQ%40mail.gmail.com.
