It's not really in a state that's easy for others to use TBH.
In theory it could be, but if you used it you'd be 90% sure to his some corner case that's not supported, e.g. some transaction type I've never encountered and don't support.
Broadly speaking, for that use case you need
- more sophisticated transaction types wit some common fields
- the volume of transactions is such you'd want this in a table format, one line per transaction, ideally going to a database. Beancount is designed to be user-editable and too verbose.
- you'd also want to automate everything (ingest the data from your brokers, normalize it in the same schema, etc) with as little manual intervention as possible.
- Beancount doesn't handle derivatives with multipliers too great right now (futures and options), you have to multiply by hand, its symbology has to be extended to support that (Johnny does that fine)
So Beancount is fine for investments, say ~100 equities or funds positions with dividends and monthly transactions, but when you're talking about 1k-100k or more trades/month - still retail level but a bit more dedicated - Beancount isn't a great solution for that.