Adding Supplemental Data to GL Journal Entries

You can use custom attributes, MATRIXX Event Detail Records (EDRs), or make a change to your General Ledger (GL) processor to add supplemental data to your GL journal entries.

You have these options for using and saving supplemental data in GL journal entries:
  • Adding custom attributes to GL transaction profiles — Any custom attributes you specify in GL transaction profiles are copied into the GL info array in events and then added to GL journal entries.

    To add custom attributes to a GL transaction profile, you must first define a custom MDC based on the MtxEventGlInfoAttr MATRIXX Data Container (MDC) and add the necessary fields. When using My MATRIXX to define a GL transaction profile, you can select fields from the extended MtxEventGlInfoAttr MDC and assign values to those fields. When a GL transaction profile is selected to generate a GL info record for a charge, any custom attributes defined in the GL transaction profile are copied to the event and then added to GL journal entries by the GL processor.

  • Using fields from EDR — The GL processor can copy selected fields in events to GL journal entries. The copyEventFields property accepts a list of comma-separated fields to add. The list can include:
    • Top-level event fields.
    • Fields of applied offers, including custom ProductOffer and PurchasedOffer attributes.
    • Fields of applied taxes.
    • Fields of applied bundles, including custom bundle extensions and purchased bundle attributes.
    • Fields of applied catalog items, including catalog item template attributes.
    • Fields of user-defined data specified in SubMan APIs and recorded in EDRs.

    However, you cannot include arrays or structs.

    The GL processor copies the following fields. You do not have to specify them with the copyEventFields property:
    • EventID
    • GlDate
    • GlCenter
    • AppliedOfferArray.ProductOfferIsTaxIncluded
    • AppliedOfferArray.ProductOfferTaxRate
    • AppliedOfferArray.ProductOfferTaxClassName
  • If your GL journal entries recognize deferred revenue, you can also use the copyEventFields property to add the recognized or remaining deferred revenue from these fields to GL journal entries:
    • EarnedBalace — The amount of recognized deferred revenue.
    • UnearnedBalance — The amount of remaining deferred revenue.

If you use MongoDB with the GL utilities, update the copyEventFields property in the gl_processor.yaml file.

If you use PostgreSQL, update the copyEventFields property in the cn-gl-processor Helm values file.