Beancount ING Importer
beancount-ing provides an Importer for converting CSV exports of
ING (Germany) account summaries to the Beancount format.
Installation
$ pip install beancount-ing
In case you prefer installing from the Github repository, please note that
main is the development branch so stable is what you should be installing
from.
Usage
If you're not familiar with how to import external data into Beancount, please read this guide first.
Beancount 3.x
Beancount 3.x has replaced the config.py file based workflow in favor of having a
script based workflow, as per the changes documented here. The beangulp examples
suggest using a Python script based on beangulp.Ingest. Here's an example of how that
might work:
Add an import.py script in your project root with the following contents:
from beancount_ing import ECImporter
from beangulp import Ingest
importers = (
ECImporter(
IBAN_NUMBER,
"Assets:ING:EC",
"Erika Mustermann",
file_encoding="ISO-8859-1",
),
)
if __name__ == "__main__":
ingest = Ingest(importer)
ingest()
... and run it directly using python import.py extract.
Beancount 2.x
Adjust your config file to include the provided ECImporter. A sample configuration
might look like the following:
from beancount_ing import ECImporter
CONFIG = [
# ...
ECImporter(
IBAN_NUMBER,
"Assets:ING:EC",
"Erika Mustermann",
file_encoding="ISO-8859-1",
),
# ...
]
Once this is in place, you should be able to run bean-extract on the command
line to extract the transactions and pipe all of them into your Beancount file.
$ bean-extract /path/to/config.py transaction.csv >> you.beancount
Contributing
Contributions are most welcome!
Please make sure you have Python 3.9+ and Poetry installed.
- Clone the repository:
git clone https://github.com/siddhantgoel/beancount-ing - Install the packages required for development:
poetry install - That's basically it. You should now be able to run the test suite:
poetry run pytest tests/.
Metadata
Release files for beancount-ing 1.1.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 | Provenance | |
|---|---|---|---|---|
| beancount_ing-1.1.0.tar.gz | 5.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| beancount_ing-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.7 kB
Release files / beancount_ing-1.1.0.tar.gz
| Download URL | beancount_ing-1.1.0.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b1a35ffbbc53ec5e089ce7368250ae308e6c65473d0f4d5fd774982b8549c901
|
|
BLAKE2b-256 checksum How to use checksums |
16fc575ab9d1623d87cb62ec5fe5a7652885b96c02050d9ebc57c64f67a23bed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.0.0 CPython/3.12.9 Darwin/24.3.0
|
Release files / beancount_ing-1.1.0-py3-none-any.whl
| Download URL | beancount_ing-1.1.0-py3-none-any.whl |
|---|---|
| Size | 6.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
45abd541ba058b12eac7b9e3aa808ee1ca39b83fb7abb9c9c2d5e56e73fa50f9
|
|
BLAKE2b-256 checksum How to use checksums |
cf1be8b83d1ad4db154df00c71fba90aec7070a22a7351db2be423ec4243089f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.0.0 CPython/3.12.9 Darwin/24.3.0
|
Security for beancount-ing 1.1.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.