Andreas Pauley

I ran my standard set of reports using hledger from this branch - I had one transaction from 2018 that was off, and it was easy enough to adjust it....

Could this case be covered by naming the file in question using the `rfo` conventions? They are described here: https://github.com/apauley/hledger-flow#statement-specific-rules-files

Interesting use case - I haven't yet used auto postings. I'd like to add some to my personal journals so that I can run into the same issues you're describing....

Hi @ketzacoatl This sounds like something that you would structure with hledger subaccounts, using the normal hledger rules files. And I think [tags](https://hledger.org/hledger.html#tags-1) could also be useful here.

Sure, I was just looking through my own rules files. This contrived example can be put in a rules file. It has both a subaccount and a tag for `ProjectA`...

You can specify multiple accounts and amounts when you want to do a breakdown of one transaction: ``` if someregex comment project: ProjectA account2 expenses:Supplies:ProjectA amount2 80 account3 expenses:Supplies:ProjectA:Tax amount3...

Yes, this is in the rules file. There are lots of cool options: https://hledger.org/hledger.html#csv-rules I don't understand what you mean by "unique ID", are you talking about the regex/matcher? In...

Hi @ketzacoatl - hledger-flow already exposes all of the hledger functionality you mention. hledger-flow just runs hledger with a specific rules file. Here is a fuller example, where someone gets...

If you are lucky enough to have the information needed for a breakdown in your CSV files, then you can match on that for your accountN and amountN postings. In...

Hi @mwesten, thanks for these reports. I do not personally have a Windows system available. I would be happy to accept a pull request that fixes these issues if you...