19B Financials WN

TABLE OF CONTENTS
UPDATE 19B ······························································································································································································· 3

Revision History ························································································································································································ 3
Overview ······································································································································································································· 3
Optional Uptake of New Features (Opt-In) ··································································································································· 3
Feature Summary ····················································································································································································· 5
Common Technology and User Experience ······························································································································· 9
Common Financials Features ······················································································································································· 9
Auto Dismiss Popup ···································································································································································· 9
Performance Enhancement in General Accounting Dashboard and Intercompany Work Area ····················· 9
Simplified Workflow Rules Configuration ···························································································································· 9
REST APIs for Financials ······························································································································································ 11
REST APIs for Currency Rates ············································································································································ 11
REST APIs for External Bank Accounts ···························································································································· 11
REST APIs for Journals ··························································································································································· 12
REST APIs for Ledger Balances ·········································································································································· 12
REST APIs to Manage Country Specific UI Rules for Simplified Bank Accounts ·············································· 12
REST APIS for Payments ······················································································································································· 13
REST APIs for Salesperson Reference Account ··········································································································· 13
REST APIS for Supplier Invoices ········································································································································· 14
Financials ··································································································································································································· 14
Assets ····································································································································································································· 15
Investment Allowance Deductions as Bonus Depreciation ························································································ 15
Budgetary Control ············································································································································································ 16
Budgetary Control Spend Authorizations ·························································································································· 16
Carry Forward Purchase Order Budgetary Control Balances Enhancement ······················································ 22
Cash Management ············································································································································································ 24
Bank Statement Reconciliation of Rejected Lines ········································································································· 24
Manual Reconciliation Enhancements ······························································································································· 25
Expenses ······························································································································································································· 25
Spend Authorization with Budgetary Control ··················································································································· 25
Usability Enhancements for Expenses ······························································································································ 30
General Ledger ··················································································································································································· 33
Multiple Segment Tracking for Revaluation Gain or Loss ··························································································· 33
Performance Enhancements in General Accounting Dashboard and Journals Work Area ··························· 34
Reverse Journal Batch ····························································································································································· 35
Single Request Submission for Streamlined Journal Batch Reversal Processing ············································ 35
Payables ································································································································································································· 36
Change First Open Period for Payables ···························································································································· 36
Payables Workflow Transaction Listing Report ·············································································································· 36
Supplier Portal Invoice Enhancement Phase Two ········································································································ 38
Customer and Supplier Balance Netting ································································································································ 41
Manage Netting Settlements in a Spreadsheet ·············································································································· 41
Receivables ·························································································································································································· 42
Manage Customer Data Import in Receivables ·············································································································· 42
Create Detailed Receivables Distributions ······················································································································· 42
Customer and Supplier Balance Netting ································································································································ 46
Manage Netting Settlements in a Spreadsheet ·············································································································· 46
Revenue Management ···································································································································································· 47
Enhanced Handling of Invalid Contract Lines ················································································································· 47
Subledger Accounting ···································································································································································· 50
Upload Mappings of Subledger Accounting Mapping Set Rules Using FBDI ····················································· 50
Tax ············································································································································································································ 51
Compound Tax on the Assessable Value ························································································································· 51
Tax Registration Number Validation for 5 New Countries (Colombia, Ecuador, Mexico, Peru, and Taiwan)
··········································································································································································································· 52
Transactional Business Intelligence for Financials ········································································································· 59
Add Non-Qualified Segments to Oracle Transactional Business Intelligence Fixed Assets Subject Areas
··········································································································································································································· 59
Cross-Pillar Reporting Between Receivables and Projects ······················································································· 59
Enhancements to Cash Management Subject Areas ··································································································· 60
Enhancements to Revenue Management Subject Areas ··························································································· 60
Expose Descriptive Flexfields on Key Flexfields for OTBI Financials Non-Essbase Subject Areas ·········· 61
Payables Invoices Holds Information Reorganized in the Oracle Transactional Business Intelligence
Subject Areas ·············································································································································································· 61
2
UPDATE 19B
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
Payables Invoices Holds Information

04 JUN 2019 Reorganized in the Oracle Transactional Updated document. Revised feature information.
Business Intelligence Subject Areas
Updated document. Delivered feature in update
26 APR 2019 Create Detailed Receivables Distributions
19B.
22 MAR 2019 Created initial document.
OVERVIEW
This guide outlines the information you need to know about new or improved functionality in this update, and
describes any tasks you might need to perform for the update. Each section includes a brief description of the
feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you
should keep in mind, and the resources available to help you.
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
GIVE US FEEDBACK
We welcome your comments and suggestions to improve the content. Please send us your feedback at
oracle_fusion_applications_help_ww_grp@oracle.com
OPTIONAL UPTAKE OF NEW FEATURES (OPT-IN)

We continue to add many new features to the Oracle Cloud Applications, and for some features, you can take
advantage of new functionality at a pace that suits you by “opting in” to the feature when you’re ready. You can
opt-in to a feature in two ways: by using the New Features work area, or by using the Setup and Maintenance
work area.
3
To opt-in using 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 Opt-In for any feature that you want to opt-in to.
4. On the Edit Features page, select the Enable option for the feature, and then click Done.
To opt-in using the Setup and Maintenance work area:
1. Click the Navigator, and then click Setup and Maintenance.

2. On the Setup page, select your offering, and then click Change Feature Opt-In.
3. On the Opt-In page, click the Edit Features icon.
4. On the Edit Features page, select the Enable option for any feature you want to opt-in to. If the Enable
column includes an Edit icon instead of a check box, then click the icon, select your feature options, and
click Save and Close.
5. Click Done.
OPT-IN EXPIRATION
Some features include an opt-in expiration update, after which they are no longer optional. If you have not opted
in to the feature by the expiration update, it will automatically be enabled for you in that update.
Click here to review details of all Oracle Applications Cloud features with an upcoming opt-in expiration update.
4
FEATURE SUMMARY
Column Definitions:
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.
Customer Action Required = You MUST take action 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 Customer Must Take Action before Use by End Users
(Feature Delivered Enabled) (Feature Delivered Disabled)
Reports plus Small Scale UI or Process-Based new features Not disruptive as action is required to make these features
will have minimal user impact after an update. Therefore, ready to use. As you selectively choose to leverage, you
customer acceptance testing should focus on the Larger set your test and roll out timing.
Scale UI or Process-Based* new features.
UI or UI or
Process-Based: Process-Based:
Feature Report Small Scale Larger Scale* Customer Action Required
COMMON TECHNOLOGY AND USER EXPERIENCE
Common Financials Features
Auto Dismiss Popup
Performance Enhancement in General Accounting
Dashboard and Intercompany Work Area
Simplified Workflow Rules Configuration
REST APIs for Financials
REST APIs for Currency Rates
REST APIs for External Bank Accounts
REST APIs for Journals
REST APIs for Ledger Balances
REST APIs to Manage Country Specific UI Rules for
Simplified Bank Accounts
5
UI or UI or
REST APIS for Payments
REST APIs for Salesperson Reference Account
REST APIS for Supplier Invoices
FINANCIALS
Assets
Investment Allowance Deductions as Bonus
Depreciation
Budgetary Control
Budgetary Control Spend Authorizations
Carry Forward Purchase Order Budgetary Control
Balances Enhancement
Cash Management
Bank Statement Reconciliation of Rejected Lines
Manual Reconciliation Enhancements
Expenses
Spend Authorization with Budgetary Control
Usability Enhancements for Expenses
General Ledger
Multiple Segment Tracking for Revaluation Gain or
Loss
Performance Enhancements in General Accounting
Dashboard and Journals Work Area
Reverse Journal Batch
6
UI or UI or
Single Request Submission for Streamlined Journal
Batch Reversal Processing
Payables
Change First Open Period for Payables
Payables Workflow Transaction Listing Report
Supplier Portal Invoice Enhancement Phase Two
Customer and Supplier Balance Netting
Manage Netting Settlements in a Spreadsheet
Receivables
Manage Customer Data Import in Receivables
Create Detailed Receivables Distributions
Customer and Supplier Balance Netting
Manage Netting Settlements in a Spreadsheet
Revenue Management
Enhanced Handling of Invalid Contract Lines
Subledger Accounting
Upload Mappings of Subledger Accounting Mapping
Set Rules Using FBDI
Tax
Compound Tax on the Assessable Value
Tax Registration Number Validation for 5 New
Countries (Colombia, Ecuador, Mexico, Peru, and
Taiwan)
Transactional Business Intelligence for Financials
7
UI or UI or
Add Non-Qualified Segments to Oracle Transactional
Business Intelligence Fixed Assets Subject Areas
Cross-Pillar Reporting Between Receivables and
Projects
Enhancements to Cash Management Subject Areas
Enhancements to Revenue Management Subject Areas
Expose Descriptive Flexfields on Key Flexfields for
OTBI Financials Non-Essbase Subject Areas
Payables Invoices Holds Information Reorganized in
the Oracle Transactional Business Intelligence Subject
Areas
8
COMMON TECHNOLOGY AND USER EXPERIENCE
COMMON FINANCIALS FEATURES
AUTO DISMISS POPUP
Simple confirmation popups will now auto dismiss after a short delay of 2 seconds, streamlining business
process flows by removing the need to click the "OK" button to dismiss the popup. This will improve usability
and enhance performance for simple interactions in Oracle Financials Cloud.
Auto Dismiss Popup Example for Expense Reports
STEPS TO ENABLE
No steps are required to enable this feature.
PERFORMANCE ENHANCEMENT IN GENERAL ACCOUNTING DASHBOARD AND

INTERCOMPANY WORK AREA
To ensure the dashboard and work area render faster, transaction counts are no longer displayed.
STEPS TO ENABLE
SIMPLIFIED WORKFLOW RULES CONFIGURATION

The Generate Rule File button is now located on the Instructions sheet of all templates for each
workflow.
9
Instructions Sheet
You can now create workflow rules for Payables Invoice Request approvals using the Invoice Request
Approval Rules sheet. This sheet is available in all Payables Invoice Approval templates.
Invoice Request Approval Rules Sheet in the Payables Invoice Approval Rules Template
An additional sample template ‘Invoice Approval Sample template 3’ is now available for the Payables
Invoice Approval workflow on the Manage Workflow Rules in Spreadsheet page.
STEPS TO ENABLE
TIPS AND CONSIDERATIONS

You can now use the Invoice Request Approval Rules sheet to create approvals rules for Payables
Invoice Requests. This sheet is available in all Payables Invoice Approval workflow templates.
The Generate Rule File button creates a rule file for all the rules in the template. For example, for
Payables Invoice Approval rule templates, a rule file is generated for rules in the Invoice Requests
Approval and Invoice Approval Rules sheet when you click Generate Rule File.
10
Every successful rule upload using the spreadsheet template overrides all the existing rules for the
workflow. In case you do not enter rules in any of the sheets within a template, then no rules will be
created for that stage and any existing BPM rules for that stage will be cleared out.
KEY RESOURCES
For an overview of the Simplified Workflow Rules Configuration feature, refer to the Manage Workflow Rules
Using a Spreadsheet topic on the Oracle Help Center
ROLE INFORMATION
No new role access is needed to use this feature.
REST APIS FOR FINANCIALS
REST APIS FOR CURRENCY RATES

Use the Currency Rates REST API resource to retrieve currency rates and dates for which rates are available
for a source and target currency combination.
STEPS TO ENABLE
Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center
> your apps service area of interest > REST API) . If you are 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
REST APIS FOR EXTERNAL BANK ACCOUNTS

Use the External Payee, External Bank Account and Payment Instrument Assignment REST API resources to
manage details about external bank accounts. You can:
Create and manage external payees for suppliers.

Retrieve external payee information.
Create and manage external bank accounts.
Create and manage external bank account owners.
Retrieve external bank account and account owner information.
Create and manage assignments of external bank accounts to external payees or external payers.
Retrieve payment instrument assignment information.
STEPS TO ENABLE
KEY RESOURCES
11
REST APIS FOR JOURNALS

Use the Journals REST API resource to manage journals. You can:
Retrieve journals.
Update the batch completion status.
Delete the batch.
STEPS TO ENABLE
KEY RESOURCES
REST APIS FOR LEDGER BALANCES

You can now use the Ledger Balances REST API resource to retrieve general ledger balances for accounts at
a summary level.
STEPS TO ENABLE
KEY RESOURCES
REST APIS TO MANAGE COUNTRY SPECIFIC UI RULES FOR SIMPLIFIED BANK ACCOUNTS
Use the Bank Account User Rules REST API resource to manage country-specific bank, branch, and bank
account-related attributes to be displayed on the simplified bank account UI. You can:
Retrieve, create, and modify UI rules.

Update labels.
STEPS TO ENABLE
12
To change labels on the simplified bank account UI, you must create the label in the lookup code
ORA_EXTERNAL_ACCOUNT_LABELS under Cash Management lookups.
KEY RESOURCES
REST APIS FOR PAYMENTS

Use the Payables Payments REST API resource to capture additional information for your payments against
Payables invoices. You can:
View, create, and update descriptive flexfields to capture additional information for a payment.
View, create, and update global descriptive flexfields to capture additional localization information for a
payment.
STEPS TO ENABLE
You can also build integrations to:
Retrieve payment and paid invoice information.

Import paid invoices after your Oracle Financials Cloud upgrade.
Void a payment.
NOTE: Manual payments are the payments created outside of Payables and then recorded in Payables. You
can create a manual payment using the Create Payments page by selecting the payment type Manual.
KEY RESOURCES
REST APIS FOR SALESPERSON REFERENCE ACCOUNT

Use the Salesperson Reference Account REST API resource to create, find, and delete reference accounts for
a salesperson. You can:
Create a reference account for a salesperson.

Delete a reference account belonging to a salesperson.
Find reference account details for a salesperson.
Get reference accounts belonging to a salesperson.
STEPS TO ENABLE
13
KEY RESOURCES
REST APIS FOR SUPPLIER INVOICES

Use the Invoices and Invoice Holds REST API resources to manage details about supplier invoices. You can:
Create and manage cross-currency, multi-period accounting related supplier invoices.

Capture additional localizations information for the invoice header, lines, distributions, and installments
using global descriptive flexfields.
Capture tax determinants such as intended use, transaction business category for tax calculation
purposes.
STEPS TO ENABLE
Additionally, you can build integrations based on your PaaS application requirements such as retainage,
reverse factoring arrangements, or placing invoices on hold.
NOTE:
If you are creating invoices for Americas localizations, then you will have to pass the values for global
descriptive flexfields, as currently the values do not default for this region.
If you are updating an invoice, then you can only update certain attributes and the update applies only to
those attributes. Related fields do not automatically get populated. For example, when you update the invoice
date in the Create or Edit Invoice pages, related fields, such as the terms date or due date, may be
autopopulated based on the invoice date you enter. Using REST API, the invoice date is updated, but the
related fields are not autopopulated. Before updating a key attribute, consider the impact on the related
attributes.
KEY RESOURCES
FINANCIALS
14
ASSETS
INVESTMENT ALLOWANCE DEDUCTIONS AS BONUS DEPRECIATION
Expedite your investment allowance deductions for property, plant, and equipment investment costs. Claim your
investment allowance deduction as bonus depreciation in the period of acquisition. Calculate your standard
depreciation from the net amount.
The following screenshots illustrates the feature and its benefits:
Specify Your One-Time Bonus Depreciation Period Over the Entire Fiscal Year Along with its Recapture Duration in Years
Allocate Your Entire Bonus Depreciation to the Current Open Period and Recapture it Within the Specified 5 Year Duration
15
Automatically Recapture Your Bonus Depreciation If the Asset is Fully Retired Before the Specified Duration in Years
Specify the new optional non-sale gain account in your Manage Asset books to recapture your investment
allowance or bonus depreciation as required by the accounting standards. Set up the recapture year accounting
rule default for the category book from the Manage Categories page.
STEPS TO ENABLE
You must opt in to enable this feature. For instructions, refer to the Optional Uptake of New Features section of
this document.
Offering: Financials
Specify the new optional non-sale gain account in your Manage Asset books to recapture your investment
allowance or bonus depreciation as required by the accounting standards. Set up the recapture year
accounting rule default for the category book from the Manage Categories page.
ROLE INFORMATION
The Asset Accounting Manager and Asset Accountant job roles are automatically updated.
BUDGETARY CONTROL
BUDGETARY CONTROL SPEND AUTHORIZATIONS

You can enable Budgetary Control for spend authorization to reserve funds for anticipated employee expenses.
CHECK AND VIEW FUNDS
The approver can check funds and view the impact of anticipated employee expenses on the budget, during
the approval process.
16
Approval of a Spend Authorization
REJECT INSUFFICIENT FUNDS
When the approver submits the authorization for approval, budgetary control validation is performed. If
budgetary control validation fails, the authorization is automatically rejected and returned to the employee for
further action.
Reject Authorization When Budgetary Control Failure
17
RESERVE FUNDS FOR ANTICIPATED EMPLOYEE EXPENSES
When the approver submits the authorization for approval and budgetary control validation passes, the spend
authorization amount is reserved. If the approver manually rejects the authorization, the amount is not reserved
and the authorization is returned to the employee for further action.
Reserved Spend Authorization
REIMBURSEMENT OF EMPLOYEE EXPENSES
After incurring the business expense, the employee creates an expense report and associates it with a spend
authorization. The payment of the expense report reclassifies the consumption from anticipated to actual
expense.
18
Budgetary Control Analysis Report
INQUIRY AND REPORTING OF BUDGET IMPACT FOR EMPLOYEE EXPENSES
All existing budgetary control and analysis reporting supports anticipated and paid employee expenses.
Budgetary Control Results by Transaction Report
STEPS TO ENABLE
OVERVIEW OF SETUP
1. Enable the Request Spend Authorization with Budgetary Control feature found under the Financials
offering.
2. Enable spend authorizations for budgetary control in Manage Budgetary Control.
3. Set up spend authorizations in Manage Cash Advance and Authorization policies. Refer to the Steps to
Enable section for the Spend Authorization with Budgetary Control feature in this What's New document.
MANAGE BUDGETARY CONTROL
1. Enable budgetary control for the expense management business function and the spend authorization
transaction type.
19
Edit Budgetary Control and Encumbrance Accounting for Expense Management Business Function
2. Enable budgetary control spend authorization payment request transaction subtype for the payables
invoicing business function.
NOTE: If you do not enable the spend authorization payment request transaction subtype, the spend
authorization will not be converted to an expense.
20
Edit Budgetary Control and Encumbrance Accounting for Payables Invoicing Spend Authorization Subtype

If Budgetary Control is already enabled then:
Spend authorization is disabled by default. You must enable spend authorization and
payment request transaction types. Note: If you do not enable the spend authorization payment
request transaction subtype, the spend authorization will not be converted to an expense.
Rebuild budgetary control cube. The cube must be rebuilt to allow for this new transaction
type balance to be stored . Run the Create Budgetary Control Balances Cube
process. See support note Maintaining Budgetary Control Cubes (Doc ID 2136813.1) for more
information.
There is no accounting when spend authorizations are approved. Accounting is created for payment
requests related to the anticipated employee expense.
Project control budgets are not impacted and burdening is not calculated.
KEY RESOURCES
For more information, refer to the following topics in Oracle Applications online help:
Spend Authorizations: Explained

Setting Up Spend Authorizations: Points to Consider
Quick Reference for Oracle Fusion Budgetary Control Documentations support note document ID
2195106.1
Spend Authorization with Budgetary Control in the What's New Document
ROLE INFORMATION
21
Roles needed for setup of Budgetary Control and Expense Management
Budget Manager
Expense Manager
Roles needed for approving spend authorization in Expense Management

Expense Manager
Roles needed for Inquiry and Reporting Budget Impact
Budget Manager
CARRY FORWARD PURCHASE ORDER BUDGETARY CONTROL BALANCES ENHANCEMENT

You can have greater flexibility and control over the purchase order and budget balances being carried forward
from year to year. There are two new parameters and one relabeled parameter for this program.
Carry Forward Purchase Order Budgetary Control Balances Process
1. PO Charge Account Filter
Use this new parameter to select which purchase orders you want to carry forward by charge
account. This also gives you the flexibility to manage the budget options differently for groupings of
purchase orders by specifying conditions on any of the accounting flexfield segments. Add chart of
accounting flexfield segment, condition and value to meet your specific carry forward business
requirements. If you don't add any filters, all purchase orders that meet the other parameter criteria will
be selected.
22
PO Charge Account Filter
2. Keep funds available unchanged in the carry forward from year
This is a new parameter. It is available when the Run Mode is Final. Finally closing a purchase order
will increase funds available, which allows other transactions to consume these funds. Select this
parameter to indicate that a budget adjustment be made to reduce funds available by same amount. This
will keep funds available unchanged in the carry forward from year.
3. Include budget for purchase orders in the carry forward to year
This parameter has been renamed but there is no change in functionality. This parameter was previously
labeled Include Budget for Purchase Orders Carried Forward. If you select this parameter, the
budget will be created for the purchase order obligation amount in the budget period of the specified
Reopen Budget Date parameter.
STEPS TO ENABLE
There is no setup required for these new parameters.

When the Keep funds available unchanged in the carry forward from year parameter is selected,
the budget will be reduced in the budget period associated with the Finally Close Through Budget
Date parameter.
If you use the PO Charge Account Filter, you may have to submit the Carry Forward Purchase Order
Budgetary Control Balances process multiple times to achieve the desired results.
For example, you have fund values defined as A through Z. Your requirements are:
fund values A through D and funds values L through S should carry forward the obligation as well
as the budget amounts
23
fund values E through K and fund values T through Z should carry forward only the obligation
all fund values should keep funds available unchanged in the carry forward from year.
To carry forward these results, the process must be submitted four times using the following PO Charge
Account Filter and parameter values:
Keep funds available Include budget for purchase

PO Charge Account Filter Fund
unchanged in the carry orders in the carry forward to
Values
forward from year year
Between A and D Yes Yes
Between L and S Yes Yes
Between E and K Yes No
Between T and Z Yes No
KEY RESOURCES
Refer to support note, Oracle ERP Cloud Budgetary Control Carry Forward Release 10, Release 11 and
Release 13 (Doc ID 2208855.1) for the Budgetary Control Carry Forward white paper.
ROLE INFORMATION
Budget manager role is needed to run the Carry Forward Purchase Order Budgetary Control Balances process.
CASH MANAGEMENT
BANK STATEMENT RECONCILIATION OF REJECTED LINES

Use the Bank statement reconciliation of rejected lines feature to manually unreconcile any individual payment
or receipt from the reconciled transactions group based on the rejection information received from banks.
STEPS TO ENABLE
this document.

In the reconciled tab of the manual reconciliation page, identify the reconciled transaction group that you
want to adjust. Select the individual line you want to unreconcile from the group, and use the new action
'Unreconcile Transaction' from the Actions menu.
The reconciliation group will be balanced by creating an external transaction of the same amount, with
the origin ‘Reversal Reconciliation’.
The external cash transaction will be created in the reconciled status with the accounting option
unselected.
The external cash reference will be populated according to the system transaction reference.
24
KEY RESOURCES
For more information on Bank Statement and Reconciliation solution, refer to Oracle Financials Cloud Using
Payables Invoice to Pay, or Oracle Financials Cloud Using Receivables Credit to Cash.
MANUAL RECONCILIATION ENHANCEMENTS

The Manual Reconciliation page has been enhanced to improve user experience. You can now add additional
columns, including the Transaction Number, to the system transactions table results.
STEPS TO ENABLE
KEY RESOURCES
For more information on Manage Bank Statements and Reconciliation, refer to Oracle Financials Cloud Using
Payables Invoice to Pay, or Oracle Financials Cloud Using Receivables Credit to Cash on the Oracle Help
Center
ROLE INFORMATION
The Manual Reconciliation page is controlled by the existing privileges.
EXPENSES
SPEND AUTHORIZATION WITH BUDGETARY CONTROL

You can now reserve funds when you submit a spend authorization for anticipated expenses. When spend
authorization is enabled for your business unit, control budgets are associated with each expense type that you
want to reserve funds for. When you submit a spend authorization, the application automatically checks
whether sufficient funds are available and rejects the spend authorization if there are insufficient funds.
The application sends a spend authorization approval request to the approver when there are sufficient funds.
You and the approvers have full visibility into the funds status. Before approving, approvers can check funds to
review funds availability.
25
Approval Notification
If there are multiple approvers, the application checks for sufficient funds before sending the approval request to
each approver. Funds are reserved only on final approval and if sufficient funds are available. Rejected spend
authorizations are returned to you for further action.
26
Overall Funds Reservation Status and Funds Availability for Estimated Expenses
When a spend authorization is approved, it is available for use against actual expenses. You assign an
approved authorization to each expense in your expense report. The application alerts you when the expense
account is different from the authorization account. The application prevents you from submitting the expense
report if the report total exceeds the reserved funds. Approvers can review the authorization associated with the
actual expense when they approve expense reports.
27
Selection of Authorization in Expense Reports
When you enable spend authorization with budgetary control, the application creates a payments request and
liquidates the reservation when validating the payment request. You can review the funds details for the
payment request in the Manage Invoices page.
Funds Details in Manage Invoices
Budgetary control actions to check and reserve raw cost amounts are not supported for project-related spend
authorizations when the project is enabled for budgetary control and the project has a top resource control
budget. Similarly, burden amount for project-related spend authorizations are not reserved. Burden amount is
reserved only when the invoice is created for the expense report related to the spend authorization.
STEPS TO ENABLE
28
this document.
SETUP TASKS
You must perform the following two setup tasks to enable budgetary control for spend authorization:
Enable spend authorization for budgetary control on the Manage Budgetary Control page. Refer to the
Steps to Enable section for the Budgetary Control Spend Authorizations feature in the What's New
document.
Set up spend authorizations on the Manage Cash Advance and Authorization Policies page.
SETTING UP SPEND AUTHORIZATIONS IN MANAGE CASH ADVANCE AND AUTHORIZATION POLICIES
1. In the Setup and Maintenance work area, navigate to the Manage Cash Advance and Authorization
Policies task.
2. To enable spend authorization for the company, select Yes from the Enable Authorizations choice list in
the All Business Units section. Steps 2 through 5 are optional steps and are used only for defaulting the
values for specific business units. Business unit-level setup is required to enable spend authorization.
3. Select Lines Only from the Attach Authorization choice list.
4. Select Required from the Behavior choice list.
5. In the Budgetary Control section, select the Reserve Funds value from the Funds Application choice list.
To only check funds, select the Check Funds value from the Funds Application choice list.
6. To enable spend authorizations for a specific business unit, select the Create icon in the Specific
Business Units section.
7. In the Create Business Unit-Specific Cash Advance Policies dialog box, select the applicable business
unit from the Business Unit choice list.
8. On the Authorizations tab, select the applicable values for the Enable Authorizations,
Attach Authorization, and Behavior choice lists. To use the settings applicable to all business units, select
the Use setup from all business units option.
9. In the Budgetary Control section, select the Reserve Funds value from the Funds Application choice list.
To only check funds, select the Check Funds value from the Funds Application choice list.
10. When the selection is Check Funds, select Yes from the Display Warning to User choice list to display
funds check warning to employees. Select No to hide funds check warning to employees.
11. Click Save and Close.
KEY RESOURCES
For more information about spend authorizations with budgetary control, refer to the following topics in Oracle
Applications online help:
Spend Authorizations: Explained

Setting Up Spend Authorizations: Points to Consider
Expense Reporting and Budgetary Control: How They Work Together
Quick Reference for Oracle Fusion Budgetary Control Documentation support note document ID
2195106.1
Budgetary Control Spend Authorizations in What's New Document
Watch Request Spend Authorization With Budgetary Control Readiness Training
29
ROLE INFORMATION
To enable spend authorizations in Budgetary Control, you must have the following role:
Budget Manager
To enable spend authorizations in Expenses, you must have one of the the following roles:
Expense Manager
Application Implementation Consultant
Financials Administrator
USABILITY ENHANCEMENTS FOR EXPENSES

To enable you to quickly submit and approve expenses, we have made several improvements to the expense
entry and approval pages. You can now modify selected expense details right from the work area and the
expense report page, which eliminates the need to drill down to the details, especially for corporate card
charges.
Editable Expenses List
From the Expenses work area, you can now easily perform the following tasks:
Select multiple expense by selecting applicable check boxes

Delete multiple expense items simultaneously by selecting applicable check boxes
Modify expense type and description
Attach receipts
Sort expenses by location and description
From the Create Expense Report page, you can perform the following tasks:
Modify expense type and description

Attach receipts
Sort expenses by location and description
30
Editable Work Area
Single Page Expense Entry
You can enter complete details of an expense, including itemization and attendees, in a single page,
which provides full visibility into the expense details at once. Additionally, the following capabilities are
now available.
Support for addition and subtraction operations in the Amount and the Daily Amount fields in
itemization, so you can calculate totals within the field.
Drag and drop receipt images
Single Page Expense Entry
Enhanced Expense Report Approval Notification Emails
Expenses lets you choose from two types of predefined expense report approval notification emails, such
as email approval notification with fixed layout and configurable notifications. The redesigned email
31
approval notification with fixed layout provides better usability and enables you to quickly spot high value
expenses. Enhancements to notification emails include the following:
Airline expenses are displayed as a separate section.

Expenses are ordered by absolute amount in descending order, date in ascending order, and
expense type in ascending order.
Amount is displayed in the approver's currency.
Details such as merchant, description, violations, justification, project information, and cost center
are displayed when applicable.
Enhanced Approval Notification
STEPS TO ENABLE
this document.
No Longer Optional From: 11.13.20.01.0
KEY RESOURCES
For more information about the usability enhancements, refer to the following topic in Oracle Applications
online help:
Setting Up and Using HTML Email Approval Notifications: Procedure
ROLE INFORMATION
32
To enable Usability Enhancements for Expenses, you must have the Application Implementation Consultant
role. When enabled, users with the Employee role can access the features.
GENERAL LEDGER
MULTIPLE SEGMENT TRACKING FOR REVALUATION GAIN OR LOSS

You can now track revaluation gain or loss using multiple segments in your chart of accounts.
STEPS TO ENABLE
this document.
Functional Area: General Ledger
Feature: Multiple Segment Tracking for Revaluation Gain/Loss
OVERVIEW OF SETUP
1. Edit the required key flexfield structure and assign the segment label Revaluation Gain/Loss Tracking
Segment to the segments you would like to use for revaluation gain/loss tracking. Deploy the General
Ledger Accounting flexfield after you have saved your changes.
Assign Segment Label
2. Enable option Track Revaluation Gain or Loss by Multiple Segments for the desired ledger in the Specify
Ledger Options page.
33
Enable Option for Ledger

You can now optionally track revaluation gain or loss for up to 5 distinct segments in your chart of
accounts structure, including your balancing segments.
Balancing, Natural Account and Intercompany segments should not be qualified as a revaluation gain
/loss tracking segment.
If you have 1 balancing segment in your chart of accounts, you can qualify 4 additional segments that are
not the Natural Account or Intercompany segment, as a revaluation gain or loss tracking segment. If you
have 2 balancing segments, then 3 additional segments can be qualified as tracking segments, or if you
have 3 balancing segments, then 2 additional segments can be qualified.
KEY RESOURCES
For more information about defining and generating revaluations, refer to the Oracle Financials Cloud Using
General Ledger guide in the Oracle Help Center
Watch Multiple Segment Tracking for Revaluation Gain or Loss Readiness Training
ROLE INFORMATION
No additional roles are required to work on this feature.
PERFORMANCE ENHANCEMENTS IN GENERAL ACCOUNTING DASHBOARD AND JOURNALS

WORK AREA
To ensure the dashboard and work area render faster, the following changes have been made:
Transaction counts are no longer displayed in the Journals section.
Approval-related Approve and Reject buttons will always display in the Journals section, regardless of
whether the user is the approver. If the user cannot approve or reject the transaction, an appropriate
message will be displayed.
34
STEPS TO ENABLE
REVERSE JOURNAL BATCH

You can now provide batch level reversal information to reverse all reversible journals within a batch.
STEPS TO ENABLE
The feature is automatically available as part of General Ledger journal processing.

You can use the batch reversal feature in the Edit Journal and Manage Journal pages.
You can now optionally provide batch level reversal information and have this applied automatically to all
unreversed journals within the batch.
If you do not provide this, only those journals in the batch that already have reversal information at the
journal level will be reversed.
The batch level reversal information provided will override what is specified at the journal level for
unreversed journals when the batch reversal is submitted.
In the Manage Journals page, you can select multiple journal batches for the Reverse Batch action to
process all unreversed journals of the selected batches that already have reversal information.
Display the Reversal Status, Reversal Period and Reversible Detail columns in the Manage Journals
page to get more insights about reversing the journal or journal batch.
KEY RESOURCES
For more information about reversing journals, refer to the Oracle Financials Cloud Using General Ledger
guide in the Oracle Help Center (http://docs.oracle.com).
ROLE INFORMATION
The General Accounting Manager and General Accountant can reverse journals and journal batches, and
perform other journal processing actions like entering and posting journals.
SINGLE REQUEST SUBMISSION FOR STREAMLINED JOURNAL BATCH REVERSAL

PROCESSING
For journal batch reversal processing, separate reversal requests were previously launched for each journal in
the batch that was submitted for reversal. This has now been streamlined with only a single reversal request
being launched for the whole batch. Individual reversal batches will continue to be generated for each journal
in the batch that is reversed.
STEPS TO ENABLE
35
PAYABLES
CHANGE FIRST OPEN PERIOD FOR PAYABLES

You can now change the first Payables period if it was originally set after the first General Ledger period. For
example – if the first General Ledger period was set as 01-JAN-2019 and the first Payables period is set as 01-
MAR-2019 – you can now move the first payables period to 01-JAN-2019. Previously, this was not possible.
You can use the below task to change the first Payables period.
Change First Payables Period
STEPS TO ENABLE
This option will be enabled only if the first Payables period was originally set after the first period of General
Ledger. If General Ledger first period and Payables first period are the same then this option is not visible.
PAYABLES WORKFLOW TRANSACTION LISTING REPORT

Use the Payables Workflow Transaction Listing Report to view transactions that are pending and rejected in
the Invoice Account Coding workflow. Pending transaction report allows users to view the list of invoices that
are pending with the users for entering accounting information. The rejected transactions report allows users to
view list of invoices that are rejected by the users and reason for rejection.
Pending Transaction Report
36
Rejected Transaction Report
STEPS TO ENABLE
1. Navigate to Schedule Processes page
2. Click on Schedule New Process
3. Search and Select Payables Workflow Transaction listing
4. Submit Report
Screenshot: Payables Workflow Transaction Listing
37
ROLE INFORMATION
This feature is available to users having the Initiate Payables Invoice Approval Task Flow privilege.
SUPPLIER PORTAL INVOICE ENHANCEMENT PHASE TWO

The Supplier Portal Invoicing Enhancement Phase Two brings in a new set of features which are explained
below.
1. Enhanced Supplier Portal UI: The UI has been enhanced for better usability by re-arranging the fields
that allow for quicker data entry. Now the Freight and Miscellaneous lines are created in the section
where the item lines are created.
Create Invoice Without Purchase Order
38
Create Invoice with Purchase Order
Freight and Miscellaneous Lines Along with Item Lines
2. New tax driver on invoice lines: Suppliers can now apply different taxes for every invoice line by
providing a Tax Classification Code. The tax driver can be provided for all invoice line types (Item, Freight
and Miscellaneous).
Tax Classification Code on Invoice Lines
3. Edit Rejected Invoices: Supplier users can now edit and resubmit invoices that are rejected from the
approval users during the invoice request approval process. The supplier users will see the invoice status
as rejected and when accessed the invoice will be opened in the Edit mode. After making necessary
changes, based on the rejection comments from approval users, the supplier can resubmit the modified
invoice. Users can recognize the invoices with Invoice Type as "Standard Invoice Request" and the
status as "Rejected".
39
Rejected Invoice
4. Approval actions for Payables user: When the approval for the Standard Invoice Request (Supplier
Portal Invoices) is in progress, the Payables users can now perform actions similar to what they can do
during the standard invoice approval process. The actions allowed on Standard Invoice Request are:
Withdraw, Resubmit and Force Approve.
Withdraw: Payables user can withdraw the invoice request workflow on unmatched supplier portal
invoices when the approval is still in process. On withdrawal of approval the approval status will be
stamped as "Withdrawn" and the supplier will see the invoice status as "Pending Import".
Resubmit: The Resubmit action is only allowed for invoice request that was withdrawn or rejected.
The Resubmit action is allowed only in the online mode.
Force Approve: Payables user will be able to Force Approve an invoice request workflow when the
approval is still in process, rejected or is withdrawn. On Force Approval, the status will be visible to
suppliers as "In Process". Force Approval is a secured action and the user would need the
security privilege "Force Approve Payables Invoice" to perform the action.
5. Cancel Standard Invoice Request: Payables users can now cancel supplier portal invoices when the
invoice request approval is in progress. On Cancellation of the Standard Invoice Request
The invoice status will be updated as "Canceled". The invoice amount will be marked as zero and
the taxes will be reversed.
The supplier user will see the status as "Canceled".
Invoice request approval process will be automatically withdrawn.
STEPS TO ENABLE
No setups are required to enable this feature. You only need to enable the feature Opt-in “Supplier Portal
Invoicing Enhancement”.
Consider the following when working with invoices from the Supplier Portal:
1. When the Invoice Request Approval process is rejected by the users, only the supplier users will be able
to edit the invoice from the supplier portal and submit the invoice. Payables users will not be able to edit
them.
2. When Invoice Request Approval process is rejected by the system, only the Payables users will be able
to resubmit them. Supplier users will not be able to edit and resubmit them from the supplier portal.
3. Resubmission of system rejected invoices can be done only in the online mode. Resubmission is not
supported through the program "Initiate Invoice Approval Workflow".
4. Force Approval is a secured action and Payables user would need the security privilege "Force Approve
Payables Invoice" to perform the action.
ROLE INFORMATION
40
No additional roles are required to work on this feature.
CUSTOMER AND SUPPLIER BALANCE NETTING
MANAGE NETTING SETTLEMENTS IN A SPREADSHEET

Use the Manage Netting Settlements in a Spreadsheet feature to process settlements that are in progress.
Settlements that are in Selected or Selected, no transactions status can be downloaded to a spreadsheet and
processed as follows:
Selected: You can review, delete, or mark them to be settled.

Selected, no transactions: You can delete them from the spreadsheet.
The spreadsheet lets you delete or settle a netting settlement. After all changes are complete, you can save and
submit the settlements for processing.
Watch a Demo
STEPS TO ENABLE
Refer to the Customer and Supplier Balance Netting Topical Essay for detailed implementation guidance:
https://cloud.oracle.com/opc/saas/datasheets/netting-topical-essay.pdf
Use the Manage Netting Settlements page to search for the types of settlements that you wish to process. For
example :
Settlements that belong to a Legal Entity

Settlements that are in Selected or Selected, no transaction status
Settlements that have the same Settlement Name
KEY RESOURCES
Customer and Supplier Balance Netting Topical Essay: https://cloud.oracle.com/opc/saas/datasheets
/netting-topical-essay.pdf
Watch Manage Netting Settlements in a Spreadsheet Readiness Training
ROLE INFORMATION
The Manage Netting Settlements in a Spreadsheet is automatically made available to you if you have
already completed the Netting Security Setup Steps.
Details of the setup can be found here: https://cloud.oracle.com/opc/saas/datasheets/loc-sec-topical-
essay.pdf
41
RECEIVABLES
MANAGE CUSTOMER DATA IMPORT IN RECEIVABLES

You can now manage the import of customer data into Receivables using the Manage Data Import task.
The Manage Data Import task is available from the Receivables Billing work area.
NOTE: The Data Import task previously available in the application navigator under Customer Data
Management is now obsolete.
STEPS TO ENABLE
If a user has saved the previous navigation to the Data Import Task in Favorites and Recent Items, then these
need to be redefined to the new navigation.
ROLE INFORMATION
Receivables Manager and Receivables Specialist roles already have access to the two duty roles that secure
the Manage Data Import task in Receivables: Trading Community Import Batch Management Duty and Trading
Community Import Process Management Duty.
CREATE DETAILED RECEIVABLES DISTRIBUTIONS

The Create Detailed Receivables Distributions feature provides the capability to split consolidated Receivables
and Cash distributions in proportion to the balancing segments used for accounting a transaction. Having
detailed distributions provides better visibility into operations at the segment level, where a segment may
represent a fund, a product, or a line of business.
At this time, this feature is intended only for the public sector industry.
NOTE: The predefined options and setup data for the Detailed Distributions feature are labeled as Multifund
Accounting. These are synonymous terms.
42
Example
STEPS TO ENABLE
this document.
Enabling detailed distributions for Receivables is a three-step process.
1. Enable the Feature Opt-in.

2. Enable it for a business unit (and ledger) in Receivables System Options.
3. Create a Subledger Accounting Method (SLAM) and associate it with the ledger.
RECEIVABLES SYSTEM OPTIONS
1. Click the Navigator, and then Setup and Maintenance.

2. Search for the task ‘Manage Receivables System Options’.
3. From this page, search for the business unit that requires the detailed distributions feature.
4. From the ‘Edit System Options’ page, enable the option ‘Enable multifund accounting’.
On enabling this option for a business unit, the detailed distributions feature becomes automatically applicable
to all other business units that share the same Ledger.
This selection cannot be reverted once enabled. Because of this, a warning message is displayed before
confirming the selection. Choose ‘Yes’ to continue.
43
SUBLEDGER ACCOUNTING METHOD
Create a Subledger Accounting Method for supporting the creation of detailed distributions and associate it with
the Ledger:
1. Click the Navigator, and then Setup and Maintenance.

2. From the Task Pane (right side of the page) select the task ‘Manage Implementation Projects’.
3. Using the reference of an Implementation Project, search for the task ‘Manage Accounting Methods’ from
the Receivables configuration.
4. Search for the predefined Accounting Method ‘Standard Accrual’ and duplicate it.
5. In the section for Journal Entry Rule Set Assignments for Receivables, delete the existing rule sets for
Adjustment, Debit Memo, Credit Memo, Invoice, Miscellaneous Receipt and Receipt.
6. Re-create these records using the following predefined Rule Sets for Multifund Accounting:
Adjustment: 'Adjustments - Multifund Accounting Balancing Method'
Debit Memo: 'Debit Memos - Multifund Accounting Balancing Method'
Credit Memo: 'Credit Memos - Multifund Accounting Balancing Method'
Invoice: 'Invoices - Multifund Accounting Balancing Method'
Miscellaneous Receipt: 'Miscellaneous Receipts - Multifund Accounting Balancing Method'
Receipt: 'Receipts - Multifund Accounting Balancing Method'
7. Activate the Accounting Method from Menu Actions > Change Status
The predefined Journal Entry Rule Sets associated with the Accounting Method will have the default status as
‘Incomplete’. On activating the Accounting Method (as stated in step-7), the corresponding Journal Entry
Rule Sets will also receive the status ‘Active’.
44
Associate this custom Accounting Method to the Ledger:
1. Using the reference of an Implementation Project, search for the task ‘Specify Ledger Options’.
2. Access the task using the scope of the Ledger for which Multifund Accounting is enabled (through the
corresponding business unit).
3. For this ledger, select the custom Accounting Method created for Multifund Accounting, in the section for
Subledger Accounting.

1. On enabling Multifund Accounting for a business unit within Receivables System Options, it becomes
automatically applicable to all the business units associated with the same ledger. If any business unit
associated with this ledger does not require multifund accounting, then it should be de-linked from that
ledger.
2. Multifund Accounting can be enabled only when there are no transactions for the business units
associated with the ledger. In addition, this choice cannot be reverted once selected. Therefore, the
decision to implement Multifund Accounting should be a part of your overall implementation
considerations, after analyzing all of your business requirements.
3. Multifund Accounting setup should be enabled before migrating the transactions from the legacy system
to Oracle Financials Cloud.
4.
45
4. All legacy transactions should be migrated as open balances (for each invoice line) using either an FBDI
template or REST service, and they should be posted to General Ledger. The option 'General Ledger
Journal Entry Summarization' on the Accounting Options Page should be set as 'Summarize by General
Ledger Date' to have all the migrated Invoices posted to a single Journal. This Journal can be manually
reversed so that it does not contradict with the open balances migration done through the General
Ledger process. It also avoids unwanted entries for Revenue/Freight/Taxes in the current period.
ROLE INFORMATION
There are no changes to the job roles or any other existing privileges for using the detailed distributions
feature. Also, the process to account and view the distributions within the Subledger and General Ledger
remains the same.
CUSTOMER AND SUPPLIER BALANCE NETTING
MANAGE NETTING SETTLEMENTS IN A SPREADSHEET

Use the Manage Netting Settlements in a Spreadsheet feature to process settlements that are in progress.
Settlements that are in Selected or Selected, no transactions status can be downloaded to a spreadsheet and
processed as follows:
Selected: You can review, delete, or mark them to be settled.

Selected, no transactions: You can delete them from the spreadsheet.
The spreadsheet lets you delete or settle a netting settlement. After all changes are complete, you can save and
submit the settlements for processing.
Watch a Demo
STEPS TO ENABLE
Refer to the Customer and Supplier Balance Netting Topical Essay for detailed implementation guidance:
https://cloud.oracle.com/opc/saas/datasheets/netting-topical-essay.pdf
Use the Manage Netting Settlements page to search for the types of settlements that you wish to process. For
example :
Settlements that belong to a Legal Entity

Settlements that are in Selected or Selected, no transaction status
Settlements that have the same Settlement Name
KEY RESOURCES
Customer and Supplier Balance Netting Topical Essay: https://cloud.oracle.com/opc/saas/datasheets
/netting-topical-essay.pdf
Watch Manage Netting Settlements in a Spreadsheet Readiness Training
46
ROLE INFORMATION
The Manage Netting Settlements in a Spreadsheet is automatically made available to you if you have
already completed the Netting Security Setup Steps.
Details of the setup can be found here: https://cloud.oracle.com/opc/saas/datasheets/loc-sec-topical-
essay.pdf
REVENUE MANAGEMENT
ENHANCED HANDLING OF INVALID CONTRACT LINES

You can now specify how invalid source document lines are handled during the accounting contract creation
process.
The Reject line option ignores the invalid source document lines and creates the contract with only the
valid source document lines.
The Reject contract option suspends the contract creation until all of the source document lines are valid.
Invalid source document lines are lines that have failed the Revenue Management data validation process.
Manage System Options for Revenue Management
MANAGE SYSTEM OPTIONS FOR REVENUE MANGAGEMENT – INVALID LINE HANDLING
There are two values for the Invalid Line Handling option:
Reject line
Reject contract
When the Invalid Line Handling option is set to Reject contract:
47
The contract creation process is suspended for source documents with invalid source document lines
until all of the invalid source document lines are corrected and error free.
The valid and invalid source document lines are displayed in the Correct Source Document Line Error
worksheet.
The valid source document’s lines are assigned a Related Line Error indicating that the line is valid but
not processed due to associated source document lines that contain data errors.
Once the invalid source document lines are corrected, a contract is created that includes all of the now
valid source document lines.
When the Invalid Line Handling option is set to Reject line or Blank:
The contract creation process is executed for all valid source document lines, regardless of whether there
are related contract lines in error status.
Only the invalid source document lines are displayed in the Correct Source Document Line Error
worksheet.
Once the related invalid source document lines are corrected, the corrected lines are added to a new
contract if the existing contract is frozen.
ContractDocCorrection.xls
CORRECT CONTRACT DOCUMENT ERRORS IN SPREADSHEET
When the Invalid Line Handling option is set to Reject contract:
The valid and invalid source document lines are displayed in the Document Line Error tab of the Correct
Contract Document Errors worksheet.
When the source document line cannot be assigned a Contract ID String, the line is displayed with a
Contract ID String error.
The valid source document lines are assigned a Related Line Error indicating that the line is valid but not
processed due to associated source document lines that contain data errors.
You can change the Data Transformation Status from Unprocessed to Purge or Reject so that the invalid
line can be excluded and processing can continue.
Use the worksheet to correct and reprocess the invalid source document lines.
When you upload your updates in the worksheet, the Validate Customer Contract Data process is
executed and the lines are reprocessed.
When the Invalid Line Handling option is set to Reject line or Blank:
48
Only the invalid source document lines are displayed in the Document Line Error tab of the Correct
Contract Document Errors worksheet.
You can change the Data Transformation Status from Unprocessed to Purge or Reject so that the invalid
line can be excluded and processing can continue.
Use the worksheet to correct and reprocess the invalid source document lines.
STEPS TO ENABLE
When using the Invalid Line Handling feature:
The Invalid Line Handling option can be modified. The default value is Blank.
Profile option changes takes effect from the time the changes are saved, and are applied to all
processing from that point forward.
Profile option changes are not retrospectively applied.
Contracts are identified and assigned unique Contract ID Strings by the Validate Customer Contract
Source Data process.
When lines are reprocessed, the latest active contract identification rules are applied when
determining the Contract ID String for the line.
If the source document line status is Unprocessed and the Contract ID String is not blank, the
Contract ID String is updated with the new value and the source document line status is set based
on the source document line status of the revised Contract ID String.
If the Contract ID String is blank for a line, the line is tagged as Unprocessed and assigned a
Contract ID String error.
You can correct invalid or missing Contract ID Strings using the spreadsheet.
You can change the Data Transformation Status from Unprocessed to Purge or Reject so that the
invalid line can be excluded and processing can continue.
After lines are reprocessed, invalid lines with a status of Purge are deleted from the table
and lines with a status of Reject are ignored.
After you save and upload the worksheet, corrections to the line and all other lines with the same
Contract ID string value are reevaluated and processed.
When Invalid Line Handling option is changed from Reject line to Reject contract:
New logic will be applied from that point forward.
Changes apply only to new lines and unprocessed lines, once they are corrected.
Lines are eligible for further contract creation processing only when all of the lines with the same
Contract ID String are in a status of Processed.
Source document lines in a status of Processed that have the same Contract ID String will be
processed.
When the Invalid Line Handling option is changed from Reject contract to Reject line:
Changes apply only to new and corrected lines.
After lines are reprocessed, any line with the same Contract ID String in a status of Processed is
converted to a contract, regardless of whether there are other lines with the same Contract ID
String in a status of Unprocessed.
Use caution when assigning invalid source document lines a status of Purge on the Correct Contract
Document Errors spreadsheet. When the lines are reprocessed, they are deleted from the table and are
unavailable for future processing unless they are reloaded as new lines.
49
ROLE INFORMATION
SUBLEDGER ACCOUNTING
UPLOAD MAPPINGS OF SUBLEDGER ACCOUNTING MAPPING SET RULES USING FBDI

You can import high volume mappings using the subledger accounting file-based data import mappings
spreadsheet template.
To do this, you must use the Create Mapping Set page to create a mapping set rule definition with
corresponding input sources and output types before adding the mappings using the subledger accounting
mapping import template.
Add the mappings by completing and uploading the spreadsheet template with the following steps:
1. Download the Subledger Accounting Mapping (XlaImportMappings) spreadsheet template from File-
Based Data Import for Oracle Financials Cloud guide.
2. Enter the mapping information in the Mappings worksheet. There are examples provided. For examples,
using the account combination or segment value as the output for the mappings.
Subledger Accounting Mappings Import Spreadsheet Template
After you finish preparing the mapping data in the spreadsheet template, click the Validate button
to validate date format, line numbers, required fields, and default mapping. Correct any error
reported.
You can save the original XlaImportMappingsTemplate with any name.
Next, click the Generate CSV File button in the Instructions and CSV Generation worksheet tab.
The Process generates both a CSV file and ZIP file.
Review the generated XlaImportMappingsTemplate.csv that is appended as a worksheet in
the same spreadsheet. It must have the same number of mapping lines that exist in the
Mappings worksheet.
The next step is to load the generated .ZIP file to the interface and application database tables.
Navigate to the Scheduled Processes workarea.
Select the Load Interface File for Import process.
Select the Import Accounting Setup process.
Upload the XlaImportMappingsTemplate.zip data file and upload it.
50
STEPS TO ENABLE

1. Use this FBDI spreadsheet solution to upload high volume mappings that have more than 2,000 lines -
for mapping set rules. Use the existing mappings import feature or enter mappings using the user
interface for low volume mappings.
2. Review the log and output files of the Load File to Interface child process for information about the data
that caused the failure.
3. Review the log and output files of the Import Accounting Setup process for information about errors from
validations performed by the application. For example, duplication of mappings.
KEY RESOURCES
For more information on using the Subledger Accounting Mapping template, refer to Oracle Financials
Cloud Implementing Subledger Accounting or Oracle Financials Cloud Using Subledger Accounting on
the Oracle Help Center.
Implementing Subledger Accounting: Subledger Accounting Mappings Import: How Data Is Processed
Watch Import Mappings Using File Based Data Import Readiness Training
ROLE INFORMATION
Shipped job role:
Application Implementation Consultant
NOTE: When defining a new user-defined job role, it must contain the following:
The privileges to manage mapping sets:

Manage Subledger Mapping Sets
Manage Subledger Mapping Set Value
A duty role to load interface file for import:
FSCM Load Interface Administration
TAX
COMPOUND TAX ON THE ASSESSABLE VALUE

Use this feature to define the taxable basis for a tax by compounding taxes based on the assessable value.
The feature is applicable to all taxes in the world.
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.
51
TAX REGISTRATION NUMBER VALIDATION FOR 5 NEW COUNTRIES (COLOMBIA, ECUADOR,

MEXICO, PERU, AND TAIWAN)
Oracle Tax provides the infrastructure to capture, maintain, and validate the information for enterprise,
suppliers, customers and other parties in the Manage Legal Reporting Unit Registrations and the Manage Tax
Registrations of Legal Reporting Unit Tax Profile, Third-Party Tax Profiles and Third-Party Site Tax Profiles.
The different types of validations for the tax registrations and taxpayer identifiers issued by the federal revenue
bureau, fiscal authorities and government agencies of the countries Columbia, Ecuador, Mexico, Peru and
Taiwan are as follows:
1. Colombia’s Party Tax Registration Number Validation:
Colombian entities (companies or persons in the public and private sector) have a tax identification
number, known as the Numero de Identificacion Tributaria “NIT”.
For first parties, NIT is defined as Legal Reporting Unit Registrations during Manage Legal Reporting Unit
Registrations task.
For customers, suppliers and other third parties, NIT is defined as Tax Registration Number / Taxpayer
Identifier Number at Manage Tax Registrations of Third-Party Tax Profiles and Third-Party Site Tax
Profiles. This information is validated for uniqueness, format, and check digit requirements.
This validation check does not apply to Foreign Entity third parties. Each foreign entity has its own
country-specific tax registration number standard, which can include alphanumeric characters.
Validation details are as follows:
a. Validation Type - ORA_CO_NIT
Description - Colombia NIT
No of Digits - <=20
Format - Only Numeric Characters are allowed
Check Digit - Yes (Last Digit)
Check Digit Validation - 11- Modulo 11 (Each number of the NIT multiplied starting from right to
left, with a sequence starting from 2, then 3, and so on until 7, if there are additional numbers, then
that start with 2 again). If the result is over 0 and less than 10, that is the verifying number we are
looking for. If the result is 11, then the VD is 0 or if it is 10, the verifying digit is 1
Example TRN No.:
Good: 412615336
Bad: AR1234567 (Invalid Format – Only Numbers allowed)
b. Validation Type - ORA_CO_NIT:FOREIGN
Description - Foreign Business Unit Entity for Colombia with Foreign Origin
No of Digits - <=20
52
Format - No Restriction on the characters
Check Digit - No
Check Digit Validation - No Check Digit Validation
Example TRN No.:
Good: AR1234567
2. Ecuador’s Party Tax Registration Number Validation:
The Registro Unico de Contribuyentes “RUC” is the unique code used to identify an entity for taxation
purposes. Validation of the “RUC” is critical to ensure the third party transaction will be valid when doing
the Transactional Amendment for the Ecuadorian Government (Monthly legal reports). This information is
validated for uniqueness, format, and check digit requirements.
a. Validation Type - ORA_EC_RUC:COMPANY
Description - Ecuador RUC validation for Companies
No of Digits - 13
The 3rd digit from left to right is “6” or “9” depending on the type of entity and the three last
digits on the right are 001, 002, 003 de-pending upon the number of additional
establishments of the same third party.
The two first positions indicate the province where it was expedited, therefore could not be
over 22 or less than 1.
Last three digits could not be 000 private or 0000 for public persons or institutions, as they
should have one establishment at least.
Check Digit -
When the 3rd position is 9, then Check Digit is 10th Digit;

When the 3rd position is 6, then Check Digit is 9th Digit
Check Digit Validation -
When the 3rd position is 9 (the verifying digit is in position 10 in this case)
Existing coefficients: 4.3.2.7.6.5.4.3.2
When the 3rd position is 6 (the verifying digit is in position 9 in this case)
Existing coefficients: 3.2.7.6.5.4.3.2
NOTE: when the reminder is 0, then the verifying digit is 0 (zero)
Example TRN No.:
Good: 1790085783001
1760001040001
53
5790185783001 (Invalid Check Digit)
4750185783001 (3rd digit from left has to be 6 or 9)
b. Validation Type - ORA_EC_RUC:INDIVIDUAL
Description - Ecuador RUC validation for Individual Persons
No of Digits - 13
The last 3 digits of the RUC represents the number of locations: 001, 002, 003, etc. for this
person where the two first digits are the province where it was expedited: will be numbers
between 1 and 22 only. Therefore, the last 3 digits will never be 000 as there is at least one
existing location.
Check Digit - 10th Digit
The DNI is validated as per the “Module 10”, where the first 9 digits are the DNI itself while
the 10th digit is the verifying number.
The used coefficients for the validation are: 2,1,2,1,2,1,2,1,2 (if the remainder is 0, then the
verifier digit is 0)
Example TRN No.:
Good: 1790085783001
1760001040001
1710034062 ((Invalid Format – to short)
c. Validation Type - ORA_EC_RUC:FOREIGN
Description - Foreign Business Unit Entity for Ecuador with Foreign Origin
No of Digits - <=20
Format - No Restriction on the characteres
Check Digit - No
Example TRN No.:
Good: RT1234567#4
3. Mexico’s Party Tax Registration Number Validation:
Registration Number with Mexico’s State Administration of Tax (SAT) has to be validated for
accuracy. This Tax Registration Number in Mexico is known as “RFC” - “Registration of Federal
Contributors” (registered at federal level), and attached to the legal entity, used by Companies and
individuals acting as a business.
54
Validation is for the format structure of the Tax Registration Number (not the data within the structure).
For persons who provide services other than those of official professional activity (not Doctors,
Consultants, Lawyers etc.), the identifying number for tax purposes at federal level would be “CURP”.
CURP is the National identifier for all Mexican citizens - “Key Unique to Register Population”. This
information is validated for uniqueness, format, and check digit requirements.
a. Validation Type - ORA_MX_RFC:COMPANY
Description - Mexico RFC Validation for Companies
No of Digits - 12
Format - Only letters and numbers are allowed. No special characters.
Segment 1: Three letters for a short company name. These letters are assigned by SAT at
company creation time.
Segment 2: Six numbers for company creation date; yymmdd
Segment 3: Last three digits called “Homoclave”; it could contain letters and numbers. This
segment provides uniqueness to Tax Registration Number.
Check Digit - No
Example TRN No.:
Good: OME910101TA3
Bad: AR12%$34567 (Invalid Format – Only letters and Numbers allowed)
OME910231TA3 ((Invalid Format – date yymmdd format is invalid)
b. Validation Type - ORA_MX_RFC:INDIVIDUAL
Description - Mexico RFC Validation for Professional Individuals
No of Digits - 13
Segment 1: Four letters for Name and last names: First two letters of last name, first letter
of second last name and first letter of name
Segment 2: Six numbers for date of birth, yymmdd
Segment 3: Last three digits called “Homoclave”; it could contain letters and numbers. Like
in the case of companies, this segment provides uniqueness to Tax Registration Number.
Check Digit - No
Example TRN No.:
55
Good: BOSF740624T74
Bad: AR45%$34567 (Invalid Format – Only letters and Numbers allowed)
BOSF740631T74 ((Invalid Format – date yymmdd format is invalid)
c. Validation Type - ORA_MX_RFC:SAT
Description - Mexico RFC Validation for SAT
No of Digits - <=20
Check Digit - No
Example TRN No.:
Good: 34DF1234567#4
d. Validation Type - ORA_MX_RFC:CURP
Description - Mexico RFC Validation for CURP
No of Digits - 18
Segment 1: Four letters for Name and last names: First two letters of last name, first letter
of second last name and first letter of name
Segment 2: Six numbers for date of birth, yymmdd
Segment 3: One letter to specify gender; H = Male, M = Female
Segment 4: Two letters for the Geographical State of birth inside Mexico
Segment 5: One letter, first internal consonant from the first of the two last names
Segment 6: One letter, first internal consonant from the second of the two last names
Segment 7: One letter, first internal consonant from the first name
Segment 8: One digit, 0-9 for dates of birth up to the year 1999, and A-Z for dates of birth
from the year 2000 forward
Segment 9: One digit to avoid duplications
Check Digit - No
Example TRN No.:
Good: BOSF740824HJCNVB09
Bad: A#$5df%$34567 (Invalid Format – Only letters and Numbers allowed)
BOSF740630AJCNVB09 ((Invalid Format – 11th digit has to be H or M)
e. Validation Type - ORA_MX_RFC:FOREIGN
Description - Foreign Business Unit Entity for Mexico with Foreign Origin
56
No of Digits - <=20
Check Digit - No
Example TRN No.:
Good: 3GRDF1234567#4
4. Peru’s Party Tax Registration Number Validation:
The Registro Unico de Contribuyentes “RUC” is the 11-digit unique code used to identify a legal entity for
VAT taxation purposes (federal level): • Companies (public or private) • Individuals (regular person)
Peru's Tax Registration Number and the Taxpayer Identification Number are validated for uniqueness,
format, and check digit requirements.
a. Validation Type - ORA_PE_RUC
Description - Peru RUC Validation for Company, Regular Person, and Foreigner
No of Digits - 11
The first 2 digits of the 11-digit RUC determines the type of entity
First 2 digits is “10”, the entity is a regular person
First 2 digits is “20”, it entity is a company
First 2 digit is “16”, it used to be a valid number, but no longer used
First 2 digit is “17”, it is either an old RUC from 1993-2000 OR the entity is a foreigner/others
The next 8 are considered the Documento Nacional de Identidad “DNI” (identity number)
Check Digit - 11th digit (Last digit)
The RUC is validated using the “Module 11” rule.

Each number of the RUC is multiplied starting from left to right with 5, 4, 3, 2, 7, 6, 5, 4, 3, 2.
Then sum all the results
The result has to be divided by 11 (the name of the Module)
After the division is made, the remaining is subtracted by 11 (11-remaining of the division)
If the result is over 0 and less than 10, that is the verifying number we are looking for
If the result is 0 or 10, the verifying digit is 1
Example TRN No.:
Good: 20503644968
Bad: ARF%34567 (Invalid Format – Only Numbers allowed)
57
20503644961 ((Invalid Format – Check Digit)
5. Taiwan's Party Tax Registration Number Validation:
There is an algorithm from the Ministry of Economic Affairs to verify that the corporate Business
Administration Number “BAN” is a valid number. Legal Entity, company sites and individuals have a
“BAN” number: Corporate entity “BAN” is validated by ERP system for uniqueness, format, and check
digit requirements.
a. Validation Type - ORA_TW_BAN:COMPANY
Description - Taiwan Business Administration Number Structure Validation for Company
No of Digits -8
The whole number is validated in 2 steps.

Step1: Each digit number multiple by a constant {1,2,1,2,1,2,4,1}
Step2: Result should be true where if Sum( a1 ~ a8) divide by 10 and remainder is 0.
Check Digit - No
Example TRN No.:
Good: 35701598
Bad: ARF$34567 (Invalid Format – Only Numbers allowed)
39292217 ((Invalid Format – remainder is non 0)
b. Validation Type - ORA_TW_BAN:INDIVIDUAL
Description - Taiwan Business Administration Number Structure Validation for Individual
No of Digits -9
Format - First letter is always an alphabet. Others are all numeric Characters.
The whole number is validated in 2 steps.

Step1: Each digit number multiple by a constant {1,2,1,2,1,2,4,1}
Step2: Result should be true where if Sum( a1 ~ a8) divide by 10 and remainder is 0.
Check Digit - No
Example TRN No.:
Good: A35701598
Bad: AR945$34567 (Invalid Format – Only Numbers allowed)
A39292217 ((Invalid Format – remainder is non 0)
58
STEPS TO ENABLE
TRANSACTIONAL BUSINESS INTELLIGENCE FOR FINANCIALS
ADD NON-QUALIFIED SEGMENTS TO ORACLE TRANSACTIONAL BUSINESS INTELLIGENCE

FIXED ASSETS SUBJECT AREAS
Oracle Transactional Business Intelligence Fixed Assets - Asset Depreciation Real Time and Fixed Assets -
Asset Transactions Real Time subject areas now support non-qualified segments, in addition to the qualified
General Ledger segments Balancing Segment, Natural Account and Cost Center.
The non-qualified segments have been made available under the 'Depreciation Accounting Details' folder, in
both subject areas Fixed Assets - Asset Depreciation Real Time and Fixed Assets - Asset Transactions Real
Time. You need to run BI Extender in order to see these fields in the folder.
Non-Qualified Segments
STEPS TO ENABLE
For details about administering, creating and editing reports, see the books available from the Oracle Help
Center > your apps service area of interest > Books > Administration or User sections.
CROSS-PILLAR REPORTING BETWEEN RECEIVABLES AND PROJECTS

The Oracle Transactional Business Intelligence Receivables - Transactions Real Time subject area has been
enhanced to include additional subfolder named Project, under the Transaction Line Details folder. Subfolders
and columns have been added to enable cross-pillar reporting between AR and Projects.
Project classification
Project codes
Project date attributes
59
Project indicator attributes
Project record information
Project type attributes.
STEPS TO ENABLE
ENHANCEMENTS TO CASH MANAGEMENT SUBJECT AREAS

The accounting information for external cash transactions is now available for reporting. Oracle Transactional
Business Intelligence Cash Management - External Cash Transactions Real Time subject area has a folder
addition:
External Transaction Accounting, with its subfolders:

GL accounting date
GL accounting date fiscal calendar
GL account
Balancing segment
Natural account
Cost center
GL overridden account
Overridden balancing segment
Overridden natural account
Overridden cost center
Subledger accounting journal details
External transaction accounting
STEPS TO ENABLE
ENHANCEMENTS TO REVENUE MANAGEMENT SUBJECT AREAS

OTBI Revenue Management - Customer Contracts Real Time subject area has been enhanced to include
attributes in support of reporting activity for automatic renewal of revenue contracts and suspension and re-
instatement of satisfaction events for period-based revenue contracts. New attributes were made to the
following folders and subfolders:
Promised Details
Promised Detail Line Amounts new column addition to source Recurring amount;
Promise Detail Lines new columns additions: recurring indicator, recurring frequency, recurring
pattern code, termination date;
Promised Detail Source Document new subfolder Source document subline and attributes:
document subline type, data transformation status, satisfaction measurement date, satisfaction
event quantity, satisfaction event percent, period action code, period action event date, previous
document sub line id;
new column additions were made to Source Document Line and Source Document Reference:
recurring indicator, recurring frequency, recurring pattern code, termination date, recurring line
60
copy number, recurring amount, revised recurring indicator, revised recurring frequency, revised
recurring pattern code, revised termination date, revised rule end date, revised rule start date,
revised accounting rule identifier, revised recurring amount
Satisfaction column additions to Satisfaction Event Details subfolder: period action code, period
action event date, previous document subline id, latest period action code, total reversal days,
latest reversal days;
STEPS TO ENABLE
ROLE INFORMATION
EXPOSE DESCRIPTIVE FLEXFIELDS ON KEY FLEXFIELDS FOR OTBI FINANCIALS NON-

ESSBASE SUBJECT AREAS
The Oracle Transactional Business Intelligence Financials non-Essbase subject areas have been enhanced to
include descriptive flexfields information for key flexfields. Exposure in the Essbase subject area General
Ledger - Balances Real Time will come in a future release.
To expose the descriptive flexfields information in Oracle Transactional Business Intelligence Financials non-
Essbase subject areas, you need to run BI Extender.
STEPS TO ENABLE
PAYABLES INVOICES HOLDS INFORMATION REORGANIZED IN THE ORACLE

TRANSACTIONAL BUSINESS INTELLIGENCE SUBJECT AREAS
Oracle Transactional Business Intelligence Payables Invoices - Transactions Real Time subject area has been
enhanced to include attributes that help you report on invoice holds. Prior to this enhancement, invoice hold
attributes were available in Payables Invoices - Holds Real Time subject area. You can now report invoice
amounts on hold without having to create a cross-subject area report.
Hold information is now available at both invoice header and invoice line level in the Payables Invoices -
Transactions Real Time subject area. Hold related attributes were added to two new subfolders in this subject
area as follows:
The Invoice Details folder has a new subfolder named 'Invoice Hold Information'. This sub-folder contains
the following attributes for invoice header holds: hold identifier, hold date, hold release date, hold name,
hold description, hold reason, held by, released by, hold details, hold release name, hold release
description, release reason, invoice hold workflow status, invoice hold receipt number, hold creation date,
hold created by, hold last updated date, hold last updated by;
The Invoice Lines folder has a new sub-folder named 'Invoice Line Details - Hold Information'. This sub-
folder contains the following attributes for invoice line level holds: line hold identifier, line hold date, line
hold release date, line hold name, line hold description, line hold reason, line held by, line released by,
line hold details, line hold release name, line hold release description, line release reason, line invoice
hold workflow status, line invoice hold receipt number, line hold creation date, line hold created by, line
hold last updated date, line hold last updated by;
61
Additional measures are added to the Invoice Amounts and Invoice Line Amounts folders, for hold
counts: line hold count, released line hold count, total number of holds, total number of active holds.
As part of this change, the Payables Invoices – Holds Real time subject area is no longer available to create
any new ad hoc reports. Any existing reports that use the Payables Invoices – Holds Real time subject area will
continue to work as is. However, if you want to make any changes to an existing report that uses the Payables
Invoices - Holds Real time subject area, then you must recreate the report afresh and use the newly added
attributes from the Payables Invoices – Transactions Real Time subject area.
STEPS TO ENABLE

The hold attributes that were available in the Invoice Hold Details folder of the Payables Invoices –
Holds Real time subject area are now available in the Invoice Hold Information and Invoice Lines – Hold
Information folders.
To identify the line number of the line on hold, use the ‘Line Number’ attribute from the Invoice Lines –
General Information. This attribute should be used in replacement of the ‘Line Held’ attribute that was
available in the ‘Invoice Hold Details folder in the Payables Invoices – Holds Real time subject area.
To identify only those invoice transaction headers or lines on hold, you need to add a filter to the report
on one of the hold attributes, for example: Hold Identifier is not null or Line Hold Identifier is not null.
To identify those invoices for which header holds are released, add a filter like Hold Release Date is not
null or Released Header Hold Count > 0. Similarly, to identify those invoice lines for which holds have
been released, add a filter like Line Hold Release Date is not null or Released Line Hold Count > 0.
ROLE INFORMATION
---
62
Copyright © 2019, 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.
63

19B Financials WN

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

19B Financials WN

Hochgeladen von

Copyright:

Verfügbare Formate

TABLE OF CONTENTS

Date Feature Notes

Payables Invoices Holds Information

22 MAR 2019 Created initial document.

JOIN ORACLE CLOUD CUSTOMER CONNECT

OPTIONAL UPTAKE OF NEW FEATURES (OPT-IN)

To opt-in using the Setup and Maintenance work area:

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

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

COMMON FINANCIALS FEATURES

AUTO DISMISS POPUP

Auto Dismiss Popup Example for Expense Reports

No steps are required to enable this feature.

PERFORMANCE ENHANCEMENT IN GENERAL ACCOUNTING DASHBOARD AND

No steps are required to enable this feature.

SIMPLIFIED WORKFLOW RULES CONFIGURATION

No steps are required to enable this feature.

TIPS AND CONSIDERATIONS

No new role access is needed to use this feature.

REST APIS FOR FINANCIALS

REST APIS FOR CURRENCY RATES

REST APIS FOR EXTERNAL BANK ACCOUNTS

Create and manage external payees for suppliers.

REST APIS FOR JOURNALS

REST APIS FOR LEDGER BALANCES

Retrieve, create, and modify UI rules.

REST APIS FOR PAYMENTS

TIPS AND CONSIDERATIONS

You can also build integrations to:

Retrieve payment and paid invoice information.

REST APIS FOR SALESPERSON REFERENCE ACCOUNT

Create a reference account for a salesperson.

REST APIS FOR SUPPLIER INVOICES

Create and manage cross-currency, multi-period accounting related supplier invoices.

TIPS AND CONSIDERATIONS

INVESTMENT ALLOWANCE DEDUCTIONS AS BONUS DEPRECIATION

The following screenshots illustrates the feature and its benefits:

TIPS AND CONSIDERATIONS

BUDGETARY CONTROL SPEND AUTHORIZATIONS

CHECK AND VIEW FUNDS

REJECT INSUFFICIENT FUNDS

Reject Authorization When Budgetary Control Failure

Reserved Spend Authorization

REIMBURSEMENT OF EMPLOYEE EXPENSES

INQUIRY AND REPORTING OF BUDGET IMPACT FOR EMPLOYEE EXPENSES

Budgetary Control Results by Transaction Report

MANAGE BUDGETARY CONTROL

TIPS AND CONSIDERATIONS

Spend Authorizations: Explained

Roles needed for approving spend authorization in Expense Management

CARRY FORWARD PURCHASE ORDER BUDGETARY CONTROL BALANCES ENHANCEMENT

Carry Forward Purchase Order Budgetary Control Balances Process

1. PO Charge Account Filter

2. Keep funds available unchanged in the carry forward from year

3. Include budget for purchase orders in the carry forward to year

There is no setup required for these new parameters.

TIPS AND CONSIDERATIONS

Keep funds available Include budget for purchase

BANK STATEMENT RECONCILIATION OF REJECTED LINES

TIPS AND CONSIDERATIONS

MANUAL RECONCILIATION ENHANCEMENTS

No steps are required to enable this feature.

SPEND AUTHORIZATION WITH BUDGETARY CONTROL