AP Guides1

Unauthorized reproduction or distribution prohibitedฺ Copyright© 2017, Oracle and/or its affiliatesฺ
ble
fe r a
ans
n - t r
no
a
) has eฺ
ฺ c om uid
ฺ i b m nt G
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h
Oracle Financials Cloud: Payables to

Cash Management Implementation
Student Guide – Volume II

D96151GC30 | D102115
Learn more from Oracle University at education.oracle.com

Authors Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
Bruce Ingram Disclaimer
Kathryn Wohnoutka This document contains proprietary information and is protected by copyright and
Vijay other intellectual property laws. You may copy and print this document solely for your
own use in an Oracle training course. The document may not be modified or altered
in any way. Except where your use constitutes "fair use" under copyright law, you
may not use, share, download, upload, copy, print, display, perform, reproduce,
Technical Contributors
publish, license, post, transmit, or distribute this document in whole or in part without
and Reviewers the express authorization of Oracle.
Angie Shahi The information contained in this document is subject to change without notice. If you
Christine Rudd find any problems in the document, please report them in writing to: Oracle University,
500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not
Carol Ann Lapeyrouse warranted to be error-free.
David Barnacle
Restricted Rights Notice
Deepak Seth
If this documentation is delivered to the United States Government or anyone using
Hari Sanka the documentation on behalf of the United States Government, the following notice is
ble
Ivy Farren applicable:
fe r a
Julianna Dodick
an s
Johanna Rusly
U.S. GOVERNMENT RIGHTS
n - t r
The U.S. Government’s rights to use, modify, reproduce, release, perform, display, or
Kondaiah Mandadi
a no
disclose these training materials are restricted by the terms of the applicable Oracle
license agreement and/or the applicable U.S. Government contract.
Kishore Singh Trademark Notice
) h as ฺ
Lokesh Jetty
ฺ c o
Oracle and Java are registered trademarks de its affiliates. Other names
mof Oracleuiand/or
Madhulika Deshmukh
i b m owners.
may be trademarks of their respective
n t G
Mitesh Kumbhat ฺ
in tude
r @
ga this S
Mary O’Neill
Mallapuram Ranganath a
w se
s h
l (a e to u
Narayana Palukuri
a
Raghupathy Varadharajan
w ns
Steven Chi ar
a
Wallace A g
Gardipe l ice
ry
wa
Ash Publishers
Jayanthy Keshavamuthy
Pavithran Adka
Sumesh Koshy
360225202020A
Contents
1 Oracle Financials Cloud: Payables to Cash Management Implementation

Overview
Course Objectives 1-2
Lesson Objectives 1-5
Course Schedule 1-6
Introduction to Oracle Cloud Applications 1-8
ble
Oracle Cloud Applications: Product Families 1-9
fe r a
Oracle Financials Cloud: Overview 1-10
ans
Financials Cloud: Key Features 1-11 n - t r
n o
Procure-to-Pay Flow 1-12
a
Tasks to Configure Payables to Cash 1-13
) has eฺ
Overview of Suppliers 1-14
ฺ c om uid
Invoice Processing Overview 1-15
ฺ i b m nt G
in tude
Overview of Subledger Accounting 1-17
@
r
ga this S
Overview of Payments: Disbursements 1-18
a
w se
Overview of Cash Management 1-19
s h
l (a e to u
Summary 1-20
a
g arwOracle
c e nsCloud Navigation
A
2 Introducing
li
aryaObjectives 2-2
s h w News Feed Home Page Layout 2-3
A Sections: Things to Finish and News and Announcements 2-4
Analytics Section 2-5
Navigator 2-6
Predefined Themes for News Feed Home Page Layout 2-7
Getting Started with Other Themes 2-8
Navigation Components 2-9
Welcome Springboard 2-10
Favorites and Recent Items 2-11
User Interface: Invoices Work Area 2-12
Search Panel Overview 2-13
Reports and Analytics Panel 2-14
Dashboards 2-15
Practice 2-1 Overview: Running Session Warmer Scripts 2-16
Practice 2-2 Overview: Getting Started in Cloud Applications 2-17
iii
Personalizations Overview 2-18
Setting User Preferences 2-19
Structure Work Area 2-21
Saved Searches 2-22
Configuring Table Columns 2-23

Practice 2-3 Overview: Exploring Infolets 2-24
Practice 2-4 Overview: Using Personalizations 2-25
Summary 2-26
3 Overview of Security
Objectives 3-2
ble
Oracle Financials Cloud Security Methodology 3-3
fe r a
Security Model: Role Based Access Control 3-4
ans
Security Reference Implementation 3-5
n - t r
Job and Duty Roles 3-6 n o
a
has eฺ
GL Predefined Job Roles 3-7
Privileges 3-9 )
Resources 3-10 ฺ c om uid
ฺ i b m nt G
Data Security Policies 3-11
@ in tude
r
ga this S
Analyze Data Security Policies by Resource 3-12
a
Role Inheritance 3-13
w se
s h
l (a e to u
Security Features Overview 3-14
a
Using Security Console 3-15
g arw cens
Compare Roles Feature 3-17
ry aA li
Move Function and Data Security Policies 3-18
w a Manage Data Access for Users Page 3-19
A s h Processes to be Performed on Users and Roles 3-20
Automatic Data Provisioning 3-21
Practice 3-1 to 3-2 Overview: Using the Security Console 3-23
Practice 3-3 to 3-5 Overview: Creating and Managing User 3-24
Upgrade-Safe Management of Factory Shipped Roles 3-25
Role Visualization 3-26
Search in Role Hierarchy Visualization 3-28
Tabular Role Hierarchy View 3-29
User Account Management 3-30
Administrator Password Management 3-31
User Account Locking 3-32
User Password Management: Self-Service 3-33
User Password Changes Audit Report 3-34
Users Categories 3-35
Add Users to User Category 3-36
iv
User Name Generation Rules 3-37
Password Policies 3-38
Notification Templates 3-40
Practice 3-6 Overview: Managing Password Security and Notifications 3-42
Self-Service External Identity Provider Setup 3-43

Bridge for Microsoft Active Directory 3-44
Auditing Security 3-45
Security Resources 3-46
Summary 3-47
4 Financials Setup Overview

ble
Lesson Objectives 4-2
fe r a
What is Functional Setup Manager? 4-3
ans
Functional Setup Manager Benefits 4-4
n - t r
Key Concepts 4-5 n o
a
has eฺ
Review Offerings and Prepare to Opt In 4-6
)
Opt into Offering, Functional Areas, and Features 4-7
ฺ c om uid
Review What’s New and Opt into New Features After Upgrade 4-8
ฺ i b m nt G
in tude
Practice 4-1 and Demonstration 4-2 4-9
@
r
ga this S
Manage Setup Data with Complete Transparency to Requirements 4-10
a
Manage Setup Data Your Way Using Flexible Processes 4-11
w se
s h
l (a e to u
Manage Setup Data Using Functional Areas 4-12
a
Related Setup Tasks 4-13
g arw cens
Tasks with Scope 4-14
ry aA li
Manage Setup Data Using Implementation Projects 4-15
w a Create an Implementation Project 4-16
A s h Review and Assign Tasks 4-17
Perform Assigned Implementation Tasks 4-18
Searching for a Task 4-19
Rapid Implementation Task List 4-20
Practice 4-3: Accessing Task Lists and Tasks 4-21
Configure Auditable Setup Attributes and View Audit Report 4-22
Audit History Enablement 4-23
Manage Setup Data Entry in Bulk 4-24
Export and Import CSV Processes 4-25
Copying Setup 4-26
Migration Overview 4-27
Classic Migration 4-28
Best Practices for Managing Setup Across Environments 4-29
Best Practices for Managing Setup: Using a Gold Copy 4-30
How Does Setup Import Manage Data? 4-31
v
Export an Offering or a Functional Area 4-32
Create a Comparison for an Offering or Functional Areas 4-33
Import an Offering or a Functional Area 4-34
Export and Import an Implementation Project 4-35
Learn More: Video Tutorials and User Guides 4-37

Learn More: User Guides 4-38
Summary 4-39
5 Enterprise Structures and Ledgers Overview

Objectives 5-2
Enterprise Structures Overview 5-3
ble
Legal Entities Defined 5-4
fe r a
Legal Entity, Ledgers, and Balancing Segment Values 5-5
ans
Legal Addresses, Jurisdictions and Authorities: Overview 5-6
n - t r
Manage Legal Reporting Units 5-7 n o
a
has eฺ
Financial Reporting Structures Overview 5-8
Chart of Accounts Components 5-9 )
Assigning Segment Labels 5-11 ฺ c om uid
ฺ i b m nt G
in tude
Accounting Calendar Overview 5-12
@
r
ga this S
Manage Currencies Overview 5-13
a
Ledgers Overview 5-14
w se
s h
l (a e to u
Ledger Structure 5-16
a
Sharing Common Applications Configurations 5-17
g arw cens
Geographies Overview 5-18
ry aA li
Practice 5-1 Overview: Reviewing Shared Components 5-19
w a Implementation Simplification 5-20
A s h Rapid Implementation Process 5-21
Practice 5-2 Overview: Using the Rapid Implementation Spreadsheet 5-22
Practice 5-3 Overview: Uploading the Chart of Accounts File 5-23
Deploying the Accounting Flexfield 5-24
Demonstration 5-4 Overview: Deploying the Accounting Flexfield 5-25
Practice 5-5 Overview: Inputting Account Combinations 5-26
Practice 5-6 Overview: Uploading the Financials Common Entities File 5-27
Specifying Ledger Options 5-28
Reviewing and Submitting Accounting Configuration 5-29
Practice 5-7 Overview: Completing the Ledger Configurations 5-30
Practice 5-8 Overview: Viewing Your Legal Entity 5-31
Summary 5-32
vi
6 Configuring Business Units, Reference Data Sets, and the Vision Story
Objectives 6-2
Common Applications Configuration for Financials 6-3
Business Units Overview 6-4
Business Unit Structure: Example 6-5

Business Unit Definition: Considerations 6-6
Implementing Business Units: Overview 6-7
Managing Business Units 6-8
Assigning Business Unit Functions 6-9
Managing Service Provider Relationships 6-10
Service Provider Model for Procurement Services 6-11
ble
Service Provider Model for Payables Payment Services 6-12
fe r a
Payment Services Model: Dedicated 6-13
ans
Payment Services Model: Self-Service 6-14
n - t r
n
Payment Services Model: Dedicated and Self-Service 6-15 o
a
has eฺ
Practice 6-1 Overview: Viewing Your Business Unit 6-16
)
Practice 6-2 Overview: Viewing the Assigned Business Unit Functions 6-17
Manage Reference Data Sets 6-18 ฺ c om uid
ฺ i b m nt G
in tude
Reference Data Sharing Overview 6-19
@
r
ga this S
Practice 6-3 Overview: Creating a Reference Data Set 6-20
a
Assigning Sets to Business Units 6-21
w se
s h
l (a e to u
Assignments to Multiple Sets, with No Common Values 6-22
a
Payables Payment Terms Example 6-23
g arw cens
Reference Data Set: Examples 6-24
ry aA li
Setting Up Payment Terms for Reference Data Sharing 6-25
w a Practice 6-4 Overview: Managing Your Business Unit Set Assignment 6-26
A s h Practice 6-5 Overview: Managing Data Access for Your User 6-27
The Vision Story: Overview 6-28
Scenario 6-29
Scenario Details 6-30
Vision Corporation Analysis 6-31
Vision Corporation Structure Diagram 6-33
Vision Corporation Enterprise Structure 6-34
Vision Corporation Business Unit and Department Structure 6-35
Vision Corporation Distribution Structure 6-36
Vision Corporation Chart of Accounts Summary 6-37
Summary 6-38
7 Configuring Oracle Payables

Objectives 7-2
Required Tasks to Configure Payables 7-3
vii
Payables Terminology 7-4
Flow of Default Values 7-5
Managing Procurement Agents 7-6
Practice 7-1 Overview: Defining Your User as a Procurement Agent 7-7
Managing Payment Terms 7-8

Payment Terms Due Date and Discount Dates 7-9
Day of Month Payment Term: Example 7-10
Defaults and Predefined Payment Terms 7-11
Practice 7-2 Overview: Creating a Payment Term 7-12
Managing Common Options for Payables and Procurement 7-13
Default Distributions 7-14
ble
Automatic Offsets 7-15
fe r a
Automatic Offset by Primary Balancing Segment 7-16
ans
Automatic Offset by All Segments, Except Natural Account 7-17
n - t r
Currency Conversion 7-18 n o
a
has eฺ
Expense Accruals 7-19
Self-Billed Invoices 7-20 )
Legal Entity Information 7-21 ฺ c om uid
ฺ i b m nt G
in tude
Practice 7-3 Overview: Managing Common Options for Payables and
@
Procurement 7-22 r
ga this S
a
Manage Invoice Options 7-23
w se
s h
l (a e to u
Change First Open Period for Payables 7-24
a
Invoice Entry 7-25
g arw cens
Matching 7-29
ry aA li
Match in Full 7-30
w a Discount 7-31
A s h Early Payment Discounts 7-32
Prepayment 7-33
Approval 7-34
Disable the Deletion of Attachments for Validated or Approved Invoices 7-35
Interest 7-36
Payment Request 7-37
One Time Payments 7-38
Self-Service Invoices 7-39
Practice 7-4 Overview: Managing Invoice Options 7-40
Manage Payment Options 7-41
Practice 7-5 Overview: Managing Payment Options 7-43
Optional Tasks to Configure Payables 7-44
Define Automated Invoice Processing Configuration 7-45
Manage Payables Calendars 7-46
Manage Tax Reporting and Withholding Tax Options 7-47
viii
Income Tax Reporting Options 7-48
Withholding Tax Options 7-49
Manage Payables Lookups 7-50
Manage Payables Descriptive Flexfields 7-51
Manage Payables Document Sequences 7-53

Manage Distribution Sets 7-55
Practice 7-6 Overview: Managing Distribution Sets 7-56
Manage Invoice Tolerances 7-57
Manage Invoice Holds and Releases 7-59
Manage Aging Periods 7-60
Define Payables Tax and Withholding 7-61
ble
Manage Tax Regions 7-62
fe r a
Manage Reporting Entities 7-63
ans
Additional Withholding Tax Setups 7-64
n - t r
Manage Interest Rates 7-65 no
a
has eฺ
Manage Bank Charges 7-66
Summary 7-67 )
ฺ c om uid
ฺ i b m nt G
8 Configuring Oracle Tax
@ in tude
Objectives 8-2 r
ga this S
Understanding Oracle Tax a8-3
s h w8-4 se
Oracle Tax Architecture
Key Building a
Blocks
u
l (a ofeTaxtoConfiguration 8-6
r w n s
A ga Tax
Foundation
l i c eConfiguration 8-7
aryaTasks to Configure Oracle Tax 8-8

s h w Tax Foundation Setup Examples 8-9
A Setting Up Foundation Tax Components 8-10
Configuration Owners and Options 8-11
Tax Regimes 8-12
Defining Defaults 8-13
General Controls 8-14
Compounding Level Controls 8-15
Configuration Options and Service Subscriptions 8-16
Taxes 8-17
Tax Rule Defaults: Place of Supply 8-18
Tax Statuses 8-19
Tax Jurisdictions 8-20
Tax Rates 8-21
Setting Up Tax Rates Overview 8-22
Override of Tax Rates on Tax Lines 8-24
Other Controls and Defaults 8-25
ix
Tax Recovery Rates 8-26
Service Subscriptions in the Cloud: Vertex 8-27
Practice 8-1 Overview: Creating a US Tax Regime and US Tax for Vertex
Integration 8-28
Define Taxes for Rapid Implementation Task List 8-29

Rapid Implementation Spreadsheets 8-30
Tax Configuration Workbooks 8-31
Tax Setup Spreadsheets 8-32
Tax Determination Process: How Taxes are Calculated 8-33
Setting Up Tax Reporting Configuration 8-34
Setting Up Global Tax Reporting 8-35
ble
Reporting and Analysis 8-36
fe r a
The Tax Simulator 8-37
ans
-
Practice 8-2 Overview: Assigning Your Business Unit to a Tax Regime 8-38
n t r
n o
Outsource Tax Processing and Reporting to Third-Party Tax Vendor Solution 8-39
a
has eฺ
Transaction Tax Management Solutions Key Benefits 8-40
Summary 8-42 )
ฺ c om uid
ฺ i b m nt G
9 Suppliers
@ in tude
Objectives 9-2
a r s S
Suppliers Overview 9-3 ag h i
h t
w seMaintenance
Data Roles for Supplier
( a s u
Setup and 9-4
al se Model
The Trading Community t o 9-5
r w
A gaModel
Supplier
l i c e9-6n
aryaProfile Tab 9-7
s h w Supplier Business Relationship Status 9-8
A Addresses Tab 9-9
Sites Tab 9-10
Invoicing 9-11
Payments 9-13
Site Assignments 9-14
Contacts Tab 9-15
Practice 9-1 Overview: Creating a Supplier 9-16
Summary 9-17
10 Payables Invoices
Objectives 10-2
Procure-to-Pay 10-3
Invoices Overview 10-4
Invoice Processing Overview 10-5
Invoice Routing for Account Coding 10-7
x
Payables Workflow Transaction Listing Report 10-9
Invoice Types 10-10
Invoice Components 10-11
Invoice Validation 10-12
Invoice Approval Flow 10-13

Line Level Approvals 10-14
Predefined Rules 10-15
Workflow Transaction Console 10-16
Practice 10-1 Overview: Opening General Ledger and Payables Periods 10-17
Practice 10-2 Overview: Creating a Manual Invoice 10-18
Practice 10-3 Overview: Creating an Invoice from Spreadsheet 10-19
ble
Configurable Payables Workflow Notifications 10-20
fe r a
Configurable Payables Workflow Notifications Process 10-21
ans
Email Components 10-22
n - t r
Adding a Branding Logo and Modifying Shared Components 10-23 n o
a
has eฺ
Configurable Payables Workflow Notifications Implementation Best Practices 10-24
Enabling Payables Workflow Notifications 10-25 )
ฺ c om uid
Configuration Prohibit Users Self Approval Section 10-27
ฺ i b m nt G
in tude
Using Quick Parts for Workflow Notifications 10-28
@
Summary 10-29 r
ga this S
a
wSubledger
11 Configuring and Using
a s h u s e Accounting
a
Objectives 11-2 l ( e to
w ns
r eAccounting
aSubledger
A g
Oracle
l i c Overview 11-3
aThe Create Accounting Process 11-4
w ary Accounting Methods Overview 11-5
A s h Predefined Accounting Methods 11-7
Accounting Event Model Example 11-8
Payables Accounting Event Model 11-9
Managing Accounting Methods and Rules Flow 11-11
How the Different Types of Rules Fit Together 11-12
Custom Formulas Overview 11-13
Managing Custom Formulas 11-14
Formula Definition 11-15
Predefined Formula Functions 11-16
Multiperiod Accounting – Deferred Expenses 11-19
Multiperiod Accounting 11-20
Implementation Steps 11-21
Multiperiod Accounting Example: Annual Rent Paid in Single Installment 11-22
Using Multiperiod Subledger Accounting Rules 11-23
Sample Custom Formula 11-24
xi
Prerequisites 11-25
The Create Multiperiod Accounting Execution Report 11-26
Mapping Sets Overview 11-27
Creating Mapping Sets 11-28
Account Rules Overview 11-29

Rule Types 11-30
Value Types 11-31
Account Rules Best Practices 11-32
Conditions 11-33
Practice 11-1 Overview: Creating Three Account Rules 11-35
Description Rules 11-36
ble
Practice 11-2 Overview: Creating a Description Rule 11-37
fe r a
Supporting References 11-38
an s
Journal Line Rules 11-39
n - t r
n
Practice 11-3 Overview: Creating Two Journal Line Rules 11-41 o
a
has eฺ
Journal Entry Rule Sets 11-42
Creating Journal Entry Rule Sets 11-43 )
ฺ c om uid
Practice 11-4 Overview: Creating a Journal Entry Rule Set 11-45
ฺ i b m nt G
Accounting Methods 11-46
@ in tude
r
ga this S
Creating or Modifying Accounting Methods 11-47
a
Practice 11-5 Overview: Duplicating and Modifying an Accounting Method 11-48
w se
s h
l (a e to u
Migrating the Accounting Configuration 11-49
a
The Create Accounting Process 11-50
g arw cens
Practice 11-6 Overview: Submitting Create Accounting in Draft and Viewing the
ry aA li
Subledger Journal in Payables 11-52
w a Practice 11-7 Overview: Submitting Create Accounting in Final/Post 11-53
A s h Manual Features of Subledger Accounting 11-54
Advanced Features of Subledger Accounting 11-55
Subledger Accounting Profile Options 11-56
Accrual Reversals Flow 11-58
Online Accounting Messages 11-59
Accounting Lines Window 11-60
Summary 11-61
12 Configuring Oracle Payments: Payables

Objectives 12-2
Practice 12-1 Overview: Creating Banks, Branches, and Accounts 12-3
Practice 12-2 Overview: Creating a Payment Document for a Bank Account 12-4
Overview of Oracle Payments 12-5
Overview of Disbursements for Payments 12-6
The Disbursements Process 12-7
xii
Key Decision and Best Practice for Payment Processing 12-8
Key Decision and Best Practices for Payment Selection Criteria 12-9
Configuring Payment System Connectivity: Overview 12-10
Prerequisites for Configuring Payment System Connectivity 12-11
Disbursement Payment File Formats 12-12

Key Decision and Best Practices for Using Formats 12-13
Practice 12-3 Overview: Creating a Disbursement Payment File Format 12-15
Transmission Configuration Concepts 12-16
Key Decision and Best Practices for Using Transmission Protocols 12-17
Practice 12-4 Overview: Creating the Transmission Configuration 12-18
Managing Payment Systems 12-19
ble
Practice 12-5 Overview: Creating a Payment System 12-20
fe r a
Defining Disbursements 12-21
ans
Prerequisites for Defining Disbursements 12-22
n - t r
Disbursement Payment Methods 12-23 n o
a
has eฺ
Creating Usage Rules for Payment Methods 12-24
Using Validations 12-25 )
ฺ c om uid
Creating or Assigning Validations to Payment Methods 12-27
ฺ i b m nt G
in tude
Creating User-Defined Validations 12-28
@
r
ga this S
Manage Payment Method Defaulting Rules 12-29
a
Practice 12-6 Overview: Creating a Payment Method 12-30
w se
s h
l (a e to u
Manage Payment Codes 12-31
a
Manage Payment Process Profiles 12-32
g arw cens
Prerequisites for Defining Payment Process Profiles 12-33
ry aA li
Payment Process Profile Concepts 12-34
w a Creating a Payment Process Profile 12-35
A s h Usage Rules Tab 12-36
Payment System Tab 12-37
Payment Tab 12-38
Payment File Tab 12-39
Grouping Tab 12-42
Reporting Tab 12-43
Managing Disbursement System Options 12-44
Practice 12-7 Overview: Creating a Payment Process Profile 12-45
Payment Document and Reference Numbers 12-46
Payment Process Requests 12-47
Selection Criteria Tab 12-48
Payment and Processing Options Tab 12-50
Streamlined Payment Processing 12-52
Positive Pay File Additional features 12-53
xiii
Update Payment Requests when Creating or Ending Employee
Bank Account 12-54
Practice 12-8 Overview: Submitting a Payment Process Request 12-55
Payment Approval: Overview 12-56
Implementation Overview: Setups 12-57

Feature Impact Guidelines 12-58
Enabling Payment Approval 12-59
Configuring Payment Approval Rules 12-60
Payment Approval Rules: Example 12-61
Initiating Approval for Payment Process Requests 12-62
Payment Approval Worklist Notifications 12-63
ble
Removing Payments During the Approval Process 12-65
fe r a
Withdrawing an Approval or Terminating the Payment Process 12-66
ans
Customer and Supplier Balance Netting Overview 12-67
n - t r
n
Customer and Supplier Balance Netting Settlement Features 12-68 o
a
has eฺ
Generate Netting Settlements 12-69
)
Customer and Supplier Balance Netting: Manage Netting Settlements in a
Spreadsheet 12-70 ฺ c om uid
ฺ i b m nt G
in tude
Importing Netting Agreements 12-71
@
r
ga this S
Customer and Supplier Balance Netting Example 12-72
a
Netting Features Specific Setups 12-73
w se
s h
l (a e to u
Netting Agreement Setup Options 12-77
a
Netting Agreements Setup 12-79
g arw cens
Summary 12-80
aA li
w ar13y Configuring Oracle Cash Management
A sh Objectives 13-2
Cash Management: Overview 13-3
Set Up and Maintain Banks, Branches, and Bank Accounts 13-4
Manage and Maintain Banks 13-5
Manage and Maintain Branches 13-6
Manage and Maintain Bank Accounts 13-7
General Tab 13-8
Payment Documents 13-9
Control Tab 13-10
Security Tab 13-12
Business Unit Access Tab 13-13
Configuring Cash Management Rapid Implementation 13-14
Bank Statement Processing Overview 13-15
Key Setup Tasks for Bank Statement Processing 13-16
Manage Cash Transaction Type Mapping 13-17
xiv
Cash Management Setups for Automatic Reconciliation Overview 13-18
Bank Statement Transaction Codes 13-19
Practice 13-1 Overview: Managing Bank Statement Transaction Codes 13-21
Payment Code Map Groups 13-22
Code Map Group Example 13-23

Bank Statement Formats 13-24
Parse Rule Sets 13-25
Parse Rule Set Example 13-26
Bank Statement Transaction Creation Rules 13-28
Practice 13-2 Overview: Managing Bank Statement Transaction Creation
Rules 13-29
ble
Bank Statement Reconciliation Setups 13-30
fe r a
Bank Statement Reconciliation Tolerance Rules 13-31
ans
- t
Practice 13-3 Overview: Managing Bank Statement Reconciliation Tolerance
n r
Rules 13-33 n o
a
has eฺ
Bank Statement Reconciliation Matching Rules 13-34
)
Practice 13-4 Overview: Managing Bank Statement Reconciliation Matching
Rules 13-36 ฺ c om uid
ฺ i b m nt G
in tude
Reconciliation Rule Sets 13-37
@
r
ga this S
Practice 13-5 Overview: Managing Bank Statement Reconciliation Rule Sets 13-38
a
Practice 13-6 Overview: Assigning a Rule Set to a Bank Account 13-39
w se
s h
l (a e to u
Defining Subledger Accounting Rules: Cash Management Accounting
a
Event Model 13-40
g arw cens
Performing Bank Statement Reconciliation 13-41
ry aA li
Practice 13-7 Overview: Performing a Bank Statement Reconciliation with
w a Autoreconciliation 13-42
A s h Reporting and Analysis 13-43
Cash Management Infolets Overview 13-44
Cash Management Infolets 13-45
Cash Positioning and Forecasting: Cash Balances 13-46
Cash Position Page 13-47
5 Day Forecast Page 13-48
Transactions Cube 13-49
Ready to Use Smart View Templates 13-50
Manual Transactions 13-51
Bank Account Transfers 13-52
Ad Hoc Payments 13-54
Setup Options in Payments 13-55
xv
Intraday Bank Statement Support 13-56
External Transactions Overview 13-57
Reconciling Journal Lines For Multiple Cash Account Combinations 13-58
Summary 13-60
14 Reporting for Payables, Payments, and Subledger Accounting

Objectives 14-2
Predefined Reports 14-3
Payables 14-4
Payables BI Publisher Reports 14-5
Payables Oracle Transactional BI Reports 14-14
ble
Payables Subject Areas 14-19
fe r a
Report on Active and Inactive Requestors in Payables Subject Areas 14-22
ans
Cross-Functional Reporting Between Payables and Projects 14-23
n - t r
n
Payables to Ledger Reconciliation Drill-down Scalability 14-24 o
a
has eฺ
Payables to Ledger Reconciliation Report 14-25
)
Practice 14-1 Overview: Running a Payables Analysis Report 14-26
ฺ c om uid
Scanned Infotile for Payables Manager and Specialist 14-27
ฺ i b m nt G
Recent Infotile 14-28
@ in tude
Holds Infotile 14-29 r
ga this S
a
Approval Infotile 14-30
w se
s h
l (a e to u
Prepayments and Payments Infotile 14-31
a
Payments 14-33
g arw cens
Run Payments Disbursement Reports Automatically 14-34
ry aA li
Run Payments Disbursement Reports Manually 14-38
w a Payments Funds Capture Reports 14-39
A s h Run Payments Funds Capture Reports Automatically 14-40
Run Payments Funds Capture Reports Manually 14-44
Payments Subject Areas 14-45
Subledger Accounting 14-46
Subledger Accounting Predefined Reports Overview 14-47
Subledger Accounting BI Publisher Reports 14-48
Subledger Accounting Subject Areas 14-51
Practice 14-2 Overview: Running a Subledger Accounting BI Publisher
Report 14-52
Summary 14-53
A Common Application Topics

Objectives A-2
Manage Oracle Social Network Objects A-3
Enablement Options A-4
xvi
Update Social Network Translations A-6
Update Translations A-7
Demonstration A-1: Managing Oracle Social Network Objects A-8
Oracle Social Network Reference Resources A-9
Define Flexfields A-10

Manage Flexfields A-11
Types of Flexfields: Descriptive A-12
Flexfield Concepts A-13
Flexfield Segments A-14
Flexfield Structure A-15
Flexfield Context A-16
ble
Flexfield Category A-17
fe r a
Flexfield Usage A-18
ans
Accessing Flexfields for Configuration A-19
n - t r
Using the Highlight Flexfields Command A-20 n o
a
has eฺ
Accessing Flexfield Management Tasks and Searching for Flexfields A-21
Value Sets A-23 )
Value Set Validation A-25 ฺ c om uid
ฺ i b m nt G
Value Set Usage A-26
@ in tude
r
ga this S
Descriptive Flexfields A-27
a
Descriptive Flexfields: Segments A-28
w se
s h
l (a e to u
Descriptive Flexfields: Context Segment A-29
a
Descriptive Flexfields A-30
g arw cens
Adding Flexfield Segments on Application Pages A-31
ry aA li
Extensible Flexfields A-35
w a Extensible Flexfields Context A-37
A s h Extensible Flexfields A-38
Extensible Flexfield Example A-39
Key Flexfields A-43
Key Flexfield Structure A-45
Key Flexfield Instances A-46
Key Flexfields A-47
Tips for Managing Key Flexfields A-49
Flexfield Implementation Flow A-51
Flexfield Reference Resources A-53
Define Lookups A-54
Sample Lookup Type A-55
Lookup Components A-56
Lookup Categories A-57
Manage Lookups A-58
Customize Lookups A-59
xvii
Define Profile Options A-60
Profile Options A-62
Profile Option Categories A-63
Profile Option Levels A-64
Profile Option Values A-65

Profile Options for Common Setup A-66
Quiz A-67
Define Attachments A-68
Key Concepts A-70
Manage Attachment Entities A-72
Manage Attachment Categories A-73
ble
Attachment Category Security A-75
fe r a
Example A-77
ans
Solution A-78
n - t r
Quiz A-79
a no
has eฺ
Summary A-81
)
B Integration Services in Payables ฺ c om uid
ฺ i b m nt G
Objectives B-2
SOAP Business Object Services r@
in tude
a B-3
gPayables i s S
REST APIs Web Services fora h
t Invoices B-5
wfor Supplier B-4
s
REST APIs Web Services h s e
u Details B-6
a
Individual REST
(a WebtoServices
l APIs
RESTgAPIs e nsePayee, External Bank Account and Payment Instrument
arwforcExternal
A li
arya Assignment B-9
s h w Payables: REST APIs for Payments B-10
A Payables: REST API Services for Supplier Invoices B-11
Payables Invoices in the Universal Business Language 2.1 XML Format B-12
Setting Up a Supplier for UBL 2.1 XML B-13
Summary B-15
C Localizations
Objectives C-2
Exporting Enterprise Financial Data for China C-3
The Export Payables and Receivables Data for China: Enterprise Process C-4
Details Exported C-5
Payables Details and Descriptions C-6
EMEA Reports for Payables C-10
Reports for France C-11
Reports for Italy C-13
VAT Reports for Italy C-14
xviii
Italy: Include Taxable Journals and Transactions in Tax Registers for Italy C-16
Intra-EU Report for Italy C-17
Exemption Reports for Italy C-18
Withholding Tax Reports for Italy C-19
Reports for Spain C-20

Online VAT Reporting for Spain C-21
Investment Register C-22
VAT Reports for Spain C-23
Modelo Reports for Spain C-24
Withholding Tax Reports for Spain C-25
Reports for Germany C-26
ble
Correction Documents for Poland C-27
fe r a
Jednolity Plik Kontrolny (JPK) Reporting for Poland C-28
ans
Print Commercial Documents for Poland C-29
n - t r
Tax Point Date Adjustment Feature in Payables C-30n o
a
has eฺ
Israel: Generate VAT File in 835 Format C-31
)
Norway: Generate Data Extract for Norway SAF-T C-32
APAC Reporting C-33 ฺ c om uid
ฺ i b m nt G
Report for China C-34
@ in tude
r
ga this S
Report for Japan C-35
a
Report for Singapore C-36
w se
s h
l (a e to u
Thailand Withholding Tax Certificate Report and Sequence Numbering C-37
a
Report for India: Export Letter of Undertaking and Under Rebate for India C-38
g arw cens
Payables Extension to Support Generation of Tax Invoice Number for India Reverse
ry aA li
Charge Invoices C-39
w a India: Copy Tax Compliance Attributes to Payables Invoices for India C-40
A s h India: Default First-Party Tax Registration Number for India C-41
Associating the Legal Reporting Unit C-42
Deferred Tax Recovery for India C-43
Using Deferred Tax Recovery for India C-44
Integrate with E-Way Bill Framework for India C-45
Enabling Electronic Filing of GST Annexure-1 Per Revised GST Reporting Structure
for India C-46
Running the Report Tax Liability Electronically for the India Output Tax C-47
Generate Customer Balance Reconciliation Report for Russia C-49
Generate Receivables and Payables Audit Report for Russia C-50
Generate VAT Reports for Russia C-51
Prepare VAT on Export Report for Russia C-52
Russia Asset Reporting for Asset Repair and Maintenance C-53
Tax Agent Invoice for Russia C-54
LAD Reporting C-55
xix
Report for Mexico C-56
Withholding Tax Reporting for Argentina C-57
Argentina: Generate Withholding Certificate Number and Capture Additional
Attributes C-58
Argentina: Enable 2018 Legislative Updates for Document Sequencing for

Argentina C-60
Withholding Tax Reporting for Chile C-62
Withholding Tax Reporting for Colombia C-63
Summary C-64
D Additional Resources
ble
Lesson Objectives D-2
fe r a
Oracle Cloud Implementation Resources D-3
ans
Oracle Help Center: docs.oracle.com D-5
n - t r
Cloud Application Services Pages D-6 n o
a
has eฺ
Financials Home Page D-7
)
Video Subject Areas on the Oracle Help Center D-8
Reference Guides D-9 ฺ c om uid
ฺ i b m nt G
Friendly Search D-10
@ in tude
Summary D-11 r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h
xx
12
Configuring Oracle Payments: Payables

ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
Copyright © 2019, Oracle and/or its affiliates. All rights reserved.
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h
Objectives
After completing this lesson, you should be able to:

• Set up a bank account.
• Manage payment system connectivity.
• Manage payment methods.

• Define payment method defaulting rules.
• Define payment codes.
• Understand payment process profiles.
• Explain disbursement system options.
• ble
Understand and submit a payment process request.
fe r a
• Manage Payments Approvals.
an s
• Understand Customer and Supplier Balance Netting. n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h
Oracle Financials Cloud: Payables to Cash Management Implementation 12 - 2

Practice 12-1 Overview: Creating Banks, Branches, and
Accounts
This practice covers the following topics:
In this practice, you will be creating a bank, a branch, and bank account.
Note: This practice is needed to run a payment process request. This course covers this
setup in another lesson.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Practice 12-2 Overview: Creating a Payment Document for a
Bank Account
• Creating a Payment Document for a Bank Account.
• Assigning a payment format.
Note: This practice is needed to run a payment process request. This course covers this
setup in another lesson.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Overview of Oracle Payments
Payments is an Oracle Cloud Application that serves as a disbursement and funds capture
engine for other Oracle Cloud Applications.
As the central payment engine, Payments:
• Processes invoice payments from Oracle Payables.

• Settles receipts in Oracle Receivables against credit cards and bank account transfers.
• Connects with external organizations like payment systems and financial institutions for
processing.
• Enables you to centralize the payment process across business units, currencies, and
geographical regions.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Overview of Disbursements for Payments
• The Payments disbursements process includes selected disbursement setups of

Payments. Disbursements is the process of paying funds owed by your company to
creditors, such as suppliers who have provided goods or services.
• A payment can take:

– An electronic form, such as EFT.
– A printed form, such as a check.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

The Disbursements Process
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
The disbursements process flow is as follows:
@ in tude
• Invoices are entered. r
ga this S
A payment method h is w
a
selected e
-
a s u s or provided on the invoice.
-
a
The invoice is l (validated.
e to
• w
r efornspayment as a payment process request.
Invoices areaselected
g ic payments and validations are applied.
Aare built linto
• a
Invoices
ry
• waPayments are built into payment files and validations are applied.
A sh - Bank instructions are added to the payment files.
• Payment files are formatted.
• If the payment files are printed, they are sent to a printer.
• If the payment files are electronic, they are transmitted to a payment system or bank.
• Various reports can be generated for payments transmitted electronically, such as:
- Separate remittance advice
- Payment File Register

Key Decision and Best Practice for Payment Processing
• Key Decision: How much of the payment process should I automate?

• Best Practice: Any combination of manual and automated steps can be used.
– Payments should not be completely automated or completely manual.
– The best practice is to automate everything and use quick payment for urgent
payments.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Advantages of straight through processing:
@ in tude
• Fewer touch points require less effort. r
ga this S
a
w the payment
• h
Exceptions are handled outside
the few exceptions. l (a
s u se process, whereas good payments are not held up by
w a e to
Advantages of tighta
g r control:
manual
c e ns
• EnablesAmanual review
li and confirmation of payments in process.
r y a
• aEnables steps to be manually initiated to accommodate specific timing needs.
s h w
A

Key Decision and Best Practices for Payment Selection Criteria
Key Decision: What invoice selection criteria should I use?

Broad invoice selection criteria:
• Creates as few payment process requests as possible.
• Recommended for a Centralized or Service Provider Processing model.

• Payment process templates can be fewer and more generic.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Payments can then derive the payment process profile
@ t de per payment, instead of forcing all
in automatically
u
r
ga tthe
payments in a payment process request to have
s S payment process profile.
same
a
w se h i
s h
a l (a e to u
g arw cens
r y aA li
w a
As h

Configuring Payment System Connectivity: Overview
The three main components are:

• Disbursement payment file formats.
• Transmission configurations.
• Payment systems.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
inpay file,
Successful transmission of a payment file, a positive
@ t u doreother type of content, requires coordination
r
ga thiThe
between sender (outbound) and receiver (inbound). Ssender must format the message according to a
sit and
w a
payment system so that the receiver can understand process it correctly.
h
as to us e
l (
a r wa nse
a Ag lice
w ary
Ash

Prerequisites for Configuring Payment System Connectivity
You must define the following in the Setup and Maintenance work area within the Financials
offering:
• Legal entities.
• Business units.
• Internal (disbursement) bank accounts.
• Oracle BI Publisher templates.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
n tudtask e list, see the lesson titled “Overview of
For information about the Define Legal Entities for iFinancials
Common Applications Configuration” in thisa r @
course. S
a g h i s
t list, see the lesson titled “Configuring Business Units
s h w Units
For information about the Define Business
s e task
l (a course.
and Reference Data Sets” in this
t o u
a e
Cash Management.” g a w ceupnsdisbursement
For information aboutrsetting banks accounts, see the lesson titled “Configuring Oracle
r y a Aabout setting
li
w a
For information up Oracle BI Publisher templates, visit:
Ash
http://docs.oracle.com/cd/E25054_01/bi.1111/e13881/toc.htm.

Disbursement Payment File Formats
• Banks, payment systems, and countries have electronic formatting requirements for
payment files and settlement batches.
• Each format in Payments is attached to one Oracle BI Publisher template.
• Each format creates an outbound message.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ
m nt Gc
ฺ i b e format is data file on which an Oracle
The outbound message created by the disbursement
@ in payment
t u dfile
r
a mustimeet
Business Intelligence Publisher (Oracle BI Publisher)
gand s S is used. The template contains prescribed
template
w
formatting attributes such as data location a t h the requirements of financial institutions and
countries. Formats enable payment
a s h u
systems s e
or financial institutions to understand transactional messages.
A format is applied to the a
( o
l in aedatat extract and the result is a formatted file, such as a payment file,
r w data
aother output.nsValidations can be associated with formats and are used to ensure valid
transaction a A
data.
g
positive pay file, or
li c e
r y
aup Oracle BI Publisher templates, see the guide titled Oracle Cloud Middleware Report Designer's
w
To set
h
AsGuide for Oracle Business Intelligence Publisher, which you can view at

Key Decision and Best Practices for Using Formats
• Key Decision: What formats should I use?

• Best Practice: Determine which payment formats your payment system or financial
institution supports.
• Consider standards-based payment formats that can be used with multiple banks:
– EDIFACT formats, such as PAYMUL, MT100, and MT103
– NACHA formats, such as Generic, CCD, PPD
– ISO20020 format
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Key Decision and Best Practices for Using Formats
Key Decision: How do I modify templates?

Best Practice: Modify predefined payment formats using
Oracle BI Publisher.
• An XML extract provides Payments data.

• Use .rtf templates to create or modify layouts for checks and reports.
– Download .rtf files from Oracle BI Publisher and save locally.
– Modify the template.
– Upload the modified template using the Oracle BI Publisher under user-defined
report.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
For a detailed discussion of tailoring formats to your
@ deWorking with Payments Formats: Article ID
inneeds,tusee
r
ga this S
1413989.1 on Oracle Support (http://oracle.support.com).
a
w se
s h
a l (a e to u
g arw cens
r y aA li
w a
As h

Practice 12-3 Overview: Creating a Disbursement Payment
File Format
This practice covers creating a Disbursement Payment File Format.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Transmission Configuration Concepts
The following concepts apply to payments transmission:

• Transmission Protocol
• Transmission Configuration
• Tunneling Configuration
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ
m nt Gc
ฺ i b
in tsystem
If your company wants to transmit payments to a payment
@ u de or bank, you must set up transmission
configurations. Transmission values tell thea
g r
system howS
s to transmit a message.
• a
w thesmethod h i
t of transmission. Examples include File Transfer
h
Transmission Protocol: Defines
s e
Protocol and HTTP Put.
a l (a to u
• Transmission w
ar ceand e Transmission details such as FTP Server IP Address, Account User
nsremote
Configuration:
Name andgPassword, directory which must be associated with one transmission
a A l i
ry
protocol.
• waTunneling Configuration: A type of transmission configuration that helps transmit data through a
Ash transmission servlet that can securely connect to your payment system without exposing internal
data.

Key Decision and Best Practices for Using Transmission Protocols
Key Decision: Which transmission protocols should I use for payment processing?
Best Practice:
• Find out what your payment system or financial institution supports.
• Favor transmission protocols that are predefined in Payments.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Practice 12-4 Overview: Creating the Transmission Configuration

• Selecting the Protocol for the Transmission Configuration.
• Creating the Transmission Configuration.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Managing Payment Systems
The purpose of setting up payment systems is to process and transmit payment files.
You must include the following:
• Processing model
• Bank name
• Transmission servlet base URL
• Disbursement type
• Disbursement payment file format
• Transmission protocol
• ble
Payment system account
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
If your company needs to transmit electronic disbursement
@ de to financial institutions, you must set
in tupayments
up a payment system. The set ups include: a
g r s S
• a
w are:se t h i
s h
Processing Model: The choices
a provider u that interacts directly with banks.
- Processor: A
a l (service t o
-
a rw A service
Gateway:
g e n seprovider that acts as an intermediary between your company and a
a A l ic
payment processor.
ry Name: The name of the financial institution that receives the electronic payment instruction.
• aBank
w
Ash• Transmission Servlet Base URL: The URL used for the transmission.
• Disbursement Type: Select electronic funds transfer and positive pay.
• Disbursement Payment File Format: The file format previously defined in this lesson.
• Transmission Protocol: The protocol previously defined in this lesson.
• Payment System Account: Used to capture your relationship with the financial institution. It
captures specific identification information required by your bank in payment messages. For
example, the financial institution may require a submitter ID and submitter password to be included
in any message You must set up these values to avoid payment file rejections by your bank.

Practice 12-5 Overview: Creating a Payment System

• Creating a payment system.
• Creating a payment system account.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Defining Disbursements
The Define Disbursements activity enables implementers to configure the disbursement of

funds, such as:
• Managing payment methods.
• Managing payment method defaulting rules.

• Managing payment codes.
• Managing payment process profiles.
• Managing disbursement system options.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Prerequisites for Defining Disbursements
Define the following prerequisites in the Setup and Maintenance work area within the
Financials offering:
• Define legal entities.
• Define business units.

• Define internal bank accounts of the deploying company.
• Define payment system.
• Define formats.
• Define transmission configuration.
• Set up Oracle Business Intelligence Publisher templates. ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
n tudtask e list, see the lesson titled “Overview of
For information about the Define Legal Entities for iFinancials
Common Applications Configuration” in thisa r @
course. S
a g h i s
t list, see the lesson titled “Configuring Business Units,
s h w Units
For information about the Define Business
s e task
a l (a to u
Reference Data Sets” in this course.
a w Set
For information aboutrthe e Branches, and Accounts task list, see the lesson titled “Configuring
UpsBanks,
n
A g
Oracle Cash Management”
l ic e
in Oracle Financials Cloud: Financials Implementation, Part II.
To definery
a
payment systems, see the section titled “Setting Up Payment Systems” in this lesson. You have
w acompleted
A s h
already this setup.
To define formats, see the section titled “Setting Up Formats” in this lesson. You have already completed
this setup.
To define transmission configurations, see the section titled “Setting Up Transmission Configurations” in this
lesson. You have already completed this setup.
To set up Oracle Business Intelligence Publisher templates, see the guide titled Oracle Cloud Middleware
Report Designer's Guide for Oracle Business Intelligence Publisher, which you can view at

Disbursement Payment Methods
• Setting up disbursement payment methods is optional because Payments predefines

many payment methods.
A disbursement payment method is a method of payment that your company uses to pay a
supplier, customer, or employee.

The payment method can be:
• Electronic, such as EFT or wire.
• Printed, such as a check.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
in tuMethods:
Payments predefines the following Disbursement Payment
@ de
• Check r
ga this S
a
w se
• Electronic
s h
a to u
• Electronic – SEPA l (
a se
• Outsourcedarw n
g ic e
• Wirea A l
Thew ary of creating disbursement payment methods is to define granular usage rules to limit the use of
purpose
h
Asdisbursement payment methods to specific business units, legal entities, and other attributes and to assign
validations for validating the invoices, payments, and payment files.
The level of granularity that you need for your disbursement payment methods is a factor to consider before
you define them.
The least granular payment methods are the predefined payment methods. With this approach, you can
associate each payment method with many payment process profiles and payment formats. This approach
requires less knowledge from source product users, such as invoice entry clerks, but may involve more work
later in the payment process.
Alternatively, you can define more granular payment methods. An example of a very granular payment
method is Italian EFT, to which you might add a validation that is specific to Italy. With a more granular
setup, validations are run early during invoice entry and errors can be fixed more quickly.

Creating Usage Rules for Payment Methods
Usage rules specify when a disbursement payment method is available for use.
You can limit the use of a payment method based on the following transaction conditions:
• Business Units
• Legal Entities
• Payment Process Transaction Types
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
in tprocess
By default, payment methods are available on all payment
@ u de transactions.
a
Usage rules specify when a disbursementgpayment
r s S is available for use by source products on
a h i
method
w rules,seyout enable or disable payment methods for each source
documents payable. By creating usage
s h
product integrated with Oracle(a
and change whether and a l Payments.
t o uYoumethod
theepayment
can provide different usage rules for different source products
a r w ns
when is available.
A
In the Usage Rulesg tab onlictheeCreate Payment Method page, you decide whether to assign the payment
a
method toyone of the following:
w aAllr payees.
Ash• Specific business units, legal entities, and payment process transaction types for Oracle Payables.
•
• Specific business units, legal entities, and payment process transaction types for Oracle
Receivables.
• Specific payment process transaction types for Oracle Cash Management.

Using Validations
• Validations are rules that ensure that transactions are valid before they are printed or
submitted electronically to payment systems. Validations ensure that disbursement
transactions, such as invoices, payments, and payment files, meet specific conditions
before they can be paid.

• You can assign validations to:
– Payment methods.
– Payment formats.
• A validation can be performed at the invoice level, payment level, or payment file level.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ
m nt Gc
ฺ i b
In payment processing, ensure that payment files sent
@ in to payment
t u de systems and financial institutions are
r
ga the
valid and correctly formatted. If this is not done, payment
s S process is slowed, which results in additional
time and cost due to problem resolution.aOracle
w t h i
Payments helps you achieve straight-through processing by
ensuring that payment-related details h
as to usare e
valid.
l (
a as early
Payments always validates
a r wpayment n s eas possible for a given object and setup. Document payable validations
A g validation
that are associated with
l i c efailures to be handled by the
methods are enforced earlier in the process than those associated with
r y a
formats. If you want same person who is entering the invoice, you
a the validation with the payment method. This is ideal for business processes in which each
can associate
w
h
Asfailures are handled centrally by a specialist or a more knowledgeable user, you can associate the validation
person has full ownership of the items entered. However, if you want focused invoice entry while validation
with the format.

Using Validations
This table shows the objects you can validate and when validations are performed for the
applicable setup.
Object Payment Method–Driven Payment File Format–Driven

Validations are Enforced Validations are Enforced
When… When…
The invoice is saved in the source The invoice installment is selected
Document Payable
product. for payment.
The payment is created by building The payment is created by building
Payment
related documents payable together. related documents payable together.
Payment File Not applicable. The payment is created.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
n tutodensure e that you catch errors before they are
Add comprehensive validations for any transactioniattribute
sent to the bank. a r @ S
a g h i s
t when formats or regulations change.
•
s h w validations
Layer them on top of predefined
s e
• Use them to create entirely u
l (a enewtovalidations for your own formats.
a
w a payment
g arwith
Associate validations
c e ns method so that documents payable are validated during invoice entry.
•
a Aimmediate
Provides
r y li feedback.
• aResolves errors and makes payments quickly.
s h w
A • Requires knowledgeable invoice entry personnel.
• Requires a larger number of payment methods with different, associated validations.
Validate after the payment process request submission if the validation is associated with a format.
• Enables a specialized payment process manager to resolve errors.
• Enables fewer payment methods.
• Requires less knowledgeable invoice entry personnel.

Creating or Assigning Validations to Payment Methods
Validations can be associated with a payment method. They catch errors during data entry
on documents payable. When creating a disbursement payment method in Payments, you
create or assign validations on the Validations tab of the Create Payment Method page.
You can:
• Select from a library of predefined validations.
• Create user-defined validations for this payment method.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
in Youtcan
Payments provides a library of predefined validations.
@ u deassociate these predefined validations with
any payment method or payment file formata r
you create. S
Predefined validations are groups of w a g t h is that work together for a specific purpose. Many of
individualevalidations
a sh us
the predefined validations are(country-specific.
w a e to although some have parameters you can set to define specific
l validations,
ar cens
You cannot modify predefined
g
aA li
values.
a r y
h w
As

Creating User-Defined Validations
User-defined validations are basic validations that correspond to simple operations. They
can be used as components to build more complex validations.
A user-defined validation specifies the object to which the validation applies:
• Document payable
• Payment
• Payment file
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
For example, user-defined validations enable you to
@ invalidatet u defollowing conditions:
the
• Length of a value: Payment Detail g r
amust be ifewer
s S than 60 characters for your bank-specific payment
a
w se t h
file format.
s h u bank account is required when payment method is
• l (a toRemit-to
Whether a field is populated:
a
Electronic.
g a rw ense
• Whether
a Acontentliofc a field is allowed: Currency must be USD when using your domestic payment
w ary
file form.
Ash

Manage Payment Method Defaulting Rules
A payment method defaulting rule determines which payment method needs to be defaulted
on Payables invoices. Defaulting rules have:
• Priorities
• Defaulting conditions
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
in rules
Oracle Payments applies the payment method defaulting
@ t u dinethe prioritized order you specify based on
the defined conditions.
g a r s S
a
w se t h i
The conditions include:
s h
• Business Units
a l (a e to u
• arwEntities
First Party Legal
g c e ns
•
a AProcessliTransaction Types
Payment
r y
• aCurrency
s h w
A • Payee Location
If the first rule is a match, Payments provides that rule's corresponding payment method on the invoice.
Suppose you specify that the payment method for all documents processed by Payables is first, Check, and
second, EFT. If the conditions for payment method Check match the conditions on the invoice, then
payment method Check is provided on the invoice.
If the conditions for payment method Check do not match the invoice, then Payments determines whether
the conditions for payment method EFT match. If the conditions for payment method EFT match the
conditions on the invoice, then payment method EFT is provided on the invoice.
Note: If the supplier, address, or supplier site has a default payment method selected, the invoice defaults
with the supplier defined payment method.

Practice 12-6 Overview: Creating a Payment Method

• Creating a payment method.
• Creating usage rules.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Manage Payment Codes
• Payments enables you to specify payment codes that are required by financial
institutions.
• Payment codes provide details to banks or payment systems about transaction handling,
bank charges, or payment reasons.

• Payments provides many predefined types of payment codes, which include:
– Bank instruction codes.
– Delivery channel codes.
– Payment reason codes.
– Service level.
– Local instrument. ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Setting up payment codes are optional. During invoice
@ in entry, t u deuser can select an applicable payment
the
r
ga thsupplier
code or it is provided by default from the applicable
s S or supplier site. Following are the predefined
payment codes: a
w se i
• s h u
a toinstruction
Bank Instruction Codes:
l ( Bank codes are values that contain information or instructions
a r wa ntosaebank or financial institution at the payment file level.

that need to be passed
• Delivery Channel e Delivery channel codes are instructions that tell the bank how to make
Ag to theliCodes:
cpayee.
a
ry A value is provided byAdefault
the payment default delivery channel value can be set on the supplier or supplier
w a site. on the invoice in Oracle Payables.
h
As • Payment Reason Codes: Payment reason codes are generally country-specific identifiers provided
by a country's government or central bank. These codes provide the payment system or bank with
additional details about the reason for the payment for regulatory reporting purposes.
• Service Level: A service level code represents an agreement between you and the bank or financial
institution that specifies the level of payment services it provides.
• Local Instrument: A local instrument code is a payment instrument, such as credit card or bank
account, that is unique to a geographical area.

Manage Payment Process Profiles
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
A payment process profile is a required setup that is
@ inassigned
t u dtoepayment process requests. It manages
documents payable, payments, and payment rfiles duringSthe payment process. Payment process profiles
gasaspecifications
w a
include several types of information, such t h is for payment file formatting and transmission.
a s
The payment method and other invoice
u e drive the assignment of a payment process profile to each
h attributes
s
document payable, and the a (
lpayment to profile drives every subsequent step of the payment process.
process
w
arprofile e
nstogether the following setups:
g
The payment process
c e
ties
• y a A configuration
Transmission
r
li
• waPayment system
h
As • Payment system accounts
Payment process profiles also:
• Control usage of the payment process profile.
• Specify payment formatting, printing, and transmission behavior.
• Control creation of payments and payment files.
• Automate report generation.

Prerequisites for Defining Payment Process Profiles
Mandatory prerequisite setups in the Setup and Maintenance work area within the
Financials offering:
• Configure Payment System Connectivity
– Manage Formats.
– Manage Transmission Configurations.
– Manage Payment Systems.
— Set up payment system accounts.
• Define Disbursements
– Manage Payment Methods.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Payment Process Profile Concepts
The following terms are associated with Payment Process Profiles:

• Documents Payable
• Payment Process Request
• Separate Remittance Advice

• Payment
• Payment File
• Payment File Register
• Positive Pay
• ble
Regulatory Report
fe r a
• Payment Document
an s
n - t r
a no
) has eฺ
om uid
ฺ
m nt Gc
ฺ i b
• Document payable: A transaction, such asin
@ an invoice,
t u dethat is selected for payment.
• a r
Payment process request: A jobgsubmitted s S processing a batch payments.
a
wA notice h ito for
t to an external payee that lists the invoices your
• Separate remittance advice:
s h s e sent
u bank account.
a (a external
company has paid tol the
t o payee's
•
a
Payment: A transfer
g se to a supplier, customer for refunds, or employee for expense
rw eofnfunds
A
reimbursement.
a l ic
ry file: The payment file is transmitted to a bank for further processing and payment or
• aPayment
s h w printed as a check run.
A • Payment file register: An internal report for keeping a register of payments generated.
• Positive pay: A document sent by your company to its payment system or bank that lists payments
made by check.
• Payment document: Check stock with the format and serial number assigned by your disbursement
bank account.

Creating a Payment Process Profile
A Payment Process Profile includes:

• Usage Rules
• Payment System
• Payment
• Payment File
• Grouping
• Reporting
• Additional Information
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
n thetseven
A payment process profile has header information iand
@ u detabs. The header defines:
• Name and Code r
ga this S
a
w se
• Description
s h
•
a l (a e to u
From Date and To Date
• Payment File
g rw ens
aFormat
• a
Processing ic determines what type of file is be transmitted.
A Type:lThis
w ary- Electronic: A payment file is transmitted.
Ash - Printed: A positive pay file is transmitted.
• Default Payment Document (Optional)
• Payment Confirmation Point: When the payment file is formatted, When the payment file is
transmitted, or Manual confirmation only.

Usage Rules Tab
A payment process profile can be created generically for use with all payments. By creating
usage rules, you can limit the use of a payment process profile based on the following
transaction conditions:
• Payment Method
• Disbursement Bank Account
• Business Unit
• Currency
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
When you set up a payment process profile, you specify
@ de on a transaction that are compatible with
in thetuvalues
r s Scanbusiness
gabanktprofile
it. You can specify whether the payment process be used on a document payable (invoice)
w
based on its payment method, disbursementa h i
account, unit, or currency. For example, if the
a
payment format associated with thes h u
payment s e
process profile allows only a specific currency, then enter that
( o
lso that the payment process profile can be used only on documents payable
wa nse t
currency in the usage rules
r
with the appropriateacurrency.
The payment a Ag profile
process l icethat is applied to a document payable depends, in part, on the usage rules
y the Usage Rules tab of the Create Payment Process Profile page. When you submit a payment
aron
specified
w
h request, Payments compares the attributes of each transaction to the payment process profile
Asprovided
process
on the Submit Payment Process Request page. Any transactions whose attributes are in conflict
with that payment process profile's usage rules fails validation. If no payment process profile has been
selected, Payments compares the attributes of each transaction to all existing payment process profiles to
determine whether one payment process profile is available for which the usage rules are a match with the
transaction attributes. If a match does not occur, a company specific implementation or user intervention
may be needed to determine the appropriate payment process profile to use.

Payment System Tab
A payment system is:

• Required for electronic payment processing.
• Optional for printed payment processing.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ
m nt Gc
ฺ i b
If the payment process profile is used for electronicin
@ u de
payment processing,
t you select a payment system and
r
a also iselect
enter details that enable the application to electronically
gcan s Stransmit files to that payment system within the
context of a payment system account. You
w a t h Automatically transmit payment file after
h
as to us
formatting to facilitate straight through e
processing.
l (
a is used
a r w
If the payment process profile
n s eoptionally
for printed payment processing, a payment system is not required for
system can a Ag litransmit

payment file handling, but
electronically ce positive payselect
you can a payment system and transmission details so that the
files to your bank.
w ary
Ash

Payment Tab
The Payment tab controls:

• Document grouping.
• Document limits.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
in tbecome
The Payment tab controls options for documents payables
@ u de payments. It controls:
• g r
a grouping s S options to define rules that are used to group
Document Grouping: Specify document
a
w when h i
t payment process profile is used. For example, if you
s h
documents payable into payments
a to u s e this
l (
select the due date, only payments with the same due date is grouped into a single
a r wa can
payment. Documents
n s e grouped by:
be
-
a
Unique
A l i ce identifier
g remittance
a ry- Remittance message
s h w - Due date
A - Bank charge bearer
- Payment reason
- Settlement Priority
- Delivery channel
- Ultimate Debtor
• Document Limits: Enumerates the maximum documents per payment.

Payment File Tab
The Payment File tab specifies:

• File formats, payment file prefix, directory, and extension.
• Payment grouping rules.
• Payment limits.
• Payment sorting.
• Bank instructions.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b e
inelectronic
The payment file tab specifies information about the
@ t u dpayment file that is transmitted to the bank. It
determines:
g a r s S
• Payment File Accompanying w a t h i
s h u s e
Letter Format
• Outbound Payment lFile
a (aDirectory
t o
•
arw cFile
Outbound Payment
g e se
nPrefix
•
a A Paymentli File Extension
Outbound
r y
w a file tab also controls:
The payment
h
As • Payment Grouping Rules: Specify how payment files are created when this payment process
profile is used. For example, if you select Payment Date, only payments that have the same payment
dates are grouped into a single payment file. Payments can be grouped by:
- Business Unit
- First party legal entity
- Payment currency
- Payment date
- Payment function
- Payment reason
- Disbursement bank account
- Payment process request
- Bills payable
- RFC identifier

• Payment Limits: You can limit payments by:
- Currency
- Number of Payments
- Conversion Type
• Payment Sorting: When you specify sort order, payments within a payment file are ordered as
specified. Sort order also determines the ordering of payments in the payment file register. You can
specify up to 3 sort orders.
• Bank Instructions: The formatting process maps the information you want included in all payment
files to payment file positions according to the payment file format specification. You can include:
- 2 Bank Instructions
- Bank Instruction Details
- 2 Payment Text Messages
ble
fe r a
ans
n - t r
n o
a
) has eฺ
ฺ c om uid
ฺ i b m nt G
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Payment File Tab
The Payment File tab also specifies:

• Batch booking.
• Overrides.
• Periodic sequences in format.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
• Batch Booking: Select Yes if you want to use
@ u de
in thistfeature.
• g r
athis payment
s S process profile to contain one or multiple service
Overrides: Decide whether you want
a h i
w se tIf you enable an override option, the payment file contains
s h
level and delivery channel combinations.
a channel u combination you select, rather than those specified in supplier
l (
the service level and delivery
t o
a r waenable
setup. If you do not
n s eany override options, the payment file can contain multiple combinations.
•
Agor payment
Periodic Sequences
a l iceinfilesFormat: If your payment system or bank requires sequencing of the
ry that is used to make the payment. You must include:
payments
aformat
you transmit, you must specify the numbering sequence in the payment
w
Ash - Sequence Identifier: Enter the same value that you entered in the payment format for the
Define Sequence field for payment files.
- Reset Sequence Value: Specify the value at which the sequence should restart when the
sequence is reset.
- Last Used Number: Sequence number that was actually used in the last payment file.

Grouping Tab
The Grouping tab is used to create multiple groups of payments for:

• ISO SEPA payment files.
• ISO CGI payment files.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
n tofudpayments e
Specify the grouping parameters to create multipleigroups within an ISO SEPA or ISO CGI
r @
a is used.
payment file when this payment process profile SThe transaction grouping rules can be based on:
a g h i s
• Payment Date
s h w se t
• (a to u
Disbursement Bank lAccount
a
•
arw cense
Ultimate Debtor
g
ChargeA
•
r y a Bearer li
• aService Level and Delivery Channel
s h w Category Purpose
A •
• Settlement Priority

Reporting Tab
The Reporting tab holds the formats and other options for various reports like:
• The Payment File Register.
• The Positive Pay File.
• The Separate Remittance Advice.

• Regulatory Reporting.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ
m nt Gc
ฺ i b e
You specify the formats for the generation of payment
@ in reports
t u dfor:
• The Payment File Register: A report g r s S for each payment file. The register lists details
a that isicreated
a
w insthat t h
s h
of each payment that is contained
a to u e payment file. You can select the format with or with out
l (
detail and whether to automatically submit when payment is confirmed.
•
r
The Positive Pay
a waFile:nAfter
se payment documents are recorded as printed, a positive pay file can be
generatedgif you set up e
A madelicby check. You must specify:
this optional feature. Positive pay prevents fraud by sending your bank a list
a
ary- Format
of payments
w
Ash - File Prefix, Extension, and Directory.
- Whether to automatically transmit file.
• The Separate Remittance Advice: Separate Remittance Advice is a report, which is an optional
feature initiated by the first party payer sent to a payee, that lists the documents payable paid as part
of each payment. You must specify:
- Conditions: Whether to create the report for All payments, Number of payments, or Payments
detail length.
- Delivery Method: Select either email, fax, or printed.
- The Format and whether to automatically submit when payment is confirmed and whether to
allow multiple copies for payment file.
• Regulatory Reporting: You must select either:
- No Reporting
- Report directly to central bank
- Reporting made by bank

Managing Disbursement System Options
Disbursement System Options provide default values for submitting payment process
requests. They can be set at two levels:
• Enterprise
• Business unit
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
To help drive consistency and save time, Payments
@ incan provide
t u dedefault values that automatically populates
certain fields on the payment process request.
g r
a Theyican
s Sbe set at two levels:
• a h
t and apply to all Business Units. You can set the
wwide ssettings
Enterprise: These are system
s h e
a l (a to u
following default options:
- Systemw
r Settings:
aemail, n e the payment method default basis, the separate remittance advice
sSet
A g
from
l c
ande separate remittance advice subject.
iFailure
ry
- a Validation Results: Set the default for both the documents and the payments.
a
w - Payment Review: Whether to stop the process to review the proposed payments after
A s h
creation.
- Payment Process Request Status Report Format: Define the format and whether to
automatically submit at payment process request completion.
- Payment Files: Whether to save the payment files in the database.
• Business Unit: Business Unit defaults override the enterprise level defaults. They include:
- Setting the payment method default basis, the separate remittance advice from
email, and separate remittance advice subject.
- Default payment specifications for Payee’s bank bearer charge format and whether to pay
each document alone.

Practice 12-7 Overview: Creating a Payment Process Profile
This practice covers creating a payment process profile.

ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Payment Document and Reference Numbers
• Payments enables you to generate payment document numbers and payment reference
numbers for:
– Checks
– Electronic payments
• You can meet a region or country-specific requirement if the required number of digits
for payment reference numbers is different from the number of digits in the Payments-
generated payment reference numbers.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
When Payments processes a payment process request,
@ u de a unique number, known as a payment
in it tgenerates
r
ga thThe
reference number, which identifies each payment. S
s payment reference number starts with 1 and
increments for every payment.
w sea i
For checks you can choose: (a s h u
• Blank Stock: rItw a l
indicatess
t o
e the check stock provided by the bank does not have the check
that
number. ga e n
a A l ic
•
a r y
Numbered Stock: These are preprinted checks. The format for this type fills in the check and the
s h w numbers must be synchronized with the system’s numbering.

A If you do not enable numbering for electronic payments, then the application-generated payment reference
numbers are stamped on electronic payments and passed to Oracle Payables as the reference numbers.
If you do enable payment document numbering for electronic payments, then payment document numbers,
as well as payment reference numbers, are generated for electronic payments. The payment document
numbers are then passed to Payables as the reference numbers.

Payment Process Requests
• A payment process request is a batch process submitted for the selection of invoices,
grouping of invoices into payments, and grouping of payments into a payment file.
• You can submit a payment process request on the Submit Payment Process Request
page. You can also create a template on the Create Payment Process Request
Template page and schedule the template to submit the payment process request later.
• For each payment process request, you can specify:
– Selection criteria
– Payment attributes
– Processing options
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
When your organization submits a pay run, it is done
@ inthrough t u da epayment process request. A best practice is
to set up templates for the most common ora r
g recurring s S payments. For instance, you might set up a
type
template for each business unit and for a
w each t
paymenth i method. In other words, have a template for the
a s h
electronic payment method and another
u
ones e
for check method payments. If a template is not available for a
( o
l canealsot be dynamically created.
particular pay run, the payarun
w
a cens
r
g
r y aA li
w a
As h

Selection Criteria Tab
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Navigate to: Payables > Payments > Tasks pane >in
@ u de Process Request > Selection Criteria
Submit Payment
t
tab.
g a r s S
a t h i
wwhichsinstallments
combination of the following: (a s h
Selection Criteria: This tab determines
u e are selected for payment. It can include one or a
a l t o
e date for an installment.
•
g a rw Latest
Pay through date:
e n sdue
• Pay from
a ic due date for an installment.
A date: Earliest
l
ry and To Payment Priority: Lowest and highest payment priority assigned to an installment.
• aFrom
w
Ash• Date Basis: Basis for the date that affects installment selection and whether to take a discount.
• Include zero amount invoices: Include invoices that have a zero amount due.
• Pay groups: Invoice categorization for payment. The default setting includes all pay groups, but you
can specify one or more pay groups.
• Currencies: Currencies for invoices and payments. The default setting includes all currencies, but
you can specify either one or more invoice currencies, or one or more payment currencies.
• Business units: Business units for invoices and payments. The default setting includes all business
units. If you specify:
- A payment business unit, the selection process finds installments for the invoice business
units that the payment business unit services.
- An invoice business unit, the selection process finds installments for that invoice business
unit.

• Legal entities: Legal entity associated with an invoice. The default setting includes all legal entities,
but you can specify one or more legal entities.
• Sources: The sources used to separate one time payments which were created as payment
sources such as Insurance Refunds, Student Refunds.
• Supplier type: Supplier classification, such as tax authority or contractor.
• Payment method: Method of payment for an installment.
• Invoice conversion rate type: Type of rate that converts the invoice currency to the ledger
currency.
• Supplier or party: Supplier or party on an invoice.
• Invoice group: User-defined name assigned to one or more invoices.
ble
fe r a
ans
n - t r
n o
a
) has eฺ
ฺ c om uid
ฺ i b m nt G
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Payment and Processing Options Tab
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ u de Process Request > Payment and
Submit Payment
t
Processing Options tab.
g a r s S
a
w se t h i
Payment Attributes
s h uof the payment.
•
a (a date
Payment Date: Thel effective
t o
• Disbursement
g arw n se The internal bank account that is used for the payment.
Bank Account:
e
•
a
PaymentA Document:
l ic Limits the payment processing to one type of document, either printed or
ry
aelectronic.
w
Ash• Payment Process Profile: A setup entity that drives processing behavior for each payment.
• Payment Conversion Rate Type: If processing a payment in a currency other than the functional
currency, the conversion rate type is used to convert the payment to the functional currency.
• Settlement Priority Override: Overrides the payment process profile’s settlement priority.
• Bank Charge Bearer Override: The party that agrees to assume the liability for bank charges
assessed on a transaction, which can be overridden by another party.
• Starting Voucher Number: If using voucher numbers, you can enter the starting number for the
payment.
• Cross-Currency Rate Type: The conversion rate type that is used to convert the invoice currency to
the payment currency.
Note: These attributes don’t affect installment selection.

Navigate to: Payables > Payments > Tasks pane > Submit Payment Process Request >Payment and
Processing Options tab.
The processing options for a payment process request determine the level of automation for that request.
For example, you can set options that submit the request through to completion without stopping, or you can
stop the request to review selected installments. The processing options are:
• Apply credits up to zero amount payment: Applies credits and creates a zero amount payment if
the sum of the selected installments is negative after the installments are grouped for payment.
• Review installments: Stops the payment process request after selecting the installments. You can:
- Review installments
- Add or remove installments
- Edit payment and discount amounts
- Specify user conversion rates
- Calculate withholding and interest
• ble
Review proposed payments: Stops the payment process request after grouping installments into
payments and before building the payments. fe r a
ans
• t r
Create payment files immediately: Creates payment files for the submitted request instead of
n -
o
waiting to combine payments from other requests into payment files.
n
• Validation failure handling for documents: Specifies processing s a
instructions for handling
h a
m) uinstructions
eฺ for handling payment
document validation failures.
• Validation failure handling for payments: Specifies c o
processing
ฺ tG i d
validation failures.
i b m
• i
First Approver: A specific user can be selected enapprover for payment approval by
nฺ astuthedfirst
g a r@ approvals.
overriding the configured rules for payment s S
a
w se t h i
s h
a l (a e to u
g arw cens
r y aA li
w a
As h

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 does not match the configuration of the payment
process profile or the internal bank account.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
n tulater
Matching during the installments selection processiprevents
@ de installment rejections during the build
r s S with the payment process profile or the internal
ga thattributes
payment process due to a mismatch of installment
bank account. a
w se i
s h u In page.
a l (a Feature
Enable from the Setup Manager
t o Opt
g arw cense
r y aA li
w a
As h

Positive Pay File Additional features
• Transmit positive pay files using the transmission configuration setup at the payment
process profile.
• Use the Transmit File parameter from the Create Positive Pay File process.
• Requires a valid payment system account and transmission configuration attached to the
payment process profile.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b e
Navigate to: Payables > Payments > Tasks panel tab
@ in > Create
t u dPositive Pay File
r s Spay files that are transmitted.
ga thetpositive
You can also use dynamic attributes to name
a
wattributes h i
a s
The transmitted files use the dynamich u s e specified in the transmission configuration that is attached
l ( e to
to the payment process profile.
a
w ns
ar ceenabled.
This feature is automatically
g
aA
Additional Tips
r y li
w
There ais no change to the existing process of automatically transmitting positive pay files when processing
h
Aspayment process requests.
To transmit positive pay files generated using the Create Positive Pay File process:
• You must have a valid payment system account and transmission configuration specified in the
Payment System tab of the payment process profile.
• The positive pay file is only transmitted when the Transmit File choice list in the Create Positive Pay
File process is set to Yes.
• The dynamic naming attributes specified in the Transmission Configuration are only used to name
the transmitted positive pay files.
• The dynamic attributes available for use are REQUEST ID, DATE, and TIME.
- Request ID refers to the process ID of the Create Positive Pay file process.
- Date is displayed in YYYYMMDD format and time is displayed in HHMMSS format. For
example, if you specify dynamic naming for the transmitted file as
&REQUESTID_&DATE_&TIME, then for a process ID of 123456 run on January 20, 2019 at
09:10:45, the file name of the transmitted file is 123456_20190120_091045.
• The static naming attributes specified in the Reporting tab of the payment process profile continue to
be used to name the generated positive pay files.

Update Payment Requests when Creating or Ending Employee Bank
Account
You can now automatically apply a payment request to a newly created bank account
Similarly, when you inactivate a bank account, you can automatically replace the account
with an alternative.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
When you create a new bank account in the Expenses
@ de you can now automatically apply the new
in worktuarea,
account to any payment requests that are not
g r S
a alreadyisassociated with a bank account.
a
w se t h
Steps to Enable
s h
(a to u
This feature is automaticallyl enabled.
a
g arw cense
r y aA li
w a
As h

Practice 12-8 Overview: Submitting a Payment Process Request

• Submitting a payment process request.
• Confirming generation of electronic payment numbering.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Payment Approval: Overview
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Oracle Payments introduces Payment Approval. You
@ in enable t u dePayment Approval feature on the Manage
the
Disbursement System Options pages. Payment
g r
a Approvals Senables you to:
a h i
t payments to approvers for review before final
shw oruemployees.
•
se
Enforce control over funds available by sending
payments are made to(a suppliers
• w a l e
policysfor
to
ar process
Define an approval payments created through a payment process request.
• Stop theA g
payment
l i c en request at the Review Proposed Payments stage, and enable approvers
tory a
optionally remove payments directly from the payment process request to prioritized payments for
w athe best use of funds available.
s h
A • Approve or reject payments from the payment process request from the payments page or directly
from emails. You can also perform other approval actions from payment approval worklist
notifications.

Implementation Overview: Setups
Setup for payments approval is performed from Setup and Maintenance using the following
tasks:
• Manage Disbursement System Options.
• Manage Task Configurations for Financials which accesses the Business Process
Management (BPM) Worklist application.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@
n setups:
The following predefined job roles grant access to ithe
t u de
• Financial Application Administratorga r s S
a
w se t h i
• Accounts Payable Supervisor
s h uAdministration Duty
•
a l (a Taskflow
Business Process Human t o
g arw cense
r y aA li
w a
A s h

Feature Impact Guidelines
Automatically Included with Any (Optional)

Feature Name
Available Shipped Job Roles Setup Needed
Enable payment
Yes Yes Yes

approvals
Configure approval
Yes Yes Yes
rules
Initiate approvals for
payment process Yes Yes No
requests
Send approval
Yes Yes No ble
notification
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
in upgrade.
Three of the features are automatically available after
@ t u de
r
ga“Configuration
s S of approval rules” have setups associated with it.
Features “Enable Payment Approvals” and
a h i
t job roles.
wexistingseshipped
s h
All features can be accessed through
a l (a e to u
g arw cens
r y aA li
w a
As h

Enabling Payment Approval
From the Manage Disbursement System

Options, click on Enable payment approval
to enforce approvals for payment process
requests.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b e
@ in tu> dPayments
Navigate to: Others > Setup and Maintenance > Financials > Manage Disbursement System
Options page.
g a r s S
a
w payment h i
tprocess requests level and not at the individual payments
h
The Approval process is enabled at the
s s e
level.
a l (a to u
When the payment approvals
g aWhen n se is enabled,
rw theepayment
option all payment process requests go through the payment
a A
approvals process.
l i c approvals process is not enabled, you must define automatic
ry for payments.
approval rules
a
s h w
A

Configuring Payment Approval Rules
Configure payment approval rules by

selecting:
• Task: PaymentApproval
• Participant: Payment Approval Serial

Participant
• Rule: Enter rule name and provide IF
and THEN details
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b e Define Approval Management for
Navigation: Others > Setup and Maintenance > Tasks
@ in Panetu>dSearch:
Financials > Manage Task Configurations for
g r
a Financials.
s S
a t h i
w youstoeconfigure
The Payment Approval features enables
Management User Interface. (a s h u
payment approval policy in Business Process
a l t o
The payment approval
g a rw e n se
policy defines:
• When to
a Ainitiate thelicpayment approval process.
ry for triggering the payment approval process, such as bank account, or pay group.
• aCriteria
w
Ash• A list of approvers who review payments and make final payment decisions.
Approval rules can be configured to route the approval notification in sequential mode, but not in parallel
mode

Payment Approval Rules: Example
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b e Define Approval Management for
Navigate to: Others > Setup and Maintenance > Tasks
@ in Pane t u dSearch:
>
Financials > Manage Task Configurations for r
ga Financials
s Slink > Edit icon > PaymentApproval (11.1.12.0.0)
task > Assignees tab. a
w se t h i
s h uthat are more than 5,000 USD to approvers. You can associate
a l a payments
Your business wants to route(all
t o
a r w nse
the pay group called “Morethan5k” with invoices greater than 5,000 USD.
The rule above routes
A i e to the user “finuser2” when a payment process request processes
g alllpayments
c
a
ry pay group equal to “Morethan5K”.
invoices with
w a
A s h

Initiating Approval for Payment Process Requests
When a Payment Process Request reaches the Payment validation stage, the status
changes to Payments approval initiated.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ u de Process Requests.
Manage Payment
t
r
a process
The payment process request is a straightgthrough s S and user intervention is not required unless you
a
w se t h i
s h
want to stop and review the payments.
u with the payment approval option enabled, the payment
l
When a payment process request
a (a is submitted
t o
approval process is automatically
astage. e
rw enstriggered after the payment process request reaches the Review
A
Proposed Paymentsg l ic
a
w a yapprovalapproval
After therpayment process is triggered, the status of the payment process request is set to
Ash
Payments initiated.

Payment Approval Worklist Notifications
Workflow:
• Generates and routes approval notifications to approvers.
• Sends approvers worklist notifications, as well as email notifications for review.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Navigate to: BPM Worklist > Select a Payment Process
@ in Request
t u delink.
Payment approval workflow evaluates all g
r
apayment s S rules and generates the worklist and email
a
w sare
the
h i approval
t to the approvers so they can review the payment
h
approval notifications. Approval notifications
s e routed
process request details.
a l (a to u
Approval notificationsrcontain
g nse payment details in the form of attachments.
a w ceindividual
r y aA li
w a
As h

Payment Approval Worklist Notifications
Enables approvers to approve, reject, withdraw approval, or terminate the payment process
request from the Review Proposed Payment page.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ
m nt Gc
ฺ i b
in Request
Navigate to: BPM Worklist > Select a Payment Process
@ t u delink.
g r
aa decision s Sto approve or reject the payment process pequest.
Approvers review payment details and make
Approvers can only approve or rejectw a t h i
an entireepayment
s h s file within a payment process request and not
individual payments within a payment
a ou
l (a e tfile.
g arw cens
r y aA li
w a
As h

Removing Payments During the Approval Process
• Reviewers can remove individual

payments.
• Reviewers cannot remove invoices.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ u de Process Requests > Review
Manage Payment
t
Proposed Payments.
g a r s S
When the payment approval processw a h i
t removing payments from a payment process request
s h e
is in progress,
s
a l (a to u
are allowed only for active approvers.
w npayments
Approvers can select rindividual e from the payment process request and click the Remove button to
sapprove
remove paymentsgifarequired e
a A l ic and remaining payments.
w ary
Ash

Withdrawing an Approval or Terminating the Payment Process
The Withdraw Approval action is available only to the:

• Submitter
• Approver
The Terminate Payment Process action is available to any user.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ u de Process Requests > Review
Manage Payment
t
Proposed Payments.
g a r s S
a
w only h i
t the payment process request status is in Payments
s h
The Withdraw Approval action is enabled
aperformed
approval initiated. This action(is s ewhen
uby the submitter or approver of the payment process request.
a l t o
g arwselect
If required, any user can
e n seTerminate Payment Process action.
the
a A l ic
w ary
Ash

Customer and Supplier Balance Netting Overview
You can access the Customer and Supplier Balance Netting pages from the Payables
landing page and the Accounts Receivable work area. Use the Customer and Supplier
Balance Netting feature to:
• Enable the automatic netting of Payables and Receivables transactions within a

business enterprise.
• Issue Payables payments and Receivables receipts for the netted amounts.
• Control how a group of trading partners who is both your supplier and your customer net
Payables and Receivables transactions.
• Automatically create the Payables payments and Receivables receipts required to clear
a selected number of Payables and Receivables transactions. ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b e
You can define netting agreements that incorporatein dbusiness
criteria, to support your payment practices. a r @ S t u
the netting
The netting process:
rules such as transaction selection
a g h i s
t and Receivables receipts required to clear a selected
•
s h w payments
Automatically creates the Payables
s e
number of Payables and
a l (a to u
Receivables transactions.
•
g a r ensework area and the Oracle Accounts Receivable work area.
Uses the OraclewPayments
• A and
Helps you
a l icsettle both AP and AR transactions for your trading partners who are both a
to quickly
ry
customer
aPermits supplier.
s h• w the settlement information to be automatically emailed to your trading partner.

A • Provides an internal netting report and listing to track of the details of the settlement such as trading
partners, invoices, transactions, and settlement date.
• Enables you to create a netting agreement for each group of trading partners that agrees to net
transactions. Netting agreements include the business rules that define the types of transactions that
may be selected for netting, and which suppliers and customers can be netted.
- Use netting groups to allow the Netting Manager to optionally create settlements for multiple
agreements at the same time.
- Implement netting groups to group together similar business related agreements for
settlements.
Key Resources: Customer and Supplier Balance Netting Topical Essay:
https://cloud.oracle.com/opc/saas/datasheets/netting-topical-essay.pdf

Customer and Supplier Balance Netting Settlement Features
• Streamline payments with your trading

partners.
• Settle payments quickly.
• Control types of invoices to net and

frequency of settlement.
• Reduce risk of late payments.
• Notify your customers of netted
transactions immediately by email.
• Settle large volumes of invoices and
ble
transactions.
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
n tudande receipts with your trading partners, without
The netting functionality helps you to quickly settleipayments
the need to create physical payments. a r @ S
• If your third-party is both yourw a g h i s
t your supplier, and you send and receive many invoices
s h s e
customer and
a to u quickly net off the invoices and transactions. Additionally,
l (
to each other, then netting enables you to
third-party. ar
wa nsettlements
you can create multiple
s e for each invoice currency that you send or receive with your
• The a
Ag lice enables you to combine multiple customers and suppliers that represent your
ry partner, so you can more easily manage the netting of invoices across different sites.
netting agreement
atrading
w
Ash• The agreement can also filter in or out certain types of invoices or transactions to be netted, based
on your business requirements.
• The process allows the netting manage to review a proposed settlement prior to completion. This
enables you to fine tune the settlement, such as removing or adding other transactions, or forcing
certain invoices to be netted.
• After completion, the process automatically emails your trading partner details of all invoices that
were netted.
• The payments and receipts are created as part of the process and can easily be identified as those
that are settled via the netting process.

Generate Netting Settlements
Use the Generate Netting Settlements process to create netting settlements for a Legal
Entity or Business Unit.
• Use the Manage Netting Settlements page to create netting settlements for a legal
entity.
• Use the Generate Netting Settlements process to create netting settlements for all legal
entities belonging to a business unit.
• You can also schedule the process to run at a time that is convenient for your business.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Navigator to: Tools -> Schedule Processes -> Generate
@ in Nettingt u deSettlements
• g r
a netting s Sof Oracle Payables and Oracle Receivables
The Netting feature enables the automatic
a
w se t h i
s h
transactions within a Legal Entity.
u Manager or Netting Manager can define a netting
• Your Payables Manager,
a l (a Receivables
t o
agreement thatw
g apractices.e n se the netting business rules and transaction criteria needed to support
r incorporates
your netting
a A process l ic automatically creates the Payables payments and Receivables receipts
• ry to clear a selected number of Payables and Receivables transactions.
The netting
arequired
h w
AsSteps to Enable
Refer to the Customer and Supplier Balance Netting Topical Essay for detailed implementation guidance:
https://cloud.oracle.com/en_US/opc/financials-cloud/implementationresources
Tips
• Determine if you want to run the process for your Business Unit or your Legal Entity.
• If you opt to run by business unit, all Legal Entities linked to your Business Unit are eligible for
selection.
• If you want to Settle Without Review, all the settlements are settled automatically, without the option
to fine tune your settlements in the spreadsheet.
Role Information
The Generate Netting Settlements job is automatically available if you completed the Netting Security Setup
Steps described in the Customer and Supplier Balance Netting Topical Essay.

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.
For Settlements that are in Selected or Selected, no transactions status you can download
them to a spreadsheet and process them as follows:

• Selected: Review, delete, or mark them to be settled.
• Selected, no transactions: 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.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
in tuanddeSupplier Balance Netting > Manage Netting
Navigate to: Payables > Payments > Task List > Customer
@
g r s S
Settlements > Select Settlement > Actions >aDownload Settlement to Spreadsheet > Click Payables tab
Navigate to: Receivables > Accountsw a h i
t> Task List > Customer and Supplier Balance Netting >
s h s e
Receivable
u > Actions > Download Settlement to Spreadsheet > Click
a l (aSelect
Manage Netting Settlements >
t
Settlement
o
arw cense
Receivables tab
g
a ANetting lSettlements
i
TIPS
r
a : y
Use the Manage page to search for the types of settlements that you wish to process.
w
Ash• Settlements that belong to a Legal Entity
For example
• 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
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.

Importing Netting Agreements
Using the Netting Agreement Import process you can:

Netting Agreement Process
Create
Import
Netting
Completed ble
Agreements
in a Netting Agreements into
fe r a
Spreadsheet Agreement the Application.
an s
Process
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Importing Netting Agreements
@ in tude
Netting Agreements can also be importedgusing
r
a the iImport
s S Netting Agreements FBDI spreadsheet.
w a h
tFBDI spreadsheet.
1. Download the Import Netting
s h s
Agreements e
2. Enter the agreements a t o u following the guidance in the notes.
l (inatheespreadsheet,
w ns
arfile
g
3. Create the zip
e
AImport’ tolicimport
4. Use a ‘File the zip file (choose fin/payables/import account)
a r y
5.w Run ‘Load Interface File for Import’ process (choose ‘Import Netting Agreements’ for the ‘Import
A s h Process’). When the process completes, the netting agreements from the spreadsheet are uploaded
into the netting interface tables.
6. Run ‘Import Netting Agreements’ process. You can optionally select a range of Legal Entities, and/or
a range for the ‘Netting Agreement’ name. To import all agreements in the interface tables, you can
leave the parameters as is.
Key Resources
Refer to the Customer and Supplier Balance Netting Topical Essay for detailed implementation guidance:
https://cloud.oracle.com/en_US/opc/financials-cloud/implementationresources

Customer and Supplier Balance Netting Example
• Valencia Farming is both your customer Number of Payables Receivables

and supplier. Invoices
• You have an agreement to net Number of Invoices 247 434
transactions. Invoice Amounts for $287,682 $261,408

Valencia Farming
• You owe Valencia Farming $287,682
across 247 invoices in Payables. Amount Netted $261,408 $261,408
• Valencia Farming owes you $261,658 Number of Invoices 227 434

across 434 invoices in Receivables. Netted
Number of invoices left 20 0

to pay ble
fe r a
Total amount $26,274
an s$0
outstanding
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Valencia Farming Example
@ in tude
In this example, Valencia farming is both g
r
a supplier s S they sell you fresh fruit and your customer
because you sell them machinery. w a your
t h i since
s h s e
u farming has sent you 247 invoices that total just over 287
• l (a Valencia
Over a period of 6 months,
a t o
thousand g arwfor
thousand dollars.
e n seoverparts.
Similarly, the last 6 months, you sent them 434 invoices totaling just over 261
a A dollars
l icmachinery
•
a r y
Instead of all 681 transactions being paid separately, you have set up an agreement with Valencia
s h w Farming to net transactions every 6 months, with any outstanding balance to be paid separately as a
A one off payment, or to be netted in a future netting settlement.
• Your netting manager runs the netting process. Since the total that you owe them is more than the
total that they owe you, all of the receivables transactions are marked as paid by netting. You are
also able to mark 227 payables invoices as netted, since they total the same amount on the
receivables side.
• Therefore 661 transactions are automatically settled, and you send Valencia Farming an email with
the details of all transactions that have been netted.
• You are now left with only 20 invoices in payables left to pay Valencia Farming, which total $26,274.
You can opt to either pay these separately, or leave them as unpaid for a future netting settlement.

Netting Features Specific Setups
Feature Description
Security: Assigning the Netting Assign the Netting Role to only those users who
Role create Netting Agreements and Netting Settlements.
Netting Payment Method Set up a netting payment method to identify the

payables invoices that are netted.
Netting Document Sequencing Set up a Document Sequence Category and

Setup Document Sequence. ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Security: Assigning the Netting Role
@ in tude
r
ga > Setup: s S
Navigate to: Others > Setup and Maintenance
w a t h i Financials > Users and Security > Manage Users
To successfully complete Netting,
a s h Netting
the
u s eManager running the process must have access to:
• a
Business units that l ( theetransactions.
own to
•
w
ar required nsto create payments and in particular receipts.
Necessarygroles
c e
a A Duty Role
Assign theyNetting
r
li Customer and Supplier Balance Netting only to those users who create
w aAgreements and Netting Settlements. Those same users must also be assigned access to the
Netting
h
AsPayables and Receivables roles, and have data access to all business units that you intend to use in the
Netting process.
Netting Payment Method Setup
Navigate to: Others > Setup and Maintenance > Setup: Financials > Payments > Manage Payment Methods
A netting payment method can be set up to identify the payables invoices that are netted. Ensure you enter
NETTING for the Code.
For Usage Rules: Check Automatically assign payment method to all payees.
For Payables: Check Enable for use in Payables.
Table: AP_CHECKS_ALL

Manage Document Sequences
Navigation to: Others > Setup and Maintenance > Setup: Financials > Payables > Show All Tasks >
Manage Payables Document Sequences
Assign a document sequence to the category:
• Applications: Payables
• Module: Payables
• Type: Gapless
• Department Type: Legal entity
ble
fe r a
ans
n - t r
n o
a
) has eฺ
ฺ c om uid
ฺ i b m nt G
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Netting Features Specific Setups
Feature Description
Netting Bank Account Setup A netting bank account is a fictitious account and
must be assigned to netting agreements.
Netting Receipt Class and Receivables includes a predefined receipt method for
Receipt Method Setup netting:ORA_AP/AR Netting. This is required to
process receipts that are created in a settlement.
Receivables System Options Two setup tasks in Receivables affect the Netting
Setup process:
ble
• Enables the payment of unrelated transactions to
fe r a
net for multiple customers in a settlement.
an s
• Control Transactions Types in receivables to
n - t r
a no
include for netting
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Netting Bank Account Setup
@ in tude
g r
a > Setup: s S
w a t h i Financials > Customer Billing > Manage Bank
Accounts
a s h use
l ( eselect
To enable a Netting bank account,
a to the Netting account field on the Bank Account setup for your legal
entity. w
ar account ns in the General tab on the Create Bank Account user interface.
• A
Check thegNettingli c e
r y a
• aFor Netting settlements that are for multiple currencies. For example, if you create a settlement that
s h w Nets within each currency, check the Multicurrency Account checkbox in the General Tab.
A • Assign the Business Units to the Bank Account in the Business Units Access tab. The Bank Account
must also have access to the Business Units that you want to include as part of your netting process.
• Edit the Business Unit and assign the NETTING Payment Method.
Netting Receipt Class and Receipt Method Setup
Navigate to: Others > Setup and Maintenance > Setup: Financials > Customer Payments > Manage Receipt
Class and Methods
To use the receipt method for netting: ORA_AP/AR Netting:
• Navigate to Manage Receipt Classes and Methods in Setup and Maintenance.
• Search for the Receipt Method equals ORA_AP/AR Netting.
• Assign your Business Unit and Account that is setup in the Netting Bank Account Setup section in
the Feature Specific Setup.

Receivables System Options Setup
Navigate to: Others > Setup and Maintenance > Setup: Financials > Receivables > Manage Receivables
System Options
Navigate to: Others > Setup and Maintenance > Setup: Financials > Customer Billing > Manage Transaction
Types
There are two setup tasks in Receivables that affect the Netting process. To process the cash receipts
within receivables, you must allow the payment of unrelated transactions if you want to net for multiple
customers in a settlement.
Additionally, you can fine tune the types of transactions to be eligible for netting.
Manage Transaction Types
Setup Transaction Types to control which types of transactions in receivables to include for netting.
• In some cases, you must exclude certain types of transactions from the agreement between the
deploying entity and the trading partner, for example, Credit Memos. Similarly, the Netting
Agreement can only cover the transactions related to a specific division or business purpose. ble
• fe r a
Receivables transactions are eligible for netting if the transaction types are associated to
n sthe
agreement.
n - tra
•
no are eligible for
Only transactions for transaction types that are assigned to the netting agreement
netting. This enables you to exclude certain transaction types from the a
has eฺ
netting selection process.
)
ฺ c om uid
ฺ i b m nt G
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
r y aA li
w a
A s h

Netting Agreement Setup Options
Feature Navigation
Netting Group Setup Implement Netting Groups to group together similar

business related agreements for settlements.
Pay Group Setup Helps control the types of payables transactions to

select when building a netting settlement.
Netting Letter: Email Subject The Netting Letter and Netting Reversal Letter can
e
be emailed directly to the third-party. abl fer
a n s
n - tr
a no
a s
m ) h deฺ Copyright © 2019, Oracle and/or its affiliates. All rights reserved.
ฺ c o u i
i bm ent G
i n ฺ
Netting Group Setup
r @ S t ud
w aga > Setup:
t h is Financials > Application Extension > Manage
Standard Lookups
a s h use
l ( Manager
Netting groups enable the Netting
a e to to create settlements for multiple agreements simultaneously:
• If you want to w
arnet ns types of trading partners or industries, enter the Netting group that can
for different
A g
be associated to li
an c e
agreement.
r y a
• aIf you want to net for only the agreements that are for the petroleum trading partners group for
s h w example, you can signify this choice when creating a settlement. The netting process ignores netting
A for the other agreements that aren’t assigned to the petroleum netting group.
Oracle uses a predefined a lookup type for this purpose : ORA_JE_NET_GROUP.
• Navigate to Manage Standard Lookups in Setup and Maintenance.
• Search for the Lookup Type equals ORA_JE_NET_GROUP.
• Add a Lookup Code, Start Date, and Meaning for the netting group.
• Add as many netting groups as you want, to differentiate between the netting agreement types.
Pay Group Setup
Navigate to: Others > Setup and Maintenance > Setup: Financials > Payables > Manage Payables Lookups
The Netting Groups control the types of agreements to settle, while the Pay Group functionality can help
control the types of payables transactions to select when building a netting settlement.

If for example, you know which transactions are eligible for netting when the transactions are entered
(manually, spreadsheet import), the payables invoices can be created with a predefined Pay Group that you
can assign to your agreement. Add lookup codes to the PAY GROUP lookup type for this purpose.
• Navigate to Manage Payables Lookups in Setup and Maintenance.
• Search for the PAY GROUP lookup type.
• Add a lookup code for your Netting pay group.
The netting agreement can then control the payables invoices to select based on the pay group. This is an
optional setup task. If you do not use Pay Groups to filter the payables invoices eligible for netting, then the
settlement process selects all the invoices that meet the criteria, regardless of which pay group is assigned
to an invoice. To default a Pay Group for invoices for a specific customer, enter the Pay Group at the
supplier level.
Netting Letter – Email Subject Setup
Navigate to: Others > Setup and Maintenance > Setup: Financials > Application Extension > Manage
Standard Lookups
ble
fe r a
You can email the Netting Letter and Netting Reversal Letter to the third-party. To set the Email subject text:
• Navigate to Manage Standard Lookups in Setup and Maintenance. ans
n - t r
• Search for the ORA_JE_NET_LETTER lookup type.
n o
• a
) as ฺ
Enter the Email subject in the Meaning field of the ORA_JE_SUBJECT lookup code.
hSubject.
om uide
The settlement number is automatically appended to the Netting Email
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
w sea
s h
a l (a e to u
g arw cens
r y aA li
w a
A s h

Netting Agreements Setup
A netting agreement:
• Controls how a group of trading
partners net Payables and
Receivables transactions.
• Includes business rules that
define the types of transactions
that may be selected for netting.
• Is created for each group of trading
partners that agrees to net transactions.
• Determines which suppliers and ble
customers can be netted.
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
in tuanddeSupplier Balance Netting > Manage Netting
Navigate to: Payables > Payments > Task List > Customer
@
Agreements
g a r s S
Navigate to: Receivables > Accountsw a h i
t> Task List > Customer and Supplier Balance Netting >
Manage Netting Agreements (a s h u s e
Receivable
a l t o
rw enuser
Access the Netting Agreement
g a seinterface from the Payments work area in Payables.
A Agreement
Access the Netting
a l ic user interface from the Accounts Receivable work area in Receivables.
aryAgreements
Searching
w
AsInhthe Search area, you can find agreements that you previously created. By default, the search selects only
active agreements that have not been end dated. However, you can change this in the Active Netting
Agreement field.

Summary
In this lesson, you should have learned how to:
• Set up a bank account.
• Manage payment system connectivity.
• Manage payment methods.

• Define payment method defaulting rules.
• Define payment codes.
• Understand payment process profiles.
• Explain disbursement system options.
• Understand and submit a payment process e
request. r a bl
sfe
• Manage Payments Approvals.
- t r an
• Understand Customer and Supplier Balance Netting.
n o n
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

13
Configuring Oracle Cash Management

ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h
Objectives

• Understand the key features of Cash Management.
• Define banks, branches, and accounts using the Rapid Implementation process.
• Configure Bank Statement Processing and Reconciliation.

• Perform Automatic Reconciliation.
• Describe the advanced features of Cash Management.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Cash Management: Overview
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Cash management integrates with several Oracle Cloud
@ t de You can Import bank statements in to
in Applications.
u
Cash Management and reconcile either manually r
ga process: S
or automatically.
s Following are the applications and
a
w se t
transaction types used during the reconciliation h i
• s h
a to u
Oracle Receivables: (Receipts
a l
• Oracle Payables
g a n se Payments
rw andePayments:
• Oracle A
a l ic payments
Payroll: Payroll
All thea ry applications transfer to the Oracle General Ledger using the Create Accounting process. Cash
above
h w
AsGeneral
Management transfers miscellaneous cash transactions such as bank charges, interest, and fees to the
Ledger.
Bank Statements can be reconciled directly from GL Journal Entries.

Set Up and Maintain Banks, Branches, and Bank Accounts
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
in tofudtheeBank Account model. Banks and branches
Banks, branches, and accounts fit together on the premise
@
r s S model also includes customers, suppliers,
ga thCommunity
are in the Trading Community model. The Trading
legal entities, and employees. a
w se i
s h youuto define and keep track of all bank accounts in one place and
The bank account setup pages
a l (atoenable
t o
a r w nse business units, functions, and users.
explicitly grant account access multiple
A
This eliminates theg redundant
l i c eduplicate bank account setup under different business units when these
a
ry share the same bank account.
business units
a
w recommends that you use the Rapid Implementation Spreadsheet task to create your banks,
A h
Oracle
s
branches, and accounts if you have a large number of banks, branches, and bank accounts to create.
Otherwise use the Manage Banks, Manage Branches, and Manage Accounting tasks from the Functional
Setup Manager to create and maintain banks, branches, and bank accounts.
Bank accounts are defined in Oracle Cash Management. Each bank can have multiple branches and each
branch can have multiple accounts.
When you enable a bank account for use with Payables, you can associate the account with multiple
payment documents.
When you set up your suppliers, you can also set up supplier bank accounts.

Manage and Maintain Banks
Required information for bank setup:

• Country
• Bank Name
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b e can create a new bank from an existing
Creating a bank is the first step in the bank accountin creation. d
r @ t u You
party. If a party with the same name for the a
message asks whether you want to useathat g same s Sis found after the bank name is entered, a
country
partythtoi create the bank. The option is available only after the
s h w e and country.
the samesname
existing party has been found with
( a to
l information: u
w
Create, edit, or update banka e
• g c ns requirements may exist for setting up a bank.
ar country-specific
e
A
Country: Some
aName: li
•
a r y
Bank Must be unique within a country.
• w Addresses (Optional)
h
As • Contacts (Optional)

Manage and Maintain Branches
Required information for branch setup:

• Bank Name
• Branch Name
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ
m nt Gc
ฺ i b
After you have created your bank, you create a branch
@ in or branches
t u de associated with the bank. The matching
r
ga branches.
option is also available when you are creating
s STo create a new branch without using the matching
w a
option, manually enter the information required. t
Youh i can define other branch-related attributes on the page.
a s
If you do not use the matching option h when
u s
aneexisting party is found, a branch with the same party name is
created. (
al se t o
r w
A ga branch
Create, edit, or update
l i c eninformation:
•
a ya The bank associated with this branch.
Bank:
r
• w Branch Name: Must be unique within a bank.
s h
A Optional Details:
• Alternate Branch Name
• Routing Transit Number
• Description
• BIC Code
• Branch Number Type
• Bank Branch Type
• EDI ID Number
• EFT Number
• EDI Location
• RFC Identifier
• Addresses
• Contacts

Manage and Maintain Bank Accounts
Four areas are associated with defining an account:

• General Information
• Control of the Account
• Security Access to the Account

• Business Unit Assignment
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
When the bank and branch are created, you can proceed
@ in totuthe debank account setup. Select the bank branch
you want to associate with your bank account. r
gaaccess
Four areas
s S are associated with defining the account: general
w a
information, control of the account, security t h i
to the account, and business unit assignment. If this
a s h
bank account is for Payables or Receivables,
u s e
the Business Unit Access needs to be added first for the
business units to use thisa bank(
l account.t o
r w s e
A gaprovides:
The Header section
l i c en
• The
r y aAccount Name: Due to the sensitivity of bank account numbers, the bank account name is
a
w often used to identify a particular bank account and must be unique across the system. Oracle
A s h recommends that you use defining attributes such as account use, bank, and currency in the bank
account name.
• Account Number: Issued by the bank.
• Currency: Usually the currency of the ledger and owning legal entity.
• Legal Entity Name: The owning legal entity of the bank account. The legal entity must have a
primary ledger associated with it before it shows up in the legal entity list of values.
• Account Use: Select Payables, Payroll, Receivables, or a combination of these.

General Tab
The General tab provides:

• GL Accounts
• Additional Information
• Contacts
• Payment Documents
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ
m nt Gc
ฺ i b
The General tab provides:
@ in tude
• GL account information: Consider g r
aassigningisaSunique GL cash account and cash clearing to each
bank account. This facilitatesw a threconciliation. If you are using bank statement
h e
book to bank
as cash us
l (
reconciliation, all subledger
t o transactions initially account to the cash clearing account. When
a r wareconciliation
the bank statement
n s ecashprocess is complete, the cash transaction is then moved from the
Aginformation: ice Provides information such as Alternate Account Name, Account Holder,
cash clearing account to the account.
• a l
ry Account Holder, EFT Number, Agency Location Code. You can also select whether the
Additional
aAlternate
w
Ash account is Active, can use multiple currencies, and is a netting account.
• Contacts: Used to record who can be contacted by phone or email.
• Payment Documents: Used during the Payment Process Request process to create a check. See
the next slide for more details.

Payment Documents
Used during the Payment Process Request process to create a check. Payment documents
include:
• Payment Document Name
• Paper Stock Type

• First Available and Last Available Document Number
• Format
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
ina payment
Every bank account that is to print checks must have
@ t u dedocument defined. The definition includes:
• Payment Document Name: Consider g r S that reflects the type of payment, for example
a usingiasname
a
w se t h
BofA Printed Check.
s h u
• Paper Stock Type: lThe
a (achoicest o are
-
g a w Indicates
Blank rStock:
e n se that the check stock provided by the bank does not has neither the
a A l
check number ic nor the formatting.
w ary- Numbered Stock: These are preprinted checks. The format for this type fills in the check
A s h and the numbers must be synchronized with the system’s numbering.

- Number of Setup Documents: This is useful if you are using Numbered Stock and need to
run a few test documents to ensure that the format fits the preprinted check.
- Format: Indicates the BI Publisher template to be used for generating the check.
- First Available Document Number: This is required for blank stock and numbered stock.
This keeps the documents in synchronization with the system numbering.
- Last Available Document Number: Indicates the last number of the available check stock
and is mandatory for numbered stock.

Control Tab
Cash Management Controls:

• Reconciliation
• Bank Statement Processing
• Bank Statement Transaction Creation Rules

• Cash Positioning and Forecasting
• Payables Controls
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
inManagement
The control tab provides control information for Cash
@ t u de and for Payables.
r
ga tControls:sS
Assign the following items for Cash Management
a
w se h i
• Reconciliation:
s h
- a
Manual Reconciliation o u Rule
l (a e tTolerance
- rw enRate
BankaExchange
g s Type
-a A i c
AutomaticlReconciliation
a r y Rule Set
s h w - Reconciliation Start Date

A - Reversal Processing Method
• Bank Statement Processing:
- Parsing Rule Set
- Bank Statement Transaction Creation Rules
• Cash Positioning and Forecasting:
- Target Balance
- Transaction Calendar

Assign the following items for Payables Controls:
• Pooled Account: If you use Automatic Offsets and you want to associate multiple legal entities with
this bank account, then enable this option. When you enable the Automatic Offsets Payables option,
Payables creates one offsetting liability distribution for each invoice distribution. If you pay an invoice
from a pooled bank account, then when Payables accounts for the invoice payment, Payables
creates one corresponding cash accounting entry for each liability distribution.
- In addition, Payables builds the cash account based on the cash account defined for the
bank account and the account segments of the liability lines.

- If you do not use a pooled account, then when the payment is accounted, a single accounting
entry is created for the cash account, using the cash account that is defined for the bank
account without modifying any account segments.
• Minimum/Maximum Payment: This refers to the smallest and largest payment amounts that you
allow in a pay run. When you initiate a pay run using the bank account, Payables uses the bank
account’s maximum payment as a default. You can override this default.
• Allow Zero Payments: If you allow zero-amount payments from this bank account, enable this ble
option.
fe r a
• an s
n - r
Maximum Outlay: The largest amount outlay that you allow for a pay run for this bank account. If
t
the total outlay of a pay run exceeds the maximum outlay for the pay run, Payables displays a
n o
a
warning, but enables you to continue processing the pay run. The maximum outlay for a bank
) has eฺ
account is supplied by default from the Payables Options window. When you initiate a pay run using
the bank account, Payables uses the bank account’s Maximum Outlay as a default. You can
override this default. ฺ c om uid
ฺ i b m nt G
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Security Tab
Further secure bank accounts by:

• Users
• Roles
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ
m nt Gc
ฺ i b
@
n be used
You can further secure the bank account so that it ican
t u deonly by certain users and roles.
The default value for secure bank accountgby
r
a users iand
s Sroles is No. In Payables and Receivables, even if
a h
wrolessiseno,t you must have proper access to the bank account.
the secure bank account by users and
s h
a and u is set to Yes, you must be named or you must carry a role that
If the secure bank account by
a l (users t o roles
g arw
is named expressly on se to use it.
the bank account
e n
a A l ic
w ary
Ash

Business Unit Access Tab
One or more business units must be granted access to the bank account before it can be
used in:
• Payables
• Receivables
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b e unit. In addition to the appropriate
Payables and Receivables account access is secured
@ in by the t u dbusiness
application use or uses being selected, onea r
g or more S units must be granted access before the bank
business
s
w a
account can be used by Payables and Receivables.t h iOnly the business units that use the same ledger as the
h
as to us
owning legal entity of the bank account can e
be assigned access.
l (
a r wa nse
a Ag lice
w ary
Ash

Configuring Cash Management Rapid Implementation
• Create Banks, Branches, and Accounts in Spreadsheet.

• Upload Banks, Branches, and Accounts.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b e list provides the required and most
in tudtask
The Define Financials Configuration for Rapid Implementation
@
frequently used setup tasks for implementation r
gaBanks,
scenarios
s Sobserved in practice. The primary mechanism for
w a
rapid implementation is to create and upload t h i Branches, and Accounts setup using a spreadsheet
upload. h
as to us e
l (
a r wa
Note: Use the standard Set
n s eset Branches,
Up Banks, and Accounts list for the ongoing maintenance and for
A g lice
those configurations that cannot be up using the rapid implementation approach.
ryabank, branch, and account information to enter into the spreadsheet template.
Prepare your
a
h• w Bank information requires the country, name, and number.
s
A • Branch information requires name, number, and BIC code.
• Account information requires name, number, currency, and legal entity.
• After you finish preparing the data in the spreadsheet, click the Generate Banks, Branches, and
Accounts File button. Save the generated XML file.
Upload the XML file into Cloud.

Bank Statement Processing Overview
Before reconciling a bank statement, you must first process the bank statement into Cash
Management by:
• Loading and importing electronic bank statements.
• Using the Parse Rule Set to transform information on the bank statement into attributes
used for reconciliation.
You can then match bank statement lines to transactions:
• Manually
• Automatically
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Manage bank statements and validate them against
@ t de balances in the general ledger and
incash account
u
subledgers to maintain an accurate picture of
g r s S cash position. Tasks include:
a the organization's
• a
w se t h i
h
Processing electronic bank statements.
s
• Reporting on bank account
a t ou
l (a ebalances.
Recording firstrw
•
g c e ns items like bank fees and charges to the general ledger.
a presentment
•
a A bank lstatements
Reconciling
r y
i to payments paid and received.
• aDefining parse rule sets to transform data during the bank statement import process.
s h w
A Cash Management supports the following protocols:
• Bank Administration Institute (BAI2)
• Society for Worldwide Interbank Financial Telecommunication (SWIFT MT940)
• Electronic Data Interchange for Administration, Commerce, and Transportation and Financial
Statement of Account (EDIFACT FINSTA)
• International Standard Organization (ISO20022)
• Import non-standard bank statement formats via spreadsheet.

Key Setup Tasks for Bank Statement Processing
For Bank Statement Processing, create and assign:

• Cash Transaction Type Mapping for Payables, Receivables, and Payroll
• Transaction Codes
• Code Map Groups

• Bank Statement Formats
• Parsing Rule Set
• Transaction Creation Rules
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
For bank statement processing to occur, you must ifirst
@
n create t u daeCash Transaction Type Mapping for
Payables, Receivables and Payroll. Then set
gthenr or edit S
a upused s predefined Transaction Codes using the mapped
transaction types. Transaction codes are
w a t h i
to create Code Map Groups and Code Map Groups are
h
as to us
used to create Bank Statement Formats. e
l (
a r wa nthrough
When a bank statement comes
s e the interface the Parsing Rule Set is used to transform data from the
bank statement file.
A g lice
a
ry thatexternal
Finally, if any transactions exist such as bank fees, the Transaction Creation Rule creates a
w a
transaction can be reconciled and accounted.
A s h

Manage Cash Transaction Type Mapping
The transaction type mapping enables you to associate a Cash Management transaction
type with a payment or receipt method or a Payroll payment type.
Create this association by mapping Cash Management Transaction Types to:
• Payables Payment Methods

• Receivables receipt methods
• Payroll Payment Types
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Mapping payment, receipt method, or Payroll payment
@ in types t u deCash Management transaction types can be
to
helpful for bank statement reconciliation. a
g r s S
When a transaction code is created, w a h i
t type needs to be associated with it. A bank statement line
s h u
a a corresponding
that has the transaction code (has
e
a transaction
s transaction type.
a l t o
e method, or Payroll payment type is mapped to the transaction type,
g rwpayment,
If a system transaction
amatching e n sreceipt
a A
the transaction type
l ic criteria can be used during autoreconciliation.
Payablesry
w a and Receivables Payment Method Mapping:
Ash• Identify the type, transaction type, and method.
• To map payable payment methods to cash transaction types, use disbursement type.
• To map Receivables receipt methods to cash transaction types, use Receipt type.

Cash Management Setups for Automatic Reconciliation Overview
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
n tudeyou must complete the following setups.
Before you can perform automatic bank statement ireconciliation
Note: You must have the Cash Manager role r @
a to perform Sthe Cash Management setups. The setups include:
a g h i s
• Banks, Branches, and Accounts
s h w se t
• (a existing
Transaction Codes: lModify
t o udelivered transaction codes or create new transactions codes as
a
rw ecodes
required. Transaction semust match your bank’s transactions codes.
g a n
• Aconstituent
Parse Rule
a l icfields.rules
Sets: Parsing are used to parse inbound addenda and other fields into more
a ry for the parsing batch job or concurrent

granular A parsing rule set is associated to a bank account and used as reference
s h w data program.
A • Bank Statement Transaction Creation Rules: Used to identify an unreconciled or external bank
statement line or lines and create an account for a transaction. For example, bank fees and interest.
• Cash Transaction Type Mapping: Based on the payment method, identify the transaction types for
Payables and Receivables and provide a description.
• Bank Statement Reconciliation Tolerance Rules: Tolerance rules include date, amount and
percentage options. Manual reconciliation can have a tolerance rule assigned to a bank account.
Automatic reconciliation can have a tolerance rule applied if the matching rule matches on the date,
amount or both.
• Bank Statement Reconciliation Matching Rules: Flexible matching rules determine how to match
Bank Statement Lines and system transactions.
• Banks Statement Matching Rule Set: Bank statement reconciliation rule sets are a group of matching
rules and tolerance rules. They are assigned to a bank account and used to reconcile bank
statement lines with transactions.
• Define Subledger Accounting Rules: You can modify predefined accounting rule setups for
accounting-enabled events by creating user-defined rules for the external entry transactions.

Bank Statement Transaction Codes
Transaction Codes are used on:

• Parse Rule Sets
• Bank Statement Transaction Creation Rules
• Bank Statements.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
in that
Bank statement transaction codes are the internal codes
@ t u dareeused on a bank statement line to identify
the type of transaction being reported.
g a r s S
a
wset ofsthese h i
t codes and transform externally reported transaction
Cash Management maintains a single
s h
a single
codes from other formats into(this u e
normalized set.
a l t o
values needed tog
se codes
arwthecetransaction
Each imported bank statement
nincludes bank statement transaction codes. Your bank should provide the
a A create
l i used on the imported bank statements.
a y the predefined transaction codes or create your own if required..

You can ruse
w
h you create the transaction code, it is available for all bank accounts without restriction.
AsWhen As soon as you create or import a bank statement and assign the transaction code to a bank statement line,
the bank account appears in the Bank Account Usage panel.
Bank account usage indicates the list of bank accounts that are using a specific transaction code in any
bank statement Line.
To create a transaction code, you must provide:
• The Transaction Code: This is typically numeric.
• Description: Provide a meaningful description to clarify the transaction type. For example, the
Check transaction type can be used for a Receivables receipt and for a Payables payment. The
description helps the user choose the correct code for a Check type.

• Transaction Type:
- Automated Clearing House
- Bank Adjustment
- Check
- Electronic Funds Transfer
- Fee
- Interest
- Lockbox
- Miscellaneous
- Zero Balancing
ble
fe r a
ans
n - t r
n o
a
) has eฺ
ฺ c om uid
ฺ i b m nt G
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Practice 13-1 Overview: Managing Bank Statement Transaction
Codes
This practice covers creating a transaction code for EFT Disbursements and Bank Fees.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Payment Code Map Groups
The types of Codes that can be created in the map groups are:
• Balance: Opening and Closing book balances.
• Transaction: Used on bank statement lines.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ
m nt Gc
ฺ i b
A single set of internal balance and transaction codes
@ t de within the Oracle Cash Management
in is maintained
u
application. The balance codes are defineda
g r s
in the lookup SCE_INTERNAL_BALANCE_CODES and the
transaction codes are defined through a
wtheareManage h i
t Bank Statement Transaction Codes task. Externally
reported balance and transaction s h u s e
acan be ttransformed
codes the ones that appear in the data files provided by the banks.
The externally reported codes l
a se( o to the internally defined codes using Oracle Payments
Code Map Groups.arw
A g licen
for thea ryaattribute
When setting up the Code Map Group in Payments for Balance code mapping, use CE_BALANCE_CODE
h w Field of the Mappings section; for transaction code mapping, enter CE_TRX_CODE for the
AsField attribute. The input value is the external code, and the output value is the internal code. The value you
enter in the Output Value field must be a valid internal code. By mapping an input value to the output value,
you are mapping the external code to the internal code.
For example, sometimes different banks may use the same external transaction code differently. Bank of
America may use BAI2 transaction code 174 to mean incoming wire transfer, but Citibank may use the
same code to mean check deposit. In such a case, you create two code map groups. One is for Bank of
America and it maps external transaction code 174 to internal code ‘WIRE IN’. The other code map group is
created for Citibank and it maps 174 to ‘CHECK DEPOSIT’.
Oracle predefines two code map groups. One for mapping the BAI2 opening and closing booked balances
codes and the other for mapping the EDIFACT opening and closing booked balance codes to the internal
balance codes.
SWIFT940 does not require a balance code mapping because it is position-based, but a code map group
can be created to map the transaction codes to the internally defined transaction codes.
Bank statement codes that are defined as internal codes do not require a code map group. For example, the
transaction codes created for bank fee, charges, and interest don’t need a code map group.

Code Map Group Example
Bank of America and Citibank use the same Transaction Code 174 for different types of
transactions.
Code Map Group Name Field Value Mapping
BofA BAI2 Code Map CE_TRX_CODE Input Value: 174

Output Value: WIRE IN
Citibank BAI2 Code Map CE_TRX_CODE Input Value: 174
Output Value: DEPOSIT
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Bank Statement Formats
Bank statement formats are defined in Oracle Payments and used during the bank
statement processing job.
Format Name Code Map Group

BofA BAI2 Format BoA BAI2 Code Map
Citibank BAI2 Format Citibank BAI2 Code Map
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
The predefined formats that can be edited and used
@ destatement process job. The predefined
infor thetubank
formats are:
g a r s S
• a
w se t h i
BAI2
s h u
• EDIFACT FINSTA l (a o
a t
• ISO20022
g arw cense
SWIFT A
•
r y a MT940 li
For theaexample above, you would need to create two formats in Oracle Payments using the Manage
s h w task. Assign the two different code map groups to the two formats. You can copy all the other
Formats
A values from the predefined BAI2 format.
When you submit the bank statement processing job, you can choose the corresponding format depending
on whether the bank statement is from Bank of America or Citibank. When the statements are processed,
the same 174 transaction code is mapped to different internal codes.

Parse Rule Sets
Cash Management supports parse rule sets to transform data during the bank statement
import process. They include:
• Sequence
• Transaction Code
• Source Field
• Target Field
• Rule
• Overwrite
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ
m nt Gc
ฺ i b
Parse rules are used to move data from one field toin
@ u
another. The
t deparse rule set is associated to a bank
account in the bank account setup. The parse r
ga rule set isS
s most commonly used to parse data from the
a
w se t
statement line addenda field into more specific h i
statement line fields. Each parse rule within a parse rule set
consists of the following fields: sh
• Sequence: Determinesa o inuwhich to process the rules.
l (atheeorder
t
• g rw Determines
aCode: e ns the statement line type.
Transaction
c
a AField: Theli interface table field that contains the data to be parsed.
•
a r y
Source
h• w Target Field: The statement line field that the data is to be parsed to.
As • Rule: Contains the syntax for determining the data within the source field to be parsed.
• Overwrite: Used to control whether to overwrite existing data in a target field or skip parsing the
data.

Parse Rule Set Example
Description Source Data Rule Target Data

Extract numeric rate EST/TRX RTE 3.76 RTE (N.NN 3.76
data. USD/LIBOR CPTY:
PRU
Extract the original ?26/OCMT/GBP13949 ?26/OCMT/GBP(NNN 13949.25

amount from ,25/? NN,NN)/?
Additional entry
information.
Extract the currency EST/TRX/RTE 3.76 RTE(7-9) USD

from the same source USD/LIBOR
field using positional CPTY:PRU
ble
matching.
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
The Parse rule syntax is described here:
@ in tude
r
ga this S
[LITERAL](<[MATCHING TOKEN],[START-END]>)[LITERAL]
a
w se
Where s h u
a l (a value
LITERAL = A string or character t o
represented by an identifier that should match the source data
exactly.
g arw cense
MATCHINGaTOKENA = A ltokeni (or set of tokens) which describes the data to extract. Valid tokens are:
r y
• waN = Extract a valid number
h
As • . = Decimal position
• X = Extract an alpha numeric
• ~ = Extract everything in the source field from the parse position to either the end of the data or up to
the next literal.
• START = A position to begin extracting data, offset by the parse position. It must be a valid numeric.
• END = A position to stop extracting data. END can be either a valid numeric or the ~ token.

Parse Rule Set Example
Description Source Data Rule Target Data

Extract the counterparty of an EST/TRX RTE 3.76 CPTY: (X~) PRU
unknown string length from the USD/LIBOR CPTY:

same source field PRU
Extract Transaction ID from CustRef # CustRef (X~).com # A.23@orlc

Customer Reference. A.23@orlc.com
(Customer Reference)
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Bank Statement Transaction Creation Rules
External cash transactions are transactions related to cash activity that have not been
recorded within the system. Following sources of external transactions exist:
• Manual entry.
• Import.
• Balancing transactions created during reconciliation for amount variances.
• Transactions created during Bank Statement Transaction Creation program
• External transactions created during Bank Account Transfer, Ad Hoc Payments and
Reversal Reconciliations.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Bank Statement Transaction Creation is a programin
@ u de unreconciled bank statement lines and
that identifies
t
r
creates transactions and an account for firstanotice itemsSsuch as bank charges, fees, or interest and
w
reconciles the bank statement transaction. is
agOraclethrecommends that you first run Autoreconciliation and
perform any manual reconciliation
a s h
on a
u
bank s e
statement before running the Bank Statement Transaction
l (
Creation program to avoidacreating o
t transactions from bank statement lines which already have
external
r w
aand specify
transactions recorded in the s e
nsome of the
application. You create the rules to identify the statement lines from which to
A g
create transactions l i c e attributes, including accounting options, of the created
a
ary
transactions.
w
Ash
Create a rule by entering:
• Name
• Legal Entity: When the legal entity is assigned, the Cash and Offset Accounts appear under the
Accounting check box.
• Statement Line Identification criteria: The criteria are used to identify the statement lines from which
to create transactions. This includes:
- Type: The same Transaction types as used on Transaction Codes.
- Transaction Code: You must create a transaction code for each type of external transaction
expected.
• Transaction Details:
- Type: The same Transaction types as used on Transaction Codes.
- Business Unit
- Cash Account
- Offset Account

Practice 13-2 Overview: Managing Bank Statement Transaction
Creation Rules
• Creating a transaction creation rule for a bank fee.
• Assigning the appropriate general ledger accounts.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Bank Statement Reconciliation Setups
For Reconciliation, assign the following:

• Matching Rules
• Reconciliation Tolerance Rules
• Automatic Reconciliation Rule Sets
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
in tbank
Bank Statement Reconciliation is the process of matching
@ u destatement lines with transactions to ensure
that all bank account activity is recorded withinr
ga tothebe S You can manually match the statement lines
application.
s
and transactions or set up reconciliationarules
w t h i
performed automatically.
Following are the key setups (for
h e
us reconciliation:
asbanktstatement
l o
•
a r
Matching Rules: waFlexible
n e
smatching rules determine how to match Bank Statement Lines and
A g ic
system transactions.
l e
• r y a
Tolerance Rules: Tolerance rules include date, amount and percentage options. Manual
a
w reconciliation can have a tolerance rule assigned to a bank account. Automatic reconciliation can
A s h have a tolerance rule applied if the matching rule matches on the date, amount or both.
• Matching Set Rule: Bank statement reconciliation rule sets are a group of matching rules and
tolerance rules. They are assigned to a bank account and used to reconcile bank statement lines
with transactions.

Bank Statement Reconciliation Tolerance Rules
Tolerance rules enable you to specify tolerances that prevent or warn you when a
reconciliation would be a breach of a defined tolerance. Define tolerance by:
• Date
• Amount
• Percentage
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Before creating reconciliation tolerance rules, consider
@ u de
in thetfollowing:
• g
By applying tolerances you can automate r S
a theisreconciliation and accounting for these types of
w a t h
transactions.
a s h use
•
a (
If no date or amountl tolerance
t o
is defined within a rule, the date or amount tolerance requires an
exact match. w
g a r ense
• For manual
a l ic a tolerance rule can optionally be assigned to a bank account.
A reconciliation,
• aFor ryautomatic reconciliation, a tolerance rule can be associated with a matching rule in the Rule Set
s h w setup and can be applied if the matching rule matches on date and amount or both.
A • The one exception occurs when you assign a tolerance rule that includes amount tolerances to a
match type matching rule that is not a one to one match. In this match type matching rule that is not
a one to one match, the amount tolerance is ignored and amounts must match exactly.
Date Tolerance: Date tolerances are primarily used for checks that may be issued on one day and do not
clear the bank until days or weeks later.
• Reconciliation date tolerances are defined as day ranges. The date tolerances are to validate that
the source transaction date or dates are within a certain number of days before and after the bank
statement line date or dates.
• In manual reconciliation, if a date tolerance is specified in the tolerance rule assigned to the bank
account it applies to all matching scenarios. In the event of a date tolerance breach, a warning
message is displayed, but the user is enabled to reconcile the statement line or lines and the
transaction or transactions. If no date tolerance is assigned or specified it is required to be an exact
date match and a warning message is displayed.

• In automatic reconciliation, a tolerance rule that includes date tolerances can be associated with a
matching rule. If the matching rule matches on the date, then the date tolerance is applied. In this
scenario a date tolerance breach prevents reconciliation.
Amount Tolerance: Amount tolerances are most often used when you are reconciling foreign currency
transactions where differences may exist due to rounding or fluctuations in the exchange rate. They can
also be used if a bank includes a processing fee in the bank statement line amount.
• Reconciliation amount tolerances can only be used in one to one matching scenarios for both
manual and automatic reconciliation. No reconciliation amount tolerances are allowed in one to
many, many to one, or many to many matching scenarios. In these scenarios the amount of the bank
statement line or lines must be equal to the amount of the transaction or transactions. Reconciliation
amount tolerances can be defined as percentage or amount ranges or both. If both percentages and
amounts are applied, the application uses the most conservative tolerance depending upon the
statement line amount.
• For example, if the amount tolerance equals plus or minus $5, the percentage tolerance equals plus
or minus 1%, and the statement line amount is $100, the application first calculates the percentage
bl e
amount (1% of $100 dollars = $1). It then compares this to the $5 amount and uses the smaller
fe r a
s
amount. In this case it is $1 dollar, so to reconcile a transaction to this line it must be between $99
an
and $101.
n - t r
• n o
In automatic reconciliation, a tolerance rule that includes percentage, amount, or both types of
a
has eฺ
tolerance ranges can be associated with a matching rule. But the tolerance can only be applied if the
matching rule is a one to one match type rule. In this scenario of a one to one type match, any
)
ฺ c om uid
amount difference within tolerance is automatically created as an external transaction in cash
management.
ฺ i b m nt G
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Practice 13-3 Overview: Managing Bank Statement Reconciliation
Tolerance Rules
This practice covers creating a bank statement reconciliation tolerance rule.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Bank Statement Reconciliation Matching Rules
Matching rules enable you to determine how to match bank statement lines and application
transactions, and help achieve a higher match rate in Autoreconciliation, minimizing the
need for manual intervention.
You can select a Match Type of:

• One to One
• One to Many
• Many to One
• Many to Many
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Create, edit, copy, and delete matching rules to beiused
@ de
n fortureconciliation. For each rule, specify:
• Matching Rule name. r
ga this S
a
w se
• h
Transaction source or sources.
s
• Match Type:
a l (a e to u
Onea torw ns one bank statement line to one system transaction.
one: Match
-
g c e
-a A li Match one bank statement line to many system transactions in summary.
One to many:
r y
a - Many to one: Match many bank statement lines in summary to one system transaction
h w
As - Many to many: Bank statement lines that do not match up with any system transactions
except for in aggregate.
• Group by attributes for bank statement or source depending upon match type.
• Matching Criteria: Includes a list of commonly used matching attributes. You can simply check the
attributes to include in their matching rule. Only group by and amount fields are available for
matching if grouping is used.
Additional Matching Criteria: Enables you to specify additional matching logic or filtering conditions that
must be true for the bank statement line or lines and transaction or transactions to be matched successfully.
Only group by and amount fields are available for matching if grouping is used. You can select one or
multiple transaction sources in a rule. Matching Type Considerations:
• If multiple sources are selected in a one to one or many to one matching rule, then the auto
reconciliation program looks for a matching transaction across the selected sources.

• If multiple sources are selected in a one to many or many to many matching rule, then the program
first finds all available transactions across the selected sources and then applies grouping rules to
the whole data pool. This means that statement lines can be reconciled to a group that includes
transactions across the different sources.
• If you want transactions included in a group to be from the same transaction source, then you can
specify Transaction Source as a grouping attribute.
ble
fe r a
ans
n - t r
n o
a
) has eฺ
ฺ c om uid
ฺ i b m nt G
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Matching Rules
This practice covers creating a bank statement reconciliation matching rule.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Reconciliation Rule Sets
Reconciliation Rule Sets are:

• A group of matching rules and tolerance rules.
• Assigned to a bank account.
• Used to reconcile bank statement lines with transactions.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b e
When creating reconciliation rules sets, provide theinfollowing d
r @ t u information:
• Enter the name of the rule set.
a ga this S
• h
Provide a detailed description.
s w se
•
a to1.u
l (sequence
a
Accept the default for
se the default matching type, which is based on the matching rule.
•
g arwrule.
Enter a matching
c e n
Accept
• a A enter alitolerance
Optionally rule.
a r y
Youwbuild the rule set and the rule set detail as a parent/child relationship. Each rule set consists of one or
s h
A more matching rules that can be prioritized or sequenced. The rules should be ordered to achieve a greater
reconciliation success rate.
Oracle strongly recommends that one-to-one rules be sequenced above rules of other types. To provide an
optimum reconciliation rate, you should change the sequence number depending on how accurately the
given rule is likely to reconcile against the correct bank transactions.
For example, transactions from sources for which the bank provides you a reference ID are likely to have a
higher reconciliation rate. These rules should be placed at the top with a lower sequence number.
Conversely, transactions with no reference ID are likely to have duplicates or lower reconciliation rates, and
you should place them at the bottom with a higher sequence number.

Rule Sets
This practice covers creating a rule set to combine the matching and tolerance rules.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Practice 13-6 Overview: Assigning a Rule Set to a Bank Account
This practice covers assigning the rule set to your bank account.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Defining Subledger Accounting Rules: Cash Management
Accounting Event Model
Oracle Cash Management provides a predefined accounting event class and accounting
event types.
Event Class Event Type Accounting

External Transaction Reconciled Yes
External Transactions
External Transaction Unreconciled Yes
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ t u de
n accounting-enabled
You can modify predefined accounting rule setups ifor events by creating user-defined
rules. r
ga this S
a
w se
s h
a l (a e to u
g arw cens
r y aA li
w a
As h

Performing Bank Statement Reconciliation
The two ways to perform a Bank Statement Reconciliation are:

• Manual
• Automatic
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
in tbank
Bank Statement Reconciliation is the process of matching
@ u destatement lines with transactions to ensure
that all bank account activity is recorded within
g r s S
a the application.
a h i
t are:
w reconciliation
The two ways to perform bank statement
s h
a interface, s e
u match the statement lines and transactions. This is useful for
• Manual: Through the
a l (user t o
exceptions to r
athewautmaticn e
sreconciliation.
process. Non-standard bank statement formats can be imported using
A g
spreadsheets
ic e
for manual
l
• ry a
Automatic: After the bank statement has been loaded, submit the Autoreconciliation process.
a
wAutoreconciliation has completed any exceptions are visible from the user interface. Automatic
s h
After
A reconciliation exceptions are bank statement lines and system transactions that remain unreconciled and
unmatched.
For each unreconciled statement line the application tries to provide a list of possible transaction matches.
Matching exceptions that are ambiguous (more than one matching statement line per system transaction)
and matches for which date and amount tolerance violations are identified, are considered possible
matches. If any possible matches have been identified, they are presented to the user in the exceptions UI.
Review the bank statement line and the appropriate matching system transaction, select, and reconcile.
After all exceptions are reconciled, run the Generate Cash Transactions process to created the external
cash transactions.
You can also view the status the reconciled payments in Payables.

Practice 13-7 Overview: Performing a Bank Statement Reconciliation
with Autoreconciliation
• Creating a Bank Statement.
• Submitting Autoreconciliation.
• Generating a Cash Transaction for Bank Charges.

• Viewing the reconciled payment in Payables.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Reporting and Analysis
The four key reports in Cash Management are:

• Cash to General Ledger Reconciliation Report
• Bank Statement Report
• Cash in Transit Report

• Bank Statement Analysis Report
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
• Cash to General Ledger Reconciliation Report:
@ in tLists u dethe subledger transactions that are
accounted in GL but are not reconciled
g r
a in Cash s S
Management.
• a
w bank t h i
s h
Bank Statement Report: Displays
s e account balances and transaction information for specific
bank statements.
a l (a to u
•
arw
Cash in Transit Report: s
n e for a specific bank account, all transactions that have been remitted
Lists,
g have e
to the bank
a
but
ic that have a reversal date on or before the effective date.
A transactions
l not been cleared. This report excludes all voided transactions. It also excludes
ry
all reversed
• waBank Statement Analysis Report: Displays bank statements used to analyze balances and
Ash transaction details.

Cash Management Infolets Overview
The Cash Management Dashboard infolets provide access to the relevant pages and
functions where you can address highlighted issues.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Navigate to: Cash Management Infolets
@ in tude
g r
a snapshot s S of your cash position, cash forecast, missing
As a cash manager, you can now view a concise
a h i
t status from the Cash Management infolets.
wreconciliation
h
bank statements, and bank statement
s s e
a l (a e to u
g arw cens
r y aA li
w a
As h

Cash Management Infolets
Infolet Name Description Icon
Provides visibility into overall cash balance across all of your

Cash Balance accounts.
Shows the number of bank accounts that are missing a bank

Missing Statements
statement.
Shows bank accounts which fail to meet their target balance.

At Risk
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
in sources
Use infolets to view information at a glance from different
@ t u de in an efficient and timely way directly from
the Welcome Springboard. You have the right
g r
a information
s S instead of just more data to sift through.
Mobile device support is available tow a h i
t on the go enabling you to see real time information.
take yourework
s h u s
a l (aCash Management:
Three Infolets are provided for
t o
• Cash Balance:
arwGives you
n e
svisibility into your overall cash balance across all of your accounts. The
g which the e
c infolets are the lastisknown
Aused onlithe
currency in amount displayed configurable and is indicated by the symbol. All the
y a
balances
r balances reported on the bank statements, where
a
w the last known balance is the balance code defined on the setup page.
s h
A • Missing Statements: The Missing Statements infolet shows the number of bank accounts that are
missing a bank statement. A bank account is included in the count on this infolet when the difference
between the last known bank statement date and the current date is more than the threshold
specified on the setup page.
• At Risk: You can set a target balance for each bank account to indicate the desired minimum
balance to maintain for the account. Bank accounts which fail to meet their target balance are
highlighted on the At Risk infolet. The expanded view shows the top five bank accounts in
descending order of variance highlighting the accounts which are most at risk. The blue portion of a
bar on the graph represents the current balance and the red portion represents the deficit for the
bank account. The currency used on the graph is the reporting currency specified on the setup page.
You can drill down from any of the infolets to the Cash Balances page where you can initiate transactions to
address any issues you notice.

Cash Positioning and Forecasting: Cash Balances
On the Cash Balances landing page, you can:

• See an overview of all your bank accounts.
• View highlighted bank accounts without up-to-date statements.
• Filter bank accounts on currency, bank, legal entity, and so on.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Navigate to: Cash Management > Cash Balances in
@ t u de
On the Cash Balances landing page you can g r
areviewiyour
s Sbank accounts balances, cash projections,
forecasts, and create transactions in w a t h
the CasheBalances
s h s work area.
uan overview of your bank accounts and you can also review the
The Cash Balances landingl page
a (a provides
t o
rw ebalance
variance of the bank account
ahighlighted. n e compared to the target balance. Any bank accounts not having up to
sYou
A
date statements are g l i c may filter the bank accounts displayed based on currency, bank, legal
a
entity, lastybank statement date, or balance ranges.
w ar
A s h
Any combination
querying at a
of filters used can be saved and are available on the Bank Account Group choice list for
later date.

Cash Position Page
• Shows the cash position for your bank accounts.

• Uses various data to determine projections.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ
m nt G c
ฺ i b
Navigate to: Cash Management > Cash Balances >
@ inView Cash t u dePosition
g r
a accountss S the current date on the Cash Position page. The
You can view the cash position for your bank
a
w se t h i for
h
projections on this page take into account:
s
• l (a e to u
Intraday statement data
a
• External cash w ns
arTransactions
• ManualA
a
g l ice
transactions.
w ary
Ash

5 Day Forecast Page
• You can use the information and data on the 5 Day Forecast page to assess the 5 day
forecast for your legal entities.
• This data helps you to manage liquid assets in the short term.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ inTaskstpanel
u detab > Cash Forecasting > 5 Day Forecast
You can assess the 5-day cash forecast forg r S based on the bank statement balances and
ayour legalisentities
a
w sPayables, h
t Payroll, and Receivables.
h
transactions entered in Cash Management,
s e
u in cash holdings, you can then plan short term liquidity
l (a or shortfalls
Based on the projected excesses
a t o
g arw
management activities se transfers or payments.
such as cash
e n
a A l ic
w ary
Ash

Transactions Cube
The Cash Balances work area uses a multidimensional database (Transactions cube) to
analyze:
• Bank account balances
• Bank statement lines

• Transactions affecting your cash positions
ble
fe r a
an s
n - t r
a no
Cash Management Transaction Cube in Smart View
) has eฺ
om uid
ฺ c
m nt G
ฺ i b e Currency, Currency Type, Source of
Ready to use dimensions include Bank, Legal Entity,
@ inBusiness
t u dUnit,
r
the Transaction, Reconciliation Status of theatransaction,Sand Flow indicator for the bank statement line.
w
g Accounting
aexisting t h is calendars on the Time dimension reducing the
The Transactions cube can re-use any
a s h use
setup required.
a ( to you can add new dimensions to the cube at any time.
l requirements,
w
r ens
For more complex analytics
a e
g ic and cube maintenance processes you can:
A setup pages
Using the flexible l
a
ry the existing cube
• aDelete
w
Ash• Add dimensions
• Extract data
• Recreate the cube
The cube maintenance processes also perform automatic updates when new bank statements are loaded or
external transactions created.
In the Transactions cube, you can perform ad hoc analysis in a spreadsheet using Oracle Hyperion Smart
View (Smart View).
Note: You cannot delete predefined dimensions.

Ready to Use Smart View Templates
• Review cash position for multiple bank accounts.

• Forecast short term cash projections for a bank account for any days/weeks/months.
ble
fe r a
an s
n - t r
a no
Ready to Use Smart View Template Report
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
To seamlessly investigate the source of the balances
@ in displayed
t u deon the reports:
• a r
Drill down to a page displaying thegcorrespondings Stransactions.
a h i
w fromseyourt cash position on this page. You can insight with
s h
You can exclude any of the transactions
udays/weeks/months/years.
a (a number
extended cash forecasts forl any
t o of
Manual Transactions
g arw cense
a
You can create AManual Transactions
li to quickly adjust cash projections by adding inflows or outflows for
a r y
transactions which are not available within the application. These transactions are saved to another
s h w
multidimensional database (Manual cube) you can view them at any time using Smart View.
A

Manual Transactions
• Adjust cash projections quickly.

• Save transactions to a Manual cube.
• View at any time with Smart View.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
You can create Manual Transactions to quickly adjust
@ de by adding inflows or outflows for
in cashtuprojections
r
a application.
transactions which are not available within the
gand s S These transactions are saved in a
w
multidimensional database (Manual cube) a t
youh i
can view the transactions at any time using Smart View.
h
s only for
aused e
usreporting purposes and have no accounting impact.
Note: Manual transactions are
l ( t o
a r wa nse
a Ag lice
w ary
Ash

Bank Account Transfers
Transfer funds between your bank accounts to:

• Maintain target balances.
• Meet financial obligations without overdraft.
• Deploy excess funds.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ de> Transfer Funds
inSelecttua row
r
a Transactions
gCash s S for the:
Bank Account Transfers generate External
a
w se t h i
• Provider bank account.
s h
• a l (a e to u
Receiver bank account.
These transactionsg rw ethensaccounting entries when reconciled with bank statement lines.
agenerate
a A leveragelicthe balancing rules provided by Oracle Intercompany to generate the accounting
ary for both the sender and receiver bank accounts.
The transactions
w
distributions
h can seamlessly process the transfer using the Payment Methods defined in Oracle Payables setup
AsYou
pages. You can configure flexible approval rules to authorize the transfers in Oracle BPM Worklist.
To enable the Bank Account Transfer assign the duty role Cash Positioning and Forecasting Management
Duty to a user.
Bank Account Transfer Guidelines:
Depending on the legal entities associated with the bank accounts, you can generate accounting
distributions using either the Intercompany Balancing Rules or the Secondary/Clearing Company Balancing
rules.
You must configure rules for either of these type of setups:
• For transfers between bank accounts belonging to the same legal entity.
• Between bank accounts belonging to different legal entities.

To distinguish your Cash Management balancing rules from others, Oracle recommends setting up
intercompany balancing rules with:
• Source as Cash Management.
• Category as Funds Transfer.
Bank Account Transfers which are settled through Payments are always routed for approval and you must
configure at least one approval rule for such transactions.
Additional configuration for Cash Management is available on Payment Methods and Payment Method
Defaulting setup pages. Only electronic payments are supported in
Release 11.
For additional information, refer to Bank Transfers and Ad Hoc Payments in Oracle Cash Management TOI.
ble
fe r a
ans
n - t r
n o
a
) has eฺ
ฺ c om uid
ฺ i b m nt G
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Ad Hoc Payments
• Address low-volume payments not associated with an invoice or purchase order.

• Use Payment Methods and options defined in Oracle Payables setup pages.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ de> Make a Payment
inSelecttua row
You can create and maintain payees whog
r
a theispayment
receive S without having to setup a supplier. You can
also define flexible approval rules to w a h
t transactions in Oracle BPM Worklist.
authorizeethese
s h s
l (a fortotheuAd Hoc payment generates the required accounting when
External cash transaction generated
a
reconciled.
g a rw ense
To enable and A
a ic payments:
create AdlHoc
ry the duty role Cash Positioning and Forecasting Management Duty.
• aAssign
h w
AsGuidelines
Ad Hoc Payments settled through Payments are always routed for approval and you must configure at least
one approval rule for these transactions.
Additional configuration for Cash Management is available on the setup pages related to Payment Methods
and Payment Method Defaulting.
The initial release of Ad Hoc Payments supports only electronic payment methods.
For additional information, refer to Bank Transfers and Ad Hoc Payments in Oracle Cash Management TOI.

Setup Options in Payments
In the Payments setup options, you can:

• Configure the setup options for payments for cash transactions.
• Specify whether you want to use a particular Payment Method for a certain type of cash
transaction.
• Configure the Payment Method Defaulting Rules for cash transactions.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b e
@ in tu> dPayments
Navigate to: Others > Setup and Maintenance > Financials > Manage Payment Method
g
When creating new users, assign the Payment
r
a duty irole
s SPayments Disbursement Administration Duty to
create setup options for payments. w a t h
s h s e
u Payments Disbursement Administration Duty role assigned.
a (a has
The Cash Manager job rolelalready t othe
g arw cense
r y aA li
w a
As h

Intraday Bank Statement Support
Use Intraday Bank activity to provide real-time cash flow information on your cash position
pages and reports.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Bank statement processing programs can now: in
@ t u de
• Handle intraday statement loads. ga r s S
a
w formats: t h i
• h
Provide native support for these
s s e
-
a l (a eV2to u
ISO20022 CAMT052
w nBAI2
arMT942,
SWIFT s
-
g c e
-a A i
EDIFACT lFINSTA
a r y
s h w
In the Intraday Bank Statement you can:
A • Upload either incremental or cumulative intraday statements.
• Create intraday statements manually.
• Use intraday statement search.
Enabling Intraday Bank Statements
If you can currently create intraday statements you also have the required duty and privilege to create
intraday statements.
When creating new users, assign the duty role Bank Statement and Reconciliation Duty to perform intraday
bank statement processing.
Note: You cannot load or create an intraday bank statement on a date which already has an existing prior
bank statement.
For additional information, refer to the Cash Positioning and Forecasting TOI.

External Transactions Overview
External cash transactions are transactions related to cash activity that has not been
recorded within the applications.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Navigate to: Cash Management > Bank Statements
@ t de > Tasks panel tab > External
inand Reconciliation
u
Transactions > Create Transaction
g a r s S
a
w are:se t h i
s h
The four sources of external transactions
u
• Manual Entry: Enterl an
a (aexternal
t o transaction directly in Cash Management.
• arw cecan
Import: Transactions
g nsbee created in a spreadsheet and uploaded through the import process.
•
a AtheTransactions:
Balancing
r y li Transactions created during reconciliation to record amount differences
w aor other charges.

between statement line and system transaction that may be due to bank fees, conversion rates,
Ash • Bank Statement: The bank statement transaction creation program enables you to configure rules
to create transactions from unreconciled statement lines to record items such as bank charges,
interest, or other miscellaneous items.
And External transactions created during:
• Bank Account Transfer
• Ad Hoc Payments.
• Reversal Reconciliations.

Reconciling Journal Lines For Multiple Cash Account Combinations
• Reconcile journal lines of multiple cash account combinations matching the same natural
account and other specified segment values.
• Previously, only journal lines created for the complete cash account combination were
available for reconciliation.
ble
fe r a
Enable
an s
Option
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b e Manage Bank Accounts task
in tu> dSearch:
Navigate to: Others > Setup and Maintenance > Financials
@
g
When performing bank account reconciliation,
r s S can manually or automatically reconcile all
a CashiManagers
a
w code t h
s h
journal lines entered on different account
s ecombinations matching the same natural account and sub-
Sub Account as GL Casha o u you're able to as

l a upeSegments,
account . For example, if you (set 01-000-1110-0000-000
t
your cash account, and select Account and
arw account
Account manually or automatically reconcile journal
g
lines entered on different
c e nscode combinations matching the same natural account 1110 and sub-
account 0000.
r y aA li
Thew a to General Ledger Reconciliation Report is also enhanced to display journal lines and closing
Cash
h
Asbalances of such cash account combinations.
Steps to Enable
1. Navigate to the Setup and Maintenance > Financials >Search: Manage Bank Accounts Task.
2. Create or edit the bank account.
3. Select Enable multiple cash account combinations for reconciliation option.
4. Select the GL Cash Account Segments you want to derive the corresponding segment values from the
bank account's cash account to retrieve multiple cash account combinations.
5. Save and close the page.
Tips
• You must have the Journal Reconciliation Enabled profile option (CE_GL_RECON_ENABLED) set
to ‘Yes' to perform manual and automatic reconciliation of bank statement lines directly from GL
Journal Lines.
• Consider using the GL Recon Start Date as a beginning date of journal reconciliation for the bank
account.

• The natural account segment is required and always selected as GL Cash Account Segment.
Review and select additional segments that qualify the bank account and you want to consider for
retrieving multiple cash account combinations.
• The closing book balance displayed in the Cash to General Ledger Reconciliation Report takes into
consideration multiple cash account combinations when this option is enabled for a bank account.
Role Information
No new role or privilege is required to set up and use this feature.
bl e
fe r a
ans
n - t r
n o
a
) has eฺ
ฺ c om uid
ฺ i b m nt G
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Summary

• Understand the key features of Cash Management.
• Define banks, branches, and accounts using the Rapid Implementation process.
• Configure Bank Statement Processing and Reconciliation.

• Perform Automatic Reconciliation.
• Describe the advanced features of Cash Management.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

14
Reporting for Payables, Payments,

and Subledger Accounting
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h
Objectives

• Describe BI Publisher Reports for Payables.
• Understand Oracle Transaction BI Reports for Payables.
• Discuss Infotiles for Payables.

• Describe BI Publisher Reports for Payments.
• Describe BI Publisher Reports for Subledger Accounting.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Predefined Reports
Predefined reports cover all major Oracle Cloud applications. These reports are:
• Oracle Transactional BI analysis.
• Oracle Business Intelligence Publisher (Oracle BI Publisher) reports.
• A few reports exist as both types, for example, the Payables Invoice Register.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ryaA li
w a
A s h

Payables
Oracle Payables provides predefined reports and infotiles for the following areas:
• Invoices
• Payments
• Payables to Ledger Reconciliation

• Period Close
• Prepayments
• Income Tax and Withholding
Some reports are defined as Oracle Business Intelligence Publisher (Oracle BI Publisher)
reports and others are defined as Oracle Transactional Business Intelligence reports. The ble
reports are secured by duty roles. fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ryaA li
w a
A s h

Payables BI Publisher Reports
Invoice Reports
Title Description
Payables Invoice Aging Report Lists unpaid invoices according to the specified aging periods.
Payables Invoice Register Provides detailed information about invoices.

Payables Key Indicators Generates reports with transaction activity and the current number of
Report suppliers, invoices, payments, and matching holds.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Invoice Reports
Title Description
Payables Matched and Modified Receipts Report Identifies receipts that were modified after
invoice matching.
Payables Matching Detail Report Provides details of how an invoice is matched to
a purchase order or receipt.
Payables Matching Hold Detail Report Provides detailed payables and purchasing
information for invoices with matching holds and
matching hold releases.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Invoice Reports
Title Description
Import Payables Invoice Creates Oracle Payables invoices from invoice

data in the open interface tables.
Validate Payables Invoices Report for the process that checks the
matching, tax, period status, conversion rate,
and distribution information for invoices. The
validation process also checks the tolerance
templates to determine if the invoice fall within
the defined tolerances and automatically applies
holds for exceptions.
ble
Supplier Balance Aging Report Report to generate a supplier aging balances
fe r a
based on a specific date, considering only
an s
accounted invoices in Payables and transferred
n - t r
to GL.
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Payment Reports
Title Description
Payables Cash Requirement Forecasts immediate cash needs for invoice payments.
Report
Payables Discounts Taken and Identifies payments where a discount was taken and payments
Lost Report where a discount was available, but not taken.
Payables Payment Register Provides detailed information about payments.
Payables Selected Installments Lists all invoice installments selected in a payment process
Report request to help determine how well the selection criteria is
selecting the right invoices to pay.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Payment Reports
Title Description
Payment Audit by Voucher Lists payments with assigned sequential voucher numbers.
Number Report
Update Matured Bills Payable Updates the status of matured bills payable from issued to
Status negotiable.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Period Close Reports
Title Description
Payables Open Items Lists changes in the value of open items, such as unpaid invoices
Revaluation Report and credit memos, due to conversion rate fluctuations.
Payables Period Close Lists exceptions that prevent the Oracle Payables accounting
Exceptions Report period from closing.
Payables Trial Balance Report Lists and subtotals by supplier and liability account, all unpaid and
partially paid invoices that Oracle Payables transferred to the
general ledger.
Payables Unaccounted Lists invoices and payments that were not accounted for a period
ble
Transactions and Sweep Report or date range.
fe r a
Prepayment Remittance Notice Lists prepayments that were applied to supplier invoices.
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Income Tax and Withholding Reports
Title Description
US 1096 Report Summarizes each United States1099 form type that is transmitted on
paper, as required by the United States Internal Revenue Service;
generates the summary on a preformatted Internal Revenue Service
form.
US 1099 Electronic Media Generates summarized United States1099 information in electronic

Report format, as required by the United States Internal Revenue Service.
US 1099 Forms – Comma Reports the total United States 1099 miscellaneous tax type payments ble
Delimited Format for 1099 suppliers in a comma delimited format.
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Title Description
US 1099 Invoice Exceptions Report Lists paid invoice distributions with inaccurate or
missing United States 1099 income tax
information.
US 1099 Payments Report Lists payments made to United States 1099
reportable suppliers.
US 1099 Report Reports the total United States 1099
miscellaneous payments for a particular 1099
supplier and generates 1099 forms for each tax
reporting entity in an organization.
ble
US 1099 Supplier Exceptions Report Lists suppliers with inaccurate or incomplete fe r a
United States 1099 income tax information.
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Title Description
Update and Report Income Tax Details Report from the process that updates or reports
income tax type or income tax region fields on
invoice distributions that are used for United
States 1099 reporting.
Payables Withholding Tax Letter Creates a withholding tax letter to mail to a
supplier on a periodic basis. The letter contains
a list of withholdings made for a supplier
summarized either by tax type and tax rate, or
by supplier site.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Payables Oracle Transactional BI Reports
The Invoices folder includes the following reports:

Title Description
Payables Credit Memo Matching Lists credit memos and debit memos for suppliers, along
Report with the invoices to which the credit memos and debit
memos are matched.
Payables Invoice Audit by Voucher Lists invoices with assigned sequential voucher numbers.
Number Listing
Payables Invoice Audit Listing Lists invoices for review and audit based on a specified
amount for a given supplier and range of invoice creation
dates.
ble
Payables Invoice Register Provides detailed information about invoices.
fe r a
an s
Payables Negative Supplier Balance
Report
Lists suppliers with negative balances, along with the
invoices and credit or debit memo transactions for the n - t r
balance. n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

The Payments folder includes the following reports:
Title Description
Payables Discounts Taken Identifies payments where a discount was taken and payments where
and Lost Report a discount was available, but not taken.
Payables Payment Register Provides detailed information about payments.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

The Payables to Ledger Reconciliation folder includes the following report:
Title Description
Payables to Ledger Lists the journals posted to the general ledger for open payables balances to
Reconciliation facilitate the reconciliation of accounting and transactional data recorded in
Report Oracle Payables and Oracle Subledger Accounting.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

The Period Close folder includes the following reports:
Title Description
Payables Posted Invoice Lists accounting lines for invoices that have been transferred to the
Register general ledger.
Payables Posted Payment Lists accounting lines for payments that have been transferred to the
Register general ledger.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

The Income Tax and Withholding folder includes the following reports:
Title Description
Payables Withholding Tax by Lists withholdings for tax codes assigned to a tax authority.
Tax Authority Report
Payables Withholding Tax Lists withholdings for a supplier. The invoice view is used to review
Report detailed withholding tax information by invoice. The supplier view is
used to review the withholding information for a range of suppliers.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Payables Subject Areas
Payables provides the following subject areas that you can use to create your own user-
defined reports.
Title Description
Payables Invoices – Holds Real Time Real-time information on holds applied to an invoice.
Payables Invoices – Installments Real Real-time information on invoice payment installments.
Time
Payables Invoices – Prepayment Real-time distribution information for prepayments
Applications Real Time applied to standard invoices.
Payables Invoices – Transactions Real Real-time information on invoices.
Time
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Title Description
Payables Invoices – Trial Balance Real Time Real-time information on posted invoices and
payments for reconciling the Payables balance

with the General Ledger balance.
Payables Invoices – Withholding Real Time Real-time information on summarized tax
amounts withheld at the supplier site level.
Payables Payments – Disbursements Real Time Real-time information on installments including
installment gross amount, amount paid, amount
remaining, and discount.
Payables Payments – Payment History Real Real-time information on clearing and unclearing
ble
Time history of payments.
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Payables folders in the Payables subject area include:

Dynamic Discounting Cross Functional

Reporting
One Time Payment

Invoice Image Routing
ble
Party Information
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Dynamic Discounting is Available in Payable Payment
@ t de Subject Area
in Disbursement
u
• g r
abeen addeds Sin the Invoice Paid Installments Details folder in
Dynamic discounting attributes have
a
w sSubject h i
t Area. This provides reporting on dynamic discounting
h
the Payables Payment Disbursement
s
a to u
terms such as annual (percent, days
e
accelerated, and early payment offer.
l
r wa Across
Cross Functional Reporting
a n sePayables Subject Areas
• Common g ic e
AInvoice lattributes across the Payables subject areas provide better cross functional
r y a
reporting among Invoice Holds, Installments, Payment Schedule, Payment, Prepayments and
a
w Payment Disbursements.
s h
A Invoice Image Routing is Available in Payables Invoices Subject Areas
• Invoice Image Routing attributes have been added in Payment Disbursements and Payables
Invoices Subject Areas including Invoice Holds, Installments, Prepayment Applications,
Transactions, Trial Balances. The attributes are available in the Invoice Details/Reference
Information folder.
One Time Payment Party Information is Available in Payables Subject Area
• One Time Payment Party information has been added in all Payables subject areas. Two payable
Party dimensions, Party and Party Site have been added to report information on one time payment
supplier details including person, organization, address, and site information.

Report on Active and Inactive Requestors in Payables Subject Areas
Report on both active and inactive requestors in the Payables Invoices - Transactions Real
Time and Payables Invoices - Prepayment Applications Real Time subject areas. You report
on requestors using the following Purchase Requestor columns:
• Purchase Requestor Name

• Purchase Requestor Last Name
• Purchase Requestor First Name
• Purchase Requestor Email Address
• Purchase Requestor Display Name
• Note: Previously only active requestors were included for reporting.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b e the Distributions folder, in the following
In the Invoice Distribution Details - Purchase Orderinsubfolder,dunder
r @ S t u
subject areas:
a g a i s
•
h w Real
Payables Invoices - Transactions
e t
Timeh
•
s u s
(a toApplications
Payables Invoices - lPrepayment Real Time.
Steps to Enable arw
a se
g e n
•
a
This feature ic
A is automatically
l enabled.
a r y
RolewInformation
h
As • No additional roles are required.

Cross-Functional Reporting Between Payables and Projects
• Payables subject area now supports Payables reporting by projects and contracts.
• In the Payables Invoices -Transactions subject area the Project Information folder now
includes information on:
– Project
– Expenditure type
– Task
• Users with the appropriate Projects subject area access can access the Projects
information in the Payables subject areas.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Payables to Ledger Reconciliation Drill-down Scalability
The Payables Reconciliation Difference

Details subfolder has been added to report
Payables reconciliation differences to
General Ledger.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Tables are added to the Subledger Accounting – Payables
@ de Real Time subject area to improve the
in tuSummary
r
ga drill-downs
performance of the GL reconciliation difference
s S to Payables.
a
w se t h i
s h
a l (a e to u
g arw cens
r y aA li
w a
As h

Payables to Ledger Reconciliation Report
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Navigate to: Payables > Payments > Tasks panel tab
@ t de > Payables to Ledger Reconciliation.
in > Accounting
u
g r
a for open s S
Lists the journals posted to the general ledger
w a ine t h i payables balances to facilitate the reconciliation of
ashdisplays
accounting and transactional data recorded Payables and Oracle Fusion Subledger Accounting.
(
One consolidated action linkl rapidly t o usthe transactions causing the difference, helping to prevent data
r wa nsummaries
mismatch between accounting
a se and difference drill-downs.
A g l ic e
a
w ary
Ash

Practice 14-1 Overview: Running a Payables Analysis Report

• Running the Payables Invoice Register report.
• Viewing the output.
• Exporting the output in Excel format.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Scanned Infotile for Payables Manager and Specialist
A Payables manager and Specialist can use the Scanned infotile to:
• Control processing of pending scanned invoices.
• Query an invoice to view the assignee.
• Provide missing information to complete the invoice.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
in tude
Navigate to: Payables > Invoices > Scanned infotile.
@
g
As a payable manager or specialist, you can
r
acontrolithe
s Sprocessing of scanned invoices that are pending in
a
w invoices h
tthat are pending action from a specialist are categorized
h
the scanned invoices queue. Incomplete
s s e
a l (a to u
into the following aging buckets:
• 0 -7 days
g a rw ense
• A
8-14 days
a l ic
• a15 ryplus days
w
h can query an invoice to view the assignee, and if required, you can take the appropriate action by
AsYou providing the missing information and completing the invoice.
In the details table, you can:
• Sort columns
• Query a specific invoice using the Query by Example icon
• Delete an incomplete scanned invoice
• Drill down to the Edit Invoice page using the Invoice Number link
To delete duplicate invoices, select multiple invoices using the Ctrl key and then delete them together.

Recent Infotile
• Manage invoices created or updated within last seven days.

• Review complete or incomplete invoices.
• Validate or Post to Ledger to complete the invoice.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Navigate to: Payables > Invoices > Recent infotile.in
@ t u de
g
The red slice in the chart indicates invoices
r
athat are iNot
s SValidated or Needs Revalidation (that is,
a
w se t h
incomplete).
s h u
a l (a that
The blue slice indicates invoices
e t o
are Validated or Canceled (that is, complete).
w
ar the
The details table displays ns
incomplete invoices at the top.
g c e
To review and
r y aA li invoice, use the Invoice Number link to drill down to the Edit Invoice page.
complete an
Youw a also:
can
h
As • Create a new invoice directly from the Recent information tile.
• Select multiple incomplete invoices and validate them together or delete or cancel them
simultaneously.

Holds Infotile
Use the Holds infotile to:

• Identify invoices on hold for any reason.
• Select a category to review the invoices and release the holds.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Use the Holds infotile to quickly identify the numberin
@ u
of invoices
t dethat have been placed on hold. Invoices are
grouped into three categories:
g a r s S
• a
w se t h i
Validation
s h
• Purchasing
a l (a e to u
• Other
g arw cens
a A to review
Select a category
r y li the invoices and quickly release the holds:
• aSelect the row containing the invoice you want to release.
s h w
A • Click the Release button.
• Select a Release reason.
• Click OK.
Note: You can select multiple invoices and release the holds together. Only releasable holds can be
released directly from the landing page.

Approval Infotile
Use the Approval infotile to review invoices that are:

• Pending your approval.
• Pending approval from others.
• Rejected.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Only accounts payable managers have access to the
@ in Approval
t u deinfotile.
r s S which has the invoices pending your approval.
ga ofthPending,
This information tile shows the default category
a
wthe Force i
In the Others category, managers
a s h
with
u s e Approve privilege can also force approve an invoice if the
Allow Force Approval optionl on
a ( the Manage
to Invoice Options page is enabled.
a w
r only
Note: This infotile displays
e
nifsInvoice Approval is enabled. If invoice approvals are not required, this
g c e
aA
infotile is not displayed.
r y li
w a
As h

Prepayments and Payments Infotile
Two payments infotiles are available:
• Prepayments display how many

prepayments are available for

application.
• Payments displays payments due in a week.
Query and make payments for
upcoming payments.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Prepayments Infotile
@ in tude
Use the Prepayments infotile to:
r
ga this S
a
w prepayments.
•
a s h
Gain better visibility into supplier
u s e
• Determine how many a l (prepayments
e to are available for application.
•
w ns
r oldereprepayment
Determine ifaan
A g l i c has not been applied yet.
•
a ya that a supplier is not overpaid.
Ensure
r
h w
Prepayments
s
are grouped into the following aging buckets:
A • 0-30 days
• 31-60 days
• 61 plus days
Payments Infotile
Use the Payments infotile to:
• Streamline your payment process by managing the invoices due in a week.
• Query and make payments for the installments coming due.
• Avoid late payments.
• Better plan your cash requirements.

Only accounts payable managers have access to the Payments infotile.
To pay an installment follow these steps:
1. Select the row with the installment.
2. Click the Pay button.
3. Enter the payment details in the dialog box.
4. Submit the payment.
The total amount due in one week is refreshed every hour. So if you make a payment in the infotile, you may
not see the amount changed immediately.
If you have access to multiple ledgers using different ledger currencies, the Payment infotile is not
displayed.
Only payment information for multiple ledgers that share the same ledger currency displays.
ble
fe r a
ans
n - t r
n o
a
) has eฺ
ฺ c om uid
ฺ i b m nt G
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Payments
Oracle Payments provides predefined disbursements and funds capture reports.

These reports are:
• Processes that result in a formatted file.
• Formatted using a specific template in Oracle BI Publisher.

• Manually generated, if opted, using the Scheduled Processes page.
• Automatically generated, if opted, using setup entities.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b e
inNo Oracle
Note: All Payment Reports are Oracle BI Publisher.
@ t u dTransactional BI reports are available in
Oracle Payments. r
ga this S
a
w se
s h
a l (a e to u
g arw cens
r y aA li
w a
As h

Run Payments Disbursement Reports Automatically
The following tables list disbursement reports with their corresponding processes that
automatically run after you enable specific options on the applicable page.
• The applicable process is called internally.
• Any required parameter values are known by Payments without your input or
intervention.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Report Process Description Output

Disbursement Payment File Creates an Document
Accompanying Letter Accompanying Letter accompanying letter for

Formats a payment file that your
company either prints
and mails to the bank,
along with the payment
file on a disk, or
manually transmits to
the bank, along with the
payment file.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h


Disbursement Positive Create Positive Pay File Creates a document Document
Pay File Formats that you transmit to your
payment system or bank

to inform it of payments
made by check.
Disbursement Send Separate Creates notices that can Document

Separate Remittance Remittance Advice be faxed, emailed, or
Advice Formats printed and mailed to
external payees; lists
the invoices ble
electronically paid to the
fe r a
payee’s bank account.
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h


Disbursement Payment File Register Creates a report displaying Document
Payment File Register the contents of a payment

Formats file, which your company
keeps for its records.
Disbursement Payment Process Request Creates a report that Document
Payment Process Status Report displays the contents and
Request Status status of a payment process
Report Formats request, which you review
online or print.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Run Payments Disbursement Reports Manually
Disbursement reports can be run manually or automatically.

Manual reports are run from:
• Payments page
• Scheduled Processes page

To illustrate:
• Click the Create Printed Payment Files link in the Tasks pane to open the Scheduled
Processes page.
• Select the applicable parameters.
• Submit the process, which results in printed checks. ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Payments Funds Capture Reports
Oracle Payments provides the following funds capture predefined reports:

• Funds Capture Accompanying Letter Formats
• Funds Capture Payer Notification Formats
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Run Payments Funds Capture Reports Automatically
An example of automatic submission of a funds capture report is the Formats tab on the
Create Funds Capture Process Profile page with the Automatically submit at settlement
check box selected in the Notification to Payer section.
• Selection of this check box results in the automatic submission of the Funds Capture
Payer Notification Formats.
• After the create settlement batches process is complete, Payments automatically
creates payment notifications that are sent to external payers to inform them that
payments have been made.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

The following tables lists funds capture reports that are automatically submitted.
• The applicable process is called internally, not by the user from a user interface.
• Any required parameter values are known by Payments without user input.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h


Funds Capture Payer Send Receipt of Payment Creates payment notifications Document
Notification Formats Notifications that can be faxed, e-mailed,
or printed and mailed to
external payers after the
settlement or settlement
batch is transmitted to inform
them of a funds capture
transaction that charges their
credit card or bank account.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h


Funds Capture Settlement Batch Creates an accompanying Document

Accompanying Letter Accompanying Letter letter for a direct debit
Formats settlement batch file that your
company either prints and
mails to the bank, or
manually transmits to the
bank, along with the
settlement batch file.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Run Payments Funds Capture Reports Manually
Funds Capture reports can be run manually or automatically. Manual reports are run from
the Funds Capture page or from the Scheduled Processes page.
To illustrate:
1. Click the Create Settlement Batches link in the Tasks pane to open the Scheduled
Processes page.
2. Select the applicable parameters.
3. Submit the process, which results in settlement batches that are submitted to your
payment system or bank.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Navigator > Receivables > Funds Capture > Createin
@ Settlement
t u deBatches
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
r y aA li
w a
As h

Payments Subject Areas
Oracle Payments has no predefined Oracle Transactional Business Intelligence reports, but
you can create your own user-defined reports using the predelivered Payables subject areas
that reference payments:
Title Description
Payables Payments – Disbursements Real Time Real-time information on amount spent or
expensed.
Payables Payments – Payment History Real Real-time information on clearing and unclearing
Time history of payments.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Subledger Accounting
Oracle Subledger Accounting provides accounting reports for fiscal and internal control
purposes.
These reports include subledger journals from:
• Oracle Subledger Accounting (SLA)

• Oracle General Ledger journals for sources such as allocations and revaluation that do
not originate within General Ledger.
The reports are:
• Comprehensive from a financial standpoint.
• Include the best source of information for each type of journal entry.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
These reports can therefore be used in lieu of the General
@ de
in tLedger-based
u journals and account analysis
reports if you need to see detailed subledger r
gajournal S as well as supporting transaction information.
entries
s
a
w se t h i
s h
a l (a e to u
g arw cens
r y aA li
w a
As h

Subledger Accounting Predefined Reports Overview
Oracle Subledger Accounting provides predefined accounting reports for fiscal and internal
control purposes.
• Account Analysis Report
• Accounting Event Diagnostic Report

• Journal Entries Report
• Subledger Period Close Exceptions Report
• Third Party Balances Report
• Subledger Accounting Method Setups Report
• Create Accounting Execution Report ble
• fe r a
Supporting References Report
an s
• Multiperiod Accounting Execution Report
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Note: No predefined Oracle Transactional Business
@ t deReports exist for Subledger Accounting.
inIntelligence
u
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
r y aA li
w a
As h

Subledger Accounting BI Publisher Reports
The following benefits have been added to the Account Analysis and the Journal Entries
reports:
• Report extracts include reconciliation information for clearing accounts.
• BIP templates can be customized to list the clearing account reconciliation details.
Title Description
Account Analysis Report Provides drill down information about the movement on a particular
account for a period or range of periods for posted journal entries.
Accounting Event Analysis Shows the transaction data used in accounting. The data is collected
Report when the profile option SLA: Enable Diagnostics is set and the Create
ble
Accounting process is run.
fe r a
Journal Entities Displays detailed information for subledger and general ledger journal
an s
entries; groups report by ledger, journal source, journal category, and
n - t r
event class at submission.
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Title Description
Subledger Period Close Lists all accounting events and journal entries that fail period close
Exceptions Report validation. Reasons for failure include incomplete transactions,
unprocessed accounting events, invalid journal entries, and journal

entries that have not been transferred. Groups report by ledger,
period, journal source, journal category, and event class at
submission.
Third-Party Balances Report Displays subledger balance and account activity information for
suppliers and customers.
Subledger Accounting Displays the accounting setups for a subledger application and
Method Setups Report accounting method.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Title Description
Create Accounting Execution When you submit the Create Accounting process, the Create
Report Accounting Execution Report is submitted automatically if the
Create Accounting process completes with a success or warning
status. The Create Accounting process output contains a message
with the Create Accounting Execution Report request identifier. Use
this request identifier to retrieve the execution
report output.
Multiperiod Accounting When you submit the Create Multiperiod Accounting process, the
Execution Report Create Multiperiod Accounting Execution Report is
ble
submitted automatically if the Create Multiperiod Accounting
process completes with a success or warning status. The report fe r a
displays entries created by the Create Multiperiod Accounting
an s
process.
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Subledger Accounting Subject Areas
Subledger Accounting has no predefined Oracle Transactional BI reports. You can use one
of the two subject areas to create your own custom reports.
Dimension folders are added for Sequences and Supporting Reference to report supporting
documents and supporting reference balances.

To simplify the subject area, code columns, such as balance type code and fund status
code, are hidden in the subject area. Instead customers can use related description columns
for these code columns for reporting.
Any existing reports that use these hidden code columns will continue to function. These
description columns have Double Column feature enabled that automatically supports
Multilanguage translation in string filtering.
ble
Title Description
fe r a
Subledger Accounting – Journals Real Time a n s
Real-time information on accounting detail journals.
Subledger Accounting – Supporting n -t r
o
Real-time information on subledger transaction
n
References Real Time supporting reference details.
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
r y aA li
w a
A s h

Practice 14-2 Overview: Running a Subledger Accounting BI
Publisher Report
• Submitting the Journal Entries report.
• Viewing the Journal Entries report.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Summary

• Describe BI Publisher Reports for Payables.
• Understand Oracle Transaction BI Reports for Payables.
• Discuss Infotiles for Payables.

• Describe BI Publisher Reports for Payments.
• Describe BI Publisher Reports for Subledger Accounting.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

As h w a
ry
aA
g li
a
s
arw cens
h
a
l (a e to u
r
w se
@
ฺ i b
ga this S
ฺ c
in tude
)
m nt G
om uid
a
has eฺ
o n n
- t r an
sfe r a bl
e
A
Common Application Topics

ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h
Objectives

• Manage Oracle Social Network Objects.
• Define Flexfields.
• Define Lookups.
• Define Profile Options.
• Define Attachments.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h
Oracle Financials Cloud: Payables to Cash Management Implementation A - 2

Manage Oracle Social Network Objects
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
To manage Oracle Social Network objects, use thein
@ u de Social Network Objects task in the
Manage Oracle
t
Setup and Maintenance work area.
g a r s S
a
w se t h i
s h
Enabling Business Objects for Integration
u about a business object, such as benefit plans or sales
• l (a information
You can determine whether
a t o
g a n senetwork.
rw inesocial
accounts, appears
• A an object
If you enable
a l ic for sharing, users can collaborate on the object through social networking.
a r
You y can choose whether all instances of an object are shared, or only at the user's discretion. You
s h w can also choose which attributes are shared, such as names and details, and who made the last
A update.
• To open the Manage Oracle Social Network Objects page, start on the Setup and Maintenance
Overview page and search for the Manage Oracle Social Network Objects task.

Enablement Options
The following enablement options are available for enabling social network objects on the
Manage Oracle Social Network Objects page:
• Manual
• Automatic
• No
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
• Manual: (Recommended) Lets users decide
@ inwhether t u deshare each instance of the object with the
to
social network. When shared, all updates r
ga that to the S
s enabled attributes of the instance appear on the
social network. If the instance isa
w deleted, t h i information is also shared.
a s h
Note: Click Enable All to enable
u
all s e
objects for all applications. Enable All automatically applies the
Manual option, which (
al means o
t the user can choose whether to share an object instance.
that
r w s e
• Automatic:a
A l i c en about all instances of the object appears on the social network, including:
g Notifications
a ry-- a Every newly created instance
s h w All subsequent updates to the enabled attributes

A - Deletion of any instances
• No: (Default value) No notifications about the object appears on the social network.
• Note: When you click Disable Object, the enabled setting of the selected business object is
automatically changed to No.

Enablement Options
After you enable an object, you must enable one or more attributes of the object.
• Only the enabled attributes are shared.
• The Status column in the Business Objects table indicates which enabled business
objects have or do not have enabled attributes.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
For business objects with no enabled attributes, only
@ t de information appears on the social
inthe following
u
network:
g a r s S
• a
w when h i
t create or update an instance of the object.
s h
Internal bookkeeping information
u s e you
• News that an instance
a l (isadeleted.
t o
g arw cense
r y aA li
w a
As h

Update Social Network Translations
Use Update Translations on the Manage Oracle Social Network Objects page for
subsequent updates to labels and attributes.
For example, if a new language pack is installed in Oracle Applications Cloud, click Update ble
Translations to send the updated labels and their translations to social network. fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Use Update Translations at the:
@ in tude
• g r
atranslations
s Sfor a selected business object to social network.
Business Objects table level to send
a
w yousselect h i
t a row for a business object with the enablement option
h
This button is enabled only when
s e
as Manual or Automatic.
a l (a to u
• Manage Oraclew
ar option e Objects page level to send translations for all business objects with
sManual
Social Network
n
A g
the enablement
l ic eas or Automatic to social network.
r
Note: When a
y you save the enablement of a business object, Update Translations sends the translations. You
a
wneed to click Update Translations after saving the enablement.
don’t
s h
A When you click Update Translations, you:
• Send translations for all business objects with enablement as Manual or Automatic to social network.
• Synchronize the newly translated text from Oracle Applications Cloud so that it can be used within
social network. This means that you can:
- Install and enable a new language.
- Take a language patch at any time.
• Send attribute labels and business object names to social network for use in its user interface.

Update Translations
Note
• In social network, the attribute or business object labels appear in the language of your
locale. If you change the locale, then these labels appear in the updated language.
• The data appears in the language in which it was originally sent to social network.
• If you have previously sent an instance of the business object to social network, then the
instance data is not updated even when you click Update Translations.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ryaA li
w a
A s h

Demonstration A-1: Managing Oracle Social Network Objects
This demonstration covers the following topic: Enabling Oracle Social Network objects on
the Manage Oracle Social Network Objects page.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Oracle Social Network Reference Resources
Related Resources:
• Oracle Cloud Applications Common Implementation Guide
• https://osn-fusioncrm.oracle.com/osn/web/help/index.html?locale=en
• https://cloud.oracle.com/mycloud/f?p=service:socialnetwork_faq:0
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ryaA li
w a
A s h

Define Flexfields
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Manage Flexfields
To manage flexfields, use the Define Flexfields tasks in the Setup and Maintenance work
area.
A flexfield:
• Provides a means to customize application features without programming.

• Extends a business object with additional data fields to capture enterprise information.
• Consists of segments representing different data or values.
• Stores data in database table columns, one for each segment.
• Appears to end users as attributes of information.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Types of Flexfields: Descriptive
Flexfield Type Description Examples

Descriptive Optional customizable • Components of a student's contact
expansion space in the user information.
interface for additional • Tracking asset specifics, such as the

information. number of floors, square footage, and
date of insurance renewals.
Extensible Similar to descriptive A list of countries where an electronic item
flexfields, but with is compatible based on country-specific
advanced capacities such standards such as power line frequency
as categories. and item attributes such as signal
resolution.
ble
Key Mandatory key for • Unique item numbers.
fe r a
identifying business entities • Account numbers.
an s
using an enterprise-defined • A composite key that collates location,
n - t r
code. n price, and shipping time. o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Flexfield Concepts
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
in youtucandedisplay in the user interface as fields. The
A single flexfield can capture multiple attributes, which
@
figure shows several fields added to an order r
a page
gand S a part number key flexfield, and additionally a
by defining
s
w a
descriptive flexfield for capturing part type t h
sales i representative information.
h
as to us e
l (
a r wa nse
a Ag lice
w ary
Ash

Flexfield Segments
• Represent attributes of entities (business objects)

• Can appear:
– Based on a structure or context.
– Globally wherever the flexfield is implemented.

• Can be made available to an application as groups of attributes called contexts.
• Can be assigned a value set that determines which values are valid for the segment.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b e can accommodate descriptive flexfields
Of the business objects that are defined to include ianflexfield, d
r @ t u some
S at the discretion of application development.
and others accommodate extensible flexfields
a g a or keyisflexfields,
h
Flexfield attributes are available across e t h
w the deployment, such as in Web Services, Oracle Business
s s
u Development Framework, and Oracle Cloud Search. Any
a l (awith
Intelligence, desktop integration Application
t o
e include flexfield
a r w reports
UI page presenting the business
n
object
s includes the flexfield attributes that extend the business object.
A g lice
Oracle Business Intelligence attributes.
a rya
s h w
A

Flexfield Structure
A flexfield structure is:

• Only relevant to key flexfields.
• A specific configuration of key flexfield segments.
• Composed of one or more instances each of which:

– Contains the same number and order of segments.
– Differ in the allowable values or value sets attached to the segments.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Flexfield Context
A flexfield context is:

• Relevant only to descriptive and extensible flexfields.
• A grouping of attributes that makes segments available to an application.
• A set of context-sensitive segments that stores a particular type of related information.

Note:
– Descriptive flexfield segments can be context-sensitive.
– Extensible flexfield segments must be context-sensitive.
• A way of reusing the same database column for a similar or different segment based on
different needs.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Flexfield Category
• Relevant only in extensible flexfields.

• A grouping of contexts.
• A hierarchy of categories.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Flexfield Usage
• Is set when application development registers the flexfield.

• Specifies the application and table the flexfield is associated with.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Accessing Flexfields for Configuration
To configure a flexfield, access it in one of the following ways:

• Using the Highlight Flexfields command.
• Accessing flexfield management tasks and searching for flexfields.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Using the Highlight Flexfields Command
In highlight mode, you can use the:

• Information icon to access details about the flexfield.
• Configure the Flexfield icon to add segments and configure them with advanced options
on segments.
• Add Global Segment icon to add global segments with common options for descriptive
flexfields.
• Add New Context icon to add context values for descriptive flexfields.
• Add Context-Sensitive Segment icon to add context-sensitive segments with common
options for the selected context value of the descriptive flexfield.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
in tumenu
Use the Highlight Flexfields command in the Administration
@ de of the Setup and Maintenance work area
r
ga thpage.
to identify the location of flexfields on the run-time
sS
a
w se i
s h
a l (a e to u
g arw cens
r y aA li
w a
As h

Accessing Flexfield Management Tasks and Searching for Flexfields
Use the flexfield management tasks in the Setup and Maintenance work area. From the task
list, search for Define Flexfields on All Tasks tab.
Tip: Use the Business Object parameter to search Application Key Flexfields, Application
Descriptive Flexfields, and Application Extensible Flexfields to find all tasks related to
flexfields.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Note: To access tasks for configuring flexfields andin
@ u
value sets,
t deyou must be provisioned with roles that
r S for managing product-specific flexfields. Contact
a list oristasks
entitle you to access the Define Flexfields task
ginformation
w a
your security administrator for details. For t h about product-specific flexfield tasks, such as Manage
a
Purchasing Descriptive Flexfields,s h
consult
u s
theeproduct-specific documentation in Oracle Cloud Applications
Help. (
al se t o
r w
A ga licen
a rya
s h w
A

Accessing Flexfield Management Tasks and Searching for Flexfields
To manage any flexfield across all Oracle Cloud Applications products, search for the Define
Flexfields task list and access the following tasks:
• Manage Descriptive Flexfields
• Manage Extensible Flexfields

• Manage Key Flexfields
After searching for and selecting the required flexfields, you can use the Configure Flexfield
icon to view and configure the flexfields.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Value Sets
• A set of values assigned to a flexfield segment or other entity outside of flexfields.

• The basis of validation for a value entered into a flexfield segment by an end user.
• Defined before you configure the key flexfield, because you assign value sets to each
segment when you configure the key flexfield.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Security on Value Sets
@ in tude
• Set up segment value security rules g r
aon valueissetsSto control access to parent or detail segment
w a th
h
values for your chart of accounts
asinquiry, e
segments.
us reporting.
• l (
Restrict data entry, online
a svalue t o and
•
a r
Create and edit wsegment n e security rules on the Define Chart of Accounts page from the Setup
A g
and Maintenance
lworke
ic area.
Note: a
You
a
rycan create value sets when you create or edit descriptive and extensible flexfield segments.
w
h you use the Add Global Segment and Add Context-Sensitive Segment icons in Highlight Flexfields
Asmode,
When
value sets are created automatically when a segment is created.

Value Sets
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
in flexfield
The figure shows a value set being used for a descriptive
@ t u de segment.
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
r y aA li
w a
A s h

Value Set Validation
Validation Types Description

Format only End users enter data rather than selecting values from a list.
Independent The list of values consists of valid values you specify.

Dependent A valid value in a list of values derives from the independent value of
another segment.
Subset The list of values is a subset of the values in an existing independent
value set.
Table The values derive from a column in an application table, which can
optionally be limited by a WHERE clause.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Value Set Usage
• Specifies the segment where the value set is assigned.

• Indicates which flexfields use a shared value set.
You can use value sets additionally for supplying values to regular user interface fields, such
as in Oracle Cloud Contracts.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
in ortuyou
If your application has more than one language installed,
@ demay install one or more additional
languages for your application in the future,a r S
select Translatable.
gcannot s If you select Translatable, you do not need
w a
to provide translated values now, but you t h i
change this option if you decide to provide them later.
h
as to us e
l (
a r wa nse
a Ag lice
w ary
Ash

Descriptive Flexfields
A descriptive flexfield:
• Is often optional.
• Provides a way to add custom attributes to entities and define validation and display
properties for custom attributes.

• Is enabled for most business entities.
• Consists of segments that are made available to end users as individual fields in the
application user interface.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Descriptive Flexfields: Segments
• Correspond to custom attributes of entities.

• Are generally standalone and need not be related or treated together with other
segments as a combination.
• Are of the following types:

– Global segment, which is always available.
– Context segment, which determines the context-sensitive segments that are
displayed.
– Context-sensitive segment, which is displayed depending on the value of the context
segment.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Descriptive Flexfields: Context Segment
• Need not be assigned a value set.

• If assigned a value set, you can use only table-validated or independent value sets.
• Note
– The data type must be character.

– The maximum length of the values being stored must not be larger than the column
length of the context.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Descriptive Flexfields
The number of segments available for configuring is determined by the number of columns
reserved by application development to store segment values. During implementation,
determine which attributes to add using the:
• Available columns
• Context values
• Combination of attributes in each context
The same column can be used for attributes in different contexts, such as Height in
Context1 and Color in Context2.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b e values allowed for the segment and how
inconfigure
For each global and context-sensitive segment, you
@ t u dthe
r
ga be
the values that are entered by end users should S including interdependent validation among the
validated,
s
segments. a
w se t h i
s h
a l (a e to u
g arw cens
r y aA li
w a
As h

Adding Flexfield Segments on Application Pages
For adding segments and configuring them with advanced options on segments (such as
change a segment’s sequence number, or configure a descriptive flexfield segment’s
business intelligence label), use the Configure Flexfield icon.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

To configure segments with common options, use the following icons on an application page
where descriptive flexfields are highlighted:
• Add Global Segment: To add global segments for descriptive flexfields. Global segments
are always relevant, irrespective of context values.

• Add New Context: To add context values for descriptive flexfields.
• Add Context-Sensitive Segment: To add context-sensitive segments for the selected
context value of the descriptive flexfield.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
• The context segment immediately precedesin
@ t u
the Add New deContext icon.
• The values that you add using theg Addr s S icon appear in the drop-down list of the context
a New iContext
segment after you refresh thew a t h
s h page.
s e
u the context drop-down list, and then use the Add Context-
• l (a valuetofrom
You must select a context
a
rw icon
Sensitive Segment
a n e a segment specific to that context value.
tosadd
• You must g
Aicons:
sign out iand
l e
c sign in to the application again to view the changes you make using the
a
w ary- Configure Flexfield
following
Ash - Add Global Segment

- Add Context-Sensitive Segment

When you use the Add Global Segment and Add Context-Sensitive Segment icons:
• You must accept the automatically set:
– Segment code
– Name and description

– Table column
– Sequence number
• You must accept the automatically created value set.
• You can enter valid values, including:
– Valid values descriptions
ble
– The default value
fe r a
– Formatting constraints for the value set, such as minimum and maximum values
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Depending on the display type, the value set created
@ deGlobal Segment and Add Context-
inby thetuAdd
r S
a valueissets:
Sensitive Segment icons is one of the following
g
• a
w se t h
An independent value set
s h
• (a to u
A format-only value lset
a
g arw cense
r y aA li
w a
As h

The following table shows which type of value set is created depending on the display
component you select:
Display Component Type of Value Set

• Check box Independent
• Drop-down List
• List of Values
• Radio Button Group
• Pop up List of Values
• Text Box Format Only

ble
• Text Area
fe r a
• Date and Time
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Extensible Flexfields
Extensible flexfields are like descriptive flexfields, with some additional features.
With extensible flexfields, you can:
• Have multiple groups of custom attributes attached to a single entity. Each group of
custom attributes is a context. In addition, different entity rows can have different groups
of attributes (or contexts) based on the value of the category. This is in contrast to
descriptive flexfields for which the attributes vary based on the context.
• Add as many context-sensitive segments to the flexfield as you need. You are not limited
by the number of segments predefined and registered for the flexfield.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

• Configure a one-to-many relationship between the entity and its extended attribute rows.
• Configure attributes in contexts, which serve as groups of attributes. Attributes in a
context appear together in the user interface.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Extensible Flexfields Context
• Can be defined as single-row, meaning a one-to-one relationship between the entity and
its extended attribute rows.
• Can be defined as multirow, meaning a one-to-many relationship between the entity row
and its extended attribute rows.

• Can be set to store translatable free-form text values.
• Is reusable throughout extensible flexfield categories.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

• An extensible flexfield category enables you to:

– Use the category value (that each entity row has) to determine which attribute groups
(contexts) apply to the row.
– Assign different combinations of contexts to different categories to capture different

information about different entity rows.
• An extensible flexfield page:
– Combines contexts into a group that is presented together in the application user
interface.
– Corresponds to one extensible flexfield category, with a separate section of the page
for each associated context.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Note
@ in tude
g r
a categories
s Sin a hierarchy. When you use hierarchical
For some extensible flexfields, you can define
a h i
t that are:
w fromscontexts
h
categories, the entity displays attributes
s e
• Directly associated with
a t ou
l (atheecategory
• arwcategories
Defined in parent
g c e ns of the category
r y aA li
w a
As h

Extensible Flexfield Example
You can specify whether end users can enter one set of data or multiple sets of data for a
context.
For example, if you have a job positions entity that stores information about different
positions in your organization, you can configure additional contexts that store a list of
requirements for that position.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

To start with, the job positions entity includes fields for the following attributes:
• Position ID
• Position code
• Description
• Department
• Location
• Hiring status
• Whether the job is permanent or temporary
• ble
Whether the job is full-time or part-time
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

• You then can extend the list of job positions to capture the following classes of attributes:
– Educational requirements, such as degrees
– Certifications and licenses required for the position
– Travel required for this position
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b e group of custom attributes. Setting up
in ttoudeach
Implement this by setting up context values corresponding
@
context values means specifying segments a r
g forineach s S such
context, as various degrees in an educational
w
requirements context and various credentialsa ath i
certification and license requirements context. You set up
a
a job position category that containss h u s
the threeecontexts for the three classes of attributes you want to
capture, and set up a pagea lfor( thatecategory.
to
w
ar cens
g
r y aA li
w a
As h

ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
in theytuseedethe additional attributes. When users define
When users create a job in the job positions category,
@
r s Scredentials, and travel required by the position.
ga thilevel,
job position requirements, they select the education
a
w se
s h
a l (a e to u
g arw cens
r y aA li
w a
As h

Key Flexfields
A key flexfield:
• Provides a means of capturing a key, such as a part number, a job code, or an account
code that represents an entity in your application.
• Consists of one or more segments, where each segment can have a meaning.
• Is not optional and must be configured to ensure that your applications operate correctly.
• Is provided by applications development and is configured and maintained with the
Manage Key Flexfields task.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Key Flexfields
• Have one corresponding combinations table containing the complete codes or

combinations of segment values that make up the codes.
• Can be used in different ways on different pages:
– Combination maintenance page, where users maintain individual combinations

directly.
– Foreign key page, where users manipulate rows containing code combination IDs
(CCID).
– Partial usage page, where users may be presented with only parts of the
configuration based on a product’s transaction table.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Key Flexfield Structure
• Defines the following segment options:

– What segments to include
– Number of segments
– Segment sequence
– Segment labels where applicable, for example, natural account and primary
balancing in general ledger
– Value sets
• Sets the maximum number of segments allowed in your key flexfield combinations table.
• Allows one or more alternate structure instances that can have different value sets.
• ble
Includes a delimiter to visually separate segment values when the key flexfield is
fe r a
displayed in the user interface.
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Key Flexfield Instances
All key flexfield structure instances:

• Contain the same:
– Set of segments
– Arrangement of segments
– Properties at the segment and structure levels
• May differ in whether dynamic combination creation is allowed, which means a valid
combination is inserted into a combinations table from a page other than the
combination maintenance page.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Key Flexfields
Key flexfield segment instances in a key flexfield structure instance may differ in the
following aspects:
• Value set
• Default type and default value

• Tree code defining a hierarchical relationship to other segment values of a key flexfield
registered with a tree structure
• Whether the segment is any of the following:
– Required
– Displayed
ble
– Enabled for business intelligence
fe r a
– Optional or required as a query criterion in a key flexfield combination search
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Key Flexfields
The predefined key flexfields are:

• Account Alias Flexfield
• Accounting Flexfield
• Asset Key Flexfield

• Budgeting Flexfield
• Category Flexfield
• Cost Allocation Flexfield
• Item Categories
• Location Flexfield ble
• fe r a
Locator Flexfield
an s
• People Group Flexfield
n - t r
• n o
Valuation Unit Flexfield a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Tips for Managing Key Flexfields
• When you configure a key flexfield, define metadata about the key flexfield, such as how
many segments are in a structure, how many structures the flexfield uses, and what
value sets each segment uses.
For example, you can use one group of value sets for the US and another for France.
• You must add segments in the order that your key requires. After they are deployed, the
order can’t be changed.
• If you change the configuration of a key flexfield, such as the delimiter, the change
affects the previously stored key flexfields with that structure.
• Enable segments to indicate that they are in use and appear at run time.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Tips for Managing Key Flexfields
• Don’t change the number, order, and maximum length of segments after you have
acquired flexfield data.
• To protect the integrity of your data, disable a segment if you have already used it to
enter data.
• You can dynamically create account code combinations when entering data by enabling
dynamic insertion on the Key Flexfield Instance page.
• At any time, enable or disable allowing dynamic combination creation.
• Define cross-validation rules to ensure that the dynamic combination creation process
doesn’t create incorrect account combinations.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Flexfield Implementation Flow
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
n tudand e deploying flexfields. Applications
Managing flexfields involves registering, planning, iconfiguring,
r @
s Sand implementors configure flexfields and
gauserthinterface.
developers develop and register flexfields. Administrators
a i
s h w se
optionally customize their appearance in the
a l (a e to u
g arw cens
r y aA li
w a
As h

Flexfield Implementation Flow
There are two types of deployment:

• A sandbox-enabled flexfield for testing flexfield behavior in a sandbox MDS repository
that is accessible only to the administrator who activates and accesses it, not to users
generally.
• A mainline-enabled flexfield for applying the flexfield definition to the mainline MDS
repository where it is available to end users.
After deploying the flexfield to the mainline, you can customize the page where the flexfield
segments appear.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Flexfield Reference Resources
Related Resources:
• Oracle Cloud Applications Implementing Common Features
• Oracle Applications Cloud Extending the Applications
• Oracle Cloud Applications Developer's Guide

To view flexfields in the Oracle Enterprise Repository, see
https://fusionappsoer.oracle.com/oer/.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Define Lookups
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Sample Lookup Type
Lookup Type Lookup Code Meaning Tag Enabled
TICKET_CLASS ANY Any class Any 

depending
upon availability
BUSINESS Business class Business 
FIRST First class First 

Economy ble
ECONOMY Economy class 
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Per the settings shown in the table, users would see
@ t de values in the list on the application UI to
inthe following
u
determine the ticket class:
g a r s S
• a
w se t h i
Any
s h
• Business
a l (a e to u
• Economy
g arw cens
r y aA li
w a
As h

Lookup Components
• Lookup Type: A static list of values that users use to make entries in the application.
• Lookup Code: An internal application code for each lookup that is not visible to users.
• Meaning: The actual UI term that appears in the lookup list of values.
• Tag: A label associated with the lookup.

• Enabled: A status that determines the availability of the meaning within the selection list
for the lookup type.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
• Lookup Type: This is the name of the fieldithat
@
n appearst u deon the setup UI and not on the application
UI where you make the selection. a
g r s S
• Meaning: The actual UI termw a h i
t the lookup code. It is the item that appears in the list
s h
a to u s e
associated with
l (
on the application UI against the specific field name, and can be selected by users to indicate their
choice.
a r wa nse
•
Ag product
Tag: Certain
a l iceofferings use lookup tags for functionality that is specific to that product. Refer
ry
to the product offering
adocumented,
specific documentation for more information. If no such use of tag is
h w the tag is ignored.

As • Enabled: If you do not enable it, the value does not appear in the selection list at run time.

Lookup Categories
• Standard Lookups: Consist of lookup codes and their meanings.

• Common Lookups:
– Available for internal system administrative use.
– Used by more than one application.

• Set-Enabled Lookups: Contain lookup codes that are part of a reference data.
– Use sets to enable various values in the lookup for different sets of users.
– Select an attribute at run time to determine which set-enabled lookup is visible to the
users.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
• An example of a Set-Enabled Lookup: The iattribute
@ de or west-coast in the location
n tueast-coast
r
g this S or the west-coast location, depending on the
determinant determines whether it isathe east-coast
selected lookup. a
w se
• s h
a to uare valid within a specified date range. If a date range is not
Lookup codes and their
l ( meanings
a r wa codes
specified, the lookup
n s eand meanings have indefinite validity from the time they are created.
a Ag lice
w ary
Ash

Manage Lookups
• Define the three types of lookups in:

– Standard view
– Common view
– Set-enabled view
• Lookups are:
– Enabled
– Associated with a module
– Striped by application taxonomy to provide a criterion for narrowing a search or
limiting the number of lookups accessed by a product-specific task such as Manage
Purchasing Lookups
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
You can create new lookup types and also add new
@ de and meanings to the existing lookup
inlookuptucodes
types, depending on the access permissions r
agrantedisto Syou. But for the lookups and lookup values to
appear as values in the lists, they needa togbe enabled.
h
s h w se t
• To enable a lookup type,
l ( a need
you
t o uto enable at least one of its lookup codes and that code must be
a r wa nse
in a valid date range.
•
you a
A l ice types are enabled at the time of deployment. You can disable the ones that
By default,gmost lookup
ry do not require.
aApplications
h
Note:
s w development can define lookups in an application view to restrict the UI pages where
A they appear.
Navigate to:
• Others > Setup and Maintenance > Tasks Panel Tab > Search > Manage Standard Lookups
• Others > Setup and Maintenance > Tasks Panel Tab > Search > Manage Common Lookups
• Others > Setup and Maintenance > Tasks Panel Tab > Search > Manage Set Enabled Lookups

Customize Lookups
• Based on the defined customization levels.

• Restricted to the extent to which customization is allowed.
• The following levels of customization are defined:
– User: Create or modify all parameters of a lookup type.

– Extensible:
— Modify only certain aspects of the lookup type such as the dates.
— Add new lookup codes.
— Cannot delete the lookup type.
– System:
— Cannot add or delete any aspect of the lookup type.
ble
— Modify only its meaning.
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Define Profile Options
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Define Profile Options
In this section, you will learn key concepts about:

• Profile Options
• Profile Option Categories
• Profile Option Levels and Values

• Profile Options for Common Setup
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Profile Options
Profile options are global configuration settings that users can modify to change the way an
application works.
For example, settings such as user preferences and application configuration parameters
can be modified per the user’s requirements.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
You can use profile options to modify:
@ in tude
• r
ga thuser S
s interface
The look and behavior of the application's
a
w used i
• h
User preferences such as settings
a s u s efor social networking
•
a
The business logic ofl (the application
e to
• w ns options that determine how and where information is stored
r processing
Log settingsaand
g c e
y a Aconsists of:
A profile option
r
li
• waName
As h
• Application and module
• Values
• Categories and Hierarchy level
You can modify any of these constituents of the existing profile options, but system administrators must
have enabled the profile option for modification.
The use of profile options is guided by the functional requirements. To determine which profile options to
use in the implementation project, refer to the product offering-specific documentation.

Profile Option Categories
Profile options are grouped into categories depending on the functional area in which the
profile options are used.
Profile option categories facilitate searching and defining data security.
A profile option can be grouped into more than one category.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b e category groups the profile options that
in profile
For example, in Oracle Receivables, the Transactions
@ t u doption
a r
are related to Receivables transactions processing,
g such
s Sas:
• Require Adjustment Reason w a t h i
s h s e
• Invoices with Unconfirmed
a t ou
l (a eReceipts
•
arw cenfors Credit Memos
Use Invoice Accounting
g
r y aA li
w a
As h

Profile Option Levels
In an application, the display and availability of profile options depends on the hierarchy
level at which it is enabled.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
The hierarchy levels are:
@ in tude
• g r
a (unless s S
Site level: The lowest level of hierarchy
accessibility to all users of thew a h i superseded by any other level) that provides
applicationtacross the deployment site. In a multitenant environment,
a s h use
l ( eintothe hierarchy that applies to the selected product family (product
Site is scoped per tenant.
a
• w
arOracle
Product level: The
ns such as Financials) and its specific users. For the same user, the profile
next level
g
offering within
c eCloud,
y a atAthis levellisupersedes any site level profile option setting.
option
r
• waUser level: The highest level in the hierarchy that applies to the specific user or user role. Also, it
h
As supersedes any product or site level setting that was defined for that user.
Note: Profile options defined at higher levels override the profile options at the lower level.
Profile values determine application behavior at a specific selected level. Contexts, such as user session or
accessed product, determine which profile option value is associated with the profile option name.
The following example of the AFLOG_LEVEL profile option shows how the profile values determine
application logging at various levels.

Profile Option Values
Profile values determine application behavior at a specific selected level. Contexts, such as
user session or accessed product, determine which profile option value is associated with
the profile option name.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ
n howi b e profile values determine application
This example of the AFLOG_LEVEL profile option ishows dthe
r @ S t u
logging at various levels:
a g a i s
• Site
h w se t h
s
(a Severe u
- Profile optionl value:
a t o
-
g a w activities
Effect:rLog
e n seat the site level indicating failures within the environment
-
a A l
Result: Only icadministrators are notified
ry
• aProduct/Product Family (CRM/SCM)
h w
As - Profile option value: Warning
- Effect: Log activities that are specific to the product family
- Result: Administrators and product-specific implementation consultants are notified
• User (Bob)
- Profile option value: Info
- Effect: Log activities pertaining to user actions such as invalid user name or password, or
account locked out
- Result: Administrators, implementation consultants, and users are notified

Profile Options for Common Setup
You can set up a common profile option, such as logging, which applies to the entire
applications suite.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
By default, logging is set to SEVERE at the Site level.
@ in To diagnose
t u de or troubleshoot any problem, set logging
to FINEST at the User level for a particular user
g r
a so that s S
you can examine the logs in detail.
As a result, actions of that particular w a h i
t in the finest level possible. The benefit of this setting
s h
a andtodoes
is that it does not affect other (users
e
user are captured
s
u not impact logging or performance at the Site level.
a l
Another example could
g arwbeThe the use
e n seof theprofile
profile option FND_SERVER_TIMEZONE to record the time zone
a A
of the database instance.
l i c selected value and the hierarchy level at which the profile option is set
determines
a ry the time stamp on all the transactions performed on that server. Usually, such profile options are
s h w
applied only at the site level because of their universal impact.
A You can find these profile options under the Manage Profile Options task on the Setup and Maintenance
Overview page.

Quiz Q
For a profile option, if you set the hierarchy level for both
site and user, the site level hierarchy takes precedence
over the user level hierarchy.
a. True
b. False
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Answer: b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Define Attachments
This section describes the tasks in the Define Attachments task list:
• Manage Attachment Entities
• Manage Attachment Categories
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Navigate to:
@ in tude
• Others > Setup and Maintenance g r
a Panel s STab > Search > Manage Attachment Entities
a > Tasks
w > Tasks h i
t Panel Tab > Search > Manage Attachment Categories
• h
Others > Setup and Maintenance
s s e
a l (a e to u
g arw cens
r y aA li
w a
As h

Define Attachments
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Key Concepts
Attachments are:
• Pieces of supplementary information that users can associate with specific business
objects. For example, users might attach receipts to expense reports.
• URLs, desktop files, or text.

• Stored in a content server.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b e
When attachments are stored in the Oracle Enterprise
@ in Content
t u dManagement document repository, users
r
can select folders or files from the repositoryaas attachments.
g s S
a
w se t h i
Attachment entities
s h u
•
a (a thattoattachments
Identify the businessl object can be attached to.
• rw after
Are typicallyanamed
g e n sthee primary table or view used to store information about the business
object. A
a l ic
ary categories
Attachment
w
Ash• Classify attachments. For example, when users add an attachment to an expense report, they can
select a category to indicate whether the attachment is a receipt, travel itinerary, and so on.
• Can optionally be used to restrict access. For example, users with a specific role are not given
access to one of the expense report attachment categories, so they cannot select it when adding
attachments to their reports. They also cannot see any attachments assigned to the category.
• Are assigned to attachment entities so that each category is tied to the relevant business objects.
Note: Each attachment entity must have at least one assigned category. Otherwise, users cannot add
attachments for the corresponding business object.

Key Concepts
• The UIs across Oracle Cloud Applications facilitate adding attachments, where
applicable.
• Depending upon the roles and access levels, you may view, add, update, or delete
attachments.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Where access is not granted, users cannot view any
@ inattachment.
t u deFor example, if a user does not have
access to a specific expense report, then the r
gasame userS
s cannot access attachments for the expense report.
a
w se t h i
s h
a l (a e to u
g arw cens
r y aA li
w a
As h

Manage Attachment Entities
• Attachment entity is a database entity – a table or a view.

• An attachment entity represents business objects with which the actual attachments can
be associated.
• You can either use the predefined entities or create new ones.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
• An attachment entity name should match the
@ innametofudtheetable or view that represents the business
r
object to attach to. The name is alsoaused in the S
s repository folder that is automatically created to
store attachments for the entity. ag h i
s h w se t
• a name
The attachment entity(display
l t o ushould be something that users know to represent the business
object.
a r wa nse
a Ag lice
w ary
Ash

Manage Attachment Categories
Attachment UIs for users to add or manage attachments are fully functional and do not
require setup.
Predefined attachment categories are already assigned to attachment entities.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
For your changes to appear in attachment UIs for users,
@ in thetuusers de must sign out and sign in again to clear
the cache for categories. If your new categories r
gin aplace.are still S
s not displayed, then the specific attachment UI likely
w
has predefined restrictions on categories a t h i
Check with your administrator or help desk.
h e
s taskuscan also be used to assign categories to entities. You do not
aEntities
Note: The Manage Attachment
a l ( o
tperforming
a r w
need to use this page unless
n s e
you are additional or technical configuration.
If an entity has only
a l ice then:
Ag one category,
• ryattachments added for the corresponding business object are automatically assigned to that
aAll
w
Ash• The Category attribute is hidden in the UIs where users add or view attachments for the business
category.
object.

Manage Attachment Categories
• Create new attachment categories as needed and assign to relevant attachment entities.
• Remove the association of categories with specific entities.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Example of creating new attachment categories in
@ t u de
g r
athat fulfill
s aS
Your company wants to identify attachments
w a t h i specific fiscal requirement. You can create a new
s h
category and assign it to all attachment
s e
entities representing business objects that are relevant to the
requirement.
a l (a to u
Example of removingrthe
g a e n se of categories
w association
A is lnot
A predefined category
a ic relevant to any of your users for certain business objects, so you remove its
ary with those objects.
association
w
Ash

Attachment Category Security
You or a technical administrator can implement data security on attachment categories to

determine:
• Which categories users can access when adding attachments.
• What actions they can perform on attachments assigned to those categories.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b e of the privileges to roles. For details,
For an attachment category or set of categories, assign
@ in onetuordmore
see the Oracle Cloud Applications Developer's
g r
a Guide. s S
a
w or your t h i
s h
After the security rules are in place, you
s e technical administrator can use the Security Enabled check
u to enable this security for specific attachment entities.
box on the Manage Attachment
a l (aEntitiestopage
Note: If security is enabled
athen n e
rwthatforecategory
ansattachment entity before any data security rules are in place for a
A g
particular category,
l i c will not be visible to anyone until rules are in place or security is
disabled. y a
Inh w
some
arcases, data security for categories is predefined. For example, predefined attachment categories
Asare available for suppliers and receivers. Both types of users can go to the same page with an attachment
UI, but see only the categories that they can access based on security.

Attachment Category Security
Each action is captured by predefined privileges:

• Read: Read Application Attachment
(FND_READ_APPLICATION_ATTACHMENT_DATA)
• Update: Update Application Attachment

(FND_UPDATE_APPLICATION_ATTACHMENT_DATA)
• Delete: Delete Application Attachment
(FND_DELETE_APPLICATION_ATTACHMENT_DATA)
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
incurrently
For example, the Expense Report attachment entity
@ t u dhase three attachment categories:
• Receipts r
ga this S
a
w se
• h
Missing Receipts Declaration
s
• Travel Itinerary
a l (a e to u
g arw cens
r y aA li
w a
As h

Example
• You need to track the mileage of cars that belong to your company.
• Your users record miles traveled in a log book, scan the relevant page, and attach the
image file as part of their expense reports.
• The clerks handling the corporate fleet vehicles need to see these attachments, but
should not view the other types of attachments for expense reports. The managers of
users submitting the expense reports can view all categories.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Solution
To implement this security:

• Use the Manage Attachments Category page to create a Mileage attachment category
and associate it with the Expense Report attachment entity.
• Define data security so that the role for the clerk can see only the Mileage category,
while the role for the manager can see all categories.
• Select the Enable Security check box on the Manage Attachment Entities page for the
Expense Report entity.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Quiz Q
Attachment categories are assigned to specific attachment entities:
a. So that the categories are available for the relevant business objects.
b. Because these are the entities with the Enable Security check box selected.
c. Only on the Manage Attachment Categories page.

d. All of the above.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Answer: a
@ in tude
r S Security is optional.
ga thisentities.
You would not assign categories to security-enabled
a
w using
s
You can also assign categories to
a h
entities
u s e the Manage Attachment Entities page.
a l ( e to
w
ar cens
g
r y aA li
w a
As h

Quiz Q
Attachments can be created without an assigned attachment category.
a. True
b. False
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Answer: b
@ in tude
r
ga thEven sS
All attachments must have an assigned category.
w a i if the attachment entity has only one associated
a s h assigned
category, attachments are automatically
u s e to that category and the user does not see a field to select
a category.
a l ( e to
w
ar cens
g
r y aA li
w a
As h

Summary

• Manage Oracle Social Network Objects.
• Define Flexfields.
• Define Lookups.
• Define Profile Options.
• Define Attachments.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

As h w a
ry
aA
g li
a
s
arw cens
h
a
l (a e to u
r
w se
@
ฺ i b
ga this S
ฺ c
in tude
)
m nt G
om uid
a
has eฺ
o n n
- t r an
sfe r a bl
e
B
Integration Services in Payables

ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h
Objectives

• Describe web services for Payables.
• Understand individual REST APIs Web Services Details.
• Use Payables Invoices in the Universal Business Language 2.1 XML Format
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ryaA li
w a
A s h
Oracle Financials Cloud: Payables to Cash Management Implementation B - 2

SOAP Business Object Services
SOAP Business Object Services categories include:

• Business Object Services
• Process Services
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b e to integrate with or extend Oracle
You can use the Simple Object Access Protocol (SOAP)
@ in web t u dservices
Applications Cloud. With web services, you a r
g canpartners
integrate
s Sheterogeneous applications within the enterprise
or expose business functions to Oracle a
w that
Cloud t h i and customers over the internet. The applications on
a h
the web understand the standardsprotocols
u s e the web services use and can communicate with each
other. (
al se t o
r w n
SOAP web services
A gain Oracle
l i c eApplications Cloud can be categorized into:
• y a Object Services: Services that expose data and operations on a business object such as
Business
r
a
w an opportunity or a marketing campaign. These services are implemented using the Application
A s h Development Framework (ADF). Therefore, the services share interface structure, common types,
and standard create, read, update, and delete (CRUD) operations.
• Process Services: Services that orchestrate business processes and not centered around any
particular business object. These services are typically implemented using Service-Oriented
Architecture (SOA) composites.
SOAP web services are based on the following industry standards:
• Extensible Markup Language (XML): A data format that allows uniform communication between
web services consumers and web services providers.
• XML Schema: A framework that describes XML vocabulary used in business transactions.
• Simple Object Access Protocol: A protocol for exchanging structured information in the
implementation of web services.
• Web Services Description Language (WSDL): An XML-based language that provides a model for
describing SOAP-based web services.
• WS-Policy: A flexible and extensible grammar framework that describes the capabilities,
requirements, and general characteristics of web services using the policies.

REST APIs Web Services for Payables
Integrates with external

systems to retrieve payments
for invoices.
REST APIs
Web
Services for
Payments.
ble
fe r a
View detailed information
an s
about the payment and
n - t r
associated invoices.
n
.
o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

REST APIs Web Services for Supplier Invoices
Use REST APIs services for payables to:

• Integrate with external systems to create and manage payables invoices.
• Create and manage details about unmatched supplier invoices, including header, lines,
distributions, installments, descriptive flexfields, and attachments.

• Create unmatched supplier invoices with types such as Standard, Prepayment, Credit
Memo, Debit Memo.
• Update key invoice information and validate, cancel, and delete invoices.
• Place or release holds on invoices.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ryaA li
w a
A s h

Individual REST APIs Web Services Details
REST APIs Web Services Description

Invoices Create and manage details about unmatched supplier invoices, including
header, lines, distributions, installments, descriptive flexfields, and
attachments
Invoice Lines Create and manage details about goods and services, including freight,
miscellaneous charges and necessary integration information for Oracle
Fusion Assets.
Invoice Distributions Create and manage details about accounting, such as accounting date,
distribution combinations, and the necessary integration information for
Oracle Fusion Assets.
Invoice Installments Create and manage details about the payment due dates, amounts, and
other payment information. An invoice can have one or more installments.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h


Invoices Descriptive Flexfields Create and manage details about the descriptive flexfield references for
an invoice.
Invoice Lines Descriptive Create and manage details about the descriptive flexfield references for
Flexfields an invoice line.
Invoice Distributions Descriptive Create and manage details about the descriptive flexfield references for
Flexfields an invoice distribution.
Invoice Installments Descriptive Create and manage details about the descriptive flexfield references for
Flexfields an invoice installment.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h


Attachments Create and delete attachments that are attached to the invoice.
Invoice Holds Create and manage holds for an invoice.
Invoice Holds Descriptive Create and manage details about the descriptive flexfield references for
Flexfields an invoice hold.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
You can further use these REST services to construct
@ t de based on your PaaS applications
in integrations
u
requirements such as:
g a r s S
For Retainage or Reverse Factoring w a t h i
s h e
arrangements:
s
• l (a such oasupay group and other information such as due date, payment
Update invoice information
a t
g a w and
method, bank raccount
e n sethird-party payment on the installments.
•
a l ic
SplittingAinstallments.
ry or release hold on installments.
• aPlace
w
h invoices on hold until some external process is complete. For example, pending approvals or
AsPlace confirmation on reverse factoring, before the hold can be released for further processing.

REST APIs for External Payee, External Bank Account and Payment
Instrument Assignment
Use the External Payee, External Bank Account and Use REST APIs to assist integration
Payment Instrument Assignment REST API resources with third-party applications.
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 and
bank account owners.
• Retrieve external bank account and account owner
information.
• ble
Create and manage assignments of external bank
accounts to external payees or external payers. fe r a
an s
• Retrieve payment instrument assignment
n - t r
information.
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
This feature is automatically enabled.
@ in tude
g
For additional information, see the following
r
achaptersisin Sthe Oracle Help Center (docs.oracle.com) REST
API for Oracle Financials Cloud R13w a
guide fore th information:
h
asthrough s additional
• (
Quick Start: Guidesl you o ausimple request example.
wa API: e t
• Working with
g a rREST
e n sProvides help with advanced tasks.
•
a A Includes
Use Cases: c
li real-world solutions with code examples.
r y
• aReference: These topics include error messages and more.
s h w
A

Payables: REST APIs for Payments
Use REST APIs to assist integration

Use the Payables Payments REST API
with third-party applications.
resource to:
• Capture additional information for your
payments against Payables invoices.

• 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
ble
payment..
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Additionally, you can build integrations to:
@ in tude
• a r
Retrieve payment and paid invoiceginformation. s S
a
wOraclese t h i
•
a s h
Import paid invoices after your
u
Financials Cloud upgrade.
• Void a payment.
a l ( e to
a w ns created outside of Payables and then recorded in Payables. You can create
rare theepayments
g
Note: Manual payments
c
r y a A using theliCreate Payments page by selecting the payment type Manual.
a manual payment
a are required to enable this feature.
No steps
w
h
AsFor additional information, see the following chapters in the Oracle Help Center (docs.oracle.com) REST
API for Oracle Financials Cloud R13 guide for additional information:
• Quick Start: Guides you through a simple request example.
• Working with REST API: Provides help with advanced tasks.
• Use Cases: Includes real-world solutions with code examples.
• Reference: These topics include error messages and more.

Payables: REST API Services for Supplier Invoices
Use REST APIs to assist integration

Use the Invoices and Invoice Holds REST
with third-party applications.
API resources to manage details about
supplier invoices:
• 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.
ble
• Capture tax determinants such as
fe r a
intended use, transaction business
an s
category for tax calculation purposes.
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Additionally, you can build integrations based on your
@ de
in PaaStuapplication requirements such as retainage,
a r
reverse factoring arrangements, or placing invoices
g S
on hold.
s
a
w support h i
t Descriptive Flexfields.
s h
Note: Currently these resources do not
s e Global
(a to u
This feature is automaticallyl enabled.
a
a rw see
For additional information,
g e n sefollowing chapters in the Oracle Help Center (docs.oracle.com) REST
the
API for Oracle A
a ic R13 guide for additional information:
FinancialslCloud
ry Start: Guides you through a simple request example.
• aQuick
w
Ash• Working with REST API: Provides help with advanced tasks.
• Use Cases: Includes real-world solutions with code examples.
• Reference: These topics include error messages and more.

Payables Invoices in the Universal Business Language 2.1 XML
Format
The Universal Business Language (UBL) 2.1 XML format is used by many countries making
it mandatory for business-to-government transactions.
• You can receive electronic invoices from suppliers in UBL 2.1 format using Collaboration
Messaging Framework (CMK).

• The Collaboration Message, UBL_2.1_INVOICE_IN, in CMK is used for receiving and
converting UBL 2.1 invoices.
• UBL 2.1 invoices sent by suppliers are received by CMK and saved in the Payables
interface tables.
• Run the Import Payables Invoices process to import the invoices.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
UBL_2.1_INVOICE_IN is automatically enabled. in
@ t u de
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
r y aA li
w a
As h

Setting Up a Supplier for UBL 2.1 XML
To receive UBL 2.1 invoices:

1. Assign the seeded collaboration message definition UBL_2.1_INVOICE_IN to the
trading partner created in CMK.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b e > Manage Collaboration Messaging
inPaneltu> dSearch
Navigate to: Others > Setup and Maintenance Tasks
@
Service Providers. r
ga this S
a
w se
s h
a l (a e to u
g arw cens
r y aA li
w a
As h

Setting Up a Supplier for UBL 2.1 XML
To receive UBL 2.1 invoices:

2. In supplier site setup, select the trading partner and add PROCESS_INVOICE_IN
under Associated Collaboration Documents.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ
m nt Gc
ฺ i b
• Receive UBL 2.1 invoices through the CMKin
@ web service
t u deor B2B adapter.
• Import invoices from the interface g r
byarunningithe
s SImport Payables Invoices process with source "B2B
a
w se t h
XML Invoice".
s h u
Use the UBL Extensions larea
a (a to map
t oadditional attributes specific to your business requirements by:
•
g a w nUBL
Modifying the rdelivered
e se2.1 XSLT using the Manage Collaboration Message Definitions task,
available
a c
Afrom theliCollaboration Messaging Framework work area.
ary
Role Information
w
h with the Accounts Payable Manager or Accounts Payable Supervisor role can access the
AsUsers Collaboration Messaging Framework work area to view message history and trading partners setup.
Users with the Accounts Payable Manager or Accounts Payable Supervisor role can access the Manage
Collaboration Messaging Configuration and Manage Collaboration Messaging Service Providers tasks
under the Setup and Maintenance work area.

Summary
In this lesson, you should have learned to:

• Describe web services for Payables.
• Understand individual REST APIs Web Services Details
• Use Payables Invoices in the Universal Business Language 2.1 XML Format
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

As h w a
ry
aA
g li
a
s
arw cens
h
a
l (a e to u
r
w se
@
ฺ i b
ga this S
ฺ c
in tude
)
m nt G
om uid
a
has eฺ
o n n
- t r an
sfe r a bl
e
C
Localizations
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h
Objectives

• Export Enterprise Financial Data for China.
• Describe the reports by country for EMEA.
• Understand the reports by country for APAC.

• Explain the reports by country for LAD.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ryaA li
w a
A s h
Oracle Financials Cloud: Payables to Cash Management Implementation C - 2

Exporting Enterprise Financial Data for China
You can export financial data from:

• Oracle Financials Common Module
• Oracle General Ledger
• Oracle Payables
• Oracle Payments
• Oracle Receivables
• Oracle Subledger Accounting (SLA)
• Oracle Assets
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Export financial data from Oracle Cloud Applications
@ de standard format developed by the
ininto atunational
National Audit Office of the People's Republicr
a of China.
gSoftware s S
The format is based on the Financial Information
a
wPeople's
Technology - Data Interface of Accounting t h i(GB/T 24589-2010) standard, and approved by the
h
a to us
Standardization Administration ofsthe eRepublic of China.
l (
a r wa nse
a Ag lice
w ary
Ash

The Export Payables and Receivables Data for China: Enterprise
Process
It exports the following Payables data:
• Document type
• Transaction type
• Payables account details
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
The Export Payables and Receivables Data for China:
@ in Enterprise
t u de process exports data from Oracle
a r
Payables, Oracle Payments, and Oracle Receivables
sforSan enterprise. On successful execution of the
process, data is exported in an XML file.ag h i
s h w se t
l (a sections:
The XML file includes the following
t o u
a sethenote
•
one of theg arwSpecifies
Document type:
e n document type number and document type. The document type is
a A l ic
following: payable and payment note.
•
a r y
Transaction type: Specifies the transaction type and transaction number based on the document
s h w type.
A - For a payable note, the transaction type is the invoice type of the Payables invoice.
- For a payment note, the transaction type is the payment type of the Payables payment. The
transaction number is the payment type indicator.
• Payables account details: Specifies payables account related information, such as account
payable, prepayment, and other payable details based on the supplier. The process exports only the
liability or prepaid lines that are transferred and posted to Oracle General Ledger. When multiple
lines with the liability accounting class for each invoice exist, only the summarized amount with the
same accounting date for each invoice is exported.

Details Exported
• Account Number • Ledger Currency

• Journal Created Date • Conversion Rate
• Accounting Year • Balance Side
• Accounting Period Number • Entered Currency

• Journal Category Number • Transaction Type Number
• Journal Number
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
in filetand
The following common details are exported to the XML
@ u deare part of the Payables section:
• r
ga number. s S
Account number: The natural account
a
w sLedger h i
t date from the journal header.
• Journal created date: ThehGeneral
s e
uyears associated with the accounting calendar of the selected
•
a
Accounting year: The l (aaccounting
e t o
g arw cwhile
ledger as specified
e nsexecuting the process.
•
a A period
Accounting
r y li number: The periods from the first period to the end period of the accounting
w a year.
h
As Journal category number: The category defined for the journal.
•
• Journal number: The journal number that is derived from the journal itemization table.
• Ledger currency: The ledger currency of the transaction.
• Conversion rate: The currency conversion rate on the transaction. When it is the ledger currency,
the value is 1.
• Balance side: The Chinese characters indicate debit or credit. The balance side of the account and
the ending balance are compared to assign an appropriate Chinese character to the account.
• Entered currency: The currency code.
• Transaction type number: The number of the transaction type.

Payables Details and Descriptions
Detail Description
Supplier Number Only suppliers with a balance greater than zero or
suppliers with valid transactions during the period are
exported. The file does not include suppliers of type

employee.
Journal Date Displays the General Ledger date of the Payables
transaction line.
Accounted Amount Balance Displays the ending accounted amount balance per
account and supplier in the current period.
Entered Balance Displays the ending entered balance per account and
supplier in the current period by the currency.
Accounted Amount Displays the ledger currency amount on the Payables
ble
accounting line.
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Detail Description
Entered Amount Displays the entered currency amount on the Payables
transaction line.
Description Displays the description from the Payables invoice header

and the payment description.
Due Date Displays the date when the invoice is due for payment. The
date is calculated based on the invoice terms date and the
invoice payment terms.
Applied Journal Number The data is exported for payment and prepayment
accounting lines. The value is blank for invoice lines.
For payment accounting lines, the applied journal number
is the journal number of the invoice paid. When the journal
ble
number is different for each invoice, the applied journal
fe r a
number is displayed on different lines.
an s
For prepayment accounting lines, the applied journal
number is the journal number of prepayment.
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
in tuonly
Note: The applied journal number for invoices is displayed
@ dewhen the invoice is applied to the
prepayment. r
ga this S
w sea
s h
a l (a e to u
g arw cens
r y aA li
w a
As h

Detail Description
Applied Date For payments, the applied date is the payment date. For
invoices, the date is the date on which the invoice was
applied to the prepayment. When the invoice is not applied

to the prepayment, the date is omitted.
Document Type Number Displays the number on the payable note for an invoice
and displays the number on the payment note for the
payment.
Transaction Number Displays the voucher number for each invoice line and
displays the document number for payment.
Invoice Number Displays the invoice number for invoices. The value is
omitted for payments.
ble
Contract Number Displays the purchase order (PO) number when the invoice
fe r a
matches the PO.
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Detail Description
Project Number Displays the project number from the invoice header.
Settlement Method Number Displays the payment method used for invoice and
payments.
Payment Date Displays the payment date of the payment. The value is
omitted, when it is an invoice line.
Clear Flag When the invoice is fully paid or applied, the process
displays 1 for the invoice and payment line. When the
invoice is unpaid or applied, it displays 0.
When the prepayment is fully applied, it displays 1. When
the prepayment is not paid or applied, it displays 0.
Remittance Bill Number Displays the global descriptive flexfield from the payment ble
header.
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

EMEA Reports for Payables
Oracle Financials Cloud for EMEA provides:

• Predefined operational, business, and reconciliation reports to meet country-specific
reporting needs.
• Reporting data models to prepare user-defined and specialized reports.

• Predefined reports for:
– France
– Italy
– Spain
– Germany
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Reports for France
VAT Report
Title Description
Deductible VAT Lists the deductible VAT amount and totals of invoices for France that
Declaration Report for are entered in Oracle Payables. The reported data is grouped by VAT
France deductibility rule, tax rate, and account number.
DAS2 Reports
Title Description
DAS2 Contractor Letters Generates letters to all contractors in France whose income is
ble
Report for France reported in the DAS2 extract file for the current year. It lists income
fe r a
tax amounts from Oracle Payables grouped by income tax type for
an s
France.
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Reports for France
Title Description
DAS2 Extract File Report for Generates the DAS2 electronic file for France that is submitted to
France the tax authorities in a predefined format.
DAS2 Type 210 Updates Generates a list of all changes to data related to DAS2 reporting for
Report for France France that are made since the last run of the verification report.
DAS2 Verification Extract for Generates DAS2 information for contractors in France and related
France income tax information from data entered in Oracle Payables. It
extracts information into the DAS2 temporary tables and
automatically submits the DAS2 Verification Extract Execution
Report for France.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Reports for Italy
Oracle Cloud Applications provide standard financial and tax reports to meet the legal and
business reporting requirements of tax authorities.
For countries like Italy, a set of country-specific reports is provided to meet local reporting
requirements for:
• Value Added Tax (VAT)
• Intra-EU activity
• Exemptions
• Withholding tax
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

VAT Reports for Italy
Title Description
Lists the tax declarable activities including payments of the invoices with
Declarable Input VAT Register for Italy deferred tax. The report lists supplier details and recoverable and non-
recoverable taxable and tax amounts grouped by tax rate code.
Payable Sales VAT Register for Self Lists the tax declarable activities including receipts of the invoices
Invoices, Inter-EU Invoices, and VAT with deferred tax, adjustments, and bills receivable.
for Italy
Purchase VAT Register for Italy Identifies all Italian invoices that are assigned to the document
sequence name for the VAT register name selected and that have
accounting dates within the period range being reported.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b e run the VAT reports for Italy. The
Run the Select Transactions for Tax Reporting process
@ in beforet u dyou
r s S and identifies the tax reporting periods and tax
ga thidentifier,
process marks the transactions with a tax reporting
registers defined for Italy.
w sea i
Run the Finalize Transactions(a s h u process to mark transactions as finally reported for the
a l for Taxt
Reporting
o
following reports:
• arwVAT
DeclarablegInput e n se for Italy
a A l ic Register
•
a ry
Declarable Output VAT Register for Italy
h• w VAT Liquidation Report for Italy
A s
- Note: Only the above listed reports can be printed in final mode and can be reprinted if
required.

VAT Reports for Italy
Title Description
Provides summary information for all reportable tax events with tax point dates
within the reporting period. Identifies the associated tax register for each
transaction. Provides a summary per tax rate code with the totals for each tax
VAT Liquidation Report for Italy
register. Includes a grand total section for all reportable sales and purchases
VAT and credit balances from the previous report. This determines the net VAT
amount to be paid to the authorities.
Trading Partner Declaration for Italy Use the Trading Partner Declaration for Italy to generate an
electronic file and audit report that supports the trading partner
declarations and reporting requirements of the Italian Revenue
Agency (IRA). ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Italy: Include Taxable Journals and Transactions in Tax Registers for
Italy
The following VAT reports for Italy include Tax Entry Repository transactions and journals,
uploaded with an FBDI spreadsheet, having a valid Document Sequence Name and Value:
• Purchase VAT Register for Italy
• Payables Sales VAT Register (Self Invoices, Inter-EU VAT) for Italy
• Receivables Sales VAT Register for Italy
• Declarable Input VAT Register for Italy
• Declarable Output VAT Register for Italy
• VAT Liquidation Report for Italy
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Steps to Enable
@ in tude
g a r s S
w a t h i
Create and enable the lookup type JE_IT_TER_JRNL_TXN_TYPE with the lookup code:
JE_IT_TER_JRNL_TXN_CODE.
a s h use
Tips
a l ( e to
The following stepsa w
r you
enable ntosreport on manual purchase/sales transactions and journals:
A g i c e
documentlsequences
•
r y a
Create for all required purchase/sales transactions and journals using the
a Manage Document Sequences setup page.
w These are sequences with no Document Sequence Categories assigned.
A s h
• Configure these sequences with Application and Module set to Tax.
• Associate the document sequences to Tax Registers using the Tax Reporting Configuration tab of
the Create/Edit Legal Reporting Unit Tax Registration page.
You can use the Tax Registers created for documents originating from Payables or Receivables, or
create separate specific Tax Registers for manual tax transactions/journals only.
• Use FBDI spreadsheets to upload manual purchase/sales transactions and journals.
Enter the document sequence in the Document Sequence Name and sequence number in the
Document Sequence Value columns of the Transaction Headers worksheet.
The Document Sequence Name and Document Sequence Value columns must be populated for
each transaction/journal to be reported. Only FBDI spreadsheets are currently supported.

Intra-EU Report for Italy
Companies in Italy must report the details of the purchase of services from companies in
European Union (EU) member states.
The reported transactions, after being declared to the tax authority, must be stamped with
declaration number issued by the tax authority.

• The Intra-EU report for Italy in Receivables is based on the Turnover Reporting
Processes.
Title Description
European Purchase Listing of Lists all Intra-EU payables transactions for services. The report
Services for Italy prints invoice details specific for Italy such as service mode,
ble
service code, and protocol number.
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b e report, run the Turnover Reporting
Before running the European Purchase Listing of Services
@ in tfor u dItaly
Selection process in:
g a r s S
• Preliminary mode and ensurew a h i
t are reported correctly.
s h s e
the transactions
u the electronic files and finally reported the transactions.
• Final mode after youl have
a (a generated
t o
The process extracts
g a e se including correction transactions such as credit memos, within the
rallwthe invoices,
n
specified datesA
a for a given l iclegal entity. Only transactions that have the additional details entered for
European
a rySales Listing of Services are extracted.
s w
Tohcomplete the declaration, run the Turnover Reporting Declaration Closure process. The process:
A • Records the declaration details of all finalized transactions.
• Marks the reported transactions with the declaration number received from the tax authority.
The European Puchase Listing of Services for Italy report:
• Displays report level totals for invoice amount.
- Note: Create your own templates to specify page totals, carry forward totals, or brought
forward totals.
• Rounds all amounts to the nearest Euro.
• Lists invoices that are reported and later canceled in the adjustments section of the report.

Exemption Reports for Italy
Companies in Italy that are regular exporters can legally request suppliers to not charge
VAT on purchase transactions.
Title Description
Produces an exemption letter for suppliers in Italy instructing them not
Letter of Intent Report for Italy
to include VAT on invoices that they submit.
Supplier Exemption Limit Lists the details of suppliers eligible for exemption in Italy and their
Consumption Report for Italy monthly consumption of assigned exemption limit. It lists
consumption details of all the suppliers, or a specific supplier. Details
include all invoices exempted during a calendar period.
ble
Subledger Letter of Intent Register Lists all exemption letters issued to suppliers or received by
fe r a
customers in Italy within a given period range.
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b e
in tand
The Letter of Intent is the official letter to send to suppliers
@ u dcustoms for this exemption. This letter
contains:
g a r s S
• Instructions to invoice withoutw a t h i
s h VAT.
s e
• Revocation or suspension
a o u letter of intent, with instructions to invoice with VAT.
l (a ofe atprevious
w totalnVAT
The exemption limitaisrthe s exemption amount that a regular exporter can claim against suppliers,
g c e
r y aA
and is monitored on a li
periodic basis.
w a
As h

Withholding Tax Reports for Italy
Title Description
Yearly Withholding Tax Report for Shows annual taxes withheld by first-party legal entities, for the
Italy supplier for the year selected. The report data can be printed or
grouped by supplier name, supplier taxpayer ID, or supplier tax
registration number.
Withholding Tax Letters for Italy Identifies letters sent to suppliers in Italy that confirm tax
amounts that are withheld on purchase invoices that are
partially or fully paid within a calendar year. Letters can be
printed for a specific supplier or for all suppliers that have tax
withheld. ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
The withholding tax reports for Italy provide specificin
@ u
withholding
t detax information on supplier invoices as
required by the tax authorities in Italy. You can r
a use
gletters these
s Sreports to produce withholding tax letters you send
w
to suppliers, reconcile the withholding taxa t h
senti to suppliers with the yearly amounts withheld for tax
and social security, and prepare s
a h
the
u s e
yearly declarations for the tax authorities.
(
al se t o
r w
A ga licen
a rya
s h w
A

Reports for Spain
Oracle Cloud Applications provide standard financial and tax reports to meet the legal and
business reporting requirements of tax authorities.
For countries like Spain, a set of country-specific reports is provided to meet local reporting
requirements for:
• Value Added Tax (VAT)
• Modelo
• Withholding tax
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Online VAT Reporting for Spain
Spanish companies, with an annual turnover of more than 6 million Euros, can now use the
Online VAT Reporting for Spain to electronically deliver VAT registers to the Spanish Tax
Authorities.
• Use Online VAT Register Reporting Confirmation for Spain process to reflect the
acceptance status on the financial documents reported to the Tax Authorities.
• Corrected financial documents can be resubmitted Effective January 1, 2017
• From July 1, 2017 transactions must be reported within four days of reception or
issuance date.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
The Online VAT Reporting for Spain solution provides
@ u de components to support this legal
in the tfollowing
requirement:
g a r s S
a h i
• Additional fields, which are specific
reporting information. (as
e t VAT Reporting for Spain, must contain the mandatory
hw utosOnline
• w a e to details and creates an XML file in a predefined format.
l transactional
r ens
Process that extracts
gaupdates
• ProcessAthat
a l ic the transaction reporting status based on the confirmation message received
a ry
from the Spanish Tax Authority.
w
Ash
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.

Investment Register
Online VAT Reporting for Spain process:
Invoices
Transaction Status R- Ready Tax Authority Status
M – Modified A - Accepted
O – On hold AE – Accepted with Error

D – Direct reporting R - Rejected
Annual/Online VAT Reporting for Spain

New invoices: Already reported invoices Annual/Online VAT Register
Communication Communication Reporting Confirmation for Spain
Type: Addition Type: Modification
ble
Tax Authority Response Messages
fe r a
A – Accepted
an s
Validation AE – Accepted with Error
R – Rejected
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b e process creates XML file for the
in tforudSpain
Annual Online VAT Investment Goods Register Reporting
@
Investment Goods Register.
g a r s S
Steps to Enable: There are not stepsw a
requirede h i
to tenable this feature.
s h s
Role Information: EMEA Financial
a t o u duty role.
l (a eReporting
g arw cens
r y aA li
w a
As h

VAT Reports for Spain
Title Description
Input VAT Journal for Spain Identifies detail and summary information about tax on invoices and
expense reports for Spain entered in Oracle Payables. Data is
reported by register type: recoverable tax register and no recoverable

tax register. The transactions can be selected based on tax reporting
type and tax reporting code.
VAT Inter-EU Invoice Journal for Identifies detail and summary information on invoices received in
Spain Spain from suppliers located in any European Union member state.
Invoices are entered and posted in Oracle Payables and have offset
or self-assessed tax distributions. The transactions can be selected
based on tax reporting type and tax reporting code.
ble
VAT Inter-EU Invoice Format for Spain Lists details of the same invoices that appear on the Spanish VAT
Inter-EU Invoices Journal report. The transactions can be selected
fe r a
based on tax reporting type and tax reporting code.
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
in tude
Before you run the VAT reports for Spain, ensure you:
@
• Configure the document sequencegto r
abe usedisforSreporting and printing transactions on the reports.
w a th process to select and mark transactions for reporting.
• Run the Select Transactions
s h s e
for Tax Reporting
uwant
l (areports
When you finish reviewingathe
e t o
and to close the tax period, run the Finalize Transactions for Tax
Reporting process. a w
r process
The nsmarks all the reported transactions as finally reported.
g c e
r y aA li
w a
As h

Modelo Reports for Spain
Modelo reports for Spain are based on Turnover Reporting processes.
Title Description
Modelo Verification Report for Lists all payables invoices and receivables transactions that are
Spain reported in the Modelo 340, 347, 349, or 415 declarations. The
report prints data based on the selected legal entity, period range,
source, and Modelo name. For receivables cash receipts, only
receipts above the entered minimum cash amount are reported.
Modelo Electronic File Generation Prepares electronic file for Modelo 340, 347, 349, or 415
for Spain declarations in a legally predefined format.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
The Modelo Reports for Spain are legally required iturnover
@ de delivered electronically in a predefined
n tureports,
format to the tax authorities in Spain.
g a r s S
a
w date h i
or ttransaction date, depending on the type of Modelo and
h
Modelo reporting is based on accounting
s s e
source of data.
a l (a to u
A transaction can be reported
a e reports, which are submitted annually, quarterly, or monthly.
rw einnsmultiple
A g
Run Modelo Electronic l
File icGeneration for Spain for one period at a time and verify your transactions or
summaryry
a
w a data.
AsTohgenerate the Modelo reports, run the following processes:
• Run the Turnover Reporting Selection Process in preliminary mode.
• Select the Reporting Group parameter as Modelo Reporting for Spain. The Turnover Reporting
Selection Process selects all the transactions with accounting date or transaction date within the
selected periods.
• Run the Modelo Verification Report for Spain.
• Run the Modelo Electronic File Generation for Spain to generate XML files for Modelo 340, 347, 349,
and 415, for a specific period.
• Run the Turnover Reporting Selection Process in final mode to mark transactions as reported.

Withholding Tax Reports for Spain
Withholding Reports
Title Description
Withholding Tax Report for Spain Identifies summary or detail withholding tax information for
Spain by invoice and withholding tax code. The report prints
information for a selected legal entity, and optionally for a
specific supplier.
Withholding Tax Magnetic Format Lists withholding tax transactions for the selected legal entity
for Spain and tax year in a flat file format in the predefined layout.
Withholding Tax Extract Report for Extracts withholding tax transactions for Spain and stores them
Spain in an interface table to be used to report withholding tax
transactions. The report selects information for a specific legal ble
entity, and optionally for a specific supplier.
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Reports for Germany
Subledger and Accounting Reports
Title Description
Z4 Report for Germany Lists all incoming and outgoing payments done through a
foreign bank.
Z5A Reconciliation Report for Shows the sum of all outstanding receivables and liabilities of
Germany goods and services traded with foreign suppliers or customers.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Correction Documents for Poland
The Corrections Documents for Poland feature help to comply with Polish legal
requirements
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Navigate to: Tools > Scheduled Processes > Schedule
@ de > Correction Documents for Poland
in NewtuProcess
r
gaInvoice s Sbe done using a Correction Document.
Any correction to a Value Added Tax (VAT)
a h i
must
w setaxt (VAT) document, which contains the changes to a
h
A correction invoice is a separatesvalue-added
ua customer.
a (a issued
transaction that has alreadyl been t o to
arw select
In Scheduled Processes,
g e n seCorrection Documents for Poland process.
the
Choose thea A
transaction l
youicneed to correct and enter the correction information. You can apply a whole
ary to make a full reversal of the invoice, apply a discount to all the invoice lines, or create a
price adjustment
w
h of the original invoice for making manual corrections in the Review/Edit Transaction pages.
Ascopy Steps to Enable
• Define Receivables transaction sources for correction documents. A specific transaction source for
processing correction documents must be defined.
• Define Receivables transaction types for correction documents. A specific transaction type for
correction documents is required, ensuring that the correction documents can contain both positive
and negative lines.
• Define Receivables transaction types for regular transactions. For each transaction type for which
correction documents are created, update the Regional Information Correction Invoice Transaction
Source and Transaction Type that must be used for that transaction type.
• Define descriptive flexfields for Receivables AutoInvoice. Define specific segments for use when
importing the Correction Invoice using Receivables AutoInvoice.

Jednolity Plik Kontrolny (JPK) Reporting for Poland
• Legally defined electronic format (XML) for electronic submission to the tax authorities
• Generates outputs for:
– Sales and Purchase VAT Registers
– Standard Audit File for Tax (SAFT) for Poland

• Includes report for the JPK Sales and Purchase Register information
• Includes four different extracts
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
JPK includes the following extracts:
@ in tude
• JPK Accounting Books Extract forg a r s S
a Poland
wfor Poland t h i
• JPK Bank Statements Extract
s h s e
•
a (aPolandto u
JPK Invoices Listingl for
• arw
JPK Sales and Purchase n e
sRegisters for Poland
A g l i c e
a rya
s h w
A

Print Commercial Documents for Poland
• Select Receivables transactions you want to print, using Poland specific templates.
• Parameters define the transaction source and add filters to identify particular
transactions
• Print transactions in draft or final mode.

• Control currency type for amounts.
• Use the BI Publisher tool to define user layouts provided they are registered with Print
Commercial Documents for EMEA.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Printing Process
@ in tude
The printing process completes using these
r
gasteps:this S
a
wuse forseeach document being printed according to the following logic:
The program determines the layout s hto
• a
Checks the Print Template o u to see if you asked for a particular layout.
l (a eparameter
t
• g
Determines atherwlayout
c e ns to the Document Fiscal Classification when the Print Template
assigned
r y a A is blank.li
parameter
• waLooks for the value in the Regional Information segment Print Template, set on the Receivables
h
As Transaction Types when no layout is assigned to the Document Fiscal Classification.
The actual printing process is launched as Print Commercial Documents Child Process.
The Process Execution Report is generated.
Printing in Draft or Final Mode
• Draft mode is used to verify that the data is complete and correct before final printing. Once they are
printed in Final mode, the Print status field of the printed transactions changes to Printed and these
are no longer available for printing in Final mode.
• After an Invoice prints in Final mode, the you can print a copy of this output, marked as Duplicate by
selecting the attachment of the printed invoice from the Edit/Manage Receivables Transactions
page.
• You can also control the currency type to be used for the amounts. The selection provided is for
Entered or Ledger Currency.

Tax Point Date Adjustment Feature in Payables
• Changes the tax point date of a Payables transaction

• Reports the transaction in a period different from initial period defined by your tax
configuration.
• Adjust tax point date at header or line level.

• Require a tax point basis of Invoice, and a status of Validated.
ble
fe r a
an s
Adjusting Tax
Point Date at
n - t r
Line Level
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
• Use the Tax Point Date Adjustment featureiin
@
nPoland t u dechange the tax point date of a Payables
to
r s Sdifferent from the one initially defined by your tax
ga in athperiod
transaction, and report the transaction
configuration. a
w se i
• s h
a to u transactions at header and/or line level.
Adjust the tax point date
l ( of Payables
taxapoint date
Note: If you adjust therw
g a e nseand
taxcperiods
of transactions already reported, you may need to resubmit the Tax
a A
reports for the impacted
l i issue separate Correction Documents to reflect the changes.
ary all solution related setup for Payables before using the Tax Point Date Adjustment feature.
Tip: Complete
w
Ash the adjusted tax point date on the transaction line is null.
• Adjustments at header level update the tax point date on the tax lines of all transaction lines where
• Adjustments at line level update the tax point date of the tax lines for just that transaction line.
• After changing the tax point date in the Create and Edit Invoice pages, submit the Process Tax Point
Date Adjustments process.

Israel: Generate VAT File in 835 Format
Generate a detailed statement of VAT in the 835 format, for uploading to the Israel Tax
Authority website.
The VAT report is part of the tax reporting process.
To generate this report, follow these steps:

• Run the Select Transactions for Tax Reporting process for your tax reporting entity and
tax period.
• Submit the Generate VAT Report for Israel process.
• After the report is generated, upload the output file to the Israel Tax Authority website.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Steps to Enable
@ in tude
You must assign the Tax Reporting Codes
r S
gtoa yourthtaxisrates.
a
w seCodes determine the VAT file line type to which the tax lines
s
While creating the VAT file, the TaxhReporting
should be assigned.
a l (a e to u
Tips
g arw cens
r y a APayablesliand Receivables transactions, you can enter the additional information for VAT
When you enter
a in the Regional Information on the header and lines.
reporting
w
h
As • Payables invoice header - Tax Authority Reference Group
• Payables invoice line - Import Document Number, Import Document Date
• Receivables invoice header - Tax Authority Reference Group
• Receivables invoice line - Export Document Number, Export Document Date\
If the Israel Tax Authority changes the VAT Aggregation amount limit, you can change the value of the
profile option ORA_JEIL_835_LIMIT.
To check if an associated VAT file line type is missing from a transaction, republish the output file in CSV
format and apply filters.
You can also see detailed information about each transaction in the CSV output.
Role Information
To use this feature, you need the following role:
• Duty Role Name and Code: EMEA Financial Reporting duty role
(ORA_JE_EMEA_FINANCIAL_REPORTING_DUTY_CRM)

Norway: Generate Data Extract for Norway SAF-T
Use the Generate SAF-T Data Extract to prepare the Norway specific audit report, based on
General Ledger transactions. Using this extract you can obtain the following information:
• Master Files section information for the Natural Accounts.
• Master Files section information for the Third Parties with transactions during the
reporting period, or with non-zero balances for the same period.
• General Ledger and Subledger Accounting journal information for the reporting period,
or for a range of days within a period.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Tips
@ in tude
r
A specific hierarchy structure needs to be inaplace for the
g s SNatural Account segment.
The hierarchy structure should have w a h i
tlevel account.
s h e
a single top
s
This top level account valuel is(a
used intotheuGenerate SAF-T Data Extract parameters.
w a e
Role Information ar
g c e ns
A the lfollowing
This featurearequires i role:
a r y
• w Duty Role Name and Code: Generate SAFT Extract (JG_GENERATE_SAFT_EXTRACT_PRIV)
A s h

APAC Reporting
Oracle Financials Cloud for Asia/Pacific provides:

reporting needs.

• Predefined reports for:
– China
– Japan
– Singapore
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Report for China
Subledger Report
Title Description
General Ledger Journal and Lists the mapping relationship between the General Ledger
Subledger Transaction Mapping Journals and source subledger transactions details.
Report
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Report for Japan
Title Description
Japan Payment Register with Bank Lists payments with calculated bank charges. This
Charges Report report is used to review the amount of bank charges
deducted from a payment.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Report for Singapore
Title Description
Input Tax Gain and Loss Report Produces the details on tax gain or loss on transactions for
for Singapore Singapore entered in foreign currencies in Oracle Payables.

The report lists data for a specific supplier or all suppliers. The
report data is grouped by tax rate code and supplier.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Thailand Withholding Tax Certificate Report and Sequence
Numbering
You can use the Thailand Withholding Tax Certificate Report and Sequence Numbering
feature to:
Maintain the Add a revenue type

withholding tax in an AP invoice line
certificate sequence by associating the
numbering rule by tax reporting code
using ADFdi. with the product
category.
Add a PND type in a tax

line by associating the Generate the
tax reporting code with withholding tax
ble
the tax rate. Add a certificate sequence
fe r a
condition in an AP number for AP
payments. an s
payment header by using
n - t r
no
GDF.
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Navigate to: Others > Setup and Maintenance > Setup:
@ in Financials
t u de > Check Functional Areas > Click
Change Feature Opt In
g a r s S
Note: Generate the Thai withholdingw a h i
t report for AP payments according to the withholding tax
certificate sequence number. (a s h u s e
tax certificate
a l t o
Steps to Enable
g a rw ense
You must enable
a l ic using opt-in page in Functional Setup Manager as the following steps.
A the feature
Navigate
w artoy the Setup and Maintenance work area.
h Financials from the Setup drop down list.
AsSelect
Check Functional Areas and Click on the Change Feature Opt In.
On the Opt In: Financials page, click the Features icon, then navigate to Regional Localization and enable
Thailand localization.
Key Resources
For information on adding the duty role (APAC Financial Reporting) to the job role (such as Tax Manager)
see:
• Financials Setup Overview chapter in the Receivables Oracle Financials Cloud: Receivables to
Collections Implementation Student Guide.

Report for India: Export Letter of Undertaking and Under Rebate for
India
The legal requirements of exports under letter of undertaking for India require you to:
• Define a letter of undertaking.
• Track all export outbound transactions against the letter of undertaking.
You can use the Export under Letter of Undertaking and Under Rebate for India to:
Mark export Track the Capture details Mark export

transactions as of proof of transactions as
details and exports and
export. balance for a export under
accordingly rebate and create
particular update the
financial year. balance for the
the required
ble
running account. accounting.
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@
n require:
The legal requirements of exports under rebate foriIndia
t u de
• g a r s S liability, which must not be charged to the
GST assessed on the tax invoice accounted
a
w se t h i
as payable
customer.
s h
Steps to Enable
a l (a e to u
a rw thisefeature.
You must opt in to enable
g ns For instructions, refer to the Optional Uptake of New Features section
A
of this document.
a li c
r y
a the feature from the Functional Setup Manager Opt In page:
To enable
h w
As 1. Navigate to the Setup and Maintenance work area.
2. Search for the Manage Localization System Options task.
3. On the Manage Localization System Options page, select the business unit for which this feature
needs to be enabled. Ensure that the country for the business unit is India.
4. Select Yes for the Enable Document Number option.
Note: Currently, this feature is applicable only to export of services.

Payables Extension to Support Generation of Tax Invoice Number
for India Reverse Charge Invoices
Use the India GST Fiscal Document Numbering feature to Generate sequence for tax
invoice, refund voucher and payment voucher in payables application.
The existing ADFDi spreadsheet for document numbering now has new values for the
following columns:
• Fiscal Document: Use this column
to specify if the document is a tax
invoice, payment voucher or a
refund voucher.
• Application: Choose Payables for
the required document numbering in
ble
accounts payable.
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
This feature is automatically enabled.
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
r y aA li
w a
A s h

India: Copy Tax Compliance Attributes to Payables Invoices for India
Use the Copy Tax Compliance Attributes to Payables Invoices for India feature to:
• Experience improved accuracy and efficient processing in claiming the input tax credit
for India GST.
• Automatically populate the tax determinants from the purchase order or the receipt lines
to the matched Payables invoices.
• Ensure that the tax determinants are available when the recoverable taxes are
processed and accounted.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Creating a Receipt or Purchase Order Matched Payables
@ in Invoicet u de
• g r
a order s S Payables invoice, the first-party tax
When you create a receipt or a purchase
a t h i
w taxseregistration
matched
invoice’s India Regional s h

registration number and third-party
a to u
information line GDFs from
number are automatically populated to the
the purchase order or receipt lines.
l (
•
a r
This enables you wtoa comply
n sewith the India GST transactional requirements and process recoverable
taxes basedg e
lic Payables Invoice
on the first- party tax registration number.
a A Matched
CreatingrayReceipt
a
• w When you create a receipt matched Payables invoice, the tax invoice number and tax invoice date
h
As are automatically populated to the invoice’s India Regional information line GDFs from the receipt
lines based on the tax fiscal document provided by supplier of inbound transactions.
Note: Before you apply this feature, ensure that the Regional Localization for India checkbox is enabled in
the Functional Setup Manager.
Tips
• When you create a transaction, ensure that the taxation country is India.
• When you create a receipt matched payables invoice, ensure that all matched receipt lines have the
same first-party tax registration number.

India: Default First-Party Tax Registration Number for India
Use the first-party tax registration number as a transaction tax determinant in tax rules to
calculate the applicable taxes and process the recoverable taxes.
• Set a default value for the first-party tax registration number of the receiving or purchase
trade organization on requisitions and purchase orders.

• Ensure accuracy in tax calculation and efficient processing in claiming input tax credits
for India GST, which are based on the first-party tax registration number.
• Avoid manual intervention in deriving the first-party tax registration number of the
receiving or purchase trade organization on requisitions and purchase orders.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in Financials
t u de > Legal Structures > Show: All Tasks >
Manage Associated Business Entities.
g a r s S
a
w sthat h i
t Regional Localization for India checkbox is enabled in
h
Note: Before you apply this feature, ensure
s e the
the Functional Setup Manager
a l (a to u
w nsUnit
Associating the LegalrReporting
a e
g
A associate
To apply this feature, l e
ic the legal reporting unit of the applicable first-party tax registration number to
a
ary or purchase trade organization. To associate the legal reporting unit:
the receiving
w
Ash1. Sign in with a role similar to that of an Application Implementation Consultant.
2. Navigate to: Others > Setup and Maintenance > Setup: Financials > Legal Structures > Show: All
Tasks > Manage Associated Business Entities.
3. Select the applicable legal entity and legal reporting.
4. Click Add.
5. Select the applicable type.
NOTE: The Type represents a receiving organization, which can be a Ship-to location, inventory
organization, or business unit based on your organization structure and the applicable India GST
place of supply rules.
6. Select the applicable name.
7. Enter the start date.
8. Click Save and Close.

Associating the Legal Reporting Unit
• To apply this feature, associate the legal reporting unit of the applicable first-party tax
registration number to the receiving or purchase trade organization.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ
m nt Gc
ฺ i b
@ in Financials
t u de > Legal Structures > Show: All Tasks >
Manage Associated Business Entities.
g a r s S
a t h i
w of anseApplication
s h
1. Sign in with a role similar to that
a and u
Implementation Consultant.
2. Navigate to: Others l> (Setup o Maintenance > Setup: Financials > Legal Structures > Show: All
a t
Tasks > Manage
g a rwAssociated
e n seBusiness Entities.
A applicable
3. Select the
a l ic legal entity and legal reporting unit.
ry Add.
4. aClick
w
Ash5. Select the applicable type. Note: The Type represents a receiving organization, which can be a Ship-to location, inventory
organization, or business unit based on your organization structure and the applicable India GST
place of supply rules.
6. Select the applicable name.
7. Enter the start date.
Tips
To default the first-party tax registration number, ensure that the taxation country for transaction is India.
By default, the First-Party Tax Registration Number field is not displayed on requisitions and purchase
orders pages. You can use page customization to show this field.
To avoid inaccurate tax calculation and input tax credit recovery, ensure that all receiving organizations on
purchase order lines or schedules are associated to the legal reporting units with the same first-party tax
registration number.

Deferred Tax Recovery for India
Defer recognition of recoverable taxes on Payables invoices and accounts as provisional or

interim recoverable tax.
• Comply with India GST’s input tax credit rules to avail recoverable taxes on regular
supplies, reverse charge supplies, internal material transfers, and import of goods.
• Defer recovery of recoverable taxes until the events specified by the GST authority of
India are met.
• Process the deferred recoverable taxes from a provisional or an interim recoverable tax
account to the final recoverable tax account per first-party tax registration number.
• Account tax liability instead of the reversal of input tax credit for transactions on which
the input tax credit has already been claimed. ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
You must opt-in to enable this feature.
@ in tude
You can recover the deferred recoverablegtaxes
r
a onlyisif: S
w a th
•
s h
The tax invoice is GST-compliant.
athe e
us of India to claim the input tax credit are complete.
• The events specified l
a se(
by t
GST o authority
r winvoice
•
A g licencompliance attributes include:
The requiredatax
a ry-- a Supplier tax invoice number.
s h w Supplier tax invoice date on the India Regional information GDFs of the Payables invoice
A line. Supplier tax invoice date.
- Original tax invoice number.
- Original tax invoice date on the India Regional information GDFs Payables debit and credit
memo line GDF.

Using Deferred Tax Recovery for India
To apply Deferred Tax Recovery for India:

• Navigate to: Others > Setup and
Maintenance > Setup: Financials >
Transaction Tax > Manage Taxes.

• Search for the required transaction tax.
• Click Control and Defaults tab.
• In Tax Recovery Controls and Defaults
section, enable the Defer recovery for
specialized handling checkbox.
• ble
Click Save and Close.
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ t de > Transaction Tax > Manage Taxes.
in Financials
u
Tips
r
ga this S
a
wthe feature
h
To use this feature, you must optsinto
a u s e and enable the Defer recovery for specialized handling
checkbox.
a l ( e to
a w ns recoverable tax on the Payables invoice, ensure that the interim tax
r oreinterim
To account the provisional
g c
a A at the lTax
account is defined
r y
i or Tax Rate level.
w a
As h

Integrate with E-Way Bill Framework for India
Eliminate manual steps to process and record E-Way bills by leveraging the integration of
India GST E-Way Bill systems with ERP Cloud. You can:
• Register a GSP as a tax partner and create partner tax profile.
• Capture the GSP credentials such as, client ID and password.

• Capture taxpayer’s NIC portal credentials such as, GST registration number and
password.
• Invoke GSP REST API to generate E-Way bill number and capture its response.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
You must opt-in to enable this feature.
@ in tude
For some business processes, the Indiang
r
a legislation
s Smandates that registered suppliers generate an E-
a GST
w se t h i
Way Bill.
s h u GST Suvidha Providers (GSP) who facilitate taxpayer
l (a atlist
The GST authority of India provides
a o of
integration with the E-Way
g se
arw cBillensystem.
r y aA li
w a
As h

Enabling Electronic Filing of GST Annexure-1 Per Revised GST
Reporting Structure for India
• Enable mandatory filing of GST Annexure-1 electronically as required by revised GST
reporting structure for India.
• Use to report suppliers GST liability on outbound taxable supplies and inward supplies
where recipient is required to self-assess/pay the GST.

• The extract contains details of all outward supplies, inward supplies liable to reverse
charge, and imported goods and services required for the annexure.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
• This filing is mandatory for every GST registered
@ in taxpayer
t u de other than composite dealers, and those
organizations which are registered as
g r
a Input service
s S distributors (ISD).
• The Taxpayers can configurew a h i
t based on the Tax Reporting Ledger tables' fields and
s h s e
the BIP report
a to u format so that it can be imported into the GSTN provided
can create the report in
offline utility tool. a l ( the pre-described
• g ause se the outward supplies tax and integrate the outward supplies tax to
rw it toeretrieve
n
You can also
a A
system. l
ic
ry
GSTN
thisafeature you can:
Using w
Ash• Run the GST Annexure-1 process to extract the required dataset required for filing GST Annexure-1
report from both Receivable and Payables modules.
• Leverage the Global Tax Reporting Ledger (TRL) to create the India GST Outward supply
Repository.
• The ANX-1 report can be created in the GSTN prescribed format.
• Create BIP report based on Tax Reporting Ledger tables’ data in the GSTN provided format of ANX-
1 report.
• Change only the BIP report data model logic in case of any future changes to the GST reporting
format of ANX-1 and not have any product dependency.
• Effectively handle any Error, if notified by GST portal upon filing of ANX-1 report.
.

Running the Report Tax Liability Electronically for the India Output
Tax
Enter
Parameters
ble
fe r a
an s
n - t r
a no
has eฺ
)
ฺ c om uid
Steps to Enable
ฺ i b m nt G
@
To enable, associate the Taxes defined in the FSM u deTaxes Types to:
in into tIndia
r sS
ga GSTthtaxes.
•
a
Separate these taxes from the Non i
wagainstseeach tax type while filing the monthly GST reports.
• s h
Extract relevant information
a to urole/privilege is required to do the setup
a
Application Implementation l (Consultant
arw >cSetup
1. Navigate to:gOthers e nseand Maintenance > Financials > Transaction Tax > Manage Taxes >
y
Search
r a forAthe required
li Transaction tax.
2.wGoa to Tax Reporting Codes and click on Add Row
As h
3. Enter the required values to classify the Tax.
Process Steps
The Tax Manager role/privilege is required to run the Process.
1. Navigate Tools > Scheduled Processes > Schedule New Process.
2. Search for the Job: Report Tax Liability Electronically for India Output Tax.
3. Enter the required parameters and run the Process.

Tax Reporting Ledger Tables
There are three Tax Reporting Ledger Tables:
• ZX_REP_CONTEXT_T: With each run of ANX-1 Process, one record is populated in this table
against the Request_Id of the job.
• ZX_REP_TRX_DETAIL_T: Contains tax information for tax reporting purposes from Accounts
Payable and accounts Receivable, and Tax repository.
•
ZX_REP_TRX_JX_EXT_T: Summary Table for GST ANX-1 Report. It contains the ANX-1 Section
information against the transactions inserted into the table zx_rep_trx_detail_t.
More details can be found in this link:
https://docs.oracle.com/en/cloud/saas/financials/18b/oedmf/ZX-tables.html
Tips
To create the GST ANX-1 BIP report data model, you do an SQL join on the 3 Tax Repository Ledger tables
and group the data based Table requirements of GST ANX-1 report format.
ble
The minimum eligibility criteria of the Transactions picked by the Process are:
fe r a
• Receivables transactions should be in COMPLETE status.
ans
• Payables Invoices should be in ACCOUNTED status. n - t r
n o
a
You are expected to write the logic of the BIP report data model so that it fetches any Transaction line
has eฺ
having the Maximum Version Number for the ANX-1 reporting.
)
ฺ c om uid
ฺ i b m nt G
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Generate Customer Balance Reconciliation Report for Russia
Generate the Customer Balance Reconciliation Report for Russia to periodically reconcile
settlements with customers.
The Customer Balance Reconciliation Report for Russia includes the following receivables
documents:
• Invoices
• Debit Memos and Credit Memos
• Receipts from customers
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
in tuBalance
This feature is available after adding the Review Customer
@ de Reconciliation Report for Russia
privilege,
g a r s S
a
w se t h i
h
JE_CUSTOMER_BALANCE_RECONCILIATION_REPORT_FOR_RUSSIA_PRIV,
s
to any duty or job role.
a l (a e to u
g arw cens
r y aA li
w a
As h

Generate Receivables and Payables Audit Report for Russia
Use the report to review the audit results of settlements with suppliers and customers. The
report contains:
• First Party Organization details and document details.
• Aggregated debt information and liability information on the customer and receivables
account balances, and supplier and payables account balances.
• Report addendum which lists the source documents for the payables and receivables
transactions, including amounts, the start dates of debts and the supporting document
details.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
The report Addendum lists the source documents for
@ t de and receivables transactions, including
inthe payables
u
a r
amounts, the start dates of debts and the supporting
g S details.
document
s
a
w se t h i
Steps to Enable
s h u Customer Balance Reconciliation Report for Russia
l
The feature is available after
a (a the
adding t oReview
g arw cense
privilege, JE_CUSTOMER_BALANCE_RECONCILIATION_REPORT_FOR_RUSSIA_PRIV, to any duty or
aA li
job role.
a r y
h w
As

Generate VAT Reports for Russia
Generate a purchase and sales ledger report with an additional sheet for adjustments, and a
tax invoice register report containing invoices issued and received.
In Russia you must legally report tax related information quarterly.
Use this feature to meet the tax reporting requirement by providing the following extracts:
• Purchase Ledger and Purchase Ledger Adjustment Sheets
• Sales Ledger and Sales Ledger Adjustment Sheets
• Invoice VAT Register – Received Invoices Register and Issued Invoices Register
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Navigate to: Tools > Scheduled Processes > Select
@ inTransactions
t u de for Tax Reporting process and Tax
Allocation process
g a r s S
• The extract data are providedw a h i
t line level of detail and need to be grouped and
s h s e
at transaction
a to u Authorities.
l (
formatted before reporting to Russian Tax
a sefor Tax Reporting process and Tax Allocation process before submitting
• Run the Select w
a r Transactions
g for Russia enprocess that creates output files for Russia specific reporting.
VAT Reports
a A l i c
Mandatory
a rySetup
s h
This wfeature groups data in the appropriate output files based on the tax boxes assigned to the transaction
A lines.
You must set up Tax Box Allocation Rules and related components to ensure that the feature works
correctly. The recommended setup is:
• Document Fiscal Classification Codes
• Transaction Business Category Codes
• User-Defined Fiscal Classification Codes
• Intended Use Fiscal Classification Codes
• Tax Reporting Types and Codes
• Tax Determining Factor Set
• Tax Condition Sets
• Tax Box Allocation Rules
Transaction Process
Regional Information – Invoices for Russia section on the transaction level and transaction line level
provides additional fields that must be populated to capture Russian specific transaction details.

Prepare VAT on Export Report for Russia
Generate a listing of export sales invoices and the status of the related confirmation
documentation.
Use the VAT on Export Report for Russia to monitor the status of your export sales
transactions and to complete these tasks:

• Identify export sales transactions for which the export documentation is not fully
confirmed.
• Track the export sales transactions that have passed the grace period and the ones for
which the grace period will expire soon.
• View the related VAT on Export invoices VAT Refund invoices.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Steps to Enable
@ in tude
r S after completing the security setup.
ga thisavailable
The VAT on Export Report for Russia is automatically
a
w typessfor
•
a s h
Define Receivables transaction
u e Export Sales invoices.
• Depending on thea l ( eregulations
customs to related to the grace period, you may need different export
w
ar types.
sales transaction ns
•
g c
Agrace period e
li number of days in the Regional Information for Russia when creating your
r y a sales
Enter the
w aexport transaction types.
Ash• Define Receivables transaction types for VAT on Export invoices.

• Define Receivables transaction types for VAT on Export Refund invoices.
Tips
• When entering export sales transactions, record the export date and the total amount confirmed by
the customs authorities in the regional information of the transaction header.
• For the unconfirmed amount of an export sales transaction when the grace period has expired, enter
a VAT on Export invoice and link it to the export sales invoice.
• After the grace period is over, enter a VAT on Export refund invoice for the amount confirmed after
the date. This allows you to offset the previously recorded VAT on Export amount. Link your VAT on
Export Refund invoice to the original export sales invoice.

Russia Asset Reporting for Asset Repair and Maintenance
• Comply with Russia Asset Reporting requirements by recording your asset repair,
modernization, and reconstruction expense details.
• Use the Maintenance Order spreadsheet to capture the work and job order details
(including freight) for each asset under repair or update and its expected return to
production date.
• Leverage the generic reporting extract for your compliance reports.
ble
fe r a
Manage
an s
Maintenance
n - t r
no
Order
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
in Maintenance
Navigate to: Assets > Task > Transactions > Manage
@ t u de Order
You must opt in to enable this feature. ga
r s S
a
w se t h i
Role Information s h
a
The Asset Accounting Manager t o uAccountant job roles are automatically updated.
l (aande Asset
g arw cens
r y aA li
w a
As h

Tax Agent Invoice for Russia
The Tax Agent Invoice for Russia feature creates tax agent invoices for selected supplier
payments using a spreadsheet.
• VAT law in Russian Federation requires separate VAT invoice to be issued by company
acting as Tax Agent for selected foreign or non-taxable purchases with place of supply
under Russian jurisdiction.
• The Tax Agent invoice includes the self assessed tax that must be paid to the Russian
Tax Authority before the original, supplier invoice payment is reconciled.
• You can recover the related output VAT only after payment confirmation of the Tax
Agent invoice.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Creating a Tax Agent Invoice
@ in tude
• Launch the Tax Agent Invoice for g r
a spreadsheet
s S and search for supplier payments that are
a Russia
w Invoice. t h i
s h
candidates to issue the Tax Agent
s e
u to create a tax agent invoice and provide the additional
• l
Mark the payments for
a (awhich you
t o want
information. w
g a r ense
• Upload A
a l ic to create the tax agent invoices.
the spreadsheet
ry and pay the tax agent invoices, and print a copy of the invoice.
• aValidate
w
h to Enable
AsSteps
You must opt in to enable this feature. 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 Tax Agent Invoice for Russia.
3. Click Opt-In.
4. On the Edit Features page, select the Enable option for the feature.
5. Click Done.
Tips
Following the recommended setup approach, the tax reporting lines for purchase ledger and sales ledger
reports are available on the tax agent invoice.
The tax reporting of unconfirmed tax agent invoice payments for purchase ledger tax lines can be deferred
to the next tax period using the tax point date adjustment feature.

LAD Reporting
Oracle Financials Cloud for Latin America provides:

reporting needs.

• A predefined reports for Mexico, Argentina, Chile and Colombia
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Report for Mexico
Title Description
Journals for Mexico Provides information about all transactions that are
accounted and posted in different subledgers. The

report also provides information related to electronic
invoices generated for sales or received from suppliers
for purchases.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Withholding Tax Reporting for Argentina
The following withholding tax reports comply with fiscal reporting requirements in Argentina.
• Purchase Withholding File for Argentina
• Purchase Withholding Certificate for Argentina
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Purchase Withholding File for Argentina
@ in tude
• g r
a zonal, s S provincial withholding tax information into
This report electronically reports federal,
a
various AFIP applications thatwrun under SIAP. t h i and
s h s e
u the file into the correct AFIP application, if required. After the
• Run the report monthly
a l (abeforetimport
o
arw tax
flat files are imported, e applications produce all required information, including flat files, and
thesAFIP
n
A g
can also generate
l i c ereports for control purposes.
• The a
ry Argentine Payables Withholding Flat File has three formats, each for different jurisdictions:
a
w - Federal - For VAT and Income withholding taxes
A s h
- Zonal - For RS and SUSS withholding taxes
- Provincial - For Turnover tax withholding taxes
Purchase Withholding
• Use this report to generate supplier withholding certificates.
• The withholding certificate is a legal document that you send to the supplier as a proof of withheld
taxes on payments. The report produces one certificate per payment for each withholding tax type,
province (if applicable), withholding category, and zone (if applicable).
• The certificate contains standard information and information specific to the withholding tax type.
• The system generates a unique certificate number by withholding type and province.
Steps to Enable
Select the Financials offering to enable Argentina in the Regional Localizations offering option
• Navigate to Setup and Maintenance > Setup: Financials > Change Configuration > Click Features >
Enable Argentina under Regional Localization.
• Assign the LAD Financial Reporting duty role to users to access these reports.

Argentina: Generate Withholding Certificate Number and Capture
Additional Attributes
• You can now generate withholding certificate numbers while creating payments.
• The certificate number is included in the disbursement XML payment file, along with
additional information required by banks in Argentina.
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b e Manage Document Sequence
in tu> dSearch:
Navigate to: Others > Setup and Maintenance > Financials
@
Categories
g a r s S
a
wNumbering t h i
s h
Configuring Sequences for Certificate
s e
u Categories page, click the Plus sign (+) to define a new
1. On the Manage Document
a l (a Sequence
t o
category.
g a rw ense
A and Close.
2. Click Save
a l ic
ry for Manage Document Sequences.
3. aSearch
w
Ash4. Select Manage Document Sequences from the results.
5. On the Manage Document Sequences page, click the Plus sign (+) to define a new sequence.
6. Assign the new sequence to the document category in the Assignment section.
Assigning Sequences to Required Context
Navigate to: Others > Setup and Maintenance > Financials > Search: Manage Localization Document
Numbering
1. On the Manage Localization Document Numbering page > Search for drop-down list > select
Argentina.
2. In the Create Document Numbering in Spreadsheet dialog box, select the Business Unit and set
Configuration For as Setup for withholding certificate numbering.
3. Click OK to download the file.
4. Add the required context as a new row and upload the file.

This feature uses sequences to generate certificate numbers for withholding certificates.
You must ensure that sequences are defined and then assigned to the correct context for all the withholding
taxes.
Once this feature is enabled, you cannot disable it.
If you prefer not to enable this feature, you can continue using the existing Generate Purchase Withholding
Certificate for Argentina process to generate the certificate numbers.
ble
fe r a
ans
n - t r
n o
a
) has eฺ
ฺ c om uid
ฺ i b m nt G
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Argentina: Enable 2018 Legislative Updates for Document
Sequencing for Argentina
• Enable 2018 legislative mandate for Argentina for document sequencing with five-digit
point of sale number support for Receivables transaction numbers.
• Create or import Receivables transactions.
• On completion, the transaction number generated will have a five- digit point of sale
number with left side padding.
Imported
ble
Transactions
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
You must opt in to enable this feature.
@ in tude
1. Navigate to: My Enterprise > New g r S
a >isReceivables.
Features
a
w Updates h
t Document Sequencing for Argentina.
h
2. Click Opt-in to 2018 Legislative
s s e for
uthe Enable option for the feature.
(a select
3. On the Edit Featuresl page,
a t o
4. Click Done. arw
g e n se
a A l ic
w ary
Ash

Argentina: Enable 2018 Legislative Updates for Document
Sequencing for Argentina
• Existing Receivables transactions which already have the transaction number generated
with a four-digit point of sale number as part of the transaction number are not changed
or updated to five-digit.
• This occurs even if they are incomplete and completed again after the 2018 legislative
changes are introduced.
Four-digit
POS
Number
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Withholding Tax Reporting for Chile
The following withholding tax reports comply with fiscal reporting requirements in Chile.
Purchase
Withholding
Certificate for
Chile
Purchase
Purchase Withholding
Withholding of Certificate
Fees Ledger Summary Report
Report for Chile
ble
fe r a
an s
Withholding Tax
Reports for Chile
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Purchase Withholding of Fees Ledger Report for Chile
@ in tude
• g r
aFees Ledger
s S report (Libro de Retencion de Honorarios) details
The Chilean Purchase Withholding
all the invoices paid during a w a of
h i
t on which amounts were withheld.
s h e
particular period
s
• Use this report to show
a t o u that you withheld taxes for invoices subject to withholding tax.
l (atax eauthorities
•
arw conly
The report includes
g e s
ninvoices subject to withholding.
r y a A Certificate
Purchase Withholding li for Chile
• aIn Chile, you must send your suppliers withholding tax certificates to certify that you withheld taxes
s h w from the professional service fees and participation amounts you paid the suppliers.
A • The withholding tax certificates show both the gross invoice amounts and the tax withheld for each
month in the tax year.
• If a supplier had only professional service fees in a particular tax year, you must send the supplier a
Fees Certificate.
• If a supplier had both professional service fees and participation, you must send the supplier a Fees
and Participation Certificate.
• Use this report to print both kinds of withholding tax certificates.
• The document type assigned to the invoices from each supplier is used to determine which
withholding certificate to print for the supplier.
Purchase Withholding Certificate Summary Report for Chile
• Use this report to review summarized information about each supplier for whom you generated an
official certificate.
• For each certificate, the report shows the certificate number, the supplier, the last date the certificate
was printed, the taxable amounts for professional service fees, and participation if applicable, and
the amount of tax withheld.

Withholding Tax Reporting for Colombia
The following withholding tax reports comply with fiscal reporting requirements in Colombia:
• Purchase Withholding Report for Colombia
• Purchase Withholding Certificate for Colombia
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Purchase Withholding Report for Columbia
@ in tude
• r
a purposes.
Use this report for managerial andgauditing s S The report details tax withholding information
a h i
t withholding type. The report shows the document
w on sanye tax
s h
for a taxable period. It can report
a to u
l (
number, withholding accounting date, taxable base amount, and withholding amount by tax
a r wa nseflexfield and supplier.

withholding type, accounting
• g liceTax details also include the VAT amount. Totals for the supplier, accounting
The VAT Withholding
Aand
y a
flexfield
r tax withholding type are calculated.
a
w Withholding Certificate for Columbia
s h
Purchase
A • Use this report to print supplier withholding certificates. For each withholding tax type, you provide
withholding certificates for each supplier where you withheld taxes. The certificates are normally
printed annually to cover all withholding taxes for a tax year; however, you can print this report for
any supplier for any period.
• The withholding certificate has the same general format for each of the withholding tax types,
including the taxable period, company information, supplier information, city where the tax was
withheld, and the city where the withholding tax was paid.
• Withholding information includes the taxable base amount and withheld amount for each concept.
The VAT withholding certificate includes additional information for each concept, such as the VAT
amount and the reported tax rate for the tax code.
Steps to Enable: Assign the LAD Financial Reporting duty role to users for access to these reports.
Tip: You can modify the predefined report formats to meet implementation-specific requirements or to
comply with changes to local regulations.

Summary
In this lesson, you should have learned to:

• Export Enterprise Financial Data for China.
• Describe the reports by country for EMEA.
• Understand the reports by country for APAC.

• Explain the reports by country for LAD.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

D
Additional Resources
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h
Lesson Objectives

• Find additional application resources
• Use the Oracle Help Center to find additional information
• Access helpful video content to learn more about specific features
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ryaA li
w a
A s h
Oracle Financials Cloud: Payables to Cash Management Implementation D - 2

Oracle Cloud Implementation Resources
Classroom and Other Resources:

• Oracle Financials Cloud: Payables to Cash Management Implementation Student Guide
(this guide)
• Oracle Financials Cloud: Using Payables

• Oracle Cloud Applications Help in the Applications
• Oracle Technology Library on OTN
• My Oracle Support (MOS)
• Oracle Help Center
• Oracle Customer Connect ble
• fe r a
cloud.oracle.com
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
• in tude
Oracle Technology Library on OTN: http://www.oracle.com/technetwork/index.html
@
• r
ga this S which includes the following documents:
My Oracle Support (MOS) (https://support.oracle.com/),
a
w Cloud
- Getting Started withh
a s Oracle
u s e Applications: Common Implementation, Article ID
1387777.1 on
a l ( e to
Oracle Support
- w
a cens
OraclerCloud Applications: Financials Reporting (Document 1458904.1)
Oracle A
g
•
r y a Help Centerli (https://docs.oracle.com/en/), including the following Oracle Financials Cloud
w abooks:
As h - Getting Started with Your Financials Cloud Implementation

- Implementing Accounting Hub
- Implementing Enterprise Structures and General Ledger
- Using Common Features for Oracle Applications Cloud (including infolet personalization
topics)
- Customizing the Applications for Functional Administrators (including infolet customization
topics)
- Using Oracle Social Network
- Security Reference for Oracle Financials Cloud
- Creating Analytics and Reports for Financials Cloud
- Administering Analytics and Reports for Oracle Financials

- Using Analytics and Reports for Financials Cloud
- Using General Ledger
- Using Hyperion Calculation Manager
- Using Hyperion Enterprise Performance Management Workspace
- Using Hyperion Financial Reporting
- Using Hyperion Financial Reporting Charting
- Using Hyperion Financial Reporting Mobile

- Using Smart View for Office
- Administering Essbase Administration Services
- Administering Essbase Administration Services Online Help
- Administering Essbase Database
- Administering Hyperion Enterprise Performance Management Workspace Enterprise
ble
fe r a
ans
n - t r
n o
a
) has eฺ
ฺ c om uid
ฺ i b m nt G
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

Oracle Help Center: docs.oracle.com
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Oracle Help Center is:
@ in tude
• Central hub for all documentation g r
a tutorials.
s S
a and
w seincludingt h i
• Organized by major producthcategories Cloud, Applications, Middleware, and Database.
a s u
a l ( e to
w
ar cens
g
r y aA li
w a
As h

Cloud Application Services Pages
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
Links to application families and to Get Started. in
@ t u de
Consistent organization, content, and linkg
r
a for iCloud
format s S service pages: Friendly task panel to use to
a
w se t h
change focus from Cloud to:
s h u
• Cloud Applications l (a o
a t
• arw cense
Cloud Intrastructure
g
•
aA
Cloud Platform
r y li
• aCloud Marketplace
s h w
A • Cloud at Customer

Financials Home Page
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
The Financials Home Page in Oracle Help Center gives
@ de to:
in youtuaccess
• The ability to select your update. ga r s S
a t h i
• List of help topics by task. hw e
s u
(a (guides). s
• Links to videos and lbooks
a t o
• aryour
Option to start
g e n se
w subscription.
• Linksa toA l ic
the new features.
w ary
A sh

Video Subject Areas on the Oracle Help Center
Link to the Video Area in Oracle Help Center

• Get Started
• Use General Ledger
• Use Accounting Hub

• Use Subledger Accounting
• Use Payables invoice to Pay
• Use Receivables Credit to Cash
• Use Other Oracle Financial Cloud Products
• ble
Implement
fe r a
• Configure and Extend
an s
• Analyze and Report n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
Navigate to the videos: Oracle Help Center (https://docs.oracle.com/en/) > Applications > Fusion Cloud
Apps > Financials > Videos.
g a r s S
a
w following h i
tvideos :
The Configure and Extend includes the
s h u s e
• l (a and
Configuring the Navigator
a t o
springboard
• rw etonHelp
Adding HelpaContent
g se Windows
a
The Get Started ic following videos :
Aincludeslthe
ry infolets to identify issues and prioritize tasks.
• waUse
Ash• Use work areas to streamline business processes.
Note: New videos are constantly being added to the video area in the Oracle Help Center.

Reference Guides
• File Based Data Import includes links to:

– Spreadsheets templates
– Load and import processes
• Tables and Views includes:

– Columns
– Primary and Foreign Keys
– Indexes
• SOAP (Simple Object Access Protocol)
Web Services
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
in tud>eApplications > Fusion Cloud Applications >
Navigate to: Oracle Help Center (https://docs.oracle.com/en/)
@
a r
Financials > Books. The guides are in the Development
g s Ssection.
• a h i
wis usedseto tload data into Oracle Cloud Applications from external
s h
File Based Data Import (FBDI)
a to and u third-party applications. The File Based Data Import for Oracle
l (
sources, such as legacy systems
a r wa nincludes
Financials Cloud Guide
s e links to:
-
a A g
Spreadsheets
iceused to load data into Oracle Cloud Applications from external sources, such
as legacy lsystems and third-party applications. The spreadsheet templates help to structure,
w ary format, and generate the data file according to the requirements of the target application
Ash tables.
- File-based load process to load the data files into the interface tables.
- Application-specific data import processes to transfer data from interface tables to the
application tables in your Oracle Cloud Applications.
• Tables and Views for Oracle Financials Cloud Guide includes:
- The tables with the basic information about the table columns, primary and foreign keys, and
indexes.
- The views, columns, and query details that are associated with each view.
• SOAP (Simple Object Access Protocol) Web Services for Oracle Financials Cloud Guide include:
- Business Object Services relationships, operations, and security
- Service Data Objects relationships and attributes
Note: Use SOAP web services to integrate with or extend Oracle Applications Cloud. Through web
services, you can integrate heterogeneous applications within the enterprise or expose business functions
to Oracle Cloud partners and customers over the Internet.

Friendly Search
ble
fe r a
an s
n - t r
a no
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
in tud>eApplications and type a word or phrase in
Navigate to: Oracle Help Center (https://docs.oracle.com/en/)
@
the Search box. You can:
g a r s S
• a h i
w typeseyourt topic in the field.
s h
Enter a simple search entry: Just
u results: Results show the guide as well as the topic with
• Review a comprehensive
a l (a viewtofo search
g a rwtopic.ense
direct links to the
• View the
a Anumber loficresults and context displayed.
ry the Search task pane to reduce the number of results.
• aRefine
w
Ash• Follow the breadcrumbs that appear at the top of topics you select to allow easy return to the list of
results.

Summary

• Find additional application resources
• Use the Oracle Help Center to find additional information
• Access helpful video content to learn more about specific features
ble
fe r a
an s
n - t r
n o
a
) has eฺ
om uid
ฺ c
m nt G
ฺ i b
@ in tude
r
ga this S
a
w se
s h
a l (a e to u
g arw cens
ry aA li
w a
A s h

As h w a
ry
aA
g li
a
s
arw cens
h
a
l (a e to u
r
w se
@
ฺ i b
ga this S
ฺ c
in tude
)
m nt G
om uid
a
has eฺ
o n n
- t r an
sfe r a bl
e

AP Guides1

Hochgeladen von

Dokumentinformationen

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

AP Guides1

Hochgeladen von

Copyright:

Verfügbare Formate

Unauthorized reproduction or distribution prohibitedฺ Copyright© 2017, Oracle and/or its affiliatesฺ

Oracle Financials Cloud: Payables to

Student Guide – Volume II

Learn more from Oracle University at education.oracle.com

Bruce Ingram Disclaimer

1 Oracle Financials Cloud: Payables to Cash Management Implementation

Configuring Table Columns 2-23

Self-Service External Identity Provider Setup 3-43

4 Financials Setup Overview

Learn More: Video Tutorials and User Guides 4-37

5 Enterprise Structures and Ledgers Overview

Business Unit Structure: Example 6-5

7 Configuring Oracle Payables

Managing Payment Terms 7-8

Manage Payables Document Sequences 7-53

aryaTasks to Configure Oracle Tax 8-8

Define Taxes for Rapid Implementation Task List 8-29

Invoice Approval Flow 10-13

Account Rules Overview 11-29

12 Configuring Oracle Payments: Payables

Disbursement Payment File Formats 12-12

Implementation Overview: Setups 12-57

Code Map Group Example 13-23

14 Reporting for Payables, Payments, and Subledger Accounting

A Common Application Topics

Define Flexfields A-10

Profile Option Values A-65

Reports for Spain C-20

Argentina: Enable 2018 Legislative Updates for Document Sequencing for

Configuring Oracle Payments: Payables

After completing this lesson, you should be able to:

• Manage payment methods.

Oracle Financials Cloud: Payables to Cash Management Implementation 12 - 2

Oracle Financials Cloud: Payables to Cash Management Implementation 12 - 3

Oracle Financials Cloud: Payables to Cash Management Implementation 12 - 4

• Processes invoice payments from Oracle Payables.

Oracle Financials Cloud: Payables to Cash Management Implementation 12 - 5

• The Payments disbursements process includes selected disbursement setups of

• A payment can take:

Oracle Financials Cloud: Payables to Cash Management Implementation 12 - 6

Oracle Financials Cloud: Payables to Cash Management Implementation 12 - 7

• Key Decision: How much of the payment process should I automate?

Oracle Financials Cloud: Payables to Cash Management Implementation 12 - 8

Key Decision: What invoice selection criteria should I use?

• Recommended for a Centralized or Service Provider Processing model.

Oracle Financials Cloud: Payables to Cash Management Implementation 12 - 9

The three main components are:

Oracle Financials Cloud: Payables to Cash Management Implementation 12 - 10

Oracle Financials Cloud: Payables to Cash Management Implementation 12 - 11

• Each format creates an outbound message.

Oracle Financials Cloud: Payables to Cash Management Implementation 12 - 12

• Key Decision: What formats should I use?

Oracle Financials Cloud: Payables to Cash Management Implementation 12 - 13

Key Decision: How do I modify templates?

• An XML extract provides Payments data.

Oracle Financials Cloud: Payables to Cash Management Implementation 12 - 14

Oracle Financials Cloud: Payables to Cash Management Implementation 12 - 15

The following concepts apply to payments transmission:

Oracle Financials Cloud: Payables to Cash Management Implementation 12 - 16

• Favor transmission protocols that are predefined in Payments.

Oracle Financials Cloud: Payables to Cash Management Implementation 12 - 17

This practice covers the following topics:

Oracle Financials Cloud: Payables to Cash Management Implementation 12 - 18

Oracle Financials Cloud: Payables to Cash Management Implementation 12 - 19