1. Implementing Accounting Hub
  2. Advanced Event Model Configuration

Advanced Event Model Configuration

Use advanced event model configuration to segregate accounting data from multiple source systems processed through a single Accounting Hub application into separate journal categories in the General Ledger.

Accounting Hub applications support multiple process categories and event classes within a single application to provide greater flexibility and granularity in accounting event processing.

If you use a single Accounting Hub application to import transactions from multiple source systems, you can use multiple event classes to classify journals based on the originating source system. You can also use multiple process categories to separate Create Accounting processing for different data sets and reduce performance impacts from high-volume transaction processing.

You can also exclude specific event types from accounting within an accounting method. Use the Exclude option in the Journal Entry Rule Set Assignments section of the Accounting Method page to disable accounting for selected journal entry rule set assignments.

When you enable the Exclude option for a journal entry rule set assignment, the Create Accounting process doesn't generate accounting entries for the associated event types.

Note:

You must enter the Rule Set value for a journal entry rule set assignment even if the assignment is excluded from accounting.

Source System Definition Template

Use the source system definition template to define the event model hierarchy for Accounting Hub applications, including:

  • Process categories
  • Event classes
  • Event types
  • Source assignments

The Source System sheet includes these columns:

  • Process Category
  • Process Category Short Name
  • Event Class
  • Event Class Short Name
  • Event Type
  • Event Type Short Name

The Transaction Information and Line Information sheets include the Event Class column to capture source assignments for specific event classes.

You can define:

  • Sources common to all event classes
  • Sources specific to individual event classes

Specify All in the Event Class column to assign a source to all event classes.

Configure Event Models Using Templates

For existing Accounting Hub applications, you can use the Download Setup Template action in the Event Model section of the Manage Subledger Application page to download a rapid implementation template.

Use the template to:

  • Add process categories
  • Add event classes
  • Add source assignments

After you validate the changes and generate the upload ZIP file, upload the file using the Upload Event Model Changes action.

Configure Event Models from the Manage Subledger Application Page

Use the Event Model section of the Manage Subledger Application page to:

  • Add process categories
  • Delete process categories
  • Add event classes
  • Delete event classes

Add Sources or Source Assignments for Event Classes

When you add a source for Accounting Hub applications with multiple event classes, specify the event class to assign the source correctly.

You can reuse sources across multiple event classes at the header or line level. You can also add additional event class assignments from the Assignments window for a specific source.

Group Source Data for Large Transactions

When your Accounting Hub application includes multiple event classes, you can enable the Group Source Data on Import option for specific event classes.

After you enable this option, select the event class source assignments at the line level that must be used as grouping attributes for splitting large transactions.

Purge Transactions by Event Class

Use event class as an additional optional filter criterion in the Accounting Hub Maintenance process to purge:

  • Invalid transactions
  • Unaccounted transactions
  • Pending reversal transactions

Upload Transactions for Event Classes

The transaction upload template contains a pair of header and line CSV files for each event class.

You can:

  • Upload transactions for all event classes
  • Upload transactions for selected event classes only

Exclude unnecessary CSV files from the upload ZIP file when transaction import isn't required for specific event classes.

Event Modeling Components

Before you design the accounting event model, analyze your source systems thoroughly.

Event Types

Event types represent business transactions within the source system that result in financial activity and require accounting entries.

Define each transaction type with financial impact as a unique event type in the Accounting Hub application event model.

Event Classes

Event classes group event types that:

  • Originate from similar business processes
  • Share common accounting rules

Defining accounting rules at the event class level simplifies accounting rule maintenance.

Each event class is mapped to a journal category used to generate journals in General Ledger.

Process Categories

Process categories group related event classes based on accounting processing requirements.

Using process categories helps you:

  • Balance system workloads
  • Reduce performance bottlenecks
  • Minimize processing time
  • Simplify exception management

For example, you can process invoice-related event classes separately from payment-related event classes.

Exclude Accounting for Event Types

Use the Exclude option in the Journal Entry Rule Set Assignments section of the Accounting Method page to exclude specific event types from accounting.

You can use this option to:

  • Support specialized accounting treatments
  • Support delta ledger processing between primary and secondary ledgers
  • Reduce redundant accounting entries

In a delta ledger configuration:

  • Common accounting entries are recorded only in the primary ledger.
  • Differential accounting entries are recorded only in secondary ledgers.

If you exclude upstream accounting events, you might need to update journal line rules for downstream events.

Considerations

Keep these considerations in mind when you configure advanced event models:

  • You must enable the Flexible Configuration of Accounting Hub Cloud Service End to End Flow feature before you configure advanced event models.
  • After you configure multiple event classes, transaction import always uses the latest FBDI transaction template with all columns.
  • You can't enable reversals for specific event classes only.
  • For existing Accounting Hub applications, only incremental additions of process categories, event classes, and sources are supported through the rapid implementation template.
  • You can't update or delete existing process categories, event classes, or event types through the rapid implementation template.
  • You can define a maximum of 10 event classes and 10 process categories in an Accounting Hub application.
  • You must configure advanced event models in both source and target environments before you migrate setup.

Keep these additional considerations in mind when you use the Exclude option:

  • Setup changes to the Exclude option can take up to one hour to reflect in online accounting.
  • The Create Multiperiod Accounting process isn't affected by the Exclude option.
  • If audit is enabled, updates to the Exclude option are audited.