Thursday, October 29, 2026

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 Subledger Accounting (SLA). In this third installment, we're going to the heart of every Accounting Hub implementation: Transformation Rules. This is where accountants, finance SMEs, and solution architects convert raw operational transactions into meaningful accounting entries. If you have ever wondered, "How did Oracle derive that account combination?" or "Where is that journal description coming from?", this is the layer responsible for it.

 

Lets jump in to the building blocks of Accounting Hub and how does the transformation of these accounting rules work:

At a high level, Oracle Subledger Accounting processes transactions using several interconnected components:

  1. Mapping Sets
  2. User-Defined Rules
  3. Account Rules
  4. Journal Line Rules
  5. Supporting References
  6. Description Rules
  7. Subledger Journal Entry Rule Sets
  8. Accounting Methods

These components work together to create the final accounting entries that ultimately feed the General Ledger.

 

Mapping Sets

Whenever I am designing an Accounting Hub solution, Mapping Sets are usually one of the first places I look. A Mapping Set allows Oracle to translate an input value into an accounting result without requiring custom code.

Eg:

 

Item

Natural Account

IT Services

600010

Advertising

600020

Materials

600030

Contractor Fees

600040

 

In the transformation rules of accounting hub- we can say if Item IT Services is encountered by FAH/Accounting Hub- it will automatically derives value 600020

The beauty of Mapping Sets is that finance teams can maintain accounting logic without involving developers.

Navigation: Setup and Maintenanceà Fusion Accounting HubàAccounting TransformationàManage Mapping Sets

 

User-Defined Formulas

A User-Defined Formula allows you to create custom calculations within Subledger Accounting and use the calculated result during accounting derivation. I often describe User-Defined Formulas as the calculation engine within Accounting Hub.

User-Defined Formulas perform the calculations that drive those accounting decisions.

Eg: Revenue Allocation

Consider a software organization selling a bundled contract.

Compent

Allocation

Software Licenses

70%

Services

20%

Traing

10%

 

For a $100,000 transaction:

Component

Allocation

Licenses Revenue

70000

Services Revenue

20000

Training Revenue

10000

A User-Defined Formula can calculate the allocated amounts which are then used by Journal Line Rules and Account Rules to create separate accounting entries.

 

Supporting References

Supporting References are one of the most underrated features within Accounting Hub.

They allow you to track additional attributes alongside accounting entries without increasing your chart of accounts complexity.

Examples include:

  • Customer
  • Supplier
  • Product
  • Contract Number
  • Employee ID
  • Project Number

Instead of adding a segment to the COA, you can capture these values as Supporting References and report on them later.

Description Rules

Description Rules allow Accounting Hub to build meaningful journal descriptions dynamically. You can strategically select what values needs to picked up for displaying the description of each journal line.

 

Account Rules

If Mapping Sets are the lookup engine, Account Rules are the actual decision makers.An Account Rule determines how Oracle derives a specific account segment or an entire account combination.

Account Rules can derive values from Source Attributes, Mapping Sets, Constants, Other Account Rues, SQL Based Custom Sources as well as User Defined Formulas. You attach these account rules to Subledger Journal Entry Rules at the Journal Line Level.

From an implementation perspective, I typically design segment rules first and then evaluate whether complete account combination rules can reduce maintenance effort.

Journal Line Rules

Journal Line Rules determine what accounting lines are generated. It helps Oracle FAH decide whether the line entry is a debit or a credit, which accounting class it belongs too, account rule assignment as well as description rules

 

Receivable 1000 Dr.

Revenue 1000 Cr.

The Journal Line Rule defines these lines.

A common mistake during design workshops is focusing solely on account derivation while ignoring Journal Line Rule design. In reality, Journal Line Rules drive the entire journal entry structure.

 

Subledger Journal Entry Rule Sets

The Subledger Journal Entry Rule Set (JERS) brings everything together. This object determines what journal lines are to be used and executed, sequencing of the accounting logic, event class of the accounting behavior.

While individual Account Rules define where to post, the Journal Entry Rule Set controls how all accounting pieces work together for a specific event.

Accounting Method

At the highest level sits the Accounting Method. An Accounting Method determines which accounting rules Oracle should apply for a ledger.You assign your subledger journal entry rule sets to your accounting method.

When clients ask me what differentiates a successful Accounting Hub implementation from a difficult one, my answer is almost always the same: the quality of the transformation rule design. The source transaction interface is important. Data quality matters. Reconciliation controls are critical.

 

In Part 4 of this Accounting Hub series, we'll move from configuration to execution and explore how source transactions are uploaded into Oracle Fusion Accounting Hub, including source system integration considerations, transaction import processes, data validation, error handling, and best practices for building scalable and supportable accounting interfaces.

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

 

Thursday, October 8, 2026

Revisiting Oracle Fusion Accounting Hub – A New Learning Journey Begins

 

A few years ago, I had the opportunity to implement Oracle Fusion Accounting Hub (FAH) for a client. At the time, it was one of the most exciting Oracle Cloud Finance implementations because it allowed organizations to centralize accounting while keeping operational transactions in their source systems.

Fast forward to today, and I find myself working with another client that is embarking on a similar Accounting Hub journey. While many core concepts remain unchanged, Oracle has continued to enhance the platform, making this the perfect opportunity for me to revisit, refresh, and deepen my FAH knowledge.

This blog marks the beginning of a new series where I'll document my learnings, implementation experiences, best practices, and practical insights into Oracle Fusion Accounting Hub.

Whether you are an Oracle consultant, solution architect, finance transformation lead, or a customer evaluating Accounting Hub, I hope this series helps you understand the true value of the product and how to successfully implement it.

Oracle Fusion Accounting Hub is a centralized accounting platform that enables organizations to create, transform, standardize, and manage accounting from multiple source systems before posting to Oracle General Ledger.

Many organizations have transactions originating from legacy ERP, Billing System, Banking Platform ,etc. instead of maintaining accounting logic in every application, organizations can send transactions to Accounting Hub where accounting rules are centrally managed.

Accounting Hub then generates accounting entries and posts them into Oracle General Ledger.


Oracle Fusion Accounting Hub Architecture

At a high level, FAH sits between your operational systems and Oracle General Ledger.

 

Business transactions remain in source systems, while accounting is centralized and controlled within Accounting Hub.

 

 

Components of Oracle Fusion Accounting Hub

When I think about Accounting Hub, I generally categorize its value proposition into three major areas.

1.)    Accounting Integration Platform

This is the feature most consultants immediately think of when discussing Accounting Hub.

Accounting Hub acts as an accounting integration platform that:

-          Receives transactions from multiple source systems

-          It standardizes incoming data and transforms this data into accounting events/journal entries

Consider a telecom company who has multiple systems such as revenue system, subscription system, etc- each having its own transactional data -here, rather than maintaining separate accounting logic in all these systems, the transactions can be loaded into FAH, where a single accounting engine determines the final accounting treatment.

2.)   Reporting and Financial Visibility

Accounting Hub is not just an integration platform-it also improves reporting capabilities by creating a centralized accounting repository. FAH provides multiple accounting tools such as Financial Reporting Studio, Account Groups/Inspector, Smartview Reports, OTBI and BIP Reports for accessing reports.

As I begin revisiting FAH, I plan to spend time exploring the following components in detail throughout this series:

Source Systems

External applications sending transactions to FAH.

Transaction Object Objects

Transaction Types such as invoices, claims, other accounting events

Attributes

Transaction attributes used for accounting derivations eg: Customers, region, cost center, line of business,etc.

Mapping Sets

Used to derive accounting values without extensive rule maintenance.

Journal Line Rules

Control account derivation and journal creation.

Supporting References

Provide reporting dimensions and additional transaction tracking.

 

Getting Started – Security Access Required

The very first step before configuring Accounting Hub is obtaining the appropriate security access.

For implementation and setup activities, users typically require the:

Accounting Hub Integration Duty

This duty provides access to Accounting Hub integration-related setup areas and allows administrators and implementers to define source systems, source objects, sources, and transaction integrations.

Security Setup

NavigatoràSecurity ConsoleàRoles

 

Copy General Accounting Manager Role à Top Role Only

 

Add Accounting Hub Administration Duty Role in Role Hierarchies

 

 

Submit Role-

 

Assign this job role to your user and ensure you give relevant Data Access Set access to this role.

 

Up Next?

Now that the foundation is in place, the next step is understanding how Accounting Hub Source System Setup.

Having implemented FAH in the past and now revisiting it for a new client, I'm looking forward to sharing both the fundamentals and the practical lessons that only come from real implementations.

Stay tuned as we continue the journey into Oracle Fusion Accounting Hub.

Friday, October 2, 2026

Easy way to default Disbursement Bank Account on Payments

Sometimes the most useful Oracle Fusion functionality is the one that's been sitting quietly in the application for years, waiting for the right business requirement.Recently, while working with a client, we encountered a requirement to automatically default the disbursement bank account during the payment process based on the Business Unit and, in some cases, the Balancing Segment Value (BSV) associated with the transaction. Instead of building a custom solution, we explored Oracle Payments and rediscovered the ORA_IBY_DEFAULT_BANK_ACCOUNT lookup.

Interestingly, this functionality has existed in Oracle Fusion for quite some time, but many implementations never leverage it because a single legal entity often operates with one primary payment bank account. As organizations grow and introduce multiple legal entities, business units, and cash management strategies, the need for intelligent bank account selection becomes much more relevant.

Consider the following scenario- not exact but similar :)

Business Unit

BSV

Bank Name

US Operation

100

BoA

Canada Operation

200

RBC

UK Operation

300

HSBC

The client wanted Oracle Fusion Payments to automatically select the correct disbursement bank account during payment processing based on the originating Business Unit or Balancing Segment.

Without automatic defaulting, payment administrators would have to manually choose the correct bank account during each payment run, increasing both effort and risk of error.

Though challenging, I did extensive research just to find one hidden functionality of Oracle Fusion ORA_IBY_DEFAULT_BANK_ACCOUNT is a lookup used within Oracle Payments to determine the default disbursement bank account for supplier payments. It allows Oracle Payments to evaluate transaction attributes and derive an appropriate internal bank account during payment processing.Common selection criteria may include Business Unit, Legal Entity,  Payment Method, Process Profile, BSVThe result is a more automated and controlled payment process. Payment i.e. ORA_IBY_DEFAULT_BANK_ACCOUNTAssume that the client has a specific requirement i.e. Invocies from Business Unit A needs to be paid from Bank Account A, Business Unit B needs to be paid from Bank Account B and so on.During Payment Process when Payment process is created – Oracle evaluates the lookup rules and identifies the Business Unit and Defaults the Bank Account associated with it from the lookup. Sounds Fun Right!! Similarly, when client wants to drive bank account selection based on BSV Oracle Payments can be configured to derive a value representing the balancing segment and use that value during bank account determination.

However as easy this functionality sounds- there are some challenges i.e. what happens if my Invoice has multiple Balancing segments (Intercompany Invoice,etc.) Oracle Payments ultimately selects a single disbursement bank account for a payment.

Because of this, organizations should establish a business rule such as:

-          1.) Use the primary BSV 2.) Use the highest dollar amount BSV 3.) Restrict Invoices to Single BSV 4.) Default based on BU rather than BSV. This decision should be made during solution design to avoid ambiguity during payment processing.

Benefits of this solution include Improved Automation, Better Controls, Simplified Payment Processing and Scalabiltiy.

 Lets look at the configurations for the same:

 Navigation:

 Setup and MaintenanceàFinancialsàPayments->Manage Disbursement Lookups

Search for the lookup ORA_IBY_DEFAULT_BANK_ACCOUNT and populate the values

Lookup Code and Meaning—Balancing Segment Value

Description: Bank Account

 

Create your payment process Template

Ensure Disbursement Account is blank

 

This requirement was a great reminder that Oracle Fusion often provides the framework needed to solve a business problem without resorting to extensive customizations.

In our client's case, the ability to default disbursement bank accounts based on Business Unit and Balancing Segment was already available through Oracle Payments. The functionality had technically existed all along, but because previous implementations relied on a single operating bank account, it was never utilized.

As organizations expand and banking structures become more sophisticated, revisiting features like ORA_IBY_DEFAULT_BANK_ACCOUNT can unlock automation, strengthen controls, and significantly improve the payment process with minimal configuration effort.

 

You can find more information on this functionality using Oracle Notes:

https://docs.oracle.com/en/cloud/saas/financials/26c/fappp/automatic-population-of-bank-accounts-by-company-codes.html#Multiple-Ledgers-Use-Different-Company-Codes

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...