HeaderReplaces FIN Basic Header / Application Header (blocks 1–3)Nov 2026 milestone
head.001
Business Application Header (BAH)
The November 2026 rules harden BAH validation — mismatches between MsgDefIdr/BizSvc and the payload are rejected rather than tolerated.
Overview
The Business Application Header is the ISO 20022 equivalent of the FIN header blocks. It carries the business sender and receiver (as BICs), the message definition identifier (e.g. pacs.008.001.08), the business service (e.g. swift.cbprplus.02), a unique business message identifier, and the creation timestamp.
Under CBPR+ the BAH is mandatory and strictly validated. Routing, duplicate detection, and service-level agreements all key off BAH content rather than anything inside the document payload.
Key elements
| Element | Name | Notes |
|---|---|---|
| Fr/FIId/FinInstnId/BICFI | Business sender BIC | — |
| To/FIId/FinInstnId/BICFI | Business receiver BIC | — |
| BizMsgIdr | Business message identifier | Unique per message; basis for duplicate control. |
| MsgDefIdr | Message definition identifier | e.g. pacs.008.001.08 — must match the payload. |
| BizSvc | Business service | e.g. swift.cbprplus.02. |
| CreDt | Creation date-time (UTC) | — |
Work with this message
Other messages
pacs.008FI to FI Customer Credit Transferpacs.009FI Credit Transferpacs.002FI to FI Payment Status Reportpacs.004Payment Returnpain.001Customer Credit Transfer Initiationpain.002Customer Payment Status Reportpain.008Customer Direct Debit Initiationcamt.052Bank to Customer Account Reportcamt.053Bank to Customer Statementcamt.054Bank to Customer Debit/Credit Notificationcamt.056FI to FI Payment Cancellation Requestcamt.029Resolution of Investigationcamt.110Investigation Requestcamt.111Investigation Response