Sei sulla pagina 1di 75

TABLE OF CONTENTS

UPDATE 20B ···························································································································································································································· 3


Revision History ····················································································································································································································· 3
Overview ····································································································································································································································· 3
Feature Summary ················································································································································································································· 5
Optional Uptake of New Features (Opt-In) ························································································································································ 10
Opt In Changes in This Update ············································································································································································ 10
Derive Bank Account Number from IBAN ········································································································································· 10
Retrieve Funds Capture Acknowledgment Files Using a Wildcard Search ··································································· 11
Streamlined Payment Processing ··························································································································································· 12
Common Technology and User Experience ······················································································································································ 12
Common Financials Features ················································································································································································ 12
Configure Workflow Rules Using Additional Project Attributes ·························································································· 12
Intercompany ············································································································································································································· 14
Configurable Intercompany Workflow Notifications ·················································································································· 14
Preview Intercompany Accounts Before Approving the Transaction ············································································· 14
REST APIs for Financials ··························································································································································································· 14
Receivables ·················································································································································································································· 14
Retrieve Customers, Customer Accounts, and Customer Sites Using a REST Service ········································ 14
Tax ····································································································································································································································· 15
Create Party Tax Profile Using a REST Service ······························································································································· 15
Financials ································································································································································································································· 16
Advanced Collections ································································································································································································· 16
Capture Notes for Collections Strategy Tasks ································································································································ 16
Employ Query By Example in Collector Searches on the Manage Resources Page ··············································· 17
Budgetary Control ········································································································································································································ 18
Maintain Account Hierarchy Levels for Budgetary Control Reporting Using File-Based Data Import ······ 18
Populate Control Budget Supplemental Segment Values by Range or Parent Value ·········································· 19
Synchronize Expense Budget Balances Across Budgetary Control and General Ledger Using File-Based
Data Import ··········································································································································································································· 20
Cash Management ······································································································································································································· 22
Drill Down to Bank Statement or External Transaction from OTBI ·················································································· 22
Expenses ···························································································································································································································· 22
Actionable Cards for Expense Reports ················································································································································ 22
Enable Maps with Oracle Maps Cloud Service ······························································································································· 24
Expenses Digital Assistant ·········································································································································································· 26
Request Cash Advances on Behalf of Other Employees ········································································································· 30
Split Expense Reports Across Projects and Accounts ················································································································ 31
General Ledger ··············································································································································································································· 35
Transfer Income Statement and Balance Sheet Account Balances to Different Closing Accounts ············ 35
Joint Venture Management ··················································································································································································· 35
Joint Venture Management ······································································································································································· 35
Payments ··························································································································································································································· 47
Settle Customer Receipts Using External Applications ············································································································ 47
Payables ····························································································································································································································· 48
Specify URL Attachments When Creating Supplier Invoices Using a Spreadsheet ··············································· 48
Receivables ······················································································································································································································· 48
Retain Receipt Method and Payment Instrument on Complete Transactions ························································· 48
Support Receivables Detailed Distributions for Invoices with Rules ··············································································· 48
Subledger Accounting ······························································································································································································· 53
Set Completion Status for All Journals in One Go and Pick Accounting Period While Importing
Subledger Journals ··························································································································································································· 53
Tax ·········································································································································································································································· 55
Highlight Configuration Elements That Aren't Optimized ····································································································· 55
Leverage Online Help During Tax Configuration and Tax Line Review ········································································ 55
Report Taxable Amount Based on Ledger Accounted Amounts in Tax Reporting ··············································· 56
Transactional Business Intelligence for Financials ································································································································· 57
Use Additional Attributes in Receivables Subject Areas ·········································································································· 57
Regional and Country-Specific Features ···························································································································································· 59
Financials for the Americas ··················································································································································································· 59
Brazil ······························································································································································································································· 59
Allow Multiple Bank Return Codes for Brazil ·································································································································· 59
Conditional Validation of State Inscription During Fiscal Document Generation Process for Brazil ········· 59
Financials for Asia/Pacific ······················································································································································································· 61
India ·································································································································································································································· 61
Extract Purchase Register and Complete Input Tax Recovery As per the Revised GST Reporting
Structure for India ······························································································································································································ 61
Japan ······························································································································································································································ 65
Process Lockbox Customer Payments Using Zengin Format for Japan ······································································ 65
Financials for EMEA ···································································································································································································· 69
Israel ································································································································································································································ 69
Process SHAAM Supplier Certificates for Israel ···························································································································· 69
Portugal ························································································································································································································ 70
Integrate Document Printing and Delivery for Portugal ··········································································································· 71
Spain ································································································································································································································ 72
Generate Online VAT Registers for Spain with Legal Format Changes ········································································· 72
Generate VAT Reports for Spain with Online VAT Registers for Spain Reporting Attributes ························· 73
Financials for Regional Localizations ······························································································································································ 73
Use SAF-T Data Extract to Report Source Documents, Payments and Assets ························································· 73

2
UPDATE 20B

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

Maintain Account Hierarchy Levels for


Updated document. Corrected Tips &
15 MAY 2020 Budgetary Control Reporting Using File-
Considerations information.
Based Data Import

Updated document. Added new section


24 APR 2020 Opt In Changes in This Update
highlighting changes to Opt In status.

Updated document. Added information


Integrate Document Printing and Delivery for
24 APR 2020 about Oracle ERP Cloud certification for
Portugal
Portugal.

Create Expense Items from Email


15 APR 2020 Feature not available in update 20B.
Receipts
06 MAR 2020 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

3
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

4
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*
OPTIONAL UPTAKE OF NEW FEATURES (OPT-IN)
Opt In Changes in This Update
Derive Bank Account Number from IBAN
Retrieve Funds Capture Acknowledgment Files Using
a Wildcard Search
Streamlined Payment Processing
COMMON TECHNOLOGY AND USER EXPERIENCE
Common Financials Features
Configure Workflow Rules Using Additional Project
Attributes

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*
Intercompany
Configurable Intercompany Workflow Notifications
Preview Intercompany Accounts Before Approving the
Transaction
REST APIs for Financials
Receivables
Retrieve Customers, Customer Accounts, and
Customer Sites Using a REST Service
Tax
Create Party Tax Profile Using a REST Service
FINANCIALS
Advanced Collections
Capture Notes for Collections Strategy Tasks
Employ Query By Example in Collector Searches on
the Manage Resources Page
Budgetary Control
Maintain Account Hierarchy Levels for Budgetary
Control Reporting Using File-Based Data Import
Populate Control Budget Supplemental Segment
Values by Range or Parent Value
Synchronize Expense Budget Balances Across
Budgetary Control and General Ledger Using File-
Based Data Import
Cash Management

6
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*
Drill Down to Bank Statement or External Transaction
from OTBI
Expenses
Actionable Cards for Expense Reports
Enable Maps with Oracle Maps Cloud Service
Expenses Digital Assistant
Request Cash Advances on Behalf of Other Employees
Split Expense Reports Across Projects and Accounts
General Ledger
Transfer Income Statement and Balance Sheet
Account Balances to Different Closing Accounts
Joint Venture Management
Joint Venture Management
Payments
Settle Customer Receipts Using External Applications
Payables
Specify URL Attachments When Creating Supplier
Invoices Using a Spreadsheet
Receivables
Retain Receipt Method and Payment Instrument on
Complete Transactions
Support Receivables Detailed Distributions for
Invoices with Rules
Subledger Accounting

7
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*
Set Completion Status for All Journals in One Go and
Pick Accounting Period While Importing Subledger
Journals
Tax
Highlight Configuration Elements That Aren't
Optimized
Leverage Online Help During Tax Configuration and
Tax Line Review
Report Taxable Amount Based on Ledger Accounted
Amounts in Tax Reporting
Transactional Business Intelligence for Financials
Use Additional Attributes in Receivables Subject Areas
REGIONAL AND COUNTRY-SPECIFIC FEATURES
Financials for the Americas
Brazil
Allow Multiple Bank Return Codes for Brazil
Conditional Validation of State Inscription During
Fiscal Document Generation Process for Brazil
Financials for Asia/Pacific
India
Extract Purchase Register and Complete Input Tax
Recovery As per the Revised GST Reporting Structure
for India
Japan

8
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*
Process Lockbox Customer Payments Using Zengin
Format for Japan
Financials for EMEA
Israel
Process SHAAM Supplier Certificates for Israel
Portugal
Integrate Document Printing and Delivery for Portugal
Spain
Generate Online VAT Registers for Spain with Legal
Format Changes
Generate VAT Reports for Spain with Online VAT
Registers for Spain Reporting Attributes
Financials for Regional Localizations
Use SAF-T Data Extract to Report Source Documents,
Payments and Assets

9
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:

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

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. Beyond the current release, the
Financials forums on Cloud Customer Connect have details of Opt In Expirations upcoming in future releases.

OPT IN CHANGES IN THIS UPDATE


The default opt in settings are changing for some features. Click on the feature name to get more
information.

Previously these features were delivered Disabled for end users, and could be activated using the Opt In page.
Beginning in Update 20B, these features are  automatically enabled for both new and existing customers.
However, both new and existing customers can still choose to opt out.

If you already enabled these features using the Opt In page, there is no change. 

DERIVE BANK ACCOUNT NUMBER FROM IBAN


This is an existing feature, originally available in Update 18C. There are no changes to the feature content, but
the Opt In status for this feature is changing. This feature is now enabled by default for all customers.  

For countries where the IBAN is used according to SWIFT (Society for Worldwide Interbank Financial
Telecommunication) guidelines, you can now create an external bank account by entering only the IBAN
instead of both the bank account number and the IBAN. When you save the external bank account, the bank
account number will automatically be derived from the IBAN according to the structure prescribed by SWIFT
and populates the Account Number field.

10
For additional details about this feature, please see:

https://www.oracle.com/webfolder/technetwork/tutorials/tutorial/cloud/r13/wn/r13-2018-financials-wn.
htm#F4365

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

This feature is enabled by default, but you can still disable the feature if required by following these steps:

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


2. On the Setup page, select Financials.
3. Click Change Feature Selection for Payments.
4. On the Edit Features: Payments page, deselect the  Enable icon for  Derive Bank Account Number from
IBAN feature.
5. Click  Done button on Edit Features

RETRIEVE FUNDS CAPTURE ACKNOWLEDGMENT FILES USING A WILDCARD SEARCH


This is an existing feature, originally available in Update 19C. There are no changes to the feature content, but
the Opt In status for this feature is changing. This feature is now enabled by default for all customers.

This feature allows retrieving multiple funds capture acknowledgment files at the same time using a wildcard
search.

For additional details about this feature, please see:

https://www.oracle.com/webfolder/technetwork/tutorials/tutorial/cloud/r13/wn/fin/releases/19C/19C-
financials-wn.htm#F8676

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

This feature is enabled by default, but you can still disable the feature if required by following these steps:

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


2. On the Setup page, select Financials, and then click  Change Feature Opt In
3. On the Opt In page, click the  Edit Features icon for Payments

4.

11
4. On the Edit Features page, select the  Disable option for “Retrieve Funds Capture Acknowledgment
Files Using a Wildcard Search”. 
5. Click  Done.

STREAMLINED PAYMENT PROCESSING


This is an existing feature, originally available in Update 18B. There are no changes to the feature content, but
the Opt In status for this feature is changing. This feature is now enabled by default for all customers.

Use this feature to simplify installments selection to ensure that selected installments are compatible with the
internal bank account and the payment process profile specified on the payment process request.

For additional details about this feature, please see:

https://www.oracle.com/webfolder/technetwork/tutorials/tutorial/cloud/r13/wn/r13-2018-financials-wn.
htm#F2371

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

This feature is now enabled by default, but you can still disable the feature if required by following these
steps:

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


2. On the Setup page, select Financials, and then click  Change Feature Opt In
3. On the Opt In page, click the  Edit Features icon for Payables
4. On the Edit Features: Payables page, select the  Enable icon for  Streamlined Payment Processing
 feature.
5. On the Feature Name: Streamlined Payment Processing pop-up window, select option  None and click 
Save and Close.
6. Click  Done on Edit Features: Payables page to return to the Setup: Financials page.

12
COMMON TECHNOLOGY AND USER EXPERIENCE

COMMON FINANCIALS FEATURES

CONFIGURE WORKFLOW RULES USING ADDITIONAL PROJECT ATTRIBUTES

Use project-related attributes to configure workflow rules, modify notification assignees, and set conditional
routing for notifications. These attributes let you route invoice approval notifications to project team
members, project task manager, and the hierarchy of the project task manager.

Here’s a list of project-related attributes that workflow administrators can use to configure invoice approval
workflow rules:

Project Task:

Task Name
Task Number
Task Organization
Task Manager
Project ID
Project Name
Project Number
Carrying Out Organization ID
Project Organization Name
Project Unit Name
Project Type ID
Project Type Name
Business Unit Name
Legal Entity Name
Work Type Name
Project Currency Code
Project Ledger Currency
Sponsored Flag
Project Classification
Project Team Member
Task Descriptive Flexfields
Project Descriptive Flexfields

Project Classification:

Project ID
Project Class Category
Project Class Code
Class Code Percentage

13
Project Team Member:

Project ID
Project Party ID
Team Member Role Name
Team Member Email Address
Team Member User Name
Team Member Start Date
Team Member End Date
Projects Track Time

STEPS TO ENABLE

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

TIPS AND CONSIDERATIONS

Click Start Synchronization on the BPM Rules Configuration page to synchronize project-related descriptive
flexfield information with the BPM workflow configuration. This operation lets you configure workflow rules
using project and task descriptive flexfield details

ROLE INFORMATION

Financial Application Administrator

INTERCOMPANY

CONFIGURABLE INTERCOMPANY WORKFLOW NOTIFICATIONS


Use enhanced workflow notifications for intercompany transaction 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

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

PREVIEW INTERCOMPANY ACCOUNTS BEFORE APPROVING THE TRANSACTION


Preview intercompany accounts in approval notifications and transaction pages for transaction types that
require manual approval. Approvers can validate the intercompany receivables account generated for the
provider and the intercompany payables account generated for the receiver before deciding to approve or
reject the transaction.

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

14
REST APIS FOR FINANCIALS

RECEIVABLES

RETRIEVE CUSTOMERS, CUSTOMER ACCOUNTS, AND CUSTOMER SITES USING A REST SERVICE

Retrieve customers, customer accounts, and customer sites using the Receivables Inquire Customer Accounts
and Sites REST Service.

You can:

Retrieve list of customers, customer accounts, and customer site details

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.

This feature is automatically opted in through the release update. To configure the feature, you must add the
new privilege for the required duty roles accessing the services.

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 (http://docs.oracle.com).

ROLE INFORMATION

A new privilege is available in the context of the customers, customer accounts, and customer site details and
needs to be added for the required duty roles based on the authorizations given to specific users:

Allows the user to view customer, customer account, and customer site information
(AR_VIEW_CUSTOMERS_PRIV)

TAX

CREATE PARTY TAX PROFILE USING A REST SERVICE


Create party tax profiles for suppliers, supplier sites, customers, and customer sites using the Create Party
Tax Profile REST Service.

Use the POST operation of the REST service to create party tax profiles.

STEPS TO ENABLE

Review the REST service definition in the REST API guides, available from the Oracle Help Center > Financials
> 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

15
FINANCIALS

ADVANCED COLLECTIONS

CAPTURE NOTES FOR COLLECTIONS STRATEGY TASKS

Create and view notes associated with Collections strategy tasks. This improves collectors' productivity when
processing strategy tasks.

You can determine whether a note is created for a strategy task based on the icons displayed in the Notes
column of the Strategy Task Details table. Notes for a strategy task have the same look and feel as the notes
at the transaction, account, and site level.

When a note is created for a strategy task, the page displays a Notes Exist icon. Click this icon to view
existing notes and to create additional notes.

If a strategy task does not have a note, use the plus icon to create a note.  Click this icon to create a
note.

16
STEPS TO ENABLE

To enable this feature, perform the following steps:

1. Click Navigator > Setup and Maintenance > Manage Standard Lookups.
2. Define the lookup code with below details:

Lookup type: IEX_FEATURES

Lookup code: IEX_STRATEGY_TASK_NOTES

TIPS AND CONSIDERATIONS

Enable this feature if you have a business need to create standard notes for collections strategy tasks.

EMPLOY QUERY BY EXAMPLE IN COLLECTOR SEARCHES ON THE MANAGE RESOURCES PAGE


Query By Example is available on the Manage Resources page, providing enhanced collector search
capability.

17
The Query By Example icon appears in both the Collectors section and Customers section of the Manage
Resources page:

In the Collectors section, use Query By Example to search on collector names and other details,
including total delinquencies, delinquencies, and average delinquencies. 
In the Customers section, use Query By Example to search on customer names and other details,
including total delinquencies, delinquencies, and total amount due.

You can search and select collectors from the Reassign Customer and Reassign Collector windows. The drop-
down list in the Collector To field in these windows is enhanced to include the most recent collectors searched
and the Search link for searching the complete list of collectors.

STEPS TO ENABLE

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

BUDGETARY CONTROL

MAINTAIN ACCOUNT HIERARCHY LEVELS FOR BUDGETARY CONTROL REPORTING USING FILE-
BASED DATA IMPORT
Assign tree labels to segment values in the Segment Values and Hierarchy File-Based Data
Import.  Application administrators can label segment values to indicate at which hierarchy level to enforce
budgetary controls.   This eliminates the need to create the tree labels separately using the application page.

STEPS TO ENABLE

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

TIPS AND CONSIDERATIONS

Download an updated Import Segment Values and Hierarchies template from the File-Based Data
Import for Financials guide.
To assign a new or an existing label in the Manage Account Hierarchy Labels page, use the Label Short
Name column of the Import Segment Values and Hierarchies template.

18
Manage Account Hierarchy Labels

To remove existing labels assigned to a segment value, enter $null$ in the Label Short Name column.
For more information on advance hierarchy structures, see the instructions in the Rapid
Implementation for General Ledger spreadsheet.

KEY RESOURCES

To download the template, go to the Import Segment Values and Hierarchies section in the Oracle
Financials Cloud File-Base Data Import for Financials.

To download the Rapid Implementation for General Ledger spreadsheet, use the setup task Create
Chart of Accounts, Ledger, Legal Entities, and Business Units in Spreadsheet.

ROLE INFORMATION

You need one of these roles to maintain account hierarchies using the Import Segment Values and
Hierarchies template:

Financial Application Administrator


Financial Integration Specialist

POPULATE CONTROL BUDGET SUPPLEMENTAL SEGMENT VALUES BY RANGE OR PARENT


VALUE
Budget managers can quickly enter segment values for control budget supplemental rules using a range of
values or a parent value.  Use the Add Values By button to enter segment values for control budget segments
at the detailed and parent value level. Use the Add Values By button to enter segment values for additional
segment filters at the detailed value level.

19
Create Supplemental Rules

STEPS TO ENABLE

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

TIPS AND CONSIDERATIONS

It is recommended that you enter ranges that contain less than a few hundred valid values. If you enter a
large range, it impacts the search performance.  For example, to create a supplemental rule for departments
that work on capital projects having thousands of department values, enter smaller ranges to fill in the values
incrementally.

KEY RESOURCES

Refer to the Oracle ERP Cloud Budgetary Control and Encumbrance Accounting Implementation Guide for
more information on control budgets and supplemental rules.

ROLE INFORMATION

You need the budget manager role to access the Manage Control Budget page.

SYNCHRONIZE EXPENSE BUDGET BALANCES ACROSS BUDGETARY CONTROL AND GENERAL


LEDGER USING FILE-BASED DATA IMPORT
Create and synchronize expense budget balances in primary ledgers for both budgetary control validation
and for General Ledger reporting and inquiry using single period file-based data import. You can prepare and
load the expense budget data file once and then simultaneously update the budget balances in both
Budgetary Control and General Ledger. You can also continue to load budget into Budgetary Control and
General Ledger separately.

STEPS TO ENABLE

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

20
TIPS AND CONSIDERATIONS

Download the updated Budgetary Control Budget Import template from the File-Based Data Import for
Financials guide and follow the updated instructions to use the Import Budget to Budgetary Control and
General Ledger process.

This feature will be incrementally enhanced in future releases. 20B Update has these restrictions:

1. Budget currency must be the same as the ledger currency.


2. Control budget calendar must be the same as the accounting calendar.
3. Budget is for expense accounts only.
4. Control budget must contain all segments of the chart of accounts.  
5. Budget must be at detailed account values. 
6. Budget amounts can only be overwritten. Incremental mode is not supported.
7. Budgets cannot be loaded into adjustment periods.

Review the full list of restrictions in the Overview section in the Instructions worksheet of the updated
Budgetary Control Budget Import template.

You can continue to use the current methods to load budgets separately. The Budgetary Control Budget
Import template has additional instructions but no new columns. You can use existing sheets without any
change.

Template Process Result

Budgetary Control Budget Import (New) Import Budget to Budgetary Load budget into Budgetary Control
Template Control and General Ledger and General Ledger simultaneously.

Budgetary Control Budget Import


Import Budget Amounts Load budgets into Budgetary Control.
Template

General Ledger Budget Balance


Validate and Upload Budgets Load budgets into General Ledger.
Import Template

KEY RESOURCES

For more information on loading budgets into Budgetary Control and General Ledger, see these resources:

To retrieve the template: File-Based Data Import for Oracle Financials Cloud Budgetary Control Budget
Import
Budgetary Control Budget Import template: Instructions worksheet

ROLE INFORMATION

To run the Import Budget for Budgetary Control and General Ledger process, the user must have one of
these roles:

Budget Manager
General Accounting Manager
General Accountant

21
CASH MANAGEMENT

DRILL DOWN TO BANK STATEMENT OR EXTERNAL TRANSACTION FROM OTBI


Drill down from Oracle Transactional Business Intelligence (OTBI) reports to Bank Statement or External
Transaction. Add an action link on a column, such as Statement or Transaction number, to enable the drill
down using a deep link. A deep link is a URL to open a page without navigating through the application menu
structure. Team members can easily navigate back and forth from the analysis to the application to review
details.

Links can be configured in the ad hoc Cash Management OTBI reports to drill down to the following pages:

View External Transaction


Edit External Transaction
View Bank Statement
Edit Bank Statement

STEPS TO ENABLE

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

ROLE INFORMATION

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

EXPENSES

ACTIONABLE CARDS FOR EXPENSE REPORTS


Easily find expenses and expense reports that require your action from the list of reports presented in a
carousel display in the Expenses work area.

Each report that is in progress or requires action is presented as a card in the Expenses work area. The
Expenses work area displays a maximum of 25 cards in the carousel display. The Create Report card is always
the first card in the carousel display. All other cards are organized by their statuses. Cards that require an
action are displayed first, followed by the cards that are in progress, in approval, and paid. Each card displays
the expense report status, report purpose, report number when purpose is not available, and report amount.
Reports that are pending approval display the approver information. You can take actions, such as Withdraw,
Resubmit, Duplicate, Delete, and Print, directly from the card. The Show All link navigates you to the Manage
Expense Reports page where you can search for additional reports.

Additionally, the tiles that earlier displayed the counts for cash advances, spend authorizations, and approvals
are now replaced by the navigation bar on the left side of the Expenses work area. The search field on the top
right corner of the work area enables you to search for expenses and expense reports. You can access tasks,
such as Advanced Search, Manage Bank Accounts, and Manage Delegates, from the Settings icon in the top
right hand corner of the Expenses work area.

22
Actionable Cards in Expenses Work Area

The Expenses work area now highlights the corporate card charges from a previous assignment. When you
navigate to the Expenses work area, a banner appears in the work area if you have outstanding corporate card
charges from a previous assignment. To add these charges to a report and submit them, navigate to the
Manage Expense Reports page by clicking the Resolve button in the banner.

Expenses Work Area with Outstanding Transactions Banner

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

23
ROLE INFORMATION

To enable Actionable Cards for Expense Reports, you must have the Application Implementation Consultant
role. When enabled, users with the Employee role can use the feature.

ENABLE MAPS WITH ORACLE MAPS CLOUD SERVICE


Calculate trip distance in mileage expense entry using Oracle Maps Cloud Service. Expense managers can
configure preferred locations to allow employees to easily select destinations in Oracle Maps. Additionally,
employees can enter the commute distance, which is deducted from the total distance to derive trip distance
eligible for mileage reimbursement.

When Oracle Maps Cloud Service is enabled for your business unit, the application displays the Use Map
button to navigate to Oracle Maps when you select a mileage expense type. On the Oracle Maps page, you can
enter start location, subsequent stops, and the end location. The Location drop-down displays both preferred
locations and the recently used locations. Your company can set up its own preferred locations.

Accessing Maps from the Create Expense Item Page

24
Preferred Lists

If your company requires you to deduct commute mileage, the Deduct commute distance check box is
displayed and the distance between your home and office is automatically populated if it exists in your profile.
You can change the commute distance when applicable.

When you submit your expense report, a snapshot of your Oracle Maps with the route is attached to the
expense report as a supporting document. The map doesn’t display actual addresses. The map attachment is
also visible to expense report approvers and auditors.

STEPS TO ENABLE

To enable Oracle Maps, perform the following steps.

1. From the Setup and Maintenance work area, navigate to the Manage Expenses System Options page.
2. Set the Enable Oracle Maps choice list to Yes.

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

To enable commute mileage in mileage expense entry, perform the following steps:

From the Setup and Maintenance work area, navigate to the Manage Policies by Expense Category
page.
Select the Mileage option from the Create Policy button choice list.

25
In the Mileage Eligibility Section on the Create Mileage Policy page, select the Enable commute mileage
deduction check box.
Select the Optional radio button if you don't need to deduct commute mileage always. Select the
Required per day radio button if it is mandatory to deduct commute mileage from your mileage
expenses. Employees must enter commute mileage if you set the value to Required per day.

To setup preferred locations, perform the following steps:

From the Setup and Maintenance work area, navigate to the Manage Standard Lookups page.
Search for the lookup type ORA_EXM_MILEAGE_LOCATIONS.
In the Lookup Codes section, select the Create icon to create lookup codes. Each lookup code is a
preferred location. In the Meaning field enter the short name of the preferred location and in the
Description field enter the location address. The address must be a valid physical address, so that the
map can calculate the distance correctly.
Click Save and Close.

KEY RESOURCES

Watch Enable Maps with Oracle Maps Cloud Service Readiness Training

ROLE INFORMATION

To enable the Oracle Maps and a mileage policy with commute deduction, you need one of these roles:

Expense Manager
Application Implementation Consultant
Financials Administrator

EXPENSES DIGITAL ASSISTANT


Create expense items automatically by texting receipt images to the Expenses Digital Assistant. The Digital
Assistant either provides immediate confirmation that the expense item is created or asks for specific
guidance to complete the expense item. Expense items are automatically matched to corporate card charges
when applicable. If configured, the application automatically submits expenses for approval.

When you use the Digital Assistant, you can create expenses using conversational phrases, such as "meal 30$
today" or "create a taxi expense". The Digital Assistant asks you for additional information based on your
company’s policies.

You can also create an expense by uploading a receipt. The Digital Assistant extracts the information from the
receipt and presents it to you for verification. You can modify the expense details using phrases, such as
“change amount to 20$” or “date is 02/14/2020”. After verification, you can complete the expense creation by
providing a security code provided by the Digital Assistant.

If you are a corporate card user, the Expenses application waits for the corporate card charge for 5 days and
tries to match the expense created from the Digital Assistant to a corporate card charge. Your company can
enable automatic submission of expense items created from the Digital Assistant.

Expenses Digital Assistant is currently supported on SMS (text messaging) channel. 

26
27
28
Creating Expense Using SMS Channel

To use this feature, you must purchase the Oracle Digital Assistant for Fusion Enterprise Resource Planning
Self Service Cloud Service - Hosted Named User SKU with part number B91448.

STEPS TO ENABLE

To enable Expenses Digital Assistant, perform the following setup:

1. Identify Digital Assistant administrators and assign them respective roles. Refer to the Digital Assistant
User Roles section of the Configure Digital Assistant chapter in the Getting Started with Digital Assistant
guide.
2. Log in as ODA Service Administrator, select the latest version of the FADigital Assistant, and train the
Digital Assistant. Refer to the Access and Setup Digital Assistant section of the Configure Digital
Assistant chapter in the Getting Started with Digital Assistant guide.

29
3. Setup a Twilio account and obtain a phone number for texting. The phone number must support MMS
(Multimedia Messaging Service) to send receipt images.
4. Connect the Twilio account to the Expenses Digital Assistant. Refer to the following sections in the
Getting Started with Digital Assistant guide:
Before you Start section in the Get Started chapter
Access and Set Up Digital Assistant section in the Configure Digital Assistant chapter
5. Schedule and run the Synchronize Financials Objects for Database Search process. This process creates
a repository of merchants used by the employees to aid in expense type derivation.

KEY RESOURCES

For more information about setting up Digital Assistant, refer to the Getting Started with Digital Assistant
guide.

ROLE INFORMATION

To assign Digital Assistant administrator roles, you must have the Identity Domain Administrator role. To
configure Digital Assistant, you must have the ODA Service Administrator role. To schedule and run
the Synchronize Financials Objects for Database Search process, you must have the Financial Application
Administrator role. When enabled, employees with Expense Entry role can create expenses through the
Digital Assistant.

REQUEST CASH ADVANCES ON BEHALF OF OTHER EMPLOYEES


Delegates can request cash advances for authorized employees. When a delegate requests cash advances,
the advances either proceed to final verification by employees or directly to approval based on the approval
rules. Employees and their delegates are notified when approval is complete.

When cash advance is enabled and the owner has granted delegate access, the delegate can submit cash
advances. The delegate can manage cash advances and search for cash advances from the Expenses work
area.

Cash Advance Delegate's View

STEPS TO ENABLE

To use this feature, perform the following tasks:

SETUP TASK

1. Set the Enable Advances option on the Manage Cash Advance and Authorization Policies page to Yes
for the specific business unit or customer site.
2. Modify your cash advance approval rule based on the scenario:

30
Scenario Required Configuration

Your company is implementing Expenses Activate the pre-configured rule,


now and requires the employees to verify CashAdvanceDelegateApprovalStage, in the BPM Worklist
cash advances submitted by their delegates. to route cash advances to the employees for verification.

Modify the FinExmCashAdvanceApproval task in the BPM


Your company has already implemented Worklist and add a new participant to route the cash
Expenses and the company requires the advance to the owner. If you use the supervisory
employees to verify cash advances submitted hierarchy for approval, you must modify the existing cash
by their delegates. advance rule to start from the cash advance owner's
manager.

Your company is already using cash


Modify the existing cash advance rule to start from the
advances and you use the supervisory
cash advance owner's manager.
hierarchy for approval.

KEY RESOURCES

For more information about delegated cash advance approvals, refer to the following topics in Oracle
Applications online help:

How to Setup Approval Rules for Delegated Cash Advances

ROLE INFORMATION

To enable cash advances, you must have the Application Implementation Consultant role. When enabled,
users with the Employee role can use the features.

SPLIT EXPENSE REPORTS ACROSS PROJECTS AND ACCOUNTS


Split all expense items in an expense report across multiple projects or general ledger accounts by entering
the split percentage at the expense report header.  Expense report approvers and auditors can review the
distributions for accuracy.

You can allocate charges to specific accounts or projects only if you are authorized to do so. When your
company allows you to allocate a single expense across multiple accounts or projects, you see the Split
Allocation button on the Create Expense Report page. Selecting the button opens the Split Allocation dialog.

31
Split Allocation Button on The Create Expense Report Page

The expense is allocated 100% to your default expense account, if you are authorized to charge to other
accounts and you have no prior expenses and your company has not enabled defaulting values from previous
expenses. You can add one or more accounts and specify the percentage of allocation. If your company has
enabled defaulting values from previous expenses, the expense account is defaulted to the last used account.

Splitting Across Accounts

Your expense is not allocated to any projects in the Split Allocation dialog if you are authorized to charge to
projects and you have no prior expenses and your company has not enabled defaulting values from previous
expenses. If your company has enabled defaulting values from previous expenses, the last used project is
already selected in the Split Allocation dialog.

32
Splitting Across Projects

If a user is authorized to charge to both projects and accounts, the Split Allocation button choice list provides
two options: By account and By project. Additionally, users can associate a spend authorization to the split
expense amounts.

Managers and auditors can review the split details in the expense approval notification and the Audit Expense
Report page respectively. The approval notification to managers summarizes the split allocation at the top of
the notification.  The Audit Expense Report page displays the split allocation for each expense.

33
Approver's View of Split Allocation

STEPS TO ENABLE

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

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

KEY RESOURCES

Watch Split Expense Reports Across Projects and Accounts Readiness Training

ROLE INFORMATION

To enable splitting expenses across projects and accounts, you must have the Application Implementation
Consultant role. When enabled, users with the Override Expense Account Allocation privilege or the Allocate
Project Expense privilege can use the features.

34
GENERAL LEDGER

TRANSFER INCOME STATEMENT AND BALANCE SHEET ACCOUNT BALANCES TO DIFFERENT


CLOSING ACCOUNTS
Select account ranges to close income statement account balances to different retained earnings accounts
using the Create Income Statement Closing Journals process; or select account ranges to close balance sheet
account balances to different closing accounts using the Create Balance Sheet Closing Journals process. This
provides more detailed tracking and reporting on closing activities related to the income statement and the
balance sheet accounts.

Business Benefits

1. Have more visibility into the year-end closing activities for both income statement and balance sheet
accounts.
2. Have tighter control over the choice of which closing account you want to use to close one or more
account balances.
3. Help comply with any specific business or legal requirements.

STEPS TO ENABLE

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

TIPS AND CONSIDERATIONS

1. Use the Account Filter parameter on the Closing Journals process submission pages to specify subsets
of source accounts to close into a specific closing account.
2. Use the following operators in the account filter: Equals, Between, and Is a Last Descendant Of. The
last descendant operator references the account hierarchy associated with the segments of the chart
of accounts instance within the context of the selected ledger or ledger set.

KEY RESOURCES

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 use this feature.

JOINT VENTURE MANAGEMENT

JOINT VENTURE MANAGEMENT


Joint Venture Management gives companies, who are the managing partners in a joint venture, the ability to
manage the costs and revenue related to a joint venture and distribute those amounts to the joint venture

35
partners according to the ownership percentage as defined in the joint operating agreement. This product
provides touchless processing for joint venture accounting processes that are typically performed manually
throughout the month. The automation of the joint venture flow helps the Joint Venture Accounting
Manager and Joint Venture Accountant to stay on top of any issues or trends related to a joint venture to
ensure:

Minimized time to close the financial books.


Accurate calculation of distributed amounts to joint venture partners.
Ability to quickly research and resolve any questions or disputes brought up by joint venture partners
related to their distributions.

This feature provides rich and easy-to-use joint venture management capabilities in the following areas:

1. Single, consolidated place to identify all joint venture partners


2. Comprehensive joint venture definitions
3. Rules to identify distributable transactions
4. Touchless processing of joint venture related transactions
5. Traceability of joint venture partner distribution amounts to original transactions

1. SINGLE, CONSOLIDATED PLACE TO IDENTIFY ALL JOINT VENTURE PARTNERS

CREATING AND MANAGING INVOICING PARTNERS

Before specifying a joint venture definition and identifying related stakeholders, you will need to create
Invoicing Partners. 

The purpose of an Invoicing Partner is to give you the ability to specify both payable (supplier) and receivable
(customer) entities related to a joint venture partner.  This way, you can reference an Invoicing Partner without
having to be concerned about whether the interaction with the Invoicing Partner will be a payable or a
receivable.  And each Invoicing Partner can be used as a stakeholder in one or more joint ventures.  Only those
customers and suppliers identified as Invoicing Partners can be designated as a stakeholder on any joint
venture.  And, with the use of alerts, you will know if any Invoicing Partner is missing needed information.  
This reduces the risk of accidentally using a customer or supplier on a joint venture that is not really a joint
venture partner.

Follow these steps to create and maintain Invoicing Partners:

1. Navigate to the Setup and Maintenance work area.


2. Search for the Financials setup and select the Joint Venture Management functional area in the list of
functional areas that appear.
3. In the task list on the right you will find a link “Manage Invoicing Partners”.

From this page, you will be able to create and manage all Invoicing Partners.

On the Invoicing Partner page, you will see a list of all Invoicing Partners.

36
To add a new invoicing partner, simply click the “+” symbol.

Enter the information in the page and click “Save”

2. COMPREHENSIVE JOINT VENTURE DEFINITIONS

Joint venture definitions provide a way to associate the essential Oracle Financials Cloud information to a joint
venture in order to identify transaction amounts and calculate the distribution amounts for joint venture
partners.  This information for each joint venture includes:  Business Unit, Cost Centers, Stakeholders, and
Ownership Definitions.  Joint venture definitions provides one place to define all that you need to process
related transactions.  And, with the use of alerts, you will know if any joint venture definition is missing needed
information, saving you time.

37
You can create and manage joint venture definitions with the Manage Joint Venture Definitions page.

Follow these steps to create and manage joint venture definitions:

1. Navigate to the Setup and Maintenance work area.


2. Search for the Financials setup and select the Joint Venture Management functional area in the list of
functional areas that appear.
3. In the task list on the right you will find a link “Manage Joint Venture Definitions”.

From this page, you will be able to create and manage all aspects related to a joint venture.

On the Joint Ventures page, you will see a list of all joint ventures.

This page gives you the ability to easily manage all your joint venture definitions including filtering and
searching for specific joint ventures by a number of different attributes including searching for joint venture
definitions that do not have their definitions completed.

To add a joint venture, simply click the “+” symbol.

38
Enter the information in the page and click “Save”.

After you save the Details of the joint venture, you can now enter the remaining information related to the
joint venture.

Click on Cost Center from the left side of the page to identify one or more cost centers related to the joint
venture.  A cost center is related to the segment with the cost center segment label.

Click on the “+” symbol to associate a cost center to the joint venture.

39
Enter the information in the page and click “Save”.

Next, click on Stakeholders from the left side of the page to identify one or more stakeholders related to the
joint venture.

Stakeholders can be internal to the managing partner or can be external to the managing partner.

Stakeholders can share in costs and/or revenue related to a joint venture.  Stakeholders may also be related to
a joint venture for informational purposes only (also known as a memo partner).

Click on the “+” symbol to add a stakeholder.

40
Enter the information in the page and click “Save”.

Finally, click on the Ownership Definition from the left side of the page to define one or more ownership
definitions.  Ownership definitions are date effective and they represent the partner split (represented as a
percentage) agreed upon.

Click on the “+” to add an ownership definition.

Once you have done that, you can click on the “+” icon in the lower part of the page to associate one or more
stakeholders to the ownership definition.

41
Enter the information in the page and click “Save”.

3. RULES TO IDENTIFY DISTRIBUTABLE TRANSACTIONS

For each joint venture, you can identify the segments and segment values in your chart of accounts that relate
to the transactions that will be invoiced to the joint venture partners.  This provides a set of rules that will be
used to identify related transactions from Subledger Accounting and the General Ledger for joint venture
processing.

Follow these steps to indicate which segments in your chart of accounts will be used in the rules for the
segment values:

1. Navigate to the Setup and Maintenance work area.


2. Search for the Financials setup and select the Joint Venture Management functional area in the list of
functional areas that appear.
3. In the task list on the right you will find a link “Manage Joint Venture Definitions”.

On the Joint Ventures page, you will see a list of all joint ventures.  From here, select the desired joint venture.

Once in the Edit Joint Venture page, click on Distributable Segments from the left side of the page.

You will see all the segments related to your chart of accounts.  In this page, you will select which segments
you want to use in the rules to specify which accounts are distributable to your partners.

You will see one segment that is automatically selected.  This segment is related to the segment where the
label for that segment is for the cost center.  The name of the segment may be different.  In the example
below, the segment that has the cost center label is named “Department”.

42
Enter the information in the page and click “Save”.

Once you have the segments identified, you can identify the cost centers and related segment values for the
joint venture.

In the Edit Joint Venture page, select Cost Centers from the left side of the page.  Here you have already
specified the cost centers and this is where you will also specify the segment values related to the distributable
transactions for the joint venture.

43
Click on the edit link on the right side of the page.

To add a set of segment values click on the “+” symbol.

Enter the information in the page and click “Save”.

44
4. TOUCHLESS PROCESSING OF JOINT VENTURE RELATED TRANSACTIONS

Based on the rules that identify distributable transactions, you can now automatically identify joint venture
transactions from Subledger Accounting and the General Ledger and automatically calculate each partner’s
share for each transaction based on the date-effective Ownership Definition specified for a joint venture.

Run the Identify Joint Venture Transactions process on distributable joint venture transactions that have not
yet been processed by Joint Venture Management. Run the Create Joint Venture Distributions process to
calculate each partner's share of the transaction.  You can run these processes as often as you like.

5. TRACEABILITY OF JOINT VENTURE PARTNER DISTRIBUTION AMOUNTS

You now have the ability to review and update the identified joint venture transactions and distribution
amounts related to a joint venture.  Key information related to the original transactions is included with the
identified joint venture transactions and distribution amounts to give you the information you need
validate and trace back to the financial information without having to navigate to a different place.  This key
information includes chart of account segment values that were charged, original transaction amount, and
currency.  Additional joint venture information also helps you validate and trace back to the joint operating
agreement without having to navigate to a different place.  This key information includes the ownership
percentage definition used to calculate the partner split, each partner's percentage share of the transactoin,
and the calculated partner's distribution amount.

Follow these steps to view and review joint venture transactions:

1. Navigate to the Home screen.


2. Search for the Joint Venture icon and select it
3. Select Transactions

Enter a joint venture at the top of the page.

Follow these steps to view and review joint venture distributions:

1. Navigate to the Home screen.


2. Search for the Joint Venture icon and select it
3. Select Distributions

45
Here you will see a page with the distributions for all joint ventures for all partners.

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

Additional steps to set up this feature are detailed within each of the Joint Venture Management areas in the
Description and Value section. 

Watch a Setup Demo

KEY RESOURCES

Watch Introduction to Joint Venture Management Readiness Training

For more information on the Joint Venture Management solution, refer to Oracle Joint Venture
Management Cloud implementation guide.

ROLE INFORMATION

To implement this feature, you will need the


role ORA_JV_JOINT_VENTURE_APPLICATION_ADMINISTRATOR that has the following
privileges:  JV_MANAGE_JOINT_VENTURE_INVOICE_PARTNER_LIST_PRIV
and JV_MANAGE_JOINT_VENTURE_DEFINITION_PRIV.

46
To use various parts of this feature there are two other roles and related privileges:  

1. ORA_JV_JOINT_VENTURE_ACCOUNTANT with privileges


JV_MANAGE_JOINT_VENTURE_DEFINITION_PRIV, JV_DISTRIBUTE_JOINT_VENTURE_TRANSACTIONS_PRIV,
and JV_REVIEW_AND_EDIT_JOINT_VENTURE_TRANSACTIONS_PRIV
2. ORA_JV_JOINT_VENTURE_ACCOUNTING_MANAGER with
privilege JV_MANAGE_JOINT_VENTURE_DEFINITION_PRIV

PAYMENTS

SETTLE CUSTOMER RECEIPTS USING EXTERNAL APPLICATIONS


Perform credit card and bank account settlements with payment systems using external applications when
creating customer receipts. The option to use external applications for settlements provides flexibility to
meet bank-specific, region-specific, or regulatory compliance requirements.

A new option ‘Use for external settlement’ is provided on the Funds Capture Process Profile. After enabling
this option, when a receipt is remitted in Receivables, the settlement transaction is directly created with the
status ‘Succeeded,’ instead of intermediary statuses such as ‘Pending in open batch’ or ‘Submitted’. You don't
need to submit the Create Settlement Batches or Submit Offline Transactions processes to transmit
settlement data with the payment system. The 'Use for external settlement' option also prevents authorization
with the payment system and creates an authorization transaction with the status ‘Succeeded.'

STEPS TO ENABLE

This feature is available by default.

Additional setup is required to configure this feature. Follow these steps:

1. In the Setup and Maintenance work area, navigate to Manage Funds Capture Process Profile.
2. Search and select your existing Funds Capture Process Profile and click the Edit icon.
3. On the Edit Funds Capture Process Profile page, enable the option ‘Use for external settlement’.
4. Click Save and Close.

TIPS AND CONSIDERATIONS

You should only enable this feature under these conditions:

1. External system is used for generating and transmitting authorization and settlement messages with
the payment system.
2. Payments is not integrated with payment system to perform authorization and settlement.

47
PAYABLES

SPECIFY URL ATTACHMENTS WHEN CREATING SUPPLIER INVOICES USING A SPREADSHEET


Specify URL attachments when creating supplier invoices using Create Invoice Spreadsheet. Previously,
invoices created through spreadsheet required manual editing of each invoice to add URL attachments.
Users could not provide the attachments of type URL when creating invoices from the spreadsheet.

STEPS TO ENABLE

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

TIPS AND CONSIDERATIONS

The URL attachments to an invoice appear in the hidden column BT. You must unhide the column to use it.

RECEIVABLES

RETAIN RECEIPT METHOD AND PAYMENT INSTRUMENT ON COMPLETE TRANSACTIONS


The receipt method and payment instrument are retained if a completed transaction needs to be set to
incomplete.

STEPS TO ENABLE

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

ROLE INFORMATION

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

SUPPORT RECEIVABLES DETAILED DISTRIBUTIONS FOR INVOICES WITH RULES


Create detailed distributions on invoices associated with revenue scheduling rules, and on all subsequent
activities created on such invoices. This feature applies to customers who set up and use Multifund
Accounting.

48
STEPS TO ENABLE

The feature is enabled by default.  To use this feature, you must modify the Subledger Accounting Method
associated with the Ledger enabled for multifund accounting according to the steps indicated below.

1. Create a new Journal Line Rule for the 'Invoice' event class and associate it with the Journal Entry Rule
Set.
2. Create a new Journal Line Rule for the 'Debit Memo' event class and associate it with the Journal Entry
Rule Set.
3. Modify the conditions within the Journal Line Rule 'Receipt Application to Multifund Transaction
Receivable' used for the 'Receipt' event class

1. NEW JOURNAL LINE RULE FOR 'INVOICE' EVENT CLASS:

(a) Navigation: Task > Manage Journal Line Rules

Search for the Journal Line Rule ‘Multifund Invoice Receivable’. Duplicate it.

49
Add the below conditions:

("Transaction Invoicing Rule" Is not null) 'And' ( "Transaction Distribution Account Class" = TAX 'Or'
"Transaction Distribution Account Class" = FREIGHT 'Or' "Transaction Distribution Account Class" = ROUND
'Or' "Transaction Distribution Account Class" = CHARGES 'Or' "Transaction Distribution Account Class" =
DEFERRED_TAX 'Or' ( "Transaction Distribution Account Class" = UNBILL 'And' "Receivables Offset Indicator"
= Y ) 'Or' ( "Transaction Distribution Account Class" = UNEARN 'And' "Receivables Offset Indicator" = Y ) )

(b) Navigation: Task > Manage Subledger Journal Entry Rule Sets

Search for the Journal Entry Rule Set ‘Invoices – Multifund Accounting Balancing Method’. Duplicate it (as
modifications can't be done on the predefined rule sets). Add the new Rule to the list with the Account
Combination Rule as ‘Multifund Transaction Default Receivables GL Account’ and mark ‘Copy’ against
Primary, Secondary and Third Balancing Segments.

2. NEW JOURNAL LINE RULE FOR 'DEBIT MEMO' EVENT CLASS:

Repeat the same process as narrated in the above section for 'Invoice' event Class.

3. MODIFIED JOURNAL LINE RULE FOR 'RECEIPT' EVENT CLASS:

(a) Navigation: Task > Manage Journal Line Rules

50
Search for the predefined Journal Line Rule ‘Receipt Application to Multifund Transaction Receivable’ and
duplicate it (as modifications can't be done on the predefined rules)

In the Journal Line Rule Conditions, add the details 'Or' "Transaction Distribution Account Class" = UNEARN
'Or' "Transaction Distribution Account Class" = UNBILL, as referred below.

(b) Navigation: Task > Manage Subledger Journal Entry Rule Sets

Search for the Journal Entry Rule Set ‘Receipts – Multifund Accounting Balancing Method’. Duplicate it (as
modifications can't be done on the predefined rule sets).

Add the modified Rule after deleting the existing one.

51
(c) Navigation: Task > Manage Accounting Methods

Search for the Accounting Method associated with the Ledger for which this add-on feature is required.  Add
the modified rule sets for Invoice, Debit Memo and Receipt after appropriately end-dating or deleting the
existing rules and activate it.

TIPS AND CONSIDERATIONS

Insert the conditions within the Journal Line Rules by selecting them from the menu list.  Do not copy-
paste them from a word pad or any other document.

When an invoice uses the In Advance invoicing rule, ensure that the Balancing Segment Value is the
same for both the Unearned Revenue and Revenue accounts across periods. Use the same approach
for the Unbilled Receivables and Revenue accounts for invoices that use the In Arrears invoicing
rule.  Note: You must use this model whether the balancing segment is manually overridden on an
invoice in the Review Distributions window or overridden through the Segment Rules in the Subledger
Accounting Setup. Otherwise Intracompany and Intercompany balancing entries will get generated.

52
KEY RESOURCES

Watch Create Detailed Receivables Distributions (update 19A) Readiness Training

ROLE INFORMATION

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

SUBLEDGER ACCOUNTING

SET COMPLETION STATUS FOR ALL JOURNALS IN ONE GO AND PICK ACCOUNTING PERIOD
WHILE IMPORTING SUBLEDGER JOURNALS
Use the enhanced Create Subledger Journals ADFdi spreadsheet to define Completion Status across all
journals, pick an Accounting Period and search for Journal Category.

You can set completion status for all subledger journals concurrently by selecting a status from the
Completion Status list in the header section of the Subledger Journal Entry ADFdi spreadsheet. All journals
entered in the template are imported with the selected Completion Status.

The spreadsheet now lets you enter subledger journals in adjusting periods, even if you have multiple
adjusting periods defined for the same date range.

Enter the accounting period value directly in the Accounting Period column. Alternately, double-click an
Accounting Period cell to open a dialog box. In the dialog box, you can search and select the relevant
accounting period.

53
Similarly, you can also search and select a journal category.

STEPS TO ENABLE

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

TIPS AND CONSIDERATIONS

NOTE:  You must download the latest ADFdi spreadsheet template using the Create Subledger Journals in
Spreadsheet task.

54
TAX

HIGHLIGHT CONFIGURATION ELEMENTS THAT AREN'T OPTIMIZED


Display a message on the Manage Taxes page highlighting configuration elements that aren't optimized.

For example, ERP Cloud now prevents you from enabling more than 25 taxes for a country because that
adversely impacts the tax calculation performance. A message alert is displayed when the system encounters
an unusually large number of taxes.

STEPS TO ENABLE

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

TIPS AND CONSIDERATIONS

You can deactivate this feature by creating a lookup. Here’s how you create it:

1. Go to Navigator > Setup and Maintenance > Manage Standard Lookups.


2. Click New to create a new lookup type. Enter ZX_OPTIN_OPTIONS in the Lookup Type field.
3. In the Lookup Codes section, click New to create a new lookup code. Enter
ALLOW_NON_OPTIMUM_TAXES in the Lookup Code field.

LEVERAGE ONLINE HELP DURING TAX CONFIGURATION AND TAX LINE REVIEW
ERP Cloud now provides enhanced online help on the Oracle Tax setup pages. The new help text gives you
information about the impact of enabling certain options on these setup pages.

This table lists out the fields that are covered by the enhancement:

Field Application Page

Apply single rate on total taxable basis Manage Taxes

Geography Type Manage Taxes

Override Geography Type Manage Taxes

Set as offset tax Manage Taxes

Tax Classification Code Set Assignments Manage Tax Rates and Tax Recovery Rates

Party Name Manage Party Tax Profiles

Party Site Number Manage Party Tax Profiles

You can also read more information about the tax lines in the Taxes region of the Payables Create and Edit
Invoice pages.

For some tax setups, the tax line details on the Payables Create and Edit Invoice page are read-only. In such
cases, you can see the exact detail from the tax setup.

55
Here’s an example of read-only details:

For Example:

Read-only tax detail on the


Payables Create and Edit Invoice Flag at the tax setup Application Page
page

Allow override of calculated tax Configuration Owner Tax Options


Whole tax line is non-editable
lines or at Tax setup.

Rate name and rate are non-


Allow tax rate override Tax Status
editable

Rate is non-editable Allow ad hoc tax rate Tax Rate

These tax lines are read-only: Offset Tax line, Canceled Tax Line, Reference documents attached to a tax line

STEPS TO ENABLE

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

REPORT TAXABLE AMOUNT BASED ON LEDGER ACCOUNTED AMOUNTS IN TAX REPORTING


Optionally use the accounted taxable amount in Tax reports instead of the tax repository taxable amount,
when there is no complex taxable basis definition such as compound Tax. The Tax reports will now show the
accounted amount as the taxable amount. For cases where the taxable basis definition is complex, such as
compound tax, prior tax or assessable value, the reports will show the taxable amount from the tax repository.

STEPS TO ENABLE

Create and enable the lookup type ZX_TRL_ACTG_AMT_SOURCE with the lookup code
ZX_TRL_STANDARD_TB_AMT.

1. To configure the lookup use these steps:


2. Go to Navigator > Setup and Maintenance > Tasks panel tab > Search.Search for Manage Standard
Lookups.
3. Select Manage Standard Lookups from the results.
4. On the Manage Standard Lookups page, click + to define a new lookup type
"ZX_TRL_ACTG_AMT_SOURCE".

56
5. Click Save.
6. Click + in the Lookup Codes section to define a new lookup code "ZX_TRL_STANDARD_TB_AMT".

7. Click Save and Close.

TRANSACTIONAL BUSINESS INTELLIGENCE FOR FINANCIALS

USE ADDITIONAL ATTRIBUTES IN RECEIVABLES SUBJECT AREAS


New subfolders and corresponding reporting attributes were added to the Receivables - Customer Account
Site Tax Profile Real Time subject area:

under folder Customer Accounts, new subfolder, Customer Account Profile, with new attributes for
account profile class
under folder Customer Accounts, new subfolder, Customer Account Contacts, with new attributes for
account contacts
under folder Customer Account Site, new subfolder, Customer Site Profile, with new attributes for site
profile class
under folder Customer Account Site, new subfolder Customer Site Contacts, with new attributes for
customer site contacts

New subfolders and corresponding reporting attributes were added to the Receivables - Bills Receivable Real
Time subject area:

57
under folder Drawee Account, new subfolder, Drawee Account Profile, with new attributes for account
profile class
under folder Drawee Account, new subfolder, Drawee Account Contacts, with new attributes for
account contacts
under folder Drawee Site, new subfolder, Drawee Site Profile, with new attributes for site profile class
under folder Drawee Site, new subfolder Drawee Site Contacts, with new attributes for customer site
contacts

New subfolders and corresponding reporting attributes were added to the following OTBI Receivables subject
areas:

Receivables - Transactions Real Time


Receivables - Adjustments Real Time
Receivables - Credit Memo Applications Real Time
Receivables - Credit Memo Requests Real Time
Receivables - Payment Schedules Real Time
Receivables - Revenue Adjustments Real Time
under folder Bill-to Customer Account, new subfolder, Bill-to Customer Profile, with new
attributes for customer account profile class
under folder Bill-to Customer Account, new subfolder, Bill-to Customer Contacts, with new
attributes for customer account contacts
under folder Bill-to Customer Site, new subfolder, Bill-to Customer Site Profile, with new
attributes for customer site profile class
under folder Bill-to Customer Site, new subfolder, Bill-to Customer Site Contacts, with new
attributes for customer site contacts

New subfolders and corresponding reporting attributes were added to the following OTBI Receivables subject
areas:

Receivables - Standard Receipts Applications Real Time


Receivables - Receipts Details Real Time
Receivables - Receipt Conversion Rate Real Time
Receivables - Miscellaneous Receipts Real Time
under folder Paying Customer Account, new subfolder, Paying Customer Account Profile, with
new attributes for customer account profile class
under folder Paying Customer Accounts, new subfolder, Paying Customer Contacts, with new
attributes for customer account contacts
under folder Paying Customer Site, new subfolder, Paying Customer Site Profile, with new
attributes for customer site profile class
under folder Paying Customer Site, new subfolder, Paying Customer Site Contacts, with new
attributes for customer site contacts

STEPS TO ENABLE

Leverage new subject area(s) by adding to existing reports or using in new reports. For details about creating
and editing reports, see the Creating and Administering Analytics and Reports book (available from the
Oracle Help Center > your apps service area of interest > Books > Administration).

ROLE INFORMATION

No new role access is needed to use this feature.

58
REGIONAL AND COUNTRY-SPECIFIC FEATURES

FINANCIALS FOR THE AMERICAS

BRAZIL

ALLOW MULTIPLE BANK RETURN CODES FOR BRAZIL


Allow processing of multiple bank return codes in Collection Documents for Brazil, if your bank uses more
than one bank occurrence code for the same electronic payment or collection return event.

These are the fields that identify the bank return event:

Collection Document Update Codes: bank occurrence codes defined by each bank
Standard Update Types: system representation of the bank occurrence codes

If your bank uses multiple bank occurrence codes for the same electronic payment return event, associate the
specific bank occurrence code with the corresponding system occurrence code of Payables bank return.
Similarly, you can associate the specific bank occurrence code with the corresponding system occurrence
code of Receivables bank returns. This way, you can capture, store and visualize exactly the bank occurrence
codes sent by your bank.

STEPS TO ENABLE

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

KEY RESOURCES

For further information about Payables Collection Documents and Bank Collection Remittance features, refer
to Quick Reference for Oracle ERP Cloud Documentation for Brazil (Doc ID 2329725.1) in My Oracle Support.

CONDITIONAL VALIDATION OF STATE INSCRIPTION DURING FISCAL DOCUMENT GENERATION


PROCESS FOR BRAZIL
The Fiscal Document Generation process for Brazil validates the state inscriptions for customers based on
the State Inscription classification previously configured for the ship-to party site. This allows generation of
fiscal documents for customers and ship-to party sites who are not required to have a state inscription.

STEPS TO ENABLE

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

TIPS AND CONSIDERATIONS

You must perform additional setup steps to enable the Fiscal Document Generation process in these cases:

When the ship-to site doesn’t have a State Inscription number and you don’t want the fiscal document
validation to fail.
When you want to inform the State Inscription classification of the ship-to parties through the
corresponding field in the fiscal document output file.

59
Here’s what you do in these scenarios:

For Shipping and Receivables Flows:

1. Go to Navigator > Setup and Maintenance > Manage Customers.


2. In the Sites section, select the ship-to site.
3. Select Tax Profile > Tax Reporting Codes > Tax Reporting Type Code and set its value as State
Inscription Classification.
4. Enter one of these values in the Tax Reporting Code field:
ICMS Taxpayer
ICMS Taxpayer Exempt from State Inscription
Non-ICMS Taxpayer

For Internal Material Transfer Flows:

1. Go to Navigator > Setup and Maintenance > Manage Party Tax Profiles.
2. Search for Legal Reporting Unit Tax Profiles.
3. Select the ship-to Legal Reporting Unit.
4. In the Tax Reporting Codes tab, select State Inscription Classification in the Tax Reporting Type Code
field.
5. Enter one of these values in the Tax Reporting Code field:
ICMS Taxpayer
ICMS Taxpayer Exempt from State Inscription
Non-ICMS Taxpayer

FISCAL DOCUMENT OUTPUT FILE

The tax reporting code of the ship-to party site is now extracted in the output file of Send Fiscal Document to
Tax Authority process.

Here’s the new element added to the output file:

Field Description Parent Type Cardinality Size

State Inscription classification


SHIP_TO_PARTY_SITE_IE_CLASS A1 CHAR 0-1 30
code of the Ship-To Party Site

FISCAL PARTNER VALIDATIONS 

The fiscal document validation doesn’t happen when your ship-to site has a State Inscription, but no tax
reporting type assigned to it. In this case, the fiscal partner should validate and log an error, if required.

Here are some other cases where fiscal document validation doesn’t take place:

Condition Solution

SHIP_TO_PARTY_SITE_IE_CLASS field is null, but Partner should raise a validation error and return it
the tax authority requires the ship-to State to the Import Fiscal Document Approval
Inscription classification. Information process.

SHIP_TO_PARTY_SITE_IE_CLASS field has Partner should raise a validation error and return it
ICMS_TAXPAYER_EXEMPT_IE, but the to the Import Fiscal Document Approval
SHIP_TO_PARTY_SITE_IE field is not null. Information process.

60
FISCAL PARTNER PROCESSING 

Partner must convert the tax reporting code into the corresponding numeric code expected by the tax
authority, while creating the fiscal document XML file:

Tax Reporting Code Ship-to State Inscription classification

ICMS_TAXPAYER 1

ICMS_TAXPAYER_EXEMPT_IE 2

ICMS_NON_TAXPAYER 9

KEY RESOURCES

For further information about Brazil Fiscal Document feature, refer to Order to Cash for Brazil (Doc ID
2335507.1) in My Oracle Support.

FINANCIALS FOR ASIA/PACIFIC

INDIA

EXTRACT PURCHASE REGISTER AND COMPLETE INPUT TAX RECOVERY AS PER THE REVISED
GST REPORTING STRUCTURE FOR INDIA

Extract the purchase register from Payables Cloud and match the supplier data to the Annexure-2 supplier
data of the revised GST reporting structure for India. Upload the output file generated by the matching
process to complete the input tax recovery process.

Annexure-2 determines the input tax to be credited to the taxpayers’ accounts.  As per the proposed
procedure, tax payers are eligible for claiming input tax credit only if the inward supply is declared by the
supplier in their Annexure-1. Based on supply information uploaded by the suppliers,
GSTN  generates Annexure-2 for every GST registered entities.

Taxpayers can match records of inward supplies autopopulated in Annexure-2 with their inward supplies.  In
order to use the GSTN offline utility for processing the matching of inward supplies with records of inward
supplies autopopulated based on supplier declaration; taxpayers must maintain their purchase register in a
prescribed template.

India Outbound Process: ERP Cloud provides a scheduled process for the India Outbound processes to extract
Purchase Register related data and generates CSV files with all the required data points as per the prescribed
format provided by GSTN for Inward and Outward reports. The csv files are placed into UCM folder for the
users to download directly and use the same file to create the Purchase Register Report in the GSTN provided
format.

61
The same process can be leveraged for the Annexure-1 as well where users can use it to retrieve the outward
supplies tax and integrate the outward supplies tax to GSTN system.

India Inbound Process: ERP Cloud facilitates an end-to-end utility where users are able to import the GST
Annexure-2 (Action) file into ERP based on a centrally provided web  service, which in turn, invokes the
Recovery Recognition process for India for the uploaded invoices through the Annexure-2 Action file and
creates accounting of the provisional or interim recoverable tax in Payables Invoices.

The feature enables you to:

Run the India Outbound process for Purchase Register which extracts the optimum dataset required for
GSTN prescribed Purchase Register report from Payables modules and enable users to match it with
Supplier declared autodrafted Annexure-2 report.

Leverage the Global Tax Reporting Ledger (TRL) to create the India GST Inward supply Repository to
create the Purchase Register report in the GSTN prescribed format.

Effectively handle any Error, if notified by GST portal upon uploading Purchase Register report to the
offline utility.

Run the India Inbound process for Annexure-2 which enables users to account the input tax credit
recovery and reconciliation of tax accounting in ERP Ledger with the Credit Ledger of the Recipient in
the GSTN portal.

STEPS TO ENABLE

To enable this feature, associate the Taxes defined in the Setup and Maintenance work area 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

62
6. Click Save and Close.

To apply this feature:

1. In the Setup and Maintenance work area, use the Manage Taxes task.

           Offering:  Financials Functional area:  Transaction Tax:  Manage Taxes

2. Search for the required transaction tax.


3. Go to the  Control and Defaults tab.
4. In the Tax Recovery Controls and Defaults section, enable the  Defer recovery for specialized handling
 option.
5. Click  Save and Close.

PROCESS STEPS:

INDIA OUTBOUND PROCESS 

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: Record Inward and Outward Taxes for India. Run the Process.

63
Parameters:

India Inbound Process:

The web service that can be used to automate the Annexure-2 file upload and import process is the ERP
Integration Service

Provides external operations for ERP integration scenarios to execute end-to-end inbound and outbound data
flows. It also tracks the status of inbound and outbound data processes.

Life Cycle Status: Active

QName: {http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/}
ErpIntegrationService

Service WSDL URL: https://(FADomain,FSCMServices)/fscmService/ErpIntegrationService?WSDL

Operation: importBulkData

64
JobName: /oracle/apps/ess/financials/apacLocalizations/financialReports,IndiaGSTInboundReport

ParameterList: ANNEXURE2

jobOptions: interfaceDetails=128

TIPS AND CONSIDERATIONS

The India Inbound process will work correctly and let you process recoverable taxes if all of these conditions
are met:

1. The Taxes in the Payables Invoice are Recoverable in nature.


2. "Enable Defer Recovery for Specialized Handling” at Tax setup level.
3. Associate the Taxes defined in the Functional Setup Manager into India Taxes Types (Tax Reporting
Codes: ORA_IN_TRANS_TAX_TYPE).
4. The Payables invoice should be in Accounted status.
5. Supplier Tax Invoice number and Date should exactly match with the Document Number and
Document date of the Annexure-2 file uploaded into ERP.
6. The file format should be CSV which the ERP Integration web service for India Inbound process accepts
for the Recovery management.

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.

Oracle® Applications Financials Implementation Guide, Release 13

ROLE INFORMATION

You need one of these roles to maintain account hierarchies using the Import Segment Values and
Hierarchies template:

Financial Application Administrator


Application Implementation Consultant
Tax Administrator

JAPAN

PROCESS LOCKBOX CUSTOMER PAYMENTS USING ZENGIN FORMAT FOR JAPAN


Process lockbox customer payments using the Zengin format for Japan. A new control file supporting Zengin
format identifies customers using the alternate payer name, creates the customer receipts, and processes all
receipt applications. The lockbox process optionally uses the customer bank name and customer branch
name, along with the alternate payer name, to identify the customer associated to the payment.

The feature provides the following functionality:

Enhancements to the existing Process Receipts through Lockbox process to record customer payments
through lockbox using the Zengin format. See the example below for details.

65
New Functional Setup and Maintenance Task called Manage Alternate Name Mapping Rules to create
and maintain Alternate Name Mapping Rules to map the Alternate Payer Name along with the
Customer Bank Name and Customer Bank Branch to the customer account number and site.
New predefined transmission format called ORA_ZENGIN_LOCKBOX (arlockboximportzenginr.ctl) with
Lockbox Header and Payment Record types.
New predefined context Zengin Cash Receipts for the Receipts Descriptive Flexfield to store the
additional required information for a Zengin lockbox.

The existing Process Receipts through Lockbox process has been enhanced to perform the following:

Process customer payments through lockbox using the Zengin format.


Convert the Japanese Imperial date format to the western calendar date.
Support conversion of the bank file dates in the Reiwa era to the Western Calendar date.
Leverage the Alternate Name Mapping Rules to use the Alternate payer name, and optionally the
customer bank name and customer bank branch name, to identify the customer account associated to
the receipt.
Create receipt for the site defined in the Alternate Name Mapping Rules for the matching alternate
name mapping rule.
If no site has been defined for the matching alternate name mapping rule, create receipt for the primary
bill-to site of the business unit of the receipt.
Assign an appropriate error message to Zengin customer payments that failed due to a missing or
invalid alternate name mapping rule.
Allow download of the Manage Lockbox Transmission ADFDI to update the customer account and site
to create records as identified receipts on resubmission of the process.
Also allow download of the Manage Lockbox Transmission ADFDI to enter null values for the customer
account and site to create records as unidentified receipts on resubmission of the process.
On successful completion of the process, create the customer payment record accordingly as an
identified or unidentified receipt.
Capture additional information in the Zengin Cash Receipts DFF context for user review and research.
The existing functionality for applying receipts to transactions remains unchanged.

The following example illustrates how to update the Manage Lockbox Transmission ADFDI to create a receipt
as identified or unidentified:

1. Navigate to the Manage Lockbox Transmission in the Accounts Receivable work area and click on it.
2. Download the Manage Lockbox Transmission ADFDI.
3. Search for the relevant Zengin customer payment record.
4. Identify the payment record that did not find a matching alternate payer name rule.

66
5. Scroll to the Customer Account Number and Site columns for this record.
6. To create the receipt as identified, replace the alternate payer name in the customer account number
field with the valid customer account and site.

7. To create the receipt as unidentified, remove the alternate payer name from the customer account
number field and leave it blank.
8. Click Upload or Submit and Post in the Lockbox Errors tab to continue with the process.

STEPS TO ENABLE

The following setups are predefined for this feature:

New predefined transmission format called ORA_ZENGIN_LOCKBOX (arlockboximportzenginr.ctl) with


Lockbox Header and Payment Record types.
Predefined context Zengin Cash Receipts under the Receipts descriptive flexfield.

67
The following setups need to be performed for processing Zengin lockbox payments:

Set up the alternate name mapping rules using the Functional Setup Manager Task Manage Alternate
Name Mapping Rules under the Task List Define Customer Payments.
Setup the lockbox from the Functional Setup Manager task Manage Lockbox.
Define the context sensitive segments as indicated in the table below for the Zengin Cash Receipts
context for lockbox, to store the Zengin lockbox information on the receipt:

Segment Name Description Table Column

Name that the user has specified to identify the


Transmission Name Attribute1
transmission.

Alternate Payer Name EFT requester name in the Zengin file. Attribute2

Zengin Customer Bank Name EFT requester bank name in the Zengin file. Attribute3

EFT requester bank branch name in the


Zengin Customer Bank Branch Name Attribute4
Zengin file.

TIPS AND CONSIDERATIONS

LOCKBOX BANK FILE

Lockbox bank file names must use the prefix ‘arlockboximportzenginr’. For example:
arlockboximportzenginr_yymmdd.
Do not include records with the Deposit/Withdrawal Type = 2 and Transaction Type = 10 to the bank
file that is loaded for import.
Do not include the trailer and end records with data type 8 and 9 respectively to the bank file that is
loaded for import.
The header and payment record types can have the data type as 1 and 2 respectively.
Do not include multiple header records from different remittance banks, branches, and accounts in a
single lockbox bank file, as this will cause validation failure.

MANAGE ALTERNATE PAYER NAME RULES

Set up the Alternate Name Mapping Rules before the process run to increase the count of lockbox
receipt records to be created with the customer identified.
For successful matching, set up unique individual rules for each combination of alternate payer name
and customer bank/branch, based on how the information will be received from the remittance bank.
Users can only set up rules for the customer sites for which they are authorized to handle lockbox
payments.
Establish best practices to manually update the Alternate Name Mapping Rules for new mappings for
future payment processing.

MANAGE TRANSMISSION FORMATS FOR LOCKBOX 

Item Number in the ORA_ZENGIN_LOCKBOX Transmission format is a System-generated sequence


number assigned to each payment. It need not be passed in the bank file loaded for import.

68
MANAGE LOCKBOX TRANSMISSION ADFDI

Do not make edits to the attribute column values in the ADFDI spreadsheet. These values contain logic
that identifies the records as Zengin payments.

ROLE INFORMATION

No additional role is required.

FINANCIALS FOR EMEA

ISRAEL

PROCESS SHAAM SUPPLIER CERTIFICATES FOR ISRAEL

Israeli Tax Authorities provide a computerized processing system known as SHAAM to maintain bookkeeping
and withholding tax certificates for suppliers that trade goods or services in Israel. Tax Managers can send
supplier information electronically and receive back a file with the valid certificate details. Use the Process
SHAAM Certificates for Israel feature to identify the supplier details to send, and update the returned
certificate and withholding tax exemption information.

STEPS TO ENABLE

To use this feature, perform the following steps:

1. For suppliers and/or supplier sites which should be included for SHAAM processing, create a
withholding tax registration.

2. Define withholding tax rates for each of the different exemption categories of withholding and assign
the predefined tax reporting code.

69
TIPS AND CONSIDERATIONS

Generate a file of suppliers and supplier sites whose bookkeeping certificates will soon expire and
transmit the file to the tax authority SHAAM processing system.

Upload the validated file returned by the tax authority to update the latest bookkeeping certificate and
withholding tax exemption details for those suppliers and sites.

KEY RESOURCES

For additional information, refer to the following topical essays which can be found on My Oracle Support:

Process SHAAM Supplier Certificates for Israel


Withholding Tax Reporting for Israel

ROLE INFORMATION

Assign the role ORA_JE_EMEA_FINANCIAL_REPORTING_DUTY to users who need to perform this processing.

70
PORTUGAL

INTEGRATE DOCUMENT PRINTING AND DELIVERY FOR PORTUGAL


Integrate the country-specific Portugal commercial document print and delivery process with the  Receivable
print and delivery process. This integration provides Portuguese users with a unified bill presentment
solution. Use this feature after completion of Oracle ERP Cloud certification for Portugal. Refer to MOS Note
2470182.1 for updates on the certification progress.

Here are the added actions that you can perform using this feature for Portugal, compared to the existing
Print Commercial Documents for EMEA solution:

Print any attached files to the Receivables transactions in PDF form, along with the invoice output.
Create a zipped PDF file for sending the transactions for third party printing.
Send Receivables transactions output by email.

STEPS TO ENABLE

To enable this feature, define a lookup code ORA_PORTUGAL under the Receivables lookup type
ORA_AR_TRX_PRINT_REGIONS.

TIPS AND CONSIDERATIONS

Use this feature to print all Receivables transactions for Portugal, except when you use invoices as Bill of
Lading or Proforma invoices.

In training mode, you can only print a hard-copy of the transaction, with a modified template as required by
the Portugal Tax Authority.

KEY RESOURCES

Oracle® Fusion Applications Financials Implementation Guide, Release 20B

71
ROLE INFORMATION

To use this feature, you must have the Print Receivables transaction privilege of:

AR_SUBMIT_BPA_TRANSACTION_PRINT_PROCESS_PRIV

SPAIN

GENERATE ONLINE VAT REGISTERS FOR SPAIN WITH LEGAL FORMAT CHANGES
Generate Online VAT Registers for Spain with support for version 1.1 of the XML format used in Spain.

The changes in the legal format effective from the July 1, 2018, are incorporated in the output format of Online
VAT Registers for Spain.

In addition, the Online VAT Registers for Spain reporting contains these enhancements:

The Receivables invoices, created by using the duplicate feature, are not selected for Online VAT
Registers for Spain reporting if the source Receivables invoices are already in submitted status for
reporting. You can view these duplicated invoices that meet the reporting criteria, but not selected for
reporting, in the log file of the Online VAT Registers for Spain.
You can distinguish between the issued invoices for resident customers and foreign customers for the
reporting purposes by using the newly introduced Tax Reporting Type.
When the received and issued invoices are created from the same intercompany batch, you can report
the transaction number of the issued invoice as a document sequence name and number or document
sequence number only.
The taxable base reported on the Online VAT Registers for Spain no longer includes taxable amounts of
the invoice lines with 0% VAT.

STEPS TO ENABLE

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

TIPS AND CONSIDERATIONS

1. Define Tax Reporting Type ‘XXXXNS_LOC’


2. Define Tax Rate used for foreign customer invoices, and assign ‘XXXXNS_LOC’ Tax Reporting Type to
it.
3. Setup ‘JE_SII_AR_IC_DOC_DISABLE' Lookup Code to ‘Yes’. The default is ‘No’

KEY RESOURCES

Online VAT Reporting for Spain Topical Essay

ROLE INFORMATION

The feature is secured by EMEA Financials Reporting duty role. This duty role is an orphan role. You must
assign it to another role or user to get access to the feature.

72
GENERATE VAT REPORTS FOR SPAIN WITH ONLINE VAT REGISTERS FOR SPAIN REPORTING
ATTRIBUTES
View Online VAT Registers for Spain reporting attributes in the VAT reports for Spain. This helps with
reconciliation across different types of reporting.

The data model for VAT reports for Spain contains these reporting attributes:

Document Type
Special Regime
Transaction Status
Tax Authority Status
Error Code
Error Description
Invoice Description
Tax Point Date
Tax Period
Tax Year
Date used as reference for 8 days submission

You can include these attributes in the VAT reports for Spain, Input VAT Journal for Spain and Output VAT
Journal for Spain, for improved reconciliation.

You no longer need to manually update the Transaction Business Category of the invoices from an
intercompany batch, where both intercompany parties reside within EU, to INTERCOMPANY/MOD349’. These
invoices are automatically reported on the Modelo 349 Report for Spain.

STEPS TO ENABLE

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

KEY RESOURCES

VAT Reporting for Spain Topical Essay

ROLE INFORMATION

The feature is secured by EMEA Financials Reporting duty role. This duty role is an orphan role. You must
assign it to another role or user to get access to the feature.

FINANCIALS FOR REGIONAL LOCALIZATIONS

USE SAF-T DATA EXTRACT TO REPORT SOURCE DOCUMENTS, PAYMENTS AND ASSETS
Use the SAF-T data extract to report source documents, payments, and assets. These, along with accounting
information currently extracted, support audit report requirements in Austria, Germany, Lithuania,
Luxembourg, Norway, and UAE.

73
The output of this process is a set of file extracts, generated in CSV format after successfully running the
Create Generic SAFT Extract, that will help you with the preparation of the country specific audit file. The
extract will be run at legal entity and tax registration number level, for closed periods only.

Using this extract you can do the following:

Extract all the master-file information for the natural accounts defined under the specified legal entity
implementation.
Extract all the master-file information for the third parties that have transactions during a given period
or have non-zero balances for the same period.
Extract all the master-file information for the taxes setup in the system and the products used in the
source documents.
Extract all the master-file information for the assets that have a date placed in service before the end
date of the period specified and are not fully retired before the given fiscal year.
Extract all the General Ledger or Subledger Accounting journal information for a given period or a
range of days within a period.
Extract all the Receivables transactions and receipts for a given period or range of days within a period,
based on either the accounting or the transaction date.
Extract all the Payables transactions and payments for a given period or range of days within a period,
based on either the accounting or the transaction date.
Extract all asset transactions of the current fiscal year and until the end-date of the accounting period
selected in the parameters.

STEPS TO ENABLE

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

TIPS AND CONSIDERATIONS

A hierarchy structure is in place for the natural account segment, with the tree being organized under
a single top level account which will identify the particular hierarchy structure. This top level account
value will be used in the ESS job parameter so that the program will extract the required data.

The extract exports all contacts and registrations for the selected legal entity and third parties.

ROLE INFORMATION

The Generate SAFT Data Extract is automatically available after completing the Generate SAFT Extract
security setup.The feature is available under the Generic SAFT
privilege GENERATE_SAFT_DATA_EXTRACT_PRIV.

---

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

75

Potrebbero piacerti anche