Tuesday, October 13, 2026

Oracle Fusion Accounting Hub Series – Part 2: Registering a Source System

 

In the first blog of this series, we explored the fundamentals of Oracle Fusion Accounting Hub (FAH) and discussed its key components, architecture, and business benefits. Now it's time to move to one of the most important setup activities in any Accounting Hub implementation: Registering a Source System.

A successful Accounting Hub implementation starts with properly defining the systems that will feed transactions into FAH. Whether transactions originate from a custom billing application, legacy ERP, industry-specific solution, or third-party platform, Oracle requires each source system to be registered before accounting transformations can be configured.

In this blog, I'll walk through the process of registering a source system using Oracle's spreadsheet-based setup approach.

Why Register a Source System?

The source system registration serves as the foundation for the Accounting Hub framework. It defines:

-          Where transactions originate

-          The event structure associated with those transactions

-          Transaction attributes available for accounting rules

-          Line-level attributes available for journal generation

-          Data elements that will be available for reporting and inquiry

Think of this as creating the "language" that Accounting Hub will use to understand your external transactions.

 

Download the Accounting Hub Setup Template

Navigation

Setup and Maintenance → Fusion Accounting Hub → Accounting Transformation → Create Subledger Application Setups in Spreadsheet

From this task, download the setup spreadsheet template.

 

Click Download Setup Template

 

Oracle recommends using a separate spreadsheet template for each source system registration. This keeps the setup organized and makes future maintenance significantly easier.

When populating the setup workbook, I recommend following the same logical flow that Oracle uses internally:

  1. Register the Source System
  2. Define the Event Model
  3. Configure Transaction (Header) Information
  4. Configure Line Information

Building the setup in this sequence helps avoid validation issues and makes the overall design easier to understand.

 

 

Step 1- Defining Source System-within the Source System tab, enter:

-          Source System Name

-          Short Name

For example- I will be using TGBilling System

This represents a fictional billing application that will send transactions into Accounting Hub for accounting generation.

One area- I was confused was – what do you mean by source system, process category, event class and event types

To understand the whole accounting model of FAH- lets take example of Payables Subledger Application- based on FAH Model- Payables is considered as a Source System.

Source System

In Payables, the source system is:

Payables

This is the application generating the business transactions.

Process Categories

Examples include:

-          Invoices

-          Payments

These group similar business processes together.

Event Classes

Within the Invoice process category, examples include:

-          Credit Memo

-          Debit Memo

-          Standard Invoice

Event Classes represent major categories of transactions.

Event Types

Under each Event Class, Oracle defines specific transaction events, such as:

-          Credit Memo Adjusted

-          Credit Memo Cancelled

-          Credit Memo Validated

These events ultimately trigger accounting generation.

Payables (marked in Red) is the source system

Invoices and Payments marked in Green are Process Categories

Event Class- Credit Memo, Debit Memo marked in Brown

Credit Memo Adjusted, Canceled and Validated are Event Types (Transaction Types)

For my TGBilling System example:

- One Process Category

- One Event Class

- Multiple Event Types

As a result, most of the setup effort will focus on defining the Event Types that drive accounting behavior.

Configuring Transaction Information

Once the source system and event structure are defined, the next step is configuring Transaction Information.

To understand this better, let's review the transaction information setup used within Oracle Payables.

Each transaction attribute requires:

-          Event Class Association

-          Name

-          Short Name

-          Data Type

Supported data types include:

-          Number

-          Text

-          Date

-          Long Text

Another important field is Journal Display.

This controls whether the value is visible within:

-          Journal inquiries

-          Accounting reports

-          Transaction drilldowns

Depending on reporting requirements, this can be set to Yes or No

 

Transaction Attributes for TGBilling System

For my example source system, I am adding the following transaction attributes:

Attribute

Purpose

Customer Name

Customer identification

Invoice Amount

Transaction amount

Type of Service

Service classification

Transaction Date

Invoice date

 

Since Transaction Date is mandatory, I will use it as the Invoice Date attribute within the source system.

These attributes need to be available across all configured Event Classes.

 

The setup workbook also provides a Line Information section.

Just like Transaction Information, Line Information allows you to capture attributes at the transaction line level.

Let's first examine how Oracle Payables uses line-level attributes.

For my simple TGBilling System example, I do not have any business requirement for additional line-level information, so this section can remain minimal.

 

 

After completing all tabs within the workbook:

  1. Return to the Source System tab.
  2. Run the validation process.
  3. Resolve any validation errors.
  4. Generate the upload ZIP file.

The generated ZIP file will be used to upload the source system definition into Oracle Fusion Accounting Hub.

Once uploaded successfully, the source system becomes available for the remaining Accounting Hub setup activities, including:

-          Mapping Sets

-          Journal Line Rules

-          Account Rules

-          Description Rules,etc.

One of the biggest mistakes I see in FAH implementations is rushing through source system design. Investing time upfront to properly define event models, attributes, reporting requirements and accounting drivers can save significant rework later when accounting rules are being built.

My recommendation is to involve both accounting and business stakeholders while designing the source system structure. The transaction attributes defined at this stage often become the key drivers for accounting derivation and reporting.

In the next blog of this Accounting Hub series, we'll move beyond source system registration and start configuring the Accounting Transformation framework, including how transaction attributes are mapped and used to derive accounting entries. We will be starting with creating Mapping Sets

 

No comments:

Accounting Hub Transformation Rules: Where the Magic Really Happens in Oracle Fusion Accounting Hub (Part 3)

  In the first two blogs of this series, I covered what Oracle Fusion Accounting Hub is and how transactions flow from source systems into S...