Explain Fusion ERP: Subledger Accounting and Ledgers in Oracle Applications

26 / 60

Fusionintermediate

Fusion ERP: Subledger Accounting and Ledgers

Explain how Fusion ERP's ledger and subledger accounting architecture evolved from EBS while retaining core concepts

The GL fundamentals carry over from EBS unchanged. This is the most comforting area for a consultant moving across.

Fusion's multi-ledger SLA architecture is like a single news event being reported simultaneously in multiple languages and styles for different audiences (local paper, international wire, and a regulatory filing) — the underlying facts (the transaction) don't change, but each output (ledger) presents it according to its own required format and rules.

Key Concepts

The three Cs still define a ledger.

    Chart of Accounts
    Calendar
    Currency

Change any one and it is a different ledger. Exactly as in EBS.

Ledger sets group ledgers for processing. Run a report, open a period or post across several ledgers as one operation, provided they share a chart of accounts and calendar.

Subledger Accounting does the same job and is configurable further. A subledger transaction is translated into journal entries by rules rather than by hard-coded logic:

    supplier invoice for 10,000 with tax
        |  SLA rules decide the accounts
        v
    debit  expense       10,000
    debit  tax recoverable 1,800
    credit liability      11,800

The change is who configures it. In EBS, non-standard accounting frequently meant custom code. In Fusion the Accounting Rules interface handles conditional logic declaratively — different accounts by supplier type, by business unit, by transaction attribute — without a developer.

The Accounting Hub extends the same engine to transactions from outside Oracle: feed a source system's events in, and SLA generates the accounting under your rules.

Multi-GAAP is handled with secondary ledgers. One set of transactions, valued twice:

    primary ledger    IFRS
    secondary ledger  local GAAP, with its own rules

Both are produced from the same subledger transactions rather than by a reconciliation exercise afterwards. Reporting currencies work the same way for currency rather than standard.

The question interviewers ask is how an invoice becomes journal entries. The answer is the chain: created in the subledger, accounted by SLA against its rules, transferred to GL as entries.

That chain is identical to R12's. Saying so — that this is evolutionary rather than a redesign — is the answer they are listening for, because it is true and because it tells them your EBS financials knowledge transfers.

What the interviewer is probing.1. "What does subledger accounting do?" Probing: the central concept. Stalls: "Posts entries." Moves up: turns subledger transactions into journal entries through configurable rules, so accounting policy is configuration rather than code.

2. "What is the four Cs of a ledger?" Probing: the fundamentals. Stalls: "Nothing." *Moves up:* chart of accounts, calendar, currency and accounting convention — a ledger is defined by those four.

3. "Why would you have a secondary ledger?" Probing: the use case. Stalls: "Backup." *Moves up:* different accounting representation for statutory or tax reporting from the same transactions.

4. "Where do you look when an entry posted to the wrong account?" Probing: troubleshooting. Stalls: "The transaction." Moves up: the SLA account derivation rules and the mapping sets, since the account is derived rather than entered.