Subledger Accounting Rules

The engine behind every journal Oracle Fusion generates. Master Oracle Fusion Subledger Accounting — journal line rules, account derivation, supporting references and how to build accounting rules that handle real-world complexity. 12 hrs · 4 sessions. Overview Most Fusion Finance consultants know how to post an invoice or create a payment. Fewer understand what drives the accounting entries that result from those transactions — the subledger accounting engine that sits underneath every AP, AR, fixed assets, and projects transaction and determines which accounts get debited and credited, what supporting reference data is captured, and how the journal is described in the general ledger. Subledger Accounting (SLA) is one of the most powerful and least understood components of Oracle Fusion Finance. When it is configured correctly, accounting entries are generated automatically, consistently, and in compliance with both IFRS and local statutory requirements. When it is misconfigured — or when the default rules are accepted without examination — accounting entries are wrong, reconciliations fail, and finance teams spend months in manual journal entry correction. This course teaches SLA from first principles: what journal line rules are, how account derivation works, what conditions and priorities do, and how to design an SLA framework that handles the complexity of a real multi-entity organisation. We cover the full SLA component hierarchy — subledger accounting methods, journal entry rule sets, journal line rules, account rules, and mapping sets — and how they interact. Every session uses real implementation examples, including the SLA configurations used in African organisations with OHADA, IFRS, and local GAAP requirements. Learning outcomes • Understand the full Oracle Fusion SLA component hierarchy and explain how each component contributes to accounting entry generation • Design journal line rules with conditions and priorities that correctly handle complex transaction classification requirements • Build account rules using all four derivation types, including mapping sets for multi-entity organisations • Configure supporting references to enable drill-down reconciliation beyond the standard account combination • Design multi-GAAP SLA frameworks that produce compliant entries in both primary and secondary ledgers from the same transaction • Diagnose and correct incorrect SLA configurations on live systems without requiring a full reconfiguration Modules 1. SLA architecture — the component hierarchy from top to bottom (3 hours) We begin with the full SLA architecture and how its components relate to each other. Starting from the subledger accounting method — the top-level container that determines which rules apply to which transactions in which ledger — we work down through journal entry rule sets, journal line rules, account rules, and mapping sets. We cover the difference between standard SLA methods (the defaults Oracle ships with Fusion) and custom methods, and when you need to create your own. We establish the vocabulary that the rest of the course uses and work through a complete example — an AP invoice — tracing every accounting entry back to the SLA rules that generated it. Topics: SLA component hierarchy; Subledger accounting methods; Journal entry rule sets; Standard vs custom SLA; Tracing an entry to its rule 2. Journal line rules — conditions, priorities, and account derivation (3 hours) Journal line rules are the heart of SLA. Each rule determines: which transactions it applies to (via conditions), what the accounting line type is (debit or credit), and how the account is derived (via account rules). This session covers journal line rule design in depth — how to write conditions that correctly identify the transactions you want to treat differently, how priorities determine which rule fires when multiple rules match, and how to test your rules without deploying them to a live system. We cover the most common journal line rule patterns: cost centre derivation from a purchase order line, natural account override for specific supplier types, and intercompany account selection based on the counterpart legal entity. Topics: Journal line rule conditions; Priority and rule evaluation; Account rule types; Common rule patterns; Testing without live data 3. Account rules, mapping sets, and supporting references (3 hours) Account rules define how Oracle Fusion derives the account for an accounting line — either from a constant value, from a source (a field on the transaction), from a mapping set (a lookup table), or from a complex derivation using multiple conditions. This session covers all four derivation types with worked examples for each. We spend significant time on mapping sets — the most powerful and most misunderstood account rule type — and cover how to design them for multi-entity organisations where the same transaction type maps to different accounts in different legal entities. We then cover supporting references: the custom dimensions that SLA can capture on every accounting entry, enabling drill-down and reconciliation beyond the standard account segments. Topics: Account rule derivation types; Mapping sets in depth; Multi-entity mapping; Supporting references design; Drill-down and reconciliation 4. Multi-GAAP SLA, troubleshooting, and live case studies (3 hours) The final session covers two advanced topics. First, multi-GAAP SLA: how to configure subledger accounting methods that produce different accounting entries for different ledgers — IFRS in the primary ledger and local GAAP in a secondary ledger — from the same underlying transaction. This is the core requirement for African organisations that report under IFRS to a parent while filing statutory accounts locally. Second, SLA troubleshooting: how to diagnose incorrect accounting entries, identify which rule is firing, understand why a condition is or is not being evaluated, and correct the configuration. We end with two case studies where participants debug SLA configurations with deliberate errors. Topics: Multi-GAAP SLA design; Secondary ledger SLA methods; OHADA vs IFRS example; Troubleshooting methodology; Debugging case studies Important Why SLA problems are hard to find and expensive to fix SLA errors rarely produce visible error messages. Instead, they produce plausible-looking accounting entries that are quietly wrong. A misconfigured account rule posts to the wrong natural account; an incorrect condition sends transactions to the wrong legal entity; a missing supporting reference makes it impossible to drill from the GL to the subledger transaction. These problems are often only discovered at audit — by which time hundreds of incorrect entries have accumulated. Delivery This is the most technically demanding course in Track 02. Groups of 3–6 consultants work best — the troubleshooting case studies in session 4 benefit from collaborative problem-solving. Pre-reading: ensure all participants are comfortable with the Fusion AP and AR transaction lifecycle before the first session. Certification Certificate of completion Price USD 1200 · per participant per person · indicative · group pricing available HRDC eligibility Up to 75% refundable Mauritius-registered employers may claim this training cost via the HRDC levy. We provide full documentation to support your claim. Languages English Provider reference SIMPLIT-084-SUBLEDGER_ACCOUNTING_RULES

• Fusion Finance consultants who configure AP, AR, Fixed Assets, or Projects and need to understand what drives the accounting • Finance architects who have accepted SLA defaults and now need to customise them for a client's requirements • Consultants troubleshooting incorrect accounting entries on a live system • Senior consultants who want to formally understand something they have been doing by trial and error • Anyone involved in a multi-GAAP or multi-entity Fusion implementation where SLA customisation is required • Finance managers who review Fusion accounting output and need to understand where the numbers come from