Where do you believe it should be? It'll be configurable, but I suppose it could be under Assets and/or Liabilities (could be two accounts if proper signs are needed).
On Sun, Dec 6, 2020 at 10:42 AM Chary Chary <[email protected]> wrote: > Martin, > > question: why in V3 you plan to place *Transfer *account under Equity ? > > > https://docs.google.com/document/d/1qPdNXaz5zuDQ8M9uoZFyyFis7hA0G55BEfhWhrVBsfc/edit# > > ==================================================== > > > > > > > > > > *One possible idea would be to allow optional posting dates, like > this:2020-01-19 * "ONLINE PAYMENT - THANK YOU" "" Assets:US:BofA:Checking > -2397.72 USD 2020-01-21 Liabilities:US:Amex:BlueCash 2397.72 USDwhich > would result in two transactions behind the scenes, like this:2020-01-19 * > "ONLINE PAYMENT - THANK YOU" "" Assets:US:BofA:Checking -2397.72 USD > Equity:Transfer2020-01-21 * "ONLINE PAYMENT - THANK YOU" "" > Liabilities:US:Amex:BlueCash 2397.72 USD Equity:Transfer* > > =================================================== > > In this case if somebody regularly checks his Net Worth, by performing > calculation Assets + Liabilities, then on *2020-01-20 *he will all of a > sudden find, that he now has *2397.72 USD *less (as they have been moved > to Equity) and on *2020-01-21 *he will find, that these *2397.72 USD *came > back, whilst in reality money have just been transferred from Checking > account to credit card > > I your early > <https://docs.google.com/document/d/1x0qqWGRHi02ef-FtUW172SHkdJ8quOZD-Xli7r4Nl_k/edit#heading=h.v7ixc4fx0f41> > document you were planning to place transfer account to *Assets*. Isn't > this more appropriate? > > In my eyes transfer account shall be under *Assets *or *Liabilities*, in > this case checking your net worth by using formula *Assets + Liabilities* > will not produce strange results, whilst your money go from one account to > another. > > Or am I missing something? > > Regards. > > On Monday, November 30, 2020 at 9:51:45 PM UTC+1 [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/452422a1-ef69-4785-832f-094cd81bf528n%40googlegroups.com > <https://groups.google.com/d/msgid/beancount/452422a1-ef69-4785-832f-094cd81bf528n%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/CAK21%2BhMH_t%3Dnb3Aq4mZxHucN1rzbDeg%3DPhtcW_Cxkyd_haFxtA%40mail.gmail.com.
