Ledger Mapping in Oracle Fusion Financials plays a crucial role in managing financial data across multiple reporting requirements. This article explores Primary and Secondary Ledger Mapping in Oracle Fusion Financials and its role within Fusion Accounting Hub, and the different types of ledgers available in Oracle Fusion Applications.

Primary Ledger

The Primary Ledger is the main record-keeping ledger and a mandatory component of any accounting setup. Each accounting configuration is uniquely defined by its primary ledger. It is directly linked to subledger transactions and provides the necessary accounting context for them. The Primary Ledger:

• Maintains transactional balances using the defined chart of accounts, accounting calendar, currency, and accounting rules set through the accounting method.  
• Is used to post journals that capture the financial impact of subledger transactions. 

Secondary Ledger

A Secondary Ledger is an optional ledger that is associated with a primary ledger. It is used to maintain an alternative accounting representation or to track the same financial data using different accounting requirements. 

A Secondary Ledger can differ from the Primary Ledger in one or more of the following aspects: 

• Chart of accounts  
• Accounting calendar or period type  
• Currency  
• Subledger accounting method  
• Ledger processing options 

A Secondary Ledger is always linked to a Primary Ledger, and an organisation can have multiple secondary ledgers associated with a single primary ledger. In scenarios where a company operates across multiple countries, separate primary ledgers are typically created to meet local legal and reporting requirements—each configured with the appropriate currency, chart of accounts, calendar, and accounting method. 

To support both local and corporate reporting needs, organisations can use secondary ledgers to maintain alternative accounting representations, such as a different accounting method or, in some cases, a different chart of accounts. 

Take your expertise to the next level with our
Oracle Fusion Subledger Accounting Training

Reporting Currency

A Reporting Currency is an optional, additional currency representation of a primary or secondary ledger. It allows organisations to maintain financial data in another currency for reporting purposes. While it differs from the source ledger in terms of currency and certain processing options, it shares the same chart of accounts, accounting calendar, and accounting method as the associated ledger. 

Why Do We Need Ledger Mapping in Oracle Fusion Financials

When the primary and secondary ledgers are configured with different charts of accounts, a mapping is required to define how journal entries are transferred from the source chart of accounts to the target chart of accounts. 

When primary and secondary ledgers use different accounting calendars, the accounting date is used to identify the corresponding non-adjusting period in the secondary ledger. A date mapping setup defines the relationship between dates and non-adjusting periods across the respective accounting calendars. 

The Chart of Accounts mapping option is used to align the source chart of accounts with the target chart of accounts for journal creation. Additionally, account rules can be configured within the mapping to support the transformation of complete account combinations between different charts of accounts. When the primary and secondary ledgers operate in different currencies, currency conversion rules must be defined to guide how transactions, journal entries, and balances are converted from the source ledger to the secondary ledger. 

Types of secondary ledgers 

1. Balance Level Secondary Ledger

In this approach, balances from the primary ledger are transferred to the secondary ledger using General Ledger (GL) consolidation. This type of secondary ledger maintains account balances from the primary ledger in an alternate accounting representation. 

It is typically used when no additional adjustments are required in the primary ledger, and only summarised balance-level data needs to be maintained in the secondary ledger. 

This type of secondary ledger does not support drill-down to journal entries or subledger transactions, limiting visibility into the underlying details. Additionally, balances are maintained only at reporting period levels, meaning the ledger is not updated in real time but only when balances are transferred through GL consolidation. Since it stores summarised data, it generates a relatively low volume of information and is generally considered a cost-effective solution for organisations. 

2. Journal Level Secondary Ledger

This type of secondary ledger is maintained through the General Ledger posting process. When a journal is posted in the primary ledger, it can be automatically replicated in the secondary ledger based on the defined journal conversion rules. 

A journal level secondary ledger stores both journal entries and balances, providing an additional accounting representation. Replication can be configured for specific journal sources and categories as required. Unlike balance-level secondary ledgers, this type supports adjustments. It can also reflect adjustments made in the primary ledger, even when applying a different accounting basis, offering a certain level of drill-down and visibility into transactions. 

Journal level secondary ledgers are particularly useful when an alternative accounting basis is required along with access to journal-level details. However, since they capture detailed data, they generate higher data volumes and may require additional system resources. 

3. Subledger Level Secondary Ledger

This type of secondary ledger is maintained using both Subledger Accounting (SLA) and the General Ledger posting process. It provides the most detailed and complete accounting representation among all secondary ledger types. 

Subledger Accounting generates journal entries from subledger transactions, while the General Ledger posting process handles entries for transactions that are not integrated with subledger accounting, such as manual journals. Together, they ensure that journals are created in both the primary and secondary ledgers. 

A subledger level secondary ledger combines the capabilities of balance-level and journal-level ledgers, while also capturing subledger transaction details. This enables full drill-down visibility and allows organisations to maintain parallel accounting representations based on different accounting requirements. Due to the detailed level of data captured, this approach generates a high volume of journal and balance data and may require additional system resources and performance considerations. 

4. Adjustments Only Secondary Ledger

This type of secondary ledger is used exclusively to record adjustments, which can be entered manually or generated through Subledger Accounting (SLA). Unlike other secondary ledger types, it does not provide a complete accounting representation, as it captures only adjustment entries rather than full transactional data. 

It must share the same chart of accounts, accounting calendar (or period type), and currency as the associated primary ledger. To generate a complete accounting view that includes both original transactions and adjustments, organisations can use ledger sets to combine the primary ledger with the adjustments-only secondary ledger for reporting purposes. 

This approach is particularly useful for managing audit and period-end adjustments, as it allows adjustments to be tracked separately, improving transparency and control. It can also support approval workflows, where entries are reviewed and validated before being considered in consolidated reporting. Since it stores only adjustment data, it generates the least volume of data among all secondary ledger types and is generally the most cost-effective option. 

Conclusion 

Evolving financial reporting requirements have significantly influenced how organizations manage accounting transactions and balances, making Ledger Mapping in Oracle Fusion Financials essential for addressing diverse reporting needs while reducing reliance on manual processes such as spreadsheets.

When organisations operate with a unified chart of accounts, a common accounting calendar, and a single Fusion instance, they can establish a centralised and reliable source of financial data. This enables greater visibility across transactions—from the primary ledger to associated secondary ledgers—with drill-down capabilities extending to subledger details. As a result, organisations benefit from consistent reporting across business units, along with reduced effort in management reporting, maintenance, and reconciliation.