Postbank SEPA XML Guide: How the Profile Differs from Deutsche Bank Group
It's tempting to assume Postbank inherits Deutsche Bank's exact SEPA rules since Postbank has been part of Deutsche Bank Group since 2010. The implemented profiles disagree in one important respect: schema version.
What the implemented Postbank profile writes and checks
| Area | Postbank profile behavior |
|---|---|
| Credit-transfer schema | pain.001.001.03 — not the .09 namespace used by the Deutsche Bank profile. |
| Batch booking | Enabled by default. |
| Grouping | MIXD. |
| Execution date | The profile enforces a future-dated batch. |
| Address structure | Rule POSTBANK_ISO_001 warns when the address is not structured. |
Don't reuse a Deutsche Bank file for Postbank
If you generate a file with the Deutsche Bank profile — pain.001.001.09, GRP grouping, strict structured-address enforcement — and then submit it through a Postbank channel expecting pain.001.001.03, the namespace mismatch alone can cause a schema-validation rejection. Generate the file with the Postbank profile selected, even though the two banks share a parent group.
Common rejections and the direct fix
- Execution date rejected. Use a value date at least one business day in the future; the profile does not accept same-day or backdated batches.
POSTBANK_ISO_001: Structured Address Compliance. A warning-level check — map street and building number into separate columns to clear it rather than relying on a single free-text address line.
Running payroll every month?
Salary Mode turns your spreadsheet into ready-to-submit SEPA XML.
Try Salary ModeReady to generate bank-compliant SEPA XML files?
Stop struggling with manual formatting. Generate compliant ISO 20022 XML files in seconds directly in your browser.
Start Converting Now (Free)