camt: Cash Management
camt.086 Bank Services Billing Statement
Written and maintained by ZagTrader. Last reviewed . How this page is sourced and checked
camt.086 is the ISO 20022 BankServicesBillingStatement message in the Cash Management business area (camt). The latest version is camt.086.001.05, and 5 versions are in the repository.
- Message
- BankServicesBillingStatement
- Latest version
- camt.086.001.05
- Submitting organisation
- TWIST & Swift
- MT equivalent
- None listed
In use: published in the current ISO 20022 catalogue.
What camt.086 is for
The BankServicesBillingStatement message is used to send from a Financial Institution (FI) to its wholesale customers (corporations, governments, institutions, etc.), information describing the FI’s billing of services rendered in the form of an electronic statement in a standardised format. The BankServicesBillingStatement is a periodic (usually end of month) recounting of all service chargeable events that occurred during a reporting cycle, typically a calendar month, along with detailed tax and currency translation information. Account balance information, although strongly recommended, is not required.
The BankServicesBillingStatement message is designed to provide details related to invoices (or an advice of debit) which a financial institution may supply to its customers. The BankServicesBillingStatement is not expressly designed to be an invoice, nor to replace invoices currently in use. The message may be used as an invoice by agreement between the sender and the receiver. No regulatory or legislative requirements were considered when creating this message standard. Users of the BankServicesBillingStatement message are cautioned to be aware of any regulatory or legal requirement for invoices before replacing existing invoices.
The BankServicesBillingStatement message can supply the detail supporting separate invoices or debits but it is not the invoice or advice of debit of record. The BankServicesBillingStatement message must accurately reflect all the charge and tax related events that occurred during the calendar month and how the FI and taxing authorities were compensated for these events. The BankServicesBillingStatement does not ask the financial institution to revise its established pricing and billing procedures.
How, when and what the customer is actually charged for remains in place. The BankServicesBillingStatement message asks the financial institution to aggregate and report what actually happened during the calendar month.
camt.086 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.
| Version | Registration status | Published in |
|---|---|---|
| camt.086.001.05latest | Registered | Latest version set |
| camt.086.001.04 | Registered | Previous version set |
| camt.086.001.03 | Registered | Archive |
| camt.086.001.02 | Registered | Archive |
| camt.086.001.01 | Registered | Archive |
camt.086 message structure
The building blocks of camt.086.001.05 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]BkSvcsBllgStmtBankServicesBillingStatement [1..1]RptHdrReport Header [1..1]ReportHeader6Provides header details on the billing statement report.
RptIdReport Identification [1..1]Max35TextIdentification of a report billing statement.
MsgPgntnMessage Pagination [0..1]Pagination1Provides details on the page number of the message.
PgNbPage Number [1..1]Max5NumericTextLastPgIndLast Page Indicator [1..1]YesNoIndicator
BllgStmtGrpBilling Statement Group [1..*]StatementGroup5Group of bank services billing statements with the same sender and receiver characteristics.
GrpIdGroup Identification [1..1]Max35TextIdentification of a group of customer billing statements.
SndrSender [1..1]PartyIdentification273Originating financial institution sending the statement.
NmName [1..1]Max140TextLglNmLegal Name [0..1]Max140TextPstlAdrPostal Address [0..1]PostalAddress27IdIdentification [1..1]Party56Choice (choice)CtryOfResCountry Of Residence [0..1]CountryCodeCtctDtlsContact Details [0..1]Contact13
SndrIndvCtctSender Individual Contact [0..2]Contact13Specifies the individual to contact in case of technical problems at the sender's location.
NmPrfxName Prefix [0..1]NamePrefix2CodeNmName [0..1]Max140TextPhneNbPhone Number [0..1]PhoneNumberMobNbMobile Number [0..1]PhoneNumberFaxNbFax Number [0..1]PhoneNumberURLAdrURL Address [0..1]Max2048TextEmailAdrEmail Address [0..1]Max256TextEmailPurpEmail Purpose [0..1]Max35TextJobTitlJob Title [0..1]Max35TextRspnsbltyResponsibility [0..1]Max35TextDeptDepartment [0..1]Max70TextOthrOther [0..*]OtherContact1PrefrdMtdPreferred Method [0..1]PreferredContactMethod2Code
RcvrReceiver [1..1]PartyIdentification273Financial institution customer receiving the statement.
NmName [1..1]Max140TextLglNmLegal Name [0..1]Max140TextPstlAdrPostal Address [0..1]PostalAddress27IdIdentification [1..1]Party56Choice (choice)CtryOfResCountry Of Residence [0..1]CountryCodeCtctDtlsContact Details [0..1]Contact13
RcvrIndvCtctReceiver Individual Contact [0..2]Contact13Specifies the individual to contact in case of technical problems at the receiver's location.
NmPrfxName Prefix [0..1]NamePrefix2CodeNmName [0..1]Max140TextPhneNbPhone Number [0..1]PhoneNumberMobNbMobile Number [0..1]PhoneNumberFaxNbFax Number [0..1]PhoneNumberURLAdrURL Address [0..1]Max2048TextEmailAdrEmail Address [0..1]Max256TextEmailPurpEmail Purpose [0..1]Max35TextJobTitlJob Title [0..1]Max35TextRspnsbltyResponsibility [0..1]Max35TextDeptDepartment [0..1]Max70TextOthrOther [0..*]OtherContact1PrefrdMtdPreferred Method [0..1]PreferredContactMethod2Code
BllgStmtBilling Statement [1..*]BillingStatement5Provides the bank services billing statement recounting of all service chargeable events that occurred during a reporting cycle, such as the end of...
StmtIdStatement Identification [1..1]Max35TextFrToDtFrom To Date [1..1]DatePeriod1CreDtTmCreation Date Time [1..1]ISODateTimeStsStatus [1..1]BillingStatementStatus1CodeAcctChrtcsAccount Characteristics [1..1]CashAccountCharacteristics5RateDataRate Data [0..*]BillingRate1CcyXchgCurrency Exchange [0..*]CurrencyExchange6BalBalance [0..*]BillingBalance1CompstnCompensation [0..*]BillingCompensation1SvcService [0..*]BillingService2TaxRgnTax Region [0..*]BillingTaxRegion3BalAdjstmntBalance Adjustment [0..*]BalanceAdjustment1SvcAdjstmntService Adjustment [0..*]BillingServiceAdjustment1
Have a camt.086 message? Paste it into the parser to see every element with its name and definition, and format checks on BICs, IBANs, dates and amounts.
External code sets used in camt.086
These elements take their values from ISO 20022 external code sets, which are published separately and updated every quarter without a new message version.
- ExternalAccountIdentification1Code4 codes
- ExternalBankTransactionDomain1Code0 codes
- ExternalBankTransactionFamily1Code0 codes
- ExternalBankTransactionSubFamily1Code0 codes
- ExternalBillingBalanceType1Code23 codes
- ExternalBillingCompensationType1Code22 codes
- ExternalBillingRateIdentification1Code19 codes
- ExternalCashAccountType1Code28 codes
- ExternalClearingSystemIdentification1Code172 codes
- ExternalFinancialInstitutionIdentification1Code0 codes
- ExternalOrganisationIdentification1Code15 codes
- ExternalProxyAccountType1Code22 codes
camt.086 questions
- What is the latest version of camt.086?
- The latest version in the ISO 20022 e-Repository release of 24 April 2025 is camt.086.001.05.
- What is the root element of camt.086?
- The XML document is Document with the namespace urn:iso:std:iso:20022:tech:xsd:camt.086.001.05, and its message element is BkSvcsBllgStmt (BankServicesBillingStatement).
- Is there an MT equivalent of camt.086?
- 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.