Oracle Fusion Cloud Subledger Accounting (SLA) is not controlled by one standalone “account rule.” It is a connected framework that takes transaction events and sources, applies conditions, derives accounts and journal lines, adds descriptions and supporting references, and assigns the resulting treatment to a ledger through an accounting method.
The practical flow is:
Transaction sources → conditions → account and journal line rules → journal entry rule set → accounting method → ledger → Create Accounting → General Ledger
As an Amazon Associate I earn from qualifying purchases.
This guide explains how those components fit together, what must be defined before configuration, how to activate and test changes, and how to troubleshoot the most common failures. Oracle updates Fusion Cloud quarterly, so the concepts are durable but task names and page layouts may differ. Depending on the product area and release, you may see Configure Accounting Rules, Define Subledger Accounting Rules, or separate tasks such as Manage Account Rules and Manage Subledger Journal Entry Rule Sets.
What SLA controls
SLA converts subledger transactions into detailed accounting entries before those entries are transferred or summarized into General Ledger. It controls:
#1 Best Overall
- FAST SPEEDS - Scans color and black and white documents a blazing speed up to 16ppm (1). Color scanning won’t slow you down as the color scan speed is the same as the black and white scan speed.
- ULTRA COMPACT – At less than 1 foot in length and only about 1. 5lbs in weight you can fit this device virtually anywhere (a bag, a purse, even a pocket).
- READY WHENEVER YOU ARE – The DS-640 mobile scanner is powered via an included micro USB 3. 0 cable allowing you to use it even where there is no outlet available. Plug it into you PC or laptop and you are ready to scan.
- WORKS YOUR WAY – Use the Brother free iPrint&Scan desktop app for scanning to multiple “Scan-to” destinations like PC, Network, cloud services, Email and OCR. (2) Supports Windows, Mac and Linux and TWAIN/WIA for PC/ICA for Mac/SANE drivers. (3)
- OPTIMIZE IMAGES AND TEXT – Automatic color detection/adjustment, image rotation (PC only), bleed through prevention/background removal, text enhancement, color drop to enhance scans. Software suite includes document management and OCR software. (4)
- Which account or account segments are used.
- Whether a journal line is a debit or credit.
- Which accounting class is assigned.
- Which amount, currency, and accounting attributes are used.
- Which transactions qualify for a rule.
- What appears in journal headers and line descriptions.
- Which additional transaction information is retained for reconciliation and reporting.
Oracle describes the broad processing sequence as capturing accounting events, identifying eligible events, applying transaction data and rule definitions, creating subledger journal entries, and transferring entries to General Ledger. See Oracle’s current implementation overview and Accounting Hub processing documentation.
The SLA object model
Understanding the dependency chain is more important than memorizing individual setup pages.
| Component | Purpose |
|---|---|
| Sources | Transaction attributes made available to accounting rules, such as supplier, customer, transaction type, or project. |
| Source values | The actual values supplied by a transaction when accounting is created. |
| Accounting attributes | Values used by accounting processing, such as accounting date, entered amount, and entered currency. |
| Conditions | Boolean logic that determines when a rule or rule detail applies. |
| Mapping sets | Lookup tables that convert one or more source values into an account, segment, or value-set value. |
| Account rules | Derive the account used by a journal line. |
| Journal line rules | Define the line’s debit or credit behavior, accounting class, amount behavior, and generation conditions. |
| Description rules | Build readable journal header or line descriptions from text and sources. |
| Supporting references | Store structured transaction information for reconciliation and reporting. |
| Journal entry rule sets | Assemble the header and line rules into a complete accounting treatment for an event class or event type. |
| Accounting methods | Group rule-set assignments and provide a reporting-basis framework for ledgers. |
Who should configure SLA?
SLA configuration usually requires both functional and data security. The accounting policy owner defines the desired treatment; a Fusion Financials consultant translates that policy into rules; an administrator provides setup access and data access; and a technical or integration specialist may be needed for Accounting Hub or custom-source work.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Oracle identifies the Subledger Accounting Administration Duty within the Financial Application Administrator security hierarchy. The exact role and data-access design depend on the implementation. Access to Payables, Receivables, or another transaction screen does not automatically grant access to SLA setup.
Separate these responsibilities:
- Setup access: create and maintain SLA definitions.
- Transaction access: create, review, or correct source transactions.
- Ledger and data access: work with the relevant ledgers, business units, and legal entities.
- Control access: approve accounting policy, testing, migration, and production changes.
Refer to Oracle’s security and SLA implementation guidance when designing responsibilities.
Prerequisites: define the accounting event before the rule
Before creating an account rule, document the accounting requirement outside the application. A useful policy statement might be:
For Payables invoices, derive the liability account from the supplier site and the expense account from the invoice distribution. Use a separate liability account for intercompany suppliers, and include supplier name and invoice number in the line description.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Then identify:
- The subledger application, such as Payables, Receivables, Assets, Cost Management, Projects, or Expenses.
- The accounting event class, such as invoices, payments, receipts, depreciation, or cost accounting events.
- The specific accounting event type.
- The ledger, chart of accounts, and accounting basis.
- The accounting classes required for the entry.
- The sources and accounting attributes available to the event class.
- Differences between statutory, tax, management, and other reporting requirements.
- The effective date and migration approach.
Sources, source values, and accounting attributes
A source is a usable transaction attribute in the accounting framework. A source value is the actual value supplied by a transaction object. An accounting attribute is a value used by the Create Accounting process, such as an accounting date or entered amount.
Sources must be available to the relevant accounting event class before they can be selected in rules. A label shown on a transaction page is not necessarily an SLA source. If the required attribute is absent, you may need to use another available source, revise the requirement, enable a supported source, or involve an Accounting Hub or integration specialist. Do not invent a source name in the setup screen.
Oracle’s Accounting Hub documentation identifies minimum accounting attributes such as:
Rank #2
- PORTABLE SCANNER FOR USE ON-THE-GO — The fastest and lightest mobile single-sheet-fed compact document scanner in its class¹
- QUICK DOCUMENT SCANNING ― This Epson ultra-fast scanner scans a single page as quickly as 5.5 seconds²; Windows and Mac compatible
- VERSATILE PAPER HANDLING ― Portable scanner scans documents up to 8.5 x 72 in; Also easily digitizes receipts and ID cards to make accounting, bookkeeping, and organizing simpler
- INTUITIVE, HIGH-SPEED SOFTWARE — Epson ScanSmart Software³ is a smart tool allowing you to easily scan, review, and save; Stay organized easily with the help of this Epson scanner
- EASY SETUP — USB-powered connect to your computer for quick and simple scanning; No batteries or external power supply required to operate portable document scanner; Standard Connectivity: USB 2.0
- Accounting Date
- Distribution Type
- Entered Amount
- Entered Currency Code
- First Distribution Identifier
These documented minimums should be treated as applicable to the relevant Accounting Hub or SLA context and verified for the target subledger and quarterly release—not copied as a universal checklist for every Fusion implementation.
Configure mapping sets for lookup-driven logic
A mapping set is preferable when the accounting relationship is essentially a lookup. For example, a source such as business unit, supplier type, product, project type, or transaction category can map to an expense account, liability segment, revenue segment, inventory account, or complete account combination.
Use a mapping set when:
- The relationship is maintained as a table of input values and outputs.
- Business users are likely to update the values regularly.
- The same lookup should be reused by multiple account rules.
Use conditional account-rule details instead when the result depends on several business conditions, prioritized exceptions, or rule components.
Mapping-set procedure
- Identify the source or sources that provide the mapping input.
- Define the output as a complete account, segment, or value-set value, according to the options available in your release.
- Enter the valid input and output combinations.
- Add a deliberate default where the accounting policy permits one.
- Test unmapped, null, blank, and newly introduced values.
- Confirm every output is valid for the applicable chart of accounts and value set.
Oracle documents mapping sets in its Subledger Accounting implementation guide. Oracle University also describes creating mapping definitions and using the SLA mapping import template where appropriate at this mapping-set resource.
An unmapped input can produce an invalid account or accounting error. It should not be assumed that Fusion will silently select the intended fallback.
Build account rules
Account rules determine the account used on a subledger journal line. Oracle documents three principal approaches.
Complete account combination
Derive the entire code combination directly. This is explicit and easy to audit when a stable business classification determines every segment. It becomes harder to maintain when several segments vary independently and is more sensitive to chart-of-accounts changes.
Segment-based derivation
Derive only the segment or segments that vary while the remaining segments come from the transaction or ledger context. This reduces duplication and can make rules more reusable, but it requires careful testing of how the other segments are supplied and whether the resulting combinations pass validation.
Value-set-based derivation
Derive a value from a value set. Oracle documents this approach as useful for sharing account rules across charts of accounts when the relevant segments use compatible value sets.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Account rules can contain conditions and priorities. Oracle documents that rule details are evaluated by priority and the first applicable detail is used. Put specific exceptions before general conditions, add an explicit default after the exceptions, and document which detail wins if more than one condition could be true.
Rank #3
- OUR MOST ADVANCED SCANSNAP. Large touchscreen, fast 45ppm double-sided scanning, 100-sheet document feeder, Wi-Fi and USB connectivity, automatic optimizations, and support for cloud services. Upgraded replacement for the discontinued iX1600
- CUSTOMIZABLE. SHARABLE. Select personalized profiles from the touchscreen. Send to PC, Mac, mobile devices, and clouds. QUICK MENU lets you quickly scan-drag-drop to your favorite computer apps
- STABLE WIRELESS OR USB CONNECTION. Built-in Wi-Fi 6 for the fastest and most secure scanning. Connect to smart devices or cloud services without a computer. USB-C connection also available
- PHOTO AND DOCUMENT ORGANIZATION MADE EFFORTLESS. Easily manage, edit, and use scanned data from documents, receipts, photos, and business cards. Automatically optimize, name, and sort files
- AVOIDS PAPER JAMS AND DAMAGE. Features a brake roller system to feed paper smoothly, a multi-feed sensor that detects pages stuck together, and skew detection to prevent paper damage and data loss
Build journal line rules
An account rule does not create a journal line by itself. It must be attached to a journal line rule within a journal entry rule set.
For each expected line, define:
- Debit or credit behavior.
- Accounting class.
- Amount source or accounting attribute.
- Currency-related behavior available for the event.
- Conditions under which the line is generated.
- The related account rule.
- An optional description rule.
- Optional supporting references.
Oracle describes line types such as Credit, Debit, Gain, Loss, and Gain or Loss in the rule-assignment context. The exact choices and behavior should be confirmed for the target subledger and release. Test that all generated lines balance and that their accounting classes reflect the approved accounting policy.
Add descriptions and supporting references
Description rules can apply at header level, line level, or both. They can combine literal text, transaction sources, conditions, and ordered description elements.
Useful patterns include:
- Supplier name plus invoice number.
- Customer name plus receipt number.
- Project number plus expenditure item.
- Asset number plus depreciation period.
- Transaction type plus accounting date.
Sources used by a description rule must be assigned to the relevant accounting event class, and the source must contain a value on the transaction. Keep descriptions concise and searchable. Excessive volatile detail creates inconsistent journal text and does not replace structured reconciliation data.
Use supporting references when the information needs to remain structured for reconciliation, drilldown, regulatory analysis, or management reporting. A description is human-readable text; a supporting reference is structured accounting information attached for downstream use. Oracle describes supporting references as optional components of journal entry rule sets. See the Accounting Hub implementation guide.
Assemble the journal entry rule set
A subledger journal entry rule set defines the complete accounting treatment for an accounting event. It brings together header-level and line-level assignments.
Header assignments can include:
- Accounting date.
- Optional accrual-reversal accounting date.
- Header description.
- Header supporting references.
Line assignments can include:
- Journal line description rule.
- Journal line rule.
- Account rule.
- Line supporting references.
At this stage, verify that the rule set belongs to the correct application, event class, and event type. Shared account rules are possible only when the sources used by the rule are available to the relevant event class.
Free tools Windows power users keep installed
One-click scans. No signup required.
When seeded Oracle behavior is close to the requirement, copy the predefined rule set and modify the copy. Use a controlled name that identifies the application, event class, purpose, and version or effective date. Copying is usually faster and preserves established line structure, but inherited logic must be reviewed. Build a new rule set when the accounting policy is materially different, unnecessary seeded lines would create confusion, or separate statutory treatments must be maintained independently.
Assign the rule set to an accounting method and ledger
Accounting methods group journal entry rule-set assignments by accounting event class and event type. An accounting method may represent US GAAP, IFRS, local statutory accounting, or a management accounting representation.
On the accounting method:
- Select the relevant event class and event type.
- Assign the journal entry rule set.
- Confirm that the accounting method’s chart of accounts is compatible with the ledger.
- Review effective dates.
- Assign the accounting method to the intended ledger if it is not already assigned.
If an accounting method has an assigned chart of accounts, Oracle documents that it can be used only with ledgers using that chart of accounts. If it has no assigned chart of accounts, Oracle documentation describes broader assignment possibilities.
Rank #4
- FITS SMALL SPACES AND STAYS OUT OF THE WAY. Innovative space-saving design to free up desk space, even when it's being used
- SCAN DOCUMENTS, PHOTOS, CARDS, AND MORE. Handles most document types, including thick items and plastic cards. Exclusive QUICK MENU lets you quickly scan-drag-drop to your favorite computer apps
- GREAT IMAGES EVERY TIME, NO EXPERIENCE REQUIRED. A single touch starts fast, up to 30ppm duplex scanning with automatic de-skew, color optimization, and blank page removal for outstanding results without driver setup
- SCAN WHERE YOU WANT, WHEN YOU WANT. Connect with USB or Wi-Fi. Send to Mac, PC, mobile devices, and cloud services. Scan to Chromebook using the mobile app. Can be used without a computer
- PHOTO AND DOCUMENT ORGANIZATION MADE EFFORTLESS. ScanSnap Home all-in-one software brings together all your favorite functions. Easily manage, edit, and use scanned data from documents, receipts, business cards, photos, and more
Use one accounting method when the accounting policy is genuinely shared. Use separate methods when reporting bases, legal requirements, or ledgers require different treatments. Multiple methods should not be used merely to hide disorganized rule sets.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Activate and effective-date the configuration
Saving a rule is not the same as making it operational. Changing a component associated with an assigned rule set can place the accounting method into an incomplete state. Validate the definitions, activate the rule-set assignments, and confirm that the accounting method is complete and active before relying on it for Create Accounting.
For a controlled change:
- Validate the modified rule components.
- Review the accounting method and assignment status.
- Confirm the effective start date.
- Activate the assignments.
- Test transactions before, on, and after the change date.
For a change to predefined accounting behavior, Oracle documents end-dating the existing assignment and creating a new assignment with a future effective start date. This is generally safer than rewriting an active definition in a way that changes the treatment of new and historical events indiscriminately.
The correct historical correction depends on whether an entry was transferred, posted, reconciled, or reported. Effective dating does not automatically undo an already-created accounting entry; reversal and re-accounting procedures may be required.
Run an end-to-end test
Use a controlled transaction in a nonproduction environment and test the complete processing chain:
Recommended Free Tools
- Create or identify the test transaction.
- Confirm that it generated the expected accounting event.
- Run Create Accounting in draft mode where that option is available for the subledger.
- Review the subledger journal entry.
- Check the account combination, debit and credit amounts, accounting class, accounting date, currency, descriptions, supporting references, and event status.
- Correct the rule, source, mapping, or assignment.
- Reprocess the transaction.
- Run final accounting.
- Transfer the accounting to General Ledger.
- Review the General Ledger journal and reconcile it back to the source transaction.
Create Accounting, transfer, and posting are not necessarily one operation. Process names, parameters, draft behavior, transfer options, and posting behavior vary by subledger and quarterly release. Confirm the exact process sequence for the application being configured.
Minimum negative-test matrix
- Normal transaction.
- Every conditional branch.
- Default branch.
- Missing mapping.
- Null or blank source.
- Unexpected or newly introduced source value.
- Multiple currencies.
- Credit memo, reversal, or adjustment.
- Period boundary.
- Effective-date boundary.
- Invalid account combination.
- Intercompany or balancing behavior where relevant.
- Multiple ledgers or accounting representations where applicable.
Troubleshooting common SLA failures
“The account rule exists, but no accounting line is generated”
- Confirm the account rule is attached to a journal line rule.
- Check whether the journal line condition evaluates to true.
- Confirm the rule set is assigned to the correct event class and event type.
- Verify that the assignment is active.
- Confirm the transaction generated an accounting event.
- Check the event’s effective date.
- Confirm that the rule belongs to a compatible application and event class.
“The source cannot be selected”
- Check that the source is assigned to the accounting event class.
- Confirm it is supported for the event type.
- Check cross-application sharing requirements.
- Verify that the proposed name is an SLA source, not merely a transaction-screen label.
“Create Accounting fails with an invalid account”
- Validate the mapping-set output.
- Check for missing required segments.
- Test cross-validation rules.
- Add a deliberate default where appropriate.
- Confirm the account belongs to the correct chart of accounts.
- Check for transaction values not covered by conditions.
“The configuration was saved but is not used”
- Activate the rule-set assignment.
- Confirm the accounting method is complete.
- Check the ledger and event type.
- Review the effective start date.
- Check whether a more specific or higher-priority detail is winning.
- Remember that an already-accounted transaction may require reversal or reprocessing.
“Descriptions are blank”
- Confirm the description rule is assigned at the expected header or line level.
- Verify source availability.
- Check whether the transaction source has a value.
- Review conditions that may suppress the description.
- Confirm the rule is attached to the intended journal line.
“The rule works in one ledger but not another”
Compare the charts of accounts, accounting-method assignments, ledger-specific SLA options, effective dates, data access, and the availability of the rule set to the second ledger. Oracle documents that subledger accounting options are configured in the context of primary and secondary ledgers, and some event classes may require an update process. See the Oracle implementation guidance.
“An import overwrote or conflicted with an existing rule”
Use unique names, document object ownership, and compare source and target definitions before importing. Oracle release material describes setup-data export and import and warns that collisions can occur when corresponding objects exist in both environments. See the Financials release material.
Migration and governance
SLA changes affect financial reporting and should be managed as controlled configuration, not as an informal account-code edit.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteQuick Recap
- Maintain an accounting-policy matrix linking each policy requirement to an event, source, line, account rule, and test case.
- Use consistent names for applications, event classes, purposes, and versions.
- Record who approved the accounting treatment and who approved the technical configuration.
- Keep seeded objects intact where possible and document every copied or customized object.
- Use effective dates instead of rewriting historical intent.
- Export and import setup data using supported configuration packages or migration processes.
- Check for collisions between source and target environments.
- Retain test evidence showing source transaction, subledger entry, General Ledger result, and reconciliation.
- Repeat regression tests after quarterly updates and after chart-of-accounts or source changes.
Production-readiness checklist
- ☐ Accounting policy is approved and documented.
- ☐ Application, event class, event type, ledger, and accounting method are confirmed.
- ☐ Every required source is available to the event class.
- ☐ Mapping sets cover expected values and have deliberate default behavior.
- ☐ Account rules use the appropriate complete-account, segment, or value-set design.
- ☐ Journal line rules define debit/credit behavior, accounting class, amount, and conditions.
- ☐ Descriptions are readable and supporting references hold structured reconciliation data.
- ☐ Journal entry rule-set assignments are complete.
- ☐ Chart-of-accounts compatibility and effective dates are verified.
- ☐ The accounting method and rule-set assignments are active.
- ☐ Positive and negative tests have passed.
- ☐ Create Accounting, transfer, General Ledger review, and reconciliation have been tested.
- ☐ Migration, approvals, rollback, and post-go-live ownership are documented.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
