beancount-blue
- Github repository: https://github.com/mescanne/beancount-blue/
- Documentation https://mescanne.github.io/beancount-blue/
beancount-blue is a collection of plugins for the Beancount plaintext accounting tool. These plugins provide additional functionality to help automate and streamline your bookkeeping.
Plugins
This collection currently includes the following plugins:
- Amortize: Amortize expenses over a specific period. For example, if you pay for a yearly subscription, you can use this plugin to spread the cost over 12 months.
- Tag: Automatically add tags to transactions based on the accounts they involve. This can help with tracking and reporting on specific categories of income or expenses.
- UK Capital Gains: A flexible capital gains calculator that can be configured to handle different tax regulations.
- Clear Residual Lots: Automatically clear out small, leftover lots in investment accounts that can occur when using the
NONEbooking method. This helps keep your books clean and accurate.
Importers & ML Prediction
This package also includes a native API importer framework for syncing transactions from real-world banks and APIs (Monzo, Starling, and TrueLayer). It features a built-in Machine Learning Predictor that leverages a scikit-learn Logistic Regression classifier (SGDClassifier) to automatically learn from your existing Beancount ledger and predict the correct counter-accounts and payees for new transactions.
See the Importers Documentation for detailed instructions on configuring the ML predictor, CLI usage, and specific bank implementations.
Installation
To use these plugins, you first need to install this package:
pip install beancount-blue
Then, you can enable the plugins in your Beancount file by adding a line like this:
plugin "beancount_blue.amortize" "{...}"
For more detailed instructions and configuration options, please see the documentation.
Contributing
Contributions are welcome! If you have an idea for a new plugin or an improvement to an existing one, please open an issue or submit a pull request. See the contributing guidelines for more information.
Release files for beancount-blue 1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| beancount_blue-1.0.3.tar.gz | 259.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| beancount_blue-1.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 369.7 kB
Release files / beancount_blue-1.0.3.tar.gz
| Download URL | beancount_blue-1.0.3.tar.gz |
|---|---|
| Size | 259.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c3014ca823aefcf24390228a7e3fe07f451427913c354315779b8aab58e85d6b
|
|
BLAKE2b-256 checksum How to use checksums |
ec6f2a33d72e8f43f71a1c11e6bc9f54afa55a0bc48755bd25f3c6a9eae8c098
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 27, 2026.
Transparency logRelease files / beancount_blue-1.0.3-py3-none-any.whl
| Download URL | beancount_blue-1.0.3-py3-none-any.whl |
|---|---|
| Size | 110.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0f8c3ec60e520c1c8a33932cd323df155c58eb5a84a5f63050324dacb00a34e4
|
|
BLAKE2b-256 checksum How to use checksums |
881fc414eb36df06536b2d9c4acb6d39d1d036d7df304a33c1b7c6fd3dedc45a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 27, 2026.
Transparency log