On Mon, May 11, 2020 at 3:29 PM jitin <[email protected]> wrote: > Hi, > > I have postings which are something like: > > 2017-04-03 * "someone" > Income:Sales:International -42.5 USD > Equity:Drawings 2524.68 INR > Expenses:Banking:PaypalCharges > > However Benacount reports them as 4 transactions in a non-intuitive way: > > Income:Sales:International -42.5 USD -42.5 USD > Expenses:Banking:PaypalCharges 42.5 USD 42.5 USD > Equity:Drawings 2524.68 INR 2524.68 INR > Expenses:Banking:PaypalCharges -2524.68 INR -2524.68 INR > > If however I add a price information to the posting like this: > > 2017-04-03 * "someone" > Income:Sales:International -42.5 USD @65 INR > Equity:Drawings 2524.68 INR > Expenses:Banking:PaypalCharges > > Beancount reports it as 3 transactions in the way I want: > > Income:Sales:International -42.5 USD 65 INR -2762.5 INR > Equity:Drawings 2524.68 INR 2524.68 INR > Expenses:Banking:PaypalCharges 237.82 INR 237.82 INR > > > I have already added price entries like this: > 2014-01-01 commodity USD > > 2015-08-30 price USD 66.15 INR > 2015-08-31 price USD 66.15 INR > 2015-09-01 price USD 66.35 INR > ... > > Is there any way for Beancount to pick up the price (the @65 INR part) > automatically from this price list according to the transaction date, > without me manually specifying the USD to INR price for each transaction? >
Not at the moment. Two reasons for this: - Balancing Beancount transactions can be mildly tricky, so limiting the effects to be local only to the data input to the transaction has been driving the design. Non-local effects of changes to the price database could be tricky to debug, e.g., you insert a transaction with a price attached to a posting, that inserts a price point in the database, and then a bunch of unrelated transactions break because the prices of their conversions is changed. (You could argue that reducing lots is a function of the inventory of the account prior to applying the transaction and that this is not local, sure, but notice that it's a bit tricky enough to resolve those at times.) - Generally speaking the rate at which a price conversion is made is an explicit specific number that is subject to being input in your transaction. I don't think it's common that one would want to use some arbitrary rate (but I'm not 100% sure). In your example, the actual PayPal charge is a precise number. Unless all you want is an approximation (I doubt it), you still have to input it. That being said, I think in a future version that could be considered, it's been requested frequently. > > Thanks a lot. > > -- > 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/def09727-5aa1-4490-b8ed-428bde58b5f9%40googlegroups.com > <https://groups.google.com/d/msgid/beancount/def09727-5aa1-4490-b8ed-428bde58b5f9%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%2BhPsoEYra3x-U6EDE8%3D3P%2BT76X4xv4q9tW8BKEsK48Th7g%40mail.gmail.com.
