ZagTrader

head: Business Application Header

head.002 Business File Header

Written and maintained by ZagTrader. Last reviewed . How this page is sourced and checked

head.002 is the ISO 20022 BusinessFileHeader message in the Business Application Header business area (head). The latest version is head.002.001.01.

Message
BusinessFileHeader
Latest version
head.002.001.01
Submitting organisation
4CB and Swift
MT equivalent
None listed

In use: published in the current ISO 20022 catalogue.

What head.002 is for

The Business File Header contains information about the parties involved in the file exchange, as well as information about the content and its structure.

The Business File headers has four major functions:

- Provides information about the sender of the file.

- Identifies the file exchanged: each file must have a unique File Identifier.

- Describes the type of message(s) exchanged: by default, the type of messages contained in a file will be ISO 20022 message definitions.

- Provides processing information to the receiving party: that would be, for instance, the total number of messages included in the file.

Usage: The Business File Header (head.002) is to be used exclusively in existing implementations, such as the Eurosystem, and will be replaced for general use by the upcoming next version defined as the Business File Envelope (nvlp.002). The Business File Header (head.002) will therefore not be maintained in the future and any new implementation must use the Business File Envelope (nvlp.002).

Definition from the ISO 20022 e-Repository, release of 24 April 2025.

head.002 versions

Every version published in the e-Repository, newest first. A message keeps its business purpose across versions; each new version is a separate schema with its own namespace.

VersionRegistration statusPublished in
head.002.001.01latestRegisteredLatest version set

head.002 message structure

The building blocks of head.002.001.01 to three levels, with multiplicity ([0..1] optional, [1..1] mandatory, * any number) and the data type or component. Element names and definitions are from the ISO 20022 repository; usage guidelines such as CBPR+ or a market infrastructure's rules can restrict them further.

  • Document [1..1]
    • Xchg BusinessFileHeader [1..1]
      • PyldDesc Payload Description [1..1]PayloadDescription2

        Contains information about the payload.

        • PyldData Payload Data [1..1]PayloadData2

          This component is used to identify the instance of the document exchanged.

          • PyldIdr Payload Identifier [1..1]Max35Text
          • CreDtAndTm Creation Date And Time [1..1]ISODateTime
          • PssblDplctFlg Possible Duplicate Flag [0..1]TrueFalseIndicator
        • ApplSpcfcs Application Specifics [0..1]ApplicationSpecifics1

          Contains business information that is considered as necessary by the service provider.

          • SysUsr System User [0..1]Max140Text
          • Sgntr Signature [0..1]SignatureEnvelope
          • TtlNbOfDocs Total Number Of Documents [1..1]Number
        • PyldTp Payload Type [1..1]Max256Text

          Identification of the type of payload.

        • MnfstData Manifest Data [0..*]ManifestData2

          Manifest that describes the related items or attachments.

          • DocTp Document Type [1..1]Max35Text
          • NbOfDocs Number Of Documents [1..1]Number
      • Pyld Payload [0..*]LaxPayload

        File Payload is used to include the exchanged documents within the file structure.

Have a head.002 message? Paste it into the parser to see every element with its name and definition, and format checks on BICs, IBANs, dates and amounts.

head.002 questions

What is the latest version of head.002?
The latest version in the ISO 20022 e-Repository release of 24 April 2025 is head.002.001.01.
What is the root element of head.002?
The XML document is Document with the namespace urn:iso:std:iso:20022:tech:xsd:head.002.001.01, and its message element is Xchg (BusinessFileHeader).
Is there an MT equivalent of head.002?
No Swift MT message is listed as its direct equivalent on this site. Many ISO 20022 messages have no MT counterpart.

All ISO 20022 messages · ISO 20022 code sets · MT messages

The ISO 20022 message definitions, element names and definitions on this page are reproduced from material published at iso20022.org under the ISO 20022 Intellectual Property Rights policy. This is not the official source: the up-to-date ISO 20022 standards and repository material are published only at iso20022.org. Explanations in our own words are by ZagTrader. ZagTrader is not affiliated with or endorsed by ISO or Swift.