RegulatoryReporting

Information needed due to regulatory and statutory requirements,.

See http://www.openapplications.org/platform/1.

Element information

Content

• Sequence [1..1]
  1. Code [0..1]    Element for the communication of all codes.
  2. Amount [0..1]    The monetary value of the object in which the amount is associated
  3. Note [0..1]    
  4. UserArea [0..1]    Allows the user of OAGIS to extend the specification in order to provide additional information that is not captured in OAGIS.This is done by defining the additional information in XML Schema and referencing the new schema in the xml instance document through the use of namespaces. Once this is done the additional information defined there can be carried in the BOD XML instance document.The Open Applications Group will make best efforts to quickly consider all proposed submissions.The USERAREA is always the last element in all components, except where the component has been extended inline.

Attributes

None

Used in

• Type PaymentTransactionType (Element PaymentTransaction)

Sample instance

<RegulatoryReporting>
   <Code>normalizedString</Code>
   <Amount currencyID="AED">1.0</Amount>
   <Note>string</Note>
   <UserArea>
      <!--any element-->
   </UserArea>
</RegulatoryReporting>