-
Notifications
You must be signed in to change notification settings - Fork 504
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with generated accounts in Automated Transactions #2350
Comments
You write:
But this is not true. Your:
works just fine. You can verify this by running Although you say:
I see:
which makes sense because the 0.13 is applied to both accounts. In any case, you need to filter on both the tag and the account name. You can do this with:
The |
This ☝🏽 tracks! Thanks for clarifying. From the docs, I didn't know the argument to |
I'm not sure what you mean, but if you mean that it needs
|
tl;dr
When an automated transaction uses a complex query to specify the rule, if a new account gets introduced in that rule, this account is omitted from the balance report.
long form
Consider this simple transaction
A simple balance query shows
Now, let's assume this purchase is from a store which has the VAT baked in; but we want to know how much VAT we pay per purchase. A simple rule for an automated transaction would look like
Our balance query now yields
This makes sense… until we want to target VAT to certain postings. The
^Expenses
rule no longer works. We would need some complex query to properly target these postings. One way I thought of doing this is using tags. Our ledger now becomes…With this, the balance query looks like
…no sign of the
Expenses:Tax:VAT
account.When I shift the tag into the posting, like so
Note the posting is now applies to the Expenses directly. The balance query now reports
This is what I expect — 5 EUR out of this should be in
Expenses:Tax:VAT
— but there's noExpenses:Tax:VAT
listed in the balance report.When I try to switch out
= %/vat/
for= expr has_tag("vat")
,= expr has_tag(/vat/)
, or any other expression which isn't the short form, I getThe text was updated successfully, but these errors were encountered: