Re: Branching transaction import logic (i.e. partially automating imports)

I'm not familiar with beancount-importer, but this should work out of the box if you use smart_importer, with nothing for you to really do. As it says : smart_importer only works by appending onto incomplete single-legged postings So in the import

Re: Branching transaction import logic (i.e. partially automating imports)

Thinking about your question further: I find that when I import transactions, credit cards are the only ones that deal with expenses and need categorization. I find that smart_importer gets almost all of them right. I do skim through the import as a part of my workflow, but it takes less than a

Copy-pasting multiline (multiple lines) query into bean-query

Hi, After doing bean-query foo.beancount to enter the interactive session, can I somehow copy-paste multiple lines in there? It seems like multi-line queries (e.g. the examples in the documentation), when pasted in there, always get split into one command per line, resulting in errors. Do I a

Re: Copy-pasting multiline (multiple lines) query into bean-query

This is a bash question. Look at how multiple lines are handled in bash (should be lots of info online). On Sat, Feb 10, 2024 at 9:24 AM Dan Andersson wrote: > Hi, > > After doing bean-query foo.beancount to enter the interactive session, can > I somehow copy-paste multiple lines in there? > > I

Re: Branching transaction import logic (i.e. partially automating imports)

Here's how I do it (from my import script): def process_entry(entry): ... do something... return entry def process_extracted_entries(extracted_entries_list, ledger_entries): """Filter the extracted entries to save on time.""" return [(filename, [process_entry(entry) for entry i

Re: Branching transaction import logic (i.e. partially automating imports)

Thank you all for super helpful answers! I hadn't realized that smart importer wouldn't touch already categorized transactions (obvious in retrospect though!). Thinking about it with that in mind, I'm going to give it a try: import -> rules -> smart_importer. >From there I'll pass everything to so

Re: Branching transaction import logic (i.e. partially automating imports)

Red - do you know if there's a way to have smart-importer mark (by tag or metadata) the transactions that it updates? If not I can probably just mark the ones categorized via rules, i.e. those not processed by smart import! I don't know unfortunately, but doing what you said (adding metadata