ChartOfAccounts

Chart of Accounts represents the accounting structure of a business.   Each account represents a financial aspect of a business, such as its Accounts Payable, or the value of its inventory, or its office supply expenses.  Typically, each account consists of a character string representing various elements such as major account code and department code.

See http://www.openapplications.org/oagis/9.

Element information

Content

• Sequence [1..1]
  1. GLEntityID [0..1]    Is the primary balancing segment of the GL Account structure. Typically, this is the owning entity for the transaction. A G/L entity is the smallest organizational unit for which individual financial statements must be drawn up according to relevant commercial law. P&L statements are required at this level.
  2. GLNominalAccount [0..1]    Is the primary account classification within a chart of accounts. For example reveune, Fixed Asset, Land, Buildings, etc.Is the primary account classification within a chart of accounts. For example reveune, Fixed Asset, Land, Buildings, etc.
  3. EffectiveTimePeriod [0..1]    defines the date and time when a particular document or item takes effect or becomes valid.defines the date and time when a particular document or item takes effect or becomes valid.defines the date and time when a particular document or item takes effect or becomes valid.defines the date and time when a particular document or item takes effect or becomes valid.
  4. AccountType [0..1]    AccountType is an account classification that specifies the use of this account. Suggested examples of account type are Asset, Equity, Expense, Liability, Revenue
  5. CurrencyCode [0..1]    Specifies the currency code of the object in which it is associated.
  from group FreeFormTextGroup
  Sequence [0..1]
  1. Description [0..*]    
  2. Note [0..*]    
  6. 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 GetChartOfAccountsDataAreaType (Element DataArea)
• Type NotifyChartOfAccountsDataAreaType (Element DataArea)
• Type OAGIS9NounsType (Element OAGIS9Nouns)
• Type ShowChartOfAccountsDataAreaType (Element DataArea)
• Type SyncChartOfAccountsDataAreaType (Element DataArea)

Sample instance

<ChartOfAccounts>
   <GLEntityID>normalizedString</GLEntityID>
   <GLNominalAccount>normalizedString</GLNominalAccount>
   <EffectiveTimePeriod>
      <InclusiveIndicator>true</InclusiveIndicator>
      <StartDateTime>2000-01-01</StartDateTime>
      <Duration>P1Y2M3DT10H</Duration>
   </EffectiveTimePeriod>
   <AccountType>normalizedString</AccountType>
   <CurrencyCode>AED</CurrencyCode>
   <Description>string</Description>
   <Note>string</Note>
   <UserArea>
      <!--any element-->
   </UserArea>
</ChartOfAccounts>