| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| README.md | 2026-08-06 | 1.2 kB | |
| v0.2.0 source code.tar.gz | 2026-08-06 | 265.7 kB | |
| v0.2.0 source code.zip | 2026-08-06 | 349.2 kB | |
| Totals: 3 Items | 616.1 kB | 1 | |
Fixed
- A German counterparty no longer comes back with their account number welded to the front of
their name.
mt-9405.0.0 maps:86:subfield?31toapplicant_name, where 4.30.0 mapped it toapplicant_iban, so?31and?32are joined into one string and the IBAN field stops existing. Measured on the vendored corpus: 59 transactions across 5 files returned acounterparty_namesuch asDE42100100100043921105Richter Renate, whilecounterparty_accountfell through to the BIC. Per the DFUe-Abkommen Anlage 3 subfield table?31is the Kontonummer and?32with?33are the name, and all 69 occurrences of?31in the corpus are account numbers, none a name.
Both fields now carry what the file says. The repair reads ?31 off the raw :86: before the
parser consumes it and only acts when the name literally starts with that value, so it becomes
a no-op the day upstream fixes it rather than a second bug.
This changes two normalised values a caller could have relied on, which is breaking by the rule at the top of this file. It is a correction, not a redefinition: the old values were the wrong-but-plausible kind that a reconciliation matches a payer by and never flags.