fwiw I agree with Zoltan - with the exception of money market funds where `@ 1.00 USD` makes sense, it never makes sense to record the unit price in a transaction, as that is a derivative property of how much is actually paid. Similar to eg Quicken where the default is 'automatically calculate price.' Writing the unit price feels like a clear anti-pattern to me... unless I really wanted to track the rounding errors the bank is earning off me? I have scripts that normalize and rewrite transactions and I hack the output to manually export `@@ total_price USD` everywhere.
The main reason I record the unit price in commodities held at cost is to match how my brokers store/expose it. Makes it easy to cross-check with statements when needed or for lot matching when selling. A secondary but equally important reason is to catch errors during import. It’s all too easy to miss a new type of fee or such that the importer hasn’t seen, if the total price is “absorbed in”. With price conversions though (as opposed to commodities held at cost), as the OP says, it’s generally more important to have both sides of the transaction reflect what the banks see, the unit price is less important, and @@ is preferred. -- 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 visit https://groups.google.com/d/msgid/beancount/9af896ee-8771-456e-975d-8fc1d25a167en%40googlegroups.com.
