r13 2018 Financials WN

TABLE OF CONTENTS
DOCUMENT HISTORY ······························································································································································································· 4
UPDATE 18B ······························································································································································································· 4

Revision History ························································································································································································ 4
Overview ······································································································································································································· 4
Feature Summary ····················································································································································································· 6
Common Technology and User Experience ······························································································································· 8
Common Financials Features ······················································································································································· 8
Enhanced Data Segregation for Third-Party Service Providers ················································································· 8
Configurable Workflow Notifications ··································································································································· 10
Financials ··································································································································································································· 11
Budgetary Control ············································································································································································ 11
Budget Transfer ·········································································································································································· 11
Expenses ······························································································································································································· 13
Disable Scan Option on Mobile Expenses ······················································································································· 13
Itemization of Meals Expense Categories ························································································································ 14
General Ledger ··················································································································································································· 15
Configure Auditable Setup Attributes and View Audit Report ··················································································· 15
Payables ································································································································································································· 16
Streamlined Payment Processing ········································································································································ 16
Receivables ·························································································································································································· 16
Flexible Routing and Approval of Receivables Credit Request ················································································ 16
Transactional Business Intelligence for Financials ········································································································· 20
Drill Down From OTBI Payables Reports to AP Transaction Details ····································································· 20
Expose Description Columns in Essbase for Non-Qualified Segments ································································ 20
Improved Cross-Pillar Reporting Between Projects and Receivables ··································································· 20
New OTBI Subject Area for Asset Balances Reporting ······························································································· 21
Regional and Country-Specific Features ··································································································································· 21
Financials for the Americas ························································································································································· 21
Mexican Electronic Accounting Version 1.3 ····················································································································· 21
Financials for EMEA ········································································································································································ 22
Tax Point Date Adjustment Using Spreadsheet ············································································································· 22
UPDATE 18A ····························································································································································································· 25

Revision History ······················································································································································································ 26
Overview ····································································································································································································· 26
Feature Summary ··················································································································································································· 27
Common Financials Features ·························································································································································· 29
Configurable Email Notifications ·········································································································································· 29
Financials ··································································································································································································· 30
Assets ····································································································································································································· 30
Fixed Assets Capitalization Thresholds ····························································································································· 30
Lease Liability Reporting ························································································································································· 32
Reporting Currency Conversion for Asset Leases ········································································································ 33
Expenses ······························································································································································································· 33
Control Display of Fields by Expense Type ····················································································································· 33
Shortcuts for Attendee Selection ·········································································································································· 35
General Ledger ··················································································································································································· 35
2
Accounting Automation ···························································································································································· 35
Payables ································································································································································································· 37
Invoice Routing for Account Coding ···································································································································· 37
Receivables ·························································································································································································· 38
Additional Attributes for Credit Checking Service ·········································································································· 38
Order Level Credit Recommendation ································································································································· 39
Receivables Invoice Delivery in Open Applications Group Integration Specification 10.1 XML Format ··· 41
Store Printed Receivables Transactions as Attachments ··························································································· 48
Web Service to Create Reference Accounts for Customers ······················································································ 49
Transactional Business Intelligence for Financials ········································································································· 50
Replace Business Unit Views for Improved Performance ·························································································· 50
Subledger Accounting - Journals Real Time Subject Area Enhancements ························································· 50
Regional and Country-Specific Features ··································································································································· 50
Financials for EMEA ········································································································································································ 50
Spain ··································································································································································································· 50
Online VAT Reporting for Spain ··········································································································································· 50
3
DOCUMENT HISTORY
This document will continue to evolve as existing sections change and new information is added. All updates
appear in the following table:
Date Update Version Notes
20 APR 2018 Update 18B Delivered new features in update 18B.
19 JAN 2018 Update 18A Delivered new features in update 18A.
UPDATE 18B
REVISION HISTORY
Date Feature Notes
20 APR 2018 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.
CUSTOMERS UPGRADING FROM RELEASE 12
If you're upgrading from Release 12 to Release 13, then you should review all of the release readiness content
for Release 13 (updates 17B - 17D, as well as, updates 18A - 18B) to learn about all of the features available
in release 13.
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
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
4
Take a look at the Customer Connect Events to help you learn more about your upgrade, and some of the new
features in R13. You can sign up to attend Upcoming Events or watch replays of existing events.
5
FEATURE SUMMARY
Action Required to Enable Feature
None
Enable via Opt Enable via Opt In UI Plus Not Enabled via Opt In UI but Issue Service
Feature (Automatically
In UI Only Additional Steps Setup Required Request
Available)
Common Technology and User Experience

Common Financials Features
Enhanced Data Segregation for Third-Party
Service Providers
Configurable Workflow Notifications
Financials
Budgetary Control
Budget Transfer
Expenses
Disable Scan Option on Mobile Expenses
Itemization of Meals Expense Categories
General Ledger
Configure Auditable Setup Attributes and View
Audit Report
Payables
Streamlined Payment Processing
Receivables
Flexible Routing and Approval of Receivables
Credit Request
Transactional Business Intelligence for
Financials
Drill Down From OTBI Payables Reports to AP
Transaction Details
Expose Description Columns in Essbase for
Non-Qualified Segments
6
None
Enable via Opt Enable via Opt In UI Plus Not Enabled via Opt In UI but Issue Service
Feature (Automatically
In UI Only Additional Steps Setup Required Request
Available)
Improved Cross-Pillar Reporting Between

Projects and Receivables
New OTBI Subject Area for Asset Balances
Reporting
Regional and Country-Specific Features
Financials for the Americas
Mexican Electronic Accounting Version 1.3
Financials for EMEA
Tax Point Date Adjustment Using Spreadsheet
7
COMMON TECHNOLOGY AND USER EXPERIENCE
COMMON FINANCIALS FEATURES
ENHANCED DATA SEGREGATION FOR THIRD-PARTY SERVICE PROVIDERS
In Oracle Financials Cloud many transactions, such as payables invoices, payment requests, assets, and
expense reports, include references to employees or persons. We allow any employees or persons defined in
Oracle Financials Cloud to be referenced in these transactions. For third-party service providers who may be
managing business processes from multiple entities, additional restrictions on employees may be required. With
this enhancement, we have enabled data security to these references.
The following table lists the places where data security for references on employees, workers, and users is
enabled.
8
Product Task Field
Assets Asset Inquiry Employee
Add Asset Employee
Prepare Source Lines Preparer
Manage All Books Preparer
Add Asset in Spreadsheet Preparer Employee
Employee (Asset Selection Criteria) Employee (Transfer

Transfer Assets
Details)
Perform What-If Analysis Employee
Manage Asset Distribution Sets Employee
Receivables Manage Customer -> Edit Customer Credit Analyst (Profile History)
Manage Customer -> Edit Account Credit Analyst (Profile History)
Manage Customer -> Edit Site Credit Analyst (Profile History)
Credit Reviews Credit Analyst
Manage Receivables Customer Profile

Credit Analyst
Class
Manage Approval Limits User
Collections Manage Collectors Employee
Payables Create Payables Invoice Preparer
Import Payables Invoice Preparer
Submit Payment Process Request First Approver
Manage Payment Process Request

First Approver
Template
Expense Manage Corporate Cards Employee
Manage Historical Credit Card

Employee
Transactions
Review Corporate Card Transactions Employee
Manage Expense Reports Employee
Manage Expense Audit List Membership Employee
Manage Cash Advances Employee
Manage Expenses Contingent Worker Employee
Review Payment Requests Employee
Review Invoices Contingent Worker
Manage Expense Reports Employee
About Me -> Manage Delegates Person
9
STEPS TO ENABLE
To minimize upgrade impact, data security policies are shipped against predefined roles that need to access
employees, workers, and users to provide access to all employees by default.
To implement enhanced data segregation, these predefined data security policies need to be replaced with data
security policies that are more restrictive. Since predefined roles cannot be modified, such changes need to be
made against copies of the predefined roles.
Steps to enable this feature are documented in the whitepaper Implementing Enhanced Data Segregation (Doc
ID 2324377.1) available on My Oracle Support.
ROLE INFORMATION
The following predefined roles now include a new data security policy:
Accounts Payable Manager

Accounts Payable Specialist
Accounts Payable Supervisor
Accounts Receivable Manager
Accounts Receivable Specialist
Asset Accountant
Asset Accounting Manager
Collections Manager
Financial Application Administrator
NOTE: Predefined roles in Expenses, including Corporate Card Administrator, Expense Auditor, Expense
Audit Manager, and Expense Manager, do not include predefined data security policies that provide access to
all employees by default.
CONFIGURABLE WORKFLOW NOTIFICATIONS

Oracle Financials Cloud lets you use Business Intelligence Publisher for workflow notifications. The templates
are optimized for mobile devices and are easily configurable. Choose from a comprehensive list of attributes to
modify the workflow notifications according to your requirements. You can change both layout and content –
add images, change colors and styling, add or remove attributes or modify text.
Support for additional Expenses notifications and for Budgetary Control override requests is added in this
release.
STEPS TO ENABLE
The feature needs to be enabled using the Feature Opt In page in Functional Setup Manager. It is not enabled
by default.
To enable the feature, complete these steps:
1. Go to the Setup and Maintenance work area.

2. Select Financials from the Setup drop down.
3. Click on the Change Feature Opt In.
4. On the Opt In: Financials page, click the Features icon for the product for which you wish to enable the
feature (Expenses or Budgetary Control and Encumbrance Accounting).
10
5. On the Edit Features page, select the Enable option for each type of notification that you want to enable
the feature for.
6. Click on Done to go back to the Setup: Financials page.
TIPS AND CONSIDERATIONS

1. Use the predefined email templates with no additional changes or modify them according to your
business requirements.
2. Preview your changed email templates before publishing.
3. Revert to the classic approval notifications at any time by disabling the feature using the Feature Opt In
page in Functional Setup Manager.
KEY RESOURCES
Financials Configurable Workflow Notifications: Overview
Configurable Workflow Notifications: Implementation Considerations (Doc ID 2215570.1) on My Oracle
Support
FINANCIALS
BUDGETARY CONTROL
BUDGET TRANSFER
As you review your budget on the Review Budgetary Control Balances page, you can select budget accounts
that require budgetary transfers and add them to a Budget Transfer Request.You can transfer between any
combination of budget accounts within the same budget period or budget year.
To transfer budget within a budget period, enter a search criteria with the Amount Type set to Period to date.
The budget period of the transfer is based on the budget period of the selected accounts.
To transfer budget on an annual basis when the underlying control budget is on a monthly basis, enter a search
criteria with the Amount Type set to Year to date and the Budget Period set to the last month of the year. The
budget year of the transfer is derived from the budget period of the selected accounts.
After selecting the accounts to be transferred, click the Budget Transfer Request icon to open the request.
11
Building a Budget Transfer in Review Budgetary Control Balances
The budget accounts and period context for your Budget Transfer Request are predefined for you. Specify the
budget amounts to transfer, and a Justification.
When transferring budget amounts on an annual basis, the Budget Transfer Request expects that the budget
amounts you enter are annual amounts. Specify the Allocation Method for “All budget periods equally” to
allocate the annual budget transfer amount evenly to all periods, or “First budget period” to allocate the amount
to the first month of the year.
Submit the request to execute the Import Budget Amounts process to update the budget amounts.
Budget Transfer Request
12
When the budget transfer request is successful, you will receive a notification.
Budget Transfer Request Notification
STEPS TO ENABLE
No steps are required to enable this feature.
The new budget transfer action is available on the Review Budgetary Control Balances page for control
budgets defined with a Source Budget Type of ‘Hyperion Planning’ and ‘Other’.
ROLE INFORMATION
The Import Budget Amounts (XCC_IMPORT_BUDGET_AMOUNTS) privilege is required to gain access to the
Transfer Budget action on Review Budgetary Control Balances. This privilege is a member of the Budgetary
Control Management Duty Role. Therefore any roles, such as budget manager, that inherit the Budgetary
Control Management Duty Role will have access to the Transfer Budget action.
EXPENSES
DISABLE SCAN OPTION ON MOBILE EXPENSES

You can disable the Scan option on the Expenses mobile application by configuring a profile option.
STEPS TO ENABLE
To disable the Scan option, define the profile option EXM_MOBILE_DISABLE_SCAN and set the profile
option value to Y
To define the profile option, follow these steps:
1. In the Setup and Maintenance work area, navigate to the Manage Profile Options page.
2. On the Manage Profile Options page, click the Create (+) icon.
3. On the Create Profile Option page in the Profile Option Code field, enter
EXM_MOBILE_DISABLE_SCAN.
4. In the Profile Display Name field, enter a profile display name.
5. From the Application choice list, select Expenses.
6. From the Start Date field, enter a start date.
7. Click Save and Close.
8.
13
8. On the Manage Profile Options page in the Profile Options Levels section, select Site as the Level value.
9. Select both the Enabled and the Updateable check boxes.
To define the profile option value, follow these steps:
1. In the Setup and Maintenance work area, navigate to the Manage Administrator Profile Values page.
2. Search for profile option code EXM_MOBILE_DISABLE_SCAN.
3. In the Search Results: Profile Options section, select the EXM_MOBILE_DISABLE_SCAN profile option.
4. In the Profile Values section, click the Create (+) icon.
5. From the Profile Level choice list, select Site.
6. From the Profile Value choice list, select Yes.
ROLE INFORMATION
You must have one of the following roles to disable the Scan option:
Application Implementation Consultant

Financial Administrator
Expense Manager
ITEMIZATION OF MEALS EXPENSE CATEGORIES

You can now itemize meals expense categories. Itemizing meals helps you capture the breakdown of meal
expenses, such as tips and taxes.
STEPS TO ENABLE
To itemize a meal expense type, follow these steps:
1. In the Setup and Maintenance work area, navigate to the Manage Expense Report Templates task.
2. On the Manage Expense Report Templates page, select the applicable template and click the Edit icon.
3. On the Expense Types tab, select the meal expense type that you want to itemize and click the Edit icon.
4. On the itemization tab, select one of the following values from the Itemization choice list:
Enabled to optionally enable itemization.
Required to make itemization mandatory.
5. Click the Include check box for the expense types that you want to make available for itemization.
ROLE INFORMATION
You must have one of the following roles to enable meals itemization:

Expense Manager
14
GENERAL LEDGER
CONFIGURE AUDITABLE SETUP ATTRIBUTES AND VIEW AUDIT REPORT

You can now configure setup attributes for audit from the Setup and Maintenance work area to maintain
internal control over the validity of the enterprise transaction system. After configuration, you can track
changes to these attributes using the Audit Report.
The following business setup objects are enabled for audit in General Ledger:
Account Combinations
Accounting Automation
Allocations and Periodic Entries
Accounting and Reporting Sequences
AutoPost Criteria Sets
Chart of Accounts Mapping
Daily Conversion Types
Encumbrance Types
Encumbrance Carry Forward Rules
Intercompany Processing Rules
Journal Categories
Journal Sources
Journal Reconciliation Rules
Journal Reversal Criteria Sets
Ledgers
Revaluations
Suspense Accounts
STEPS TO ENABLE
Navigate to the Setup and Maintenance work area to configure the auditable setup attributes:
1. Select the Manage Audit Policies task.

2. Select the Configure Business Object Attribute.
3. Select the product, business object, and attributes for audit enablement.
4. Save the selection.
To view the audit report:
1. From the Navigator, select Tools to open the Audit Reports.
KEY RESOURCES
Oracle Financials Cloud Implementing Common Features for Financials
15
PAYABLES
STREAMLINED PAYMENT PROCESSING

During the payment process request, the installments selection process confirms that the business unit,
currency, and payment method of the installment matches the usage rules defined on the payment process
profile.
Similar matching occurs between the business unit and currency of the installment and the internal bank
account. An installment is not selected if it is within the selection parameters, but does not match the
configuration of the payment process profile or the internal bank account.
Matching during the installments selection process prevents later installment rejections during the build payment
process due to a mismatch of installment attributes with the payment process profile or the internal bank
account.
STEPS TO ENABLE
Enable the feature from the Functional Setup Manager Feature Opt In page. The steps are:
1. Go to the Setup and Maintenance work area.

2. Select Financials in the drop-down list at the top of the page.
3. Click Change Feature Opt In.
4. On the Opt In: Financials page, click the Features icon for Payables.
5. On the Edit Features: Payables page, select the Enable icon for Streamlined Payment Processing
feature.
6. On the Feature Name: Streamlined Payment Processing pop-up window, select option Restricted
Installments Selection and click Save and Close.
7. Click Done on Edit Features: Payables page to return to the Setup: Financials page.
RECEIVABLES
FLEXIBLE ROUTING AND APPROVAL OF RECEIVABLES CREDIT REQUEST

You can now configure Oracle Business Rules to determine whether a credit request against a Receivables
transaction requires a manual review to create a credit memo. The notification process informs users of any
required actions. Users will also be able to capture additional information on the credit request or on
subsequent workflow notifications.
Two new human tasks are available to manage this process.
a. FinArTrxnsCreditMemosAutomaticManual: To configure the decision for using a manual review to create

a credit memo. This human task does not invoke any workflow notifications.
b. FinArTrxnsCreditMemosCreationPostProcess: To initiate the workflow for manual review to create a
credit memo, based on the decision from the previous human task
FinArTrxnsCreditMemosAutomaticManual. You can configure multiple reviewers for this workflow
through the task configuration assignee rules. Reviewers can review the credit request details and
perform the required actions, including the creation of a credit memo for the requested amount. They can
also capture and/or update additional information on the credit request using the new Review Credit
Memo Request page.
16
You can use additional attributes within the Assignee rule conditions to configure the routing rules for both the
existing and the new human tasks. These attributes include –
Salesperson Name
Salesperson Email ID
Sum of all Adjustments Amounts
Sum of all Receipts Amounts
Credit Memo Reason Code Descriptive Flexfield Attribute 1 – 15
Invoice Line Description
Collector Descriptive Flexfield Attribute 1 – 15
Line Level Credit
Invoice Line Type
Invoice or Line Adjustments
Receipts Applied
Receivables System Options Descriptive Flexfield Attribute 1 – 15
Item Number
Line Amount Requested
Transaction Information Descriptive Flexfield Attribute 1 – 15
Revenue Scheduling Rule Start Date
Revenue Scheduling Rule End Date
Revenue Scheduling Rule Number of Periods
Revenue Scheduling Rule Rule Type
Revenue Scheduling Rule Name
Tax Credit Amount Requested
You can capture an additional attribute Dispute Type on the Manage Disputes page, to classify a transaction
dispute. It can be updated from the Review Credit Memo request page, which can be accessed from
FinArTrxnsCreditMemosApproval workflow notifications.
The Review Credit Memo Request page allows you to review the credit request information and do updates to
the attributes like Dispute Type, Rebill Number, and Rebill Group. This page can be accessed from
FinArTrxnsCreditMemosApproval and FinArTrxnsCreditMemosCreationPostProcess workflow notifications.
17
STEPS TO ENABLE
This feature is automatically opted in through the release update. To configure the feature for manual creation
of a credit memo, you must complete these additional steps:
1. Configure the Assignee Rules for the new SOA human task FinArTrxnsCreditMemosAutomaticManual
with the output value HtOutcmeCreateManualCreditMemo. By default,
FinArTrxnsCreditMemosAutomaticManual is set as 1 is 1 rule for automatic processing.
2. Configure the Assignee Rules for the new human task FinArTrxnsCreditMemosCreationPostProcessing
based on the earlier human task output value. You can configure different workflow approval models
based on whether credit memo creation is manual or automatic. By default, it is set as 1 is 1 rule to
ignore the manual process, that is, if the output of the earlier human task for Task.payload.
CMCreationType is Automatic, then this process is ignored.
18
In addition to it, you can optionally use the lookup type ORA_IEX_DISPUTE_TYPE_CODE to extend the
seeded values provided for the Dispute Type.
A default BIP report is available as part of the human

task 'FinArTrxnsCreditMemosCreationPostProcessing'. This is available in the folder path Shared Folders ->
Financials -> Workflow Notifications -> Receivables -> Billing, with name 'Manual Credit Memo Request
Notification'. You can copy the standard version of this report layout and customize its content using the
existing BIP features.
ROLE INFORMATION
Three new privileges are available in the context of the new Review Credit Memo Request page:
Review Credit Request (to view the Review Credit Request page, View Transaction Activities button, and
Internal Comments attribute)
Update Dispute Type on Credit Request (to allow an update to the Dispute Type attribute)
Update Re-bill Details on Credit Request (to allow an update to the Re-bill Number and Re-bill Group
attributes)
The privilege Review Credit Request is added by default to the Duty Roles Billing Management Duty and
Collections Management Basic. You can add the other two privileges—Update Dispute Type on Credit Request
and Update Re-bill Details on Credit Request—to the required duty roles based on the update authorizations
given to specific users.
19
TRANSACTIONAL BUSINESS INTELLIGENCE FOR FINANCIALS
DRILL DOWN FROM OTBI PAYABLES REPORTS TO AP TRANSACTION DETAILS

The action link framework in Oracle Business Intelligence Enterprise Edition (OBIEE) allows you to click on an
object and navigate directly to the source application. Using this framework, OTBI for Financials provides the
capability to drill from an OTBI ad-hoc report based on a Payables OTBI subject area to the Invoice and
Payment Details in Oracle Payables Cloud.
Hyperlinks can be configured in the ad-hoc Payables OTBI reports to drill down to the following:
View Invoice details

Edit an Invoice
View Payment details
Create a Payment
STEPS TO ENABLE
The high level steps to configure a drill down from OTBI ad-hoc reports to Invoice or Payment transaction
details are:
1. Create an ad-hoc report using the appropriate Payables subject area.

2. Select the column for which you wish to configure the drill down to transaction details.
3. In the ‘Column Properties’, setup an Action link to drill down to the required transaction details.
For details on specific drill downs and examples, search for 'How to drill down from OTBI ad hoc reports to
transaction details in Oracle Fusion Applications' white paper, soon to be available on Customer Connect.
KEY RESOURCES
For details on specific drill downs and examples, search for 'How to drill down from OTBI ad hoc reports to
transaction details in Oracle Fusion Applications' white paper, soon to be available on Customer Connect.
EXPOSE DESCRIPTION COLUMNS IN ESSBASE FOR NON-QUALIFIED SEGMENTS

The General Ledger - Balances Real Time Subject Area has been enhanced to expose the description
columns for non-qualified segments.
STEPS TO ENABLE
IMPROVED CROSS-PILLAR REPORTING BETWEEN PROJECTS AND RECEIVABLES

OTBI for Receivables has been enhanced to support receivables reporting by project contracts.
In the Receivables - Transactions Real Time subject area, 'Transaction Details' > 'Project Contract Header
Details' folder has been expanded to include information on project contracts. Users with the appropriate
Projects subject area access can access Projects information in the Receivables subject area.
STEPS TO ENABLE
20
NEW OTBI SUBJECT AREA FOR ASSET BALANCES REPORTING

Use the Fixed Assets - Asset Balances Real Time subject area to review balances for Cost, CIP Cost,
Depreciation Reserve, Bonus Depreciation Reserve, Impairment Reserve, and Revaluation Reserve balance
sheet accounts.
You can report on additions, adjustments, depreciation, impairments, retirements, revaluations, transfers, and
unplanned depreciation during a period, and analyze summarized information by employee, which includes
beginning and ending balance details.
For each asset, the subject area includes accounting details, asset book information, account balance details,
category details, asset type, asset location, asset cost center, manager, employee, and asset account
information.
STEPS TO ENABLE
REGIONAL AND COUNTRY-SPECIFIC FEATURES
FINANCIALS FOR THE AMERICAS
MEXICAN ELECTRONIC ACCOUNTING VERSION 1.3
The Mexican Electronic Accounting version 1.3 feature includes the following three major enhancements:
1. Compliance with XML reporting version 1.3
Compliance with XML reporting version 1.3 is required by the Mexican Tax Authority (SAT). It includes
minor technical changes to all reports, i.e. Chart of Accounts, Trial Balance, Journal Entries and
Accounts Auxiliary report. It also includes the reporting of proof of payments made and received (known
as ´Comprobante de Pagos´), where key information such as CFDI Fiscal Unique Identifier and Taxpayer
ID can now be captured through corresponding fields in the Additional Information region of the Cash
Receipts and Payments transactions, and XML elements get generated to report such payment proof
transactions.
2. Inclusion of expense report accounting entries as part of the Mexican Electronic Accounting
reporting
This enhancement impacts the Journal Entries (Polizas) report, that now generates XML elements to
represent the expense report invoices, entered in Payables, either manually or imported from
Expenses or legacy systems, where key information such as CFDI Fiscal Unique Identifier and third party
Taxpayer ID are captured through existing merchant related fields such as Merchant Document Number
and Merchant Taxpayer ID at invoice distributions level.
21
3. Ability to identify and report journals entered in GL
This enhancement provides the ability to capture CFDI Fiscal Unique Identifier and Taxpayer ID
information through corresponding fields in the Additional Information region, for manually entered or
imported journals either at journal header or journal line levels, and generate XML elements such as
CompNal for the journals that do have such information associated to them.
STEPS TO ENABLE
The feature is automatically available. Make sure users have access to the LAD Financial Reporting Duty role
to access the reports.

Ensure that CFDI Fiscal Unique Identifier and Taxpayer ID fields are entered as additional information
for any proof of payment transactions that require electronic accounting reporting.
Ensure that CFDI Fiscal Unique Identifier and Taxpayer ID are entered as Merchant related fields in any
Oracle Payables expense invoice that require electronic accounting reporting.
ROLE INFORMATION
LAD Financial Reporting Duty
FINANCIALS FOR EMEA
TAX POINT DATE ADJUSTMENT USING SPREADSHEET

You can now use the Tax Point Date Adjustment feature to change the tax point date of multiple Payables or
Receivables transactions using spreadsheet capabilities.
Select the Payables or Receivables transactions at header and/or line level.

Download the selected transactions to your spreadsheet application.
Use the spreadsheet features to assign new tax point dates as applicable.
Upload the modified spreadsheet to the application.
Process the uploaded data to update the tax point date of the transactions in Payables or Receivables.
Please remember that adjusting the Tax Point Date of already reported transactions may result in a need to
resubmit the Tax reports for the impacted tax periods.
PROCESSING
Submit the Select Transactions for Tax Point Date Adjustment process.When submitting the process, provide
the criteria to identify which transactions should be selected, and the level of detail for the extract – transaction
headers only, or both transaction headers and lines.
22
When the selection process completes successfully, download the comma-separated values (csv) output file to
your spreadsheet application.Use macros, or other spreadsheet functionality to assign new tax point dates
where applicable, and save your changes in csv format.
Upload the modified file to the Cloud applications using the Universal Content Management (UCM)
infrastructure features.
23
Submit the Process Tax Point Date Adjustments process, select Process Type of Import. This process identifies
which tax lines of a transaction require the tax point date to be updated, and processes those changes.
24
STEPS TO ENABLE
If you have previously enabled the Process Tax Point Date Adjustments feature, there are no additional steps
required to use this feature.
Complete all solution related setup for Payables and Receivables before using the Tax Point Date Adjustment
feature.
KEY RESOURCES
Oracle® Fusion Applications Financials Implementation Guide, Release 13
Tax Point Date Adjustment Topical Essay
25
UPDATE 18A
REVISION HISTORY
Date Feature Notes
19 JAN 2018 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.
CUSTOMERS UPGRADING FROM RELEASE 12
If you're upgrading from Release 12 to Release 13, then you should review all of the release readiness content
for Release 13 (updates 17B - 17D, as well as, updates 18A - 18B) to learn about all of the features available
in release 13.
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
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
Take a look at the Customer Connect Events to help you learn more about your upgrade, and some of the new
features in R13. You can sign up to attend Upcoming Events or watch replays of existing events.
26
FEATURE SUMMARY
None Issue
Enable via Enable via Opt In UI Not Enabled via Opt In UI
Feature (Automatically Service
Opt In UI Only Plus Additional Steps but Setup Required
Available) Request
Common Financials Features

Configurable Email Notifications
Financials
Assets
Fixed Assets Capitalization Thresholds
Lease Liability Reporting
Reporting Currency Conversion for Asset Leases
Expenses
Control Display of Fields by Expense Type
Shortcuts for Attendee Selection
General Ledger
Accounting Automation
Payables
Invoice Routing for Account Coding
Receivables
Additional Attributes for Credit Checking Service
Order Level Credit Recommendation
Receivables Invoice Delivery in Open Applications Group
Integration Specification 10.1 XML Format
Store Printed Receivables Transactions as Attachments
Web Service to Create Reference Accounts for Customers
Transactional Business Intelligence for Financials
Replace Business Unit Views for Improved Performance
27
None Issue
Enable via Enable via Opt In UI Not Enabled via Opt In UI
Feature (Automatically Service
Opt In UI Only Plus Additional Steps but Setup Required
Available) Request
Subledger Accounting - Journals Real Time Subject Area

Enhancements
Regional and Country-Specific Features
Financials for EMEA
Spain
Online VAT Reporting for Spain
28
COMMON FINANCIALS FEATURES
CONFIGURABLE EMAIL NOTIFICATIONS

Oracle Financials Cloud now uses Oracle Business Intelligence Publisher for configurable email notifications.
The email templates are optimized for mobile devices and are easily configurable. Choose from a
comprehensive list of attributes to modify the email notifications according to your requirements. You can
change both layout and content. This includes adding images, changing colors and styling, adding or
removing attributes, or modifying text.
Support for the following notifications has been added in the current update:
Product Feature Notification

Intercompany Transaction Approval Notification
Configurable Intercompany Email
Intercompany Intercompany Enter Receiver Distribution
Notifications
Notification
Configurable Payables Email

Payables Invoice Account Coding Notification
Notifications
Expense Audit and Receipt Management

Notifications
Expense Audit Information Request
Notification
Receipt Received Notification
Receipt is Overdue Notification
Expenses Configurable Expenses Notifications Cash Advance Notifications
Cash Advance Rejected by Auditor
Notification
Cash Advance Paid by Check
Notification
Cash Advance Paid by Direct Deposit
Notification
STEPS TO ENABLE
You must enable the feature using the Opt In page in Functional Setup Manager. This feature is not enabled
by default.
To enable the feature, complete these steps:
1. Navigate to the Setup and Maintenance work area.

2. Select Financials from the Setup choice list. .
3. Click the Change Feature Opt I n link.
4. On the Opt In: Financials page, click the Features icon for the product that you want to enable for the
Configurable Email Notifications feature (Expenses, Payables or Intercompany).
5.
29
5. On the Edit Features page, select the Enable option for the notification that you want to enable.
6. Click Done.
The feature is now enabled.

1. Use the predefined email templates with no additional changes or modify them according to
your business requirements.
2. Preview your changed email templates before publishing.
3. Revert to the standard approval notifications at any time by disabling the feature using the Opt In page
in Functional Setup Manager.
KEY RESOURCES
Financials Configurable Email Notifications: Overview
Configurable Email Notifications: Implementation Considerations (Doc ID 2215570.1) on My Oracle
Support at https://support.oracle.com
FINANCIALS
ASSETS
FIXED ASSETS CAPITALIZATION THRESHOLDS
You can enforce the capitalization threshold limit automatically for all of your asset additions. Optionally specify
the low value threshold limit for each asset category so that these low value assets are fully reserved using the
specified method and life.
30
The following screenshot illustrates the feature and its benefits.
Confirm the Results of Your Capital Threshold Settings
STEPS TO ENABLE
Complete the basic setup of your asset book from the Manage Asset Books task and complete your basic
category setup for this book from the Manage Asset Categories task. Then, add your book name to the
ORA_FA_ALLOW_CAP_THRESHOLD lookup values in the Manage Fixed Asset Lookups task.
Activate the Advanced Rules for Your Book
Set the Capitalization and Low Value Threshold Amounts for the Book
31
Specify the Low Value Asset Depreciation Rules for the Category Book
After you load your assets from the Mass Additions File-Based Data Import template to the corporate book, the
Prepare Asset Transaction data process determines whether the assets should be expensed or capitalized
based upon the specified threshold values. For a tax book, the Mass Copy process evaluates the capitalization
and low value thresholds. You can view the capitalization threshold evaluation results from the Edit Source
Lines, Prepare Source Lines, or Add Asset pages.
LEASE LIABILITY REPORTING

Streamline the reconciliation and reporting of your lease liability balances using the Asset Lease Liability
Report.
Identify Out-of-Balance Lease Liability Transactions at a Glance
STEPS TO ENABLE
From the Manage Asset Books page, open your book. Ensure that the Asset Leases check box is enabled.
32
REPORTING CURRENCY CONVERSION FOR ASSET LEASES
Report your leases in any currency other than your ledger currency. Using reporting currencies, you can
maintain and report lease accounting and balances in more than one currency. Convert right-of-use asset
balances at historical rates and lease liability balances at the current rate. Load your asset lease terminations
or reassessments in bulk using the supplied File-based data import templates.
Choose the Currency for Your Lease Inquiry View
You can view the lease amounts and accounting entries for primary and reporting currencies.
You can load your lease terminations or reassessments in bulk using the supplied File-based data import
templates using the enhanced Import Asset Leases process.
STEPS TO ENABLE
From the Manage Asset Books page create a corporate book with a primary ledger that has reporting
currencies. Ensure that the book’s Asset Leases check box is enabled.
EXPENSES
CONTROL DISPLAY OF FIELDS BY EXPENSE TYPE

You can more easily control the information gathered for each expense type on the Create Expense Item
page. You can enable fields, such as Description, Merchant Name, Expense Location, and Number of
Days, on the Manage Expense Report Templates page for the expense template and on the Create
Expense Type page for each expense type. The settings for the expense type override the settings for the
expense template. The following settings are available for each field.
Hidden. The field is not displayed.

Optional. The field is displayed when the expense type is selected, but you are not required to enter data.
Required. The field is displayed when the expense type is selected and you are required to enter data.
33
The fields available for configuration vary by expense category. The Number of Days field is available only for
Accommodation, Car Rental, and Miscellaneous expense categories.The application does not allow you to
control field display if an associated expense policy requires any of these fields for policy enforcement. The field
display behavior at the expense type level overrides all other configurations, such as fields controlled by profile
options, the Manage Tax Fields page, and the Manage Expense Fields by Category page.
STEPS TO ENABLE
To enable or disable fields by expense type in an existing template, you must complete these steps:
1. In the Setup and Maintenance work area, navigate to the Manage Expense Report Templates task.
2. On the Manage Expense Report Templates page, select the expense template and click the Edit icon.
3. Click the Expense Fields tab.
4. Select the expense field behavior for the Description, Merchant Name, Expense Location, and Number of
Days fields. The behavior selected here applies to all expense types unless you define behavior for a
specific expense type.
5. To define expense field behavior for an expense type, click the Expense Types tab.
6. Select the expense type and click the Edit icon.
7. Click the Expense Fields tab.
8. Select the expense field behavior.
9. Click Save the details.
NOTE: The filed behavior defined for an expense type overrides the field behavior defined at the
expense template.
Defining Expense Field Behavior for an Expense Template
34
If you are already using Cloud Expenses, the Description, Merchant Name, Expense Location, and Number
of Days fields are displayed by default. You can then disable the expense fields that are not applicable for the
expense type or for the template.
ROLE INFORMATION
You must have one of the following roles to enable expense fields by expense type:

Expense Manager
SHORTCUTS FOR ATTENDEE SELECTION

We have made it easier for you to add attendees to your expense items on the Create Expense Item
page. Four new shortcuts are available for faster attendee selection as follows.
Direct Reports. Allows you to select attendees from the list of people reporting to you. This short cut is
available only for employee attendee selection.
Favorites. Allows you to select attendees from a list of favorites. You can mark any attendee as a
favorite when entering an expense item.
Recent Attendees. Allows you to select any previously selected attendees. The Recent Attendees list
shows attendees selected in reports during the past six months. The list conveniently filters to employees
when you enter employee attendees and it filters to nonemployees when you enter nonemployee
attendees.
Others. Allows you to search for any employees and any nonemployees who are designated as
attendees. You can select multiple attendees from the search results.
New Shortcuts
STEPS TO ENABLE
GENERAL LEDGER
ACCOUNTING AUTOMATION
Accounting Automation streamlines and automates your end-to-end accounting and transaction processes,
including Import Daily Rates, Create Accounting, Import Journals and Posting, greatly reducing manual work
35
and time lags in your business operations. The data flows through all of the required processing steps with no
user intervention, while making it easy to involve the right people at the right time to resolve exceptions. This
ensures the continuous availability of the most accurate and up-to-date financial information.
Users are notified of exceptions and guided through how to resolve them to allow accounting to be completed.
Additional users can optionally be notified of errors generated during the transaction accounting process.
Main Components of the Accounting Automation Feature:
When you opt in, the Manage Accounting Automation setup page automatically opens where you can
complete the setup.
Email notification and report for the default user: Summary of processed data, errors and pending
approvals to the specified default user.
Email notification and report for the other specified users: Summary of errors and pending approvals to
the specified users.
STEPS TO ENABLE
Use the Manage Accounting Automation setup page to enable and schedule the accounting automation.
You can also optionally specify the users to be notified of the errors generated while processing accounting
transactions, based on the ledger or ledger set, and the category that an error falls under.
Manage Accounting Automation Setup Page
Step 1: Enable Automation
Step 2: Specify the Scheduled Submission Time
Step 3: Specify the Default User to Notify
Step 4: Optionally specify additional users to be notified of the errors found while processing accounting
transactions, based on the ledger or ledger set, and the category that an error falls under.

1. When you enable Accounting Automation, transaction data for all of the ledgers (primary, secondary,
and journal and subledger level reporting currencies) in the system is processed.
2.
36
2. Accounting Automation should not be enabled if you are using or plan to use segment value security.
3. Approvals are not automatically submitted for any type of journal batch. If a journal batch needs
approval, it must be submitted for approval manually or through the AutoPost process.
4. Accounting Automation should not be enabled if you are using or plan to use any form of coexistence.
5. Accounting will only be generated for events with an accounting date of system date or earlier. Future-
dated accounting will not be generated automatically.
6. Incomplete journal batches will not be picked up by Accounting Automation for posting.
7. Accounting Automation will not pick up transactions that were created on a date before Automation was
enabled, unless the transaction has an accounting date the same as or after the date
that Automation was enabled.
8. If you use Oracle Receivables and plan to enable Accounting Automation, you must schedule to run the
Create Receivables Accounting process daily, before the Accounting Automation scheduled time.
ROLE INFORMATION
The Accounting Automation feature is secured by the Manage Accounting Automation Setup and Run
Accounting Automation Program privileges. The new accounting automation privileges are assigned to the
General Accounting Functional Administration Duty, which rolls up to the Financial Application Administrator
and Application Implementation Consultant job roles.
PAYABLES
INVOICE ROUTING FOR ACCOUNT CODING

The Invoice Routing for Account Coding feature enables customers to route invoices to business users for
entering accounting information. Generally, all unmatched invoices need the accounting information entered to
complete it. The Payables clerk usually has to interact with multiple users to get this information. The
information is internal, can differ from invoice to invoice, and depends on the expenditure incurred. In most
cases, the business users that have incurred the expenditure can provide the details for the accounting
information. This feature provides customers an efficient way to route unmatched invoices to these business
users to provide the accounting information.
Users are notified about the assignment through email and workflow notifications. Accounting information can
be entered directly in the workflow notification. Upon completion of the assigned task, the accounting
information is updated on the invoice and it is ready for the next step in processing such as approval or payment.
Users on the invoice routing list can only access those invoices assigned to them. They can perform additional
actions such as, request additional information, reassign to other users, or return the assignment.
Business validations are performed during the entry of the accounting information. User are alerted when there
is any excess or shortfall of the accounting information.
STEPS TO ENABLE
1. Enable the feature from the Functional Setup Manager Feature Opt In page. The steps are:
a. Go to the Setup and Maintenance work area.
b. Select Financials in the drop-down list at the top of the page.
c. Click Change Feature Opt In.
d. On the Opt In: Financials page, click the Features icon for Payables. On the Edit Features:
Payables page, select the enable check box for ‘Invoice Routing for Account Coding’ feature
e. Click Done to return to the Setup: Financials page.
2. The feature must to be enable at the business unit level in Manage Invoice Options. The steps are:
a.
37
2.
a. Go to the Setup and Maintenance work area.

b. Select Financials in the drop-down list at the top of the page.
c. Select Payables in the Functional Area.
d. Select Manage Invoice Options; select the scope “Business Unit”.
e. Select the “Enable invoice account coding workflow” option in the “Invoice Entry” region.
f. Click on Save and Close.

1. The Account Coding workflow task is seeded with the assignment rules that assigns all invoices to users
having the AP Supervisor role. The assignment rule can be modified based on business needs.
2. The Invoice Account Coding Assignment rules can be defined based on the invoice attributes.
3. The Configurable Payable Email Notification feature is available for the Account Coding workflow,
however, this feature is not enabled by default. This can be enabled by using Opt In for the feature:
‘Configurable Payable Email Notification’.
RECEIVABLES
ADDITIONAL ATTRIBUTES FOR CREDIT CHECKING SERVICE

You can now use descriptive flexfields to pass additional values to credit case folders created as the result of
credit checking failure. Pass additional information related to the source transaction requesting the credit
check, such as Contract Start Date, Contract Billing Frequency, and Contract Invoicing Rule. The descriptive
flexfields are displayed in the Additional Information section of the Edit and View Credit Case Folder pages.
You can edit these additional attribute values before the case folder is approved. Once the case folder is
approved, these values are rendered read-only.
Edit Case Folder Page - Additional Information Region
STEPS TO ENABLE
Define the credit case folder descriptive flexfields to match the values passed through the Credit Checking
Service. If the data types for the attributes do not match, or if the descriptive flexfields are not defined, these
additional attributes will not appear in case folders created as a result of a credit check failure.
38
ROLE INFORMATION
No new role access is needed to use this feature.
ORDER LEVEL CREDIT RECOMMENDATION

Credit Management now supports order level credit recommendation. This feature contains the following
components:
Creation of a case folder at the order level.

Enhanced Credit Case Folder pages with the request type Credit Checking Failure.
New public business event when a case folder is closed.
1. Creation of case folder at order level
If a new order is submitted for a customer account that has an active case folder with the request type
Credit Checking Failure for a different source transaction, the Credit Checking Service now creates a
new case folder for the customer account with the request type Credit Checking Failure and the new
source transaction information. You can view all the active case folders for a customer account in the
Credit Reviews work area.
2. Enhanced Credit Case Folder pages with the request type Credit Checking Failure
You can filter case folders by Source Transaction Number in the Credit Reviews work area. The Source
Transaction Number column is hidden by default. You can view additional source information for a case
folder using the Credit Case Folder page:
The Source Transaction number is part of the page title, for example, “Credit Case Folder 2007
(Source Transaction 58910)”.
Use the Credit Checking Details window to view details of a credit request, including the customer
and customer account on the source document, and whether a case folder is created from a
preauthorization request.
39
Two new recommendation types are introduced for case folders with the request type Credit Checking
Failure:
Approve Source Transaction Credit Request: Upon approval of the case folder containing this
recommendation, the application uses the attributes passed using the Credit Checking Service to
create a credit authorization, bypassing the available credit amount check or order amount limit
check.
Decline Source Transaction Credit Request: This recommendation indicates that the credit request
from the source transaction is declined. No credit authorization is created upon case folder
approval.
3. New public business event when a case folder is closed
When a case folder status is updated to Closed, Receivables publishes a public Credit Case Folder
Closure business event. When all recommendations in a case folder have been successfully
implemented, the case folder status is automatically updated from Approved to Closed. A credit analyst
can also manually close a case folder using the Close action. The public Credit Case Folder Closure
business event contains the following information:
Key attributes of the case folder, including case folder number, status, credit analyst, creation
date, and last updated date.
40
Key attribute values that the calling party has passed using the latest credit checking service call,
including customer, customer account, requested authorization amount, source document
information.
Key attributes of the new credit authorization record (if Approve Source Transaction Credit
Request is one of the recommendations), including credit authorization number, authorization
expiration date, and authorization amount.
List of all approved recommendations (if the case folder is approved), including the new values for
credit limit and credit classification.
STEPS TO ENABLE
ROLE INFORMATION
No new role access is needed to use this feature.
RECEIVABLES INVOICE DELIVERY IN OPEN APPLICATIONS GROUP INTEGRATION

SPECIFICATION 10.1 XML FORMAT
Use this feature to generate and deliver Receivables XML invoices in the latest Open Applications Group
Integration Specification (OAGIS) 10.1 format using the Collaboration Messaging Framework (CMK).
Receivables XML invoicing now supports embedding invoice header attachments in the XML payload. You can
receive inbound acknowledgements in OAGIS 10.1 Confirm Business Object Document (CBOD) format from
your trading partner.
The new OAGIS 10.1 invoice format allows you to include unlimited additional user-defined attributes in the
standard user area of the XML message.
Use the Customer Import FBDI to import Trading Partner and Customer Account Collaboration configuration
into CMK, as part of Customer Account Profile import.
STEPS TO ENABLE
Use the Feature Opt-in page in Functional Setup Manager to enable the Receivables Invoice Delivery in Open
Applications Group Integration Specification 10.1 XML Format feature.
NOTE: If you are using the existing Receivables XML Invoicing feature through Service Oriented Architecture
(SOA) business-to-business (B2B) gateway and decide to opt-in for this new feature, you will need to re-do
the Trading Partner setup in Fusion CMK.
SET UP YOUR RECEIVABLES CUSTOMER ACCOUNT PROFILE
In the Edit Account Profile page: Invoicing section, perform these two tasks:
1. Set the Preferred Delivery Method field to XML.

2. Select the Enable for XML Invoicing check boxes for all transaction classes that you want to enable for
XML delivery: Invoice, Debit Memo, Chargeback, Credit Memo.
You can also perform this setup using the Customer Import spreadsheet.
41
SET UP THE COLLABORATION MESSAGING FRAMEWORK (CMK)
Complete the following required setup in Fusion CMK both to generate and deliver XML invoices and to receive
inbound CBOD acknowledgement from your customer.
1. Use the Manage Collaboration Messaging Configuration task in the Setup and Maintenance work area to
enable the Order To Cash Collaboration Business Process.
2. Define Service Providers for XML invoice delivery. a. Use the Manage Collaboration Messaging Service
Providers task in the Setup and Maintenance work area to define your Service Providers. b. In the Edit
Collaboration Messaging Service Provider page, define the Delivery Methods, Outbound Collaboration
Message, and Inbound Collaboration Message.
Outbound Collaboration Message to be added is OAGIS_10.
1_PROCESS_INVOICE_COLLAB_MSG_OUT.
Inbound Collaboration Message to be added is OAGIS_10.1_CONFIRM_BOB_COLLAB_MSG_IN.
Associate the inbound CBOD message to the invoice outbound message as shown below.
3. Define your Trading Partners, one for each Customer Account.

a. Use the Manage B2B Trading Partners task in the Collaboration Messaging work area to define
Trading Partners.
b. In the Edit Trading Partners page, associate the outbound invoice (PROCESS_INVOICE_OUT)
and inbound CBOD (CONFIRM_MESSAGE_RECEIPT_IN) collaboration documents to the
Trading Partner.
4. Associate the Service Provider and Trading Partner created in the previous steps to the Customer
Account from Manage Customer Account Collaboration Configuration task in the Collaboration
Messaging work area. Search for an existing Customer Account and click the Edit Collaboration
Configuration button.
42
Service Provider, Trading Partner, and the collaboration document are associated to the Customer Account
NOTE: It is not required to explicitly associate inbound CBOD collaboration document to the Customer
Account as the association is already done at the Service Provider level.
This setup in Fusion CMK is required in order to generate and deliver XML invoices and to receive inbound
CBOD acknowledgement from your customer.
NOTE: Fusion CMK supports delivering XML invoices directly to Trading Partners without a Service Provider.
To enable this feature, use the predefined Service Provider 'None' and set up your Trading Partners.
SETUP FOR INCLUDING ATTACHMENTS WITH XML INVOICE DELIVERY
To include invoice header attachments in the XML payload, complete these steps:
1. In the Manage Attachment Categories page, create an Attachment Category to use exclusively for XML
invoice attachments.
2. In the Manage Receivables Profile Options page, search for the

AR_BPA_PRINT_ATTACH_CATEGORY profile option. Add a profile value at Site level, and set this
profile value to the Attachment Category Name defined in the previous step.
43
3. In the Attachments window of the Create Transaction page, select the Attachment Category that you
associated with the AR_BPA_PRINT_ATTACH_CATEGORY profile option whenever you add an
attachment to a transaction.
USING THE USERAREA EXTENSION ATTRIBUTES IN OAGIS 10.1 XML INVOICING
The OAGIS 10.1 XML Invoice format lets you extend the XML invoice attributes using the Extension tag
with the typecode 'UserArea'. For example, a customer may require a specific attribute on the XML
invoice that is not mapped in the OAGIS 10.1 format and has no standard tag available in OAGIS 10.1. In
cases like this, you can add the attribute to the UserArea extension of OAGIS 10.1.
You can compute and load these extension attributes for Receivables transactions, according to your
business needs, into the AR_EXTENSION_ATTRIBUTES table using the public API arp_util.
insert_ar_extension_attributes.
Receivables supports adding UserArea Extension attributes at the Invoice Header, Invoice Line and
Invoice Tax Line levels in OAGIS 10.1 XML.
The arp_util.insert_ar_extension_attributes API needs to be invoked by customizing the delivered Load
Extension Attributes for XML Transactions Business Intelligence (BI) Publisher report.
The Load Extension Attributes for XML Transactions BIP report process runs as a child process of the
Generate and Transfer XML Transactions process. The extension attributes for Receivables transactions
are computed and loaded into the table as part of the XML invoice creation process.
This BIP report process, if customized to load extension attributes, generates an output containing any
errors that occur during execution.
To customize the Load Extension Attributes for XML Transactions BIP report for loading extension attributes,
complete these steps:
1. Log into Oracle Fusion BI Publisher Enterprise using the xmlpserver URL for user with BI Administrator
Role and navigate to Catalog.
2. Customize the Load Extension Attributes for XML Transactions data model.
44
3. Click on the gear icon and select 'Edit Data Set'.
4. PL/SQL code should be written in the SQL Query section to compute and load extension attributes for
transactions being processed. The arp_util.insert_ar_extension_attributes API needs to be invoked
through this code.
NOTE: When using the extension attributes functionality, RA_CUSTOMER_TRX_ALL.

READY_FOR_XML_DELIVERY flag needs to be set to Y for transactions once the extension attributes are
inserted. The API to set this flag is arp_util.update_ready_for_xml_flag.
45
Signature of arp_util.insert_ar_extension_attributes API is:
PROCEDURE insert_ar_extension_attributes(extension_attr_tbl IN ARP_UTIL.
EXTENSION_ATTR_TBL_TYPE, x_msg_count OUT NOCOPY NUMBER, x_msg_data OUT NOCOPY
VARCHAR2, x_return_status OUT NOCOPY VARCHAR2);
EXTENSION_ATTR_TBL_TYPE is a PL/SQL table of EXTENSION_ATTRIBUTE_RECORD record type, and

definition of EXTENSION_ATTRIBUTE_RECORD record type is as given below:
TYPE EXTENSION_ATTRIBUTE_RECORD IS RECORD(EXTN_ENTITY_ID AR_EXTENSION_ATTRIBUTES.

EXTN_ENTITY_ID%type, ASSOCIATED_EXTN_ENTITY_ID1 AR_EXTENSION_ATTRIBUTES.
ASSOCIATED_EXTN_ENTITY_ID1%type,
ASSOCIATED_EXTN_ENTITY_ID2 AR_EXTENSION_ATTRIBUTES.ASSOCIATED_EXTN_ENTITY_ID2%
type,ENTITY_TYPE_CODE AR_EXTENSION_ATTRIBUTES.ENTITY_TYPE_CODE%type,
PROCESS_TYPE_CODE AR_EXTENSION_ATTRIBUTES.PROCESS_TYPE_CODE%type,
ATTRIBUTE_NAME AR_EXTENSION_ATTRIBUTES.ATTRIBUTE_NAME%type,
ATTRIBUTE_VALUE AR_EXTENSION_ATTRIBUTES.ATTRIBUTE_VALUE%type);
The extension attributes once loaded can be updated using the arp_util.update_ar_extension_attributes
API. ATTRIBUTE_NAME and ATTRIBUTE_VALUE columns in the AR_EXTENSION_ATTRIBUTES
table can be updated using this API.
Signature of arp_util.update_ar_extension_attributes API is:
PROCEDURE update_ar_extension_attributes(extension_attr_tbl IN ARP_UTIL.EXT_ATTR_TBL_FR_UPDATE,

x_msg_count OUT NOCOPY NUMBER, x_msg_data OUT NOCOPY VARCHAR2, x_return_status OUT
NOCOPY VARCHAR2);
EXT_ATTR_TBL_FR_UPDATE IS PL/SQL table of EXT_ATTR_RECORD_FR_UPDATE record type, and

definition of EXT_ATTR_RECORD_FR_UPDATE record type is as given below:
TYPE EXT_ATTR_RECORD_FR_UPDATE IS RECORD(EXTN_ENTITY_ID AR_EXTENSION_ATTRIBUTES.

EXTN_ENTITY_ID%type, ENTITY_TYPE_CODE AR_EXTENSION_ATTRIBUTES.ENTITY_TYPE_CODE%
type, PROCESS_TYPE_CODE AR_EXTENSION_ATTRIBUTES.PROCESS_TYPE_CODE%
type, ATTRIBUTE_NAME AR_EXTENSION_ATTRIBUTES.ATTRIBUTE_NAME%
type, NEW_ATTRIBUTE_NAME AR_EXTENSION_ATTRIBUTES.ATTRIBUTE_NAME%
type, NEW_ATTRIBUTE_VALUE AR_EXTENSION_ATTRIBUTES.ATTRIBUTE_VALUE%type);
COLLABORATION MESSAGING SETUP USING THE CUSTOMER IMPORT FBDI
You can import both the CMK setup required for XML invoicing and Customer Account Profile information
using the Customer Import FBDI template.
The prerequisite setup for importing CMK trading partners is to define Service Providers using the
Manage Collaboration Messaging Service Providers task.
NOTE: You cannot use the predefined Service Provider None to import the trading partner setup using
the Customer Import FBDI template.
The new CMK setup related columns are hidden by default in the
RA_CUSTOMER_PROFILES_INT_ALL sheet of the Customer Import template. To display these
columns:
Highlight the column XML Invoicing for Credit Memo and the next column.
Right click to display the new CMK setup related columns:
Enable Collaboration Messaging Configuration: If you want to import CMK setup for the
Customer Account, set the value to Y in this column.
Service Provider Name: Name of the B2B messaging service provider. This should have
been defined in the system through Manage Collaboration Messaging Service Providers
task.
46
Trading Partner ID: User-defined code that identifies a customer account as a trading
partner to receive XML transactions.
Trading Partner ID Type: Labeling category for the identifier that you used to define the
trading partner in the PARTNER_ID attribute. Valid values are: DUNS, Generic (typically
the customer account number), GLN, MISC, PHONE, TAXID, Name (typically the customer
account name).
Receivables Outbound XML Transaction Document: Option that indicates whether the
trading partner is enabled to receive Receivables transactions in XML format.
Receivables Inbound Confirmation Document: Option that indicates whether the trading
partner is enabled to send back a confirmation BOD after receiving an XML transaction.

After a run of the Generate and Transfer XML Transactions process, use the Manage Transactions task
in the Receivables Billing work area to view the XML Delivery status.
Use the Manage Collaboration Messaging History page in the Collaboration Messaging work area to
verify successful processing of transactions with an XML payload.
Review any errors during XML invoice generation and delivery, using the Manage Undelivered
Collaboration Messages and Manage Failed Collaboration Messages pages in the Collaboration
Messaging work area.
For transactions with the XML Delivery Status 'Processing Error', the error details are displayed in
the Manage Undelivered Collaboration Messages page. You can either reprocess these
transactions in the Manage Undelivered Collaboration Messages page or set them to the
'Delivery Failed' status by cancelling the transactions.
For transactions with the XML Delivery Status 'Delivery Failed', the error details are displayed in
the Manage Failed Collaboration Messages page. You can reprocess with another run of the
Generate and Transfer XML Transactions process. Set the Transactions Included parameter to
Failed Transactions.
By default, the Inbound CBOD from the Customer must have an acknowledgement code of Success,
Error, or Other to appear in the XML Delivery Status attribute in the Manage Transactions page. If
customers want to use their own status codes, you can map the customer's codes to one of the three
statuses using the Manage Confirmation Codes page from the Manage B2B Trading Partners task in the
Collaboration Messaging work area.
KEY RESOURCES
Refer to the following topics in the Collaboration Messaging Framework documentation for further
information on: How to use Collaboration Messaging; how to reprocess messages in error; and how to
process outbound and inbound messages using CMK:
Using Collaboration Messaging
Reprocessing Undelivered Messages
Process Outbound Collaboration Messages
Process Inbound Collaboration Messages
47
https://docs.oracle.com/en/cloud/saas/supply-chain-management/r13-update17d/faicf/define-
collaboration-messaging.html#FAICF2082721
ROLE INFORMATION
Users with the Accounts Receivable Manager or Accounts Receivable Specialist role can access the
Collaboration Messaging work area tasks, and import CMK setup using the Customer Import FBDI process.
Users with access to Receivables Administration Duty will have access to the Manage Collaboration
Messaging Configuration and Manage Collaboration Messaging Service Providers tasks under the Setup and
Maintenance work area.
STORE PRINTED RECEIVABLES TRANSACTIONS AS ATTACHMENTS

Use the Store printed transaction as attachment feature to retain and access original printed or emailed
transaction as an attachment. When this feature is opted in, the Upload Printed Receivables Transactions
background process, that runs as a post process to the Print Receivables Transactions process, ensures that
printed and emailed transaction copies are stored as an attachment on the transaction. You can access the
original printed transaction as an attachment in the Review Transaction page.
STEPS TO ENABLE
The Store Printed Receivables Transactions as Attachments feature is enabled by default in the Functional
Setup Manager feature opt-in page.
However, additional setup is required to enable this feature. Follow these steps:
1. Navigate to the Setup and Maintenance work area.

2. Search for the setup task Manage Receivables Lookups.
3. In the Manage Receivables Lookups page, search for the AR_FEATURES lookup type. (If the lookup
type AR_FEATURES does not exist, create it first using the setup task Manage Standard Lookups.)
4. Add a lookup code AR_STORE_PRINTED_TRANSACTIONS to the AR_FEATURES lookup type and
save the changes.

Printed and emailed transaction copies are stored as attachments on the transaction header as a post
process to the Print Receivables Transactions background process.
48
Use the Review Transaction page to access a copy of a printed or emailed transaction:
WEB SERVICE TO CREATE REFERENCE ACCOUNTS FOR CUSTOMERS

Use this feature to create reference account combinations for a customer bill-to site, using the new Customer
Bill-to Site Reference Accounts SDO in the Customer Profile web service. The reference account combinations
that you create are used to derive account combinations for distributions on Receivables transactions, when
AutoAccounting is set up to derive account combinations based on Bill-to Site.
STEPS TO ENABLE
There are no steps to enable this feature. This is a new Web service operation.
The name of the operation in the Customer Profile Web Service to create reference account combinations for a
customer bill-to site is createReferenceAccountsForBillToSite
SDO Name: Customer Bill-to Site Reference Accounts
SDO Description: Service to create bill-to site reference accounts for customer accounts. This setup is used for
deriving account combinations for distributions on Receivables transactions, when AutoAccounting is set up to
derive account combinations based on Bill-to Site.
49
KEY RESOURCES
Refer to the SOAP Web Services for Oracle Financials Cloud documentation for details of this service:
https://docs.oracle.com/en/cloud/saas/financials/r13-update17d/oeswf/Receivables-Web-Services-
Overview.html
Refer to the Usage Notes for Receivables Customer Profile Service in the Oracle ERP Cloud Integration
for Credit to Cash section of the SOAP Web Services documentation: http://www.oracle.com/webfolder
/technetwork/docs/fbdi-r13-17d/fbdi/supportingdocs/fin-CustomerProfileServiceAM.pdf
ROLE INFORMATION
Users with Accounts Receivable Manager or Accounts Receivable Specialist role can access this
service.
TRANSACTIONAL BUSINESS INTELLIGENCE FOR FINANCIALS
REPLACE BUSINESS UNIT VIEWS FOR IMPROVED PERFORMANCE

To improve query performance in Financial subject areas, Business Unit views were replaced with more
optimized ones.
STEPS TO ENABLE
SUBLEDGER ACCOUNTING - JOURNALS REAL TIME SUBJECT AREA ENHANCEMENTS

The Payables Transaction Details folder in the Subledger Accounting - Journals Real Time subject area has
been synchronized with similar folders in the Payables subject areas, for better usability: new columns added
to Header Information, Reference Information and Tax Information folders.
STEPS TO ENABLE
REGIONAL AND COUNTRY-SPECIFIC FEATURES
FINANCIALS FOR EMEA
SPAIN
ONLINE VAT REPORTING FOR SPAIN

Effective January 1, 2017, Spanish companies with an annual turnover above 6 million Euros must report
received and issued transactions in a predefined electronic format. From July 1, 2017 transactions must be
reported within four days of reception or issuance date. Transactions created in the first semester must be
reported by the end of the year.
50
The Online VAT Reporting for Spain solution provides the following components to support this legal
requirement:
Additional fields, which are specific to Online VAT Reporting for Spain, must contain the mandatory
reporting information.
Process, which extracts transactional details and creates an xml file in a predefined format.
Process that updates the transaction reporting status based on the confirmation message received from
the Spanish Tax Authority.
Online VAT Register Reporting for Spain process creates xml file for the following registers:
Issued Invoices Register

Received Invoices Register
Selected Intra-EU Transactions Register
Payments Register
Receipt Collections Register
Online VAT Register Reporting Confirmation for Spain updates transactions with the response message details.
Annual Online VAT Register Reporting for Spain process creates an xml file for the following register:
Cash Collection Register
Annual Online VAT Response for Spain updates customer accounts and sites that were reported to the Tax
Authority with the corresponding confirmation information.
51
Annual Online VAT Investment Goods Register Reporting for Spain process creates xml file for the following
register:
Investment Goods Register
Online VAT Reporting for Spain Process
STEPS TO ENABLE
KEY RESOURCES
Online VAT Reporting for Spain Topical Essay
ROLE INFORMATION
EMEA Financial Reporting duty role
---
52
Copyright © 2018, Oracle and/or its affiliates. All rights reserved.
This document is provided for information purposes only, and the contents hereof are subject to change without notice.This document is not warranted to be error-free, nor subject to any
other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically
disclaim any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced
ortransmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.
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.
53

r13 2018 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

r13 2018 Financials WN

Hochgeladen von

Copyright:

Verfügbare Formate

TABLE OF CONTENTS

Date Update Version Notes

20 APR 2018 Update 18B Delivered new features in update 18B.

19 JAN 2018 Update 18A Delivered new features in update 18A.

Date Feature Notes

20 APR 2018 Created initial document.

CUSTOMERS UPGRADING FROM RELEASE 12

JOIN ORACLE CLOUD CUSTOMER CONNECT

Action Required to Enable Feature

Common Technology and User Experience

Improved Cross-Pillar Reporting Between

COMMON FINANCIALS FEATURES

ENHANCED DATA SEGREGATION FOR THIRD-PARTY SERVICE PROVIDERS

Assets Asset Inquiry Employee

Add Asset Employee

Prepare Source Lines Preparer

Manage All Books Preparer

Add Asset in Spreadsheet Preparer Employee

Employee (Asset Selection Criteria) Employee (Transfer

Perform What-If Analysis Employee

Manage Asset Distribution Sets Employee

Manage Customer -> Edit Account Credit Analyst (Profile History)

Manage Customer -> Edit Site Credit Analyst (Profile History)

Credit Reviews Credit Analyst

Manage Receivables Customer Profile

Manage Approval Limits User

Collections Manage Collectors Employee

Payables Create Payables Invoice Preparer

Import Payables Invoice Preparer

Submit Payment Process Request First Approver

Manage Payment Process Request

Expense Manage Corporate Cards Employee

Manage Historical Credit Card

Review Corporate Card Transactions Employee

Manage Expense Reports Employee

Manage Expense Audit List Membership Employee

Manage Cash Advances Employee

Manage Expenses Contingent Worker Employee

Review Payment Requests Employee

Review Invoices Contingent Worker

Manage Expense Reports Employee

About Me -> Manage Delegates Person

Accounts Payable Manager

CONFIGURABLE WORKFLOW NOTIFICATIONS

To enable the feature, complete these steps:

1. Go to the Setup and Maintenance work area.

TIPS AND CONSIDERATIONS

Budget Transfer Request

Budget Transfer Request Notification

No steps are required to enable this feature.

TIPS AND CONSIDERATIONS

DISABLE SCAN OPTION ON MOBILE EXPENSES

To define the profile option, follow these steps:

To define the profile option value, follow these steps:

Application Implementation Consultant

ITEMIZATION OF MEALS EXPENSE CATEGORIES

To itemize a meal expense type, follow these steps:

Application Implementation Consultant

CONFIGURE AUDITABLE SETUP ATTRIBUTES AND VIEW AUDIT REPORT

1. Select the Manage Audit Policies task.

To view the audit report:

1. From the Navigator, select Tools to open the Audit Reports.

STREAMLINED PAYMENT PROCESSING