The place to do this would be in ingest, wouldn’t it? The ingest configuration is just Python, so one could conceivably write a module to assign accounts based on the incoming data. I know there was a module that would try to use ML to do that based on your account history.

If you don’t want to do that, another option is hledger. I used that for a while before deciding to switch back to beancount for its ingest process. However, considering I have made no progress on that over the last year, I might just go back to using hledger.

hledger’s ingest process is not as sophisticated as beancount’s. You can’t write arbitrary plugins like with beancount, but you can pattern match on the incoming text and assign accounts that way. You can also define automatic transactions in your books, which I found incredibly helpful for managing my budget.

You can easily create any kind of abstraction with beancount's programming interface [1]. I find it very comfortable, because I can manipulate the data structure directly (and not just the plain text as in e.g. vim).

For example, here is a plugin that I wrote to "delay" a posting of a transaction to another date via an intermediate ("transfer") account [2] and its tests [3] that solves a problem pretty similar to yours (I should someday package my plugins properly and maybe put them on PyPI, but I haven't had the time yet). The beancount documentations also has a list of existing published plugins [4].

[1]: https://beancount.github.io/docs/beancount_scripting_plugins...

[2]: https://linx.marussy.com/selif/v31rtbi5.py

[3]: https://linx.marussy.com/selif/tpwlujdk.py

[4]: https://beancount.github.io/docs/external_contributions.html

Sounds like you need to develop a plugin or take a look at existing ones (for example effective date [1] might be helpful)

[1] https://github.com/redstreet/beancount_reds_plugins/tree/mas...

I wrote a couple of small bash scripts for common entries to keep the typing to a minimum.

./purchase 10 AAPL 128.80