SEPA creditor identifier errors: check shape and MOD97
Trace creditor scheme identifiers, supported national shapes and the MOD97 calculation excluding the business code.
Start with the creditor scheme, not the creditor account
A creditor identifier identifies the collecting party independently of its IBAN. The mandate reference identifies an agreement within that creditor context. An exporter that substitutes an account number for the scheme identifier can therefore produce well-formed XML with an unusable collection instruction. Look at CdtrSchmeId, its private Other Id, and the SEPA scheme name before editing debtor account details.
The lite validator resolves the transaction-level creditor scheme when present and otherwise uses the payment block value. Its report points to the effective Id field. SDD-CREDITOR-ID means that the general shape, a supported national shape or the arithmetic checksum failed. It does not mean the issuing institution was consulted.
Exclude the business code from the arithmetic
The initial two characters identify the country and the next two are check digits. The following three-character business code is excluded from the MOD97 calculation. An ERP implementation that includes those three characters will reject correctly formed identifiers or manufacture incorrect check digits. Replacing ZZZ with another permitted business code must not change the arithmetic result.
For the checksum, use the national part followed by the country letters and check digits, convert letters to their numeric values and evaluate the remainder. This is separate from an IBAN test: applying the ordinary IBAN rearrangement to the entire creditor identifier incorrectly retains the business code. The local check uses bounded arithmetic and never queries an issuing registry.
Understand the national boundary
This release covers national shape and the outer checksum for German, French, Croatian, Polish and Romanian creditor identifiers. Germany and Croatia use eleven numeric characters in the national part; the current German structure starts that part with zero. French identifiers have a six-character national part within the supported hexadecimal shape. Other national procedures and fiscal identification checksums require separate checks. A covered country's technical checksum cannot establish that a real authority issued the number.
SDD-CI-SCOPE is a review warning for another country. Do not remove that warning by selecting a different country code: retain the real identifier and obtain the applicable specification and rights. A passing generic pattern is insufficient to assert complete national coverage.
Fix the source and rerun the whole file
Compare the identifier with the creditor onboarding record rather than guessing new digits. Confirm that the debtor-facing mandate uses the corresponding creditor and mandate reference. Once corrected in the source system, regenerate the XML so that its group and payment-block control sums still match the transactions. The sample action opens a fictional creditor-checksum failure; the downloadable outcomes distinguish that independent rule error from missing MsgId, which requires a supplied XSD.
For several files, Pro/Team checks preserve per-file failures and mark matching collections across the selected batch as review warnings. Reports contain version and scope so that an integrator can distinguish a checksum repair from a schema or bank-profile result. No creditor registration, mandate authenticity or bank acceptance is established.
Before and after
Before: independent rule fails
<Id>DE10ZZZ00000000001</Id>After: this field passes
<Id>DE09ZZZ00000000001</Id>Fictional failing XML · Passing rule-only demo · Expected codes and source locations
Primary evidence and scope
EPC creditor identifier overview v12.0 and Bundesbank creditor identifier structure provides the technical CI facts, including exclusion of the business code from the checksum. EPC CORE C2PSP 2025 v1.0 and EPC B2B C2PSP 2025 v1.0 describe the selected collection schemes and the current address postponement. The ISO message catalogue lists .12; this implementation deliberately selects .08 or explicit legacy .02. Sources checked 6 November 2026.
This explanation and its controls are independently written. No EPC text, TVS or bank rule package is redistributed. A rule-only demo establishes none of the official XSD, real mandate, authorisation, registration, working-day/cutoff or acceptance layers.
Recheck the regenerated batch
SEPA pain.008 validator · Related SEPA repair guide · API / CLI scope