AccountingModelConfig

Represents the mapping of the financial data model to a logical data model and configuration for the generation of Transaction Journal records.

Where possible, we changed noninclusive terms to align with our company value of Equality. We maintained certain terms to avoid any effect on customer implementations.

This type extends Metadata and inherits its fields.

AccountingModelConfig components have the suffix .accountingModelConfig and are stored in the accountingModelConfigs folder.

Introduced in API version 57.0.

  • Type: AccountingType (enumeration of type string)

  • Required: Yes

  • Description: Required.

    Determines whether the accounting set generates revenue or expense type transaction journal records.

  • Possible values:

    • Expense
    • Revenue
  • Type: string
  • Required: No
  • Description: The code for your accounting system’s default accrual account.
  • Type: string
  • Required: No
  • Description: Represents the name of your account for written off payments.
  • Type: dateTime

  • Required: Yes

  • Description: Required.

    The date used to filter source records for processing. The Accounting Subledger only considers records created on or after this date.

  • Type: ExpectedCashFlowGrouping (enumeration of type string)
  • Required: No
  • Description: Determines whether Accounting Subledger groups transaction journal records by fund account or by a combination of fund account and due date.
  • Possible values:
    • GroupByFundAccount
    • GroupByFundAndDueDate

Changing this setting doesn’t impact existing records; it only affects records created or reversed afterward.

  • Type: string
  • Required: No
  • Description: Reserved for internal use.
  • Type: string

  • Required: Yes

  • Description: Required.

    Represents the structure of your financial data in JSON format.

  • Type: boolean

  • Required: Yes

  • Description: Required.

    Indicates whether only records that are true are processed when the Subledger Job runs.

  • Type: boolean
  • Required: No
  • Description: Reserved for internal use.
  • Type: boolean

  • Required: Yes

  • Description: Required.

    Indicates whether the Accounting Model has been used or activated at least once (true) or not (false).

If the value is set to true , you can’t select another object for the object model or change the number of objects associated with that Accounting Model.

  • Type: string
  • Required: No
  • Description: Reserved for internal use.
  • Type: string

  • Required: Yes

  • Description: Required.

    A user-friendly name for AccountingModelConfig, which is defined when the AccountingModelConfig is created.

  • Type: PaidCashFlowGrouping (enumeration of type string)
  • Required: No
  • Description: Determines the level of detail for generated transaction journal records.
  • Possible values:
    • GroupByFundAccount — Accounting Subledger splits all transaction journal records into fund accounts. Secondary records are created for payment type records but not for transaction type records.
    • GroupBySummary — Accounting Subledger only splits credits for revenue and debits for expenses by fund accounts.
  • Type: string
  • Required: No
  • Description: Specify the record type IDs from the primary object to be processed. This field is case-sensitive.

If no record type is specified in the filter, all records are processed.

  • Type: int
  • Required: No
  • Description: Determines the load order sequence of the multiple Accounting Model. The lower number runs first. For example, load order 1 runs before load order 2.

The following is an example of an AccountingModelConfig component.

The following is an example package.xml that references the previous definition.

This metadata type supports the wildcard character * (asterisk) in the package.xml manifest file. For information about using the manifest file, see Deploying and Retrieving Metadata with the Zip File.