Skip to main content

beancount-openbanking-io

A Beancount / beangulp importer for open-banking.io — zero-knowledge PSD2 bank sync for EEA & UK banks.

Transactions arrive as zero-knowledge encrypted envelopes and are decrypted locally by the official open-banking-io SDK with a key only you hold. Your statement is never readable off your machine — a good fit for a plaintext-accounting ledger you keep yourself.

Why

If you sync EU/UK banks into Beancount, your options have been thinning out:

  • GoCardless / Nordigen stopped approving new personal Bank-Account-Data accounts, and imposes a 4-requests-per-account-per-day rate limit that breaks routine imports.
  • Other aggregators terminate your bank connection in the clear on their servers.

open-banking.io is an alternative built for self-hosters: client-side decryption, no eIDAS certificate to obtain, no per-account daily rate-limit wall.

Install

pip install beancount-openbanking-io

This pulls in beancount, beangulp, and the open-banking-io SDK.

Configure

Export your credentials bundle from the open-banking.io dashboard, then create a small YAML file whose name ends in openbanking.yaml:

# myfinances.openbanking.yaml
credentials: ./open-banking.io-credentials.json   # path is relative to this file
accounts:
  - id: f1345859-....          # open-banking.io account id (from client.get_accounts())
    account: Assets:Bank:Nordea:Checking
    currency: DKK              # optional guard
    counterpart: Expenses:Uncategorized   # optional; default holding account for the other leg
    assert_balance: true       # optional: emit a booked-balance (ITBD) assertion

To list your account ids:

from open_banking_io import OpenBankingClient

with OpenBankingClient.from_credentials("open-banking.io-credentials.json") as client:
    for account in client.get_accounts():
        print(account.id, account.aspsp_name, account.currency, account.iban)

Use

Wire it into your beangulp import script like any other importer:

# import.py
import beangulp
from beancount_openbanking_io import OpenBankingImporter

if __name__ == "__main__":
    beangulp.Ingest([OpenBankingImporter()]).main()
python import.py extract myfinances.openbanking.yaml >> ledger.beancount

Re-running is safe: each entry is stamped with its stable open-banking.io transaction id (obio-id), so already-imported transactions are skipped.

Mapping

open-banking.io Beancount
amount (unsigned) + creditDebitIndicator signed posting amount — DBIT → negative, CRDT → positive
creditorName (DBIT) / debtorName (CRDT) payee
remittanceInformation / note narration
bookingDate (→ valueDate → transactionDate) entry date
status PDNG ! (flagged/uncleared); BOOK → *
transaction id obio-id metadata (dedup key)
ITBD booked balance optional balance assertion

Each transaction gets a second, amount-elided posting to the counterpart account (default Expenses:Uncategorized) so entries balance on import; reclassify it later (e.g. with smart_importer). Transactions whose direction cannot be determined are skipped, never imported with a guessed sign.

License

MIT — see LICENSE.

Metadata

Release files for beancount-openbanking-io 1.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for beancount-openbanking-io 1.0.0
File Size Uploaded Provenance Actions
beancount_openbanking_io-1.0.0.tar.gz 8.4 kB With provenance Details for beancount_openbanking_io-1.0.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for beancount-openbanking-io 1.0.0
File Interpreter ABI Platform Actions
beancount_openbanking_io-1.0.0-py3-none-any.whl Python 3 none any Details for beancount_openbanking_io-1.0.0-py3-none-any.whl

Total release size: 16.2 kB

Release files / beancount_openbanking_io-1.0.0.tar.gz

Download URL beancount_openbanking_io-1.0.0.tar.gz
Size 8.4 kB
Tags Source
SHA-256 checksum
How to use checksums
1e7f480320e5b1a36f73d8cb6c5d6345bf3c31b925f5149745f5db2c87a5f815
BLAKE2b-256 checksum
How to use checksums
7bdeb933640336b83b7cbafbb31258945fda003d3e7b103913567dae3a2093c3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 20, 2026.

Transparency log

Release files / beancount_openbanking_io-1.0.0-py3-none-any.whl

Download URL beancount_openbanking_io-1.0.0-py3-none-any.whl
Size 7.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
22ef793be65ee1d9aadae499a30b7976a28e298503f3df23c76e8203989d045a
BLAKE2b-256 checksum
How to use checksums
718dacd4d575e68871f9512288e811c3d8e494221dbb76ae4c1e85e8df846b35
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 20, 2026.

Transparency log

Security for beancount-openbanking-io 1.0.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.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for beancount_openbanking_io-1.0.0.tar.gz

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 Nov 20, 2026.

Transparency log

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.

Release history Release notifications | RSS feed

This release

1.0.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page