Update 22C

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	Module	Feature	Notes
20 DEC 2022	Common Financials	Predefined Roles for Oracle Fusion Enterprise Resource Planning for Self Service Cloud Service	Updated document. Revised Key Resources section.
15 DEC 2022	Payables	Conversion of Emails Into Attachments for Supplier Invoices Using Intelligent Document Recognition	Updated document. This feature is not yet available.
24 AUG 2022	Financials Common/Taxes	Product Fiscal Classification Defaulting from Purchase Category	Updated document. Revised feature information.
12 AUG 2022	Financials Common/Taxes	Product Fiscal Classification Defaulting from Purchase Category	Updated document. Corrected Opt-In Lookup Code name.
12 AUG 2022	Lease Accounting	Lease Termination Import	Updated document. Added Key Resources.
29 JUL 2022	Common Financials	Service Excellence Continuing Investments	Updated document. Revised feature information.
29 JUL 2022	Budgetary Control	Budgetary Control Invoice Payments for Cash Budgets in Manage Payment Process Requests	Updated document. Added Key Resources.
18 JUL 2022	Expenses	Prepaid Expense Entry	Updated document. Delivered new feature in update 22C.
16 JUN 2022	Regional Shared Features	VAT Reporting Performance Improvements	Updated document. Revised setup and opt-in information.
16 JUN 2022	Financials Common	Predefined Roles for Oracle Fusion Enterprise Resource Planning for Self Service Cloud Service	Updated document. Delivered new feature in update 22C.
16 JUN 2022	General Ledger	Efficiency Improvements for General Ledger Posting Processes	Updated document. Delivered new feature in update 22C.
16 JUN 2022	Common Financials	IMPORTANT Actions and Considerations	Updated document. Added information about deprecated features in update 22C.
03 JUN 2022			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

Retrieve Large Purchase Order Payloads for B2B Messaging

Configure Oracle Collaboration Messaging Framework to process large purchase orders (typically more than 2,000-lines) when you initiate B2B communication. The payload for a large purchase order is retrieved in small parts from Oracle Purchasing and then combined and delivered as one purchase order, resulting in improved performance.

After you enable the feature, enter a value in the Large PO Processing section of the Manage Collaboration Messaging Configuration page in the Large PO Minimum Line Count field to specify the minimum number of lines in a large PO. Then enter a value in the PO Lines Retrieved in a Single Query field to specify the number of lines to retrieve from Oracle Purchasing in each part (1000 lines by default). The values you set in the Large PO Delivery Duration (30 minutes by default) and Large PO Delivery Attempt Interval (3 minutes by default) fields indicate how long and how often to attempt delivery of the PO.

NOTE: This feature was also made available in the May monthly update of 22B.

Large Purchase Order Processing in Manage Collaboration Messaging Configuration

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: Order Management

Tips And Considerations

In general, a purchase order with more than 2,000 lines is considered a large purchase order, but you can determine the minimum line count for your large purchase orders based on your specific business needs.

Key Resources

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

Role And Privileges

You have a couple of options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

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

• Users who are assigned configured job roles that contain this privilege are able to access this feature:
  • Manage Collaboration Messaging Configuration (CMK_MANAGE_COLLAB_MESG_CONFIG_PRIV)

Send UBL PEPPOL Invoice Responses to Suppliers

Use the new predefined message definition UBL-2-1-InvoiceApplicationResponse-Out to send details about rejected invoices in the UBL PEPPOL format to your suppliers.

Enable the procure-to-pay business process to exchange the associated document, Invoice Acknowledgment-Outbound.

Set up this message definition as an outbound collaboration message for a trading partner and then associate the trading partner, and the Invoice Acknowledgment-Outbound document with a supplier using the Manage Supplier B2B Configuration task in the Collaboration Messaging work area.

UBL-2-1-InvoiceApplicationResponse-Out Message Definition

Enables automated invoice status communication using the UBL PEPPOL application response message.

Steps to Enable

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

Key Resources

• Configuring and Managing B2B Messaging for Oracle Applications Cloud guide available on the Oracle Help Center.

Role And Privileges

You have a couple of options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

• Users who are assigned any of these predefined job roles can access this feature:
  • Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)

• Users who are assigned a configured job role that contains these privileges can access this feature:
  • Manage B2B Supplier Trading Partners (CMK_B2B_SUPPLIER_TRADING_PARTNERS_PRIV)
  • Manage B2B Trading Partners (CMK_B2B_TRADING_PARTNERS_PRIV)

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

• Changes to the fiscal document pages to show the correct discounts and adjustments in line with the recent enhancements in the fiscal document extract.

• Display of notes icon on AR invoices Edit Transaction page enhanced to display a “Create Note” icon when no note is associated and display a “Notes” icon when invoice has note associated with it.

• Display the email addresses and phone numbers in the Bill-to Contact LOV on the Edit Transaction page. This enhancement helps users to quickly identify the correct bill-to contact.

• The Deliver Balance Forward Bills process can run concurrently from different users and all bills are recorded as successfully printed.

• Support withdrawal of the AR dispute management workflow tasks when task creator is no longer with the organization.

Resiliency

• Error message has been improved in the error notification to display the proper message that user or approver does not have the privilege to reassign task to another user, when approval task is reassigned to another user using vacation rules and the user going on vacation does not have privilege to reassign the task

• Hold Resolution Workflow performance improved by fetching only the relevant invoice details from service call instead of fetching all invoice lines and distributions details to build the notification title and process orchestration

Performance

• Improved performance of Balance Transfer Job during printing of Output file with source and target Account Information

Steps to Enable

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

Simplified Workflow Rules Configuration

Use the Simplified Workflow Rules Configuration feature to create workflow rules using spreadsheets for Payables Invoice Approval and General Ledger Journal Approval workflows. Download the templates using the Manage Workflow Rules in Spreadsheet task to create and manage workflow rules according to your approval policies.

This feature was introduced in update 18C. In addition to the existing features, the 22C update also lets you view additional configuration settings for approval routings to do the following:

• Configure the job level options to better control the approvals.

• For approval routing of Group in Parallel, specify the voting percentage that is needed for the outcome to take effect, such as a majority vote or a unanimous vote.

Additional settings for job level hierarchy in approval routing lets you configure relative to whom the approval goes and further limit the list of approvers within the job level hierarchy.

Use voting outcome option when multiple users, working in parallel, must act and outcome takes affect only when consensus percentage is satisfied. Votes can be counted instantly and the voted outcome triggered when minimum percentage is met, instead of waiting for all to finish.

Steps to Enable

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

Tips And Considerations

Supplementary Job Level Options

To view more Job Level options for rules whose approval routing is Job Level Hierarchy:

1. Click on View Additional Settings.
2. Select the Supplementary Job Level Options checkbox.

How to View Supplementary Job Level Options

The Job Level approval routing ascends the supervisory hierarchy, starting at a given approver and continuing until an approver with a sufficient job level is found. Use the supplementary Job Level options for improved control over list of approvers,

1. Relative-to: Minimum Job Level - Specify whom the minimum Job Level Range value is relative to. Possible values are: Starting Approver, Creator & Absolute.
2. Relative-to: Maximum Job Level - Specify whom the maximum Job Level Range value is relative to. Possible values are: Starting Approver, Creator & Absolute.
3. Effective Approvers - Select only the approvers specified in this option from the calculated list of approvers. Available options are: All Approvers, Starting and Final Approver & Final Approver Only.
4. Include all Managers at Last Level - Includes all managers in the list of approvers if the job level is same as that of the last approver in the list. Possible values are: Yes/ No.

Enter Values for Supplementary Job Level Options for Rules Whose Approval Routing is Job Level Hierarchy

Voting Outcome Properties

To view Voting Outcome Properties for approval routing of Group in Parallel:

1. Click on View Additional Settings.
2. Select the Voting Outcome Properties checkbox.

How to View Voting Outcome Properties

Use this option when multiple users, working in parallel, must act, such as in a hiring situation when multiple users vote to hire or reject an applicant. You specify the voting percentage that is needed for the outcome to take effect, such as a majority vote or a unanimous vote.

1. The Voted Outcomes, select an outcome for the workflow assignment (for example, Any, ACCEPT, REJECT, or any other outcome specified).

   • The Any outcome enables you to determine the outcome dynamically at runtime. For example, if you select Any and set the outcome percentage to 60, then at runtime, whichever outcome reaches 60% becomes the final voted outcome. If 60% of assignees vote to reject the outcome, then it is rejected.

2. Vote Percentage - specify a percentage value required for the outcome to take effect (for example, a majority vote (51) or a unanimous vote (100)).

   • For example, assume there are five workflow assignments made in parallel, two of them are accepted and three are rejected, and the required percentage of approval is 50%, then the overall outcome is rejected. Selecting a percentage of 30% when workflow is assigned to only two approvers does not make sense.

3. In the Default Outcome list, select the default outcome to take effect if the consensus percentage value is not satisfied.
   • This happens if there is a tie or if all users do not respond before the workflow assignment expires.

4. Specify additional group voting details:

   • Immediately trigger voted outcome when minimum percentage is met.

     • If selected, the overall outcome of the workflow can be computed early with the outcomes of the completed workflow assignments, enabling the pending assignments to be withdrawn. For example, assume four users are assigned to act on, the default outcome is APPROVE, and the consensus percentage is set at 50. If the first two users approve, the third and fourth users do not need to act on, since the consensus percentage value has been satisfied.

   • Wait until all votes are in before triggering outcome.

     • If selected, the workflow waits for all responses before a final outcome is initiated.

[Figure 4] Enter Voting Outcome Properties where, (i.) Workflow requires 100% Approval from all assignees. (ii.) Terminate the workflow immediately when 50% of the assignees have Rejected

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 And Privileges

• To use simplified workflow rules configuration, you need this role:
  • Financial Application Administrator

Workflow Transaction Console

Use the Workflow Transaction Console to proactively monitor all workflow tasks and resolve the exceptions for these workflows:

• Invoice Approval
• Expense Approval
• Journal Approval
• Invoice Hold Resolution

This feature was introduced in update 19D, with Invoice Hold Resolution workflow added in update 21B. In update 22C, this feature will be enabled by default for all customers.

When this feature is enabled, users will continue to see the following statuses on the transactions, even when the approval process fails for the transaction.

Workflow Name	Workflow Transaction Status
Invoice Approval	Initiated
Expense Approval	Pending manager approval or Pending individual approval
Journal Approval	In process

If you have not enabled this feature, the following statuses are displayed for the transactions where the approval process failed.

Workflow Name	Workflow Transaction Status
Invoice Approval	Rejected
Expense Approval	Required
Journal Approval	Saved

In case of the Hold Resolution Workflow, there are no changes to the workflow status of the transaction irrespective of whether this feature is enabled or not.

If you had already enabled this feature and then decided to opt out, this feature will not be re-enabled for you in update 22C.

For all failed workflow transactions, the workflow administrator or workflow submitter of the transaction receives an email notification for the error. Workflow administrators must review all failed transactions and the failure causes on the Workflow Transaction Console page and take appropriate action.

You can find additional details for this feature in the 19D release notes and help center documentation.

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

This feature has been enabled by default for new customers from update 19D onwards.

From 22C update, this feature will be enabled by default for upgraded customers as well.

You still have the option to opt out of using this feature. However, we strongly recommend that you plan for the uptake of this feature. If you wish to opt out of using the feature, follow these steps:

1. Click the Navigator, and then click New Features (under the My Enterprise heading).

2. On the Features Overview page, go to the Available Features tab.

3. Select the Workflow Transaction Console feature and click on the Enabled icon.

4. On the Edit Features page, deselect the Enable option for the feature or feature choices as required and then click Done.

Tips And Considerations

To display only financial-related tasks in the Workflow Transaction Console, enable the transaction security feature by using these steps:

1. Go to Navigator > Setup and Maintenance > Manage Enterprise HCM Information.

2. Click Edit > Correct.

3. In the Transaction Console Information section, select Enable Transaction Security.

Role And Privileges

• Financial Application Administrator

Predefined Roles for Oracle Fusion Enterprise Resource Planning for Self Service Cloud Service

Oracle Fusion Enterprise Resource Planning for Self Service Cloud Service enables customers to easily provide access to self-service functions, such as expense reporting, timecard entry, and transaction approval to users.

Either use the predefined abstract role Enterprise Resource Planning Self Service User or create a new role and assign it to users who need access to this service. The abstract role is a comprehensive collection of privileges that provide access to all ERP self-service capabilities, including expense reporting, timecard entry, talent profile management, and scheduled process submission. In addition, assign additional predefined duty roles for approvals and reporting access.

Enterprise Resource Planning Approval Duty

This duty allows a user with the Enterprise Resource Planning Approval Duty to:

• Manage time cards
• Manage change requests
• View payables invoices
• Approve lease contracts 

Enterprise Resource Planning Reporting Duties

Assign one or more predefined reporting duty roles to allow self-service users to view reports and drill down to view transaction details.  Each of the duties supports reporting for specific business functions and provides access to appropriate Oracle Transactional Business Intelligence (OTBI) subject areas, Financial Reporting Center, and drill-down to the related transaction pages.

Use the reporting duties as building blocks to create new roles tailored to business-specific requirements. Define data security policies for each new role to allow appropriate data access for each of the reporting duties.

The predefined reporting duty roles are:

• General Ledger Self Service Reporting Duty (with updated Drill Down to Journal privilege) 
• Payables Self Service Reporting Duty
• Receivables Self Service Reporting Duty
• Fixed Assets Self Service Reporting Duty
• Budgetary Control Self Service Reporting Duty
• Revenue Management Self Service Reporting Duty
• Projects Self Service Reporting Duty 

The business benefit of using the Enterprise Resource Planning Self Service User is to speed up implementation for defining self-service access with targeted business functions available in the new role. 

Steps to Enable

These roles are delivered in 22C. For instructions, refer to security guide in Getting Started with Your Financials Implementation for more details. 

Tips And Considerations

• Continue to use existing roles that provide targeted business functions for self-service users, such as Customer Account Payable Specialist, Team Collaborator, and Project Team Member, separately or in combination with the new Enterprise Resource Planning Self Service User role.

• Use the existing privilege Allocate Project Expense for allocation in combination with the new Enterprise Resource Planning Self Service User role to allow reporting of project expenses.

Key Resources

• Getting Started with Your Financials Implementation
• Updated Oracle Fusion Service Descriptions

Taxes

Derivation of Tax Rates Based on UOM for Quantity-Based Taxes

Use the transaction Unit of Measure to derive the appropriate tax rate for quantity-based taxes. This allows users to compute, charge, and report accurate tax amounts when multiple UOMs are used for the same item.

Create a tax rate setup using a quantity-based rate for a Unit of Measure through the existing Manage Tax Rates page and use this tax rate for tax calculation on a transaction, even if the transaction uses a different Unit of Measure. The enhanced tax calculation converts the quantity-based rate configured in the tax rate setup to the transaction Unit of Measure.

NOTE: Unit of Measure conversion between tax rate Unit of Measure and transaction Unit of Measure must be defined in order to allow the quantity-based tax rate derivation during tax calculation.

This feature allows the tax calculation on transactions with a Unit of Measure different from the one used in in the tax rate definition for a quantity-based tax.

Steps to Enable

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

Exclusion of Documents from Tax Calculation by Partner

Exclude Payables invoices that result in no taxes calculated by tax partners from the tax partner transaction data extract. This helps improve process performance and reduce payload and processing costs by avoiding unnecessary calls to the partner tax engine.

This is applicable for both batch and online tax partner integration.

Steps to Enable

You can exclude Payables invoices from tax partner calculation for specific Payables sources, supplier types or specific supplier and supplier sites.

For setting up exclusions based on Payables sources, complete the following steps:

1. Click Navigator > My Enterprise > Setup and Maintenance > Search > Manage Standard Lookups.
2. Search for the ZX_OPTIN_OPTIONS lookup type. If it is not defined, create it.
3. In the Lookup Codes section, add and enable the PTNR_AP_EXCLUDE_SOURCE lookup code. Click Save.

4. Create ZX_AP_EXCLUSION_SOURCES lookup type.
5. In the Lookup Codes section, add and enable lookup codes for Payables sources that you want to use for exclusion. These values must be from the lookup codes defined for the Payables lookup type SOURCE. For example, you can configure exclusion for the source External, as shown below. 

For setting up exclusions based on supplier types, do the following steps:

1. Search for the ZX_OPTIN_OPTIONS lookup type. If it is not defined, create it.
2. In the Lookup Codes section, add and enable the PTNR_AP_EXCLUDE_SUPPLIER_TYPE lookup code. Click Save.

3. Create ZX_AP_EXCLUSION_SUPPLIER_TYPES lookup type.
4. In the Lookup Codes section, add and enable lookup codes for supplier types that you want to use for exclusion. These values must be from the lookup codes defined for the lookup type POZ_VENDOR_TYPE and assigned to suppliers. For example, you can configure exclusion for the supplier type MANUFACTURING, as shown below. 

For setting up exclusions based on specific supplier and supplier sites, do the following steps:

1. Search for the ZX_OPTIN_OPTIONS lookup type. If it is not defined, create it.
2. In the Lookup Codes section, add and enable the PTNR_AP_EXCLUDE_SUPPLIER_SITE lookup code. Click Save.

3. The exclusion, in this case, is based on the Allow tax applicability setting at the supplier site address or supplier level. If it is checked or not set, the invoices will be included. If it is unchecked, the invoices will be excluded.

Tips And Considerations

• Excluded Payables invoices cannot be reported by the tax partner as there is no call made to the tax partner for such invoices.
• The lookup definitions are not date effective. The settings will be considered as of the system date for all the invoices.
• Predefined Payables sources which start with ORA_ cannot be used as sources for exclusion based on Payables sources.
• The exclusion criteria apply only for Payables invoices and not other documents such as Purchase orders and requisitions.
• The following table shows how the exclusion logic works based on the Allow tax applicability setup at the supplier and supplier site address level.

Allow tax applicability checkbox at supplier level	Allow tax applicability checkbox at supplier site address level	Invoice included/excluded from partner calculation
Not set	Not set	Included
Not set	Checked	Included
Not set	Unchecked	Excluded
Checked	Not set	Included
Checked	Checked	Included
Checked	Unchecked	Excluded
Unchecked	Not set	Excluded
Unchecked	Checked	Included
Unchecked	Unchecked	Excluded

Input Tax Rate Code Association for Payables Intercompany Invoices

Set up an input tax rate code that corresponds to an output tax rate code. On the Payables intercompany invoice, the tax engine will then use the input tax rate code associated with the output tax rate code on the Receivables intercompany invoice. This allows the segregation of input and output tax rate codes which can be used to fulfill tax reporting needs.

Many customers, particularly those operating in the European Union, use the tax rate code to separate their input and output transactions. Currently, this is not possible for intercompany transactions as the tax engine copies the tax rate code from the intercompany Receivables invoice to the intercompany Payables invoice. By enabling this feature, customers can meet this requirement for intercompany transactions.

Steps to Enable

A new field Input Tax Rate Code is added to the Edit Tax Rate page in the Rate Period Details region. The tax rate code provided in this field will replace the tax rate code copied from the intercompany Receivables transaction on the corresponding intercompany Payables invoice.

The new field is only available on the Edit Tax Rate page and cannot be updated through other means such as Rapid Implementation spreadsheets and REST API.

Tips And Considerations

1. The input tax rate code association is only applicable to intercompany Payables invoices and not for any other transactions.
2. If the Input Tax Rate Code field has a value, it will be copied over when a new rate period is created. You can change it if required.
3. The Input Tax Rate Code list of values will only display tax rate codes for which the following conditions are met:

• The tax regime and the tax are the same as those of the tax rate code for which the input tax rate code is being specified.

• The Allow ad hoc tax rate check box option is selected for the tax rate code.

• The tax jurisdiction is the same as the tax rate code for which the input tax rate code is specified. If the tax rate code does not specify a tax jurisdiction, then the input tax rate code also should not have a tax jurisdiction specified.

Examples

In the following examples of intercompany Receivables and Payables invoices, assume that the tax regime and tax for the tax rate codes STD-OUTPUT and STD-INPUT are GB-VAT-Regime and GB-VAT respectively.

1. There is no Input Tax Rate code specified.

Tax Rate Code	Input Tax Rate Code for Tax Rate Code	Percentage	Tax Status	Tax Jurisdiction
STD-OUTPUT	Not specified	10	STANDARD	GREAT BRITAIN

If STD-OUTPUT is the tax rate code on the Receivables transaction, the same tax rate will be on the Payables invoice as well.

2. The Input Tax Rate code is specified, and both tax rate codes have the same rate percentage, tax status and jurisdiction.

Tax Rate Code	Input Tax Rate Code for Tax Rate Code	Percentage	Tax Status	Tax Jurisdiction
STD-OUTPUT	STD-INPUT	10	STANDARD	GREAT BRITAIN
STD-INPUT		10	STANDARD	GREAT BRITAIN

If STD-OUTPUT is the tax rate code on the Receivables transaction, the tax line on the Payables invoice will have the tax rate code of  STD-INPUT, the tax status of STANDARD and the jurisdiction GREAT BRITAIN. If the tax status for STD-INPUT was STANDARD-INP, the tax line on the Payables invoice will have the tax status of STANDARD-INP.

3. The Input Tax Rate code is specified, and both tax rate codes have the different rate percentages, and jurisdiction is not specified.

Tax Rate Code	Input Tax Rate Code for Tax Rate Code	Percentage	Tax Status	Tax Jurisdiction
STD-OUTPUT	STD-INPUT	10	STANDARD
STD-INPUT		20	STANDARD-INP

If STD-OUTPUT is the tax rate code on the Receivables transaction, the tax line on the Payables invoice will have the tax rate code of  STD-INPUT and the tax status, STANDARD-INP, but the percentage will be retained as 10%.

4. Input Tax Rate code is specified for the tax rate code with a rate percentage of 0. Both the tax rate codes have same tax status and jurisdiction.

Tax Rate Code	Input Tax Rate Code for Tax Rate Code	Percentage	Tax Status	Tax Jurisdiction
STD-OUTPUT	STD-INPUT	0	STANDARD	GREAT BRITAIN
STD-INPUT		10	STANDARD	GREAT BRITAIN

If STD-OUTPUT is the tax rate code on the Receivables transaction, the tax line on the Payables invoice will have the tax rate code of STD-INPUT, but the percentage will be retained as 0%. To self-assess the standard tax rate for this tax, STD-INPUT needs to have an offset tax rate associated. If not, tax processing will result in an error.

All the examples in this section pertain to how a tax that appears on the intercompany Receivables invoice is treated on the corresponding intercompany Payables invoice. When the Payables legal entity is in another country, say Belgium, the self-assessment (reverse-charge) of Belgian VAT will happen as part of the process of evaluating additional applicability.

Product Fiscal Classification Defaulting from Purchase Category

Use the Purchase Category code specified on the transaction line as the Product Fiscal Classification value during tax calculation when the Purchase Category Set matches the Primary Inventory Category Set defined in the Manage Country Default Controls. This enables the reuse of tax rules and exceptions for non-inventory purchases defined for inventory-based purchases. Such rules can leverage the levels available in Product Fiscal Classification Types, dramatically reducing the number of rule conditions, and improving run-time performance.

Customers implementing taxes for Procure-to-Pay flows use the Purchasing Category Set as a key tax determinant. While Purchasing Category Set is available as a determinant to use in Tax Rules, it does not support the definition of level-based conditions supported for Product Fiscal Classifications. Customers can achieve this by defining items (Master Items) for their non-inventory purchases, associating each item with the appropriate item category (i.e., the purchasing category), and defining the Purchasing Category Set as a Product Fiscal Classification Type. However, many customers do not want to define items for their non-inventory purchases. To minimize the need for manual user updates on invoice lines for non-inventory purchases, this enhancement copies the Purchasing Category available on the transaction line to the Product Fiscal Classification field so that tax rules or exceptions defined with Product Fiscal Classifications can be used.

The new feature is available only if the opt-in CALC_22C_OI_CP_PURCATEG_TO_PFC is enabled.

This feature uses the Purchasing Category as the Product Fiscal Classification during the tax calculation flow only when all three of the following conditions are true:

• Purchasing Category Set is identical to the Primary Inventory Category Set in Manage Country Default Controls.
• Purchasing Category Set value on the transaction line is defined.
• The Product Fiscal Classification value on the transaction line is not defined.

The Purchasing Category is not used as the Product Fiscal Classification field when any of the following is true:

• Purchasing Category Set is not identical to Primary Inventory Category Set in Manage Country Default Controls.
• Purchasing Category Set value on the transaction line is not defined.
• Purchasing Category Set value on the transaction line is defined but the Product Fiscal Classification Value on the transaction line is also defined.

Business benefits for this feature are:

• Leveraging the Product Fiscal Classification levels in rule conditions or Tax Exceptions reduces the configuration necessary to determine taxes for non-inventory purchase transactions.

• Simplifies the ongoing maintenance of such rule conditions or exceptions.

• Improves the run-time performance, particularly in rule condition processing.

Steps to Enable

To enable this feature, follow these steps and define the lookup type ZX_OPTIN_OPTIONS and the lookup code CALC_22C_OI_CP_PURCATEG_TO_PFC:

1. Go to Manage Standard Lookups page.
2. Search for the lookup type ZX_OPTIN_OPTIONS. If the lookup type does not exist add new lookup type ZX_OPTIN_OPTIONS.
3. Add the new lookup code CALC_22C_OI_CP_PURCATEG_TO_PFC to the lookup type and select the Enable check box.
4. Save the data.

To use this feature, follow these setup and process flow steps:

1. Navigator > Setup and Maintenance Task > Manage Country Default Controls. Search the Country and go to Edit Country Default Controls > Fiscal Classification Defaults. Define the default value used on transactions belonging to parties in the applicable country in the Primary Inventory Category Set field. Save and Close.
2. Navigator > Setup and Maintenance Task > Manage Product-Based Fiscal Classifications > Create Product Fiscal Classification Type Group for Inventory Category Set.
3. Navigator > Setup and Maintenance Task > Manage Tax Rules - Tax Applicability Rules, Tax Rate Rules, or other rules depending on your requirements. Create rules that you require choosing the Tax Determining Factor Class of Product Inventory linked, and the Tax Determining Factor Name value defined in the previous step.
4. Navigator > Setup and Maintenance Task > Manage Tax Exceptions, if required. Create a tax exception for the tax based on Product Fiscal Classification.
5. Navigator > Payables > Invoices > Create an invoice by matching with a PO line for a non-inventory item. Ensure that a value is not selected in the Product Fiscal Classification field. Calculate tax for the non-inventory item. You will observe that the tax engine uses the Purchasing Category value to evaluate Product Fiscal Classification-based rules and exceptions.

Tips And Considerations

• To use this feature, make sure that CALC_22C_OI_CP_PURCATEG_TO_PFC is enabled and the Purchasing Category Set is selected as the Primary Inventory Category Set in the Manage Country Default Controls.

• If the Purchasing Category on the transaction line is not defined, the Product Fiscal Classification value will not be copied.

• Ensure that the Purchasing Category on the transaction line belongs to the Catalog that has been defined as the Primary Inventory Category Set in Manage Country Default Controls.

Role And Privileges

No additional role is required.

Accounting and Control

Budgetary Control

Budgetary Control Invoice Payments for Cash Budgets in Manage Payment Process Requests

Provide Budgetary Control validation in Payment Process Requests. This validation allows payment of invoices only when funds are available in the cash control budget.

Prevent Invoice Payments When There Are Insufficient Funds

Budgetary control validation has been added to payment processing requests. Invoices are paid only when there are available funds in the cash control budget. Budgetary control validation failures are displayed on the Resolve Payment Validation Errors page. You can review the budgetary control validation failure, correct the failure or remove the payment, and resubmit the payment process request.

Resolve Payment Validation Errors

See details of the budgetary control validation failure by clicking on the funds status to open the View Funds Results page.  On the Resolve Payment Validation Errors page, click the View Payment icon to open the Payment page.

Payment Fails Due to Insufficient Funds

Completed payments are reserved and reduce the funds available for the cash control budget.  If a payment or payment file is voided, funds will be added back to the cash control budget.

Funding the Cash Control Budget

The cash control budget can also be impacted by journal entries. When the cash accounts defined in the Edit Budgetary Control page, Accounts in Journals Subject to Cash Controls region are present in a journal, it will impact the cash control budget balances.

Edit Budgetary Control

Journals that debit the assigned accounts will increase the cash control budget balance as a negative expenditure when journals budgetary controlled and reserved in General Ledger.

Steps to Enable

Budgetary Control Setup

Enable cash controls on the Manage Budgetary Control and Encumbrance page. When you enable cash controls for a ledger a cash control budget is automatically created.

See the video for details on setup.

Subledger Setup

To budgetary control the correct cash distribution in General Ledger, enable these options:

• Multifund accounting in Receivables.
• Automatic offsets on the Manage Common Options for Payables and Procurement page.
• Pooled account for the bank account on the Edit Bank Account page.

Tips And Considerations

Cash Control Budget

A generic cash control budget is automatically created when you enable cash controls.  This control budget is not automatically put in use so you can modify it to meet your business needs. You can:

• Update budget segments.
• Assign tree hierarchies to budget segments to control at a parent level.
• Create supplemental rules for exceptions to the control level.

Payables Payment Consumes the Cash Control Budget

When cash controls are enabled for Payables Payment Consumes the Cash Budget:

• The payment date is the budget date.

• The invoice distribution combination and the bank’s cash account are used to determine the budget account.   The invoice distribution combination is used for all segments except natural account which is replaced by the cash account on the bank account that the payment is made.

• The amount reserved in the cash control budget is the amount for each payment’s invoice distribution. When an invoice is partially paid the amount is derived by prorating the amount paid for the invoice in the ratio of distribution amount and total invoice amount.

Example:

Two invoices are paid through a single payment. The first invoice is for $100 USD and has two distributions, the second invoice is for $200 USD and has only one distribution. The first invoice is partially paid for $80 USD and the second invoice is fully paid. Following table details the amount as well as the account considered for each invoice distribution during funds reservation in cash budget.

Bank account cash account is 01-000-8111

Invoice		Distribution			Reserved Amount	Budget Account
Number	Amount	Number	Account	Amount
INV-001	100	1	01-111-5310	60	48	01-111-8111
INV-001	100	2	01-121-6420	40	32	01-121-8111
INV-002	200	1	01-131-7530	200	200	01-131-8111

• Accounting created for these payments will no longer be budgetary controlled in General Ledger because payments created from a payment process request are budgetary controlled in the Payables subledger. Assign your bank account’s cash account in the Edit Budgetary Control page, Accounts in Journals Subject to Cash Controls region. 

Payment features not yet supported for cash controls in the Payables subledger will be consumed against the cash control budget when the journals for these unsupported payments are reserved in General Ledger:

• Quick payments
• Manual payments
• Supplier refunds
• Pay in full
• Reissue

Budgets Entry for Cash Control Budgets

• You can load initial or adjusted budget amounts in the cash control budget using any of the Budgetary Control budget entry methods.

• When Budget Entry Classification for Initial or Adjustment Budget Balance using Spreadsheet and Budget Transfer feature is Opted in, you can choose if the budget entry impacts the initial or adjustment budget balance.

• If you have not enabled this feature, budget entries impact the budget adjustment balances because the budget period for cash controls budgets are automatically opened.

• For budget accounts that you want a control level other than absolute, create supplemental rules for these exceptions. If control level is none for budget entry business function, budget balances aren’t updated.

Budget Entry Classification for Initial or Adjustment Budget Balance Using Spreadsheet and Budget Transfer Feature

• Starting in 23C, this feature will no longer require the Opt In to enable it and you will determine whether your budget entries should update initial budget or adjusted budget amounts by specifying the classification of budget entries.

• We recommend implementing this feature in your next fiscal year budget preparation cycle to ensure all budget entries are categorized consistently. However, don’t enable the feature on the Opt In page until you’re ready to load the budget entries for the new fiscal year budget.

Segment Value Security

• If segment value security is configured, ensure all users that manage payments have access to the cash account. Budget accounts are dynamically created for payments in Budgetary Control and shown to the user in the View Funds Results page in Payments.

Key Resources

• Payment Process Requests in Using Payables Invoice to Pay
• Load Budgets in Using Financials for the Public Sector
• Revenue and Cash Controls in Using Financials for the Public Sector
• Overview of Multifund Accounting in Implementing Receivables Credit to Cash

Role And Privileges

• Budget manager role is needed to access the Manage Control Budget page.
• Accounts Payable Supervisor or Accounts Payable Payment Supervisor role is needed to create and manage payment process request payments.

General Ledger

Account Balances Search by Segment Value Description

This enables users to search using business friendly terms without having to remember numeric values. We are introducing an additional search criteria radio button to help you search by the segment value description when inquiring on account balances in the Inquire on Detail Balances page. This option is utilized by clicking a radio button with the field "Search by Description", selecting the "Search by Description" radio button and entering the segment value description in the segment text field. Finally click on the search button.

The business benefits of this feature are:

• Increased efficiency by allowing you to find desired segments more quickly.

Steps to Enable

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

Tips And Considerations

Three radio buttons are present as options for searching. The first two options "Starts with" and "Equal to" only search the segment value, while "Search by Description" only searches the "Description" field.

Key Resources

• For more information, refer to the Using General Ledger guide in the Oracle Help Center.

Role And Privileges

Users with access to this inquiry page can use this feature.

Efficiency Improvements for General Ledger Posting Processes

The following General Ledger processes can now be run in parallel: AutoPost Journals, Manual Posting of Journals, and AutoReverse Journals. In addition, users can also run many instances of the AutoPost Journals process at the same time.

This allows for operational improvements and results in increased throughput because these processes do not need to wait for each other to complete.

Steps to Enable

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

Role And Privileges

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

Joint Venture Management

Consistent Use of Project Attributes Across Joint Venture Management

Consistently display project attributes across the Joint Venture Management module. Display Project Number, Project Name, Task Number, Task Name, Expenditure Type, and Expenditure Description across all applications and reports.

This ensures clarity and a consistent user experience across the Joint Venture Management processes.

Steps to Enable

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

Key Resources

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

Role And Privileges

• Joint Venture Accountant
• Joint Venture Accounting Manager

Descriptive Flexfields Configuration for Joint Venture Management

Configure descriptive flexfields to add additional fields beyond what is provided in the Joint Venture Management work areas.

You can configure descriptive flexfields for the following work areas:

• Joint Ventures
• Stakeholders

This helps customers track and report on additional information unique to their organizations.

Steps to Enable

To configure descriptive flexfields for Joint Venture Management, log in as a user with the joint venture application administrator role (ORA_JV_JOINT_VENTURE_APPLICATION_ADMINISTRATOR_JOB) and complete the following tasks to configure descriptive flexfields for Joint Venture Management:

1. Configure the profile option to enable descriptive flexfields in the Joint Ventures and Stakeholders work areas.
   1. Navigate to Setup and Maintenance and select the Joint Venture Management functional area under the Financials offering.
   2. Make sure that you’ve selected to show All Tasks, and then click the Manage Joint Venture Profile Options task.
   3. On Manage Joint Venture Profile Options, in the Profile Option Code field, enter ORA_JV_ENABLE_DFF_DISPLAY and click Search. The system displays the Enable Joint Venture Descriptive Flexfields Display profile option, which is used to enable descriptive flexfields for Joint Venture Management.
   4. In the Profile Values section, click Add.
   5. In the first row:
      1. Select Site for the Profile Level.
      2. Select Yes for the Profile Value.
   6. Click Save.
2. Set up descriptive flexfields for Joint Venture Management
   1. Navigate to Setup and Maintenance.
   2. On the Setup page, open the Tasks panel on the right and search for Manage Descriptive Flexfields.
   3. In the Manage Descriptive Flexfields page, select the module Joint Venture Management and click search.

4. Add the descriptive flexfields for your business to make them visible on the Joint Venture and Stakeholder work areas.

Tips And Considerations

Configuring descriptive flexfields involves managing the available flexfields registered with your Oracle Applications Cloud database and configuring their flexfield-level properties, defining and managing descriptive flexfield contexts, and configuring global and context-sensitive segments.

Use a global segment to configure descriptive flexfields that are always available as fields in a work area. Use a context segment to configure fields that provide the context on whether associated context-sensitive fields appear in a work area.

In general, configuring descriptive flexfields involves:

1. Creating segment labels for business intelligence enabled flexfields.
2. Configuring global segments by providing identity information, the initial default value, and the display properties.
3. Configuring the context segment by specifying the prompt, whether the context segment should be displayed, and whether a value is required.
4. Configuring contexts by specifying a context code, description, and name for each context value, and adding its context-sensitive segments, each of which is configured to include identifying information, the column assignment, the initial default value, and the display properties.

Key Resources

• Watch Descriptive Flexfields Configuration for Joint Venture Management Readiness Training

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

Role And Privileges

• Joint Venture Application Administrator
• Joint Venture Accountant
• Joint Venture Accounting Manager

Designation of Distributable Accounts As Distribution Only

Designate accounts for a joint venture as Distribution Only for transactions that aren’t directly related to costs or revenue. Distribution only accounts are processed but not invoiced. Joint Venture Accounts Sets provide an easy and flexible method for specifying the accounts by using filter criteria to support single accounts, ranges of accounts, and the exclusion of accounts.

This option facilitates invoicing and financial reporting and reduces maintenance activities.

Steps to Enable

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

Tips And Considerations

• An account set enables you to set up filter criteria on chart of account segment values that can be reused across joint ventures.

• Review your joint operating agreement (JOA) for specific account information and cross reference it with the accounts available in your financial system prior to creation of the Account Sets.

Key Resources

• Watch Joint Venture Account Sets Enhancements Readiness Training

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

Role And Privileges

• Joint Venture Application Administrator
• Joint Venture Accountant
• Joint Venture Accounting Manager

Display Projects Associated with the Joint Venture in Distributable Project Values

Configure a descriptive flexfield in Project Management to associate a joint venture to a project. Only those projects associated with the joint venture are listed while defining distributable project values in a joint venture definition and while selecting projects in ownership definition assignment rules.

This option improves efficiency when defining joint ventures and ownership definition assignment rules.

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

1. Opt in to Project Costing in Project Management.
2. Opt in to Project Capitalization and Progress Management in Joint Venture Management.
3. Activate profile option to enable the project descriptive flexfield association.
4. Set up a descriptive flexfield in Project Management.
5. Specify the descriptive flexfield in the Joint Venture System Options.
6. Associate joint ventures to projects in Project Management.
7. Set Up Joint Venture Management users with the privilege to view project values.

Tips And Considerations

This configuration is not required to use the features available in a Joint Venture Management integration with Project Management.

For a project to appear in the list of project values in Joint Venture Management, the business unit of the owning organization of the project must match the business unit of the joint venture.

Key Resources

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

Role And Privileges

• Joint Venture Application Administrator
• Joint Venture Accountant
• Joint Venture Accounting Manager

Joint Venture Account Sets to Identify Distributable Accounts

Rather than using distributable segment values, assign Joint Venture Account Sets to joint ventures to identify the accounts whose transactions will be distributed to the joint venture partners. Joint Venture Accounts Sets provide an easy and flexible method for specifying the accounts by using filter criteria to support single accounts, ranges of accounts, and the exclusion of accounts.  

Business Benefit:

• Using Joint Venture Account Sets in place of distributable segment values, which required users to specify each individual account separately, reduces the likelihood of user-introduced errors when identifying accounts.

• Account maintenance is reduced because the Joint Venture Account Set can be based on a range which would automatically include dynamically created accounts.

Steps to Enable

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

Tips And Considerations

An account set enables you to set up filter criteria on chart of account segment values that can be reused across joint ventures.

Review your joint operating agreement (JOA) for specific account information and cross reference it with the accounts available in your financial system prior to creation of the Account Sets.

Key Resources

• Watch Joint Venture Account Sets Enhancements Readiness Training

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

Role And Privileges

• Joint Venture Application Administrator
• Joint Venture Accountant
• Joint Venture Accounting Manager

Joint Venture Management Overhead Method – Rate Based on Operational Measure

Provide an additional overhead method where the calculation is based upon a rate applied to operational measures. This method provides the ability to calculate overhead based upon operational measures recorded for a specific period, the beginning of the year through a specific period, or the inception of the joint venture through a specific period.

This new method ensures compliance to the joint operating agreement by ensuring accurate calculation and distribution of overhead costs.

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

1. Opt in to Joint Venture Overhead in Joint Venture Management.
2. Access the task Manage Joint Venture Overhead Methods under the functional area Joint Venture Management.
3. Create the overhead method with the following values for the attributes:

• Type - Rate based
• Basis Source - Operational measures
• Click “Select Measure Types” and then select the operational measure types to be used in the overhead calculation
• Save the overhead method

Tips And Considerations

In an overhead method, you must specify the partner account before the method can be activated. This partner account is used while creating the Receivables invoice to recoup the overhead costs from partners. Before you define the partner account on the overhead method, ensure that the GL Code Combination for the partner account has been defined using Manage Account Combinations.

Key Resources

• Watch Joint Venture Overhead Readiness Training.

• Watch Joint Venture Overhead Enhancements Readiness Training.

• Watch Joint Venture Management Overhead Method – Rate Based on Operational Measure Readiness Training.

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

Role And Privileges

• Joint Venture Application Administrator
• Joint Venture Accountant

Payables and Expenses

Expenses

Expense Allocation Line-Level Split with Multiple Selections

Allocate specific percentages or amounts to a project or expense account at line level during expense report entry. The application allows for selecting one or more lines to specify split allocations applicable to the selection made. You can create multiple such selections with varying split allocations inside the report.

To access the Split Allocation window, select the lines you want in the expense report and click the Split Allocation button. Select individual lines in the report and click the button to enter project or account allocations for these lines.

The line level split allows employees to apply allocations to specific lines of an expense report. This is useful to split the selected lines in the expense report and appropriate the expenditure between projects or accounts accurately at the line detail. 

The ability to split allocations across different line selections made is useful to segment the expenditure into various account and projects within the same report.

Steps to Enable

To enable splitting expenses in expense entry, perform the following steps:

• From the Setup and Maintenance work area, navigate to the Manage Expenses System Options page.
• Set the Enable Split Allocations option on the Manage Expenses System Options page to Yes at the specific business unit level or at the site level.

Key Resources

• This feature originated from the Idea Labs on Oracle Customer Connect:  https://community.oracle.com/customerconnect/discussion/593954/system-should-allow-user-to-split-the-allocation-at-expense-item-level.

Role And Privileges

There is no need for a new role.

Expense Item Creation from Receipts Emailed from Personal Email Address

Allow employees to send expense receipts from personal email addresses to create expenses. This enables the Expenses application to recognize receipts forwarded from personal addresses as valid expenses and create these expenses automatically.

A personal email address is defined as an employee's email of type 'Home' in HCM. On successful creation of an expense, an email confirmation with the expense details is sent. Email notifications are also sent if the expenses cannot be processed or created. The application automatically submits successfully created expenses for approval when auto-submission is enabled.

Expense Creation Email Confirmation

This feature makes submitting expenses using email receipts both easier and faster because employees can now send receipts from both their work and personal email addresses. Employees no longer need to worry about ensuring that their receipts are sent to their work email addresses or spend extra time forwarding their receipts to their work email addresses.

Steps to Enable

To enable this feature, perform the following steps:

1. Sign in as the Application Implementation Consultant.
2. From the Setup and Maintenance work area, navigate to the Manage Auto Submit and Matching Options page.
3. Under Electronic Receipt Setup, set Allow Expense Creation from Personal Emails to Yes.

You can set this option for all business units or specific business units as needed.

Electronic Receipt Setup

Role And Privileges

To enable this feature, you need to have the role of Application Implementation Consultant.

MasterCard Adjustment Code Exclusion

Exclude specific adjustment codes that indicate payments from MasterCard transaction files. This will help prevent overpayment to card issuers.

Use the ORA_EXM_MC_EXCLUDE_ADJUSTMENTS lookup type to define the specific adjustment codes that should be excluded when processing credit card transaction files from MasterCard. The Upload Corporate Card Transactions process excludes all adjustment transactions that match the adjustment codes when lookup codes are present under the ORA_EXM_MC_EXCLUDE_ADJUSTMENTS lookup type.

If you don't specify any adjustment codes in the ORA_EXM_MC_EXCLUDE_ADJUSTMENTS lookup type, then the upload process automatically excludes all payment adjustment transactions.

Following are the benefits of using this feature:

• Control which adjustment codes to exclude from loading to Expenses.
• Exercise greater control over which credit card adjustment transactions employees can create expenses and claim reimbursement.
• Prevent double payment of expenses when an employee has already made a direct payment to MasterCard.

Steps to Enable

To specify the adjustment codes to exclude from the Upload Corporate Card Transactions process for MasterCard, complete these steps:

1. Sign in as the Application Implementation Consultant.
2. From the Setup and Maintenance work area, navigate to the Manage Standard Lookups task.
3. Search for the ORA_EXM_MC_EXCLUDE_ADJUSTMENTS lookup type.
4. In the Lookup Codes section of the page, add the adjustment reason codes that you want to exclude from upload.

Define Lookup Codes in the ORA_EXM_MC_EXCLUDE_ADJUSTMENTS Lookup Type

In the above example, adjustment transactions with adjustment reason codes 0160, 0440 will be excluded from loading to Expenses. All other adjustment transactions will be loaded to Expenses and employees can add them to their expense reports.

Tips And Considerations

Assign lookup codes to the ORA_EXM_MC_EXCLUDE_ADJUSTMENTS lookup type to exclude specific adjustment codes only during upload of MasterCard transaction files. Otherwise, if lookup codes are not defined, the upload process excludes all payment adjustment codes.

Key Resources

For additional details on uploading corporate card transactions from card issuers refer to the following topics in Expenses Implementation Guide:

• Travel Card Processing 
• Upload MasterCard Corporate Card Transaction Files

Role And Privileges

To use this feature, you need one of these roles:

• Financial Application Administrator
• Application Implementation Consultant

Notification and Expense Report Enhancements for Manually Applied Cash Advances

View cash advance details in the expense report reimbursement notifications where cash advances are manually applied against expense reports. Additionally, view the details of the manually applied cash advances in the View Expense Reports page as well as in the Printable Expense Report page.

This feature is an enhancement to the Manual Application of Cash Advances to Expenses feature released in update 22B. You can refer to the What's new details of the 22B feature here.

The Manual Application of Cash Advances to Expenses feature introduced in 22B allowed employees to manually apply cash advances to expenses during expense report submission. In update 22C, you can view the details of the manually applied cash advances in the expense report reimbursement notifications.

Expense Reimbursement Notification

The Report Total section of the expense report now shows the total cash advance amount applied to the report.

Cash Advances Applied Displayed in the Report Total Section of the View Expense Report Page

Additionally, the details of the manually applied cash advances are now available in the printed expense report page.

Cash Advances Section in the Printable Expense Report Page

If approvers or auditors reject expense reports or if employees withdraw any reports, then the cash advances that are applied to the reports are automatically removed and returned to the employee’s available cash advances. If expense amounts are adjusted during expense report audit and applied cash advances exceed the reimbursement due to employee, then the difference is added back to employee’s available cash advances. The available cash advance amounts and the statuses are updated accordingly on the Cash Advances work area. The adjustment and rejection notifications identify any changes to the applied cash advances. These changes were made available in release 22B. In 22C, in addition to these, the employees will see an info banner which informs them of these changes when they open the affected report for the first time after it was returned, short paid or adjusted, or when employee withdraws the report.

Info Banner Informing the Employee That the Cash Advances Were Removed Because the Report Was Returned

These enhancements improve the usability of the manual application of cash advances. Employees have better visibility into the cash advance amounts that were manually applied by them and can easily track the amounts that are owed to them.

Steps to Enable

You must enable manual application of cash advances to view these enhancements. Refer to Steps to Enable in 22B What's New - Manual Application of Cash Advances to Expenses.

Key Resources

• Refer to the feature details in Expenses Implementation Guide and Expenses User Guide to understand how to set up manual application of cash advances and how to apply the cash advances manually to expense reports.

Role And Privileges

To enable manual application of cash advances, you need one of these roles:

• Expense Manager
• Application Implementation Consultant

Prepaid Expense Entry

Allow employees to enter prepaid expenses in expense reports. Create prepaid expenses using the Expenses REST service. Prepaid expenses are travel expenses that a company reimburses directly to a vendor before or after an employee enters them in an expense report. Entering these expenses in expense reports allows companies to accurately allocate these expenses.

When an expense type is enabled for prepaid expenses, the Create Expense page displays the 'This is a prepaid expense' checkbox. When the employee selects this checkbox to indicate that the expense is prepaid, the reimbursable amount is updated to 0, indicating that the employee is not reimbursed for the expense.

Prepaid expenses can also be created using Expenses REST APIs - Create an expense record, Update an expense record. If PrepaidFlag parameter is set to 'Y' in the expense payload, the expense is marked as prepaid.

Expense Marked As Prepaid

In an expense report, the prepaid expense is tagged in the report summary page and the prepaid amount is listed separately under the Report Total section for easy identification. The prepaid expense is excluded from the amount reimbursable to the employee to provide accurate reimbursement information.

Prepaid expenses in expense report

Approvers can also view the prepaid expenses tag in the approval notification when reviewing the expense reports for approval. This helps them view the total cost of the employee's travel or business expenses.

Approval notification

Auditors will see the reimbursable amount as 0 for prepaid expenses on the Audit Expense Report page. They can review the expense details but they can't modify the prepaid flag that's set by the employee. Auditors also can't short pay or adjust prepaid expenses as these are expenses that are already paid.

When the Process Expense Reimbursements process is run, prepaid expenses are not passed to Payables as employees are not reimbursed for these expenses and they have no financial implications. Accounting distributions for these expenses are not passed to Payables as the expenses were prepaid, with the assumption that the distributions were captured as part of the original payments.

Prepaid expenses help approvers and auditors view the total cost of an employee's travel expenses or business expenses. By adding prepaid expenses to their expense reports, employees can help companies track the expenses that were paid by the company directly to the vendors or merchants.

Steps to Enable

To enable prepaid expenses, perform the following steps:

1. Navigate to Setup and Maintenance work area > Financials offering.
2. Select the Expenses functional area and go to the Manage Expense Report Templates task.
3. Select the template you want to modify.
4. In the Edit Expense Report Template page, search and select the expense type for which you want to allow prepaid expenses.
5. Select 'Allow prepaid expense items' on the Edit Expense Type page.
6. Click Save or Save and Close. 
7. Repeat steps 3-6 for each expense type you want to enable for prepaid expenses.

Allow Prepaid Expenses for the Expense Type

Tips And Considerations

• Prepaid expenses can't be enabled for Itemization Only expense types.
• Employees can mark only cash expenses as prepaid expenses.
• Employees can't mark itemized lines as prepaid expenses. They can only mark parent expenses as prepaids when itemization is enabled.
• Prepaid expenses can't be marked as personal expenses or vice versa.

Key Resources

• This feature originated from the Idea Labs on Oracle Customer Connect: https://community.oracle.com/customerconnect/discussion/comment/592598

Role And Privileges

To enable prepaid expenses, you need one of these roles:

• Expense Manager
• Application Implementation Consultant

Reimbursable Currencies in Expense Reports by Business Unit

Configure reimbursable currencies available for selection in expense reports by business unit based on local and regional regulations. This allows companies to limit the reimbursable currencies available for selection in expense reports and reduce errors.

You can set up the allowed currencies by navigating to User Options for Expense Report for a particular business unit from the system task Manage Expenses System Options.

Set the Allow Reimbursement Selection dropdown to Yes to enable the Allowed currencies list for selecting and configuring currencies in the business unit.

The ability to configure the allowed currencies by business units lets companies ensure that the reimbursement is in accordance with the business unit's geo regulations applicable to the claimable currencies. This improves compliance with local regulations by only allowing the selected available currencies to be used in reports.

Steps to Enable

To enable this feature, perform the following steps:

1. In the Manage Expenses System Options page, select a business unit to edit the system options for this business unit.
2. Navigate to the User Options for Expense Reports region and set the Allow Reimbursement Selection dropdown to Yes. This will enable the Allowed currencies dropdown list for selecting and configuring currencies for the business unit.

Key Resources

• This feature originated from the Idea Labs on Oracle Customer Connect: https://community.oracle.com/customerconnect/discussion/559506/limit-selection-of-reimbursement-currencies-in-expense-report-header-per-bu

Role And Privileges

There is no need for a new role.

Tax Recoverability Determination for Expense Payment Requests

Determine the tax recoverability of payment requests based on the expense type, expense location and employee legal entity location. This provides additional flexibility in managing tax recoverability of expenses without the need to use multiple expense types.

Currently, the Tax Classification Code associated with the expense type is the only attribute used for tax recoverability determination. With this feature, tax product categories also can be associated with the expense types in the expense report template setup which helps in tax recoverability determination. When a tax product category is associated to an expense type, the related tax determining factors are passed to Payables from Expenses when the payment requests are created for expense reports: tax product category assigned to the expense type, tax classification code when applicable, expense location, and employee legal entity location.

Payables passes these tax determining factors to Oracle Tax for tax and recovery determination. Oracle Tax uses one or more of these tax determining factors, based on the tax rules configured, to determine the recoverability for each expense line. 

Oracle Tax enables the setup of tax product categories using the Manage Product-Based Fiscal Classifications page. Oracle Tax enables the configuration of rules for payment requests- such as Tax Applicability, Tax Rate and Tax Recovery rules based on product categories, expense locations, legal entity location, and tax classification codes.

The tax determining factors that may be used in tax rules are:

1. Expense Location: Expenses of the same type can be incurred in multiple locations. However, different locations may attract different tax rates for the same expense type. Capturing the location where the expense was incurred could be critical in determining the taxability and tax recovery. Location of an expense item corresponds to a geography in the Manage Geographies page. 
2. Tax Product Category: Tax product category is a tax determinant that indicates the taxable nature of an item or service purchased or sold. It can be used to create tax rules and exceptions in Oracle Tax. By associating each taxable expense type to a tax product category, this determinant can now be used in recovery determination rules for expense reports.
3. Employee Location: Depending on the employee’s primary location, the tax on an expense report may or may not be recoverable. This determining factor can be used to simplify the rules for tax recoverability. Employee location is the address of the main legal reporting unit associated with the employee's legal entity. 
4. Tax Classification Code: Tax classification code can be used as one of the determinants for tax applicability, tax recovery rate determination and other tax rules. If configured on the expense type, the tax classification code will continue to be passed to Payables. 

This feature enables determination of tax recoverability based on additional expense details, such as tax product category, employee legal entity location and expense location. The new attributes supported by Tax allows customers to reduce expense type setup and comply with the local tax regulations effectively.

Using this feature, customers can eliminate the need to enter or override the Tax Classification Code by employees. This simplifies expense entry for employees.

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 23A

Enable the Feature Opt In

This feature is controlled by the FSM opt in 'Tax Recoverability Determination for Expense Payment Requests'. To enable the opt in:

1. Navigate to the Setup and Maintenance work area.
2. Select the Financials offering.
3. Click Change Feature Opt In.
4. On the Opt In: Financials page, click the Features icon for Expenses.
5. Enable "Tax Recoverability Determination for Expense Payment Requests" feature opt in.
6. Click Done.

FSM Opt In for the Feature

Expenses Setup for the Feature

After enabling the opt in perform the following steps to configure a tax product category for an expense type:

1. Navigate back to Setup and Maintenance work area > Financials offering.
2. Select Expenses functional area and go to Manage Expense Report Templates task.
3. Select the template you want to modify and open the expense type setup page.
4. Search and select a tax product category value you want to assign to the expense type.
5. After selecting a tax product category value, navigate to Expense Fields tab and set Expense Location field to Required if it's not already set to Required.
6. Click Save or Save and Close.

This associates a tax product category to the expense type. Tax product category is not displayed to employees on the Create Expense page when creating expenses. The application assigns the tax product category to each expense and this information together with other tax determining factors is passed from Expenses to Payables when the Process Expense Reimbursements process creates payment requests in Payables.

Select Tax Product Category for an Expense Type

Tax setup for the feature

Configure Product Category in Tax Setup:

1. You must specifically configure a L-1 node/ Parent Fiscal Classification Codes for Expense Tax Product Category and should create it as a Tax Lookup Code under the predefined lookup type: ORA_ZX_EXM_PRODUCT_CATEGORY. This ensures that only the product categories that are configured for Expenses would show up in the Tax Product Category dropdown on the Expense Type setup page. On the Expense Type setup page, you will be able to view and select only fiscal codes that are NOT country specific, i.e. no country code is specified while defining the fiscal code. 
2. Tax Product Category dropdown on the Expense Type setup page will pick up the child nodes under this parent node of Fiscal Classification Code. You must define the tax product categories required for the expense type setup under this parent node of Product Category.

Set Up Configuration Owner Tax Options (COTO):

1. Based on the Expenses FSM opt in, the allowed values for the Regime Determination Set field in the Manage Configuration Owner Tax Options page for 'Employee Expense Report' will change. If the opt in is enabled, the dropdown will display 2 values: STCC and TAXREGIME. If the FSM opt in is disabled, STCC will be defaulted and cannot be updated (this is the current behavior).
2. When the Expenses FSM opt in is enabled, the Regime Determination set in COTO will continue to default to STCC.
3. If a COTO record is not defined for a Business Unit (BU), Oracle Tax uses STCC as the Regime Determination Set for that BU.
4. If you select Regime determination set as TAXREGIME for a COTO you setup for a BU, you will need to define the Tax Rules and defaults necessary for Tax calculation and Recovery determination. Tax Rules for payment requests can be defined based on the tax determining factors that Expenses will pass to Payables for expense reports.
5. Once TAXREGIME is selected and saved for a BU in COTO for Employee Expense Reports, the Expenses FSM opt in will be frozen and will become a read-only value. You will not be able to disable the FSM opt in once COTO is selected with TAXREGIME for Employee Expense Report.

Note that you can still set up Recovery Rate Determination rules for expense reports irrespective of the setting for Regime Determination Set for a BU.

STCC and TAXREGIME in Regime Determination Set for Employee Expense Report Event Class

Configure Tax Rules:

While defining Tax Rules in Oracle Tax, the types of location are specified by a “Tax Qualifier” as shown in the screenshot below.

Tax Qualifiers

The Tax Product Category, Employee Location and Expense Location fields which are passed to Payables from Expenses are available for use in defining tax rules as existing tax determining factors in Oracle Tax as shown in the table below.

Expense Attributes to Tax Qualifiers Mapping

Expenses Attributes	Tax Determining Factors - Determining Factor Class	Tax Determining Factors - Tax Class Qualifier	Tax Determining Factors - Determining Factor Name
Expense Location	Geography	Ship To	Country, State, City, Province, etc.
Employee Location	Geography	First Party Tax Registration Number	Country, State, City, Province, etc.
Tax Product Category	Product Non-inventory linked		Product Category

Note that this mapping applies only if the tax rule is created for the event class of “Employee Expense Report” as shown in the screenshot below. The screenshot shown is for a Recovery Rate rule, but the same behavior holds for other types of rules such as Tax Applicability rules.

Event Class - Employee Expense Report

Consider a tax rule condition set for a recovery rate determination rule for the event class of “Employee Expense Report” as shown in the table below.

Determining Factor Class	Tax Class Qualifier	Determining Factor Name	Operator	Value	Description
Geography	Ship To	Country	Equal To	GB	Great Britain
Geography	First Party Tax Registration Number	Country	Equal To	GB	Great Britain
Product Non-inventory linked		Product Category	Equal To	14111514	Paper pads or notebooks

During the recovery rate determination process for a payment request, Oracle Tax would use the values from the Expense Location, Employee Location and Tax Product Category fields passed into Payables to compare against the values as shown in the table. If the values match, then Oracle Tax would use the recovery rate applied for this condition set. Else, it would proceed to the next condition till a match is found. If no match is found, Oracle Tax would use the default recovery rate.

Tips And Considerations

• The tax product category start date must be before the expense type start date for the values to populate in the Tax Product Category dropdown on the Expense Type setup page.

• For creating the tax rules based on these additional attributes, implementers must configure the tax rules under the event Class - Employee Expense Report.

• This enhancement does not impact any of your existing tax configurations. You can continue to use STCC for tax calculation. However, you can optionally use these additional attributes to determine tax recoverability as per your business needs. 

• This feature is presently available through the FSM opt in as described above. The new Tax Product Category field on Expense Type setup page will be available only if the feature opt in is enabled. Once the opt in expires, the Tax Product Category field will always be available.

• Once FSM opt in is enabled and TAXREGIME is set as COTO for event class Employee Expense Report, the opt in becomes a read-only field and you cannot disable it anymore.

Key Resources

• The product category list in the Oracle Tax setup populates the values for the Tax Product Category dropdown in Expense Type setup. For more information on product category see the Product Category Fiscal Classifications topic under Manage Product-Based Fiscal Classifications in the Implementing Tax Guide.

• For more details on COTO refer to Manage Configuration Owner Tax Options topic in Implementing Tax Guide.

Role And Privileges

To use this feature, you need one of these roles:

• Financial Application Administrator
• Application Implementation Consultant
• Tax Administrator/Expense Manager

Payables

Form 1099-MISC and Form 1099-NEC for Tax Year 2022

Generate Form 1099-MISC and Form 1099-NEC for Tax Year 2022 according to the new layout published by the US Internal Revenue Service (IRS). The following changes are made for tax year 2022:

• Continuous use forms

Both forms are now designed for continuous use, instead of annual revision. IRS will update the forms and instructions as needed. The calendar year is printed on the forms automatically based on the year for which the report is generated.

• Change in box numbers and positions in Form 1099-MISC

Box number 13 in Form 1099-MISC is assigned to the Foreign Account Tax Compliance Act (FATCA) filing requirement checkbox. As a result, the box numbers 13 through 17 are now renumbered as box numbers 14 through 18, respectively.

Form 1099-MISC Changes

Form 1099-NEC Changes

The revised Form 1099-MISC and Form 1099-NEC are now compliant with the specifications published by IRS.

Steps to Enable

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

Tips And Considerations

The specifications for electronic filing for Form 1099-MISC and 1099-NEC are yet to be published by IRS for the year 2022. Any updates to electronic filing will be delivered after the specifications are released.

Simplified Activation of Intelligent Document Recognition

Activate and view the activation status of Intelligent Document Recognition using the Manage Intelligent Document Recognition Options task. 

You can see the activation status in the Status attribute on the Manage Intelligent Document Recognition Options page. When Intelligent Document Recognition isn't yet activated, the Save and Save and Close buttons on the page are displayed as Activate and Activate and Close buttons respectively.  Administrators can use these buttons to activate Intelligent Document Recognition. After successful activation, the status changes to Active.

Manage Intelligent Document Recognition Options

Administrators can use the Status attribute to easily identify if Intelligent Document Recognition is activated. Prior to this feature, there was no indicator on the Manage Intelligent Document Recognition page to display the activation status.

Steps to Enable

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

Key Resources

• For additional details, refer to Features, Recommendations, Guidelines, and Tips for Oracle Intelligent Document Recognition for Payables Invoices (Doc ID 2656229.1) on My Oracle Support.

Payments

Budgetary Control Invoice Payments for Cash Budgets in Manage Payment Process Requests

Provide Budgetary Control validation in Payment Process Requests. This validation allows payment of invoices only when funds are available in the cash control budget.

Prevent Invoice Payments When There Are Insufficient Funds

Budgetary control validation has been added to payment processing requests. Invoices are paid only when there are available funds in the cash control budget. Budgetary control validation failures are displayed on the Resolve Payment Validation Errors page. You can review the budgetary control validation failure, correct the failure or remove the payment, and resubmit the payment process request.

Resolve Payment Validation Errors

See details of the budgetary control validation failure by clicking on the funds status to open the View Funds Results page.  On the Resolve Payment Validation Errors page, click the View Payment icon to open the Payment page.

Payment Fails Due to Insufficient Funds

Completed payments are reserved and reduce the funds available for the cash control budget.  If a payment or payment file is voided, funds will be added back to the cash control budget.

Funding the Cash Control Budget

The cash control budget can also be impacted by journal entries. When the cash accounts defined in the Edit Budgetary Control page, Accounts in Journals Subject to Cash Controls region are present in a journal, it will impact the cash control budget balances.

Edit Budgetary Control

Journals that debit the assigned accounts will increase the cash control budget balance as a negative expenditure when journals budgetary controlled and reserved in General Ledger.

Steps to Enable

Budgetary Control Setup

Enable cash controls on the Manage Budgetary Control and Encumbrance page. When you enable cash controls for a ledger a cash control budget is automatically created.

See the video for details on setup.

Subledger Setup

To budgetary control the correct cash distribution in General Ledger, enable these options:

• Multifund accounting in Receivables.
• Automatic offsets on the Manage Common Options for Payables and Procurement page.
• Pooled account for the bank account on the Edit Bank Account page.

Tips And Considerations

Cash Control Budget

A generic cash control budget is automatically created when you enable cash controls.  This control budget is not automatically put in use so you can modify it to meet your business needs. You can:

• Update budget segments.
• Assign tree hierarchies to budget segments to control at a parent level.
• Create supplemental rules for exceptions to the control level.

Payables Payment Consumes the Cash Control Budget

When cash controls are enabled for Payables Payment Consumes the Cash Budget:

• The payment date is the budget date.

• The invoice distribution combination and the bank’s cash account are used to determine the budget account.   The invoice distribution combination is used for all segments except natural account which is replaced by the cash account on the bank account that the payment is made.

• The amount reserved in the cash control budget is the amount for each payment’s invoice distribution. When an invoice is partially paid the amount is derived by prorating the amount paid for the invoice in the ratio of distribution amount and total invoice amount.

Example:

Two invoices are paid through a single payment. The first invoice is for $100 USD and has two distributions, the second invoice is for $200 USD and has only one distribution. The first invoice is partially paid for $80 USD and the second invoice is fully paid. Following table details the amount as well as the account considered for each invoice distribution during funds reservation in cash budget.

Bank account cash account is 01-000-8111

Invoice		Distribution			Reserved Amount	Budget Account
Number	Amount	Number	Account	Amount
INV-001	100	1	01-111-5310	60	48	01-111-8111
INV-001	100	2	01-121-6420	40	32	01-121-8111
INV-002	200	1	01-131-7530	200	200	01-131-8111

• Accounting created for these payments will no longer be budgetary controlled in General Ledger because payments created from a payment process request are budgetary controlled in the Payables subledger. Assign your bank account’s cash account in the Edit Budgetary Control page, Accounts in Journals Subject to Cash Controls region. 

Payment features not yet supported for cash controls in the Payables subledger will be consumed against the cash control budget when the journals for these unsupported payments are reserved in General Ledger:

• Quick payments
• Manual payments
• Supplier refunds
• Pay in full
• Reissue

Budgets Entry for Cash Control Budgets

• You can load initial or adjusted budget amounts in the cash control budget using any of the Budgetary Control budget entry methods.

• When Budget Entry Classification for Initial or Adjustment Budget Balance using Spreadsheet and Budget Transfer feature is Opted in, you can choose if the budget entry impacts the initial or adjustment budget balance.

• If you have not enabled this feature, budget entries impact the budget adjustment balances because the budget period for cash controls budgets are automatically opened.

• For budget accounts that you want a control level other than absolute, create supplemental rules for these exceptions. If control level is none for budget entry business function, budget balances aren’t updated.

Budget Entry Classification for Initial or Adjustment Budget Balance Using Spreadsheet and Budget Transfer Feature

• Starting in 23C, this feature will no longer require the Opt In to enable it and you will determine whether your budget entries should update initial budget or adjusted budget amounts by specifying the classification of budget entries.

• We recommend implementing this feature in your next fiscal year budget preparation cycle to ensure all budget entries are categorized consistently. However, don’t enable the feature on the Opt In page until you’re ready to load the budget entries for the new fiscal year budget.

Segment Value Security

• If segment value security is configured, ensure all users that manage payments have access to the cash account. Budget accounts are dynamically created for payments in Budgetary Control and shown to the user in the View Funds Results page in Payments.

Key Resources

• Payment Process Requests in Using Payables Invoice to Pay
• Load Budgets in Using Financials for the Public Sector
• Revenue and Cash Controls in Using Financials for the Public Sector
• Overview of Multifund Accounting in Implementing Receivables Credit to Cash

Role And Privileges

• Budget manager role is needed to access the Manage Control Budget page.
• Accounts Payable Supervisor or Accounts Payable Payment Supervisor role is needed to create and manage payment process request payments.

Payment Approval Based on Payment Process Request Total Amount

Define payment approval workflow rules based on the total amount in a payment process request. Workflow administrators can route the payment process requests to multiple approvers based on the total amount in the payment process request.

This feature allows you to route all payment process requests to the treasury department if the request total payment amount exceeds the threshold limit, for example, a requirement to route all payments exceeding 100000.

Steps to Enable

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

Tips And Considerations

The following conditions must be satisfied to derive the payment process request total amount:

1. Require conversion rate entry check box and Conversion Rate Type are selected in Manage Payment Options page.
2. Payment process request should be submitted for a single ledger or multiple ledgers with the same primary ledger currency.
3. Payment approval rule configured based on payment process request total amount attribute.

If any of these conditions are not satisfied, then the payment process request total amount cannot be calculated and causes the approval process failure during the rules evaluation on total amount.

Workflow submitter will receive an error notification if approval process fails due to not satisfying any of the above conditions.

Receivables and Cash

Advanced Collections

Attachment Category Enhancement in Dispute Creation

Select from the complete list of attachment categories when adding attachments to a dispute against a customer transaction.

When creating a dispute against a transaction using the Manage Disputes page, the user can select from the complete set of attachment categories that is also available in the Edit Transaction and Review Transaction pages.

• The Create Dispute process now has access to all attachment categories associated with transactions, instead of only the one attachment category Customer Transaction.

• Financial managers can control which job roles (for example, Collection Manager) can perform which actions (read, edit, or delete) on attachments that belong to an attachment category (for example, dispute or collection).

Steps to Enable

Make the feature accessible by assigning or updating privileges and/or job roles. Details are provided in the Role section below.

Implementing attachment security is a simple two-step process. The first step is to Gather Attachment Security Policy and the second step is to Define Attachment Security

Step 1: Gather Attachment Security

You can create an unlimited number of attachment policies. Each policy needs to be named uniquely. Below is a helpful table to collect your policy definitions.

Srl #	Policy Name	Condition	Job Roles (Job Roles in scope for the policy)	Actions (Attachment Operations allowed for the policy)
1	Dispute Attachment Owner	DisputeAttach Dispute	Collection Manager	Read Update

Step 2: Define Security Policy

To define a data security policy for an attachment category:

1. Sign in with the predefined IT Security Manager role.

2. Go to Security Console.

3. On the General subtab of the Administration tab of the Security Console, click Manage Database Resources.

4. On the Manage Database Resources and Policies page, search for the Display Name equal to Application Attachment Category. The category appears in the search results, with an Object Name of FND_DOCUMENT_CATEGORIES

   The data security policies defined for the selected database resource appear in the Policies Details region.

5. In the Search Results region for the selected database resource, select Edit from the Actions menu.

6. On the Condition tab of the Edit Data Security page, select Create from the Actions menu.

7. In the Create Database Resource Condition dialog box, name the condition and specify the attachment categories in scope for the data security policy.

8. The following table suggests values for an example condition:

   Example For Defining Condition

   Field	Value
   Name	Dispute
   Display Name	Dispute
   Description	Dispute
   Condition Type	SQL predicate You can also specify the condition as a filter on a table or view.
   SQL Predicate	category_name in ('Dispute') The SQL predicate consists of a query on the table or view named by the database resource (in this example, FND_DOCUMENT_CATEGORIES). The category name specified in the predicate must exactly match the name that you specified when you created the attachment category.

9. Add policy and attach role for above condition.

   

   Policy Action

Role And Privileges

This has been explained in the Steps to Enable section in step 1.

Receivables

Portal Upload as a Delivery Method for Customer Transactions

Select the Portal Upload option as the preferred delivery method in a customer profile, instead of Print, Email or XML, for transactions uploaded to a supplier portal or external system. The transactions having Portal Upload as the preferred delivery method, will be excluded from delivering by the Print, Email and XML scheduled processes.

The Portal Upload option as a preferred delivery method is also supported by:

1. The Receivables Invoice REST API when updating the print attributes of transactions
2. The Customer Profile SOAP service when creating or updating a customer profile
3. File-Based Data Import (FBDI) for Customer Import for a customer profile.

You can also define more custom preferred delivery methods under Setup and Maintenance -> Manage Receivables Lookups -> AR_INV_DELIVERY_METHOD. By adding a new lookup code and enabling it, you will get a new custom preferred delivery method available at both account and site level of customer profile. Similar to Portal Upload, transactions having this new custom preferred delivery method, will be excluded from delivering by the Print, Email and XML scheduled processes.

This can increase the process efficiency of delivery of transactions to customers that make use of an external portal.

Steps to Enable

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

Tips And Considerations

• You need to set up the customer profile, and enable this delivery method, either at account level or site level to use it.

Asset and Lease Management

Lease Accounting

Lease Disclosure Summary Report

Use the Lease Disclosure Summary Report to summarize lease expenses, cash flows, future lease payments, weighted average items, and lease details. This report helps lease administrators and accountants create the lease disclosures for IFRS16 and ASC42 financial reporting.

The business benefits include:

• Simplify compliance with IFRS16/ASC842 disclosure report for year-end reporting.
• Reduce year end processes with a single report for IFRS16/ASC842 disclosures.

Steps to Enable

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

Role And Privileges

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

Lease Milestone Tracking

Capture and track important lease-related milestones. Many decisions and events need tracking throughout the lifecycle of the lease, such as providing documents, early termination options, renewal options, terminations, and more. Missing these events or decisions could have financial impacts by incurring penalties, paying additional costs, or missing incentives. The lease administrator can capture milestones for leases, assets, payments, and options. Each milestone has an associated date, notification date, and responsible users. Notifications are sent to the responsible user until the milestone is complete.

Milestone Tracking

Milestones on Lease Dashboard

The business benefits of Lease Milestone Tracking include:

• Improve communication of impending milestones.
• Maximize profits by meeting all milestones.

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 23A

Role And Privileges

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

Lease Rights and Obligations

Capture lease-related rights and obligations. There are many terms and conditions on a lease, and the lease administrator needs to know the rights and obligations. Rights are entitlements granted by the lessor to the lessee. Examples include the right to sub-lease, roof rights to install antennas or satellite dishes, and the right to put signage on the building. Obligations outline which party is responsible for performing or paying for specific services, costs, or duties. Examples of obligations include building security, parking, and maintenance.

Rights and Obligations

The business benefits of Lease Rights and Obligations include:

• Increase operational efficiency with quick access to contractual rights, entitlements, and obligations.

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 23A

Role And Privileges

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

Lease Termination Import

Use the Lease Termination Import utility to simplify end-of-lease activities such as exercising or canceling options and terminating leases. As leases move through their lifecycle and come to the end of the term, lessees need to make decisions related to each of these activities, and each one impacts the lease term, balances, and payments. The Lease Termination Import utility removes or reduces the need for manual intervention during the end-of-lease processes.

Manage Options and Termination Import

Business benefits include:

• Improve efficiency by performing multiple transactions through the Manage Options and Termination import.
• Reduce data entry effort with the import utility.
• Streamline business processes by populating the import from originating systems.

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 23A

Tips And Considerations

1. Terminate leases and assets, and exercise or cancel options through an FBDI spreadsheet template. This method is useful for large volumes of terminations or options to manage. Help text exists for each column to explain what to enter, what is required, and the field type.

2. The FBDI spreadsheet converts the data to a zip file for the File Import process. You then load the file to the lease interface table. The final step is to run the Import Lease process with the import type of Manage Options and Terminations. The Manage Options or Terminations imports the termination and option decision from the interface table to the Lease Accounting module. Terminations and option are visible in the Lease Accounting module after this process completes.

3. The Lease Dashboard includes exceptions or errors.

Key Resources

• To access the Lease Contract Manage Import FBDI template, please refer to LeaseContractManageTemplate.xlsm under https://docs.oracle.com/en/cloud/saas/financials/22c/oefbf/leasecontractmanageimport-3060.html#leasecontractmanageimport-3060

• This feature originated from the Idea Lab:
  • https://community.oracle.com/customerconnect/discussion/612430

Role And Privileges

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

Region and Country-Specific Features

Regional Shared Features

Generic SAF-T Assets Extract by Legal Entity

Use legal entity as a filtering parameter when generating the assets section of the generic SAF-T extract. This aligns the Asset section with other sections of the SAF-T extract to provide a complete legal entity view.

Provides flexibility and ease to extract asset information only by legal entity during a run of the Generate SAF-T data extract.

Steps to Enable

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

Tips And Considerations

In order for the Legal Entity to work as a filter for the extract, you need to assign a Balancing Segment Value to each Legal Entity you use. This is a common requirement for most ERP reports that use Legal Entity as a parameter.

Key Resources

• SAF-T Data Extract Topical Essay, here.

VAT Reporting Performance Improvements

Enhance the overall performance of VAT reporting with improvements to extraction and data processing.

This feature improves the performance and data processing of all the Select Transactions for Tax Reporting Process based reports and processes:

• Generate VAT Report for Israel
• Tax Allocation Process
• Tax Allocations Listing Report
• Tax Allocation Exceptions Report
• Tax Box Return Preparation Report
• Finalize Transactions for Tax Reporting
• Declarable Input VAT Register for Italy
• Declarable Output VAT Register for Italy
• VAT Liquidation Report for Italy
• Yearly Tax Report
• Input VAT Journal for Spain
• Output VAT Journal for Spain
• VAT Inter-EU Invoice Journal for Spain
• VAT Inter-EU Invoice Format for Spain
• Generate VAT Report for Israel
• Generate JPK VAT File for Poland
• VAT Reports for Russia

There is no change in the functional flow for the end user. You can submit the reports and the processes as you did earlier.

This enhancement reduces the processing time, and improves performance and data processing of all Select Transactions for Tax Reporting Process based reports and processes, when submitted multiple times per tax period.

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 23A

To enable this feature, follow these steps in the Feature Opt In:

1. Go to Setup and Maintenance > Setup > Financials > Change Feature Opt In.
2. Select Financials > Feature > VAT Reporting Performance Improvements.
3. Select Enable check box and save changes.

This feature is enabled by default starting from the 23A release.

To turn off the VAT Reporting Performance Improvements feature, enable the Lookup Type ORA_ZX_TRL_EXTRACT_DATA_SOURCE and Lookup Code  TRL_EXTRACT_ID_SOURCE_OPT_OUT.

Tips And Considerations

Before you use this feature, you must enable the opt in for VAT Reporting Performance Improvements.

Role And Privileges

No additional role is required.

Brazil

Control of Payment Terms and Installments on Brazilian Transactions Using a REST API

Use the Receivables REST API to update the installment due date and generate automatic bank occurrences on transactions associated with collection documents that were sent to the bank.

This feature is not available for installment updates on transactions associated with a consolidated collection document with multiple installments.

This feature allows user to bulk update installments due date and generate automatic bank occurrences if associated to a collection document sent to the bank.

Steps to Enable

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

Corporate Card Issuer Payments Using Collection Documents for Brazil

Process corporate card issuer payments using Brazilian collection documents. Collection documents, along with processing payments for regular suppliers, can also process payments for credit card issuers registered as parties in Cloud ERP.

The enhanced Create Collection Documents page allows selection of either a Supplier or a Party. The user can select a corporate card issuer party and the corresponding invoices interfaced from Expenses which are enabled for collection document processing.

The Import Payable Collection Document FBDI can also be used to import corporate card issuer collection documents sent by banks (Brazilian DDA file).

The Brazilian collection document pages and the Import Payable Collection Document FBDI support corporate card issuers parties and their related invoices to process corporate card invoice payments using the collection document payment method.

Steps to Enable

To enable this feature, follow these steps and define the lookup type JL_ENABLE_FEATURE and the lookup code JLAP_22C_OI_CD_CC_SUPPORT

1. Go to the Manage Standard Lookups page.
2. Search for the lookup type JL_ENABLE_FEATURE. If it does not exist, add it and Save.
3. Add the new lookup code JLAP_22C_OI_CD_CC_SUPPORT
4. Save the data.

Derivation of Tributary Situation Codes for the Return-to-Vendor Fiscal Document XML Extract

Derive the Brazilian Tributary Situation Codes (CST) for tax on goods and include the correct outbound codes in the fiscal document XML extract file for return-to-vendor shipment transactions.

The Brazilian tax authority requires reporting the Tributary Situation Code (CST) for each tax on goods in a fiscal document. The Fiscal Document Generation process associates the CST code to a tax reporting type, which is used to derive the CST code during tax calculation. These codes are included in the fiscal document XML extract file.

However taxes are not re-calculated in a return-to-vendor shipment flow, they are instead copied from the source document entered in the Fiscal Document Capture. The inbound Tributary Situation Code (CST) must be updated to an outbound code in the return-to-vendor fiscal document.

These new elements are implemented in the existing TAX_LINES group in the fiscal document XML extract file:

Tax authority integration partners can capture and use the new fields for proper reporting to the tax authorities.

Use this feature to map an inbound Tributary Situation Code (CST) to an outbound code in the fiscal document XML extract file, and use the corresponding value required by the tax authority in the fiscal document XML extract file for the return-to-vendor shipment transactions.

Steps to Enable

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

Fiscal Document Generation for Brazil When Order and Item Primary UOMs Differ

Generate fiscal documents from Shipping using a unit of measure different from the item primary unit of measure. This removes a previous restriction to use the item primary unit of measure on sales orders when Fiscal Document Generation for Brazil is enabled.

Both the shipment-based fiscal document XML extract and the fiscal document user interface pages display the same unit of measure used in the sales order, instead of the item primary unit of measure, which could be different.

This feature fulfills the business requirement for a customer to create a shipment-based fiscal document, using the same unit of measure from the sales order which may be different from the primary unit of measure used for Inventory and Shipping purposes.

Steps to Enable

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

Germany

Certification for Germany

Oracle Cloud ERP Financials has been certified according to the IDW PS 880 standard, based on the latest GoBD, German accounting and data access principles, published by the German Ministry of Finance. The Auditing Standard IDW PS 880 of the Institute of Public Auditors in Germany (IDW) is used for software audit processes. In connection with GoBD, the audit process assesses accounting-related software products and supports compliance with legal and regulatory requirements for companies in Germany.

Use SAF-T data extract CSV files for the requirements of German GoBD audit file. This includes the creation of the required index file for all the columns listed in the 14 different types of CSV files in the SAF-T data extract.

This certification documents the compliance of Oracle Cloud ERP with German financial and tax regulations. It helps reduce cost and effort in case of tax audits and during year end closing.

Steps to Enable

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

Tips And Considerations

• The index xml file is provided and reviewed after each release as it needs to reflect all the columns included in the CSV files of the extract at any given moment.

• In order to run the Generate SAF-T Data Extract process for Germany you need to set the Format Type parameter to Generic.

Key Resources

• For more details and the GoBD Compliance Guide, please review the following MOS note, Oracle Fusion Cloud ERP: Germany GoBD Audit Files (Doc ID 2753649.1)

• SAF-T Data Extract Topical Essay, here.

U.S. Federal Financials

U.S. Federal Financials

U.S. Federal Business Event Type Codes (BETC) and Trading Partner Attribute Validation on Journal Lines

Assign Business Event Type Codes (BETC) and Trading Partner Attributes on journal entry lines to properly record cash transactions for Classification Transactions and Accountability (CTA) reporting. Federal Program Agencies use the CTA system to report monthly accounting activity to the U.S. Treasury's Bureau of the Fiscal Service. The accounting information submitted through the CTA component serves as a basis for Treasury's publications to Congress and the public, regarding federal revenues and expenditures.

The agency selects the accounts used to determine the transactions that are reported on the CTA bulk file. The agency should define the default Agency Location Code - ALC for each record used when the ALC cannot be determined from a bank account. The Manage CTA FBWT Account Definitions task provides the ability to manage account definitions that will be used for CTA reporting.

The Federal attributes are applicable to General Ledger journals and provide the ability to capture Federal Award financial attributes required for DATA Act reporting and for GTAS and DATA Act file creation and reporting.

Below is the list of attributes captured for all General Ledger journals at the line level while creating the journal manually or importing it:

Attribute Name	Column Name
BETC	GLOBAL_ATTRIBUTE1
Federal or Non-Federal Code	GLOBAL_ATTRIBUTE2
Trading Partner TAS	GLOBAL_ATTRIBUTE_NUMBER1
Trading Partner BETC	GLOBAL_ATTRIBUTE3
Agency Location Code	GLOBAL_ATTRIBUTE4
Enable for DATA Act Reporting	GLOBAL_ATTRIBUTE5
DATA Act Award Type	GLOBAL_ATTRIBUTE6
Procurement Instrument Identifier (PIID)	GLOBAL_ATTRIBUTE7
Parent Award ID	GLOBAL_ATTRIBUTE8
Federal Assistance Identification Number (FAIN)	GLOBAL_ATTRIBUTE9
Unique Record Identifier (URI)	GLOBAL_ATTRIBUTE10

These attributes are not required for the following types of journals:

• Journals imported from subledgers such as payables, receivables, and so on.
• Encumbrance and budget type journals
• Manual tax journals because government agencies are not subject to tax

The U.S. Federal Business Event Type Codes (BETC) and Trading Partner Attribute Validation on Journal Lines feature provides the capability to capture the attributes on a GL journal (that is either created manually or imported) required for Governmentwide Treasury Account Symbol Adjusted Trial Balance System (GTAS), Digital Accountability and Transparency Act of 2014 (DATA Act) and Classification Transactions and Accountability (CTA) interfaces.

Steps to Enable

U.S. Federal Financials must be enabled.

Tips And Considerations

No specific tips and considerations needed.

Key Resources

• For more information on Federal Business Event Type Codes (BETC) and Trading Partner Attribute Validation on Journal Lines, refer to the Implementing U.S. Federal Financials and Using U.S. Federal Financials guides.

Role And Privileges

Use the existing role, Financial Application Administrator.

U.S. Federal Purchase Order Attributes

Assign U.S. Federal attributes on purchase orders for Government wide Treasury Account Symbol Adjusted Trial Balance System (GTAS) and Data Act Reporting.

The purchase order attributes are required for order headers, order schedules and order distributions. These attributes will be supported as global descriptive flexfield (GDF) attributes at the order header, order schedule, and order distribution level. These attributes need to be defaulted, populated, and validated for orders entered manually or created by import processing. The content has to be validated and revalidated when the transaction is submitted for approval.

Below is the list of attributes captured while creating an order manually or importing it.

Attributes captured at order header level:

Attribute Name	Column Name
Enable for DATA Act reporting	GLOBAL_ATTRIBUTE1
DATA Act Award Type	GLOBAL_ATTRIBUTE2
PIID	GLOBAL_ATTRIBUTE3
Parent Award ID	GLOBAL_ATTRIBUTE4
FAIN	GLOBAL_ATTRIBUTE5
URI	GLOBAL_ATTRIBUTE6

Attributes captured at order schedule level:

Attribute Name	Column Name
Trading Partner TAS	GLOBAL_ATTRIBUTE_NUMBER1
Trading Partner BETC	GLOBAL_ATTRIBUTE1

Attributes captured at order distribution level:

Attribute Name	Column Name
BETC	GLOBAL_ATTRIBUTE1

The U.S. Federal Purchase Order Attributes feature provides the capability to capture the required attributes on a purchase order (either created manually or imported) that are needed for Governmentwide Treasury Account Symbol Adjusted Trial Balance System (GTAS) and Data Act Reporting.

Steps to Enable

U.S. Federal Financials must be enabled.

Key Resources

• For more information on Federal Purchase Order attributes, refer to the Implementing U.S. Federal Financials and Using U.S. Federal Financials guides.

Role And Privileges

Use the existing role, Financial Application Administrator.

U.S. Federal SAM Supplier Import Into Federal Financials

Use automatically imported System for Award Management (SAM) supplier data to support federal agency obligation, accounts payable and disbursement processes. The Office of Management and Budget (OMB) requires agencies to use information in SAM as the official source for making payments to suppliers, with certain exceptions. Current and potential government suppliers must register in SAM to be awarded contracts by federal agencies. Trading partners provide basic information relevant to procurement and financial transactions.

The SAM process enables agencies to import and automatically process data pertinent to the core financial system. Agencies can:

• Automatically update mandatory payee information in existing trading partner records to reflect the relevant changes contained in the daily updates.

• Accommodate the data definitions, such as data types, field names, and field lengths, used in SAM for all fields common in both SAM and the core trading partner file.

• Prevent users from manually updating the relevant data fields whose source must be SAM for trading partners required to register in SAM.

In addition, the SAM process maintains payee (trading partner) information to support federal agency obligation, accounts payable, and disbursement processes.

The business benefits of the U.S. Federal SAM Supplier Import into Federal Financials feature include:

• Provides the capability to import and process data contained in System for Award Management (SAM) as the source for making payments to trading partners.

• Maintains payee (trading partner) information to support federal agency obligation, accounts payable, and disbursement processes.

Steps to Enable

• U.S. Federal Financials must be enabled.

• The SAM extract file must be downloaded from the General Services Administration website (gsa.gov).

• The Federal SAM Administration Duty role (ORA_FV_SAM_ADMINISTRATION_DUTY) must be assigned to a job role that the user has access to.

• The Federal SAM Administration Duty role must have the following privileges assigned to perform the following tasks:
  • Manage SAM Trading Partners privilege (FV_MANAGE_SAM_TRADING_PARTNERS) to manage SAM trading partners

Key Resources

• For more information on Federal SAM processing, refer to the Implementing U.S. Federal Financials and Using U.S. Federal Financials guides.

Role And Privileges

• The Federal SAM Administration Duty role (ORA_FV_SAM_ADMINISTRATION_DUTY) must be assigned to a job role that the user has access to.

• The Federal SAM Administration Duty role must have the following privileges assigned to perform the following tasks:
  • Manage SAM Trading Partners privilege (FV_MANAGE_SAM_TRADING_PARTNERS) to manage SAM trading partners
  • Assign SAM Suppliers privilege (FV_ASSIGN_SAM_SUPPLIERS) to assign business units to trading partners
  • Assign SAM Customers privilege (FV_ASSIGN_SAM_CUSTOMERS) to assign customers to trading partners

IMPORTANT Actions and Considerations

DEPRECATION OF OLDER DIGITAL ASSISTANT SKILL VERSIONS

The Digital Assistant and its skills continuously receive updates as they get smarter and provide enhanced conversational experiences. Check for updated versions for every release in the Skill Store. Versions stop working when the underlying platform version becomes inactive, at the longest 2 years after release.

The Expenses skill built using Oracle Digital Assistant platform version 20.08 is deprecated and may become obsolete soon. You can continue using your skill in platform version 20.08, however, no updates or bug fixes for this specific version of the skill will be provided. We encourage you to move to the latest version of the Expenses skill at the earliest opportunity. For more details on the lifecycle of skill versions, see Lifecycle Phases of Platform Versions.

DEPRECATION OF PAYMENT INFOTILE

Invoices Landing Page

The Payment infotile on the Invoices landing page displays the total amount due for payment by the currency. Clicking the amount displays the invoices due in the subsequent table. The Payment infotile will no longer be available from update 22C onwards. However, you can still retrieve the information from the Payment infotile using the suggested alternatives.

• Option A: Manage Invoices - Saved Search: Create a saved search to get the supplier invoice balance for validated/approved and fully/partially unpaid invoices.

• Option B: OTBI - Supplier Dashboard: Deploy catalog to get supplier and invoice outstanding balances.

Detailed steps for the above options are explained in MOS Note Alternate Options for Supplier Outstanding Balance (Doc ID 2871676.1) on My Oracle Support.