BankServicesBillingStatementV02

camt.086.001.02

Scope 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. Usage 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. The BankServicesBillingStatement message is intended for use with the ISO 20022 Business Application Header.

Message Construction

Every ISO20022 message has at the highest level what we call ‘building blocks’. Because the message is constructed as immutable records, the association is by composition. Below you can see the relationship between the message and its constituent building blocks: For comparison, see the ISO20022 official specification

classDiagram
     direction LR
%% BankServicesBillingStatementV02 recursion level 0 with max 0
BankServicesBillingStatementV02 *-- "1..1" ReportHeader3 : ReportHeader
BankServicesBillingStatementV02 *-- "1..1" StatementGroup2 : BillingStatementGroup
  

Now, we will zero-in one-by-one on each of these building blocks.

ReportHeader building block

Provides header details on the billing statement report. Provides header details on the report. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% ReportHeader3 recursion level 0 with max 1
class ReportHeader3{
    ReportIdentification IsoMax35Text
}
ReportHeader3 *-- "0..1" Pagination : MessagePagination
%% Pagination recursion level 1 with max 1
class Pagination{
    PageNumber IsoMax5NumericText
    LastPageIndicator IsoYesNoIndicator
}
  

ReportHeader3 members

BillingStatementGroup building block

Group of bank services billing statements with the same sender and receiver characteristics. Group of the statement header reporting the bank services billing and the billing statement. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% StatementGroup2 recursion level 0 with max 1
class StatementGroup2{
    GroupIdentification IsoMax35Text
}
StatementGroup2 *-- "1..1" PartyIdentification58 : Sender
StatementGroup2 *-- "0..2" ContactDetails3 : SenderIndividualContact
StatementGroup2 *-- "1..1" PartyIdentification58 : Receiver
StatementGroup2 *-- "0..2" ContactDetails3 : ReceiverIndividualContact
StatementGroup2 *-- "1..0" BillingStatement2 : BillingStatement
%% PartyIdentification58 recursion level 1 with max 1
class PartyIdentification58{
    Name IsoMax140Text
    LegalName IsoMax140Text
    CountryOfResidence CountryCode
}
PartyIdentification58 *-- "0..1" PostalAddress11 : PostalAddress
PartyIdentification58 *-- "1..1" IParty13Choice : Identification
PartyIdentification58 *-- "0..1" ContactDetails3 : ContactDetails
%% ContactDetails3 recursion level 1 with max 1
class ContactDetails3{
    NamePrefix NamePrefix1Code
    Name IsoMax140Text
    PhoneNumber IsoPhoneNumber
    MobileNumber IsoPhoneNumber
    FaxNumber IsoPhoneNumber
    EmailAddress IsoMax2048Text
    PreferredMethod PreferredContactMethod1Code
}
ContactDetails3 *-- "0..0" OtherContact1 : Other
%% PartyIdentification58 recursion level 1 with max 1
class PartyIdentification58{
    Name IsoMax140Text
    LegalName IsoMax140Text
    CountryOfResidence CountryCode
}
PartyIdentification58 *-- "0..1" PostalAddress11 : PostalAddress
PartyIdentification58 *-- "1..1" IParty13Choice : Identification
PartyIdentification58 *-- "0..1" ContactDetails3 : ContactDetails
%% ContactDetails3 recursion level 1 with max 1
class ContactDetails3{
    NamePrefix NamePrefix1Code
    Name IsoMax140Text
    PhoneNumber IsoPhoneNumber
    MobileNumber IsoPhoneNumber
    FaxNumber IsoPhoneNumber
    EmailAddress IsoMax2048Text
    PreferredMethod PreferredContactMethod1Code
}
ContactDetails3 *-- "0..0" OtherContact1 : Other
%% BillingStatement2 recursion level 1 with max 1
class BillingStatement2{
    StatementIdentification IsoMax35Text
    CreationDateTime IsoISODateTime
    Status BillingStatementStatus1Code
}
BillingStatement2 *-- "1..1" DatePeriod1 : FromToDate
BillingStatement2 *-- "1..1" CashAccountCharacteristics2 : AccountCharacteristics
BillingStatement2 *-- "0..0" BillingRate1 : RateData
BillingStatement2 *-- "0..0" CurrencyExchange6 : CurrencyExchange
BillingStatement2 *-- "0..0" BillingBalance1 : Balance
BillingStatement2 *-- "0..0" BillingCompensation1 : Compensation
BillingStatement2 *-- "0..0" BillingService2 : Service
BillingStatement2 *-- "0..0" BillingTaxRegion1 : TaxRegion
BillingStatement2 *-- "0..0" BalanceAdjustment1 : BalanceAdjustment
BillingStatement2 *-- "0..0" BillingServiceAdjustment1 : ServiceAdjustment
  

StatementGroup2 members

Extensibility and generalization considerations

To facilitate generalized design patterns in the system, the BankServicesBillingStatementV02 implementation follows a specific implementaiton pattern. First of all, BankServicesBillingStatementV02 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, BankServicesBillingStatementV02Document implements IOuterDocument. Because BankServicesBillingStatementV02 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type BankServicesBillingStatementV02.

classDiagram
    class IOuterRecord
    BankServicesBillingStatementV02 --|> IOuterRecord : Implements
    BankServicesBillingStatementV02Document --|> IOuterDocument~BankServicesBillingStatementV02~ : Implements
    class IOuterDocument~BankServicesBillingStatementV02~ {
        BankServicesBillingStatementV02 Message
     }
  

Document wrapper for serialization

The only real purpose BankServicesBillingStatementV02Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:camt.086.001.02’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using BankServicesBillingStatementV02.ToDocument() method. The returned BankServicesBillingStatementV02Document value will serialize correctly according to ISO 20022 standards.

classDiagram
    BankServicesBillingStatementV02Document *-- BankServicesBillingStatementV02 : Document
  

Sample of message format

This is an abbreviated version of what the message should look like.

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.086.001.02">
    <BkSvcsBllgStmt>
        <RptHdr>
            <!-- ReportHeader inner content -->
        </RptHdr>
        <BllgStmtGrp>
            <!-- BillingStatementGroup inner content -->
        </BllgStmtGrp>
    </BkSvcsBllgStmt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_sHrTETqxEeWZFYSPlduMhw"
  nextVersions="_bf9SDW2PEei3KuUgpx7Xcw"
  previousVersion="_cVsZ9ZqmEeGSON8vddiWzQ_1763088977"
  name="BankServicesBillingStatementV02"
  definition="Scope&#xD;&#xA;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.&#xD;&#xA;Usage&#xD;&#xA;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.&#xD;&#xA;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. &#xD;&#xA;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.&#xD;&#xA;The BankServicesBillingStatement message is intended for use with the ISO 20022 Business Application Header."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="BkSvcsBllgStmt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_sHrTEzqxEeWZFYSPlduMhw"
    nextVersions="_bf9SD22PEei3KuUgpx7Xcw"
    previousVersion="_cVsZ9pqmEeGSON8vddiWzQ_-2124285410"
    name="ReportHeader"
    definition="Provides header details on the billing statement report."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="RptHdr"
    complexType="_6Q_lh5qlEeGSON8vddiWzQ_-723206236" />
  <messageBuildingBlock
    xmi:id="_sHrTFTqxEeWZFYSPlduMhw"
    nextVersions="_bf9SEW2PEei3KuUgpx7Xcw"
    previousVersion="_cVsZ95qmEeGSON8vddiWzQ_1850153158"
    name="BillingStatementGroup"
    definition="Group of bank services billing statements with the same sender and receiver characteristics."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="BllgStmtGrp"
    complexType="_akFHMTq2EeWZFYSPlduMhw" />
  <messageDefinitionIdentifier
    businessArea="camt"
    messageFunctionality="086"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

The following items are used as building blocks to construct this message.