Account Rules Account rules are used to determine the accounts for subledger journal entry lines. In addition, you can specify the conditions under which these rules apply. Using these capabilities, you can develop complex rules for defining accounts under different circumstances to meet your specific requirements. You can define account rules for an account, segment, or value set. Account Rules by Account Define account rules by account to determine the entire account combination. For example, an account rule defined by account can be used to determine the complete supplier liability account in Oracle Fusion Payables. Account Rules by Segment Define segment rules to derive a specific segment of the general ledger account. For example, a particular segment like the company segment can be determined from the distribution account. Another segment can be determined with the use of a constant value. Creating the account one segment at a time offers greater flexibility, but also requires more setup. Use both segment based and account based rules to derive a single account. Segment- specific rules are used, where they are defined, and take the remaining values from an account-based rule. For example, you can use an account rule which is for all segments and also separately use a rule which is for one particular segment. Segment-specific rules take precedence over the all segments account based rule. Combine account rules with segment rules. In this case, the segment value is derived from the segment rule to override the corresponding segment of the account. If the segment rule has conditions associated with the priorities and none are met, no override occurs and the segment value is derived from the account rule. Note: If the returned account is end dated with a date that is the same or before the subledger journal entry accounting date, and an alternate account is defined in the general ledger, the alternate account is used. The original account is stored on the journal line for audit purposes If the alternate account is invalid, and the Post Invalid Accounts to Suspense Account option is selected in the Create Accounting process, then a suspense account is used. An error message is displayed if a valid suspense account is not available. Account Rules by Value Sets In the absence of a chart of accounts, you may define account rules based upon value sets. This enables you to share the same rule between more than one chart of accounts if the segments in these charts of accounts share the same value set. Sharing Account Rules across Applications You may share account rules across applications in the following ways. Assign an account rule from the same or a different application to a journal line rule in the subledger journal entry rule set. For example, to derive an expense account for journal line rule Expense, assign the Projects Cost Account rule owned to the Payables journal line rule Expense. Create an account rule based on an account rule from another application and assign it to a journal line rule. For example, you may create an account rule Invoice Expense Account referencing Project Cost Account assigned in the Priorities region. You may attach the Invoice Expense Acco
https://docs.oracle.com/en/cloud/saas/financials/20b/faisl/subledger-accounting- setup.html#FAISL212668