Update 21C

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 OCT 2022	Budgetary Control	Budget Entry Classification for Initial or Adjustment Budget Balance Using Spreadsheet and Budget Transfer	Updated document. Added opt in expiration update.
01 DEC 2021	Payables	Electronic Filing of Forms 1099-MISC and 1099-NEC for Tax Year 2021	Updated document. Delivered feature in update 21C.
24 SEP 2021		IMPORTANT Actions and Considerations	Updated document. Added section.
24 SEP 2021	Receivables	AutoInvoice Interface Lines Review and Update Using a REST API	Updated document. Revised Role information.
24 AUG 2021	Common Financials Features	Service Excellence Continuing Investments	Updated document. Revised feature information.
24 AUG 2021	Payables	Forms 1099-MISC and 1099-NEC for Tax Year 2021	Updated document. Delivered feature in update 21C.
24 AUG 2021	Tax	Touchless Resubmission of Partner Transaction Data Extract	Updated document. Added Steps to Enable.
04 JUN 2021			Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

Join Oracle Cloud Customer Connect

Please take a moment to join the Cloud Customer Connect forums for Financials Cloud. Oracle Cloud Customer Connect is a community gathering place for members to interact and collaborate on common goals and objectives. This is where you will find the latest release information, upcoming events, or answers to use-case questions. Joining takes just a few minutes. Join now!

https://cloud.oracle.com/community

Security and New Features

The Role section of each feature identifies the security privilege and job role required to use the feature. If feature setup is required, then the Application Implementation Consultant job role is required to perform the setup, unless otherwise indicated. (If a feature doesn't include a Role section, then no security changes are required to use the feature.)

If you have created job roles, then you can use this information to add new privileges to those roles as needed.

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.

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.

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 in this update, 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 current Opt In Expirations across all Oracle Cloud Applications. Beyond the current update, the Financials forums on Cloud Customer Connect have details of Opt In Expirations upcoming in future updates.

Feature Summary

Common Technology and User Experience

Common Financials Features

Employee Vacation and Delegation Rules Report

Use the Employee Vacation and Delegation Rules report to view the vacation and delegation rules set by your employees in Oracle Business Process Management (BPM). Workflow administrators can use this report to review details of the rules defined by employees to delegate or reassign their workflow tasks.

The report contains the following details:

Section	Content
Originator Employee Details	Information about the employee who has defined the vacation or delegation rule, such as the employee name, person number, position, job code, location and email ID.
Rule Details	Details of the rule defined by the employee. Includes the rule type (vacation or delegation), validity period, type of action(reassign or delegate) and the rule conditions based on which the workflow tasks will be reassigned or delegated.
Destination Employee Details	Information about the employee to whom the workflow tasks are reassigned or delegated. Includes the employee's name, person number, position, job code, location, email ID and the name and person number of the employee's manager.

Employee Vacation and Delegation Rules Report

Steps to submit the report:           

1. Log in and navigate to the Manage Workflow Rules in Spreadsheet page.
2. Click the Submit Vacation Rules Report URL link to open the window to enter the report parameters.         
3. Click Submit. The submitter receives a confirmation bell notification when the report is generated and ready for download.

Steps to Enable

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

Tips And Considerations

If you don’t enter the date parameters while submitting the report, it’s submitted for the current calendar period by default.

Role And Privileges

• Users with Financials Application Administrator role can access the Manage Workflow Rules in Spreadsheet UI.

• Privilege details:
  • Run BPM Workflow Reports

ERP Data Access Assignment Report

The ERP Data Access Assignment Report provides a listing of all active data access assignments managed by the Manage Data Access for Users module.

Sample Report Layout

The business benefits include:

• The ERP Data Access Assignment Report provides a complete extract of all active data access assignments in a single spreadsheet.
• The report helps reduce the time needed to prepare the information required for a security audit.

Steps to Enable

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

Tips And Considerations

• Report preparation is done in the background. The user will be notified when the report is available for download.
• The report shows all active assignments. For the list of assignments for a user or a role, use the Export to Excel option after querying the desired assignment records.

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:

Performance

• Performance Improvement for Withholding Tax Calculation: Improve withholding tax calculation performance for payment process requests that generate a large number of payments.

• Performance Improvement while Opening Payables Invoices with Attachments: Improve performance in the Manage Invoices page when querying and opening Payables invoices that have attachments.

• Netting Settlements Performance Improvement: Netting settlements now handle agreements in batches instead of individually, leading to improved performance.

Usability

• General Ledger Period Close Restrictions for Open Intercompany Transactions: Prevent the close of General Ledger periods when there are unprocessed Intercompany transactions in the respective ledger and period.

• Support Upload of Printed Documents to Receivables Invoice as Attachments: Support upload of printed documents to a Receivables invoice as attachments when the document is delivered via more than two channels (such as Email, Print and SFTP).

• Changes to Expense Report Number Digits Display: The number of digits of the expense report number displayed to users in the Expenses work area is increased to 12 digits.

• Improved Handling of Accounting Error Message in Expense Entry: The invalid account error message that the user receives while submitting an expense report provides the corrective actions to resolve the issue.

Steps to Enable

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

Intercompany

Credit Memo for Negative Intercompany Transactions

Create credit memos in Receivables and Payables for negative intercompany transactions. Transactions with a credit receivable and a debit payable are also created as credit memos.

This feature is an enhancement to the existing processing intercompany transactions feature. It lets you create a credit memo in the Receivables and Payables applications when the Intercompany transaction type used to create the transaction requires invoicing. These factors determine if the system creates an invoice or credit memo:

• the Intercompany transaction type.
• whether it is a debit or credit transaction amount.
• whether it is a negative or positive transaction amount.
• the Receivables (or credit memo) transaction type assigned to the intercompany transaction type and business unit.

The Receivables transaction type determines the document (Invoice or Credit Memo) created in Receivables. However, you can override this during intercompany transaction creation by choosing a different Receivables transaction type for each transaction in the batch.

Receivables allows you to create invoices or credit memos with either positive or negative amounts from intercompany transactions. Payables lets you create credit memos from negative intercompany transactions. This table shows various options to create intercompany invoices or credit memos.

This feature

• Enables compliance with legal, fiscal, taxation, and document sequencing regulations in jurisdictions where it’s necessary to produce separate invoice and credit memo transactions and documents for intercompany activity. 

• Provides flexibility during intercompany transaction creation by allowing override of Receivables transaction type for each transaction in a batch.

• Reduces the volume of intercompany batches by allowing the creation of multiple transactions with different Receivables transaction types within a single batch.

Steps to Enable

This feature is enabled by default once the following setup is completed.

• In the Setup and Maintenance work area, under Financials, Customer Billing, use the Manage Autoinvoice Grouping Rules task to add a new row for the transaction class of Credit Memo as shown in this  screenshot.

• In the Setup and Maintenance work area, under Financials, Customer Billing, use the Create Receivables Transaction Types task to create as many credit memo Receivables transactions types as required. They must have a Transaction Class of 'Credit Memo' and Creation Sign of 'Any'.

• In the Setup and Maintenance work area, Financials, Intercompany use the Manage Intercompany Receivables Assignment task to assign credit memo Receivables transaction types for your negative transactions.

Tips And Considerations

• The Receivables Transaction Type field on the Create Intercompany Batch page is enabled if the selected intercompany transaction type requires invoicing.
• You can override the default Receivables transaction type before submitting the transaction for processing.
• If you don't have a Receivables transaction type specified either on your negative transaction or in the setup, Oracle Cloud Receivables will create a negative invoice.
• You can also select different Receivables transaction types for transactions that will be created as invoices in Oracle Cloud Receivables.

Web Services

Cash Management

Bank Transfers Using a REST API

Create, update, and view bank transfers with or without settlements using the Bank Transfers REST API.

This REST API enables external systems to integrate with Cash Management for initiating and settling fund transfers between bank accounts.

Steps to Enable

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

Tips And Considerations

• During the settlement process, use the UI to manage bank transfers that require user actions.
• There are no changes to accounting or to external transactions generated for bank transfers.

General Ledger

Account Combination Shorthand Aliases Retrieval Using a REST API

Retrieve shorthand aliases for account combinations using the Account Combinations Shorthand Aliases List of Values REST API. You can search for an account combination using the shorthand alias. With this REST API, you can retrieve all shorthand aliases details for one or more charts of accounts.

The business benefits of this feature are:

• Reduced errors from automating a manual process.
• Increased efficiency from streamlining across external processes or systems.

Steps to Enable

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

Key Resources

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

Chart of Accounts Filter Creation Using a REST API

Use the Chart of Accounts Filter REST API to create an identifier for a chart of accounts filter with one or more segments. This identifier can then be used as a job parameter for submitting processes that have an account filter parameter. 

The benefits of this feature are:

• Reduced errors from automating a manual process.
• Increased efficiency from streamlining across external processes or systems.

Steps to Enable

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

Key Resources

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

Role And Privileges

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

Receivables

Additional Attributes to Identify Receipts for Reversal Using the Receivables Standard Receipt SOAP Service

Specify additional attributes to identify receipts for reversal using the processReverseReceipt operation in the Receivables Standard Receipt SOAP Service. This enables unique identification of receipts for automated receipt reversal and helps reduce errors when there are duplicate receipt numbers.

Improve customer satisfaction by reducing receipt reversal errors and ensuring customer account balances are accurate.

Steps to Enable

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

Tips And Considerations

Use the receipt_id if there are cases where the receipt numbers being reversed may be the same.  This value can be obtained by using the Get operation in the Standard Receipts REST service.

Key Resources

For more information, refer to the following in the Oracle Help Center.

• About SOAP Web Services in Oracle Applications Cloud
• REST API for Common Features in Oracle Applications Cloud

AutoInvoice Interface Lines Review and Update Using a REST API

Review and update AutoInvoice interface line attributes using the Receivables Transaction Interface Lines REST API.

Use the Receivables Transaction Interface Lines REST service to get and update an interface line. You can perform these activities:

• Retrieve the details of a Transaction Interface Line.
• Update a Transaction Interface Line.
• Update Interface Header Information.
• Update Interface Line Information.
• Retrieve the details of an Interface Line Transaction Descriptive Flexfield.
• Retrieve the details of an Interface Header Information Descriptive Flexfield.
• Retrieve the details of an Interface Line Information Descriptive Flexfield.

Receivables Transaction Interface Lines: The AutoInvoice Interface Lines resource is used to retrieve and update the interface line.

Interface Line Transaction DFF: The Interface Line Transaction Descriptive Flexfields resource is used to retrieve the flexfield segments of the line transaction descriptive flexfield context for the interface line.

Interface Header Information DFF: The Interface Header Information DFF resource is used to retrieve and update the flexfield segments of the header attributes for the interface line.

Interface Line Information DFF: The Interface Line Information resource is used to retrieve and update the flexfield segments of the line information descriptive flexfield for the interface line.

AUDIT: The update on interface line using Receivables Transaction Interface Lines REST service can be Audited. In the Manage Audit Policies page, enable the Interface Line Audit option to capture the audit data.

You can view details about these services in the REST API for Oracle Financials Cloud guide

• Update AutoInvoice Interface data before importing invoices and other transactions.
• Create an audit trail to find the data mismatches between upstream and downstream products.

Steps to Enable

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

Key Resources

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

Role And Privileges

• You must create a new privilege access to use this feature:
  • Create a new privilege for the Interface service
  • Add the privilege to the user

Name: Manage Receivables AutoInvoice Interface Line

Code: AR_MANAGE_AUTOINVOICE_INTERFACE_PRIV

Description: Allow Oracle Financials Cloud users to access the operations associated with the AutoInvoice Interface Line.

Current Direct Debit Authorization Update on Existing Invoices Using a SOAP Service

Update the direct debit authorization on existing invoices where the debit authorization start date is later than the invoice creation date using the createUpdateCCToken operation on the Receivables Invoice SOAP Service.

Improve receipt processing by automating requisite direct debit authorization updates using the Receivables Invoice SOAP Service.

Steps to Enable

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

Customer Modification to Standard Receipts Using a REST API

Add or update customers on standard receipts using the Receivables Standard Receipts REST API.

Use the Standard Receipts REST API resource to update the customer details. With this service, you can:

• Add the customer details on a standard receipt using the update operation
• Change the customer details on a standard receipt using the update operation

You can view details about these services in the REST API for Oracle Financials Cloud guide.

The business benefits of this feature are:

• Increased value from integration with other existing software investments
• Reduced errors from automating a previously manual process
• Increased efficiency from streamlining across external processes or systems

Steps to Enable

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

Key Resources

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

On-Account Credit Memo Creation Using a REST API

Create on-account credit memos without specifying an invoice or invoice line using the Receivables On-Account Credit Memo REST API.

You can create on-account credit memos with distributions, attachments, and notes. Additionally, you can capture information on credit memo lines and distributions using descriptive flexfields, including transaction flexfields and global descriptive flexfields.

Improve your customer service satisfaction by more efficiently processing customer on-account credit memos when integrating your on account credit memo creation activities across multiple systems. 

Steps to Enable

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

Tips And Considerations

The purpose and usage of this REST API is similar to the Receivables Invoice REST API.  Refer to the Use Cases section in the Oracle Help Center for more details.

Key Resources

For more information, refer to the following in the Oracle Help Center.

• REST API for Common Features in Oracle Applications Cloud
• REST API for Oracle Financials Cloud - Receivables Credit Memos
• REST API for Oracle Financials Cloud - Use Cases - Manage Receivables Credit Memos

Receipt Methods Retrieval Using a REST API

Retrieve receipt methods using the Get Receivables Receipt Method REST API. Use the Get action as the most efficient way to retrieve receipt methods for external systems.

Use the Get action in the Receipt Methods REST API along with other tools to build external user interfaces that require receipt method information, according to your business requirements.

Steps to Enable

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

Key Resources

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

Tax

Tax Reporting Code Association Using a REST API

Create tax reporting code associations for suppliers, supplier sites, customers, and customer sites using the Create Tax Reporting Code Association REST API.

Use the POST operation of the REST service to create the tax reporting code association.

The tax reporting code association can be created using REST API in an automated way reducing manual efforts.

Steps to Enable

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

Key Resources

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

Role And Privileges

• This REST Service is secured with the same privileges as the Party Tax Profile REST Service. Thus, a user who has the privileges to execute the Party Tax Profile REST Service would be able to execute this new REST Service as well.

Financials for EMEA

Netting Agreement Update Using a REST API

Update the netting agreement using the Netting Agreement REST API. This helps handling large volume of agreements.

Additionally, you can create an agreement and search for existing agreements using this REST API.

Reduces manual effort to update a large volume of agreements.

Steps to Enable

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

Key Resources

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

Financials

Advanced Collections

Collections Data Point for Account Total Amount Past Due

Provide the data point Account Total Amount Past Due for Sites.

Access the Account Total Amount Past Due for Sites data point from the Edit Scoring Data Point page. Information includes the total amount past due for the customer account at the site level. This data point is the sum of the total amount due on all transactions for all sites. The value of this data point is therefore the same for all sites belonging to the customer account.

Screenshot of the Scoring Data Point

This helps determine the collectability of open balances belonging to each customer site.

Steps to Enable

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

Assets

Asset Inquiry Page Enhancements

The Export to Excel icon in the Asset Inquiry page:

• Immediately downloads the spreadsheet file when the asset volume is less than 201.
• Delivers the spreadsheet file through a notification when the asset volume is more than 200.

You can export a high volume of assets to a spreadsheet more efficiently.

Steps to Enable

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

Invoice Rules Tab in the Create Book and Edit Book Pages

Access the options related to invoice transfer from Payables using the Invoice Rules tab in the Create and Edit Book pages.

The following options related to invoice transfer from Payables are now grouped under the Invoice Rules tab in the Create Book and Edit Book pages. Previously these options were in the header region of these pages:

• Use Payables invoice date as date placed in service
• Allow unallocated Payables invoice lines
• Suspend automatic merge of Payables invoice lines

You can easily find the invoice rules for the corporate books and manage them.

Steps to Enable

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

Budgetary Control

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

In Update 21B users specify the budget entry classification as initial budget or budget revisions for file-based budget data import and budget spreadsheets to impact either initial or adjustment budget balances.

In this update, budget transfers from Review Budgetary Control Balances are classified as budget revisions and update budget adjustments balance regardless of the budget period status.

Budget transfers are classified as a budget revision when the control budget period status is open or available for budgeting.

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

The 21B opt-in for Budget Entry Classification for Initial or Adjustment Budget Balance using Spreadsheet now includes Budget Transfers. 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

Functional Area:  Budgetary Control and Encumbrance Accounting

Available in:  21B

Tips And Considerations

New Customer Installations:

• This feature defaults with Opt-In enabled.

Upgraded Customer Installations:

• This feature was introduced in 21B for file-based budget data import and budget spreadsheets. In 21C, the Budget Transfer process, initiated on Review Budgetary Control Balances page is added to this feature. If you have enabled this feature in 21B, no further action is needed.

• When this feature is disabled, the budget entry classification is determined by period status. When the budget period status is Open, the budget balance is classified as an adjustment. When the budget period status is Available for budgeting, the budget balance is classified as Initial. When this feature is enabled, you select the budget entry classification of the budget balance for budget spreadsheet and file-based budget data import regardless of the period status.

• 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.

• Classification of budget entries by budget period status will be removed in a future release. 

• If you have scheduled either the Import Budget Amounts or Import Budget for Budgetary Control and General Ledger process, or you have created custom ERP integration to invoke any of these processes, you must update them to reflect the new and changed parameters introduced by this feature.

• The Import Budget Amounts process Import mode parameter has been renamed to Budget Amounts Entered As and has these new values.

Key Resources

• Import Budget Data from a Flat File for Budgetary Control in Using Financials for Public Sector
• Budgetary Control Budget Import in File-Based Date Import (FBDI) for Financials

Role And Privileges

• Budget Manager role is needed to submit these processes:
  • Enter Budgets in Spreadsheet
  • Import Budget Amounts
  • Import Budget for Budgetary Control and General Ledger
  • Budget Transfer

Budgetary Control Budget Balance Synchronization to Different Period Names and Non Budgeted Segments

Map the Budgetary Control budget segments and calendar to the General Ledger calendar and chart of accounts to enable automatic synchronization of the Budgetary Control and General Ledger budget balances.

Synchronize budget balances between Budgetary Control and General Ledger even when your budget calendar and budget segments are different than the ledger.

Budget calendar doesn’t have to be the same as the accounting calendar.  Budget segments can be a subset of the chart of accounts.

Mapping Between Chart of Accounts and Budget Accounts

Steps to Enable

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

Tips And Considerations

Consider these points for the Import Budget for Budgetary Control and General Ledger process and Budget revisions from EPM Planning Financials:

• Imported budget periods are automatically converted to the corresponding accounting period by using the first date of the budget period for these processes when importing into General Ledger.

• The segment value in the Mapping Between Chart of Accounts and Budget Accounts region of the Manage Budgetary Control page is assigned when importing budget in General Ledger and a segment value is not present in the import budget data.

Key Resources

• Budget Entry in Using Financials for the Public Sector
• Enterprise Performance Management Financials Module in Using Financials for the Public Sector

Role And Privileges

• The Budget Manager role is needed to submit Budgetary Control and General Ledger process and manage Budgetary Control.
• The EPM Planning Administrator role is needed to enable budget revisions and set up data mapping.

Journal Sources Cost Accounting and Receipt Accounting Added As Budgetary Control Exceptions

Journals created from Cost Accounting and Receipt Accounting will be excluded by default when budgetary control is enabled for new ledgers.

These journal source exceptions prevent budgetary control validation on General Ledger journals generated for Cost Accounting and Receipt Accounting subledger transactions that haven’t yet been budgetary controlled in the subledgers.

Budgetary Control Exceptions

Steps to Enable

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

Tips And Considerations

Upgrade Customer Installations:

The Cost Accounting and Receipt Accounting journal sources are not added as Budgetary Control Exceptions to ledgers that are already enabled for Budgetary Control and Encumbrance Accounting.  Add these journal sources as exceptions in the Edit Budgetary Control and Encumbrance Accounting page.

Key Resources

• Ledger and Business Unit Options in Using Financials for the Public Sector

Role And Privileges

• Application implementation consultant role is needed to access the Manage Budgetary Control task.

Cash Management

Bank Transfers Using a REST API

Create, update, and view bank transfers with or without settlements using the Bank Transfers REST API.

This REST API enables external systems to integrate with Cash Management for initiating and settling fund transfers between bank accounts.

Steps to Enable

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

Tips And Considerations

• During the settlement process, use the UI to manage bank transfers that require user actions.
• There are no changes to accounting or to external transactions generated for bank transfers.

Expenses

Dual Currency Corporate Card Support

Upload corporate card transactions for dual currency corporate cards. Enable employees to submit them in expense reports and create payment requests for these transactions in the payment currency accepted by the card issuer.

Dual currency markets are countries where charges incurred within the country are billed in the local currency and charges incurred outside the country are billed in a predetermined currency other than the local currency. Companies pay card issuers in their local currencies for both local and foreign charges. Dual currency cards are prevalent in markets with volatile currencies.

When a company account is enabled to accept dual currency card charges and the billed currency of the corporate card transaction is different from the payment currency of the company account, Expenses converts the billed amount of the transaction to an equivalent amount in the payment currency of the company account using the designated conversion rate on the transaction date. The original amount in the billed currency is preserved. When a conversion rate is not available, the transaction remains invalid with the Missing currency conversion rate status. The employee sees the charges in the receipt currency and the converted billed amount in the Expenses work area.

Currently, to upload card charges to Expenses, the billed currencies of transactions must equal the payment currencies of the corresponding company accounts. With dual currency support, companies can seamlessly process dual currency corporate card charges and enable employees to submit these charges directly from the Expenses work area.

Steps to Enable

To enable this feature, perform the following steps:

1. Sign in as the Corporate Card Administrator.
2. From the Setup and Maintenance work area, navigate to the Manage Corporate Card Programs page.
3. Drill down to the company account associated with the country where dual currency cards are issued.
4. Enable the Allow multiple billed currencies option.
5. Save the changes.

Enabling Dual Currency Support

Corporate card administrators can view the original billed amount in the Review Corporate Card Transactions page. Billed amount is converted to payment currency of the company account.

Dual Currency Transactions with Original Billed Amount

Dual Currency Transaction in Expense Report

Tips And Considerations

• Enable the Allow multiple billed currencies option only for the company accounts where dual currency cards are issued for your employees.
• There are no changes to the payment request creation process. Payment requests are created in the payment currency of the company account.

Role And Privileges

• To enable dual currency support, you need the Corporate Card Administrator role.

Single Click Audit Activation with Preconfigured Rules

Allow companies to audit anomalous expenses, such as duplicate expenses, expenses with public sector attendees, and expenses with violations, using preconfigured models and rules. Enable this intelligent audit for the company by the click of a button.

Additional audit rules identify the following:

• Expense reports of top spenders within a specified time frame
• Expense reports of top violators within a specified time frame
• Employees who violate specific policies above a designated threshold
• Expense reports with public sector attendees
• Duplicate expense items

Currently, audit rules are defined at the business unit level. With single click audit activation, companies can enable audit rules for all business units at once. Companies can define exceptions to the audit rules for specific business units according to business requirements. Additionally, new audit rules enable companies to identify potential anomalies even when expenses are within company policies.

Steps to Enable

To enable this feature, perform the following steps:

1. Sign in as the Expense Manager.
2. Navigate to the Setup and Maintenance work area.
3. Search for the Manage Expense Report Audit Rules task.
4. To enable the audit rules for all business units for the first time, click the Activate Rule button. The page refreshes to allow entry of start and end dates for the audit rules.
5. Enter an effective start date.
6. Optionally enter an effective end date if the end date of the audit rule is known.
7. Uncheck the rules that are not applicable.
8. Click Save.
9. To define audit rule exceptions for specific business units, select the Create icon from the Specific Business Units section.
10. Enter an effective start date.
11. Optionally enter an effective end date if the end date of the audit rule is known.
12. Uncheck the rules that are not applicable.
13. Click Save and Close.
14. To view existing rules for a specific time period, select the Effective Date choice list and select the applicable time period.

NOTE: When you enable the following audit rules, you must also schedule the Generate Summary Metrics for Expenses process. When scheduled, this process updates the data for top spenders, top violators, and violators by policy.

• Audit expense reports of top spenders
• Audit expense reports of top policy violators
• Audit expense reports with same policy violation for more than the specified times

Audit Rules at Site Level

Audit Rule Exceptions at Business Unit Level

Expense Report with Audit Reasons

Role And Privileges

• To enable single click audit activation, you need the Expense Manager role.

Federal Financials

U.S. Federal Accounting Based on Funding Derivation Type

Create Federal invoice and payment accounting based on funding derivation type to comply with the U.S Standard General Ledger requirements.

You can assign optional funding derivation types to Treasury Account Symbol payment business event type codes (BETC) and a required funding derivation type to Fund Attributes.

The funding derivation type is exposed as a source attribute in subledger accounting and included as criteria in predefined accounting rules in order to create proper federal accounting.

In the Business Event Type Codes tab of the Treasury Account Symbol page, you can optionally assign up to three default payment BETCs for each of the funding derivation type values:

• Derived from General Fund
• Not derived from General Fund
• Null.

The funding derivation type is not applicable for collections BETC.

Federal Treasury Account Symbol Page BETC Tab

The funding derivation type is a required value for Fund Attributes. In the Reporting section of the Fund Attribute page, assign a funding derivation type value of Derived from General Fund or Not derived from General Fund.

Federal Fund Attributes Page

The business benefits include:

• Supports compliance with the U.S Standard General Ledger requirements

• Provides defaulting and validation rules that enables efficient processing while reducing data entry errors. This can save time and effort validating data accuracy and completeness for reporting purposes.

Watch a Demo

Steps to Enable

1. Update the funding derivation type for BETCs using the the Federal Business Events Type Codes REST API.
2. Assign applicable BETC values for agency TAS' including specifying the defaults based on funding derivation type, as necessary.
3. Assign funding derivation type to funds on the Fund Attributes page.

Tips And Considerations

There is no BETC page available for entering and modifying BETC values, because they are predefined based on information from the U.S. Treasury. You must use the Federal Business Events Type Codes REST API to update the predefined values and populate the funding derivation type.

Key Resources

• Watch U.S. Federal Accounting Based on Funding Derivation Type Readiness Training

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

U.S. Federal Budget Execution Configuration

Configure Federal Groups, Federal Ledger Options, and Budget Transaction Types for the Federal budget execution process.

FEDERAL GROUPS

The Manage Federal Groups page provides the ability to share selected setup across ledgers that have a common natural account value set.

The Manage Federal Groups page is accessed in the Setup and Maintenance work area with the Manage Federal Groups task:

• Offerings: Financials.
• Functional Area: U.S. Federal Financials.
• Task: Manage Federal Groups.

Manage Federal Groups Page

Click the Add (+) button to create a new federal group or select a row and click the Edit (pencil) button to update the federal group.

New Federal Group Page

The new Federal Group page attributes include the following:

1. Name: Name of the Federal Group.
2. Description: Description of the Federal Group.
3. Natural Account Value Set: Natural account value set for ledgers that can be assigned to the Federal Group.
4. Freeze Levels: Identifies if the budget levels for the ledger are frozen.
5. Sequence*: Sequence number of the budget level.
6. Level*: Name of the budget level.
7. Description*: Description of the budget level.

NOTE: Multiple budget levels can be defined for each federal group.

FEDERAL LEDGER OPTIONS

The Manage Federal Ledger Options page allows the user to define ledger specific options for the ledger including budget execution related options.

The Manage Federal Ledger Options page can be accessed in the Setup and Maintenance work area with the Manage Federal Ledger Options task:

• Offerings: Financials.
• Functional Area: U.S. Federal Financials.
• Task: Manage Federal Ledger Options.

Manage Federal Ledger Options Page

Click on Add (+) button to create a new federal ledger option or select a row and click on the Edit (pencil) to update the federal ledger option.

Federal Ledger Options Page

The Federal Ledger Option page attributes include the following:

1. Name: Name of the Ledger.
2. Federal Group: Identifies the Federal group assigned to the Ledger.
3. Document Number Entry: Identifies if the budget transaction document numbering is Manual or Automatic.
4. Document Number Type: Identifies if the budget transaction document number type is Alphanumeric or Numeric.
5. Default Segment Values: Default account combination for budget transaction.
6. USSGL Tree: USSGL tree for the Ledger.
7. Closing Segments: Closing segment for the Ledger.

BUDGET TRANSACTION TYPES

The Budget Transaction Types page provides the ability to require selected attributes and define debits and credits to be generated for budget transactions based on the budget transaction type.

The Budget Transaction Type page can be accessed in the Setup and Maintenance work area with the Manage Budget Transaction Types task:

• Offerings: Financials.
• Functional Area: U.S. Federal Financials.
• Task: Manage Budget Transaction Types.

Manage Budget Transaction Types Page

Click on Add (+) button to create a new budget transaction type record or select a row and click on the Edit (pencil) to update the budget transaction type.

Budget Transaction Type Page

The Budget Transaction Type page attributes include the following:

1. Type: Name of the budget transaction type.
2. Description: Description of the budget transaction type.
3. Federal Group: Federal group assigned to the budget transaction type.
4. Budget Level: Budget level assigned to the budget transaction type.
5. Authority Type Code: Authority type assigned to the budget transaction type.
6. Close Budget: Identifies if the budget transaction type is used for year-end closing.
7. Require Trading Partner: Identifies if the trading partner is required.
8. Require Reduction Type: Identifies if the reduction type is required.
9. Enabled: Identifies if the budget transaction type is enabled.
10. Debit*: Debit GL account for the budget transaction type.
11. Credit*: Credit GL account for the budget transaction type.

NOTE: Multiple debit and credit pairs can be defined for a budget transaction type

This feature gives the capability to create budget execution configurations that are required to create budget transactions.

It provides the following business benefits:

• Supports compliance with U.S. Standard General Ledger requirements.
• Decrease the overall configuration time by sharing a selected configuration across ledgers that share the same natural account value set.

Steps to Enable

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

Tips And Considerations

• Ledgers assigned to the same Federal Group must share the same Natural Account Value Set.
• Budget Transaction Types can be shared across ledgers that are assigned to the same Federal Group.

Key Resources

• Watch U.S. Federal Budget Execution Readiness Training.
• For more information on federal budget execution, refer to the Implementing U.S. Federal Financials and Using U.S. Federal Financials guides.

Role And Privileges

• Use the existing job role ‘Financial Application Administrator’.

U.S. Federal Invoice Attributes for Direct Invoices

Capture federal attributes on direct invoice transactions (invoices not matched to purchase orders or receipts) to support GTAS and CTA interfaces as well as PAM and SPS payment file formats.

INVOICE HEADER

• Payment Reference Number

The Payment Reference Number field is a free-text field. Use this field to store additional payment information, such as credit card numbers.

Invoice Header Level Federal Attribute

INVOICE LINE

• Trading Partner TAS (Treasury Account Symbol)
• Trading Partner BETC (Business Event Type Code)

The Trading Partner TAS and Trading Partner BETC attributes are used for reporting purposes when doing business with other government agencies. These attributes are required when the supplier on the invoice is another federal agency.

NOTE: Designating a supplier as federal or non-federal to be provided in a future release.

Invoice Line Level Federal Attributes

INVOICE DISTRIBUTION

• BETC (Agency Business Event Type Code)

The BETC is a required value on each distribution line for SPS and PAM payment files. The list of values in the BETC field contains the BETCs associated with the agency TAS derived from the fund value on the distribution account.

Invoice Distribution Level Federal Attribute

If the required attributes are not entered on the corresponding invoice lines and invoice distributions, the correct values are populated by default during invoice validation. If no default is configured, but the value is required according to the setup, a hold is placed on the invoice. The user can either enter the values manually or update the setup and revalidate the invoice.

The business benefits include:

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

Watch a Demo

Steps to Enable

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

Key Resources

• Watch U.S. Federal Invoice Attributes for Direct Invoices Readiness Training

U.S. Federal PAM Input System

Populate input system on the PAM payment file from Federal Options at the business unit level.

Specify the input system name and the agency abbreviation code for each business unit individually on the Federal Options page. This information is populated on PAM payment format files.

Note that the input system name and agency abbreviation code are optional attributes for a business unit on the Federal Options page.

Federal Options Page

Alternatively, use the following profile options to specify the input system name or the agency abbreviation at site level:

• Input System for PAM Payment Files
• Agency Abbreviation for PAM Payment Files

The business benefits include:

• Optionally define these attributes at the business unit level or as profile option values at the site level.
• Either the business unit level values or the profile option values are populated on PAM payment files.

Watch a Demo

Steps to Enable

To enable this feature, perform the following steps:

1. In Setup and Maintenance navigate to the Manage Federal Options task.
2. Create a new record for you business unit or edit an existing record.
3. Enter the PAM Input System and/or the PAM Agency Abbreviation and save the changes.

Alternatively, if you are going to use the same values for all or most of your business units across your agency:

1. Navigate to the Mange Federal Profile Options task.
2. Find the Input System for PAM Payment Files profile option and set the site level value to the PAM Input System Name you want to use.
3. Find the Agency Abbreviation for PAM Payment Files profile option and set the site level value to the Agency Abbreviation you want to use.

Key Resources

• Watch U.S. Federal PAM Input System Readiness Training

General Ledger

Chart of Accounts Filter Creation Using a REST API

Use the Chart of Accounts Filter REST API to create an identifier for a chart of accounts filter with one or more segments. This identifier can then be used as a job parameter for submitting processes that have an account filter parameter. 

The benefits of this feature are:

• Reduced errors from automating a manual process.
• Increased efficiency from streamlining across external processes or systems.

Steps to Enable

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

Key Resources

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

Role And Privileges

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

Account Combination Shorthand Aliases Retrieval Using a REST API

Retrieve shorthand aliases for account combinations using the Account Combinations Shorthand Aliases List of Values REST API. You can search for an account combination using the shorthand alias. With this REST API, you can retrieve all shorthand aliases details for one or more charts of accounts.

The business benefits of this feature are:

• Reduced errors from automating a manual process.
• Increased efficiency from streamlining across external processes or systems.

Steps to Enable

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

Key Resources

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

Joint Venture Management

Joint Venture Overhead

Create user-defined rules to calculate overhead charges or management fees for managing partners of a joint venture to recover costs associated with managing the joint venture.

In this initial release, Joint Venture Management enables you to calculate overhead based on a percentage of the costs to be billed to joint venture partners, with the flexibility to process the calculated overhead as a cost recovery or as a revenue to the joint venture.

This enables the managing partner to:

• Conform to the joint operating agreement by ensuring accurate calculation and distribution of overhead and management fees associated with costs to be billed to the joint venture partners.

• Minimize month-end processing and reduce potential errors caused by manual entry through the use of automated processes.

Watch a Demo

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

Opt-in to Joint Venture Overhead in Joint Venture Management.

Watch a Setup Demo

Tips And Considerations

In an overhead method, you must identify the partner account before you can activate it. 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.
• For more information, refer to the Implementing Joint Venture Management guide.

Role And Privileges

To implement this feature, you will need the following job roles/privileges:

• Role
  • Joint Venture Accountant

• Privileges
  • Manage Joint Venture Overhead Methods
  • View Joint Venture Overhead Methods
  • Create Joint Venture Source Transactions
  • Manage Joint Venture Source Transactions
  • View Joint Venture Source Transactions

Performance Improvements in Creating Joint Venture Definitions and Processing Transactions and Distributions

Performance improvements in key automated processes across the joint venture life cycle including creating joint venture definitions from a rapid implementation spreadsheet, identifying joint venture transactions, creating joint venture distributions, and generating joint venture receivable invoices.

Save time and increase productivity with efficient joint venture processes.

Steps to Enable

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

Usability and Navigation Improvements for Joint Ventures

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

Enhancements include:

• Incorporation of intuitive and simplified application designs in the Joint Venture Distributions work area that focuses on an engaging user experience.
• Replacement of task name with task number in the Joint Venture Definitions work area.

The business benefits include:

• Improvements to the Joint Venture Distributions work area provide a streamlined and intuitive user experience to search, review and edit joint venture distributions prior to processing. 

• Replacement of task name with task number in the joint venture setup ensures accurate identification of project-related transactions for distribution.

Watch a Demo

Steps to Enable

To use the Joint Venture Distributions work area, an administrator must complete the following setup tasks:

1. Enable Oracle Search Extension Framework in the profile options. 
2. Run initial ingest process to build the indices (invoices and distributions) in the Oracle Search Cloud Service (OSCS) database and populate existing invoices and distributions data to the database.

All other enhancements are delivered enabled and do not require any action to be taken to use them.

Watch a Setup Demo

Tips And Considerations

1. The Joint Venture Distributions work area requires Oracle Search Extension Framework, which is delivered with your SaaS subscription.
2. Running the initial ingest process is typically a one-time task. Joint Venture Management requires two indices to load the data, one for invoices and the other for distributions. Therefore, you will need to run the process twice, once for each index.

Key Resources

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

Role And Privileges

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

Lease Accounting

End of Lease Processing

Lease Accounting provides tools that support the end of lease processing activities of managing options and terminating leases. As leases move through their life and come to the end of the term, lessees need to make decisions related to these activities, and each one may increase or decrease the lease term. For example, exercising a renewal option extends a lease, but exercising a termination option shortens the lease. Lessees can also opt to do nothing and let the lease end naturally. Each choice has an impact on the lease dates, liability balance, and right-of-use balance.

Manage Options and Terminate Leases Available from Actions

The business benefits include:

• Insights into upcoming options through the Lease Accounting dashboard.
• Reduce time and effort through the automated expiration of leases.
• Improve operational efficiency with streamlined lease termination and option management processes.

Watch a Demo

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

Tips And Considerations

Leases with upcoming end dates, upcoming options, and leases recently terminated are available on the Lease Accounting dashboard.

Key Resources

• Watch Manage Options and Terminations Readiness Training

Lease Disclosure Reports: Liability Analysis

Lease Accounting provides lease liability analysis reports to help lessees create the disclosures according to IFRS16 and ASC842 standards. These reports include discounted and non-discounted liability projections at the portfolio and lease level. The information is categorized by short-liability, one to five years, and greater than five years.

Lease Liability Analysis Report Available from the Drawer Panel

The business benefits include:

• Save time creating disclosures with better liability analysis.
• Make better decisions regarding future balance sheet impacts from leases.

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

Rapid Implementation for Lease Accounting

Complete setups required for Lease Accounting from a Rapid Implementation spreadsheet. Setups include Lease System Options, Lease Payment Templates, and Index Rates.

The business benefits include:

Adding multiple system options, discount rate indexes, and payment templates from one place increases efficiency, resulting in a faster implementation.

Steps to Enable

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

Offering: Financials

Role And Privileges

• The Manage Lease Configuration privilege is assigned to the Financial Application Administrator.  Please use this role to complete the Lease Accounting setup configuration through rapid implmentation.

Payables

Prevention of Split in Invoice Accounting When Funds Are Not Reserved

Prevent invoice accounting splits when the invoice contains both expense and non-expense distributions, and the non-expense distributions should not be reserved in Payables and General Ledger. This removes the need to configure subledger accounting rules to block the split of accounting journals during import into General Ledger.

With this feature:

1. A single journal entry is created for an invoice with both non-expense distributions that don’t require budgetary control and expense distributions that require budgetary control.
2. Budgetary control validation of non-expense distribution lines is assigned a funds status of Not Required.

Payables invoices can contain both expense and non-expense distributions. Payables does not reserve funds for non-expense distributions, but funds for non-expense distributions are reserved in General Ledger when the invoice journal accounting entries are posted to the ledger. The accounting entry for these invoices is split, with one journal entry created for the amount that is not reserved in Payables and a second journal entry for the amount already reserved.

View accounting for a budgetary controlled invoice in a single journal when there are expense and non-expense invoice distributions. When you enable this feature, non-expense distributions will no longer be budgetary controlled in General Ledger.

Steps to Enable

Create the lookup code XLA_PROMO_31698963_ON under the Subledger Accounting lookup type ORA_XLA_PROMOTIONAL_OPTIONS. This ensures that the invoice journal accounting entry is not split in General Ledger. You must create this lookup code in English.

Tips And Considerations

The following invoice distribution types are considered non-expense and are not subject to budgetary control when this feature is enabled:

• Accrual
• Recoverable Tax
• Tax Rate Variance / Tax Exchange Rate Variance
• Withholding

Budgetary control validation of non-expense distribution lines have a funds status of Not Required.

If you want to continue to budgetary control non-expense distributions, then don’t enable this feature.  Separate journal batches will be created and the non-expense journal lines will be budgetary control in General Ledger.

Recognition Rate Report for Image Invoices

Generate and review a report that indicates the recognition rate of invoice attributes created from imaging. Use the report to update setup data, such as supplier information, and to determine whether to implement adaptive learning on the invoices.

The new report is available in two formats.

1. Supplier Summary: In this format there are two sections. The first section shows a monthly overview of the recognition rates for the image invoice attributes which are further broken down into matched and unmatched invoice categories. The second section provides a summary for every combination of supplier and supplier site to analyze which suppliers have lower recognition rates and would need attention.

2. Invoice Details: This format also has two sections where the first section again provides a monthly overview of the recognition rates for the image invoice attributes. The second section provides an analysis of attributes for every invoice wherein the data recognized by IDR is compared with the data after the invoice is moved to complete state.

Report Parameters: The report has the following parameters:

• From / To Creation Date
• Business Unit
• Report Format

Analyze the recognition rate of header attributes for image invoices in multiple dimensions and identify areas that need improvement, either by modifying the configuration or by performing adaptive learning on the supplier invoices.

Steps to Enable

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

Tips And Considerations

1. The report analyzes the data for all invoices except those in the Incomplete status.
2. Cancelled invoices are not included in the computation of the recognition rate.
3. The report only analyzes the invoices accessible to the user who submits the report.

Role And Privileges

• The access to the report is controlled by the privilege "View Scanned Payables Invoices".

Forms 1099-MISC and 1099-NEC for Tax Year 2021

The Form 1099-MISC and the Form 1099-NEC have been updated according to the specifications published by the US Internal Revenue Service (IRS) for 2021. The following changes are made for tax year 2021:

• Box 11 in Form 1099-MISC

If you are in the business of purchasing fish for resale, you must report total cash payments of $600 or more paid during the year to any person who is engaged in the business of catching fish in Box 11. Use the income tax type MISC11 to report transactions in this box. Select the income tax type MISC11 in the supplier profile to default the value on the invoices automatically for such suppliers. Alternatively, select the income tax type MISC11 during invoice creation.

• Form 1099-NEC resized

The height of the form is reduced to accommodate 3 forms on a page.

There is no change in the process for generating the forms. Submit the process US 1099 Report to generate the paper Forms 1099-MISC and 1099-NEC. After the process is completed, click Republish. Select the Copy A and Copy B of the respective forms for printing. Here's a sample output of Form 1099-MISC Copy B:

Submit the process US 1096 Report after running US 1099 Report for generating Form 1096.

Submit the process US 1099 Forms (comma delimited format) to generate the output in comma delimited format. The output includes the amount for income tax type MISC11 in the following sequence:

Position	Data element
1	Payer's name
2	Payer's address line 1
3	Payer's address line 2
4	Payer's city
5	Payer's state
6	Payer's postal code
7	Payer's phone number
8	Payer's TIN
9	Supplier's TIN
10	Supplier's name
11	Supplier's address line
12	Supplier's city
13	Supplier's state
14	Supplier's postal code
15	Reserved
16	Reserved
17	MISC1 (box 1)
18	MISC2 (box 2)
19	MISC3 (box 3)
20	MISC4 (box 4)
21	MISC5 (box 5)
22	MISC6 (box 6)
23	MISC7 (box 1 of Form 1099-NEC)
24	MISC8 (box 8)
25	MISC9 (box 7)
26	MISC10 (box 9)
27	MISC11 (box 11)
28	Reserved
29	MISC13 (box 13)
30	MISC14 (box 10)
31	MISC15A (box 12)
32	MISC15B (box 14)
33	Reserved
34	Reserved
35	Reserved
36	MISC4 NEC (box 4 of Form 1099-NEC)

Form 1099-MISC and 1099-NEC comply with the IRS specifications for tax year 2021.

Steps to Enable

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

Tips And Considerations

• Select the income tax type MISC11 in the supplier profile to default the value on the invoices automatically for suppliers that must be reported in Box 11.

• If you have already entered transactions in 2021 which must be reported in Box 11, update the income tax type to MISC11 on the invoices. Note that you must update the income tax type on the invoice distributions, not on invoice lines.

• For updating all invoices of a supplier in a specific date range, use the Update and Report Income Tax Details process after updating the default income tax type in the supplier profile. Note that this process will update all invoices meeting the parameters, so make sure you select the supplier and date range carefully.

Key Resources

• For additional details about 1099 reports, refer to “Submit US 1096 and 1099 Reports” in Oracle Help Center.
• For instructions on Form 1099-MISC and 1099-NEC, refer to the IRS link: https://www.irs.gov/instructions/i1099mec

Role And Privileges

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

Electronic Filing of Forms 1099-MISC and 1099-NEC for Tax Year 2021

Generate electronic files for the Form 1099-MISC and the Form 1099-NEC according to the new specifications for tax year 2021 published by the US Internal Revenue Service (IRS). The following changes are made for tax year 2021:

FORM 1099-MISC

If you're in the business of purchasing fish for resale, you must report total cash payments of $600 or more paid during the year to any person who is engaged in the business of catching fish. Use the income tax type MISC11 for reporting such purchases. Select the income tax type MISC11 in the supplier profile to default the value on the invoices automatically for such suppliers. Alternatively, select the income tax type MISC11 during invoice creation.

FORM 1099-NEC

Starting from 2021, Form 1099-NEC is part of the Combined Federal/State Filing Program. If you enable combined filing, then the Form 1099-NEC includes K records for reporting state totals.

The electronic files for the Form 1099-MISC and the Form 1099-NEC comply with the IRS specifications for tax year 2021.

Steps to Enable

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

Receivables

Additional Attributes to Identify Receipts for Reversal Using the Receivables Standard Receipt SOAP Service

Specify additional attributes to identify receipts for reversal using the processReverseReceipt operation in the Receivables Standard Receipt SOAP Service. This enables unique identification of receipts for automated receipt reversal and helps reduce errors when there are duplicate receipt numbers.

Improve customer satisfaction by reducing receipt reversal errors and ensuring customer account balances are accurate.

Steps to Enable

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

Tips And Considerations

Use the receipt_id if there are cases where the receipt numbers being reversed may be the same.  This value can be obtained by using the Get operation in the Standard Receipts REST service.

Key Resources

For more information, refer to the following in the Oracle Help Center.

• About SOAP Web Services in Oracle Applications Cloud
• REST API for Common Features in Oracle Applications Cloud

AutoInvoice Interface Lines Review and Update Using a REST API

Review and update AutoInvoice interface line attributes using the Receivables Transaction Interface Lines REST API.

Use the Receivables Transaction Interface Lines REST service to get and update an interface line. You can perform these activities:

• Retrieve the details of a Transaction Interface Line.
• Update a Transaction Interface Line.
• Update Interface Header Information.
• Update Interface Line Information.
• Retrieve the details of an Interface Line Transaction Descriptive Flexfield.
• Retrieve the details of an Interface Header Information Descriptive Flexfield.
• Retrieve the details of an Interface Line Information Descriptive Flexfield.

Receivables Transaction Interface Lines: The AutoInvoice Interface Lines resource is used to retrieve and update the interface line.

Interface Line Transaction DFF: The Interface Line Transaction Descriptive Flexfields resource is used to retrieve the flexfield segments of the line transaction descriptive flexfield context for the interface line.

Interface Header Information DFF: The Interface Header Information DFF resource is used to retrieve and update the flexfield segments of the header attributes for the interface line.

Interface Line Information DFF: The Interface Line Information resource is used to retrieve and update the flexfield segments of the line information descriptive flexfield for the interface line.

AUDIT: The update on interface line using Receivables Transaction Interface Lines REST service can be Audited. In the Manage Audit Policies page, enable the Interface Line Audit option to capture the audit data.

You can view details about these services in the REST API for Oracle Financials Cloud guide

• Update AutoInvoice Interface data before importing invoices and other transactions.
• Create an audit trail to find the data mismatches between upstream and downstream products.

Steps to Enable

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

Key Resources

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

Role And Privileges

• You must create a new privilege access to use this feature:
  • Create a new privilege for the Interface service
  • Add the privilege to the user

Name: Manage Receivables AutoInvoice Interface Line via Rest Service

Code: AR_MANAGE_AUTOINVOICE_INTERFACE_LINE_REST_PRIV

Description: Retrieve and Update Auto Invoice Interface Lines via Rest Service.

Country-Specific Inbound Acknowledgment and Status Processing for Receivables Invoices Delivered in Universal Business Language 2.1 XML Format

Provide inbound acknowledgment and status processing for Receivables invoices delivered in Universal Business Language 2.1 XML format for Australia and France, in accordance with country-specific legal requirements.

The inbound response supports Universal Business Language (UBL) 2.1, over Pan-European Public Procurement On-Line (PEPPOL), an Electronic Data Interchange (EDI) protocol, using Business Interoperability Specifications (BIS) 3 format.  This feature can also meet other country requirements using these messaging specifications.

Steps to Enable

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

Tips And Considerations

• The invoice inbound status and error message can be viewed from the Manage Transactions page through the attributes XML Delivery Status and XML Delivery Error Message.

• The status values and error messages received through the inbound acknowledgment are mapped to the Receivables Lookups with Lookup Types XML_DELIVERY_STATUS and XML_DELIVERY_ERROR_MESSAGE respectively.  Predefined values are provided as part of this feature.  This list can be manually extended to support more values.

Credit Case Folder Business Events

Raise a business event when a credit case folder is created or needs a data refresh from external data sources.

You can subscribe to the following business events to receive a notification when a credit case folder is created or when a data refresh is requested on an existing credit case folder.

Supported Business Event	Description	Enable by Default
Credit Case Folder Created	The business event is published when a credit case folder is created.	No
Credit Case Folder Refresh Requested	The business event is published when a user clicks Refresh Data on the credit case folder.	No

A business event is a definable logical occurrence in a business scenario.  Here the business event is triggered when a credit case folder is created or a data refresh is requested. Use business events to perform operations in other systems based on these public events in the application. Your application administrator must enable business events before you can use them. After you enable the business events feature, the application sends a signal, along with a payload containing information about the business event, whenever the specific event occurs.

Attributes in the Payload for the Business Events 

The payload for both business events contains details about the specific credit case folder and the data points present in it. This table lists the attributes in the payload for both business events.

Attribute	Description
CaseFolderNumber	Credit case folder number.
CaseFolderStatus	Credit case folder status.
CaseFolderDescription	Credit case folder description.
CustomerName	Customer name on the credit case folder.
CustomerAccountNumber	Customer account number on the credit case folder.
Review Type	Source of creation of the credit case folder.
CaseFolderCreationDate	Credit case folder creation date.
CaseFolderLastUpdatedDate	Credit case folder last updated date.
Score	Credit score calculated using the scoring model and data point values for the customer.
CreditAnalystName	Credit analyst name.
CreditClassification	Credit classification of the customer or customer account.
CaseFolderTemplateName	Case folder template name.
SourceName	Source application from which the credit review originated.
SourceTransactionType	Source transaction type.
SourceTransactionNumber	Source transaction number.
RequestedAmount	Requested amount by the source transaction.
AvailableCredit	The credit amount that is currently available to the customer.
CurrentCreditLimit	The current credit limit amount assigned to the customer.
CaseFolderCurrencyCode	Credit case folder currency code.
DataPoint	Credit case folder data point information.

This table lists the child attributes of the parent attribute DataPoint.

Child Attribute	Description
DataPointID	The unique identifier of the data point.
DataPointName	The data point name.
DataPointDescription	The data point description.
SystemDerived	Indicates whether this data point is automatically calculated by the application.
Source	Indicates whether the data point comes from Collections, Credit Management, or a third party source.
Category	Category of the data point.
DataType	The type of data this data point stores.
Scorable	Option that indicates whether this data point can be used in scoring models.
DataPointValue	The data point value.

Integration developers and administrators can subscribe to business events from the Oracle Integration Cloud using the Oracle ERP Cloud Adapter. They can use the information in the payload to configure event handlers that perform business operations.

For example if you want to enable close to real-time credit data integration with external sources then subscribe to these two business events. Whenever a new credit case folder is created or a data refresh is requested for an existing credit case folder, you receive a notification about the event, along with a payload containing details of the case folder and the data points present in it. You can then pass the latest values from third-party external sources for the data points that can use them. This way the data points contain the most current data from external data sources.

For more information, refer to Oracle ERP Cloud Adapter Capabilities and Developing Integrations with Oracle Integration Cloud Service.

Steps to Enable

See Enable Business Events in the Use Cases section in the REST API for Oracle Financials Cloud guide on the Oracle Help Center.

Key Resources

• For more information on configuring and viewing business events for your service area of interest, refer to Understand the Oracle ERP Cloud Adapter.
• For more information on REST APIs, refer to the REST API for Oracle Financials Cloud guide in the Oracle Help Center.

Current Direct Debit Authorization Update on Existing Invoices Using a SOAP Service

Update the direct debit authorization on existing invoices where the debit authorization start date is later than the invoice creation date using the createUpdateCCToken operation on the Receivables Invoice SOAP Service.

Improve receipt processing by automating requisite direct debit authorization updates using the Receivables Invoice SOAP Service.

Steps to Enable

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

Customer Modification to Standard Receipts Using a REST API

Add or update customers on standard receipts using the Receivables Standard Receipts REST API.

Use the Standard Receipts REST API resource to update the customer details. With this service, you can:

• Add the customer details on a standard receipt using the update operation
• Change the customer details on a standard receipt using the update operation

You can view details about these services in the REST API for Oracle Financials Cloud guide.

The business benefits of this feature are:

• Increased value from integration with other existing software investments
• Reduced errors from automating a previously manual process
• Increased efficiency from streamlining across external processes or systems

Steps to Enable

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

Key Resources

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

Funds Transfer Error Code Bulk Removal on Failed Invoices

Remove Funds Transfer Error codes on failed transactions to reattempt automatic receipt processing of these transactions.

Pass the value Y for the ClearCreditCardErrors attribute for the Credit Card Token Update web service under the Receivables Invoice web service to clear the Funds Transfer Error codes from a failed transaction.

Transactions can fail automatic receipt processing due to credit card errors or customers updating their credit card payment details. Bulk clearing of credit card errors on failed transactions enables them for inclusion in the next run of automatic receipt processing.

Steps to Enable

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

Non-Invoice Related Channel Revenue Management Deduction Claim Creation for Lockbox with Remittance References

Provide automatic creation of non-invoice related Channel Revenue Management deduction claims for Lockbox receipts with remittance references provided.

The feature provides the following functionality for creation of non-invoice related underpayments:

• Enhancements to the feature Oracle Channel Revenue Management Integration with Oracle Receivables for Claim Creation and Settlement for Lockbox Receipts delivered in 21A.

• Enhancements to the existing Process Receipts Through Lockbox process to create Claim Investigation for the following:
  • Invalid remit references provided along with negative remittance applied amount to the lockbox data file for import.
  • Process Receipts Through Lockbox process has been submitted with the ESS parameter for Post Receipt with Invalid Transaction Reference as Unapplied as Yes with Claim.
  • The claim investigation activity defined at the lockbox receipt method’s remittance bank account is used as the default activity for the claim investigation application to the imported receipt.

All other feature considerations as delivered in 21A will remain.

Business benefits include:  Accelerate claim processing to quickly settle underpayments and overpayments, including processing all settlement-related financial transactions.

• Automatic deduction claim creation via the Lockbox process.
• Consistency with other receipt creation sources.
• Complete deductions settlement solution with automated integration between Channel Revenue Management and Receivables

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

Key Resources

• For more information on the Oracle Channel Revenue Management Integration with Oracle Receivables for Claim Creation and Settlement for Lockbox Receipts feature, click here

On-Account Credit Memo Creation Using a REST API

Create on-account credit memos without specifying an invoice or invoice line using the Receivables On-Account Credit Memo REST API.

You can create on-account credit memos with distributions, attachments, and notes. Additionally, you can capture information on credit memo lines and distributions using descriptive flexfields, including transaction flexfields and global descriptive flexfields.

Improve your customer service satisfaction by more efficiently processing customer on-account credit memos when integrating your on account credit memo creation activities across multiple systems. 

Steps to Enable

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

Tips And Considerations

The purpose and usage of this REST API is similar to the Receivables Invoice REST API.  Refer to the Use Cases section in the Oracle Help Center for more details.

Key Resources

For more information, refer to the following in the Oracle Help Center.

• REST API for Common Features in Oracle Applications Cloud
• REST API for Oracle Financials Cloud - Receivables Credit Memos
• REST API for Oracle Financials Cloud - Use Cases - Manage Receivables Credit Memos

Receipt Methods Retrieval Using a REST API

Retrieve receipt methods using the Get Receivables Receipt Method REST API. Use the Get action as the most efficient way to retrieve receipt methods for external systems.

Use the Get action in the Receipt Methods REST API along with other tools to build external user interfaces that require receipt method information, according to your business requirements.

Steps to Enable

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

Key Resources

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

Revenue Management

Revenue Allocation When Using Standalone Selling Price Ranges

Automatically determine whether the stated selling price for goods and services sold falls within or outside the Standalone Selling Price range, and assign the Standalone Selling Price value for the purpose of revenue allocation, according to company accounting policy.

You define the policy where you specify the unit standalone selling price to be used for allocation of the transaction price in each scenario.

CREATE STANDALONE SELLING PRICES SPREADSHEET

Standalone Selling Price Range

Upload the acceptable range of your standalone selling prices (the low and high points) using the Create Standalone Selling Prices spreadsheet. The Identify Customer Contracts process compares the selling price with the standalone selling price range to determine whether the selling price is below the low point, in range, or above the high point.

When you upload the standalone selling price midpoint and tolerance percentages, the Identify Customer Contracts process automatically calculates the standalone selling price low and high points.

Use the spreadsheet to upload the standalone selling price policies and ranges for your items, memo lines, performance obligation templates, or item groups.

Standalone Selling Price Policy for Ranges

The standalone selling price policy determines the rules you follow each time the Identify Customer Contracts process compares the selling price with the standalone selling price low and high points.

You can upload the policy that your business follows to determine the standalone selling price to be used for allocation while using standalone selling price ranges.  You must define the standalone selling price policy for the following three scenarios:

• Below low point (when the selling price falls below the standalone selling price low point)
• In range (when the selling price falls between standalone selling price low and high points; low and high points being inclusive)
• Above high point (when the selling price falls above the standalone selling price high point)

You can choose any of the following values for the above scenarios:

• SSP Low Point
• SSP Midpoint
• SSP High Point
• Selling Price
• Sales Point

The sales point represents the price published by the business as the published sales point of an item or service.

SSP Type

The SSP Type determines whether the unit standalone selling price is the observed value or estimated value. You can specify the SSP Type while uploading the standalone selling prices through the Create standalone selling prices spreadsheet.  The SSP Type is also displayed on the Customer Contract.  Prior to this release, the SSP Type was displayed in the Customer Contract as follows:

• The SSP Type of the unit standalone selling price observed by the system was displayed as the standalone selling price.

• The SSP Type of the unit standalone selling price uploaded through the Create Standalone Selling Prices spreadsheet was displayed as ESP, which indicates that it is an estimated selling price.

You can now specify either of the following when you upload standalone selling prices or a standalone selling price range:

• User Estimated SSP: Specify this value when the unit standalone selling price you upload determines that the standalone selling price is estimated by the user.

• User Observed SSP: Specify this value when the unit standalone selling price you upload determines that the standalone selling price is observed by the user outside the application.

The SSP Type of the unit standalone selling price observed by the application is now displayed as Observed SSP.

Create Standalone Selling Prices Spreadsheet

The following new attributes are added to the Create SSP spreadsheet:

• SSP Type: Specifies whether the unit standalone selling prices or ranges being uploaded are user observed or user estimated.

• SSP Low Point and SSP High Point: The low and high standalone selling price points that the selling price is compared with when you use the standalone selling price ranges.

• SSP Midpoint and SSP Tolerance: Used by the application to calculate the standalone selling price low and high points.

• Sales Point: Specifies the published sales point of the item.

• Below Low Point: Specifies the business policy when the selling price falls below the standalone selling price low point.

• In Range: Specifies the business policy when the selling price falls between the standalone selling price low and high points.

• Above High Point: Specifies the business policy when the selling price falls above the standalone selling price high point.

The Unit SSP attribute is no longer a required attribute when you use the standalone selling price ranges to derive unit standalone selling price.

Manage Standalone Selling Prices in Spreadsheet

You can manage standalone selling price ranges and the policy for standalone selling prices ranges through the Manage Standalone Selling Prices spreadsheet. You can edit values for standalone selling price ranges and policies for standalone selling price ranges in this spreadsheet if the standalone selling price range is not used in allocation. Once the standalone selling price range of an item is used in allocation, the record is marked In Use by the application and the values cannot be further modified.

Manage Standalone Selling Prices in Spreadsheet

You can see the changed and new attributes in the image above of the Manage Standalone Selling Prices spreadsheet.

Manage Customer Contracts Page

You can view the following new attributes in the Performance Obligations tab and the Promised Details tab of the Customer Contract page:

• Entered Unit SSP Amount: Displays the absolute value of the Unit SSP when the standalone selling price representation type is Discount Percentage of Unit List Price, Gross Margin, or Percentage of Base Unit Price.

• SSP Range Test Result: Displays the result of the comparison of the selling price with the standalone selling price low and high points. Possible values are Below the Low Point, In Range and Above the High Point.

• SSP Range Value Applied: Displays the range value applied based on the test result.  The possible values are SSP Low Point, SSP Midpoint, SSP High Point, Selling Price, or Sales Point.

Customer Contract Page

Let us see how the Unit SSP is derived for item On Premise Support in the above contract:

• The items On Premise Support and Cloud Support are assigned to a standalone selling price profile whose SSP representation type is Discount percentage of unit list price.

• The actual discount percentage for the item On Premise Support is 18.18%.  The SSP low and high points for this item as seen in the Create Standalone Selling Prices Spreadsheet image are 12% and 20% respectively.

• Since the actual discount percentage for the item On Premise Support falls between the SSP low and high points, the selling price is considered to be In Range.

• The Create Standalone Selling Prices Spreadsheet image displays the policy defined for this item when the selling price is In Range. According to the policy for standalone selling price ranges uploaded for this item, selling price has to be used as Unit SSP in this scenario.  Hence you can see the Unit SSP as 18.18% which is the same as the actual discount percentage.

Standalone Selling Price Profile

You can define default values for the SSP tolerance percentage and the policy for SSP ranges for a standalone selling price profile. These values default to all the items assigned to the SSP profile. You can override the values at the item level according to your business practices. These values default in the Create Standalone Selling Prices spreadsheet. As dictated by your business practices and policy changes, the default values of the SSP tolerance and SSP ranges can be overwritten by uploading the desired values through the worksheet.

Validations

The Create Standalone Selling Prices spreadsheet and the Manage Standalone Selling Prices spreadsheet validate the standalone selling price ranges and policy for standalone selling price ranges of the required attributes to ensure successful processing and assignment of the standalone selling prices.

These validations are applied only when the Unit SSP is blank. Some of the key validations are:

• When the Unit SSP is not blank, the SSP Midpoint, SSP Tolerance Percentage, Sales Point, and Policy for SSP Ranges are not required.

• The SSP Midpoint, SSP Tolerance Percentage, and Sales Point are not required attributes.

• Define the rules you choose for the Policy for SSP Ranges for the item. For example, you should provide a value for the Sales Point if you want to use the Sales Point as the Unit SSP in your SSP policy, such as when the selling price is Above the High Point.

The business benefits include:

• Address the industry practice of some industries, such as the software industry, where the standalone selling price is estimated as a range instead of an individual standalone selling price.

• Dynamically determine the unit standalone selling price based on the selling price for robust revenue allocation.

• Increase the productivity by automatically calculating the standalone selling price range, which is the standalone selling price low and high points when you provide the standalone selling price midpoint and tolerance percentage.

Steps to Enable

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

Tips And Considerations

• The selling price that you select for the policy for SSP ranges represents the following based on the SSP representation type of the item:  

  SSP Representation Type	What does Selling Price represent?
  Unit price	Unit selling price
  Discount percentage of unit list price	Actual discount percentage
  Gross margin	Actual gross margin percentage
  Percentage of base unit price	Actual base price percentage

• The SSP Type ESP has been renamed and is now displayed as User Estimated SSP.

Key Resources

• Refer to the Manage Standalone Selling Prices section of the Revenue Management user guide documentation for further information on how to upload and manage standalone selling prices.

Tax

First Party Tax Registration Number Default on Payables Invoices Created Manually

Assign the first party tax registration number by default to Payables invoices during either invoice creation or import for organizations with advanced legal structures. Advanced legal structures include, for example, a legal entity with multiple legal reporting units or an organization with different tax registration numbers defined for each legal reporting unit. An incorrect first party tax registration number can lead to incorrect tax calculation and reporting.

The First Party Tax Registration Number is stamped on the Validate Payables Invoice or Calculate Tax Click event.

Logic to stamp the First Party Tax Registration Number for the Payables Invoices created manually from the UI:

1. For non-India BUs  / LEs:

   1. Non-PO Matched Invoices:

      • If the BU/LE is associated with the reporting code ZX_ENABLE_FPTRN_DEFAULTING, then the First Party Tax Registration Number is derived using the logic introduced in 21B for AP Import Invoices.

      • If the BU/LE is not associated with the reporting code, ZX_ENABLE_FPTRN_DEFAULTING, then the default Registration Number of the Main LRU is stamped as the First Party Tax Registration Number. If there is no default Registration Number for the Main LRU, then no value is stamped for the First Party Tax Registration Number.

   2. PO Matched Invoices:

      • The default Registration Number of the Main LRU is stamped as the First Party Tax Registration Number. If there is no default Registration Number for the Main LRU, then no value is stamped for the First Party Tax Registration Number.  (This is the behavior whether or not the reporting code, ZX_ENABLE_FPTRN_DEFAULTING, is associated with the BU/LE.)

2. For India BUs/ LEs:

   1. Non-PO Matched Invoices (Same as non-India BUs  / LEs):

      • If the BU/LE is associated with the reporting code, ZX_ENABLE_FPTRN_DEFAULTING, then the First Party Tax Registration Number is derived using the logic introduced in 21B for AP Import Invoices.

      • If the BU/LE is not associated with the reporting code, ZX_ENABLE_FPTRN_DEFAULTING, then the default Registration Number of the Main LRU is stamped as the First Party Tax Registration Number. If there is no default Registration Number for the Main LRU, then no value is stamped for the First Party Tax Registration Number.

   2. PO Matched Invoices:

      • The First Party Tax Registration Number is copied from the PO/Receipt, whether or not the BU/LE is associated with the reporting code ZX_ENABLE_FPTRN_DEFAULTING.

Refer - https://www.oracle.com/webfolder/technetwork/tutorials/tutorial/cloud/r13/wn/fin/releases/21B/21B-financials-wn.htm#F17752

Enables companies to derive the correct First Party Tax Registration Number. An incorrect First Party Tax Registration Number can lead to incorrect tax calculation and reporting.

Steps to Enable

The first party tax registration number is defaulted as per the Logic described only when the appropriate Reporting Type Code is associated with the Business Unit / Legal Entity in the respective Party Tax Profile.

Steps to Associate:

A. Create the Reporting Type Code

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

     Tax Reporting Type Code    - ZX_ENABLE_FPTRN_DEFAULTING

     Tax Reporting Type Purpose - Tax reporting type

     Data Type - Yes or no indicator

     Start Date - <start date of the reporting type>.

3. Enable Reporting type use

     Party tax profile  - Enabled - Y

4. Save and Close.

Reporting Type Code Setup

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

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

BU and Reporting Type Code Association

Tax Reporting Code Association Using a REST API

Create tax reporting code associations for suppliers, supplier sites, customers, and customer sites using the Create Tax Reporting Code Association REST API.

Use the POST operation of the REST service to create the tax reporting code association.

The tax reporting code association can be created using REST API in an automated way reducing manual efforts.

Steps to Enable

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

Key Resources

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

Role And Privileges

• This REST Service is secured with the same privileges as the Party Tax Profile REST Service. Thus, a user who has the privileges to execute the Party Tax Profile REST Service would be able to execute this new REST Service as well.

Touchless Resubmission of Partner Transaction Data Extract

Automatically resubmit the data extract of Payables invoices and Receivables transactions to tax service providers for tax calculation when the first submission times out without a response. The automatic resubmission helps ensure proper tax calculation and helps prevent incomplete Receivables transactions and non-validated Payables invoices.

You can use this feature to ensure the incomplete Receivables transactions and non-validated Payables invoices are timely resubmitted to the tax partner.

Steps to Enable

To enable the feature, you need to run the Partner Transaction Data Extract with the parameters as:

• For Receivable Transactions:
  • Application Name - Receivables
  • Business Unit - <Applicable Business Unit>
  • From Transaction Date - (Optional) <start date of the transactions>
  • To Transaction Date - (Optional) <end date of the transactions>
  • Request ID - <0> (To process all the transactions); <negative value of the Auto Invoice Process> (To process the stuck records of a specific Auto Invoice Process)

• For Payables Transactions:
  • Application Name - Payables
  • Business Unit - <Applicable Business Unit>
  • From Transaction Date - (Optional) <start date of the transactions>
  • To Transaction Date - (Optional) <end date of the transactions>
  • Request ID - <0> (To process all the transactions); <negative value of the Partner Transaction Extract Process> (To process the stuck records of a specific Partner Transaction Extract Process)

NOTE:

• This process can be scheduled as per the business requirement.

• If the process id run with the Request ID parameter as NULL or Blank, then only the new transactions are processed and the re extraction of the stuck transactions doesn't happen.

Tips And Considerations

• This feature uses the existing Opt In options under the Lookup Type - ZX_OPTIN_OPTIONS, i.e., the lookup codes available for defining the transaction date range when no date range is populated in the Partner transaction data extract process schedule.

  PTNR_EXTRACT_LOW_DATE_AGE

  PTNR_EXTRACT_HIGH_DATE_AGE

  All invoices without a response from the tax partner between the PTNR_EXTRACT_LOW_DATE_AGE and PTNR_EXTRACT_HIGH_DATE_AGE would be re-extracted for tax processing. If these lookup values are not set, the default is considered as 1096 days before and 91 days after sysdate.

• Lookup Code PTNR_REEXTRACT_MIN_MAX_HOURS can be defined to change the default time_hour period i.e. 6_96 in format LowHours_HighHours. For Example, this lookup code can be set to 3_100 to pick up the transactions that are imported and stuck for more than 3 hour and less than 100 hours. Please note that the lower limit cannot be less than 3 hours i.e., even if this lower limit value given is smaller than 3, the transactions that are imported and stuck for more than 3 hours are considered.

Lookup code - PTNR_REEXTRACT_MIN_MAX_HOURS

Display Sequence - 1

Enabled - <Check Box Checked>

Start Date - <start date>

Meaning - 3_100

Description - Lookup for Partner Re Extract Min Max Hours

Tag - PTNR_REEXTRACT_MIN_MAX_HOURS

• Opt out Lookup Code PTNR_REEXTRACT can be defined and enabled to opt out of this touchless resubmission feature.

Lookup code - PTNR_REEXTRACT

Display Sequence - 1

Enabled - <Check Box Checked>

Start Date - <start date>

Meaning - PTNR_REEXTRACT

Description - Opt Out Lookup for Partner Re Extract

Tag - PTNR_REEXTRACT

• Steps to create the Lookup Codes:

  • Task - Manage standard Lookups

  • Lookup Type - ZX_OPTIN_OPTIONS

Description - <ZX_OPTIN_OPTIONS>

Meaning - <ZX_OPTIN_OPTIONS>

Module - Tax

Lookup Configuration Level - User

REST Access Secured - Secure

Regional and Country-Specific Features

Financials for the Americas

Brazil

Consolidated Discount and Price Adjustment Information in Fiscal Document Lines for Brazil

Use the enhanced Fiscal Document Extract for Brazil to consolidate discounts and price adjustments applied to sales orders in the corresponding line information in the fiscal document extract.

When you apply a price adjustment and a discount to a sales order item line, the Fiscal Document Extract for Brazil consolidates them into the same fiscal document line information. The extract process adds or subtracts the price adjustment to the price unit and line amount, and lists the discount amount in the existing TRADING_DISCOUNT tag.

Tax authority integration partners are no longer required to consolidate multiple lines to have an item line with related discount and price adjustments. In previous versions, the extract process created additional fiscal document lines for each price adjustment and discount in the extract, and tax authority integration partners were required to perform these consolidations.

Steps to Enable

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

Colombia

Transaction Number End Value Validation for Colombia

Incorporate and validate end values for Receivables transaction numbers in Colombia, as provided by the Colombian tax authority.

This feature provides these benefits:

• Helps ensure invoices are issued with transaction numbers within the approved sequence.
• Reduces the risk of non-compliance with the requirement of the Colombian tax authority.

Steps to Enable

1. Define the sequence end value in the Create Document Numbering for Colombia spreadsheet in the Manage Localization Document Numbering task.
2. Click Upload to save the changes.

Sequence End Value in Create Document Numbering for Colombia Spreadsheet

3. Receivables validates transactions with a transaction type associated with a document sequence having a defined sequence end value. The validation ensures that the sequence number doesn't go beyond the defined sequence end value. 

Transaction Number End Value Validation

Tips And Considerations

Receivables blocks completion of transactions created with a number greater than the sequence end value. You must create a new localization document numbering setup with a new sequence end value for the relevant transaction type.

Key Resources

• Related Help: Localization Document Numbering for Receivables Transactions Topical Essay in My Oracle Support (Doc ID 2579121.1).

Financials for Asia/Pacific

India

Receivables Transaction Number as Tax Invoice Number in the Electronic Invoice Flow for India

Provide the capability to use the Receivables transaction number as the India tax invoice number during electronic invoice processing. This simplifies the electronic invoice implementation for companies that do not require tax invoice number generation before shipment.

This feature lets you use the AR Invoice Number as the Tax Invoice number for India Bill-only flows instead of using India Document Numbering. The E-invoice process automatically uses the transaction status to pick the document number for E-invoice schema either from Receivables Transaction Number field or the India Tax Invoice Number field.

For FDG related flows this change is not applicable. Also it will not have any impact on Payables document numbering and Advanced Receipt flows for India.

When the setup for an India business unit uses the AR Transaction number as the Tax invoice number, the India Document Numbering setup is ignored and the process does not stamp an India document sequence in the invoice header global descriptive flexfield or in the line level Tax Invoice Number field.

This feature will ensure that India customers will have an alternative approach to configure India Document sequencing for India Bill only flows as per their business needs and will enable the India customers to adopt a more flexible implementation approach for India Tax Invoice Numbering. This feature will address below concerns of customers with the existing approach of India Document sequencing.

1. This feature gives the flexibility to customers who don’t want to have multiple document numbers for the same transaction and will be able to map the Indian document sequencing requirements with core capability of AR transaction Number.
2. This feature will enable users to apply cash receipts with reference to an AR Transaction Number and do not need to search for AR Tax invoice number while applying receipts to invoice. Customer is expected to quote the Tax document Number for accounting the inward supply and for payment
3. No additional configuration is required for India Einvoice process. The end to end process will process the change in India Document sequence setup based on which Einvoice Outbound process will pick up Tax Invoice as per schema requirements either from India GDF of receivables transaction or AR invoice number itself

Steps to Enable

To enable this feature, an additional option “Use AR Transaction Number as Tax Invoice Number” is introduced in ‘Manage Localization Systems Options’ setup to drive the logic of India Document Numbering for Bill only flows.

1. Sign in with a role who has access to that of an Application Implementation Consultant.
2. In the Setup and Maintenance work area, search for Task: Manage Localization System Options
3. Search for India Business Unit and Edit
4. Ensure that the flag: "Use AR Transaction Number as Tax Invoice Number" is set to 'Yes'
5. Save and close.

• This option is set to NULL by default, to ensure no impact to existing customers. When the option is set to NULL or No, an India Tax invoice number (document sequence number) is generated if the Enable Document Numbering option is set to Yes.

• If both options are set to Yes, or if the Enable Document Numbering option is set to No, then an India Tax invoice number is not generated.

Tips And Considerations

1. This change is applicable for Bill only Flows related to India Business Units. For FDG related flows this change is not applicable. Also it will not have any impact on Payables document numbering and Advanced Receipt flows for India.
2. If customer switches between Receivables Document sequencing and India Document Sequencing in the mid of the period, the system should not take accountability of gapless number. Customer should change the setup and it will be his sole responsibility to maintain gapless sequencing as per GST provisions.
3. The Einvoice process will not have any impact on its Error handling mechanism with this change. It will work as its working today.
4. Before uptaking this new feature, customers are recommended to complete the Einvoice(outbound+inbound) process for existing transactions.

Financials for EMEA

Common Country Features

Netting Agreement Update Using a REST API

Update the netting agreement using the Netting Agreement REST API. This helps handling large volume of agreements.

Additionally, you can create an agreement and search for existing agreements using this REST API.

Reduces manual effort to update a large volume of agreements.

Steps to Enable

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

Key Resources

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

Netting Settlements Scheduling

Schedule netting settlements according to organization business requirements to improve overall netting processing. You can now schedule the Generate Netting Settlements process using the standard scheduling functionality provided by Enterprise Scheduler Service (ESS).

Significantly reduces the manual effort for organizations that run the Generate Netting Settlements process on a daily or periodic basis.

Steps to Enable

To enable this feature, do the following:

1. Click Navigator > Others > Setup and Maintenance > Search > Manage Standard Lookups.
2. Search for the JE_ENABLE_FEATURE lookup type.
3. In the Lookup Codes section, add the NET_21C_OI_BATCH_SCHEDULE lookup code.
4. Click Save.

Tips And Considerations

The Generate Netting Settlements process now has two additional parameters - Schedule Multiple Times and Transaction Due Date Offset. To schedule the process to run multiple times, set the value of the Schedule Multiple Times parameter to Yes and enter the number of days in the Transaction Due Date Offset field. When the value of the Schedule Multiple Times parameter is set to Yes, you can't use the date fields. The settlement date, accounting date, and conversion rate date will be the same as the system date. The transaction due date will be calculated based on the value entered in the Transaction Due Date Offset field and the system date. For example, if the value is 5, the transaction due date will be calculated as five days from the system date. You can use the standard scheduling functionality provided by ESS to schedule the process based on your requirements. The settlement name for each run will be suffixed with a timestamp.

Here's an example:

The Generate Netting Settlements process is scheduled to run daily for the next three days. Let's assume today's date is 27-Apr-2021 and the value of the Transaction Due Date Offset field parameter is 5.

• For the process run on 28-April-2021, the settlement date, accounting date, and conversion rate date will be 28-April-2021. The transaction due date will be 3-May-2021, five days from 28-April-2021.

• For the run on 29-April-2021, the settlement date, accounting date, and conversion rate date will be 29-April-2021. The transaction due date will be 4-May-2021.

• For the run on 30-April-2021, the settlement date, accounting date, and conversion rate date will be 30-April-2021. The transaction due date will be 5-May-2021.

If you don't want to schedule the process, you can continue to use the process as before with the Schedule Multiple Times parameter set to No, which is also the default value for this parameter.

Key Resources

• Related Help: Netting topical essay

Germany

Asset Cost and Reserve Report for Germany

The Asset Cost and Reserve Report lists the asset cost and depreciation reserve balances at the asset, cost center, or statutory subcategory level. The report provides sorting and totals by asset category, asset type, cost account, cost center, statutory category, and statutory subcategory.

The Asset Cost and Reserve Report is enhanced to meet Germany’s statutory reporting requirement. You define two global segments, the statutory category and statutory subcategory in the Category Books descriptive flexfield. Specify the name of the statutory category and statutory subcategory for each asset category while assigning the asset categories to the asset book. Run the Asset Cost and Reserve Report in Germany’s statutory format from the Scheduled Processes page by selecting ‘Yes’ for the German Statutory Reporting parameter.

You can now print the Asset Cost and Reserve Report in Germany’s statutory format.

Steps to Enable

1. Define Statutory and Statutory Subcategory Segments.
   • In Setup and Maintenance, go to the task ‘Manage Fixed Assets Descriptive Flexfields’.
   • Search and edit the ‘Category Books’ descriptive flexfield.
   • Define the statutory category and statutory subcategory as global segments.

2. Specify which segment of the Category Books descriptive flexfield is the statutory category and statutory subcategory.

• In Setup and Maintenance, go to the task ‘Manage Fixed Assets Lookups’.
• Search for the lookup type ‘ORA_FA_STAT_CAT_SEG_T_CN’ and enter the table column used for the statutory category segment as the lookup code.
• Search for the lookup type ‘ORA_FA_STAT_SUBCAT_SEG_T_CN’ and enter the table column used for the statutory subcategory segment as the lookup code.

3. Enter statutory category and statutory subcategory values in the Edit Asset Categories page.

4. Select ‘Yes’ for the parameter German Asset Reporting when you run the Asset Cost and Reserve Summary Report.

Portugal

Invoice QR Code for Portugal

Generate and assign a QR code to customer invoices in accordance with Portuguese legal requirements.

This feature helps comply with the Portuguese legal requirement to create and print a QR code on all billing documents.

Steps to Enable

To enable this feature, do the following:

1. Click Navigator > Others > Setup and Maintenance > Search > Manage Standard Lookups.
2. Search for the JE_ENABLE_FEATURE lookup type.
3. In the Lookup Codes section, add the PT_21B_OI_QR_CODE lookup code.
4. Click Save.

Invoice QR Code for Portugal Standard Lookup

Tips And Considerations

You can print the QR code on Receivables transactions using either the Print Commercial Documents process or Print Receivables Transactions process.

To enable the Print Receivables Transactions process option, do the following:

1. Click Navigator > Others > Setup and Maintenance > Search > Manage Receivables Lookups.
2. Search for the ORA_AR_TRX_PRINT_REGIONS lookup type.
3. In the Financials Generic Lookup Type section, add the ORA_PORTUGAL lookup code.
4. Click Save.

Enable Print Receivables Transactions for Portugal

NOTE: You can use only one printing process at a time. If you have enabled the lookup for the Print Receivables Transactions process, you can’t use the Print Commercial Documents process for printing Receivables transactions for Portugal.

Key Resources

• Related Help: Invoice QR Code for Portugal and Cloud Certification for Portugal Topical Essays in My Oracle Support.

IMPORTANT Actions and Considerations

DEPRECATION OF EXPENSES SOAP SERVICES

The Expense Item and Expense Report SOAP services will be no longer be supported from Update 22B. You must transition to using Oracle REST APIs to manage expense item and expense report data stored in Oracle Fusion Financials Cloud. The following services related to Expenses will be desupported:

• Project Expense Allocation SDO
• Expense Report
• Expense Cost Center Allocation SDO
• Expense Distribution
• Expense Descriptive Flexfield SDO
• Expense Item
• Expense Report Descriptive Flexfield SDO
• Expense Company Allocation SDO

To view and manage expense item and expense report data, use the Expense Reports and Expenses REST API services.