Update 21D

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date	Product	Feature	Notes
19 JAN 2022	Cash Management	Mass Reconciliation of Bank Statement Lines and System Transactions	Updated document. Added key resources information.
19 JAN 2022	Expenses	Expense Report Risk Indicator in Expense Audit	Updated document. Revised feature information.
03 SEP 2021			Created initial document.

Overview

HAVE AN IDEA?

We’re here and we’re listening. If you have a suggestion on how to make our cloud services even better then go ahead and tell us. There are several ways to submit your ideas, for example, through the Ideas Lab on Oracle Customer Connect. Wherever you see this icon after the feature name it means we delivered one of your ideas.

GIVE US FEEDBACK

We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.

DISCLAIMER

The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.

This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.

Optional Uptake of New Features (Opt In)

Oracle Cloud Applications delivers new updates every quarter. This means every three months you'll receive new functionality to help you efficiently and effectively manage your business. Some features are delivered Enabled meaning they are immediately available to end users. Other features are delivered Disabled meaning you have to take action to make available. Features delivered Disabled can be activated for end users by stepping through the following instructions using the following privileges:

• Review Applications Offering (ASM_REVIEW_APPLICATIONS_OFFERINGS_PRIV)
• Configure Oracle Fusion Applications Offering (ASM_CONFIGURE_OFFERING_PRIV)

Here’s how you opt in to new features:

1. Click Navigator > My Enterprise > New Features.
2. On the Features Overview page, select your offering to review new features specific to it. Or, you can leave the default selection All Enabled Offerings to review new features for all offerings.
3. On the New Features tab, review the new features and check the opt-in status of the feature in the Enabled column. If a feature has already been enabled, you will see a check mark. Otherwise, you will see an icon to enable the feature.
4. Click the icon in the Enabled column and complete the steps to enable the feature.

In some cases, you might want to opt in to a feature that's not listed in the New Features work area. Here's how to opt in:

1. Click Navigator > My Enterprise > Offerings.
2. On the Offerings page, select your offering, and then click Opt In Features.
3. On the Opt In page, click the Edit Features (pencil) icon for the offering, or for the functional area that includes your feature.
4. On the Edit Features page, complete the steps to enable the feature.

For more information and detailed instructions on opting in to new features for your offering, see Offering Configuration.

Opt In Expiration

Occasionally, features delivered Disabled via Opt In may be enabled automatically in a future update. This is known as an Opt In Expiration. If your cloud service has any Opt In Expirations you will see a related tab in this document. Click on that tab to see when the feature was originally delivered Disabled, and when the Opt In will expire, potentially automatically enabling the feature. You can also click here to see features with Opt In Expirations across all Oracle Cloud Applications.

Feature Summary

Collaboration Messaging Framework

Collaboration Messaging Framework

Business-to-business (B2B) messaging is a key component of collaborative relationships and can increase the quality, quantity, and frequency of information that can be exchanged between trading partners.  However, the differences in B2B standards, technical capabilities of trading partners, and the diversity of trading partners can make this costly to establish and maintain.  Oracle Supply Chain Collaboration and Visibility Cloud manages B2B communications with trading partners by leveraging the Oracle Collaboration Messaging Framework, a next-generation B2B messaging platform that maps and routes standards-based B2B messages through a B2B solution provider, on-premise B2B application, or direct to the trading partner.  Oracle Collaboration Messaging Framework is a common infrastructure component that is included with all Oracle Cloud Applications environments at no additional charge.  It is also tightly integrated with Oracle Cloud Applications, making it easy for Oracle Supply Chain Collaboration Cloud customers to set up and manage multiple trading partner connections.

Deliver B2B Messages Via SFTP

Add a new delivery method for Secure File Transfer Protocol (SFTP), using either the Manage B2B Trading Partners or Manage Collaboration Messaging Service Providers tasks, depending on whether or not you are using a service provider.

The layout of the Delivery Methods tab has been updated, delivery methods are listed on the left hand side of the screen and the details for each delivery method displayed on the right, with only the fields that are relevant to the selected delivery method displayed.

Select a trading partner or service provider and then select Edit, on the Delivery Methods tab, add a row with a name for the delivery method and select the Delivery Method Type of SFTP. On the right side of the screen enter the details including the SFTP Host, SFTP Port, the User Name and Password required to access the directory, the File Name and the Remote Directory.

Messages delivered via SFTP will be delivered to the remote directory listed and the file name is generated using the file name from the delivery method with the Message GUID and the date time stamp appended i.e., filename_<MessageGUID>_<dateTimeStamp>.

Delivery Methods Tab

You have an additional secure protocol for sending your B2B messages.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• Oracle Supply Chain Management Cloud: Configuring and Managing B2B Messaging guide available on the Oracle Hep Center.

Role Information

• Users who are assigned this predefined job role are automatically able to access this feature:
  • B2B Administrator (ORA_CMK_B2B_ADMINISTRATOR_ABSTRACT)

Find a Document Using a Description Instead of a Coded Value

Document selection in all tasks now uses an easy-to-understand descriptive value instead of a coded name. For example, "Purchase Order - Outbound" is used instead of the coded name "PROCESS_PO_OUT". You can see this in all tasks where you select documents including:

• Manage Collaboration Messaging History
• Edit Customer Collaboration Configuration
• Edit Supplier B2B Configuration
• Edit Customer Account Collaboration Configuration
• Manage External Message Definitions
• Manage Collaboration Message Definitions

Document Selection in Manage Collaboration Messaging History

You can easily recognize documents when configuring B2B setup for your organization.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• Oracle Supply Chain Management Cloud: Configuring and Managing B2B Messaging guide available on the Oracle Hep Center.

Role Information

• Users who are assigned this predefined job role are automatically able to access this feature:
  • B2B Administrator (ORA_CMK_B2B_ADMINISTRATOR_ABSTRACT)

Financials Common

Common Financials

Service Excellence Continuing Investments

Our ongoing investment in service excellence has a focus on overall usability, resiliency, performance, and security. This work is based on monitoring performance trends, reviewing common use patterns, analyzing service requests, and participating in many discussions with customers.

In this update, our ongoing investment in service excellence includes improvements in the following areas:

Usability and Scalability

• A Notes icon on the Collections transaction page indicates the existence of notes for the transaction
• The Create Multiperiod Accounting process runs in multiple parallel threads to increase scalability and processing throughput
• Simplification of the customer setup for Portugal 
• More than 500 rows can be displayed in the Manage Fiscal Document ADFdi for Brazil

Resiliency

• Correct handling of the secondary ledger representation in SAFT-PT when the natural account used differs from the primary ledger

• Prevention of incorrect status update of an approved fiscal document for Receivables transactions with multiple service lines for Brazil

• The Deliver Balance Forward Bills process has resiliency improvements to precisely track the delivery status of the balance forward bills to prevent incorrect processing of bills that were already printed

• The Create Balance Forward Bills process contains updates to the balance forward bill report data model logic for resiliency improvements to efficiently retrieve the Balance Forward Bills Detail Print Report from BI Publisher

• The Identify Customer Contract process has resiliency and diagnostic improvements on processing a performance obligation for the accounting contract to efficiently compute the allocated amount for the exempted or non-exempted performance obligation interoperability with prospective accounting

Performance

• The AutoMatch process contains performance improvements on application of receipts to transactions. It also considers skipping the generation of amount-based recommendations, if the AR_AM_SKIP_AMOUNT_MATCH lookup is enabled, resulting in increased performance efficiency

• The Process Receipts Through Lockbox process contains performance improvements to increase scalability and processing throughput

• The Receivables Open Items Revaluation Report contains performance improvements to reduce processing time for high volume data

Steps to Enable

You don't need to do anything to enable this feature.

Taxes

Tax Exception Application to Related Taxes

Apply the tax exception derived for a source tax to related taxes in the same regime or jurisdiction. For example, apply the tax exception derived for a US State tax to City or County taxes. This reduces the setup and ongoing maintenance, and improves the run-time performance during tax calculation processing.

Organizations with a nexus in multiple states or provinces, such as in the US and South America, often use tax rate determination rules based on product fiscal classification to determine the tax rate for a particular tax jurisdiction.

An organization can alternatively set up tax exceptions by product fiscal classification, instead of using tax rate determination rules, in order to reduce the number of tax rules and conditions brought about by changes in tax rates and the addition of new tax jurisdictions. Even so, the large number of jurisdictions creates ongoing issues for both maintenance and performance.

Because the differences in tax treatment are usually by state or province, it is often only necessary to define tax exceptions at the state or province level. The Tax Engine can then assign the tax exception to the related lower-level jurisdictions, such as city and county.

The feature allows you to:

• Derive the Tax Exception rate for lower-level jurisdictions by using the Tax Exemption Source Tax specified at the Tax level. For example, for the County Tax, users can specify the Tax Exemption Source Tax as State. If this is done, the Tax engine will use the exception that was derived for the State tax for the current transaction line and apply it for the tax line for the County tax.

• Define Tax exception based on both Product category and Inventory Linked Product Fiscal Classification, only once for each of the higher jurisdiction level taxes and it will be applicable for all lower jurisdiction level taxes.

Business Benefit

• The tax rates in countries with a large number of tax jurisdictions can vary from one state/province to another for each product fiscal classification code. This feature ensures that the same tax rates can be applied to transactions with a minimal amount of setup, helping to reduce performance issues and overall maintenance.

• This feature is scalable to both Procure To Pay and Order To Cash flows across modules.

• If there is any change in Tax rate or any inclusion of any new states, this feature will minimize the setup changes in the Tax exception setups to accommodate that. Users will no longer need to create new Tax Rules or to change the conditions, this will reduce the maintenance efforts.

Steps to Enable

To enable this feature, associate the user defined reporting code to content owner (BU or LE) and the lower level TAX.

Steps to Associate:

A.  Create the Reporting Type Code

1. Navigator -> Setup and Maintenance Task - Manage Tax Reporting Types.   
2. Click on ‘+’ to create a new tax reporting type with the below values.

Tax Reporting Type Code: 'ORA_USE_EXCEPTION_SOURCE_TAX'

Tax Reporting Type Purpose:  Tax reporting type

Data Type: Text

Start Date: 1/1/01

3. Enable Reporting type use

Party tax profile  Enabled:  Y

Tax  Enabled:  Y

4. Save and Close.
5. Tax Reporting Code

Click on ‘+’ to create a new tax reporting code with the below values

Tax Reporting Code:  'ORA_USE_EXEMPTION_SOURCE_TAX'

Description:  ORA_USE_EXEMPTION_SOURCE_TAX

Effective Start Date: 1/1/01 (any date).

B.  Associate the reporting type code with the BU/LE Party Tax Profile

1. Navigator -> Setup and Maintenance Task - Manage Party Tax Profiles   
2. If required for BU, select Business Unit Tax Profiles in the LOV and Open Business Unit in edit mode. Go to the Tax Reporting Codes tab. Click on ‘+’ , and select 'ORA_USE_EXCEPTION_SOURCE_TAX' in the reporting type LOV. Select ‘ORA_USE_EXEMPTION_SOURCE_TAX’ in the reporting code LOV. Enter effective start date from which defaulting should be enabled. Save and Close.   
3. If required for LE, Select Legal Entity Tax Profiles Open Legal Entity in edit mode. Go to Tax Reporting Codes tab. Click on ‘+’ , and select 'ORA_USE_EXCEPTION_SOURCE_TAX' in the reporting type LOV. Select ‘ORA_USE_EXEMPTION_SOURCE_TAX’ in the reporting code LOV. Enter effective start date from which defaulting should be enabled. Save and Close.

C.  Associate the reporting type code with the lower level Tax

1. Navigator -> Setup and Maintenance Task - Manage Taxes
2. Search the Tax and go to Tax reporting Code tab. Click on ‘+’ , and select 'ORA_USE_EXCEPTION_SOURCE_TAX' in the reporting type LOV. Select ‘ORA_USE_EXEMPTION_SOURCE_TAX’ in the reporting code LOV. Enter effective start date from which defaulting should be enabled. Save and Close.

D.  Assign Source Tax to Lower level Tax

1. Navigator -> Setup and Maintenance Task - Manage Taxes
2. Search the Tax and go to Control and Defaults.
3. Check "Use Tax Exemption from an Existing Tax".
4. Provide Source Tax in "Tax Exemption Source" field
5. Save and Close.

To apply this feature:

1. Sign in with a role similar to that of a Tax Manager.
2. In the Navigator work area, Go to Financials -->Transaction Tax --> Manage Tax Exceptions
3. Create Tax Exception for Source Tax based on Product Fiscal Classification. For more details follow:

https://docs.oracle.com/en/cloud/saas/financials/20b/faitx/tax-configuration.html#FAITX1463811

Tips And Considerations

• To apply the tax exception to a lower-level tax from the source tax, both taxes must be applicable to the transaction. This ensures that the correct tax exception against the source tax and jurisdiction is used during calculation of the lower-level tax amount.

• The Compounding precedence of the source tax must be lower than the compounding precedence of the lower-level tax.

• The tax exception defined for the source tax is not applied if a tax exception is already defined at the lower level.

• If no source tax is applicable to the transaction at the lower level, the tax engine treats this as no tax exception exists in the source tax.

• You cannot apply a source tax exception with the type "Special Rate" to a lower-level tax.

Tax Registration Number Masking

Mask the tax registration number on all transactions to comply with the European Union General Data Protection Regulation for data protection and privacy of all individuals within the European Union and European Economic Area. The tax registration number is overwritten with a random number.

This is an enhancement to the existing process "Removal of Personally Identifiable Information", which will mask the Tax Registration number of a given party along with other attributes

You can remove an individual's personal data:

• If requested by an individual
• If the individual is no longer a valid supplier/customer for your organization

Along with the existing tables and columns from Payables, IBY, Receivables listed in https://docs.oracle.com/en/cloud/saas/financials/21a/faipp/payments-security.html#FAIPP3447843, the Tax Registration Number details are also being added.

Srl No	Product	Table	Column	Data Type	Redact	Reason for Redaction
1	Tax	ZX_REGISTRATIONS	REGISTRATION_NUMBER	VARCHAR2(50 CHAR)	Yes	Sensitive data
2	Tax	ZX_PARTY_TAX_PROFILE	REP_REGISTRATION_NUMBER	VARCHAR2(50 CHAR)	Yes	Sensitive data
3	Tax	ZX_LINES	TAX_REGISTRATION_NUMBER	VARCHAR2(50 CHAR)	Yes	Sensitive data
4	Tax	ZX_WITHHOLDING+LINES	TAX_REGISTRATION_NUMBER	VARCHAR2(50 CHAR)	Yes	Sensitive data

Business Benefit

Comply with the European Union General Data Protection Regulation for data protection and privacy of all individuals within the European Union and European Economic Area

Steps to Enable

To mask the Tax Registration Number of any given party for any product in Oracle Financials applications, you submit the Remove Personally Identifiable Information in Financials process.

1. Navigate: Navigator > Tools > Scheduled Processes.
2. On the Scheduled Processes page, click Schedule New Process.
3. Search and select Remove Personally Identifiable Information in Financials.
4. From the Party choice list, select the person's name for whom you want to remove personally identifiable information.
5. Click Submit.

Tips And Considerations

• The process will mask Tax Registration Number related to party such as supplier or customer.

• The process will mask taxpayer identifier information related to 3rd parties for Transaction Tax regimes as well as Withholding Tax Regime.

• On any transaction, if Tax determination rules are created based on 3rd party Tax Registration number and if the Registration number is redacted, then in such cases, Tax will not be calculated on the transaction

Web Services

Customer Dispute Submission Using a REST API

Submit customer disputes for one or more transaction lines using the Receivables Dispute REST API. Specify the specific transaction line or lines to dispute and the reason for the dispute. The REST API both creates the dispute and initiates the credit memo approval workflow.

You can use this service to register disputes in Receivables Cloud from external sources, and initiate the approval workflow to track them.

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Tips And Considerations

This service supports creation of disputes on one or more transaction lines against the quantity and/or line amount.

Key Resources

• For an overview of REST APIs and the technical details, see the REST API for Oracle Financials Cloud guide in the Oracle Help Center.

Party and Party Site Fiscal Classification Assignment Using REST APIs

Create party fiscal classification assignments for suppliers and customers using the Party Fiscal Classification Assignment REST API, and for supplier sites and customer sites using the Party Site Fiscal Classification Assignment REST API. This avoids manual user intervention to assign party fiscal classifications after creating a party or party site using a REST API.

The party fiscal classification assignments for suppliers, customers, supplier sites, customer sites can be created using REST API in an automated way reducing manual efforts.

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Key Resources

• For an overview of REST APIs and the technical details, see the REST API for Oracle Financials Cloud guide in the Oracle Help Center.

Print Attributes Update Using a REST API

Update print attributes, such as the print status, when printing or reprinting transactions using the Receivables Invoice REST API. This helps users maintain the most current record of printed transactions.

To update the print attributes on a transaction, pass the value Y for the InvoicePrinted attribute. You can update these print attributes: print status, time and date, customer preferred delivery method, and customer contact email addresses for Email delivery.

The business benefits include:

• Maintain a current record of printed transactions even when the transactions are printed outside of Oracle Cloud.
• Update print attributes of printed transactions in bulk.

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Tips And Considerations

Pass the value Y for the InvoicePrinted attribute to update any of the print attributes.

Key Resources

• For an overview of REST APIs and the technical details, see the REST API for Oracle Financials Cloud guide in the Oracle Help Center.

Workflow

Simplified Workflow Rules Configuration

Use the Simplified Workflow Rules Configuration feature to create workflow rules for Payables Invoice Approval and General Ledger Journal Approval workflows using spreadsheets. This feature was introduced in update 18C. In update 21D, you can specify custom values for start approver name for rules using Supervisory Hierarchy or Job Level Hierarchy approval routing. Example: 'Manager of Invoice Line.Project Manager Name' or 'Invoice Line.Project Manager Name'.

The Start Approver attribute in the Approvers section allows you to choose the starting approver from the available list of values, for rules using Supervisory Hierarchy and Job Level Hierarchy. Administrators can now use the 'Add Custom Value' option to define rules using start approvers other than those available in the list of values. You can specify either transaction attributes that indicate a user (for example, Invoice Line.Project Manager Name) or specify the user name of a specific user (for example, John.Brown). You can also specify the manager of transaction attribute users or specific users. For example, Manager of Invoice Line.Project Manager or Manager of John.Brown.

Invoice Approval Rules Sheet > Add Custom Value option

Custom Value for the Start Approver

Add Custom Value for Start Approver in Datasets

NOTE: Data Sets are available only for the Payables Invoice Approval Rule Creation templates.

For additional information about the Simplified Workflow Rules Configuration feature, please click here.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

• When using transaction attributes as the Start Approver, use the syntax: Fact Name.Attribute name. For example, Invoice Line.Project Manager Name.
• To start the approval routing from a specific user, specify the user name in the Start Approver column.

Key Resources

• For an overview of the Simplified Workflow Rules Configuration feature, refer to the Manage Workflow Rules Using a Spreadsheet topic on the Oracle Help Center.

Role Information

• Financial Application Administrator

Intelligent Document Recognition

IDR for Payables

Intelligent Document Recognition offers a fully integrated intelligent voice recognition solution that provides a seamless user experience, supporting the entire invoice lifecycle from document capture, recognition, and routing to invoice entry, approval, and payment -- all based on a unified security mode, our customers are able to quickly process supplier invoices from entry to payment. This end-to-end solution requires minimal setup and configuration, thereby reducing the total cost of ownership and enhancing capital management.

AVAILABILITY

IDR is currently only available to a small group of customers on Oracle Cloud infrastructure.

TIMING

Note that Intelligent Document Recognition releases independently of other Fusion products.

• Release to development and test environments: 11/8/2021
• Release to production: 11/22/2021
• Next release is planned for February or March of 2022

TESTING RECOMMENDATION

This release will improve invoice recognition accuracy rates with no major impact to the user experience. Only basic testing is needed.

Accounting and Control

Budgetary Control

Budget Creation and Synchronization Using Spreadsheet for Both Budgetary Control and General Ledger

Enter budgets in a spreadsheet to create budgets and synchronize budget balances for both Budgetary Control validation and for General Ledger reporting and inquiry.

You can prepare and load the expense budget data file once and then simultaneously update the budget balances in both Budgetary Control and General Ledger. You can also continue to load budget into Budgetary Control and General Ledger separately.  Select the Budget Usage parameter in Enter Budgets in Spreadsheet task to control where the budget data file will be loaded.  

Enter Budgets in Spreadsheet

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Financials  No Longer Optional From: Update 22B

Tips And Considerations

These are the opt-in defaults for your installation type:

Installation Type	Opt-In
New customer	Enabled
Upgrade customer	Disabled

Using this feature with Enter Budgets in Spreadsheets

Select the Budgetary Control validation and General Ledger reporting budget usage parameter:

• To load budget simultaneously in Budgetary Control and General Ledger

• To Specify a scenario member from the General Ledger Balances cube in which the budget is stored.  Use the Define Budget Scenarios setup task to create and review existing scenarios. Submit the Create Scenario Dimension Members process to update General Ledger Balances cube with the new created scenario member.

Select the Budgetary Control Validation budget usage parameter:

• To load budget into Budgetary Control balances only.
• To load budget separately in General Ledger use the Create Budgets in Spreadsheet task in the General Accounting Dashboard.

Key Resources

• Import Budget Data from a Spreadsheet for Budgetary Control in Using Financials for the Public Sector

Role Information

• Budget Manager role is needed to access Enter Budgets in Spreadsheet task.

General Ledger

Configurable Import Submission Options for Journal Creation Spreadsheet

Control the display of submission options when loading journals using the Create Journal in Spreadsheet task. You can create specific lookup values to set up default submission options or hide specific options.

Follow these steps to configure different submission options :

1. Navigate to the Setup and Maintenance work area and click Search under the Tasks menu.
2. In the Search page, search for the Manage Common Lookups task and navigate to the corresponding page.
3. In the Manage Common Lookups page, create a new lookup type with the following details. 

Lookup Type	Meaning	Module	Lookup Configuration Level	REST Access Secured
GL_JE_PROCESSING_OPTIONS	Journal Processing Options	General Ledger	User	Secure

See the following illustration.

Defining Lookup Type: GL_JE_PROCESSING_OPTIONS

4. To configure the default submission option, define one of the following lookup codes under the GL_JE_PROCESSING_OPTIONS lookup type based on your preference:

Lookup Code	Display Sequence	Enabled	Meaning	Description
FDI_DEFAULT_SUBMIT_OPTION	1	Checked	DEFAULT_SAVE	Set the default submission option to Save to Interface
FDI_DEFAULT_SUBMIT_OPTION	1	Checked	DEFAULT_IMPORT	Set the default submission option to Submit Journal Import
FDI_DEFAULT_SUBMIT_OPTION	1	Checked	DEFAULT_IMPORT_POST	Set the default submission option to Submit Journal Import and Posting

For example, to default the submission option to Save to Interface, enter the Meaning as DEFAULT_SAVE. Similarly to default other submission options like Submit Journal Import or, Submit Journal Import and Posting, enter the corresponding Meaning as DEFAULT_IMPORT or DEFAULT_IMPORT_POST respectively.

See the following illustration.

Defining Lookup Code to Default Submission Option

5. To hide specific options on the Submission Options dialog box, define the lookup codes as displayed in the following table. You can refer to the description column to understand which specific options would be hidden by each of these lookup codes.

Lookup Code	Display Sequence	Meaning	Description
FDI_HIDE_SAVE_TO_INTERFACE	2	Hide Save to Interface	Hide Submission Option Save to Interface
FDI_HIDE_SUBMIT_IMPORT	3	Hide Submit Import	Hide Submission Option Submit Journal Import
FDI_HIDE_SUBMIT_IMPORT_POST	4	Hide Submit Import and Posting	Hide Submission Option Submit Journal Import and Posting
FDI_HIDE_NO_IMPORT_DFF	5	Hide Do Not Import Descriptive Flexfields	Hide Import Descriptive Flexfields No option
FDI_HIDE_IMPORT_DFF_NOVAL	6	Hide Import Descriptive Flexfields Without Validation	Hide Import Descriptive Flexfields Yes without validation option
FDI_HIDE_IMPORT_DFF_WITHVAL	7	Hide Import Descriptive Flexfields with validation	Hide Import Descriptive Flexfields Yes with validation option
FDI_HIDE_DEFER_ACCT_VAL	8	Hide Defer Account Validations	Hide Other Options Defer Account Validations to Journal Import
FDI_HIDE_SEND_EMAIL_ON_ERR	9	Hide Send Email on Error	Hide Other Option Send Email Notification for Journal Import Failures

See the following illustration for an example of how to define the lookup codes and how the submission options window is rendered as a result.

Defining Lookup Codes to Hide Specific Submission Options

Sample Submission Options Dialog Box

The business benefits include:

• Minimizes the number of clicks while creating General Ledger journals via spreadsheet by enabling accounting users to set a specific default submission option.
• Provides accounting users the flexibility to choose what submission options should be exposed while creating General Ledger journals via spreadsheet.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

• Do not hide all the submission options i.e. Save to Interface, Submit Import and Submit Import and Posting. At least one of these options must be displayed. 
• Do not hide all the options for Import Descriptive Flexfields radio button in the Submission Options window.

Joint Venture Management

Joint Venture JADE Audit Report Improvements

Joint venture audit report improvements enable auditors to view additional transaction details on the Joint Audit Data Exchange (JADE) report.

Enhancements include:

• Information about source transactions originating in General Ledger and joint venture generated source transactions. Prior to this enhancement, the JADE report contained information for source transactions originating in Subledger Accounting only.

• Additional details for joint venture source transactions, including:
  • Transaction Source
  • Transaction Type
  • Transaction ID
  • Transaction Reference:
    • For Payables transactions, this is a concatenation of the invoice number, invoice line number, distribution line number, and invoice date. 
    • For General Ledger transactions, this is a concatenation of the journal source, journal name, and journal batch name. 
    • For joint venture source transactions, this is a concatenation of the joint venture name, transaction date, and overhead method name.
  • Transaction Date

• Additional details for source transactions originating from subledger accounting for Payables, including:
  • Invoice Date
  • Distribution Line Number

• Additional details for source transactions originating from general ledger and subledger accounting, including:
  • Accounting Date
  • Posted Date

• Additional details for source transactions originating from general ledger:
  • Posted Date

• Additional joint venture distribution details, including:
  • Receivables Invoice Number
  • Joint Venture Receivables Invoice Type
  • Joint Venture Receivables Invoice Date
  • Joint Venture Distribution ID
  • Joint Venture Distribution Line Number
  • Distribution Line Status

• The selection criteria has been enhanced to enable the joint venture accountant to generate audit reports for a range of:
  • Joint ventures
  • Invoicing partners
  • Projects

The business benefits include:

• Ability to generate detailed audit reports of joint venture expenditures for review by external auditors to verify compliance with the joint operating agreement (JOA).
• Reduce cost and save time on the joint venture auditing process with an audit report containing all the information required for audit purposes.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• For more information, refer to the Using Joint Venture Management guide.

Role Information

• Joint Venture Accountant

Joint Venture Operational Measures and States

Record and manage date effective operational states and measures for various levels within a joint venture to achieve more accurate calculations for overhead and allocation of accounting amounts. Operational states enables tracking of the status of a joint venture. Operational states are industry-specific and are therefore user-defined. Examples from the Oil & Gas industry would be exploration, production, on hold, or complete. Operational measures provide statistics for the activities associated with the joint venture such as units of production, water usage, equipment hours, or employee hours. These operational states and measures provide additional visibility into the operations of the joint venture.

Enhancements include:

• Operational States application that enables you to record and manage date effective operational states for your joint ventures at all levels within the joint venture.

• Operational Measures application enables you to define the different types of measures you will be tracking for your joint ventures and to also record and manage date effective operational measures for your joint ventures at all levels within the joint venture.

The business benefits include:

• Provides visibility to the different states of your joint venture, which represent distinct phases in its lifecycle. This visibility will provide additional data to ensure you have the data you need when making decisions about your operations.

• Provides a single source of truth for the measures you track for your joint venture. Having a single place to record these measures ensures data accuracy when reviewing key metrics for your joint venture for accurate financial allocations, planning, and reporting.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Determine the different types of operational states and measures for your joint ventures that you need visibility into to effectively set up the functionality.

Key Resources

• For more information, refer to the Using Joint Venture Management guide.

Role Information

• Joint Venture Accountant

Joint Venture Partner Contribution Requests

Provides the ability to initiate joint venture partner contribution requests from within Joint Venture Management and automate the creation and processing of partner contributions. This feature also includes generating Receivables invoices in Oracle Receivables for the partner contributions and capturing references of the Receivables invoices within Joint Venture Management.

The business benefits include:

• Saves time and reduces cost in processing contribution requests and corresponding receivables invoices.
• Reduces potential errors that can occur due to manual creation of partner contributions and associated receivables invoices.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Ensure that the appropriate currency conversion rates and rate types are set up to create the partner contribution Receivables invoices in currencies other than the ledger currency. Failure to do so will result in the Receivables invoice creation process ending in error.

• Set up currency conversion rates using the task Manage Daily Rates
• Set up the Receivables profile option AR_DEFAULT_EXCHANGE_RATE_TYPE using Manage Receivables Profile Options.

Key Resources

• Watch Receivables Invoices in Partner Currency (update 21D) Readiness Training.

• For more information, refer to
  • Implementing Joint Venture Management guide and
  • Using Joint Venture Management guide.

Role Information

• Joint Venture Accountant

Joint Venture Subledger for Internal Transfers

This functionality automates the process to distribute costs to all partners, including internal stakeholders that manage their financial accounts in the same primary ledger as the joint venture, but in a separate cost center. You can now automatically create internal transfer journal entries to transfer the distributed costs from the joint venture to an internal partner that does not want to receive an invoice.

Enhancements include:

• A Joint Venture Subledger that's fully integrated with Subledger Accounting. This subledger is used to create internal transfer journal entries from Joint Venture Management for posting to the General Ledger.

• Interactive processes to review the results of the creation of the joint venture internal transfer source transactions, the status of the joint venture subledger transactions, and the distributions associated with a specific internal transfer transaction.

The business benefits include:

• Reduced time and effort to process joint venture distributions with additional automated processes.
• Visibility of the status of the Subledger Accounting entries generated by the process ensures accurate and timely period close processing.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Subledger Accounting setup is needed to take advantage of this enhancement.

Key Resources

• Watch Joint Venture Subledger for Internal Transfers (update 21D) Readiness Training.
• For more information, refer to the Implementing Joint Venture Management guide.

Role Information

• Joint Venture Accountant

Joint Venture Transaction Status for Identified Transactions That Are Not Distributable

Provides the ability to change the joint venture transaction status to "Not Distributable" for all transactions, not just for project-related transactions.  Prior to this enhancement, companies could only put transactions on hold if they did not want specific transactions to be distributed and billed to partners.  Included is the ability to specify a change reason and change reason description for this and any other change made to Joint Venture Transactions, thus improving auditing of any changes made.

Set the joint venture transaction status to Not distributable and enter change reason.

View the joint venture transaction change history.

The business benefits include:

• Ability for managing partners to determine the transactions to put on hold (which are potentially available to be billed at a later date) versus transactions to mark as "Not Distributable" (which are not intended to be distributed or billed in the future).

• Increased insight for managing partners and auditors by capturing the reason joint venture transactions were manually updated.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

• Alert users of the new requirement to specify a reason code for any manually updated joint venture transactions.
• Ensure that you set up any additional reason codes using the task Manage Standard Lookups.

Key Resources

• For more information, refer to
  • Implementing Joint Venture Management guide and
  • Using Joint Venture Management guide.

Role Information

• Joint Venture Accountant

Receivables Invoices in Partner Currency

The ability to use alternate currency enables the managing partner to create joint venture invoices in various currencies while continuing to report in their ledger currency. Prior to this enhancement, managing partners could create joint venture invoices only in the primary ledger currency associated with the joint venture.

Set up the alternate currency to create the joint venture Receivables invoice from Joint Venture Management on the Joint Venture Stakeholder:

The business benefits include:

• The ability for a managing partner to support joint ventures with global partners by generating invoices in their own currency.
• Reduction of time and effort in processing invoices in multiple currencies.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Ensure that the appropriate currency conversion rates and rate types are set up to create joint venture Receivables invoices in currencies other than the ledger currency. Failure to do so will result in the Receivables invoice creation process ending in error.

• Set up currency conversion rates using the task Manage Daily Rates
• Set up the Receivables profile option AR_DEFAULT_EXCHANGE_RATE_TYPE using Manage Receivables Profile Options.

Key Resources

• Watch Receivables Invoices in Partner Currency (update 21D) Readiness Training.

• For more information, refer to
  • Implementing Joint Venture Management guide and
  • Using Joint Venture Management guide.

Role Information

• Joint Venture Application Administrator
• Joint Venture Accountant

Subledger Accounting Simplified Navigation from Joint Venture Management

Providing the ability to drill down to the associated subledger accounting transaction from Joint Venture Management enables the joint venture accounting manager to quickly identify the original transaction that was distributed to joint venture partners. Prior to this enhancement, a joint venture accounting manager would manually go the associated original transaction in case of questions or disputes, which is time-consuming.

Enhancements include:

• Source transaction reference in the Joint Venture Distributions work area for transactions originating in Payables and Payroll subledgers.
• Source transaction reference in the Joint Venture Invoices work area for transactions originating in Payables and Payroll subledgers.
• Drill down to a view-only page in subledger accounting to review the source journal entries from which joint venture transactions were created.

Open the Joint Venture Distribution that you wish to drill down to the source transaction and click the Subledger Journal link.

View the Subledger Journal Lines of the original transaction associated with the joint venture distribution. Click View Journal Entry Button to drill down into the posted journal entries.

View the journal entries from the original source transaction.

The business benefits include:

• Easy access to the associated subledger accounting transaction from Joint Venture Management facilitates quick error resolution and settlement of disputes.
• Improved reputation with external partners.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Users may need to be given additional access in case they want to drill down to the view-only page in subledger accounting to review the source journal entries from which joint venture transactions were created. The user's profile must have permissions to access this information in Oracle Financials Subledger Accounting. To do so:

• Create a new role and add function security policies and data security policies to the role.
• Add the new role to the user.
• Identify the data access sets of the source transactions and configure these data access sets to the user and role.

For more details on the security setup for viewing subledger journals, see the chapter on Security in the Implementing Joint Venture Management guide.

Key Resources

• For more information, refer to the Using Joint Venture Management guide.

Role Information

• Joint Venture Accounting Manager

Usability and Navigation Improvements for Joint Venture Transactions

Usability improvements in Joint Venture Management applications provide increased productivity through reduction of clicks, minimized scrolling, and simplified navigation.

Enhancements include:

• Incorporation of intuitive and simplified application designs in the Joint Venture Transactions work area that focuses on an engaging user experience.

The business benefit includes:

• Improvements to the Joint Venture Transactions work area provide a streamlined and intuitive user experience to search, review, and edit joint venture transactions prior to processing, reducing errors and saving time.

Steps to Enable

The Joint Venture Transactions, Joint Venture Distributions, and Joint Venture Invoices work areas require Oracle Search Extension Framework, which is enabled by default in your environment.

You can verify that Oracle Search Extension Framework is enabled in your environment from the task - Manage Administrator Profile Values. In the profile values section, verify that you have an entry with Profile Level as "Site" and Profile Value as "Yes" for the Profile Option Code ORA_FND_SEARCH_EXT_ENABLED.

Run the process “ESS job to create the index definition and perform initial ingest to OSCS” to create index definition and perform initial ingest to Oracle Search Extension Framework database. Running the initial ingest process is typically a one-time task for each predefined index. The joint venture work areas require three indices to load the data: one for joint venture invoices, one for joint venture distributions, and the other for joint venture transactions. Therefore, you will need to run the process thrice, once for each index:

• fa-fin-jv-invoices
• fa-fin-jv-distributions
• fa-fin-jv-transactions

Failure to run the initial ingest process will cause the work areas to not display any data and instead show the message “There’s nothing here so far.”

Key Resources

• Watch Usability and Navigation Improvements for Joint Venture Invoicing Readiness Training
• Watch Usability and Navigation Improvements for Joint Ventures Readiness Training
• For more information, refer to the Implementing Joint Venture Management guide

Role Information

• Application Implementation Consultant
• Joint Venture Accountant
• Joint Venture Accounting Manager

Asset and Lease Management

Assets

Asset Book Change During Source Lines Preparation

Change an incorrect asset book during source line preparation when a primary ledger has multiple associated corporate books. Use either the Assets page or the Prepare Source Lines page to change an incorrect asset book for Payables invoice lines transferred through the Create Mass Additions process.

Asset addition lines in a corporate book can be changed to an another corporate book associated with the same primary ledger. When the book is changed the queue name of the asset addition line is automatically changed to Book Changed, To post the line, enter all the mandatory attributes and change the queue name to Post using either the Edit Source Line page or Prepare in Spreadsheet.

The change book action is allowed for:

• Invoices transferred from Payables.
• Asset lines loaded using the Fixed Assets Mass Additions Import template.

The change book action is not allowed for:

• Asset lines transferred from Projects.
• Asset lines added either through Add Asset page or Add Assets in Spreadsheet.
• Asset lines already split.
• Directly on merged child line but changing the book for merged parent line will automatically change the book for all its child lines.
• Asset lines added to an existing asset as cost adjustment.

1. Click Change Book in Assets page.

2. Click Submit on the Book Change dialog box.

You can now change asset books during source line preparation when a primary ledger has multiple associated corporate books.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Financials  No Longer Optional From: Update 22C

Rule-Based Asset Book Defaulting for Invoices Transferred from Payables

Assign a default asset book to source lines transferred from Payables based on the qualified segments of the asset clearing account including balancing segment, cost center, and natural account.

When you have multiple asset books for a primary ledger, you must have a unique asset clearing account for each asset book to transfer Payables invoices to the correct asset book. Previously the Create Mass Additions process transferred invoices to an asset book when the natural account segment value in the invoice distribution account matched the asset clearing account of any asset category setup for the asset book. You can now transfer Payables invoices to the correct asset books by considering the Primary Balancing segment and Cost Center segment along with the Natural Account segment, or any one of Primary Balancing and Cost Center segments, along with the Natural Account segment.

Enable the Invoice Rules options in the Rules section of the Create Asset Book page or Edit Asset Book page.

• Natural Account - Enabled by default and can’t be disabled
• Primary Balancing - Can be enabled or disabled at anytime
• Cost Center - Can be enabled or disabled at anytime

You can specify the following combination of options:

1. Natural Account: Enabled by default and provides the existing behavior. The Natural account segment alone is considered in deciding the book.
2. Natural Account and Primary Balancing: Use these options when you set up an asset book for each balancing segment. You must set up at least one asset category for each primary balancing segment based on which the assets are transferred to the book.
3. Natural Account and Cost Center: Use these options when you set up an asset book for each cost center. You must set up at least one asset category for each cost center segment based on which the assets are transferred to the book.
4. Natural Account, Primary Balancing, and Cost Center: Use these options when you set up an asset book for each balancing segment and cost center combination. You can set up at least one asset category for each primary balancing and cost center combination based on which the assets are transferred to the book.

INVOICE TRANSFER

Create Mass Additions process transfers invoices to Assets as below:

1. First decides whether selected invoice distribution line is eligible for transfer to Assets or not by considering the natural account segment alone. The line is eligible if natural account segment of invoice distribution matches with asset clearing of any category setup for asset books belong to the same primary ledger.
2. If invoice line is eligible then transfers the invoices that matches the invoice rules of the selected asset book.

Enable the rules in the Invoice Rules tab of the Create Book or Edit Book page.

Transfer Payables invoices to the correct asset book by considering the Primary Balancing segment and/or the Cost Center segment, along with the Natural Account segment.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• Refer to support note Rule-Based Asset Book Defaulting for Invoices Transferred from Payables, (Doc ID 2797150.1) for more information on this feature.

Lease Accounting

Fixed Rent Increases

In business environments where lease administrators manage hundreds or thousands of leases, automatic rent calculation is essential to streamline business processes and avoid data entry errors.

The lease terms and conditions often include an automatic increase or decrease of the rental payment based on a fixed percentage or fixed amount. For example, rental payments may automatically increase two percent each year to cover inflation.  Lease administrators have the ability to capture a rent increase rate or amount and automatically modify the rent for future periods.

Payment Increase Agreement

The business benefits for fixed rent increases include:

• Reduced time and effort to perform rent increases or decreases. 
• Automated accounting by including rent increases into the right-of-use and lease liability, when applicable.
• Better control over payments to lessors with automated calculations.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Financials

Role Information

You do not need any new role or privilege access to set up and use this feature.

Lease Payment Updates

Update operating expense payments with the actual amounts before sending them to Payables for processing. The lease administrator can capture both rental and operating expense payments related to a lease. The operating expenses are often just an estimate at the beginning of the lease, and the amount can change each period. For example, the lease administrator may capture estimates for future utility charges. The actual amount invoiced to the lessee is what should be paid to the supplier or lessor.

Through the Manage Payments functionality, the lease administrator can search for payments and update the amount and supplier invoice number prior to sending to Payables.

Payment Search Window

The business benefits of updating lease payments include:

• Reduce effort to pay suppliers and lessors for lease related charges.
• Improved control of the amounts being paid to the lessor.
• Faster payments and reduced late fees by paying the correct amount.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Financials

Role Information

You do not need any new role or privilege access to set up and use this feature.

Lease Disclosure and Transaction Reports

Generate reports to help lessees create disclosures according to IFRS16 and ASC842 standards. The Lease Transactions and Balances report includes lease information, lease costs, cash, and right-of-use and liability balances. The reports provide balances and the related transactions that result in the balance changes from period to period.

Lease Transaction and Balances Report Available from the Drawer Panel

The business benefits include:

• Simplify compliance reporting using data from the transaction and balances report.
• Improve audit and traceability of lease balances with related transaction activity.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Financials

Role Information

You do not need any new role or privilege access to set up and use this feature.

Payables and Expenses

Expenses

Attendee Capture in Expenses Mobile Application

Capture employee and non-employee attendee details for all expense types to accurately track attendees.

The Expenses mobile application enables employees to add employee and non-employee attendee details to meals, entertainment, and miscellaneous expense types. Employees can add the attendees directly from their phone contacts and calendar events, or add them manually by providing required details. When adding attendees manually, employees can search for other employee attendees by first name, last name, or email address, and add them to the expenses from the search results. Nonemployee attendees can be added by providing the attendee details such as first name, last name, company, email, and phone number. The application alerts employees if an employee's email id is provided for a nonemployee attendee.

When employee attendees are added from phone contacts or calendar events, the Expenses mobile application updates their names to match with their existing employee records. The mobile application validates the attendee categories and alerts employees when they add invalid attendees to the expenses. It also checks if employee attendees are missing when the policy mandates them and alerts the employees accordingly.

Add Attendees from Calendar Event

Employees can also allocate expense amounts to the attendees individually or split the amount equally among all attendees. The Expenses mobile application alerts employees if attendee amount is missing when policy mandates it, or if total amount doesn't match the expense amount. Employees can fix the issues and submit the expenses directly from the mobile application.

Employee and Non-Employee Attendees with Amount Divided Equally

Attendee capture in the mobile application enables employees to add attendees to their expenses and submit them directly from the mobile application. Adding attendees directly from calendar events and phone contacts improves ease of use and helps save time.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

To use this feature, ensure that you have downloaded the latest Expenses mobile application.

Key Resources

• Refer to the Capture Attendee Information for Expense Categories topic in the Oracle Financials Cloud Implementing Expenses guide to learn how to set up attendees policy.

Role Information

You must add the ORA_PER_REST_SERVICE_ACCESS_PUBLIC_WORKERS_RO role to employee roles to enable the attendee information.

Auditing of Duplicate Expenses and Expenses Under Receipt Threshold

Route expenses for audit that were identified as duplicates by the Expenses application and changed to actual expenses by employees. Detect expenses that circumvent receipt requirements by being under the receipt thresholds enforced by the company.

Set up audit rules to flag these scenarios when employees submit expense reports:

• Employee submits a duplicate expense by marking the expense as not a duplicate to get paid twice for a single expense.
• Employee submits expenses just under the required receipt threshold, to avoid providing proof of spending.

By setting up audit rules to identify duplicate expenses that weren’t marked as duplicates and expenses that are within the receipt required threshold, companies can reduce the time auditors spend on expense reports and help them identify fraudulent activity.

Steps to Enable

To set up auditing of duplicate expenses and expenses under receipt threshold, perform the following steps:

1. Sign in as an expense manager.
2. From the Setup and Maintenance work area, navigate to the Manage Expense Report Audit Rules page.
3. Under Audit Rules for Expense Report Item, you can configure these rules:
   1. Audit expense reports for duplicate expense - To set up auditing of duplicate expenses.
   2. Audit expense reports with amount below the missing receipt threshold - To set up auditing of expenses that are less than the receipt threshold. You must enter a percentage of the receipt threshold. An expense amount less than this value is flagged. You must also enter the number of incidents and a period in months. This rule will flag expenses only if these occurrences exceed the specified number of times in the specified period.

Manage Expense Report Audit Rules

Role Information

You need the Expense Manager role to enable auditing of duplicate expenses and expenses under the receipt threshold.

Detailed View of Audit Results in Expense Audit

Display automatic audit checks performed on expense reports using audit rules. Provide auditors with a detailed view of these audit results.

Expenses provides a detailed view window that displays the audit rules applied to each expense report, along with a pass or fail status for each rule.

Auditors can review these audit result details while auditing an expense report. Auditors can view the number of expense items that failed a particular rule. If a rule failed because of duplicate expense items or duplicate attendees, auditors can drill down into the expense item details.

To access the detailed view, navigate to the Manage Expense Reports page, and drill down on an expense report. On the Audit Expense Report page, click the Audit Rules Checked link in the Expense Report Summary drawer to open the window.

Audit Rules Checked

Duplicate Expenses

Duplicate Attendees

Auditors now have greater insight into the audit rules run on expense reports and are better informed to make decisions.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

To set up audit rules, refer to the documentation link under Key Resources.

Key Resources

• How You Set Up Expense Report Auditing

Role Information

You need the Expense Auditor role to use this feature.

Expense Report Risk Indicator in Expense Audit

Evaluate the potential risk of an expense report using preconfigured rules and provide visual indicators for risk in the expense report audit.

The Expenses application calculates the risk of an expense report based on the audit rule violations for the expenses in the report. The possible risk values associated with each expense report are High, Medium, or Low. Auditors can select a specific expense report from the Manage Expense Reports page and click Audit Expense Report to view the risk and take appropriate action.

Auditors can also view the risk for each expense report in the Manage Expense Reports page. The Risk column in the Manage Expense Reports page is not exposed by default. To view the Risk column in the audit search results, select the View option from the Search Results table. Then select the Columns option and enable the Risk column. 

Manage Expense Reports

Audit Expense Report

Audit reasons have default risk levels assigned as listed in the table below.

Audit Reason Code	Audit Reason Meaning	Risk Level
AGED_EXPENSE_ITEMS	Aged expense items	Low
AMOUNT_OVER_THRESHOLD	Amount over threshold	Low
AUDIT_LIST_MEMBER	Audit list member	High
EMPLOYEE_INACTIVE	Inactive employee	High
EMPLOYEE_ON_LEAVE	Employee on leave of absence	High
EXPENSE_TEMPLATE	Expense template	Low
EXPENSE_TYPE	Expense type	Medium
EXPENSE_TYPE_AMOUNT	Expense type over amount	Medium
EXPENSE_CUM_AMOUNT	Expense type over cumulative amount	Medium
ORA_KEYWORD_VIOLATION	Keyword violation	Medium
IMAGED_RECEIPT_MISSING	Missing imaged receipt	Medium
POLICY_VIOLATION	Policy violation	High
RANDOM_SELECTION	Random selection	Null
RECEIPT_REQUIRED	Receipt required	Low
ORA_DUP_EXPENSE_ITEM	Duplicate expense item	High
ORA_PUB_SEC_ATTENDEE	Public sector attendee	Medium
ORA_SAME_POL_VIO_IN_PAST	Same policy violation in past	High
ORA_TOP_POL_VIOLATOR	Top policy violator	High
ORA_TOP_SPENDER	Top spender	High
ORA_EX_RECPT_THRESHOLD	Exceeded receipt required threshold	Medium
ORA_DUP_ATTENDEE	Duplicate attendee	Medium

To customize the risk levels for each audit reason, navigate to the Manage Standard Lookups page and create the following Lookup Types: EXM_AUDIT_RISK_HIGH, EXM_AUDIT_RISK_MEDIUM, and EXM_AUDIT_RISK_LOW. Associate the Audit Reason Codes from the above table with the new Lookup Types.

If you are associating an Audit Reason Code without the ORA_ prefix, add it to the Lookup Code and Meaning columns. For example, to associate audit reason code EXPENSE_TYPE with Lookup Type EXM_AUDIT_RISK_LOW, enter EXPENSE_TYPE to the Lookup Code and the Meaning columns.

If you are associating an Audit Reason Code with the ORA_ prefix, add it to the Meaning column and add the same reason code without the ORA_ prefix to the Lookup Code column. For example, to associate audit reason code ORA_KEYWORD_VIOLATION with Lookup Type EXM_AUDIT_RISK_HIGH, enter KEYWORD_VIOLATION to the Lookup Code column and enter ORA_KEYWORD_VIOLATION to the Meaning column.

The Audit Reason Codes that are not associated with the new Lookup Types will have a risk level of Null.

Help auditors with a high volume of reports prioritize their audits by risk level. 

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

You must set up audit rules to make use of the risk indicator. To set up audit rules, refer to the documentation link under Key Resources.

Key Resources

• How You Set Up Expense Report Auditing

Role Information

• You need the Expense Auditor role to use this feature.
• You need the Application Implementation Consultant role to customize the risk levels for each audit reason.

Pay Group for Cash Advances and Expense Reports

Enable specific pay groups for cash advances and expense reports with negative reimbursement amounts. Creating distinct pay groups allows companies to process cash advance and expense reimbursements separate from the refunds collected from employees.

These pay groups prevent the negative payment requests from getting applied against positive payment requests and cash advances. This helps in efficiently processing the cash advances and expense reimbursements.

Using specific pay groups also helps companies to easily track and close all the negative payment requests.

Steps to Enable

To set up a pay group for negative expense reports, perform the following steps:

1. Sign in as the Application Implementation Consultant.
2. From the Setup and Maintenance work area, navigate to the Manage Expenses System Options page.
3. Under Processing Options for Expense Report, select a pay group for Pay Group for Negative Expense Reports.
4. You can select a value from the list of pay groups available or you can search for a specific pay group and assign the value.

You can assign the pay group at the implementation level on the Manage Expenses System Options page, which applies to all business units. Alternatively, you can specify exceptions for specific business units on the Create System Options: Specific Business Unit dialog box.

Pay Group for Negative Expense Reports

To set up a pay group for cash advances, perform the following steps:

1. Sign in as the Application Implementation Consultant.
2. From the Setup and Maintenance work area, navigate to the Manage Cash Advance and Authorization Policies page.
3. Under Cash Advances, select a pay group for Payment Group for Cash Advances.
4. You can select a value from the list of pay groups available or you can search for a specific pay group and assign the value.

You can assign the pay group at the implementation level on the Manage Cash Advance and Authorization Policies page, which applies to all business units. Alternatively, you can specify exceptions for specific business units on the Create Business Unit - Specific Cash Advance Policies dialog box.

Pay Group for Cash Advances

Configured Pay Group Assigned to a Negative Expense Report

Role Information

• To setup pay groups, you need one of these roles:
  • Expense Manager
  • Application Implementation Consultant

Policy Enforcement for Miscellaneous Expenses in Mobile Application

Validate miscellaneous expenses for policy violations within the Expenses mobile application. The mobile application performs the same validations that are enforced online. If your company policy permits submission of expenses with policy violations, provide a justification in the mobile application. If company policy does not allow an expense report submission with policy violations, you cannot submit an expense item. You must correct the expense item using the mobile application.

Expenses evaluates each miscellaneous expense reimbursement eligibility and alerts employees to miscellaneous expenses that are not eligible for reimbursement.

Miscellaneous Policy Violation Warning Message on View Expense Screen

Miscellaneous Policy Violation Error Message on View Expense Screen

Enforcing miscellaneous policies in the Expenses mobile application enables employees to review their miscellaneous expenses, fix any issues, and submit them directly from the mobile application.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

To use this feature, ensure that you have downloaded the latest Expenses mobile application.

Key Resources

• Refer to the Set Up a Miscellaneous Expense Policy topic in the Oracle Financials Cloud Implementing Expenses guide to learn how to set up a miscellaneous policy.

Role Information

You don't need a new role or privilege access to use this feature.

Project Expenditure Organization Capture in Expenses Mobile Application

Capture project expenditure organization in Expenses mobile application for project-related expenses. Provide a default project expenditure organization when applicable and restrict selection to valid project expenditure organizations.

When employees navigate to the Add Expense screen and the Add Mileage screen on the Expenses mobile application, the project expenditure organization field is displayed when the project-related expense is selected. Depending on the configuration, a default value is displayed in the project expenditure organization field. They can either select the default value or select a relevant expenditure organization from the list. They can also search for a specific organization and select from the search results. If the expenditure organization field is configured as mandatory, the application shows an alert when the field is not populated.

Project Expenditure Organization Field Displayed for a Project-Enabled Expense

Assigning expenses to the correct project expenditure organization ensures that the expense is charged to the right organization. 

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

• Ensure that Expenditure Organization (Organization_ID) is enabled for Expense Report Line in Project Costing Fields DFF, for the project expenditure organization field to be displayed for project-related expenses

• To use this feature, ensure that you have downloaded the latest Expenses mobile application.

Role Information

You don't need a new role or privilege access to use this feature.

Payables

Automatically Increment the Date Parameter for Cost Transfers to Cost Management Schedule Runs

Automatically increment the date parameter of the Transfer Costs to Cost Management process based on the scheduled frequency. Use this option to schedule the process for the desired frequency without manual intervention.

This feature automatically increments the Cutoff Date parameter of the Transfer Costs to Cost Management process.

Transfer Cost to Cost Management - Cutoff Date Parameter

Transfer Cost to Cost Management - Auto Increment Option

In the Schedule tab of the Advanced Options section for the Transfer Costs to Cost Management process, select the schedule frequency and enable the Auto Increment option. This will automatically increment the Cutoff Date parameter.

For example, let’s assume that the Transfer Costs to Cost Management process is scheduled to run with a frequency of Daily from 01-Nov-2021 to 30-Nov-2021. The Cutoff date is set as 01-Nov-2021 and the Auto Increment option is enabled. In this case, when the process runs on 1st Nov 2021, the cutoff date will be 01-Nov-2021. On 2nd Nov 2021, the cutoff date will be automatically incremented to 02-Nov-2021.

You can use this option to schedule a process to run for an extended period of time, while ensuring that the cutoff date for the data being transferred in each run is incremented as per the scheduled frequency.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Any preexisting schedule for this process will continue to run with a fixed cutoff date. You can enable the Auto Increment option for cutoff date only after defining a new schedule with the desired frequency.

Create Invoice for Items Ordered and Priced in Different Units of Measure

Customers in certain industries like food and beverage, often purchase items that naturally vary in size per item (blocks of cheese, pieces of meat, and so on). It's common for such items to be invoiced based on the actual weight delivered.

Create purchase order matched invoices for items with dual units of measure (UOM). Dual UOM items can be ordered in the UOM used for packing and shipping. They are invoiced based on the actual weight of the items received in the item's secondary UOM. You can select the secondary UOM as the pricing UOM, which is a new attribute available on the order line. The items are invoiced according to the actual quantity received in the item's secondary UOM.

For example, a buyer places an order for Chicken in the item's primary UOM, Case, and prices it in the item’s secondary UOM, Pounds.

• Each Case weighs around 80 Pounds on average.
• The price agreed is $1.25 per pound.
• Supplier delivers a case of chicken weighing 82 pounds.
• The invoice is based on the actual weight of item delivered in its secondary UOM, i.e. 82 pounds.

Purchase Order Line Ordered in Primary UOM and Priced in Secondary UOM

Invoice Created in the Secondary UOM

This feature enables you to accurately price and invoice the item based on the exact weight delivered, while ordering it in the UOM used for packing and shipping.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

• You must create the invoices for dual UOM items in the same UOM that is used for pricing on the purchase order.

• Due to the nature of these items, invoiced quantity may vary from the expected quantity on the order. Configure an appropriate tolerance for quantity ordered to allow variations. Use 3-way matching level with tighter tolerances for quantity received to avoid overbilling.

Key Resources

• For more information on creating purchase orders for dual UOM items, refer to the Procurement feature "Purchase Items That Are Priced in Their Secondary UOM".

Receivables and Cash

Advanced Collections

History of Collections Scoring Details

Maintain a history of collections scoring details, including the data point values, to better explain the score calculation. The user can store the history of collections scoring details with data point values at the time of the collection scoring process. This helps provide a better understanding about the collection score calculation by showing the values against each data point which are used in the collection formula.

A new data model is created for this feature with the table name IEX_SCORE_DATA_POINT_HISTORIES. Scoring data point values and weight scores of scoring formulas are stored in the columns DATA_POINT_VALUE and WEIGHTED_SCORE respectively.

The business benefits include:

• Provide better clarity about the calculation of collection score.
• Use stored data point values for reporting or other customized processes.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Financials

Collections Strategies by Transaction Type

Define and run collections strategies based on the transaction type assigned to the transaction. This helps support more flexible and targeted strategies.

You can define and run strategies and strategy tasks for individual transactions by transaction type. Use the Manage Collections Strategies page to specify the transaction type and create/add the strategy task against the transaction type, when these strategy tasks are applicable to a transaction.

For example, create a strategy and define 'n' number of transaction types for the strategy, and create/add 'n' number of tasks for each transaction type. The 'Process Strategy Task' evaluates the transaction type of each transaction and assigns the strategy tasks accordingly.

Site Strategy:

Transaction Type	Strategy Task
License Invoice	Soft letter, Soft call
Royalty Invoice	Send Soft Dunning Letter, Send Medium Dunning Letter

Say a party has 3 delinquent transactions and Site Strategy opened on the customer. Strategy Tasks got assigned to transaction basis transaction type.

Transaction Number	Transaction Type	Strategy Tasks
TRX1	License Invoice	Soft Letter, Soft Call
TRX2	Royalty Invoice	Send Soft Dunning Letter, Send Medium Dunning Letter
TRX3	License Invoice	Soft Letter, Soft Call

The business benefits include:

• Extends the capability of assigning delinquent strategies to transaction by transaction type.
• Improves the collections process by focusing the delinquent tasks for specific customers and transactions.

Steps to Enable

The feature is enabled by default. To use this feature, complete these steps:

Offering: Financials

I. Enable Feature

1. Click Navigator > My Enterprise> Offerings
2. On the Offerings page, select Financials.
3. Click the Opt In Features button
4. On the Opt In: Financials page, click the Features icon for Collections. A list of Collections features is displayed.
5. The following Collections features need to be enabled as prerequisite and save the changes.
   • Collections Scoring and Strategy Assignments by Segment
   • Automatically Initiate or Fulfill Collections Tasks in Third Party Systems
   • Collections Strategies for Individual Transactions

II. Define Transaction Level Strategy Group

1. From the Setup and Maintenance work area, access the Manage Collections Strategies.
2. Use the Create or Edit Strategy Group page to create a strategy group with transaction level tasks for each transaction type.

Cash Management

Mass Reconciliation of Bank Statement Lines and System Transactions

Reconcile high volumes of bank statement lines and system transactions. This allows users to select and group several statement lines and system transactions outside the application and perform reconciliation. 

You can select a large volume of system transactions and bank statement lines, and group and reconcile them using a spreadsheet.

Users can select and group statement lines and system transactions belonging to either one or multiple sources to create one-to-many or many-to-many reconciliations that cater to the specific bank reporting process. 

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

1. To perform mass reconciliation, you must do the following:

• Export the unreconciled transactions into a spreadsheet.

• Review and use the column “Reconciliation Group” column from the TransactionsAvailableforReconciliation.xls to enter a common reference for matching bank statements and system transactions.

• Import the reconciliation details into Oracle Cash Management using File-Based Data Import (FBDI).

2.  In the Manual Reconciliation UI, you can provide a date range to export the transactions falling in that range. If no dates are provided, the statement lines and system transactions of the last 180 days are exported to the spreadsheet.

3. The manual tolerance rule set up on the bank account is evaluated to reconcile the grouped transactions.

Key Resources

Related Help:

• Cash Management Bank Statement Reconciliation Data Import in the File-Based Data Import (FBDI) for Financials guide
• How Mass Reconciliation of Bank Statement Lines and System Transactions Is Processed in the Using Payables Invoice to Pay or Using Receivables Credit to Cash guides
• Whitepaper - Release 21D: Mass Reconciliation of Bank Statement Lines and System Transactions (Doc ID 2827173.1)

Receivables

Customer Dispute Submission Using a REST API

Submit customer disputes for one or more transaction lines using the Receivables Dispute REST API. Specify the specific transaction line or lines to dispute and the reason for the dispute. The REST API both creates the dispute and initiates the credit memo approval workflow.

You can use this service to register disputes in Receivables Cloud from external sources, and initiate the approval workflow to track them.

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Tips And Considerations

This service supports creation of disputes on one or more transaction lines against the quantity and/or line amount.

Key Resources

• For an overview of REST APIs and the technical details, see the REST API for Oracle Financials Cloud guide in the Oracle Help Center.

Print Attributes Update Using a REST API

Update print attributes, such as the print status, when printing or reprinting transactions using the Receivables Invoice REST API. This helps users maintain the most current record of printed transactions.

To update the print attributes on a transaction, pass the value Y for the InvoicePrinted attribute. You can update these print attributes: print status, time and date, customer preferred delivery method, and customer contact email addresses for Email delivery.

The business benefits include:

• Maintain a current record of printed transactions even when the transactions are printed outside of Oracle Cloud.
• Update print attributes of printed transactions in bulk.

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Tips And Considerations

Pass the value Y for the InvoicePrinted attribute to update any of the print attributes.

Key Resources

• For an overview of REST APIs and the technical details, see the REST API for Oracle Financials Cloud guide in the Oracle Help Center.

Revenue Management

Standalone Selling Prices in One Reference Currency

A business who establishes standalone selling prices in a single currency can now use those established standalone selling prices in accounting contracts denominated in other currencies.

You can now use your established standalone selling prices that are designated in a single reference currency to evaluate and assign pricing dimensions and standalone selling prices to all of your accounting contracts, regardless of the associated entered or accounted currency of the source document line.

This feature lets you:

• Designate a single reference currency for standalone selling prices applicable across all ledgers configured within your instance. 
• Designate an application-wide reference currency for standalone selling prices applicable to all source document lines, regardless of the source application.
• Designate rate type and date for translating source document lines to reference currency equivalents when evaluating amount pricing band segment value assignments.
• Evaluate and assign pricing dimension amount band segments based on the source document line’s reference currency equivalent amount.
• View the standalone selling price for the performance obligation and underlying promises in both reference and entered currencies in the Edit Customers Contracts page.
• Simplify and reduce the ongoing maintenance of establishing and maintaining standalone selling prices and pricing dimension bands in multiple currencies.

In support of this new feature, the following configurations and attributes are now available in the Revenue Management application.

MANAGE SYSTEM OPTIONS FOR REVENUE MANAGEMENT

Manage System Options for Revenue Management

REFERENCE CURRENCY STANDALONE SELLING PRICES

A new region, Reference Currency for Standalone Selling Prices, is now available in the Manage System Options for Revenue Management page.

NOTE: The Reference Currency for Standalone Selling Prices settings are only applicable to the assignment of pricing dimension combinations and SSPs.  The settings are not used in the conversion of foreign currency source document lines to ledger currency.

Use the Reference Currency for Standalone Selling Prices region to:

• Enable the Enable Reference Currency option.

• Select the currency to use as the reference currency.

• Select the rate type for converting revenue line amounts to the reference currency.

• Select the rate date of the rate to use to convert amounts to the reference currency.
  • Contract date is the date associated with the revenue management accounting contract.
  • Reference currency rate date is the date interfaced on the source document header or source document line from your upstream systems.

When the Enable Reference Currency option is enabled:

• The application uses the currency selected in the Currency field as the lookup currency when assigning SSPs instead of the entered currency of the source document line.  

• The application uses the rate from the rate type and date for the selected currency to convert the applicable entered currency amounts from the source document line to the reference currency.  The reference currency equivalent amount is then use to evaluate and assign the pricing dimension amount segment pricing band value for the pricing dimension combination for the line's item, memo line, item group or template.

• The application uses the date type in the Rate Date as the date for the rate for conversion of the entered currency to reference currency for the pricing dimension combination and SSP assignment.

When the Enabled Reference Currency option is not enabled:

The application uses the standard functionality for assigning pricing dimension combinations and SSPs, where SSPs are established in the source document line entered currency.

REVENUE BASIS DATA IMPORT FILE BASED DATA IMPORT (FBDI)

The Reference Currency for Standalone Selling Prices feature lets you select either the revenue management accounting contract date or a reference currency rate date as the date type when looking up the conversion rate for translating the source document line amounts and prices to reference currency equivalents for pricing dimension combination amount bands and SSP assignments.

Depending on your source applications and the document types you are using to capture your sales cycle transactional data, you may choose to use the booking, activation, or funding date available on the transaction header or line as this date. The source document and source document lines interface tables now contain the Reference Currency Conversion Rate Data attribute to capture the desired date.

When you select Reference Currency Rate Date as the rate date in the Manage System Options for Revenue Management page, the application uses the date provided on the source document or source document line in this attribute field as the reference currency conversion rate date.

Source Documents

Source Document Lines

The application applies a default hierarchy when determining which reference currency conversion rate date to use.

• Source document line – Reference Currency Conversion Rate Date
• Source document – Reference Currency Conversion Rate Date
• Source document – Document Date

When the rate date is selected as the contract date in the Manage System Options for Revenue Management page, the default hierarchy is not applied and the date in the Reference Currency Conversion Rate Date column is ignored.

CREATING AND MANAGING STANDALONE SELLING PRICES IN REFERENCE CURRENCY

The Standalone Selling Prices in One Reference Currency feature simplifies the creation and management of standalone selling prices.  When enabled, you only need to create and maintain standalone selling prices in one single currency for each unique combination of Item, Memo Line, Performance Obligation Template, and Item Group, Pricing Dimension Combination, Effective Period, Unit of Measure for the SSP Representation Types in use.  You need only upload standalone selling prices in the defined reference currency.  You no longer need to create and maintain standalone selling prices based on the entered currencies of your source transaction lines.

CREATING AND MANAGING PRICE DIMENSION PRICING BANDS

The Standalone Selling Prices in One Reference Currency feature not only simplifies the creation and management of standalone selling prices, it also simplifies the creation and maintenance of pricing dimension bands. When enabled, you only need to create and maintain pricing dimension bands in one single currency for pricing dimension amount segments using pricing bands. This eliminates the need to define and maintain pricing bands for each entered currency.

ASSIGNMENT OF PRICING DIMENSION PRICING BANDS

Revenue Management lets you segment your pricing dimension structures using amount bands. You can define amount bands for several attributes, such as the selling amount, list price amount, and base price amount, along with any amount defined within an extensible numeric attribute.

When the Reference Currency for Standalone Selling Prices option is enabled, Revenue Management uses the applicable pricing dimension amount’s reference currency equivalent when evaluating and assigning the pricing band amount segment band value.

The reference currency equivalent amount is derived by taking the source document line’s applicable amount and converting it to the reference currency using the reference currency conversion rate information.  The reference currency equivalent amount is then evaluated against the pricing bands, which are assigned to the SSP profile defined in the reference currency.  The resulting pricing band segment value is then stamped on the performance obligation or promised detail line.

ASSIGNMENT OF STANDALONE SELLING PRICES

Once the pricing dimension combination is assigned to the performance obligation or promised detail line, Revenue Management can assign the standalone selling price. Revenue Management selects the standalone selling price to assign to the performance obligation or promised detail line based on the combination of attributes: Item, Memo Line, Performance Obligation Template, or Item Group; Pricing Dimension Combination; Effective Period; Unit of Measure; and Currency. Revenue Management uses the same logic except when looking up the SSP, the reference currency is used instead of the source transaction line’s entered currency.  When the Reference Currency for Standalone Selling Prices option is enabled, Revenue Management selects and assigns the standalone selling price defined in the reference currency.

If the item, memo line, performance obligation template or item group is assigned to a Standalone Selling Price Profile using a SSP Representation Type of Unit Price, the Reference Currency Unit Price SSP is translated back to the source transaction line’s entered currency prior to stamping the SSP.  Revenue Management uses the inverted value of the reference currency conversion rate to derive the entered currency Unit Price SSP.

If the item, memo line, performance obligation template or item group is assigned to a Standalone Selling Price Profile using a SSP Representation Type of Percentage of Base Unit Price, Discount Percentage of Unit List Price, or Gross Margin where the Reference Currency Unit SSP is represented by a percentage, the percentage is used as defined for the reference currency. There is no conversion performed back to the line’s entered currency before stamping the SSP on the performance obligation or promise detail line.

ADDITIONAL ERROR HANDLING AND MESSAGING

Edit Customer Contracts Page

Reference currency-specific error messages are now available to help you resolve data issues when using the Standalone Selling Prices in One Reference Currency feature.  If the Identify Customer Contracts process is unable to assign the pricing dimension combination or SSPs to the performance obligation or promised detail line due to missing rate information required for converting amounts, Revenue Management line-level error messages now display reference currency-specific error messages.

When the application is unable to derive the reference currency rate from the General Ledger Daily Rates table, it marks the promised detail line and assigns an error message stating that the reference currency conversion rate is missing.

The contract is then assigned an allocation status of Pending allocation with an allocation pending reason of Reference currency conversion rate is missing.

When you re-run the Identify Customer Contract process, if the application finds the missing rate, the error message and allocation status is updated accordingly.

VIEWING ASSIGNED REFERENCE CURRENCY UNIT SSP

You can view the reference currency unit SSP assigned to the accounting contract by selecting the Reference Currency Unit SSP attribute by clicking View > Columns in the Performance Obligations and Promised Detail tabs in the Edit Customer Contract page.  The reference currency code value used at the contract’s inception to assign the pricing dimension segment values and standalone selling prices for the contract is displayed in the attribute column label.  The column attribute value represents a unit price or percentage, depending on the SSP representation type of the Standalone Selling profile that is assigned to the line.   You can view the unit SSP in both the reference and entered currency for the line.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

• The Reference Currency for Standalone Selling Prices option is an application-wide setting and applies to all ledgers defined within the Revenue Management application.

• You can enable or disable the option at any time.  Changes to the settings apply to new and unprocessed lines from the change date forward.  

• Reference currency attributes assigned to a contract at the time of contract creation are used throughout the contract’s life cycle and any follow on activities such as contract modifications.

• Discard Customer Contract process: When discarding an accounting contract via the Discard Customer Contract process, the contract's assigned pricing dimension combination and SSP are cleared. When you re-run the Identify Customer Contracts process, the pricing dimension combination and SSP are derived again based on the current Reference Currency for SSP settings.

• Interfaced unit SSP: For source document lines where the unit SSP is interfaced from the source application, the Revenue Management uses the interfaced unit SSP for the line, regardless of the Reference Currency for Standalone Selling Prices option setting.

• Implied Obligations: SSPs are assigned to implied obligations based on the Standalone Selling Price profile of the implied obligation’s item or memo line. When Reference Currency for Standalone Selling Prices option is enabled, the reference currency rate date of the implied obligation’s related line is used when evaluating and assigning pricing dimension amount band segment values.

• Immaterial Change: When adding a new performance obligation to an existing contract using the immaterial change functionality, Revenue Management uses the reference currency rate date on the new source document line or its header when available.  When not available, Revenue Management uses the source document line’s contract revision date as the reference currency rate date.

Role Information

No new role access is needed to use this feature.

Region and Country-Specific Features

Brazil

Bulk Reprocessing of Fiscal Documents in Error Status for Brazil

Use the Import Fiscal Document Approval FBDI for Brazil to reprocess in bulk the fiscal documents returned in error by the tax authority.

The Brazilian tax authority returns fiscal documents in error when there are validation issues. If the validation issue is due to a common setup error shared by multiple fiscal documents, reprocess and resubmit these fiscal documents in bulk using the Import Fiscal Document Approval FBDI template after fixing the setup errors.

To reprocess fiscal documents in bulk:

1. In the Fiscal Document Key column, enter the fiscal document key for each transaction.
2. In the Fiscal Document Event Code column, enter Status Request.
3. In the Tax Authority Return Code column, enter Reprocess.
4. Submit the template.

Import Fiscal Document Approval FBDI Example

Reprocess and resubmit fiscal documents with a common setup issue in bulk that were returned in error by the tax authority. This replaces the manual process of correcting each fiscal document individually.

Steps to Enable

You don't need to do anything to enable this feature.

Portugal

On-Account Credit Memo for Portugal

Allow on-account credit memos in Portugal. This was previously not available for Portugal.

You will be able to create manual on-account credit memos for a Portugal implementation.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

• There are two new Global Descriptive Flexfield attributes to capture the reference time period of an on-account credit memo.
• Reference Date From and Reference Date To. These two dates will be used as the reference for the on-account credit memo in both the printed output and the SAF-T file.
• You need to use this in combination with the existing Global Descriptive Flexfield attribute Reference Application Type set as Multiple.

Key Resources

• Billing Software Certification for Portugal topical essay.

Regional Shared Features

Single Step Submission of Select Transactions for Tax Reporting and Tax Allocation Processes

Submit the Select Transactions for Tax Reporting and the Tax Allocation processes in one step.

This is an enhancement to the existing Select Transactions for Tax Reporting and Tax Allocation Process that allows you to submit these processes in one step for reporting entities that use the Tax Allocation Process and related reports. This feature has no impact on reporting entities which are not using the Tax Allocation Process. For those, you can continue to run the Select Transactions for Tax Reporting process independently.

The business benefits include:

• Reduce the processing time for the Tax Allocation and the Select Transactions for Tax Reporting processes.
• Help automate the tax period closure and reduce tax reporting processing time.
• Minimize user clicks during the tax period closure.

Steps to Enable

To enable this feature, follow these steps to define the JE_FEATURE_OPTIN lookup type with the lookup code JE_21D_OI_SINGLE_TRL_EXEC:

1. Go to the Manage Standard Lookups page.
2. Search for the lookup type JE_FEATURE_OPTIN.
3. Add the new lookup code JE_21D_OI_SINGLE_TRL_EXEC to the lookup type and select the Enable check box.
4. Save the data.

Tips And Considerations

• For a legal reporting unit where Enable allocation is checked and JE_FEATURE_OPTIN lookup type is defined with the lookup code JE_21D_OI_SINGLE_TRL_EXEC, the Select Transactions for Tax Reporting and Tax Allocation processes run in one step. You can't run the Select Transactions for Tax Reporting process alone. When the selection process is submitted as a standalone process, it will finish with an error.

• To submit selection process and tax allocation process in one step, you just submit the Tax Allocation process. The Select Transactions for Tax Reporting process is submitted as a child process. The Tax Allocation process pauses until the selection process completes.

• If the Enable allocation checkbox is enabled but there are no allocation rules defined, you can clear the check box.

• If the Enable allocation checkbox isn't enabled, you can run the Select Transactions for Tax Reporting process in standalone mode.

Key Resources

• Related Help: Tax Allocation Process and Reporting Topical Essay

Role Information

• To use this feature, you need these privileges and roles:
  • Prepare Tax Selection Processing (JE_PREPARE_TAX_SELECTION_PROCESSING_PRIV)
  • Prepare Tax Allocations (JE_PREPARE_TAX_ALLOCATIONS_PRIV)
  • Prepare Tax Box Allocation Rules (JE_PREPARE_TAX_BOX_ALLOCATION_RULES_PRIV)
  • Prepare Tax Allocation Listing (JE_PREPARE_TAX_ALLOCATION_LISTING_PRIV)
  • Prepare Tax Allocation Rules Listing (JE_PREPARE_TAX_ALLOCATION_RULES_LISTING_PRIV)
  • Prepare Tax Final Reporting (JE_PREPARE_TAX_FINAL_REPORTING_PRIV)

U.S. Federal Financials

U.S. Federal Financials

U.S. Federal BETC on Interest Invoice

Populate the Business Event Type Code on interest invoices to properly classify the type of payment for inclusion in SPS and PAM payment files.

During payment processing, the Federal BETC on Interest Invoice feature populates the BETC on the interest invoice created based on the invoice options settings. If the interest allocation method is set to all invoice lines, the BETC is copied from the first distribution line of the first invoice line to all distributions of the interest invoice. If the interest allocation method is set to single distribution, the default payment BETC of the fund segment of the interest expense distribution account assigned on the invoice options page is used and populated as the BETC for all distribution lines of the interest invoice.

Business benefits include:

• Complies with government reporting requirements.
• Generates the correct payment format file and report for interest invoices.

Steps to Enable

Complete the Mange Invoice Options task in Payables:

• Set up the Interest Expense Distribution account.
• Set the interest allocation method to All Invoice Lines or Single Distribution.

U.S. Federal Journal Line Attributes

Capture Federal attributes on General Ledger journal lines to support GTAS, DATA Act, and CTA interfaces.

The following attributes have been added at General Ledger journal line level to capture information required for GTAS and CTA reporting:

• BETC: The agency Business Event Type Code, identifies the type of activity and the effect of a transaction on the fund balance with Treasury. In combination with the TAS it's used to classify transactions reported to Treasury through all GWA-compliant FMS systems.

• Federal or Non-Federal Code: Determines if the record is Federal, General Fund or Non-Federal, it indicates the type of entity involved in the transaction.

• Trading Partner TAS: Trading Partner Treasury Account Symbol, identification code assigned by Treasury, in collaboration with OMB and the owner agency. This code is only entered, and is a required value, when the Federal or Non-Federal Code is Federal or General Fund.

• Trading Partner BETC: Trading Partner Business Event Type Code, identifies the trading partner's type of activity and the effect of a transaction on the fund balance with Treasury. This code is only entered, and a required value when the trading partner TAS is required. The trading partner BETC type (payment or collection) cannot match the agency BETC type (payment or collection).

• Agency Location Code: The list of values contains all internal agency location codes defined.

The following attributes have been added at the General Ledger journal line level to capture federal award financial information required for DATA Act reporting:

• Enable for DATA Act Reporting: Indicates if the journal line is enabled for recording DATA Act award attributes.

• DATA Act Award Type: The award type can be procurement or financial assistance.

• PIID: Procurement Instrument Identifier, identifies the specific award being reported, required if the DATA Act award type is procurement.

• Parent Award ID: An optional field, available only when the DATA Act award type is procurement.

• FAIN: Federal Award Identification Number, unique ID for  an optional attribute when the DATA Act award type is financial assistance.

• URI: Unique Record Identifier, an optional attribute when the DATA Act award type is financial assistance. When the DATA Act award type is financial assistance, either the FAIN or the URI has to be populated.

U.S. Federal Journal Line Attributes

The business benefits include:

• Enables statutory government reporting.
• Provides defaulting and validations that reduce the amount of manual data entry required.
• Reduces the chance of data entry errors and decreases the amount of time and money spent on investigating inaccuracies.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• File-Based Data Import (FBDI) for Financials, General Ledger Journal Import