The ISO 20022 Business Application Header (BAH) is a standard set of data that travels with an ISO 20022 business message and describes it: who sent it, who it is addressed to, which message type and version it is, a unique identifier, when it was created and whether it is a copy or a possible duplicate. It is itself an ISO 20022 message definition, identified as head.001, and in XML it appears as the AppHdr element alongside the main Document.
The header sits between the network transport layer and the business content. It lets the receiving application route and process a message without first opening the payment or report inside. Market practice groups make it mandatory for many flows: the Swift CBPR+ guidelines for cross-border payments require it, as do many domestic high-value systems that moved to ISO 20022 formatted messages, such as CHAPS and T2.
ISO 20022 Business Application Header in plain terms
Think of a letter sent inside a company's internal mail. The letter itself says what needs to be done. The routing slip clipped to the front says which department sent it, which desk it is for, what kind of form it is and when it was posted. A mailroom clerk can sort hundreds of letters by reading only the slips.
The business application header is that routing slip for financial messages. The payment instruction or statement is the letter. The header lets a bank's systems recognise a message, send it to the right application and spot an accidental resend, all before anyone reads the payment details. Because every message carries the same kind of slip, systems built by different firms can understand each other.
What the header contains
The main elements, using their ISO 20022 tag names, are:
- From (Fr) and To (To). The sending and receiving parties, usually identified by Bank Identifier Code (BIC), and optionally by Legal Entity Identifier (LEI) or a clearing member ID.
- Business message identifier (BizMsgIdr). A unique reference for this message, set by the sender.
- Message definition identifier (MsgDefIdr). The exact type and version of the enclosed document, for example
pacs.008.001.08for a customer credit transfer. - Business service (BizSvc). The usage rules the message follows, such as a named CBPR+ or market infrastructure service.
- Creation date and time (CreDt). When the message was created.
- Copy and duplicate flags.
CpyDplctmarks copies and duplicates, andPssblDplctflags a message that may already have been sent. - Related (Rltd). The header of an earlier message this one relates to, used for copies, returns and responses.
- Signature (Sgntr). An optional digital signature over the header and document.
Two versions are in common use: head.001.001.01, the original, and head.001.001.02, which CBPR+ and several market infrastructures adopted.
How the header is used in processing
When a message arrives, the receiving system reads the header first. The message definition identifier tells it which schema to apply during payment message validation. The From and To fields drive routing and entitlement checks. The business message identifier and the duplicate flag support duplicate detection, a form of idempotency that stops the same payment being booked twice when a message is resent after a timeout.
A header that is missing, malformed or inconsistent with the document, for example naming a different message version from the one enclosed, is usually rejected outright or sent to a message repair queue. The header's identifier is not the same as the references inside the payment: the end-to-end transaction reference and the UETR belong to the transaction and stay constant along the chain, while each bank in the chain creates a new header with its own business message identifier.
Header versus network envelope
The BAH is part of the ISO 20022 business layer, so it is independent of the network. On Swift, the message also travels inside a network envelope with its own technical addressing and delivery data, and other networks use their own transport. Keeping the header separate means the same message can move over Swift, a domestic financial market infrastructure or an API without changing its business meaning.
In the older MT format used before the move to ISO 20022, similar information was spread across the basic, application and user header blocks of a message such as the SWIFT MT103. The BAH gathers it into one standard structure that any ISO 20022 message can carry.
Adoption
The header is widely used because the main payment systems have migrated to ISO 20022. On SWIFT, the coexistence period for cross-border payment instructions in MT and ISO 20022 ended on 22 November 2025. In the US, Fedwire Funds Service moved to ISO 20022 on 14 July 2025. Each scheme publishes its own usage guidelines for the header, so the same element can be mandatory in one market and optional in another, and firms connected to several systems maintain separate rules for each as part of their payment messaging set-up.