On Thursday, February 12, 2026 at 1:48:55 PM UTC-8 [email protected] wrote:
On Tuesday, February 10, 2026 at 3:29:35 AM UTC+10:30 [email protected] wrote: I only do automatic lot specification so I'm not sure on the best approach to suggest, but I would presume your concerns are also easier to address by specifying date or label of a lot rather than a price, and let the more accurate price calculations run through. Neither of these really seem like plausible alternatives. When I submit a buy execution to my broker it gets filled like this: 2020-03-12 * "SMLF" #20200228-tlh-rzv Assets:US:Interactive-Brokers 1000 SMLF {31.4550 USD, 2020-03-12} @ 31.455 USD Assets:US:Interactive-Brokers 400 SMLF {30.5350 USD, 2020-03-12} @ 30.535 USD Ah yes, I’d completely forgotten about this, which my transactions are full of as well. Yet another reason @@ doesn’t work. On a different note, how do you get 4 decimal points with Interactive Brokers? Looking at my journal, I seem to get two through their flexquery downloads. FWIW, I've never had my broker display different per-unit pricing in different reports. It is conceivable Vanguard does but (at least until their big push for better IT in the early 2000s) they historically had the worst IT infrastructure among major brokers by a fair margin so I'd expect it to be limited to them. I wish I could say this were true. Take Fidelity whose IT infra hasn’t had the complaints that Vanguard has had. Until recently, they provided ofx, csv, and web display (ofx is gone now). Ofx had 5 digits, while csv/web has always had two. -- 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/89af5c06-15c2-470b-aa33-dc379dbf82b7n%40googlegroups.com.
