Choose a parsing workflow

Start with Parse your first statement if you have not parsed a statement yet. It contains a complete input and executed output. The guides below address the choices an application makes after that first parse.

Pick the operation

Input or requirement	Entry point	Guide
One statement, or intentionally merged metadata	mt940.parse()	Read files, text and streams
Separate statements beginning with :20:	mt940.parse_statements()	Keep separate statements and group transactions
Amounts, dates, balances and optional fields	mt940.models.Transactions	Read transactions, amounts and balances
JSON for storage or another service	mt940.JSONEncoder	Export a statement to JSON
A different bank tag or processing rule	tags and processors arguments	Customise tags and ordered processors
Preserve defaults while selecting parsing fixes	mt940.Options	Choose compatibility options

A collection returned by parse can be empty even when its metadata contains an account or balances. An unrecognised string can also return an empty collection. Check the fields you require instead of treating an empty transaction list as a universal parse-failure signal.

Supported bank variants and tag output tables are in Bank formats and field reference. When an expected field is missing or changed, use Diagnose unexpected output to trace the source, tag and processor involved. The generated API reference documents exact arguments and exceptions.