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're 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.
-
If the returned account is end dated with a date that's 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, the Create Accounting process creates the journal in the invalid status. An error message is displayed to indicate the GL account is invalid.
-
If the derived account or the alternate account is invalid and the Create Accounting process is submitted with the process event parameter set to Invalid Account, the invalid account is replaced with the suspense account defined in the ledger option for the ledger.
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 Account rule to the journal line rule Expense in the journal entry rule set.
-
To share an account rule across applications, all sources used by the account rule must be available for the event class.
-
If the sources are available, an account rule is assigned to a journal line rule in the journal entry rule set. Verification occurs to confirm that all sources used by the account rule are available for the journal line rule accounting event class. Journal line rules are only available if the sources are shared; such as reference objects.
Account Rules and Mapping Sets
Mapping sets can be used to associate a specific output value for an account or segment. You can use mapping sets in account rules to build the account.
Account Rules Conditions
In the account rules you may specify conditions for each rule detail line. Priorities determine the order in which account rule conditions are examined. When the condition is met, the rule associated with that priority is used. Depending on which of the defined conditions is met, a different account rule detail is employed to create the account.
The Create Accounting process evaluates conditions based on the priority of the rule detail. When the condition is met, the rule detail is applied.
Constant values that are used in any Conditions region must not contain the following characters:
-
"
-
,
-
& -
|
-
(
-
)
-
'
For example, in the condition "Project Type" = ABC (123), the constant value following the equal sign, ABC (123), contains restricted characters ( ) that enclose 123 and is invalid.