beancount-io
bea is the command-line interface for Beancount.io.
Create and edit plain-text Beancount ledgers, import bank exports, validate
accounts, run BQL queries, and generate financial reports. Local bookkeeping
needs no Beancount.io account. Optional AI assistance and hosted ledger
management use your Beancount.io credentials.
The Python distribution is beancount-io; its executable is bea.
Run bea --version and bea COMMAND --help to check the version and options
you have installed.
Contents
Install
Install bea once. You do not install Beancount, Beanquery, or Fava
yourself — bea manages a separate engine environment automatically.
# Installs software; needs Homebrew or uv plus network.
brew install bex-co/tap/bea # macOS and Linuxbrew — dual venv at install time
uv tool install beancount-io # anywhere with uv and Python 3.12+ — engine on first use
Optional Beangulp and Beanprice stay out of that base install. Enable them explicitly into the managed engine when you need ingest helpers or quote fetching:
# Needs network once; Beangulp also needs system libmagic.
bea engine enable beangulp # then: bea ingest identify|extract|archive …
bea engine enable beanprice # then: bea price … (not bea add price)
bea import --csv and bea add price work without those features. Ledger-skill
updates that still mention a separate Beancount install are tracked in milestone
m21.
| Channel | When the engine appears | After that |
|---|---|---|
| Homebrew | During brew install (frontend + engine venvs in the keg) |
Local commands work offline |
PyPI (uv tool / pipx) |
First local command that needs the ledger engine | Same environment is reused offline |
bea upgrade updates the frontend through its package manager and refreshes the
matching engine. If a first-use or upgrade provision fails, retry a local
command such as bea check once the network is available — do not
pip install beancount.
The default installation omits AI dependencies. For bea ask, install the
extra (or run it without replacing your bea):
# Installs software; needs uv plus network.
uv tool install 'beancount-io[ask]'
uvx --from 'beancount-io[ask]' bea ask --help
Quick start
bea --no-input init books --currency USD --date 2026-08-01 \
--opening-balance "Assets:Checking 1000"
cd books
bea add transaction "Coffee" --date 2026-08-02 \
--posting "Expenses:Dining 12.50" --posting "Assets:Checking"
bea check
bea format -i main.bean
bea list transaction --limit 10
bea report balance-sheet
The purchase leaves 987.50 USD in checking: the currency comes from the account and Beancount fills in the balancing posting. For a bank export, see the import guide; for your first month end to end, follow the tutorial.
Command map
| Command | Purpose |
|---|---|
bea init [DIRECTORY] |
Create a local ledger with common accounts |
bea add TYPE |
Append one of eleven directive types |
bea import SOURCE |
Preview or apply a bank CSV (--csv) or importer (--config) |
bea ingest OP |
Beangulp identify/extract/archive (needs bea engine enable beangulp) |
bea price |
Fetch quotes via bean-price (needs bea engine enable beanprice; not bea add price) |
bea list TYPE |
Inspect directives and filter transactions |
bea check |
Validate the complete ledger |
bea format [PATH…] |
Format to stdout (safe default); --in-place / -i rewrites, -o writes elsewhere |
bea query [BQL] |
Run a query or start the interactive BQL shell |
bea doctor OP |
Beancount's eleven diagnostic operations |
bea example |
Generate an example ledger history |
bea treeify |
Render an account column in any text as a tree |
bea report TYPE |
Overview, income statement, balance sheet, or trial balance |
bea balance [ACCOUNT…] |
Trial-balance subtrees for matching accounts |
bea ask [QUESTION] |
Ask about a local ledger through the hosted AI service |
bea cloud … |
Sign in and manage hosted ledgers |
bea engine status|enable |
Inspect or enable optional engine features (Beangulp / Beanprice) |
bea upgrade [--check] |
Check for an update or invoke the owning package manager |
Global options come before the command; --file selects the root ledger:
bea --file main.bean check
bea --json list transaction --limit 100
Every flag, default, and help string is listed in the generated command reference.
Exit codes
| Code | Meaning |
|---|---|
| 0 | Success, including previews and intentional duplicate skips |
| 1 | Ledger, schema, formatting-check, or other runtime failure |
| 2 | Bad arguments, missing file or input, missing optional dependencies |
| 3 | Authentication or permission failure, including a read-only destination |
| 4 | Conflict: concurrent change, import review required, or uncertain remote write |
The usage guide documents the full contract: JSON error shape, cloud HTTP mapping, prompts, and output exceptions.
Learn more
- Tutorial:
your first month, from
initto a month-end report. - Usage: the contract — targets, JSON envelope, exit codes, prompts, environment.
- Importing: no-code CSV import, rules, and Python importers.
- Reference: every command's usage, arguments, and options, generated from the code.
Development
# Clones the repo and syncs dependencies; needs git and network.
git clone https://github.com/bex-co/beancount-io.git
cd beancount-io/cli
uv sync --all-groups
uv run bea --help
make check-all
Python 3.12+, Typer, and Pydantic for the beancount-io frontend. The frontend
never loads Beancount, Beanquery, or Fava. The single beancount-io wheel
bundles helper/Fava sources as resources; a child process runs them with
automatically managed upstream dependencies. Retain NOTICE.fava and LICENSE.engine.
src/cli/ holds command UX; src/bea_engine/ and src/fava/ are engine-side;
tests/ the pytest suite; docs/ the guides above; openapi/v1.json the
pinned contract for hosted commands. make check-all is the handoff gate:
lint, deadcode, format-check, typecheck, test, spec-check, and docs-check. Do
not hand-edit generated API clients, command stubs, docs/REFERENCE.md, or
lockfiles; keep scratch files under tmp/.
See the package guide
for architecture boundaries and contribution rules.
Optional Beangulp/Beanprice are enabled with bea engine enable (see Usage);
ledger-skill onboarding updates remain milestone m21.
Releases
Releases ship to PyPI and Homebrew from cli-vX.Y.Z tags; the
release guide
holds the tagging procedure and one-time credentials setup.
License
Frontend: MIT © Beancount.io. Bundled ledger helper: GPL-2.0-only; vendored Fava retains its MIT notice. Vendored Fava attribution is preserved in NOTICE.fava.
Metadata
Release files for beancount-io 0.2.0
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_io-0.2.0.tar.gz | 611.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| beancount_io-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.2 MB
Release files / beancount_io-0.2.0.tar.gz
| Download URL | beancount_io-0.2.0.tar.gz |
|---|---|
| Size | 611.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
039651ce0e82f2b73220b74f2f892024e19e89dccae3496dfdf0355b4b349fcc
|
|
BLAKE2b-256 checksum How to use checksums |
102a19396d89f67597dab60c97ef22cd12004033129687be4d8ce7b6eee4e69d
|
| 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 12, 2026.
Transparency logRelease files / beancount_io-0.2.0-py3-none-any.whl
| Download URL | beancount_io-0.2.0-py3-none-any.whl |
|---|---|
| Size | 613.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b4031f249c074a886d44dfb12d9566c72d47b87285cebbb9856d571b079c3c74
|
|
BLAKE2b-256 checksum How to use checksums |
0c4e501beb2d01ae095d6138064198bfd6d66d35834f4a1077312c57919b84d5
|
| 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 12, 2026.
Transparency log