Business Application Header, head.001

The Business Application Header, known as head.001, is the envelope that travels with an ISO 20022 business message, and it tells the receiver who sent the message, who should receive it, what the message is, and when it was created, before the receiver opens the business content. The BAH is a separate XML document that wraps the business message, so a pacs.008 arrives as a head.001 plus a pacs.008. The BAH is defined in the ISO 20022 standard as head.001.001.01, and it is mandatory in some contexts and optional in others, which is a detail that many specifications get wrong. Source: ISO 20022, head.001.001.01 Business Application Header; SWIFT, Cross-border Payments and Reporting Plus usage guidelines. The BAH fields are six, and each has a purpose that a business analyst must be able to explain. To carries the receiver, also as a BIC, such as COBADEFFXXX for Bank B. MsgDefIdr carries the message definition identifier, such as pacs.008.001.08, which tells the receiver which message type and version to expect. BizSvc carries the business service, such as swift.cbprplus.02, which tells the receiver which market practice applies. CreDt carries the creation date and time, such as 2026-11-09T10:00:00, which is used for reconciliation and investigation. A BAH that omits any of these, or that carries a wrong value, will be rejected or misrouted, and the business message inside it will never be processed. A worked example shows a complete BAH for a pacs.008. The From is AGRIFRPPXXX, the To is COBADEFFXXX, the BizMsgIdr is BANKA20261109-001, the MsgDefIdr is pacs.008.001.08, the BizSvc is swift.cbprplus.02, and the CreDt is 2026-11-09T10:00:00. The receiver, Bank B, reads the From and checks that Bank A is a known sender, reads the To and checks that the message is for Bank B, reads the MsgDefIdr and loads the pacs.008 version 08 schema, reads the BizSvc and applies the CBPR+ usage guidelines, reads the BizMsgIdr and checks that it has not seen this identifier before, and then opens the pacs.008 and processes the payment. If the BizMsgIdr were a duplicate, Bank B would reject the message as a duplicate, and the payment would not be processed twice. The CBPR+ rules for when a BAH is required and when it is omitted are specific, and they must be stated in the requirement. A BAH is not required for some domestic messages, where the clearing system provides its own envelope, and it is not required for customer to bank messages such as pain.001, where the bank provides its own channel envelope. A BAH is also used for admi messages, which are system messages, and for camt messages, where the header carries the same six fields. A business analyst who assumes a BAH is always required will add it where it is not needed, and a business analyst who assumes it is never required will omit it where the network expects it, and the message will be rejected in both cases. Failure in the BAH is a header failure, and the recovery is to fix the header and resend, with a new BizMsgIdr, because the old identifier is associated with a rejected message. If the From is wrong, the message is rejected as unauthenticated, and the sender must correct the BIC and resend. If the To is wrong, the message is routed to the wrong bank, and the receiving bank will reject it, and the sender must correct the To and resend. If the MsgDefIdr is wrong, the receiver will load the wrong schema, and the validation will fail, and the sender must correct the version and resend. If the BizMsgIdr is a duplicate, the receiver will reject it as a duplicate, and the sender must generate a new identifier, not reuse the old one. The effect on the bank, the customer and operations is that the BAH is the first control, and a failure there stops the payment before the business content is even read. For the customer, a BAH failure means the payment was never sent, and the customer must be told the payment did not go through, not that it is in progress. For operations, the BAH is the routing and duplicate detection control, and the BizMsgIdr is the key that links the header to the business message, to the posting and to the reconciliation, so the requirement must name it as the duplicate detection key, or the system will process duplicates. For a business analyst, product owner or subject matter expert, the test is to write a BAH for any ISO 20022 message and to explain each field, its source and its validation. Ask who the From and To are, how the BizMsgIdr is generated and how duplicates are detected, what the MsgDefIdr is for the message version, what the BizSvc is for the market practice, and what the CreDt is used for. Ask when a BAH is required and when it is omitted, under CBPR+ and under the domestic scheme, and ask what happens when each field is wrong. The ISO 20022 head.001 definition is the source for the fields, and the SWIFT CBPR+ usage guidelines are the source for the rules, and both must be cited in the specification, with version and effective date. Two mistakes are common and must be avoided. The first is to confuse the BAH From and To with the pacs.008. The second is to confuse the BizMsgIdr with the pacs.008 MsgId, which are related but not the same: the BizMsgIdr identifies the business message as a whole, and the MsgId identifies the group header inside it, and in practice they are often the same value, but the specification must state whether they are the same or different, or the duplicate detection will be ambiguous. The correct design is to state the header fields, their sources and their validations separately from the business message fields, and to test the header with a wrong value for each field, to prove the rejection works. Takeaway: head.001 is the envelope for an ISO 20022 business message, with From, To, BizMsgIdr, MsgDefIdr, BizSvc and CreDt, and it is read before the business content. Under CBPR+ it is required for FI to FI messages over SWIFT, and it is omitted for some domestic and customer to bank messages. A wrong header rejects the message, and a duplicate BizMsgIdr rejects it as a duplicate. Further reading: ISO 20022, head.001.001.01 Business Application Header; SWIFT, Cross-border Payments and Reporting Plus usage guidelines. Last reviewed 7 November 2026.