Holds Header information associcated with the JournalEntry noun. Holds Line information associcated with the JournalEntry noun. The ID associated with this Chart of Accounts (the name in tenant default mandatory locale). Not needed on incoming journals from source systems. FC adds because it needs it anyway. Published on journals going to BIS to save an extra join - BIS can quer The Name associated with this Chart of Accounts. Not needed on incoming journals from source systems. FC adds because it needs it anyway. Published on journals going to BIS to save an extra join - BIS can query it directly. The Financial Period that this journal was expected to be posted to. Initially set from the original journal in the source system. If the journal lines from source system journal contain mixed periods this is empty. If a period is supplied here it will be used for all lines, regardless of any entries on the lines. If no period is supplied either here or on the lines, periods will be derived from the accounting date at header level (but set in MultiBook/AccountingDate/PeriodID - this field is never updated by FC.) If that is not supplied, the journal is put on hold and the header can be edited (that can update this field). Every journal which leaves FC is for a single period - this is one of the main tasks FC does for MBL - create journals with single period and single date. In that case, when a journal is split, this field is backfilled by FC to hold the period as supplied on the lines by the source system. We assume this to be correct when it is supplied, and will . MBL works off the Financial MultiBook/Accountin Date/PeriodId version. Source system's accounting date. Retained and passed on, but MBL works off the MultiBook/AccountingDate/PostDateTime, which occasionally is not the same as this one. Journals can arrive using multiple dates (when this field is blank) but are always passed on with a single date. FC also makes sure dates and periods are aligned. We expect this date to be correct when it is supplied, but reserve the right to change it if it falls outside the accounting period above, when it will be amended by inserting a MultiBook/Accounting Date/PostDateTime which is either the first or the last day of the Accounting period. If it is supplied, then this date (or the adjusted version) will be applied to all journal lines by FC, regardless of what they contain. If it is not supplied, FC will work from line dates and split the journal if necessary by date or adjusted date. If split by source system date FC then backfills this once journals are split, from the line date as supplied by source system. The Financial Year that this journal was expected to be posted to. From the original journal in the source system. If the journal lines from source system journal contain mixed periods/dates this is empty Identifies the Name of the object in which associated. Indicates the time period in which the associated component is effective. 0 or nonexistent when this is a standard period. Only used for adjustment periods. Rarely supplied by source system, though some will map year-end periods to adjustment periods, eg 13 to 12.1. Can exist on CDx or JE journals. MBL will use the MultiBook/AccountingDate/AdjustmentSequence field. This is used to indicate a short year when the financial year is adjusted. Unlikely to be supplied by most source systems, though may be created by mapping. Just passed on if it is. MBL will use the MultiBook/AccountingDate/AdjustmentSequence field. Journal Type ID of the accounting Journal that is being referenced. Mandatory. If missing or invalid, entire journal will be rejected - the most critical error. Name of the Journal Type. Not needed on incoming journals, added when MBL publishes to BIS to save joins. FC will remove if supplied by source system. Is the identifier of the given Line Component within the document An identifier for an object. The ID has a number of possible attributes to further define how it should be used.. Identifies the engineering change revision that this entity addresses. The code for the currency associated with an amount. The code for the currency associated with an amount. Valid currency. If it is present in header then the header value will be used and this value overwritten by FC. If no value in header, this is a mixed currency journal. If Book amount is copied (see above) then this is same code as Book currency. Rate from Originating to Book currency. Calculated by FC (first book) and MBL (other books). Based on 1:1 units. Rounded to default rounding on Rate Type used for source -> book conversion. No lookup of Currency fortress rates. Specifies the unit base of the source currency for currencies with small denominations. Specifies the unit base of the target currency for currencies with small denominations. True means it is a division signed rate, and false is a multiply signed rate. It is preferred to use multiply signed rates so set to False where possible. The reference tot he rate type for a specific currency exchange rate. Only supplied if the Amount is supplied, except on Reval and difference postings, when a currency code may be supplied with a zero amount. Reference to a Person Noun The date and time that this journal was approved for posting to the ledger. If fields supplied by source system, passed through. If none supplied and we have approvals in FC, then added in FC The code for the currency associated with an amount. Not currently used The date and time that the Journal Entry document was generated. The time this BOD is generated. Either a date or a period must be supplied either at header level or on each line. This is the link that ties back to a sub ledger transaction entry ID. It is the identifier of an original/ source transaction or document. The type indicates the type of document i.e. PurchaseOrder, Invoice, Receipt, Credit Memo, Voucher etc. For example, it could be the receipt or the summarized inventory activity. This is the singular field that refers to an audit record. Together with the Sender information, this is part of the referencing system, which will enable drill back audit trail functionality. The (originating) amount is the real-world currency in which the transaction actually occurred, eg invoice currency or cheque currency or payroll currency. In the case of a mixed currency journal this element is not used, and no currency code is supplied For transactions entered directly into the GL this currency is simply chosen and entered by the accountant. Source system - totals can be processed by processing all the lines first before sending out the BOD. Normally positive. If negative is a negative debit, and debit lines must sum to a negative debit. This is the total amount - It is the total of all Debits, but it excludes values posted to Statistical Accounts. This is the total amount - It is the total of all Debits The book amount is the amount in the single, standard currency of the book. In the primary book it is supplied by the source ledger system, which normally calculates it from the originating amount (except for LN which triangulates). In other books it is calculated from the source amount which is one of the originating currency, or the book or source currency of the preceding book in the Conversion Chain. This is the Book currency total debits. We will support zero value journals so it can be zero. It can be zero in two cases: 1. All of journal is posted to Statistical accounts so there are no Book Amounts or 2. A transaction has been voided LatAm style, so has zero value but still needs to appear in books. It is NOT mandatory. Normally positive. If negative is a negative debit, and debit lines must sum to a negative debit. This is the total amount - It is the total of all Debits. The source amount is the amount from which the book currency is calculated. In a journal published by MBL, it is a copy of another value. We replicate it so that BIS can easily produce reports showing how the book amount was derived, without having to reconstruct the Conversion Chain logic. This is the total Source amount - total of the Debits. Normally journals from source systems will have nothing in the source amount field. However, given the way that LN calculates its book amount, the source amount may be populated by what LN calls the “reference” currency value. This is truly the amount from which the book amount is calculated, so fits the definition of a source amount. FC copies Originating Amount into Source Amount, for both source system journals (unless it is already populated) and for JE and JC entries. If there is a single currency, then the total is inserted here: if mixed currency, then this is left blank. Normally positive. When MBL publishes journals, iif the source currency is the Originating currency and the journal is a mixed currency journal this element is not used. Otherwise it is populated by MBL. Identifies the types associated with the PaymentTerm. Used to hold a description for the journal. Eg invoice, Payroll, Cash Payment - the BOD type. Most source ledger systems not being fed by BODs, so not able to provide this. FC will provide in future when it starts to transform other BODs into journals. A free form note. The lang attribute identifies the language that the note is in. The author identifies the author of the note. The enrtyDate indicates the date the note was entered or last modified Any other document (BOD) references that are passed through from the Source System This is likely to come into use once Fin Controller receives documents directly, not via a Source Ledger system. These references allow tracking the history of the transaction through the entire business cycle. But as long as the previous step is always provided, we could drill from BOD to BOD, so only one is really needed, which is held in SourceDocumentReference above: these others are optional. 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 throught 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. The journal ID from the source system (TBD) The journal number from the source ledger system. This is passed through as data. It may be numeric or may eg have a prefix. We assume it will be unique within a ledger (ie an Accounting Entity) But we wi For future use, hard coded to "Actual" on all MBL and Financial Controller Journals. Future options may include Budget, Forecast etc A "Standard", "Correction" or "Reversal" Journal. A Reversal Journal is the exact reverse of an existing posted journal. A Correction replaces the original posted journal or journal lines on a journal. Reversal and correction for FC use only. All source Journal Type Identifies the Accounting Book which is the first book of entry for this Journal. The value is normally null on a source system journal, but must be present if this is a Correction or Reversal journal If null then the Primary Book is assumed. If the So Posting status of Journal A flag to identify if this journal was produced from a source ledger system, JE, CDx, other system similar to a ledger, other system not a ledger. Source system sets this, unless JE when FC sets it. It helps to decide what validation is applied to journ Some countries have multiple references for the same invoice. China has an internal invoice number and an external invoice number for the same physical invoice. These are human-readable references. Supplied by source system and passed on. One day may b This may be a sequential number, or a set of sequential numbers with different prefixes. Used (eg in Italy, Argentina) where source systems have unique sequential numbering per document type such as sales invoice or purchases. Supplied by source system This contains a reference to the person who entered the journal. This contains a reference to the person who last made a modification to the journal. This contains a reference to the person who posted the journal. This contains a reference to the person who approved the journal. These are used for any warnings which are needed for the report e.g. currency rate not found Identifies the date used to go and look up currency exchange rates which are date based. The unit-of-measure (UOM) code associated with a quantity. This is based upon the ISO standard. When no schemeName exists this is the default ID for the enterprise at the level where this object is maintained. The value of the ID must uniquely identify this object throughout the enterprise within the scope of the level where it is maintained (tenant, accounting entity or location). The specific values for this attribute are determined by the individual noun. The accounting entity that is associated with the maintenance of this instance of the noun. For objects that are maintained at the tenant level this attribute must not be included in the document. The location that is associated with the maintenance of this instance of the noun. This attribute must not be included on the ID of objects that are maintained at the tenant or accounting entity level. The number of times this object has been published with these attributes for the accounting entity and location. The LID of the system where the object can be maintained. This can be used by BIS to help automate the drill back process. This attribute contains the Code List ListID for the code that it is associated with. Journal Warning The accounting entity that is associated with the maintenance of this instance of the noun. For objects that are maintained at the tenant level this attribute must not be included in the document. The location that is associated with the maintenance of this instance of the noun. This attribute must not be included on the ID of objects that are maintained at the tenant or accounting entity level. A nominated Code List, as defined in Ledger Setup. One of the 30 user dimensions. The accounting entity that is associated with the maintenance of this instance of the noun. For objects that are maintained at the tenant level this attribute must not be included in the document. The location that is associated with the maintenance of this instance of the noun. This attribute must not be included on the ID of objects that are maintained at the tenant or accounting entity level. Enum list in Public MDM. Only needs one value for now. Is the primary document id for the document associated. Is the alternate document id for the associated document. Free form text that describes the object and repeats as needed to provide support for multilingual descriptions Rate Type Is the alternate document id for the associated document. Free form text that describes the object and repeats as needed to provide support for multilingual descriptions When no schemeName exists this is the default ID for the enterprise at the level where this object is maintained. The value of the ID must uniquely identify this object throughout the enterprise within the scope of the level where it is maintained (tenant, accounting entity or location). The specific values for this attribute are determined by the individual noun. The accounting entity that is associated with the maintenance of this instance of the noun. For objects that are maintained at the tenant level this attribute must not be included in the document. The location that is associated with the maintenance of this instance of the noun. This attribute must not be included on the ID of objects that are maintained at the tenant or accounting entity level. The number of times this object has been published with these attributes for the accounting entity and location. The LID of the system where the object can be maintained. This can be used by BIS to help automate the drill back process. Not used in this instance. Only one instance of Description should be used in this noun. This is required for language codes other than 'en-us' when the element that includes this attribute is used. The code from the Code, ie the human readable code The name of the code list, in the system language, no locale. This is required for language codes other than 'en-us' when the element that includes this attribute is used. The accounting entity that is associated with the maintenance of this instance of the noun. For objects that are maintained at the tenant level this attribute must not be included in the document. The location that is associated with the maintenance of this instance of the noun. This attribute must not be included on the ID of objects that are maintained at the tenant or accounting entity level. Yes means this is another element somewhere on the Journal header or line which is replicated here in order to serve up all nouns and codes (including enums) as the same type of data in the same list. The sequence attribute is used for the ordering of elements within a document. It is not intended to be used as an identifier. An identifier for an object. The ID has a number of possible attributes to further define how it should be used.. Free form text that describes the object and repeats as needed to provide support for multilingual descriptions The amount of discount allowed expressed in the transaction currency. Monetary amount used for consolidation at accounting entity level. Monetary amount used for consolidation at tenant level. The ID of a source document (BOD) that fed the transaction that generated this journal. BOD number - highly unlikely to be supplied by source ledgers. FC will provide in future when it starts to transform other BODs into journals. Likely to be supplied Identifies the engineering change revision that this entity addresses. The ID of the LedgerSetup. This is the same as the Accounting Entity Code ID of Rate Type. Which is name in tenant default mandatory locale. Identifies the engineering change revision that this entity addresses. An identifier for an object. The ID has a number of possible attributes to further define how it should be used.. Identifies the engineering change revision that this entity addresses. This is the data as supplied by the source system. FC and MBL just record and pass it on. The BOD ID Identifies the engineering change revision that this entity addresses. The ID of the source document (BOD) from the source system that fed the transaction that generated this journal. BOD number - highly unlikely to be supplied by source ledgers. FC will provide in future when it starts to transform other BODs into journals Identifies the engineering change revision that this entity addresses. The ID of the source document (BOD) from the source system that generated this journal. FC copies the details of this BOD into these fields. MBL then copies this information. This allows access back to the journal in the source system (TBD) Identifies the engineering change revision that this entity addresses. heading Is the identifier of the given Line Component within the document Eg invoice, Payroll, Cash Payment - the BOD type. Most source ledger systems not being fed by BODs, so not able to provide this. FC will provide in future when it starts to transform other BODs into journals. Is the primary document id for the document associated. Is the identifier of the given Line Component within the document The name of the noun that carries the information being referenced. Valid values are carried in the DocumentType Code list. The timestamp marking the beginning of a time period during which a related entity or status is effective or applicable. Indicates the duration of time as represented by ISO 8601. Where the value space is a six dimensional space where the coordinates designate the Gregorian year, month, day, hour, minute, and second. The number of seconds can include decimal digits to arbitary pecision. This can be used in place of the EndDateTime, but not in conjunction with it. Is the ending timestamp of the event. This can be used in place of the Duration, but not with it. The timestamp marking the beginning of a time period during which a related entity or status is effective or applicable. Indicates the duration of time as represented by ISO 8601. Where the value space is a six dimensional space where the coordinates designate the Gregorian year, month, day, hour, minute, and second. The number of seconds can include decimal digits to arbitary pecision. Is the ending timestamp of the event. This can be used in place of the Duration, but not with it. Reference to a Person Noun The date and time that this journal was entered. Entered means prepared - posting is handled separately below. Eg a temp may enter and an accountant then post This date=time would then relate to a Draft version. If posted immediately could be same as p Valid currency, e.g. GBP. Must be same as currency defined for book, otherwise this is an error. Must be same in header and on all lines. This is book currency of primary book for source ledger, or first posting book for JE/JC, it is book currency of bo Only supplied if the Amount is supplied, except on Reval and difference postings, when a currency code may be supplied with a zero amount. Must be valid for the Chart of Accounts for this book. It cannot be set to Deleted. In either case, the journal is held if any one line shows the error. MBL maps these for all but the initial book. We will post to Closed accounts with a warning messag Name of the Natural Account. Only used by MBL when publishing to BIS. Not needed on source system or FC published journals. Published on outgoing BOD for use in BIS. FC also needs to know this for validation, so it looks it up, stores it and passes it on to MBL. All available locales. The ID of the accounting entity that is associated with this ID The ID of the location that is associated with this ID when applicable. When no schemeName exists this is the default ID for the enterprise at the level where this object is maintained. The value of the ID must uniquely identify this object throughout the enterprise within the scope of the level where it is maintained (tenant, accounting entity or location). The specific values for this attribute are determined by the individual noun. The accounting entity that is associated with the maintenance of this instance of the noun. For objects that are maintained at the tenant level this attribute must not be included in the document. The location that is associated with the maintenance of this instance of the noun. This attribute must not be included on the ID of objects that are maintained at the tenant or accounting entity level. The number of times this object has been published with these attributes for the accounting entity and location. When no schemeName exists this is the default ID for the enterprise at the level where this object is maintained. The value of the ID must uniquely identify this object throughout the enterprise within the scope of the level where it is maintained (tenant, accounting entity or location). The specific values for this attribute are determined by the individual noun. The accounting entity that is associated with the maintenance of this instance of the noun. For objects that are maintained at the tenant level this attribute must not be included in the document. The location that is associated with the maintenance of this instance of the noun. This attribute must not be included on the ID of objects that are maintained at the tenant or accounting entity level. The number of times this object has been published with these attributes for the accounting entity and location. The LID of the system where the object can be maintained. This can be used by BIS to help automate the drill back process. Accounting Entity ID, as defined (for now) in Code List. Depends on BOD being identified - may or not have a Location The LID of the system where the object can be maintained. This can be used by BIS to help automate the drill back process. Not used - Journal Type is defined at Tenant level. Leave blank. Not used - Journal Type is defined at Tenant level. Leave blank. The ID of the accounting entity that is associated with this ID Not used - Ledgers are not divided into Locations The ID of the accounting entity that is associated with this ID The ID of the location that is associated with this ID when applicable. The LID of the system where the object can be maintained. This can be used by BIS to help automate the drill back process. When no schemeName exists this is the default ID for the enterprise at the level where this object is maintained. The value of the ID must uniquely identify this object throughout the enterprise within the scope of the level where it is maintained (tenant, accounting entity or location). The specific values for this attribute are determined by the individual noun. The ID of the accounting entity that is associated with this ID The ID of the location that is associated with this ID when applicable. The number of times this object has been published with these attributes for the accounting entity and location. The LID of the system where the object can be maintained. This can be used by BIS to help automate the drill back process. The ID of the accounting entity that is associated with this ID The LID of the system where the object can be maintained. This can be used by BIS to help automate the drill back process. The ID of the user who last modified the contents of the journal on the system The ID of the person who posted the Journal wherever it was first-posted - could be in Source Ledger System or could be in FC The ID of the user who approved the journal . If fields supplied by source system, passed through. If none supplied and we have approvals in FC, then added in FC An identifier for an object. The ID has a number of possible attributes to further define how it should be used.. The ID of the accounting entity that is associated with this source document Accounting Entity ID, as defined (for now) in Code List. The ID of the location that is associated with this source document when applicable. The System issuing the journal will provide a unique ID. This can consist of the journal number, and if necessary the book and year the journal is intended for. The ID for this object formatted as closely as possible to the way the customer would expect to see the ID. This element is used for display only and has no other purpose. Holds basic information associated with Journal Entry. Originating or transactional amount, which is the real world currency of the transaction. If none is entered/supplied then the book amount is copied in JE or FC. The originating value is held in MBL as part of the core transaction data, alongside r The book amount or base currency amount. Normally positive when the DebitCredit Flag is "Debit" and negative when the DebitCreditFlag is "Credit". If opposite sign, then all values on line must be opposite sign or the line is in error. Can be zero - eithe Normally blank for source ledger journals (but see comments re LN on header fields). FC will copy Originating Amount to Source Amount, so that first book has same pattern of values as other books. FC copies Originating Amount into Source Amount, for bo Source to Book rate. This is the main rate that we store. Normally supplied by source ledger. If not supplied, derived mathematically from values. In JE, FC generates for initial book, where normally Source=Originating. In JE it will look to user l Calculated rate for reporting only This element will used to store SunSystems 'Value 3' which is used as the reporting currency. This element will used to store SunSystems 'Value 4' which is used as either a secondary reporting currency, or secondary base currency. Natural Account for this Journal line These include both the user-defined Dimensions, defined on the Chart of Accounts Dimension Sequence, and the System Dimensions, eg Journal Type and Accounting Book. For User Dimensions, only the Dimensions/Codes defined for the Chart of Accounts of this 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 throught 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. Usually the source ledger's journal line number. If it originated in JE, then the JE line number. Can be blank when JC or MBL adds a line to a journal from a source ledger. DEBIT or CREDIT. If debit we expect positive amounts in all fields (book, source, originating or functional, source, amount, as well as all memo values which are present). If credit we expect negative values. Signs can be reversed, but all v Date and period information for this line, coming from the source system. FC standardises, splits journals, so FC and MBL only produce journals with single period and single date, which are held on the header. These fields are for audit purposes only, a This is the data as supplied by the source system. FC and MBL just record and pass it on. For example the invoice number or journal number in the source system this line was created for. But this must be a BOD, so will not be supplied by source ledger s The line type relates to the type of journal line and uses one of the following values form the ‘Line Types’ enumerated code list in PMDM: RealisedGainsLosses, RevaluedGainsLosses, TranslationDifference, RoundingDifference, Standard (default value). Note that source systems using a SyncSourceSystemJournalEntry always send the value ‘Standard’. AGL creates lines containing the remaining values in addition to ‘standard’. Requirement for those systems that require day books. Supplied by source system and passed on by FC and MBL. Normally this is an integer but it may have a prefix. Any other document (BOD) references that are passed through from the Source System This is likely to come into use once Fin Controller receives documents directly, not via a Source Ledger system. These references allow tracking the history of the trans Some countries have multiple references for the same invoice. China has an internal invoice number and an external invoice number for the same physical invoice. Human readable references This may be a sequential number, or a set of sequential numbers with different prefixes. Used (eg in Italy, Argentina) where source systems have unique sequential numbering per document type such as sales invoice or purchases. Supplied by source system The narrative that describes the reason for the entry. Monolingual. Optional A numeric amount associated with the code referenced. Will either be provided by a source system so copied onto outgoing journals, or it can be assigned at journal entry time. If supplied, both a code and a value must be supplied, otherwise an error wil These are used for any warnings which are needed for the report e.g. currency rate not found Identifies the date used to go and look up currency exchange rates which are date based. This this a segmented account with the Nominal Account and then a delimited list of the dimension values. As an example, SX.e uses division, department, account, sub-account. The sequence attribute is used for the ordering of elements within a document. It is not intended to be used as an identifier. When no schemeName exists this is the default ID for the enterprise at the level where this object is maintained. The value of the ID must uniquely identify this object throughout the enterprise within the scope of the level where it is maintained (tenant, accounting entity or location). The specific values for this attribute are determined by the individual noun. The ID of the accounting entity that is associated with this ID. Used with the global ID - no schemeNameAttribute. This will come from the accounting entity code list. The ID of the location that is associated with this ID when applicable. . Used with the global ID- no schemeNameAttribute. The sequence number that identifies the number of times that this BOD, for this object, has been published. Used with the global ID- no schemeNameAttribute. The logical ID of the system that is this SOR for this noun instance.. Used with the global ID- no schemeNameAttribute. "Final" (we may support "Provisional" later) Free form text that describes the object and repeats as needed to provide support for multilingual descriptions date and time this document becomes effective Enum list in Public MDM This is required for language codes other than 'en-us' when the element that includes this attribute is used. When no schemeName exists this is the default ID for the enterprise at the level where this object is maintained. The value of the ID must uniquely identify this object throughout the enterprise within the scope of the level where it is maintained (tenant, accounting entity or location). The specific values for this attribute are determined by the individual noun. The accounting entity that is associated with the maintenance of this instance of the noun. For objects that are maintained at the tenant level this attribute must not be included in the document. The location that is associated with the maintenance of this instance of the noun. This attribute must not be included on the ID of objects that are maintained at the tenant or accounting entity level. The number of times this object has been published with these attributes for the accounting entity and location. The LID of the system where the object can be maintained. This can be used by BIS to help automate the drill back process. Is the primary document id for the document associated. The date that document was created within the system of record. Free form text that describes the object and repeats as needed to provide support for multilingual descriptions The ID from the BookInstance section of the LedgerSetup. Identifies the Book Instance. Name of the book in the tenant default mandatory locale. LedgerType. Enum list in Public MDM This is required for language codes other than 'en-us' when the element that includes this attribute is used. Enum Code List in Public MDM This is required for language codes other than 'en-us' when the element that includes this attribute is used. Allows an amount to be associated to a dimension code Valid code within nominated code list, eg "KG" or "TONNE" in a Code List of Weight. In some cases only one code will exist in the Code List where only one unit is used. Reference to a Person Noun The date and time that this journal was last modified? All languages All available languages This is required for language codes other than 'en-us' when the element that includes this attribute is used. This is the identifier for this Property within this document. Identifies the data type of the value of this property. The unit-of-measure (UOM) code associated with a quantity. This is based upon the ISO standard. The code for the currency associated with an amount. This attribute contains the Code List ID for the codes that are associated with corresponding entity. Dimension The accounting entity that is associated with the maintenance of this instance of the noun. For objects that are maintained at the tenant level this attribute must not be included in the document. This is required for language codes other than 'en-us' when the element that includes this attribute is used. Identifies where the note is used and is associated to an Infor defined code list, 'NoteType,' that indicates the processes that might use the note. An optional identifier, that when used can uniquely identify each instance of a note within a BOD. It is only unique within the context of the document. Indicates if the note should be published externally or if it is for internal use only. It may have the values 'Internal' and 'External'. Person who created the note Entry date and time in GMT. Status of a note. This attribute contains the Code List ListID for the code that it is associated with. Payment Basis Identifies the Terms i.e. the time and number of payments and the amount or percentage of the payment. Identifies the Discount the time and number of payments and the amount or percentage of the discount from the payment. Identifies the Peanlty what happen when the time and number of payments and the amount or percentage of the penalty to add to the payment. The sequence attribute is used for the ordering of elements within a document. It is not intended to be used as an identifier. The datetime on which the object was last modified. The date that document was created within the system of record. Free form text that describes the object and repeats as needed to provide support for multilingual descriptions A free form note. The lang attribute identifies the language that the note is in. The author identifies the author of the note. The enrtyDate indicates the date the note was entered or last modified Identifies the Terms i.e. the time and number of payments and the amount or percentage of thepayment. Identifies the Discount the time and number of payments and the amount or percentage of the discount from the payment. Identifies the Peanlty what happen when the time and number of payments and the amount or percentage of the penalty to add to the payment. This indicates the dates at which payments are made by one party to another. Identifies the types associated with the PaymentTerm. An identifier for an object. The ID has a number of possible attributes to further define how it should be used.. Free form text that describes the object and repeats as needed to provide support for multilingual descriptions The penalty amount in the transaction currency. Monetary amount used for consolidation at accounting entity level. Monetary amount used for consolidation at tenant level. When no schemeName exists this is the default ID for the enterprise at the level where this object is maintained. The value of the ID must uniquely identify this object throughout the enterprise within the scope of the level where it is maintained (tenant, accounting entity or location). The specific values for this attribute are determined by the individual noun. A container that holds a list of IDs without RevisionID. The name of the user who last modified the journal A container that holds a list of IDs without RevisionID. The name of the person who posted the Journal wherever it was first-posted - could be in Source Ledger System or could be in FC A container that holds a list of IDs without RevisionID. The name of the user who approved the journal. If fields supplied by source system, passed through. If none supplied and we have approvals in FC, then added in FC A container that holds a list of IDs without RevisionID. The name of the user who entered the journal. Entered means prepared - posting is handled separately below. Eg a temp may enter and an accountant then post. Or may be the same person. Reference to a Person Noun The date and time that this journal was first posted. This may be a source system, or for non-primary books journals may be FC Is the tag and information of the new information to be passed. Free form text that describes the object and repeats as needed to provide support for multilingual descriptions A free form note. The lang attribute identifies the language that the note is in. The author identifies the author of the note. The enrtyDate indicates the date the note was entered or last modified. Indicates the time period in which the associated component is effective. This attribute contains the Code List ID for the codes that are associated with corresponding entity. Workflow Properties Is the tag and information of the new information to be passed. Free form text that describes the object and repeats as needed to provide support for multilingual descriptions A free form note. The lang attribute identifies the language that the note is in. The author identifies the author of the note. The enrtyDate indicates the date the note was entered or last modified Indicates the time period in which the associated component is effective. This attribute contains the Code List ListID for the code that it is associated with. Journal Warning Parameters The code for the currency associated with an amount. The code for the currency associated with an amount. This is the data as supplied by the source system. FC and MBL just record and pass it on. The Financial Period that this journal was expected to be posted to. From the original journal in the source system. For JE this is blank. This is the data as supplied by the source system. FC and MBL just record and pass it on. The Accounting Date that this journal was expected to be posted to. From the original journal in the source system. For JE this is blank. This is the data as supplied by the source system. FC and MBL just record and pass it on. The Financial Year that this journal was expected to be posted to. From the original journal in the source system. For JE this is blank. Identifies the Name of the object in which associated. Indicates the time period in which the associated component is effective. This is the data as supplied by the source system. FC and MBL just record and pass it on. 0 or nonexistent when this is a standard period. Only used for adjustment periods. For JE this is blank. This is the data as supplied by the source system. FC and MBL just record and pass it on. This is used to indicate a short year when the financial year is adjusted. For JE this is blank. Valid currency, e.g. GBP. Must be same as in header if it is present in header. We will not accept mixed currency source amounts coming in from Source Ledger. We will accept in JE or by import when first book of entry is a secondary book. FC will copy Only supplied if the Amount is supplied, except on Reval and difference postings, when a currency code may be supplied with a zero amount. This is the data as supplied by the source system. FC and MBL just record and pass it on. Is the alternate document id for the associated document. This is the data as supplied by the source system. FC and MBL just record and pass it on. Date and time when the document was published Free form text that describes the object and repeats as needed to provide support for multilingual descriptions A free form note. The lang attribute identifies the language that the note is in. The author identifies the author of the note. The enrtyDate indicates the date the note was entered or last modified Is the identifier of the given Line Component within the document An identifier for an object. The ID has a number of possible attributes to further define how it should be used.. This is the data as supplied by the source system. FC and MBL just record and pass it on. Is the primary document id for the document associated. Is the alternate document id for the associated document. BOD Publication Date/Time Free form text that describes the object and repeats as needed to provide support for multilingual descriptions A free form note. The lang attribute identifies the language that the note is in. The author identifies the author of the note. The enrtyDate indicates the date the note was entered or last modified Is the identifier of the given Line Component within the document An identifier for an object. The ID has a number of possible attributes to further define how it should be used.. The name of the noun that carries the information being referenced. Valid values are carried in the DocumentType Code list. Eg invoice, Payroll, Cash Payment - the BOD type. Some source ledger systems are not being fed by BODs, so they may not be able to provide this. FC will provide in future when it starts to transform other BODs into journals. Points to an Enum Code List. When no schemeName exists this is the default ID for the enterprise at the level where this object is maintained. The value of the ID must uniquely identify this object throughout the enterprise within the scope of the level where it is maintained (tenant, accounting entity or location). The specific values for this attribute are determined by the individual noun. The accounting entity that is associated with the maintenance of this instance of the noun. For objects that are maintained at the tenant level this attribute must not be included in the document. The location that is associated with the maintenance of this instance of the noun. This attribute must not be included on the ID of objects that are maintained at the tenant or accounting entity level. The number of times this object has been published with these attributes for the accounting entity and location. The LID of the system where the object can be maintained. This can be used by BIS to help automate the drill back process. Code List "Source System Journal Code" Enum including Source Ledger, Correction, Imported from Ledger, Imported from Other, Entered (at least). Codes TBC mid-August. This is required for language codes other than 'en-us' when the element that includes this attribute is used. Rate as calculated or as it is defined in Currency Maintenance and looked up. Is the rate to convert from Source to Book currency when each are expressed in the units shown below. Is the value which is not a power of 10 in the currency rate definition. 1, 10's 100's, 1000's etc. Unit as defined in Currency fortress for rates. Must be a power of ten. If value in Currency fortress is not a power of 10, then set this to 1. One of source and target is always 1, both may be. When calculated from values 1, 10's 100's, 1000's etc. Unit as defined in Currency fortress for rates. Must be a power of ten. If value in Currency fortress is not a power of 10, then set this to 1. One of source and target is always 1, both may be. When calculated from values w True means it is a division signed rate, and false is a multiply signed rate. It is preferred to use multiply signed rates so set to False where possible Usually the same Rate Type applies to all lines in a journal. But occasionally can use different ones, normally only when a breakout code is in use. Rate type may not include rates for all codes, and system may default to Standard Rate. Exceptionally, e An identifier for an object. The ID has a number of possible attributes to further define how it should be used.. Free form text that describes the object and repeats as needed to provide support for multilingual descriptions date and time this document becomes effective The date and time that the associated object is to be completed. The date and time when the payment terms go into effect. Used in conjunction with NumberOfDays Indicates the duration of time as represented by ISO 8601. Where the value space is a six dimensional space where the coordinates designate the Gregorian year, month, day, hour, minute, and second. The number of seconds can include decimal digits to arbitary pecision. Indicates a percentage of discount that is available based on the specified term. The penalty rate (percentage) charged based on the specified term. The amount due based on the terms code expressed in the transaction currency. Monetary amount used for consolidation at accounting entity level. Monetary amount used for consolidation at tenant level. The number of months beyond the Billing Date in which payment is due. The day within the ProxMonth beyond the Billing Date in which payment is due. The daywithin the ProxWeek beyond the Billing Date in which payment is due. The type that is associated with this grouping of terms. Element for the communication of all codes. Represents the Properties or Features of the associated entity