Ah, perfect. Thanks for pointing me to it - I've even looked at that document before and missed that section.
-Aaron On Monday, November 30, 2020 at 3:51:45 PM UTC-5 [email protected] wrote: > Yes, this problem will be fixed in v3. > It's annoying me too. I'm currently porting the parser to C++ (almost > done) and will make corresponding changes. > See here: > > https://docs.google.com/document/d/1qPdNXaz5zuDQ8M9uoZFyyFis7hA0G55BEfhWhrVBsfc/edit#heading=h.72lcw09z1ob1 > > > > On Mon, Nov 30, 2020 at 11:33 AM Aaron Lindsay <[email protected]> wrote: > >> Martin, is allowing for different posting dates for different legs of a >> transaction natively in beancount something you would consider for v3? >> >> It is somewhat of an annoyance that some transactions post to different >> accounts on different dates in the real world (credit card payments sent by >> billpay from checking account, paper checks mailed from health/dependent >> care reimbursement accounts and later deposited, etc.). In beancount v2, >> this means you may have to 'lie' to reconcile accounts with conflicting >> balance assertions when a transaction needs to be on one side of a balance >> boundary in one account and not in the other because a given transaction >> can only have one date. Shifting the dates one way or the other can work >> around this, but can also involve shifting the dates of unrelated >> transactions which also need to be on one side or the other of the balance >> assertion. >> >> I'm attempting to update my finances more frequently to turn it from a >> monthly chore to to a quick daily habit (with a dose of automation for >> getting the transactions to the point where I can review them), and I'm >> running into issues like this more frequently. It also feels a little wrong >> to me to be keeping a record of my finances that differs from my banks' >> views of what happened. >> >> -Aaron >> >> p.s. To be clear, I'm guessing I can probably write a plugin to do this, >> I'm just wondering if it's something fundamental enough that you would >> consider putting support for it into the core of beancount. >> >> -- >> 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 view this discussion on the web visit >> https://groups.google.com/d/msgid/beancount/9b869b13-7a10-4aae-a77f-85193a678874n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/beancount/9b869b13-7a10-4aae-a77f-85193a678874n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/beancount/9809a0ba-3b76-4258-9b15-a816a664acfcn%40googlegroups.com.
