* Martin Michlmayr <[email protected]> [2019-04-17 23:01]:
> 1) when you send the check, you decrease the bank account. You then
> tell your bank importer script to ignore all entries where checks are
> cashed (it might be something like "CHECK POSTED"). This solves the
> deduplication problem, but imho doesn't give a satisfactory answer for
> the reconciliation step since it's difficult to get a list of all
> outstanding checks.
Ok, you could use flags for that.
When you write a check, you add a manual entry like this:
2018-12-20 * "Foo Bar" "Wrote check for Foo Bar"
check: 12345678
Liabilities:Payables 1000.00 USD
! Assets:Checking -1000.00 USD
And next month you import the bank data. You can now use flags to
find all outstanding checks:
select ANY_META('check'), position WHERE account = 'Assets:Checking' AND
flag = '!'
Note that this doesn't work at the moment due to this bug:
https://bitbucket.org/blais/beancount/issues/353/posting-flag-ignored-how-to-query-posting
And when you import the bank data, you change the flag from ! to *
when you see it on your bank statement. (Remember the deduplication
is already done by the importer ignoring the entry).
And that's it. That seems like the easiest workflow to me.
BTW, I didn't notice but Zack's and mine example used ledger-syntax
for metadata (; foo: bar); you have to drop the semicolon for
beancount.
--
Martin Michlmayr
https://www.cyrius.com/
--
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/beancount/20190417161246.GL1709%40jirafa.cyrius.com.
For more options, visit https://groups.google.com/d/optout.
