Posting dates

[redst...@gmail.com]

Currently in the Beancount Language Syntax, transactions can have dates, but individual postings cannot - the date associated with them is the transaction's date.

Would you be open to updating the language syntax so a date can be optionally specified for a posting like so:

2014-12-01 * "Annual Insurance payment for 2015"

    Liabilities:Credit-Card   $100

    2015-01-01 Expenses:Insurance

Perhaps the posting's date could become a part of its metadata (like "posting_date") so nothing else will be affected.

The motivation for this is, it's not uncommon to desire a different effective date for a leg or legs of a transaction. This allows for a compact an intuitive form. See [1] for more:

[1] https://github.com/redstreet/beancount_plugins_redstreet/blob/master/effective_date/README.md

[Martin Blais]

Yes, there already a task defined for this, this work will be done when tackling the more general transaction merging problem.
Look for the settlement proposal doc earlier on this list.

--
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 beancount+...@googlegroups.com.
To post to this group, send email to bean...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/c8cbb85e-67d6-4bf8-abcb-fd29e75f9ce1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[redst...@gmail.com]

Great, I'll look forward to it!

[benjamin....@gmail.com]

(Resurrecting this old thread...)

Hello,

Have you made any progress on this feature ?

I don't seem to find anything about it.

Thanks

[Martin Blais]

Nope.

To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/16161a45-05a6-4e14-bd8d-334020c1c641%40googlegroups.com.

[benjamin....@gmail.com]

Got you.

Is this feature request still valid or the design change would be too burdensome ?

I understand you probably don't have a need for it. And on the other hand the repercussions of such a feature would be non trivial so I'm curious.

[Martin Blais]

On Mon, Jul 30, 2018 at 7:56 AM <benjamin....@gmail.com> wrote:

Got you.

Is this feature request still valid or the design change would be too burdensome ?

Haven't had time; still makes sense to me. 

There's almost 6000 lines of ideas in the TODO file and 100's of open tickets. Here:

https://bitbucket.org/blais/beancount/src/tip/TODO

Just keeping my head above water.

To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/5a674499-4b5b-48f8-a15b-6d1670386158%40googlegroups.com.

[benjamin....@gmail.com]

I understand.

Thanks for the feedback :)

[trs...@tutanota.com]

One day Martin, I hope to know enough Python to maybe help you out with some of those. You've created a wonderful thing here and provided enough documentation (including thought processes to underlying development decisions) to make that possible.

I for one greatly appreciate not only all your work (code AND documentation), but the fact that you have also released the project as free software. Cheers, mate!

TRS-80
--
Securely sent with Tutanota. Claim your encrypted mailbox today!
https://tutanota.com

30. Jul 2018 22:59 by bl...@furius.ca:

To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/CAK21%2BhMXYwCKckiq-mEjxdhg%2B7nf0R_h_DL8YfGv0CcFHPuFTw%40mail.gmail.com.

[Martin Blais]

Thank you!

To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/LJ5wZ2n--3-0%40tutanota.com.