TABLE OF CONTENTS

UPDATE 20A ···························································································································································································································· 2

Revision History ····················································································································································································································· 2
Overview ····································································································································································································································· 2
Optional Uptake of New Features (Opt In) ··························································································································································· 2
Feature Summary ················································································································································································································ 4
Financials ··································································································································································································································· 7
Advanced Collections ··································································································································································································· 7
Exclude Internal Invoices from Collection Activities ····················································································································· 7
Skip or Cancel Collections Strategy Tasks Using a REST Service ························································································ 7
Assets ····································································································································································································································· 8
Calculate Monthly Lease Interest for Nonmonthly Asset Lease Payments ·································································· 8
Bill Management ············································································································································································································· 9
Review Balance Forward Bill Details Using Bill Management ································································································ 9
Cash Management ······································································································································································································· 10
Reconcile Journal Lines for Multiple Cash Account Combinations ·················································································· 10
General Ledger ················································································································································································································ 11
Configurable Journal Workflow Notifications ·································································································································· 11
Prevent General Ledger Period Closure When Open Subledger Periods Exist ·························································· 12
Payables ······························································································································································································································ 13
Receive and Process Electronic Invoices Compliant with the European Standard EN 16931 ··························· 13
Payments ···························································································································································································································· 15
Capability to View Up to Six Digits of the Bank Account Number ····················································································· 15
Reevaluate Routing Rules During Receipt Remittance ············································································································· 16
Use Two-Factor Authentication for Inbound File Transmission ························································································· 16
Receivables ························································································································································································································ 17
Configurable Credit Memo Request Approval Workflow Notifications ·········································································· 17
Disallow Future Dated Invoices Created Manually When Chronological Document Sequence Enabled ·····
18
Override Default Scoring Models on Credit Case Folders ······································································································· 19
Recognize Scheduled In-Arrears Revenue After Payment is Received ·········································································· 19
Revenue Management ······························································································································································································· 21
Allocate Revenue to Promised Details Based on Extended Standalone Selling Prices ········································ 21
Tax ·········································································································································································································································· 23
Troubleshoot Missing Taxes on Transactions Using the Enhanced Tax Simulator ·············································· 23
Use Default Values When Tax Calculation Finds Inconsistent Tax Configuration ················································· 24
View Third-Party Details of Imported External Transactions ······························································································· 26
Transactional Business Intelligence for Financials ································································································································· 27
Enhancements to Receivables Subject Areas ································································································································· 27
Report on Active and Inactive Requestors in Payables Subject Areas ············································································ 27
Regional and Country-Specific Features ···························································································································································· 27
Financials for Asia/Pacific ······················································································································································································ 28
Enable Electronic Filing of GST Annexure-1 Per Revised GST Reporting Structure for India ························· 28
UPDATE 20A

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 Feature Notes

Tax: View Third-Party Details of Updated document. Delivered feature in

30 JAN 2020
Imported External Transactions update 20A.
06 DEC 2019 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.

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

2
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 in a
couple of ways:

Access the Opt In page from the New Features Work Area

1. Click the  Navigator, and then click  New Features (under the My Enterprise heading)
2. On the New Features page, select the offering that includes new features you’d like to review
3. Click  Go to Opt In for any feature you want to opt in
4. On the Edit Features page, select the  Enable option for the feature, and then click  Done

or...  Access the Opt In page from the Setup and Maintenance Work Area

1. Click the  Navigator, and then click  Setup and Maintenance

2. On the Setup page, select your offering, and then click  Change Feature Opt In
3. On the Opt In page, click the  Edit Features icon for any area that includes features you want to opt in
4. On the Edit Features page, select the  Enable option for any feature you want to opt in to. If the Enable
column includes an Edit icon instead of a check box, then click the icon, select your feature options, and
click  Save and Close. 
5. Click  Done.

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 release, 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. 

3
 FEATURE SUMMARY

Column Definitions:

Features Delivered Enabled

Report = New or modified, Oracle-delivered, ready to run reports.

UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential
impact to users is minimal.
UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.

Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to
enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features
must be assigned to user roles before they can be accessed.

Ready for Use by End Users Action is Needed BEFORE Use by End Users
(Features Delivered Enabled) (Features Delivered Disabled)

Reports plus Small Scale UI or Process-Based new features will Not disruptive as action is required to make these features
have minimal user impact after an update. Therefore, customer ready to use. As you selectively choose to leverage, you set
acceptance testing should focus on the Larger Scale UI or your test and roll out timing.
Process-Based* new features.

UI or UI or
Process-Based: Process-Based:
Feature Report Small Scale Larger Scale*
FINANCIALS
Advanced Collections
Exclude Internal Invoices from Collection Activities
Skip or Cancel Collections Strategy Tasks Using a
REST Service
Assets
Calculate Monthly Lease Interest for Nonmonthly
Asset Lease Payments
Bill Management

4
 Ready for Use by End Users Action is Needed BEFORE Use by End Users
(Features Delivered Enabled) (Features Delivered Disabled)

Reports plus Small Scale UI or Process-Based new features will Not disruptive as action is required to make these features
have minimal user impact after an update. Therefore, customer ready to use. As you selectively choose to leverage, you set
acceptance testing should focus on the Larger Scale UI or your test and roll out timing.
Process-Based* new features.

UI or UI or
Process-Based: Process-Based:
Feature Report Small Scale Larger Scale*
Review Balance Forward Bill Details Using Bill
Management
Cash Management
Reconcile Journal Lines for Multiple Cash Account
Combinations
General Ledger
Configurable Journal Workflow Notifications
Prevent General Ledger Period Closure When Open
Subledger Periods Exist
Payables
Receive and Process Electronic Invoices Compliant
with the European Standard EN 16931
Payments
Capability to View Up to Six Digits of the Bank
Account Number
Reevaluate Routing Rules During Receipt Remittance
Use Two-Factor Authentication for Inbound File
Transmission
Receivables
Configurable Credit Memo Request Approval
Workflow Notifications
Disallow Future Dated Invoices Created Manually
When Chronological Document Sequence Enabled
Override Default Scoring Models on Credit Case
Folders

5
 Ready for Use by End Users Action is Needed BEFORE Use by End Users
(Features Delivered Enabled) (Features Delivered Disabled)

Reports plus Small Scale UI or Process-Based new features will Not disruptive as action is required to make these features
have minimal user impact after an update. Therefore, customer ready to use. As you selectively choose to leverage, you set
acceptance testing should focus on the Larger Scale UI or your test and roll out timing.
Process-Based* new features.

UI or UI or
Process-Based: Process-Based:
Feature Report Small Scale Larger Scale*
Recognize Scheduled In-Arrears Revenue After
Payment is Received
Revenue Management
Allocate Revenue to Promised Details Based on
Extended Standalone Selling Prices
Tax
Troubleshoot Missing Taxes on Transactions Using
the Enhanced Tax Simulator
Use Default Values When Tax Calculation Finds
Inconsistent Tax Configuration
View Third-Party Details of Imported External
Transactions
Transactional Business Intelligence for Financials
Enhancements to Receivables Subject Areas
Report on Active and Inactive Requestors in Payables
Subject Areas
REGIONAL AND COUNTRY-SPECIFIC FEATURES
Financials for Asia/Pacific
Enable Electronic Filing of GST Annexure-1 Per
Revised GST Reporting Structure for India

6
 FINANCIALS

ADVANCED COLLECTIONS

EXCLUDE INTERNAL INVOICES FROM COLLECTION ACTIVITIES

Mark as internal Receivables invoice installments that you want to exclude from Collections Scoring, Strategy
Assignment, and Dunning.

Use these steps to exclude invoice installments with the value C from the Collections Delinquency
Management process and Collections Scoring and Strategy Assignments process:

1. Update the installment attribute “Exclude from Collections” to the value C using the Invoice Installments
REST service.
2. Run the Collections Delinquency Management process.
3. Run the Collections Scoring and Strategy Assignments process.

STEPS TO ENABLE

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

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.

SKIP OR CANCEL COLLECTIONS STRATEGY TASKS USING A REST SERVICE

Skip or cancel strategy tasks using the enhanced Collections Strategies REST service.

Use the Collections Strategies REST service to skip a task or cancel a task. You can perform these activities:

Retrieve the strategy template task details

Skip the strategy template task
Skip the strategy user task
Cancel the strategy execution task
Skip pre-execution wait time of a task
Skip post-execution wait time of a task

Strategy Execution Task: The strategy execution task resource is used to create current and completed tasks
for a collection strategy assignment.

Strategy Template Task: The strategy template task resource is used to retrieve all the future (to be
performed) tasks which are defined from Strategy template and template tasks that are skipped.

7
Strategy User Task: The strategy user task resource is used to create user tasks for collection strategy
assignments which are not available in a Strategy template.

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

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.

ASSETS

CALCULATE MONTHLY LEASE INTEREST FOR NONMONTHLY ASSET LEASE PAYMENTS

Calculate monthly accrued interest for leases with quarterly, semi-annual, or annual frequency. The
application calculates the present value based on the lease payment frequency, and then allocates the
calculated interest evenly to each month.

The Create Lease page includes a new option, Calculate monthly accrued interest. Normally, for a lease with a
nonmonthly payment frequency, for example, a quarterly payment frequency, the application accounts for
interest on lease liability at the end of each quarter as and when the payment occurs. As a result, there is no
interest expense in other accounting periods. When you enable the Calculate monthly accrued interest option,
the application accounts for interest on lease liability monthly instead of quarterly.

For example, you create a lease with a lease start date of 01-Jan-2019 and a payment frequency of quarterly.
The lessee makes lease payments for 2019 on 31 March 2019, 30 June 2019, 30 September 2019, and 31
December 2019. The application calculates the present value for quarterly frequency and generates either a
quarterly or monthly amortization schedule, depending on whether you enabled the Calculate monthly
accrued interest option.

Enabled: The application divides the interest amount for the first quarter by three and accounts for it on
31 January, 28 February, and 31 March.
Not enabled: The application accounts for interest on finance lease liability on these dates and there is
no interest expense in other accounting periods.

STEPS TO ENABLE

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

TIPS AND CONSIDERATIONS

Interest on Lease Liability: The application accounts for interest on lease liability in the amortization
schedule in the period in which interest due date falls. 

8
 Operating Lease Expense: For operating leases, the application also accounts for the operating lease
expense on each interest due date on the amortization schedule.
Converting Existing Leases:  You may have many leases with quarterly, semi-annual, or annual
frequency that were created before this release, and you want to convert them to use a monthly
accrued interest amortization schedule. You can perform a Change Financial Term or Reassessment
transaction on the Change Financial Terms page or using the Fixed Asset Lease Import file-based data
import template to enable this option.
When you enable the option by performing a reassessment transaction, the amortization
schedule starts from the current lease quarter. For example, if you perform a reassessment
transaction in May 2019, the amortization schedule starts in April and the Calculate Lease
Expenses process accounts for catchup interest expense for April. When you run the Calculate
Lease Expenses process for a period, the process begins calculating monthly interest from May.

NOTE: You must enable only the  Calculate monthly accrued interest check box in Change Financial Terms
page and you can’t modify any other lease attribute. Once you enable this option, it can’t be disabled.

When you enable the Calculate monthly accrued interest option:

The Generate Schedules process calculates the present value based on the lease payment frequency,
and then allocates the calculated interest evenly for each month in the quarter, half year, or year. The
amortization schedule includes the interest amount and liability for each month.
The calculated quarterly interest needs to be divided equally among the months in the quarter and
accounted for in the respective month.
You can enable or disable this option on the Edit Lease page only in the period the lease is added.

In a reassessment transaction, you can only enable the Calculate monthly accrued interest option and you can’
t disable if it is already enabled.

BILL MANAGEMENT

REVIEW BALANCE FORWARD BILL DETAILS USING BILL MANAGEMENT

Use Bill Management to view opening balance, payments, current charges, and credits and adjustments on
balance forward bills.

The Account Overview page contains a new Balance Forward Bills infotile with the customer’s balance forward
bills. Click the Due Amount value of a balance forward bill to view the bill details.

The details of a balance forward bill include:

Opening Balance: Displays the beginning balance of the balance forward bill.
Payments: Displays the payments received in the current billing cycle.
Current Charges: Displays the sum of current charges and late charges in the current billing cycle.
Credits and Adjustments: Displays the sum of credits and adjustments in the current billing cycle.

The Transaction History includes two new columns: Billing Number and Billing Date. These columns identify
the balance forward bill number and billing date of each transaction included in a bill.

9
 STEPS TO ENABLE

The feature is available for users of Bill Management who receive balance forward bills.
In the Manage Bill Management System Options page, enter in the Transaction History in Months field
the number of months to display for past balance forward bills.

ROLE INFORMATION

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

CASH MANAGEMENT

RECONCILE JOURNAL LINES FOR MULTIPLE CASH ACCOUNT COMBINATIONS

Reconcile journal lines of multiple cash account combinations matching the same natural account and other
specified segment values. Previously, only journal lines created for the complete cash account combination
were available for reconciliation.

In this example, when performing bank account reconciliation, Cash Managers will be able to manually or
automatically reconcile all journal lines entered on different account code combinations matching the same
natural account ‘1110’ and sub-account ‘0000’.

The Cash to General Ledger Reconciliation Report is also enhanced to display journal lines and closing
balances of such cash account combinations.

STEPS TO ENABLE

To enable this feature, perform the following steps: 

1. Navigate to the Setup and Maintenance work area.

2. Select the Financials offering.
3. Search for and select the Manage Bank Accounts task. 
4. Create or Edit the bank account.
5.

10
 5. Select Enable multiple cash account combinations for reconciliation option.
6. Select the GL Cash Account Segments you want to derive the corresponding segment values from the
bank account's cash account to retrieve multiple cash account combinations. 
7. Save and close the page.

TIPS AND CONSIDERATIONS

You must have the Journal Reconciliation Enabled profile option (CE_GL_RECON_ENABLED) set to
'Yes' to perform manual and automatic reconciliation of bank statement lines directly from GL Journal
Lines. 

Consider using the GL Recon Start Date as a beginning date of journal reconciliation for the bank
account.
The natural account segment is required and always selected as GL Cash Account Segment. Review and
select additional segments that qualify the bank account and you want to consider for retrieving
multiple cash account combinations. 
The closing book balance displayed in the Cash to General Ledger Reconciliation Report takes into
consideration multiple cash account combinations when this option is enabled for a bank account. 

KEY RESOURCES

For more information on Bank Statement and Reconciliation solution, refer to Oracle Financials Cloud Using
Payables Invoice to Pay, or Oracle Financials Cloud Using Receivables Credit to Cash.

ROLE INFORMATION

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

GENERAL LEDGER

CONFIGURABLE JOURNAL WORKFLOW NOTIFICATIONS

Use enhanced workflow notifications for journal approval. You can use Oracle Business Intelligence Publisher
templates to generate email and in-application notifications. Modify templates to meet business
requirements and policies. Choose from a comprehensive list of attributes to modify the notifications
according to your requirements. You can change both layout and content – add images, change colors and
styling, add or remove attributes or modify text.

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

TIPS AND CONSIDERATIONS

The templates used for the generation of the workflow notifications are located in the Reports and
Analytics > Shared Folders > Financials > Workflow Notifications folders.

11
 A single template is used to generate both the email and in-app notifications for a
particular workflow.  If you have chosen to use configurable notifications for both in-app and email
notifications for a workflow, any modifications that you make to the predefined template, will be
reflected in both types of notifications.

KEY RESOURCES

Overview of Financials Configurable Workflow Notifications on the Oracle Help Center.

Configuring Journal Email and In-App Notifications

PREVENT GENERAL LEDGER PERIOD CLOSURE WHEN OPEN SUBLEDGER PERIODS EXIST
Prevent the closure of a General Ledger accounting period if the accounting period for any of the
corresponding subledgers is still open, or if incomplete accounting entries or transactions exist for the
period.  This ensures an effective period close process by validating all transactions are complete and aren't
held up during the close. 

You can enforce the enhanced period close process on a primary ledger. When you enable this feature, the
period close process prevents the corresponding General Ledger accounting period from being closed if any
of the following exceptions exist:

Subledger accounting periods are not closed

Unprocessed and untransferred subledger transactions
Intercompany exceptions
Pending transactions in the General Ledger interface
Unposted transactions in General Ledger

You can exclude one or more of the following subledgers so the General Ledger period close process skips
any exceptions encountered within the context of the excluded subledgers:

Payables
Receivables
Revenue Management
Project Foundation

This feature provides the following business benefits:

Brings the General Ledger period close process in line with your corporate-wide business policy, if any.

Comply with the general business practice of not allowing a closed General Ledger period to be
reopened, unless there are material changes. In general, companies follow this practice unless there are
strong justifications and related approvals. By using this feature, you might not need to reopen a closed
accounting period, because you already ensured all unprocessed transactions and exceptions were duly
resolved before the General Ledger period was closed.

Provides more meaningful and accurate financial reporting, because all exceptions would have been
duly resolved and accounted for, before reporting.
Helps comply with audit requirements, if any.

12
STEPS TO ENABLE

To enable this feature for a primary ledger, perform the following steps:
1. Navigate to the Setup and Maintenance work area.
2. Select the Financials offering and General Ledger functional area.
3. Set the ledger scope for the Specify Ledger Options task and then select the task.
4. On the Specify Ledger Options page, select the Prevent General Ledger Period Closure When Open
Subledger Periods Exist option in the Period Close section.
5. Save and close the page.

To exclude one or more subledgers so the General Ledger period close process skips exceptions encountered
in those subledgers, perform the following steps:

1. Navigate to the Setup and Maintenance work area.

2. Select the Financials offering.
3. Search for and select the Manage General Ledger Lookup Values task.
4. Enter ORA_GL_INCLD_STRICT_PRD_CLOSE in the Lookup Type field and click Search.
5. For each subledger that you want to exclude, click in the Enabled field to deselect it.
6. Save and close the page.

TIPS AND CONSIDERATIONS

1. You are allowed to revert back to the pre-existing functionality by deselecting the Prevent General
Ledger Period Closure When Open Subledger Periods Exist option under the Period Close section on
the Specify Ledger Options page of a primary ledger.
2. By default, the General Ledger accounting period close process considers exceptions, if any, within the
context of all subledgers. You can optionally exclude one or more subledgers. Subledger inclusions
and exclusions apply to every primary ledger for which the Prevent General Ledger Period Closure
When Open Subledger Periods Exist option is enabled.

KEY RESOURCES

Watch Prevent General Ledger Period Closure When Open Subledger Periods Exist Readiness Training

Related Help:

Period Close chapter in the Implementing Enterprise Structures and General Ledger guide
Accounting Period Close chapter in the  Using General Ledger guide

ROLE INFORMATION

You don't need any new role or privilege access to set up and use this feature.

PAYABLES

RECEIVE AND PROCESS ELECTRONIC INVOICES COMPLIANT WITH THE EUROPEAN STANDARD
EN 16931
Receive and process electronic invoices compliant with the European electronic invoicing standard EN 16931
using UBL 2.1 XML format.

The European electronic invoicing standard EN 16931 is being adopted by governments and businesses
globally in order to streamline their procurement process.

13
A message definition for EN 16931 is available in the Collaboration Messaging Framework. The electronic
invoices sent by suppliers are received by Collaboration Messaging Framework and saved in the Payables
interface tables. You can then import the invoices by running the Import Payables Invoices process.

STEPS TO ENABLE

1. Navigate to the applicable supplier site and select Collaboration Messaging Framework in the B2B
Communication Method field.    

B2B Communication Method

2. In Associated Collaboration Documents, click Manage Trading Partners. Create a Trading Partner and
assign the predefined Message Definition "UBL_2.1_EN_16931_INVOICE_IN".     

3. In Associated Collaboration Documents, click the Edit button.  

4. Add the trading partner created in step 2 and add PROCESS_INVOICE_IN under Associated
Collaboration Documents.

14
KEY RESOURCES

https://docs.oracle.com/en/cloud/saas/financials/19d/fappp/invoices.html#FAPPP600176

ROLE INFORMATION

Users with the Accounts Payable Manager or Accounts Payable Supervisor role can configure trading
partners and service providers, and view message history from the Collaboration Messaging Framework work
area.

PAYMENTS

CAPABILITY TO VIEW UP TO SIX DIGITS OF THE BANK ACCOUNT NUMBER

Enables you to view the last six digits of the external bank account number. Currently you can view only the
last four digits. You need to change the masking settings in the Manage System Security Options to achieve
this.

STEPS TO ENABLE

1. Login with a user having administrative privilege.

2. Search for the task Manage System Security Options.
3. Select the hyper link to the Manage System Security Options.
4. Under Payment Instrument Masking, select 'Edit Masking' button against Bank Account Numbers.
5. The Edit Bank Account Masking pop up window will display. Select Masking Type as 'Display last
digits'.
6. Enter Number of Digits to Display as 6.
7. Select 'Save and Close' button.

15
REEVALUATE ROUTING RULES DURING RECEIPT REMITTANCE
Reevaluate routing rules for direct debit transactions during receipt remittance. Receipts can be routed using
different routing rules if the remittance bank account on the receipt has been changed by user during
remittance.

A new option 'Reevaluate routing rules' is available in the Create and Edit Funds Capture Process Profile
pages. When you enable this option, the routing rules are reevaluated during the remittance process. If the
remittance bank account on the remittance batch is different from the remittance bank account on the
receipts, then the receipts can be routed using different routing rules, if defined.

STEPS TO ENABLE

Enable the option 'Reevaluate routing rules' in the Create or Edit Funds Capture Process Profile page for the
applicable profile.

TIPS AND CONSIDERATIONS

It is recommended to enable this option when following two conditions are met:

1. You have the remittance bank account selected on the remittance batch and it is different from the one
on the receipts.
2. You use the remittance bank account as a criterion to configure routing rules.

USE TWO-FACTOR AUTHENTICATION FOR INBOUND FILE TRANSMISSION

Secure inbound transmission of acknowledgment file and bank statement using two-factor authentication.
You can configure authentication based on a security key in addition to user credentials in the transmission
configuration setup.

When you configure a transmission configuration using the Secure File Transfer Retrieval Protocol for Static
File Names protocol, you can attach the Client Private Key File and Client Private Key Password with the
transmission configuration. The private key file and password allow authentication based on a security key, in
addition to verifying user credentials.

16
STEPS TO ENABLE

In the Create or Edit Transmission Configuration page:

1. Create a configuration using the Secure File Transfer Retrieval Protocol for Static File Names protocol.
2. In the Parameters section, configure the Client Private Key File and Client Private Key Password.

TIPS AND CONSIDERATIONS

1. The imported key file is only visible in the Client Private Key File field if the file type is .ssh. An example
of a valid key file name is 110819_081326_fuscdrmsmc34.ssh. 
2. You must provide a value for the Client Private Key Password attribute.

RECEIVABLES

CONFIGURABLE CREDIT MEMO REQUEST APPROVAL WORKFLOW NOTIFICATIONS

Use enhanced workflow notifications for credit memo request approval. You can use Oracle Business
Intelligence Publisher templates to generate email and in-application notifications. Modify templates to meet
business requirements and policies.

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 20B

17
TIPS AND CONSIDERATIONS

The predefined template is used by default to present the workflow notification. You can copy and
modify this template according to your business requirements and set the modified template as the
new default.

Navigation for accessing the default template: Reports and Analytics - Shared Folders - Financials -
Workflow Notifications - Receivables - Billing

ROLE INFORMATION

You don't need any new role or privilege access to use this feature.
BI Administrator Role and BI Consumer Role have default permissions to access the report and modify
the predefined template.

DISALLOW FUTURE DATED INVOICES CREATED MANUALLY WHEN CHRONOLOGICAL

DOCUMENT SEQUENCE ENABLED
Disallow creation of invoices manually with future transaction and accounting dates when chronological
document sequencing is enabled on the ledger.

STEPS TO ENABLE

You enable this feature on the transaction type assigned to the invoice, by enabling the option 'No future
dates with chronological document sequencing'.

TIPS AND CONSIDERATIONS

This feature only applies to transactions created in a ledger that has chronological document
sequencing enabled. Additionally, the transaction types assigned to invoices must have the option 'No
future dates with chronological document sequencing' enabled.

Invoices created through the Import AutoInvoice process also use this feature to prevent the creation of
invoices with future dates.

ROLE INFORMATION

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

18
OVERRIDE DEFAULT SCORING MODELS ON CREDIT CASE FOLDERS
Change the default scoring model during credit review according to the requirements of your enterprise and
the customer. Case folder templates with scoring models are assigned based on credit classification and
review type. Changing the scoring model updates the credit score associated with the review.

You can update the scoring model in the Scoring Details page, based on the revised credit profile of the
customer:

STEPS TO ENABLE

This feature is automatically opted in through the release update. To configure the feature on the Scoring
Details page, you must add the new privilege for the required duty roles.

TIPS AND CONSIDERATIONS

The feature is available to users of Receivables Credit Management. The processes to manage the Credit
Case folder and derive the Credit Score remain the same.

ROLE INFORMATION

A new privilege is available in the context of the Scoring Details page and needs to be added for the required
duty roles based on the update authorizations given to specific users:

Update Credit Scoring Model in Case Folder (AR_MANAGE_CREDIT_SCORE) - to allow an update to the
Scoring Model attribute

RECOGNIZE SCHEDULED IN-ARREARS REVENUE AFTER PAYMENT IS RECEIVED

Recognize revenue on transactions that use the In Arrears invoicing rule after you receive payment. The In
Arrears rule normally recognizes revenue based on the predetermined revenue recognition schedule. You
can assign the transaction or transaction line a payment-based revenue contingency to temporarily defer
revenue recognition until payment is received.

19
STEPS TO ENABLE

To enable this feature, define a lookup AR_CONT_INV_INARREARS_RULE under the lookup type
AR_FEATURES.

20
TIPS AND CONSIDERATIONS

The configured contingency setup does not apply to Invoice lines with the revenue scheduling rules
Deferred Revenue option enabled. In this case, the invoice line amount is assigned to the Unearned
Revenue account by default. Because there is no contingency removal event, you must schedule
revenue manually using the Manage Revenue Adjustments page.
For partial receipt applications against an invoice, the amount allocated to the invoice line according to
the active Application Rule Set is considered for relieving the contingency. This applied amount is
further prorated across the revenue scheduling periods proportionate to the amounts deferred.
If any period is closed while creating the reversal entries, the amount is recognized in the next
available open period. Using the above example, if the January period were closed, then the amount
would be designated in the February period.
Activities against an invoice after the creation of revenue contingencies, such as credit memo
applications and adjustments, are treated as reductions against unearned revenue. The corresponding
amount is reversed from the unearned revenue account as part of the activity accounting.

ROLE INFORMATION

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

REVENUE MANAGEMENT

ALLOCATE REVENUE TO PROMISED DETAILS BASED ON EXTENDED STANDALONE SELLING

PRICES
Select the extended standalone selling price amount to allocate revenue within a performance obligation
using the new Performance Obligation template attribute, Allocation Basis. Control how performance
obligation revenue is distributed and recognized across the individual lines of the performance obligation.

Performance Obligation Template

When you select the Derive pricing dimension combination option in the performance obligation template,
you can now select the allocation basis: 

Extended SSP amount: When the allocation basis is set to Extended SSP amount, the performance
obligation level allocated revenue is distributed to the underlying promised detail lines for the
obligation using the ratio of the promised detail line’s standalone selling prices. 

21
 Selling amount: When you set the allocation basis to Selling amount or leave it blank, the Identify
Customer Contract process distributes the performance obligation level allocated revenue to the
underlying promised detail lines for the obligation using the ratio of the promised detail line’s selling
(line) amount.

Create Standalone Selling Prices Worksheet

To use the Extended SSP amount as the allocated basis, the Create Standalone Selling Prices worksheet is
modified to capture component selling prices for performance obligation templates. 

You upload the component selling prices for a performance obligation template and item combination for a
given pricing dimension, effective period, and currency.   The component selling price represents the selling
price of the item or service when it is sold as part of a bundle.

Alternatively, you can define the component selling price in the Unit SSP column on the source document
lines representing the bundle offering.

STEPS TO ENABLE

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

TIPS AND CONSIDERATIONS

When you use this feature:

You can modify the Allocation Basis option. The default value is blank.
The Allocation Basis option changes take effect from the time the changes are saved, and are
applied to all processing from that point forward.
The Allocation Basis option changes are not retrospectively applied.
When you change the Allocation Basis option from blank or Selling amount to Extended SSP amount:
The Identify Customer Contracts process applies the new logic from that point forward.
Changes apply only to new performance obligations created for the template.
The Identify Customer Contracts process distributes performance obligation level allocated
revenue to its underlying promised detail lines based on the ratio of the promised detail line
component selling prices. 
For source document lines associated with a bundle, the standalone selling price populated in
the Unit SSP column represents the component selling price and not the item or services
standalone selling price.
For performance obligations with promised detail lines in which the component SSP can’t be
assigned or is missing, the Identify Customer Contracts process marks the promised detail line
as missing SSP and sets the Contract Allocation Status to Not Allocated with an Allocation
Pending Reason of SSP Not Available.

22
 When you change the Allocation Basis option from Extended SSP amount to Selling amount or blank:

The Identify Customer Contracts process applies the new logic from that point forward.
Changes apply only to new performance obligations created for the template.
The Identify Customer Contracts process ignores the component selling prices on the promised
detail lines.
The Identify Customer Contracts process distributes performance obligation level allocated
revenue to its underlying promised detail lines based on the ratio of the promised detail line
selling (line) amount.

KEY RESOURCES

Refer to the Revenue Management documentation for further information on how to use performance
obligation templates and create standalone selling prices.

ROLE INFORMATION

No new role access is needed to use this feature.

TAX

TROUBLESHOOT MISSING TAXES ON TRANSACTIONS USING THE ENHANCED TAX SIMULATOR

Improve tax compliance by using the enhanced Tax Simulator to analyze why a particular tax was not
automatically calculated. Accurately identify the tax configuration errors and apply the corrective fix.

To troubleshoot taxes that were not calculated on a transaction:

1. Navigate to the Manage Simulator Transactions task.

2. In the Edit Simulator Transaction page, click the Create Tax Line button and enter the expected tax line
manually.
3. Navigate to the Tax Lines Details page to review the details of how tax calculation failed, including tax
applicability rules, direct rate rules, place of supply rules, and the rule conditions and transaction line
values for the tax line you entered manually.

23
STEPS TO ENABLE

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

ROLE INFORMATION

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

USE DEFAULT VALUES WHEN TAX CALCULATION FINDS INCONSISTENT TAX CONFIGURATION
Minimize run-time errors during transaction processing by allowing the tax engine to use predefined default
values for tax status, tax rate, and other tax line attributes when the process encounters an inconsistent tax
configuration. This helps improve auditability and allows tax specialists to correct the tax configuration.

In the following examples, the tax calculation process would normally end in error:

The tax rule specifies a tax rate with an end date prior to the tax determination date.
A quantity-based tax calculation cannot find a quantity-based tax rate for the unit of measure on a
transaction line.

After enabling this feature, tax calculation can continue using the predefined default tax rate for the tax that
resulted in the error.

Similarly, if tax processing leads to a tax status, recovery rate, taxable basis formula or tax calculation formula
that is not active on the tax determination date, the predefined default values would be used on the calculated
tax line or tax distribution.

If you provide a transaction header level tax control amount or transaction line level tax control amount, but
no applicable tax is found during tax processing, Oracle Tax creates a tax line using predefined default values
for the default tax regime and tax that you configured in the Manage Country Default Controls task.

Instead of using the values predefined by Oracle Tax, you can choose to specify the default values for tax rate,
tax status, tax recovery rate, taxable basis formulas, and tax calculation formulas to use in place of any
corresponding values that fail during tax processing.

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

Use the Feature Opt-In user interface to enable this feature.

24
 Enable the ‘Use application defaults’ option for your tax regime.

Enable the ‘Use application defaults’ option for your business unit or legal entity, depending on your tax
configuration subscription.

TIPS AND CONSIDERATIONS

Upgrading customers need to opt-in to enable the feature.

For new customers, this feature will be automatically enabled.
Once the feature is enabled, turn on the use of application defaults at both of the following levels:

25
 Party Tax Profile for the BU (or LE) that is a Configuration Owner in the Manage Party Tax
Profiles page.
Tax regime in the Mange Tax Regimes page.
For Configuration Owners and tax regimes for which the feature is enabled, the application default
configuration is created:
When a new tax is enabled for processing or simulation.
For all existing taxes that are enabled for processing or simulation by a system-scheduled
process.

ROLE INFORMATION

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

VIEW THIRD-PARTY DETAILS OF IMPORTED EXTERNAL TRANSACTIONS

View third-party details of external transactions on the Review Subledger Journals page after you import
them using the Tax Entry Repository Data Upload process.

STEPS TO ENABLE

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

TIPS AND CONSIDERATIONS

To view the third-party details of imported external transactions, here’s what you do:

1. Run Create and Assign Subledger Sources process.

2. Go to Navigator > Setup and Maintenance > Manage Accounting Attributes.
3. Check the third-party assignment at event class level for errors.
4. Update and check the accounting attributes on all journal line rules.
5. Go to Navigator > Setup and Maintenance > Manage Journal Line Rules.
6. Search for the required event class and select the appropriate result.
7. Go to the Accounting Attributes Assignments tab and select Third Party as the Accounting Attribute
Group.
8. Go to Navigator > Setup and Maintenance > Activate Subledger Journal Entry Rule Set Assignments.
9. Select the required attributes for Accounting Method and Subledger Application. 
10. Go to Navigator > Setup and Maintenance > Manage Accounting Methods.
11. Select the accounting method assigned on the Activate Subledger Journal Entry Rule Set Assignments
page and activate it.

After performing these steps, import the transactions using the Tax Entry Repository process and verify that
the third-party details of the newly imported transactions are shown on the Review Subledger Journals page.

NOTE: You can see the Activate button only for accounting methods that are inactive.

KEY RESOURCES

Manage External Taxable Transactions

Tax Entry Repository Data Upload Interface

26
 TRANSACTIONAL BUSINESS INTELLIGENCE FOR FINANCIALS

ENHANCEMENTS TO RECEIVABLES SUBJECT AREAS

Report on customer account descriptive flexfields in the Oracle Transactional Business Intelligence
Receivables - Transactions Real Time subject area. Customer account descriptive flexfields have been added
to the new subfolder Bill-to Customer Descriptive Flexfields, under the Bill-to Customer Account folder.

STEPS TO ENABLE

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

ROLE INFORMATION

No new role access is needed to use this feature.

REPORT ON ACTIVE AND INACTIVE REQUESTORS IN PAYABLES SUBJECT AREAS

Report on both active and inactive requestors in the Payables Invoices - Transactions Real Time and Payables
Invoices - Prepayment Applications Real Time subject areas. You report on requestors using the Purchase
Requestor columns:

Purchase Requestor Name

Purchase Requestor Last Name
Purchase Requestor First Name
Purchase Requestor Email Address
Purchase Requestor Display Name

in the Invoice Distribution Details - Purchase Order subfolder, under the Distributions folder, in the following
subject areas:

Payables Invoices - Transactions Real Time

Payables Invoices - Prepayment Applications Real Time.

Previous to this change, only active requestors were included for reporting.

STEPS TO ENABLE

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

ROLE INFORMATION

No additional roles required.

ATURES

27
REGIONAL AND COUNTRY-SPECIFIC FEATURES

FINANCIALS FOR ASIA/PACIFIC

ENABLE ELECTRONIC FILING OF GST ANNEXURE-1 PER REVISED GST REPORTING STRUCTURE
FOR INDIA

Enable filing of GST Annexure-1 electronically as required by revised GST reporting structure for India. The
extract contains details of all outward supplies, inward supplies liable to reverse charge, and imported goods
and services required for the annexure.

Filing Annexure-1(ANX-1) is mandatory for every GST registered taxpayer other than composite dealers, and
those organizations which are registered as Input service distributors (ISD).  GST Annexure-1 is used to report
suppliers GST liability on outbound taxable supplies and inward supplies where recipient is required to self-
assess/pay the GST (e.g. Inward supplies that attract GST on Reverse charge basis, inward supply of goods
imported to India etc.).

The Taxpayers can configure the BIP report based on the Tax Reporting Ledger tables' fields and can create
the report in the pre-described format so that it can be imported into the GSTN provided offline utility
tool.  User can use it to retrieve the outward supplies tax and integrate the outward supplies tax to GSTN
system.

The feature enables you to:

Run the GST Annexure-1 process which will extract the required dataset required for filing GST
Annexure-1 report from both Receivable and Payables modules.
Leverage the Global Tax Reporting Ledger (TRL) to create the India GST Outward supply Repository.
On this basis which, the ANX-1 report can be created in the GSTN prescribed format.
Create BIP report based on Tax Reporting Ledger tables’ data in the GSTN provided format of ANX-1
report.
Change only the BIP report data model logic in case of any future changes to the GST reporting format
of ANX-1 and not have any product dependency.
Effectively handle any Error, if notified by GST portal upon filing of ANX-1 report.

STEPS TO ENABLE

Setups required to enable this feature, associate the Taxes defined in the FSM into India Taxes Types so that
these taxes are separated out from the Non GST taxes and relevant information against each tax type can be
extracted while filing the monthly GST reports.

1. Application Implementation Consultant. role/privilege is required to do the setup

2. In the Setup and Maintenance work area, go to the Manage Taxes task:

Offering:  Financials Functional area:  Transaction Tax:  Manage Taxes

3. Search for the required Transaction tax.

4. Go to Tax Reporting Codes and Click on Add Row
5. Enter any of the following values to classify the Tax

28
 6. Click Save and Close

Process Steps:

1. Tax Manager role/privilege is required to run the Process.

2. In the Navigator work area, Go to Tools à Scheduled Processes à Schedule New Process

Search for the Job: Report Tax Liability Electronically for India Output Tax. Run the Process.

29
Parameters:

3. Tax Reporting Ledger Tables:

i. zx_rep_context_t
ii. zx_rep_trx_detail_t
iii. zx_rep_trx_jx_ext_t

              More details can be found in the below link:

https://docs.oracle.com/en/cloud/saas/financials/18b/oedmf/ZX-tables.html

30
 ZX_REP_CONTEXT_T:  With each run of ANX-1 Process, one record will be populated in this table against
the Request_Id of the job.

ZX_REP_TRX_DETAIL_T contains tax information for tax reporting purposes from Accounts Payable and
Accounts Receivable, and Tax repository.

ZX_REP_TRX_JX_EXT_T:  Summary Table for GST ANX-1 Report. It contains the ANX-1 Section
information against the transactions inserted into the table zx_rep_trx_detail_t

1.
31
TIPS AND CONSIDERATIONS

1. To create the GST ANX-1 BIP report data model, you will have to do a SQL join on the 3 Tax Repository
Ledger tables and Group the data based Table requirements of GST ANX-1 report format.

2. The minimum eligibility criteria of the Transactions to get picked by the Process are that Receivables
transactions should be in COMPLETE status and the Payables Invoices in ACCOUNTED status.
3. You are expected to write the logic of the BIP report data model such that it will fetch any Transaction
line having the Maximum Version Number for the ANX-1 reporting.

---

32
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as
expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish,
or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.
S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use,
duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or
documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous
applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all
appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC
International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The
Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are
not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement
between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content,
products, or services, except as set forth in an applicable agreement between you and Oracle.

33