Skip to main content

MT940

CI PyPI Python Monthly downloads Documentation Coverage License

Parse MT940 bank statements into Python transactions, decimal amounts, dates and balances. The mt-940 distribution imports as mt940, supports Python 3.10 through 3.15 and has no runtime dependencies. Type information ships in the package through py.typed.

Parse your first statement

Install the package in your project's environment:

uv pip install mt-940

This complete example uses a fictional account. Paste it into Python:

import mt940

source: str = """:20:EXAMPLE-001
:25:EXAMPLE-ACCOUNT
:28C:1/1
:60F:C260101EUR100,00
:61:2601020102D12,50NTRFCOFFEE//BANK-001
:86:Coffee supplies
:62F:C260102EUR87,50
"""
statement: mt940.models.Transactions = mt940.parse(source)
transaction: mt940.models.Transaction = statement[0]
print(transaction.data['date'], transaction.data['amount'])
print(statement.data['final_closing_balance'])

The test suite executes that code. Its output is:

2026-01-02 -12.50 EUR
87.50 EUR @ 2026-01-02

The debit mark D produces a negative Decimal. The closing balance comes from :62F: in the input. Parsing does not calculate or reconcile balances. Transaction fields live in transaction.data, and statement metadata lives in statement.data. A missing source field can be absent or None, depending on its tag and processors.

Choose the input and output you need

  • Pass a pathlib.Path for a file. A missing Path raises FileNotFoundError. Plain strings naming no existing file are interpreted as statement text.
  • Pass raw str or bytes, or an open text or binary stream. Streams are read from their current position and remain open. Numeric file descriptors close after reading.
  • Use mt940.parse_statements(source) for separate :20: statement blocks. mt940.parse(source) merges transactions and keeps the last value for each statement metadata key. :28C: page numbers do not split statements.
  • Use json.dumps(statement, cls=mt940.JSONEncoder) to export metadata and transactions. Decimal values become strings. There is no matching decoder that reconstructs the models.

The usage guide explains these choices. The API reference covers tags, processors, models and parser helpers.

Bank formats and compatibility

Built-in tags cover references (20, 21), account and sequence information (25, 28C), time (13D), floor limits (34F), balances (60, 62, 64, 65), transactions (61), details (86), summaries (90C, 90D) and non-SWIFT extensions (NS). Bank-specific fixtures are regression evidence for those files. They do not guarantee every export from a named bank.

Custom tag instances and ordered pre/post processors can adapt a collection. StatementASNB and StatementGLS are explicit alternatives for their :61: variants. Processor overrides replace a whole slot. Copy its default list when adding a callback.

Ten mt940.Options switches preserve legacy output unless enabled. All default to False. mt940.Options(reversal_sign=True) changes the sign of RC transactions, and mt940.Options.all() enables every declared switch. The Options reference documents each effect. Compare outputs for your bank before changing options.

Develop and contribute

Clone develop. master tracks stable releases. Development and documentation tools use Python 3.12, while the library supports Python 3.10 through 3.15:

git clone --branch develop https://github.com/WoLpH/mt940.git
cd mt940
uv sync --python 3.12
uv run lefthook install
uv run tox

The checks include the Python test matrix and combined coverage, five type checkers (mypy, basedpyright, pyright, pyrefly and ty), Ruff, documentation, spelling, repository configuration, workflow security and dependency audits. See CONTRIBUTING.rst for focused commands and fixture requirements. The runnable examples/ package uses fictional data and includes recorded outputs checked by pytest.

Support

mt940 is maintained by Rick van Hattem in his own time. Most of that time goes on bank statement dialects, because every bank reads the spec slightly differently.

If it saved you an afternoon, a tip covers an hour of issue triage: Ko-fi or GitHub Sponsors.

If your company funds its dependencies, this package is on thanks.dev.

ko-fi

Documentation | Source | Issues | Releases | BSD-3-Clause licence

Metadata

Release files for mt-940 5.1.3

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

Source distribution (sdist)

Source distribution for mt-940 5.1.3
File Size Uploaded Provenance Actions
mt_940-5.1.3.tar.gz 199.6 kB With provenance Details for mt_940-5.1.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for mt-940 5.1.3
File Interpreter ABI Platform Actions
mt_940-5.1.3-py3-none-any.whl Python 3 none any Details for mt_940-5.1.3-py3-none-any.whl

Total release size: 248.4 kB

Release files / mt_940-5.1.3.tar.gz

Download URL mt_940-5.1.3.tar.gz
Size 199.6 kB
Tags Source
SHA-256 checksum
How to use checksums
bb165c60c828cfa741515caf947535d8682451a088cc06b5d81df26b5a84b851
BLAKE2b-256 checksum
How to use checksums
5862c204df04ddf2fcaae60412075d714bf49941be0b1ea378848de3af4f9ccf
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 Oct 28, 2026.

Transparency log

Release files / mt_940-5.1.3-py3-none-any.whl

Download URL mt_940-5.1.3-py3-none-any.whl
Size 48.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
36d8e3fa6683600b90ce3c63016489f16c31cc7c7e003baf80d060aac876c25e
BLAKE2b-256 checksum
How to use checksums
76a9eec419a2adcd8eb6ab847686c642ccc4d6f8160d58a9fc0d1f4b22326f74
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 Oct 28, 2026.

Transparency log

Security for mt-940 5.1.3

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

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for mt_940-5.1.3.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 Oct 28, 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

5.1.3 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