cloud oracle financials · oracle financials cloud implementing payables invoice to pay preface ii...

Oracle FinancialsCloud

Implementing Payables Invoice toPay

20A

Oracle Financials CloudImplementing Payables Invoice to Pay

20APart Number F24523-01Copyright © 2011, 2019, Oracle and/or its aliates. All rights reserved.

Authors: Asra Alim, Wallace Gardipe, Mary Kalway, Barbara Kostelec, Carol Ann Lapeyrouse, Sampriti Singharoy

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

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

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

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

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

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

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

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

The business names used in this documentation are ctitious, and are not intended to identify any real companies currently or previously in existence.


Contents

Preface i

1 Automated Invoice Processing Conguration 1How Integrated Invoice Imaging Works for Oracle Cloud Implementations ..................................................................... 1

Considerations for Integrated Invoice Imaging for Oracle Cloud Implementations ....................................................... 3

Considerations for Receiving Invoice Images from Email ................................................................................................... 5

Routing Incomplete Invoices ...................................................................................................................................................... 7

How to Override Default Business Units on Unmatched Scanned Invoices .................................................................... 9

Processing Electronic Invoices ................................................................................................................................................. 10

2 General Payables Options 15Manage Common Options for Payables and Procurement ............................................................................................... 15

Manage Invoice Options ........................................................................................................................................................... 24

Manage Payment Options ........................................................................................................................................................ 34

Manage Tax Reporting and Withholding Tax Options ....................................................................................................... 35

3 Payables Conguration 43Distribution Sets .......................................................................................................................................................................... 43

Payment Terms ........................................................................................................................................................................... 43

Payment Terms and Reference Data Sharing ...................................................................................................................... 45

Example of Creating Payment Terms Based on Days ....................................................................................................... 48

Invoice Tolerances ...................................................................................................................................................................... 50

Invoice Holds and Releases ...................................................................................................................................................... 52

Considerations for Payables Calendar Period Frequencies ............................................................................................... 53

How Periods for Payables Calendars Are Generated ......................................................................................................... 54

How You Set Up Third-Party Payments ................................................................................................................................ 56

Auditing Payables Business Objects ....................................................................................................................................... 57

FAQs for Payables Conguration .......................................................................................................................................... 162


4 Payables Tax and Withholding 165Guidelines for Reporting Limit Methods for Income Tax Regions ................................................................................. 165

Reporting Entities ...................................................................................................................................................................... 165

Dene Payables Setup for Withholding Tax ....................................................................................................................... 166

Withholding Tax Codes ............................................................................................................................................................ 167

Withholding Tax Code Rate Types ....................................................................................................................................... 168

Withholding Tax Classications ............................................................................................................................................. 169

Withholding Tax Certicates and Exceptions ..................................................................................................................... 170

FAQs for Payables Tax and Withholding .............................................................................................................................. 171

5 Approving Invoices 173How Invoices Are Approved ................................................................................................................................................... 173

6 Conguration for Rapid Implementation 175Overview of Invoice and Payment Conguration for Rapid Implementation ............................................................... 175

7 Disbursements 177Electronic Payments ................................................................................................................................................................. 177

Check Payments ......................................................................................................................................................................... 181

How Disbursements Are Processed ...................................................................................................................................... 186

Payment Methods ...................................................................................................................................................................... 191

Usage Rules ................................................................................................................................................................................ 192

Payment Method Defaulting .................................................................................................................................................. 193

Payment Process Proles ........................................................................................................................................................ 194

How You Set Up Payment Approval .................................................................................................................................... 196

How You Implement the Granting Payment Function Access Setup Task ................................................................... 197

How You Use Oracle BI Publisher Enterprise to Modify Templates for Use with Formats ....................................... 200

Example of Seing Up User-Dened Validations for Payment Methods or for Payment Files ................................ 201

FAQs for Disbursements ......................................................................................................................................................... 203


8 Payment System Connectivity 205Options for Validations ........................................................................................................................................................... 205

How You Set Up Formats ....................................................................................................................................................... 206

Transmission Protocols ........................................................................................................................................................... 209

Transmission Congurations ................................................................................................................................................. 209

How You Set Up Transmission Congurations .................................................................................................................. 210

How You Congure Prey Good Privacy (PGP) Encryption and Digital Signature for Outbound and Inbound Messages

......................................................................................................................................................................................................... 212

How You Test the Transmission Conguration ................................................................................................................. 215

How You Set Up a Payment System .................................................................................................................................... 216

Payment System Accounts ..................................................................................................................................................... 218

Import a Security Credential File .......................................................................................................................................... 220

FAQs for Payment System Connectivity .............................................................................................................................. 221

9 Payments Security 223System Security Options: Critical Choices ........................................................................................................................... 223

Enable Encryption of Sensitive Payment Information ...................................................................................................... 226

Set Up a Supplier's Bank Account ........................................................................................................................................ 227

How You Update Bank, Branch, and Bank Account Numbers on External Bank Accounts ...................................... 230

How Supplier Bank Account Import Data is Processed ................................................................................................... 230

Removal of Personally Identiable Information ................................................................................................................ 236

FAQs for Payment Security .................................................................................................................................................... 243


10 Cash Management and Banking Conguration 245How Bank, Branch, and Account Components Work Together ..................................................................................... 245

Considerations When You Create Accounts ...................................................................................................................... 246

Cash Management Prole Options ...................................................................................................................................... 247

Overview of Parse Rule Sets .................................................................................................................................................. 248

Overview of Transaction Type Mapping ............................................................................................................................. 250

Overview of Tolerance Rules .................................................................................................................................................. 251

Reconciliation Matching Rules ............................................................................................................................................... 252

Overview of Reconciliation Rules Sets ................................................................................................................................. 257

Overview of Bank Statement Transaction Codes .............................................................................................................. 257

How You Map Congurable BAI2 Transaction Codes ...................................................................................................... 258

Overview of Bank Statement Transaction Creation Rules ............................................................................................... 259

Create Banks, Branches, and Accounts in Spreadsheet .................................................................................................. 259

Seing Up Cash Positioning and Forecasting .................................................................................................................... 261

Bank Account Validation ........................................................................................................................................................ 264

11 Business Events 347Overview of Public Business Events .................................................................................................................................... 347

Business Events for Payables ................................................................................................................................................ 347

Enable the Payables Business Events Prole Option ........................................................................................................ 351

Business Events for Payments .............................................................................................................................................. 352

Enable the Payments Business Events Prole Option ...................................................................................................... 352


Preface

i

PrefaceThis preface introduces information sources that can help you use the application.

Using Oracle Applications

HelpUse help icons to access help in the application. If you don't see any help icons on your page, click your user imageor name in the global header and select Show Help Icons. Not all pages have help icons. You can also access the OracleHelp Center to nd guides and videos.

Watch: This video tutorial shows you how to nd and use help.

You can also read about it instead.

Additional Resources

• Community: Use Oracle Cloud Customer Connect to get information from experts at Oracle, the partnercommunity, and other users.

• Training: Take courses on Oracle Cloud from Oracle University.

ConventionsThe following table explains the text conventions used in this guide.

Convention Meaning

boldface Boldface type indicates user interface elements, navigation paths, or values you enter or select.

monospace Monospace type indicates le, folder, and directory names, code examples, commands, and URLs.

> Greater than symbol separates elements in a navigation path.

https://docs.oracle.com/en/cloud/saas/applications-help/

https://docs.oracle.com/en/cloud/saas/applications-help/

https://apex.oracle.com/pls/apex/f?p=44785:265:0::::P265_CONTENT_ID:27341


http://www.oracle.com/pls/topic/lookup?ctx=cloud&id=OACPR158049

https://appsconnect.custhelp.com/

http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=906


Preface

ii

Documentation AccessibilityFor information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website.

Videos included in this guide are provided as a media alternative for text-based help topics also available in this guide.

Contacting Oracle

Access to Oracle SupportOracle customers that have purchased support have access to electronic support through My Oracle Support. Forinformation, visit My Oracle Support or visit Accessible Oracle Support if you are hearing impaired.

Comments and SuggestionsPlease give us feedback about Oracle Applications Help and guides! You can send an e-mail to:[email protected].

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs

mailto:[email protected]


Chapter 1Automated Invoice Processing Conguration

1

1 Automated Invoice Processing Conguration

How Integrated Invoice Imaging Works for Oracle CloudImplementations

Watch video

The integrated invoice imaging solution for Oracle Cloud provides scanned image import, intelligent characterrecognition, and automatic invoice creation. In addition, the solution routes invoices with exceptions to accountspayables personnel for review and completion.

This gure shows the integrated invoice imaging ow.

E-Mail Scanned Images

RouteInvoices

EditInvoices

Exception Management

Oracle Cloud

Import Images

RecognizeImages

StoreImages

ProcessInvoices

PayInvoices





2

Here's a summary of the steps in the imaging process followed by details of the processing ow.

1. To use the integrated invoice imaging solution, you must have a designated e-mail account to send the invoiceimages. When you sign up for the Oracle Cloud Application Service, you're provided with one.

2. After you have the e-mail account, prepare the invoices for processing.

◦ If your business process is to receive invoice images from your suppliers, communicate to them yourimaging requirements. The suppliers can then e-mail the invoice images directly to the designated e-mailaccount.

◦ If you receive paper invoices, prepare images from the invoices and send the images to the e-mailaccount.

3. Once the images are sent to the e-mail account, the imaging solution retrieves them for further processing. Thesolution checks for new images every minute and creates invoices from the images.

4. If any exceptions occur during automatic invoice creation, the invoices are marked as incomplete and routedto accounts payable personnel for review and completion. The incomplete invoices appear in the Scannedinformation tile on the Invoices landing page.

5. After the rest of the invoice processing tasks are nished, such as validation and approval, the invoices areready for payment.

E-Mail Scanned ImagesBased on agreements with your suppliers, you might receive paper invoices at your bill-to locations, or you mightreceive images by e-mail. You can communicate imaging requirements to your suppliers, such as to send images in theTIFF format with a minimum of 300 dpi.

For images sent by e-mail, imaging specialists can check for quality and proper formaing. For paper invoices, imagingspecialists can sort the invoices into dierent categories based on parameters, such as geography, invoice type, invoiceamount, and due date. They can then scan the invoices to convert them to images.

Imaging specialists forward the images to the designated e-mail account. They can optionally specify aributes in the e-mail subject for the purposes of routing and recording.

Import ImagesOracle Imaging retrieves the images from the designated e-mail account at scheduled intervals. All of the invoiceimages in an email are grouped into a batch.

Recognize ImagesThe imaging solution then sends the batches for intelligent data recognition and extraction of the invoice aributes.

Oracle's Imaging Solution oers cuing-edge intelligent recognition capabilities for extracting the invoice aributesfrom the scanned images. Unlike other solutions that use supplier-specic templates to extract information, Oracle'sImaging Solution can intelligently locate data within the invoice. The data can be found regardless of its location on theimage and whether Imaging has processed invoices from that supplier before. As suppliers are added, or an existingsupplier changes its invoice layout, Imaging can extract the aributes from the new invoice layouts.

Store ImagesOracle Imaging stores the invoice images and extracted information. For the rest of the invoice life cycle, any referenceto the invoice image points to the imaging repository. This ensures documents are never replicated further duringinvoice processing.



3

Process InvoicesThe imaging solution uses the extracted aributes from the images to create the invoices. If exceptions occur duringprocessing, the invoices are marked as incomplete and routed to accounts payable personnel using Oracle BusinessProcess Execution Language (BPEL) workows. A default routing rule routes the incomplete invoices to all users withthe Accounts Payable Specialist and Accounts Payable Supervisor job roles.

Incomplete invoices appear in the Scanned information tile on the Invoices landing page. Invoice header aributes andlines requiring aention are highlighted on the Edit Invoice page for quick identication and resolution. With a dualmonitor setup, you can review both the invoice and the invoice image at the same time.

Oracle Imaging provides an image viewer that's embedded within Oracle Fusion Payables. Accounts payable personnelcan review and annotate the images using the embedded image viewer.

This gure shows the Scanned information tile on the Invoices landing page.

Pay InvoicesAfter you complete the rest of the invoice processing tasks, such as validating, approving, and accounting, the invoicesare ready to be paid. You can schedule a payment process request to select them for payment.

Related Topics

• What's an incomplete invoice

http://www.oracle.com/pls/topic/lookup?ctx=fa20a&id=E46A24095BCF25CCE040D30A68813473



4

Considerations for Integrated Invoice Imaging for OracleCloud ImplementationsThe integrated invoice imaging solution for Oracle Cloud provides scanned image import, intelligent characterrecognition, and automatic invoice creation. In addition, the solution routes invoices with exceptions to accountspayables personnel for review and completion.

Scanning Invoice ImagesReview these critical points for scanning invoices.

• Consider any legal requirements for processing and storing invoices in the same country that received theinvoices.

• Scan invoices in black and white using the TIFF image format with International Telegraph and TelephoneConsultative Commiee Group IV compression at 300 dpi. Scanning this way provides the optimal balancebetween scan quality and image size.

Note: Avoid the JPEG format because the lossy compression logic results in loss of image details,aecting recognition accuracy.

• Enable adaptive thresholding technology on scanners to remove background colors, gray scaling, andgradients for pure black and white images. Black and white images provide optimal Optical CharacterRecognition accuracy as well as a reduced image size.

• To achieve a higher rate of recognition:

◦ Dene purchase order numbers as a combination of leers and numbers instead of using the defaultseven-digit numeric format. For example, dene purchase order numbers like CN388392.

◦ Implement a uniform numbering scheme for purchase orders across all business units.

Aaching Invoice Images in E-MailReview these critical points for aaching invoice images in e-mail.

• Include invoice images in e-mail aachments in the following ways:

◦ Single page invoice in one aachment

◦ Multiple page invoice in one aachment

◦ Multiple invoices in one aachment

◦ Single and multiple page invoices in multiple aachments

• Organize invoices within the aachments for successful recognition. If you have:

◦ Single page invoices in an aachment, you don't have to place a blank page between invoices as aseparator.

◦ One multiple page invoice in an aachment, place a blank page at the end or beginning of theaachment. This method prevents processing each page as a single page invoice.

◦ More than one multiple page invoice in the batch, insert a blank page between the invoices.



5

◦ Both single and multiple page invoices in an aachment, insert a blank page between invoices.

Note: If you have supporting documentation there is a designated separator page you can insert between theinvoice and the supporting documentation. For more information see the MOS document: DOC ID 2017464.1.

Processing InvoicesReview these critical points for processing invoices.

• Schedule the Import Payables Invoices and Validate Payables Invoices processes to run every 15 to 30 minutes.

• Dene distribution sets for your supplier sites.

• Modify the invoice routing rule to achieve the specialization that you want within your payables department.For example, route the incomplete invoices based on supplier, business unit, or invoice amount. Routing thisway can ensure the payables personnel process invoices based on their specic assignments. The default ruleroutes all incomplete invoices to users with the Accounts Payable Specialist and Accounts Payable Supervisorjob roles.

Related Topics


• Distribution Sets

Considerations for Receiving Invoice Images from EmailThe integrated invoice imaging solution provides for processing invoice images that are received by email.

The email must be sent in a certain format and meet specications that are acceptable by Oracle's Imaging Solution.Imaging specialists must scan and convert the paper invoices received from suppliers to images. Alternatively, ifinvoices have been received as email aachments, imaging specialists check for quality and proper formaing.

You can optionally enter aributes in the email subject for recording on the invoice and for routing if the invoices areincomplete. A precongured routing rule is provided to route incomplete invoices to all users with Accounts PayablesSpecialist and Accounts Payable Supervisor job roles.

Consider the following when receiving invoice images through email.

Invoice Images as Email AachmentsInvoice images can be included in email aachments in the following ways:

• Single page invoice in one aachment.

• Multiple page invoice in one aachment.

• Multiple invoices in one aachment.

• Single and multiple page invoices in multiple aachments.

Note: A single invoice can't be represented by multiple aachments.




6

Tip: Depending on the size of each scanned image, consider grouping the images into a single email tooptimize the number of emails sent for processing. You can have multiple aachments on the same email.

Aribute Information in the Email SubjectYou can specify up to four aributes in an email subject. These aributes can be recorded on the invoice or used toroute the incomplete invoices to payables personnel for review and completion. Use the underscore sign (_) as aseparator to indicate the start of routing aribute information.

Note: You can also use one of these aributes to override the default business unit on an unmatchedscanned invoice. This aribute is always Routing Aribute 1.

For example, you have a specic business requirement to record categories on the invoice. These categories includeinvoice priority, supplier category, manufacturing plant number, storage bin number, and processing queue. You canspecify values for these categories in the email subject.

This table lists the categories and their possible values.

Category Value

Invoice priority

Regular, Urgent

Supplier category

Regular, Supply chain related

Manufacturing plant number

Plant-1, Plant-2, Plant-3

Storage bin number

Bin#1, Bin#2, Bin#3

A supplier sends an invoice with the email subject of Invoice-1234 aached. The imaging specialist reviews theemail and provides additional routing information in the email subject. The revised email subject is Invoice-1234aached_Urgent_Supply chain related_Plant-1_Bin#1.

This table shows how the content in the email subject maps to the routing aributes.

Email Subject Content Routing Aribute Mapping

Invoice-1234 aached

Not applicable since the text appears before the rst separator character

Urgent

Routing aribute 1

Supply chain related

Routing aribute 2

Plant-1

Routing aribute 3

Bin#1 Routing aribute 4



7

Email Subject Content Routing Aribute Mapping

Tip: The routing aribute number and the category aren't explicitly linked together. You must enter the valuefor the category in the same order.

The supplier sends another invoice with the email subject of Invoice-2345 aached. The revised email subject isInvoice-2345 aached_Regular_Supply chain related_Plant-1_Bin#1. The routing rule is dened as follows:

• If routing aribute 1 = Urgent, assign invoice image to accounts payable specialist Harry.

• If routing aribute 1 = Regular, assign invoice image to accounts payable specialist Nathan.

In this example, invoice 1234 is assigned to Harry and invoice 2345 is assigned to Nathan.

As in the previous example, aributes can include alphanumeric characters. The maximum length for each aributedepends on how many aributes you're using. For example, if you use all ve aributes, the maximum length of eacharibute is 34 characters. You can modify the maximum length of each aribute to meet your requirements however,the sum of the aribute values should not exceed the limit. This limit is calculated as follows, assuming that all veaributes are used.

• Total number of characters allowed by Oracle Forms Recognition: 233

• Number of characters in the default le path areC:\OFR\Import\: 14

• Number of characters in the le extension .tif, including the period: 4

• Number of characters reserved for internal use as a unique reference number: 40

• Number of separator characters: 5

• Limit is the total characters minus le path minus le extension minus reserved characters minus separatorcharacters (233-14-4-40-5): 170

Note: The limit changes if you use fewer than ve aributes, because fewer separators are needed.

If the aribute in an email subject exceeds the maximum length specied for that aribute, the Oracle Imaging processerrors.

Routing Incomplete InvoicesAn incomplete invoice is an invoice created from an image that has invalid or missing information. Incomplete invoicesare automatically routed to users with the Accounts Payable Specialist and Accounts Payables Supervisor job roles forreview and completion.

Routing Rule AdministrationYou can modify the predened routing rule using the Approval Management extensions of the Oracle SOA Suite andOracle Human Workow. The Oracle Business Process Management (BPM) Worklist application provides the interfaceto administer the rule.

Users with the Financial Application Administrator job role are BPM Worklist administrators and can accessthe rules in the BPM Worklist application. To navigate to the BPM Worklist application, use the Manage Task



8

Congurations for Financials task. The predened task that assigns and routes incomplete invoices is called theFinAPIncompleteInvoiceHold task.

TasksThe following table lists the predened seings for the FinAPIncompleteInvoiceHold task.

Field Seing

Task Aggregation

Once per stage

On Error Notify

Not applicable

Allow all participants to invite otherparticipants

Not enabled

Allow participants to edit futureparticipants

Not enabled

Allow initiator to add participants

Not enabled

Enable automatic claim

Enabled

Complete task when participantchooses

Not enabled

Enable early completion of parallelsubtasks

Not enabled

Complete parent tasks of earlycompleting subtasks

Not enabled

Expiration and Escalation Policy

Never Expire

Reminders

No reminders

Rule Sets and RulesThe FinAPIncompleteInvoiceHold task has a rule set, which is a collection of rules, called IncompleteInvoiceRuleSet.This rule set has a rule called JobRoleAssignmentRule. Rules consist of IF and THEN components. The IF componentspecies the conditions that determine when to apply the rule. The THEN component species what happens when theconditions are met.

The following table lists the predened seings for the JobRoleAssignmentRule rule.



9

Field Value Description

Condition

FinAPHoldApprovalPayloadType.holdName is "Incomplete Invoice"

Activates the rule when the invoice isplaced on an incomplete hold. To useother invoice aributes, select from thecondition browser window.

List Builder

Resource

Determines the resource to which theinvoice is routed.

Response Type

Required

Indicates that the routing noticationrequires a response.

Participants

Users: null, Groups: "AP_ ACCOUNTS_PAYABLE_ SPECIALIST_JOB AP_ACCOUNTS_ PAYABLE_ SUPERVISOR_JOB" Application Role: null

Identies the participant to whom theinvoice is routed.

Rule Name

"JobRoleAssignmentRule"

Identies the approval reason to display inthe approval history diagram.

Rule ConditionsYou can use the available invoice header, line, and distribution aributes in the routing rule condition.

To edit the rule condition:

1. Start a search in the in the IF section of the rule. The Condition Browser opens.2. Select the aribute to use in the condition.

Related Topics


How to Override Default Business Units on UnmatchedScanned InvoicesBusiness units for unmatched scanned invoices are automatically determined based on aributes, such as supplieraddress and the Default Business Unit prole option. You can override automatic business unit assignment and instead,specify a business unit by performing the following steps:

• Indicate that routing aribute 1 represents the business unit.

• Find the business unit ID for the overriding business unit.

• Specify the business unit ID in the e-mail subject.




10

Indicate Routing Aribute 1 Represents Business UnitAs part of the standard invoice imaging ow, you can use up to four additional aributes to route scanned invoices forcompletion or to record on the invoice. To override the default business unit, you must indicate that values for routingaribute 1 represent business units.

Perform these steps:

1. Navigate to the Manage Payables Lookups page.2. Search for lookup type ORA_IMAGING_ROUTING_ATTRIBUTES.3. Enable lookup code ORA_BUSINESS_UNIT.

Find the ID for the Overriding Business UnitYou must use the identier for the business unit as the override. To nd the business unit ID:

1. Navigate to the Manage Business Units page.2. Search for the applicable business unit.3. If you don't see the Business Unit ID column in the Search Results table, use the View menu to enable the

column.

Specify the Business Unit ID in the E-mail SubjectFor scanned invoices that aren't matched to purchase orders, edit the e-mail subject to:

1. Append the underscore sign (_) followed by the business unit ID. For example, if a scanned invoice has an e-mail subject of Invoice 42366_30014001, the business unit ID for that invoice is 30014001.

Note: If you specify an invalid ID, or the ID is missing from the e-mail subject, the business unit isautomatically assigned.

Processing Electronic InvoicesOracle Fusion Payables provides the ability to receive electronic invoices from suppliers. Oracle Fusion CollaborationMessaging Framework (CMK) provides a simplied way to set up business to business (B2B) communication withtrading partners.

CMK supports two models for seing up B2B messaging with trading partners.

1. Using a service provider: In this model, a service provider such as Oracle Business Network acts as anintermediary between the trading partners and the Fusion Applications customers. Once a trading partner ison-boarded to OSN, the partner can exchange messages with any Fusion Applications client. OSN is denedout of the box in CMK but you can also dene other service providers if needed.

2. Using CMK web service: CMK provides a web service for exchanging messages with CMK directly without usingOracle Business Network or other service providers



11

This gure illustrates invoice processing through email using the Collaboration Messaging Framework.

Conguring Collaboration Messaging FrameworkSetup Electronic Invoicing Using a Service Provider

CMK includes the Oracle Business Network (formerly Oracle Supplier Network) as a service provider out of thebox, making it very easy to setup, and connect to trading partners on the network. Other service providers must becongured in the Collaboration Messaging work area as follows:

1. Navigate to Manage Collaboration Messaging Service Providers.2. Create a new Service Provider.3. In Delivery Methods, you can specify how outgoing messages should be delivered to the service provider.4. Select Inbound Collaboration Messages tab to congure XML invoice formats that will be used by the service

provider. Each XML format supported by CMK is available as a separate message denition. For example, selectUBL_2.1_EN_16931_INVOICE_IN for EN 16931 invoice in UBL format.

5. In Outbound Collaboration Messages tab, you can congure the list of outbound messages that are required forthe service provider.

6. Save and Close.

Next, you have to congure the Trading Partners using this service provider.

1. Navigate to Manage B2B.2. Select the Service Provider and enter the trading partner identication.3. Select Inbound Collaboration Messages and add the XML invoice formats that will be used by this supplier.

The supplier sites used for electronic invoicing must be associated with trading partners.

1. Navigate to the supplier site and select B2B Communication method as Collaboration Messaging Framework.2. In Associated Collaboration Documents, click the Edit buon. Add the trading partner created earlier and add

PROCESS_INVOICE_IN under Collaboration Documents.



12

Setup Electronic Invoicing Using CMK Web ServiceIf the supplier communicates directly using the CMK web service, then there is no need to setup a service provider.

1. Navigate to Manage B2B Trading Partner.2. Select Service Provider as None and enter the trading partner identication.3. In Delivery Methods, you can specify how outgoing messages should be delivered to the supplier.4. Select Inbound Collaboration Messages tab to congure XML invoice formats that will be used by the supplier.

Each XML format supported by CMK is available as a separate message denition. For example, selectUBL_2.1_EN_16931_INVOICE_IN for EN 16931 invoice in UBL format.

5. In Outbound Collaboration Messages tab, you can congure the list of outbound messages that are required forthe supplier.

6. Save and Close.

Associate the supplier sites with the trading partner.

1. Navigate to the supplier site and select B2B Communication method as Collaboration Messaging Framework.2. In Associated Collaboration Documents, click the Edit buon. Add the trading partner created earlier and add

PROCESS_INVOICE_IN under Collaboration Documents.

Send Rejected Invoices to a Supplier

Electronic invoices received by CMK must be imported using Import Payables Invoices. Invoices that are rejected dueto supplier errors, are automatically sent to the supplier by email for correction. The supplier has to resend the invoicepayload after they have been corrected.

Note: Email with rejected invoice details are sent to a supplier only when the supplier email ID is provided inthe XML invoice.

The following steps explain the setup required to send rejection emails automatically to a supplier when they arecongured using a service provider:

1. Navigate to Manage Collaboration Messaging Service Providers.2. Add a Delivery Method of type Email.3. Select Outbound Collaboration Messages tab and add the message denition

OAGIS_10.1_ACKNOWLEDGE_INVOICE_COLLAB_MSG_OUT. Select the delivery method created above.4. Navigate to the supplier site.5. In Associated Collaboration Documents, click the Edit buon and add ACK_REJECTED_INVOICE_OUT under

Collaboration Documents.

The following steps explain the setup required to send rejection emails automatically to a supplier when they arecongured without a service provider:

1. Navigate to Manage B2B Trading Partners.2. Add a Delivery Method of type Email.3. Select Outbound Collaboration Messages tab and add the message denition

OAGIS_10.1_ACKNOWLEDGE_INVOICE_COLLAB_MSG_OUT. Select the delivery method created above.4. Navigate to the supplier site.5. In Associated Collaboration Documents, click the Edit buon and add ACK_REJECTED_INVOICE_OUT under

Collaboration Documents.

Extend Electronic Invoice Conguration



13

CMK delivers pre-seeded message denitions that map the XML payload elds to the Fusion application objects such asInvoices using XSLT les. Customers can change the mappings delivered out of the box, to accommodate either tradingpartner specic variations, or specic requirements that are not addressed by the out-of-the-box mappings.

The steps for updating the mapping are as below:

1. Navigate to Collaboration Messaging work area and click on Manage Collaboration Message Denitions.2. Search for the message by selecting Direction as Inbound and Document as PROCESS_INVOICE_IN

From the search results, select the message ORCL_CMK_PROCESS_INVOICE_002 for OAG 7.2.1 orOAGIS_10.1_PROCESS_INVOICE_COLLAB_MSG_IN for OAG 10.1. Download the transformation package byselecting Actions > Export Transformation Package.

3. The Transformation package gets downloaded as a zip le with source and target XSDs and the XSLT.4. You can update the mapping in the downloaded XSLT and save it to local system.5. The seeded message denitions cannot be modied. You can duplicate the seeded message and congure

them using the modied XSLT. Select the message to be modied and select Actions > Duplicate CollaborationMessage.

6. You can edit the defaulted Message Name if required. Select the modied XSLT saved earlier. Save and Close7. The new message created must be associated with the B2B Trading Partner or the Service Provider.8. If the trading partner sends invoices through a service provider, such as Oracle Supplier Network, add the new

message denition to the service provider from the task Manage Collaboration Messaging Service Providers.

◦ Select the Inbound Collaboration Messages tab. Enter Name and select the new Message denition thatyou created. Make the new message Active.

◦ Mark the existing Message as Inactive and duplicate the Message.

◦ Enter Name and select the new Message denition that you created.

◦ Make the new message Active.

9. If the trading partner sends invoices directly to CMK web service, then add the new message denition to thetrading partner from Manage B2B Trading Partners

◦ Select the Inbound Collaboration Messages tab.

◦ Mark the existing Message (if any) as Inactive and Add new message.

◦ Enter Name and select the new Message denition that you created.

◦ Make the new message Active.

10. Save and Close.



14


Chapter 2General Payables Options

15

2 General Payables Options

Manage Common Options for Payables andProcurement

Guidelines for Common Options for Payables and ProcurementFor invoice business units, you can set options common to the procure-to-pay business ow on the Manage CommonOptions for Payables and Procurement page.

The common options are grouped into the following categories:

• Default distributions

• Automatic osets

• Currency conversion

• Expense accruals

• Self-billed invoices

• Legal entity information

Default DistributionsDefault distributions are used to dene accounts for payables transaction accounting.

Note: You can also specify some default distributions for a supplier on the Edit Site page.

Oset SegmentsIf you enter invoices for expenses or asset purchases with more than one primary balancing segment value, considerusing automatic osets. Automatic osets balance accounting entries for Oracle Fusion Payables transactions. If youdon't use automatic osets, an invoice transaction has a single liability accounting entry and a payment transaction hasa single cash accounting entry.

Currency ConversionThis table describes the options you can set for currency conversion.

Option Description

Require conversion rate entry If enabled, you must provide a conversion rate whenever you enter an invoice or a payment ina currency other than the ledger currency. If you maintain daily rates, the rate is automaticallysupplied based on the date and rate type that you enter. If daily rates don't exist for that dateand rate type, you can't enter or save the transaction. If the conversion rate type is User,then you must enter a conversion rate. You can't create accounting entries for, or pay foreigncurrency invoices without conversion rates.



16

Option Description

If you don't enable this option, you can enter conversion rates manually on invoices andpayments, or submit the Apply Missing Conversion Rates process. When you create a billspayable document, you must still provide a maturity rate, rate type, and date.

Conversion rate typeThis seing provides the default conversion rate type when you enter invoices or createpayments. You can change the conversion rate type at invoice entry or payment creation time.

Realized Gain or Loss DistributionsThese distributions represent the default realized gain and loss accounts for paymentsfrom each of your bank accounts. If the conversion rate changes between invoice entry andpayment time, the realized gain or loss is automatically calculated and recorded to theseaccounts.

Expense AccrualsDetermine when to accrue for expense items.

Self-Billed InvoicesThis table lists the options for self-billed invoices.

Option Description

Gapless invoice numberingYou can enable gapless, that's, no breaks in numbering, invoice number generation for yourbuying organization during pay on receipt processing. You can enable gapless numbering forthe entire business unit with this seing or limit it to a supplier site.

Buying Company IdentierA unique identier that's included in the invoice number created by the pay on receipt processand in the debit memo number from returned receipts.

Legal Entity InformationThis table describes the options for legal entity information.

Option Description

VAT Registration Member StateIf your company operates in a member state of the European Union, select the country.

VAT Registration NumberIf your company operates in a member state of the European Union, enter the value-added tax(VAT) registration number for your organization.

Bill-to LocationEnter the bill-to location to provide default values. The application uses the bill-to location toderive legal entity information.



17

Note: You can use the Create Chart of Accounts, Ledger, Legal Entities, and Business Units in Spreadsheettask to automate common options setup.

Related Topics

• Create Chart of Accounts, Ledger, Legal Entities, and Business Units in Spreadsheets

• How Charts of Accounts, Ledgers, Legal Entities, and Business Units Are Created Using Spreadsheets

Default DistributionsDefault distributions are used to dene accounts for payables transactions. Invoices may get some distributions fromsupplier sites and others from common options setup.

Default DistributionsThe following table describes the default distributions on the Manage Common Options for Payables and Procurementpage.

Distribution Description

Liability The default liability distribution for new invoices, unless the Site Assignments tab on the

Supplier page has a dierent distribution.

Caution: You can only specify a distribution with an account type ofLiability.

Prepayment

The default distribution for prepaid expenses, unless the Site Assignments tab on the Supplierpage has a dierent distribution.

Bill Payable

The default distribution for future-dated payments, unless the Site Assignments tab on theSupplier page has a dierent distribution.

Conversion Rate Variance Gain andLoss

Records conversion rate variance gains and losses for inventory and expense items that areaccrued on receipt. Variance is calculated between an invoice and purchase order or, an invoiceand receipt, depending on how you matched the invoice.

Discount Taken Records discounts taken if the Discount Allocation Method option on the Manage Invoices

page is set to Single distribution.

Miscellaneous Records charges for invoice lines with a type of Miscellaneous. If you don't enter a value,

miscellaneous charges are prorated across invoice item lines.

Freight

Records charges for freight lines. If you don't enter a value, miscellaneous charges are proratedacross invoice item lines.

http://www.oracle.com/pls/topic/lookup?ctx=fa20a&id=CEFF937A852C827DE040D30A68814B57

http://www.oracle.com/pls/topic/lookup?ctx=fa20a&id=CEFF937A852D827DE040D30A68814B57



18

Distribution Description

Prepayment Tax Dierence Records tax amount dierences between a prepayment and the invoices that the prepayment

is applied to. These dierences are usually due to changes in tax rates from the time theprepayment is created to the time the invoice is created.

Caution: This distribution is used only if the Applied Amount Handlingoption in the tax record is set to Recalculate.

Automatic OsetsIf you enter invoices for expenses or asset purchases with more than one primary balancing segment value, you mightwant to use automatic osets. Automatic osets balance accounting entries for Oracle Fusion Payables transactions. Ifyou don't use automatic osets, an invoice transaction has a single liability accounting entry and a payment transactionhas a single cash accounting entry.

On the Manage Common Options for Payables and Procurement page, you can select the method for creating theoseing accounting entry. You can oset by primary balancing segment, or you can oset by all segments, exceptnatural account.

Invoice Accounting EntriesAmounts are automatically allocated for the following invoice accounting entries:

• Conversion rate variance gain or loss

• Liability

• Nonrecoverable tax for invoices matched to purchase orders

• Nonrecoverable tax for invoices not matched to purchase orders, where no tax expense account has beendened for the tax rate

• Withholding tax, if the withheld amount is applied at invoice validation time

Payment Accounting EntriesAmounts are automatically allocated for the following payment accounting entries:

• Cash, if you use a pooled bank account

• Cash clearing, if you use a pooled bank account and if you account for payments at clearing time

• Discount

• Realized gain or loss

• Bills payable

• Withholding tax, if amounts are withheld at payment time



19

Considerations for Oset SegmentsYou can use the Oset Segments option on the Manage Common Options page to create balanced accounting entriesfor invoice and payment transactions. You can select the segments to override on the oseing entry lines withouthaving to dene intercompany or intracompany rules. This option is also used by Oracle Fusion Receiving to derive thereceiving inspection account.

Tip: Consider this option carefully before seing it. Changing automatic osets after creating accountingentries can result in accounting inconsistencies or slow performance.

To meet more complex oseing requirements, you can set up intracompany or intercompany rules at the ledger levelin Oracle Fusion General Ledger. If you enable additional balancing segments for your chart of accounts, you mustdene intracompany or intercompany rules for the journal entry to balance.

Select one of the following oset segment methods:

• None

• Primary balancing segment

• All segments, except natural account

NoneThe invoice liability distribution provides the liability entry line account, without any segment override. Receiving usesthe receiving inspection distribution that's dened for the destination organization.

Note: If you anticipate creating invoices that cross balancing segment values, select another method or set upintracompany or intercompany rules in General Ledger.

Primary Balancing SegmentThis method builds the liability entry line account using both the charge distribution on the invoice line and the liabilitydistribution on the invoice header. The charge distribution provides the primary balancing segment value and theliability distribution on the invoice header provides the remaining segment values. The resulting journal entry isbalanced by the primary balancing segment.

Receiving builds the receiving inspection entry line account using both the purchase order charge distribution andthe receiving inspection distribution for the destination organization. The charge distribution provides the primarybalancing segment value and the receiving inspection distribution provides the remaining segment values.



20

This gure illustrates how the invoice liability entry line account is built when the oset segment method is set toPrimary Balancing Segment.

Charge Distribution on Line

Liability Distribution on Invoice Header

Liability Account for Line

Primary Balancing Segment

Natural Account Segment Other Segments





All Segments, Except Natural AccountThis method builds the liability entry line account using both the liability distribution on the invoice header and thecharge distribution on the invoice line. The liability distribution on the invoice header provides the natural accountsegment and the charge distribution provides the remaining segment values. The resulting journal entry is balanced byall segments, except the natural account segment.

Receiving builds the receiving inspection entry line account using both the receiving inspection distribution for thedestination organization and the purchase order charge distribution. The receiving inspection distribution provides thenatural account segment and the purchase order charge distribution provides the remaining segment values.



21

This gure illustrates how the liability entry line account is built when the oset segment method is set to All Segments,Except Natural Account.

Charge Distribution on Line

Liability Distribution on Invoice Header

Liability Account for Line







Example of Creating Balanced Liability Account Entries by PrimaryBalancing SegmentOn the Manage Common Options for Payables and Procurement page, you can select a method for automatic osets.The following example illustrates how liability accounts are built using the Primary balancing segment method.

ScenarioA supplier sends you an invoice for two items. Each item should be charged to a dierent company.

Transaction DetailsThe invoice is for 100 USD and consists of:

• Item 1 for 60 USD




22

AnalysisThe accounting exeld consists of the following segments:

• Primary balancing segment

• Account

• Cost center

Each primary balancing segment value represents a company. The default liability account for the supplier site is 00-LIAB-000.

This table lists the distribution combination information that you enter for each invoice item line.

Invoice Distribution Debit Credit

01-EXP1-111

60

02-EXP2-222

40

Resulting Liability Account Journal EntriesThis table lists the liability accounts and amounts that are automatically created for the invoice.

Liability Account Debit Credit

01-LIAB-000

60

02-LIAB-000

40

Example of Creating Balanced Liability Account Entries by AllSegments Except Natural AccountOn the Manage Common Options for Payables and Procurement page, you can select a method for automatic osets.The following example illustrates how liability accounts are built using the method called All segments, except naturalaccount.

ScenarioA supplier sends you an invoice for two items. The oseing liability account must retain all segments of the invoicedistribution, except for the account segment.



23

Transaction DetailsThe invoice is for 100 USD and consists of:



AnalysisThe accounting exeld consists of the following segments:

• Primary balancing

• Account

• Cost center

Each primary balancing segment value represents a company. The default liability account for the supplier site is 00-LIAB-000.

This table lists the distribution information that you enter for each invoice item line.

Invoice Distribution Debit Credit

01-EXP1-111

60

02-EXP2-222

40

Resulting Liability Account Journal EntriesThis table lists the liability accounts and amounts that are automatically created for the invoice.

Account Debit Credit

01-LIAB-111

60

02-LIAB-222

40

Considerations for Accruing Expense ItemsSet the Accrue Expense Items option on the Manage Common Options for Payables and Procurement page to indicatewhen to accrue for expense items.

At ReceiptAccrue when receipts are created. You can override this seing on the PO schedule for expense destination types.



24

Note: Inventory items are always accrued at receipt.

Period EndAccrue at the end of a period. During period close, expense accruals are created for all receipts that don't have invoices.Accrual entries are reversed when the next period is opened.

FAQs for Manage Common Options for Payables andProcurement

What's the dierence between conversion rate gain or loss distributions and realizedgain or loss distributions?Conversion rate gain or loss distributions record the rate variances for inventory or expense items that accrue onreceipt. The invoice validation process calculates the variance between the invoice and either the purchase order orreceipt, depending on how the invoice was matched.Realized gain or loss distributions record the rate variances between invoice entry and payment time. The gain orloss calculation is based on the Account for Payment option on the Manage Payment Options page, as well as atprepayment application. You can account at payment issue, clearing, or at both issue and clearing. If you account atpayment issue, bills payable documents are accounted at maturity.

Realized gain or loss is always calculated at foreign currency prepayment application time, regardless of the Accountfor Payment seing.

Manage Invoice Options

Guidelines For Invoice OptionsInvoice options are seings and default values that control how invoices are processed for an invoice business unit. Youset invoice options on the Manage Invoice Options page.

Invoice Entry and Matching OptionsThe following table describes the invoice entry options. You can also set some of these options on a supplier. Theinvoice options are used unless the supplier has a dierent default value.

Option On Supplier Setup? Description

Require invoice grouping

No

Requires you to enter the name of a groupwhen creating an invoice.

Allow document category override

No Allows override of the invoice document

category if the Sequencing By ledgeroption is set to Ledger or Legal entity.



25


Caution: If the ledger optionis set to No Sequencing:

• A documentcategory isn't

assigned to theinvoice.

• You can't setthis option or

enter a document

category on theinvoice.

Allow adjustments to paid invoices

No

Lets you cancel or add lines to paidinvoices. In addition, you can undo amatch to a purchase order that's notnally matched and match the invoice to adierent purchase order.

Caution: You can't modifydistributions because accountingwould be aected.

Allow remit-to supplier override for third-party payments

No

Allows override of the remit-to suppliername and address on invoice installmentsfor suppliers with third-party relationships.

Recalculate invoice installments

No

Recalculates Installments during theinvoice validation process.

Hold unmatched invoices

Yes Applies a Matching Required hold to

invoices that aren't matched to purchaseorders or receipts.

Note: You can set thisoption on a supplier to: Yes,No, Default from PayablesOptions.

Prevent deletion of invoice aachments

No

Aachments won't be allowed to bedeleted once the invoice is approved ifapproval is enabled or when the invoice isvalidated.

Receipt acceptance days

No

Species the number of days to add to thegoods received date when recalculatinginstallments.



26


Invoice currency

Yes

Provides the default invoice currency.

Payment currency

Yes

Provides the default payment currency.

Pay group

Yes

Provides the default group used whenpaying invoices.

Payment priority

Yes

Provides the default priority for payinginvoices.

Payment terms

Yes

Provides the default payment terms.

Terms date basis

Yes

Provides the default basis for determiningthe terms date.

Pay date basis

Yes

Provides the default basis for determiningthe pay date.

Accounting date basis

No

Provides the default basis for determiningthe accounting date.

Budget date basis

No

Provides the default basis for determiningthe budget date.

The following table describes the options for matching invoices to purchase orders, receipts, and consumption advicedocuments. You can also set some of these options on a supplier. The invoice options are used unless the supplier has adierent default value.


Allow nal matching

No

Lets you perform a nal match whenmatching to a purchase order, or whenadjusting a matched invoice distribution.

Allow matching distribution override

No

Allows override of the invoice distributionthat's created from matching an invoice toa purchase order.



27


Caution: You can't override thedistribution for a matched invoiceif you accrue at receipt. You alsocan't override the distribution ifthe purchase order is projects-related, and the item destinationfor the purchase order distributionis inventory.

Transfer PO distribution additionalinformation

No

Transfers descriptive exeld informationfrom the purchase order distribution tothe invoice distribution when you match toa purchase order.

Note: If you enable this option,ensure that the exeld structuresfor the purchase order distributionsand the invoice distributions arethe same.

Quantity tolerances

Yes

Provides the default quantity-basedtolerance set.

Amount tolerances

Yes

Provides the default amount-basedtolerance set

DiscountsThe following table describes the discount options. You can set some of these options on a supplier to: Yes, No, Defaultfrom Payables Options.


Exclude tax from calculation

Yes Subtracts tax from the invoice when

calculating the discountable amount foran installment.

Caution: You can't set thediscount allocation methodoption to Tax lines andsingle distribution.

Exclude freight from calculation

Yes

Subtracts freight from the invoice whencalculating the discountable amount foran installment.



28


Discount allocation method

No

Determines how discounts are allocatedacross invoice distributions.

Always take discount

Yes

Takes the available discount for a supplier,regardless of when you pay the invoice.

PrepaymentsThe following table describes the prepayment options.


Payment terms

No

Provides the default payment terms for aprepayment.

Selement days

Yes

Species the number of days to add to thesystem date to calculate the selementdate.

Note: You can't apply aprepayment to an invoice until on,or after, the selement date.

Use distribution from purchase order

No

Builds the distribution combinationfor the matched invoice distributionusing information from the supplierand purchase order. The prepaymentdistribution on the supplier providesthe natural account segment and thepurchase order distribution combinationprovides the rest of the segment values.

Show available prepayments duringinvoice entry

No

Displays the available prepayments duringinvoice entry.

ApprovalsYou can use the invoice approval workow to automate the invoice approval process. The workow determines if aninvoice requires approval and if so, routes the invoice to the approvers, who can then approve or reject the invoice.

The following table describes the approval options.



29

Option Description

Enable invoice approval

Sends invoices through the approval workow. Invoices can't be paid until they're approved.

Require validation before approval

Sends invoices through the approval workow after the invoices are checked for completenessby the validation process.

Accounting Preference Choose your accounting preference for the invoices.

• Account regardless of approval status: Account the invoices regardless of the approvalstatus.

• Require accounting before approval: Only invoices that are accounted are sent throughthe approval process.

• Require approval before accounting: Only invoices that are approved are accounted.

Allow force approval

Allows managers to override the workow and manually approve invoices. For example, youmight want to force approve if the workow doesn't complete, or you have the authority to paywithout using the workow.

InterestThis table lists the options you can set for interest on overdue invoices.


Create interest invoices

Yes Calculates interest on overdue invoices

and creates interest invoices. You canset this option on a supplier to: Yes, No,Default from Payables Options.

Minimum interest amount

No

The minimum amount of calculatedinterest that sets the threshold forcreating an interest invoice. Interestinvoices that don't meet the minimuminterest amount aren't created.

Interest allocation method

No

Allocates interest across invoicedistributions.

Interest expense distribution

No

Identies the distribution combinationused if allocating interest expense to asingle distribution.



30

Payment RequestsThe following table describes the payment request options.

Option Description

Payment terms

Provides the default payment terms.

Pay group

Provides the default pay group used when paying a prepayment.

Payment priority

Provides the default payment priority used when paying a prepayment.

Self-Service InvoicesThe following table describes the options you can set for invoices created through Oracle Fusion Supplier Portal.

Option Description

Limit invoice to single purchase order

Limits an invoice to the schedules belonging to a single purchase order.

Allow invoice backdating

Allows a supplier to enter an invoice for a date in the past.

Allow unit price change for quantity-based matches

Allows a supplier to enter a unit price on an invoice that's dierent from the unit price on thepurchase order.

Require aachment

Supplier users can't submit an invoice without an aachment. This applies to both matchedand unmatched invoices.

Note: You can use the Create Chart of Accounts, Ledger, Legal Entities, and Business Units in Spreadsheettask to automate your invoice options setup.

Related Topics



How Invoice Installments Are RecalculatedDuring invoice entry, installments are automatically created using payment terms and terms date information. You cancongure your setup to recalculate installments during the invoice validation process.

Seings That Aect Installment RecalculationSelect the Recalculate invoice installments option on the Manage Invoice Options page to recalculate the installments.





31

Note: Installments are recalculated, regardless of how the recalculate option is set, when both of the followingconditions occur:

• You enable the Exclude tax from calculation option on the Manage Invoice Options page.• You manually change a tax amount.

How Invoice Installments Are RecalculatedInstallment recalculation uses the most recent applicable start date and the more favorable payment terms. Todetermine which is more favorable, the ranks on the payment terms are compared.

Caution: Installments aren't recalculated if you manually edit or split any of the installments.

The following table shows which start dates and payment terms are used for recalculating installments for matched andunmatched invoices.

Matched to a Purchase Order Start Date Payment Terms

No Most recent of the following:

• Invoice date• Terms date• Goods received date plus number

of receipt acceptance days

Invoice payment terms

Yes Most recent of the following:

• Invoice date• Terms date• Goods received date plus number

of receipt acceptance days

More favorable of the following:

• Invoice payment terms• Purchase order payment terms

Related Topics• Payment Terms

Considerations for Discount Allocation MethodsDiscounts are taken when invoices are paid. On the Manage Invoice Options page, you can specify how to allocate thesediscounts. Select any one of the following methods:

• All invoice lines

• Tax lines and single distribution

• Single distribution

All Invoice LinesThis method automatically prorates discounts across all invoice lines. Discounts are assigned to the charge accountunless the invoice is matched to a purchase order that's set to accrue on receipt. For those invoices, the discount isassigned to the price variance account.



32

Note: If you exclude tax from discount calculations, discounts are allocated only to expense lines and not totax lines.

Tax Lines and Single DistributionThis method prorates a percentage of the discount across tax lines based on the percentage of tax lines on the invoice.

For example, if tax distributions represent 10 percent of the total invoice amount, 10 percent of the discount is proratedacross the tax distributions. The remaining 90 percent of the discount is applied to the Discount Taken distributionspecied on the Manage Common Options for Payables and Procurement page.

Note: You can't select this method if you exclude tax from discount calculations.

Single DistributionThis method credits the Discount Taken distribution specied on the Manage Common Options for Payables andProcurement page. Select this method if you enable automatic osets and you want to distribute the discount takenacross balancing segments.

Interest InvoicesIf you enable automatic interest calculation for a supplier and pay an overdue invoice, an invoice for the interest isautomatically created and paid.

Caution: You must pay the overdue invoice in a payment process request or through a quick payment.

SetupTo set up automatic interest rate calculation:

• Dene interest rates using the Manage Interest Rates task.

• Set the Create Interest Invoices option using the Manage Suppliers task.

• Enable the Create interest invoices option using the Manage Invoice Options task.

Note: You can add, change, or delete an interest rate at any time. If a rate isn't dened, the interest calculationuses a zero rate.

AributesThis table describes some of the aributes of an interest invoice.

Aribute Description

Number

The interest invoice number is the overdue invoice number plus the sux -INTx, where x isthe number of interest invoices for that overdue invoice. For example, if the invoice number is54362, the invoice number for the third interest invoice is 54362-INT3.

Payment terms

The payment terms on an interest invoice are immediate. If immediate terms aren't dened,the payment terms for the interest invoice are the same as the payment terms for the overdueinvoice.



33

Aribute Description

Amount

The interest calculation is based on the rate on the Manage Interest Rates page and is inaccordance with the United States Prompt Payment Act. The calculation formula compoundsinterest monthly, up to a maximum of 365 days interest.

Currency

The invoice currency for an interest invoice is the same as the invoice currency on the overdueinvoice. The payment currency for an interest invoice is the same as the payment currency onthe overdue invoice.

Related Topics

• How Interest on Overdue Invoices is Calculated

Interest Allocation MethodsThe Interest Allocation method on the Manage Invoice Options page determines how invoice distributions for interestinvoices are created.

Select one of the following seings:

• Single distribution

• All invoice lines

Single DistributionThis seing uses the Interest Expense distribution on the Manage Invoice Options page as the invoice distribution forthe interest invoice.

All Invoice LinesThis seing uses the natural account segment from the Interest Expense distribution to build the distributions for theinterest invoice.

Payment RequestsOracle Fusion Payables can receive requests from internal or external sources to disburse funds to payees that aren'tdened as suppliers. Payables records these requests as payment requests.

Internal payment requests can come from Oracle Fusion Receivables and Oracle Fusion Expenses. You can create apayment request from Receivables for a customer refund or from Expenses for an expense report. You can disburse thefunds and manage the payment process using the payment management functionality in Payables.

Payment requests from external sources can be imported using the File Based Data Import (FBDI) spreadsheetfor making One Time Payments. You can import, update, approve, pay transactions, and get the status update forpayments. The payees, parties, and bank accounts are created automatically when the transactions are imported intothe application.

http://www.oracle.com/pls/topic/lookup?ctx=fa20a&id=90BA9D73E72E5146E040D30A68814290



34

Seing Up Payment RequestsThe following setups aect the payment request process.

• Invoice options: Set the default options for payment requests, such as payment terms, pay group, and paymentpriority.

• Document sequence category: Comply with document sequencing policies using the predened PaymentRequest category or override the document category, if allowed.

• Common Options for Payables and Procurement: Enter the default Liability and Expense accounts for OneTime Payments.

You can use the following setups in Oracle Fusion Payments to manage payment requests separately from otherpayments:

• Payment method controls

• Payment method default rules

• Payment le and report formats

• Payment aribute validations

Reporting on Payment RequestsYou can track progress of a payment request in the originating application. After a payment request has been approved,you can report on and audit the request in Payables using the following reports:

• Payables Invoice Aging

• Payables Invoice Audit by Voucher Number Listing

• Payables Open Items Revaluation

• Payables Cash Requirement

Related Topics

• How You Issue Manual Refunds

• How Expense Report Payment Requests Are Processed

• Document Sequencing in Payables

Manage Payment Options

Guidelines for Payment Accounting OptionsOn the Manage Payment Options page, set the Payment Accounting option to determine when payment accountingentries are created.

Tip: Carefully consider this seing at implementation time. After you set this option, the only change you canmake is from accounting At Payment Issue to accounting At Payment Issue and Clearing.

Select from the following options:

• At payment issue

http://www.oracle.com/pls/topic/lookup?ctx=fa20a&id=963C6A4F99EEB6DBE040D30A68817CA6

http://www.oracle.com/pls/topic/lookup?ctx=fa20a&id=97655C3636937FB2E040D30A688132A3

http://www.oracle.com/pls/topic/lookup?ctx=fa20a&id=9E3C38FFA71BC953E040D30A68817D6B



35

• At payment clearing

• At payment issue and clearing

At Payment IssueWith this seing, the liability account is debited and the cash account is credited when a payment is created. For abills payable payment, the credit is to the bills payable account. Then at payment maturity, the bills payable account isdebited and the cash account is credited. Realized gain or loss is calculated at payment creation and for a bills payablepayment, at payment maturity.

At Payment ClearingWith this seing, the liability account is debited and the cash account is credited when the payment clears. Realized gainor loss is calculated at payment clearing.

At Payment Issue and ClearingWith this seing, accounting entries are created at:

• Issue time: The liability account is debited and the cash clearing account is credited. For a bills payablepayment, the credit is to the bills payable account. Then at payment maturity, the bills payable account isdebited and the cash clearing account is credited.

• Clearing time: The cash clearing account is debited and the cash account is credited.

Note: Realized gain or loss is calculated at all points mentioned.

Note: You can use the Create Chart of Accounts, Ledger, Legal Entities, and Business Units in Spreadsheettask to automate your payment options setup.

Related Topics



FAQS for Manage Payment Options

What's the dierence between the currency conversion seings on the commonoptions page and the payment options page?The currency conversion seings on the Manage Common Options for Payables and Procurement page aect invoicetransactions.The seings on the Manage Payment Options page aect payment transactions.

For business units that process both invoice and payment transactions, the Conversion Rate Type option is thesame for both types of transactions. You can set this option on either the Manage Common Options for Payables andProcurement page or the Manage Payment Options page.

Manage Tax Reporting and Withholding Tax Options





36

Withholding Tax OptionsWithholding tax options are seings and default values that control how Oracle Fusion Tax processes withholding for abusiness unit. You can enable your withholding tax options for a specic eective period.

Withholding Tax OptionsSet the following withholding tax options on the Manage Tax Reporting and Withholding Tax Options page:

Option Description

Event ClassApply withholding tax to standard invoices, including credit and debit memos, or prepaymentinvoices.

Apply WithholdingApply withholding if the tax authority requires your company to withhold taxes from suppliers.

Process Transaction TaxesCalculate withholding tax on transaction tax lines.

Allow Manual WithholdingCreate and adjust manual withholding tax lines for your invoices.

Regime Determination SetSelect the template that determines the tax regime to use for all transactions belonging to thisevent class. The options include WHTSTCC and WHTTAXREGIME.

Calculation Point Specify the time when withholding tax is applied.

The options are Invoice, Payment, or Both. The options available are controlled by the regimedetermination set.

Tax Invoice Creation Point Specify the time when a tax authority invoice is generated.

The options are dependent on the value in the Calculation Point eld:

• If the calculation point is Invoice, you can select Blank, Invoice, or Payment as the taxinvoice creation point.

• If the calculation point is Payment, you can select Blank or Payment as the tax invoicecreation point.

Include Discount Determine if a deduction of a discount is applied to the taxable basis when the calculationpoint is Payment.

Select:

• No to always exclude the discount amount from the taxable basis.• Yes to always include the discount amount in the taxable basis.• Blank for the deduction of a discount to be applied based on the taxable basis formula

denition.



37

Option Description

Rounding LevelApply rounding to calculated tax amounts once for each withholding tax rate per invoice or tothe calculated withholding tax amount on each invoice line.

Calculation Point OptionsOn the Manage Tax Reporting and Withholding Tax Options page, dene the calculation point to specify the time toapply withholding taxes to supplier invoices.

Calculation point is determined at:

• Invoice

• Payment

InvoiceSelect Invoice for taxes to be automatically withheld at invoice validation. If you select this option, Oracle Fusion Taxcalculates withholding only once. If you adjust an invoice after it was validated, you must adjust the withholding taxmanually and enable the Allow manual withholding option.

Taxes can be withheld from standard invoices, including credit and debit memos, and prepayment invoices. If you selectthe calculation point of Invoice for the event class, Prepayment invoices, consider timing the entry of the prepaymentapplication before the invoice is validated.

If you:

• Apply the prepayment before the invoice is validated, Oracle Fusion Tax creates a withholding tax net of theprepayment amount.

• Validate the invoice rst, Oracle Fusion Tax creates a withholding tax based on the taxable invoice amount.When you apply the prepayment, the withholding tax on the invoice isn't updated. You can manually adjust thewithholding tax amount and the withholding invoice.

As an alternative, you can cancel all of the withholding taxes on the validated invoice before you apply theprepayment. Once you apply the prepayment, withholding taxes are created net of the prepayment amount.

PaymentSelect Payment for taxes to be automatically withheld when you create payments in a payment process request or witha Quick payment.

Tax Invoice Creation Point OptionsOn the Manage Tax Reporting and Withholding Tax Options page, dene the tax invoice creation point to specify whento automatically create withholding tax invoices to remit withheld taxes to tax authorities.

Tax invoice creation point is determined at:

• Blank



38

• Invoice

• Payment

The options available are dependent on the value in the Calculation Point eld.

BlankSelect Blank so Oracle Fusion Tax doesn't automatically create withholding tax invoices. You can enable this option forany value you selected as the calculation point.

You must run the withholding tax reports to determine the amounts to remit to your tax authorities, and create thewithholding tax invoices.

InvoiceSelect Invoice for a withholding invoice to be automatically created when an invoice subject to withholding tax isvalidated. You can enable this option only if the calculation point is applied at invoice validation time.

PaymentSelect Payment for a withholding invoice to be automatically created when an invoice subject to withholding tax is paid.You can enable this option if the calculation point is applied either at invoice validation or at payment.

Include Discount OptionsUse the Include Discount option on the Manage Tax Reporting and Withholding Options page to specify whether toinclude discount amounts in the calculation of withholding tax when the calculation point is Payment.

Select from the following options:

• No

• Yes

• Blank

NoSelect No to exclude the deduction of the discount to the taxable basis for taxes.

For example, assume you have an invoice for 100 USD. The discount amount taken is 5 USD and the automaticwithholding tax rate is 10 percent. If the discount amount is excluded, the automatic withholding tax amount is 10percent of 95 USD or 9.5 USD.

YesSelect Yes to include the discount to the taxable basis for taxes.

For example, assume you have that same invoice for 100 USD. The discount amount taken is 5 USD and the automaticwithholding tax rate is 10 percent. If the discount amount is included, the automatic withholding tax amount is 10percent of 100 USD or 10 USD.

Note: This seing applies only to payment time withholding. You cannot enable this seing if the CalculationPoint option is set to Invoice. At the time of invoice validation the discount amount to be taken is unknown,so withholding tax is calculated on the entire invoice amount.



39

BlankSelect Blank for the application to apply the deduction of the discount based on the taxable basis formula denition.

Income Tax Reporting OptionsUse the Manage Tax Reporting and Withholding Tax Options task to manage the following income tax reportingoptions for an invoice business unit:

• Use combined ling program

• Use supplier tax region

• Income tax region

• Include withholding distributions in income tax reports

Use Combined Filing ProgramEnable this option if you're using US 1099 Combined Federal and State Filing Program reporting. When you submitthe US 1099 Electronic Media Report, K records are produced for all tax regions participating in the program that havequalifying payments.

Tip: If you le tax information with the Internal Revenue Service electronically and don't use the combinedling program, don't enable this option.

Use Supplier Tax RegionThis option is used with combined ling. You can enable this option to use the tax region from US 1099 suppliers as thedefault tax region on invoice distributions. If needed, you can override the tax region on the Manage Distributions page.If you enable this option, you could have as many K records as you have dierent supplier tax regions.

Income Tax RegionThis option is used with combined ling. You can forward US 1099 payment information to one tax region, regardless ofthe tax regions your US 1099 suppliers do business from. If you enter a value in the Income Tax Region eld, you mighthave only one K record. If needed, you can still override the tax region on an invoice distribution.

Include Withholding Distributions in Income Tax ReportsEnable this option to report on federal income tax withheld for US 1099 suppliers. The withholding tax distributions thatare automatically created have an:

• Income tax type of MISC4 for reporting in box 4 on the 1099-MISC form

• Income tax region, if combined ling is enabled

Note: If you manually create withholding tax lines, then you must enter the income tax type and income taxregion manually.

When you enable this option, the Update 1099 Withholding Tax Distributions process runs. This process updates theincome tax type and income tax region on existing withholding tax distributions. The process selects distributions toupdate as follows.

If the current date is:

• Before March 1 of the current calendar year, distributions with a payment date of January 1 of the previouscalendar year or later are updated.



40

• March 1 of the current calendar year or later, distributions with a payment date of January 1 of the current yearor later are updated.

US 1099 Reporting: ExplainedIn the United States (US), you must report to the Internal Revenue Service certain types of payments that you make toUS 1099 reportable suppliers. You can designate suppliers as federally reportable in the supplier setup. When you enterinvoices for the supplier, you classify invoice distributions by US 1099 miscellaneous type using the Income Tax Typeeld. At year end, you can report accumulated US 1099 payment information to the Internal Revenue Service, other taxagencies, and your suppliers, in standard format.

If you're using combined ling, the US 1099 electronic format produces K records and B records. The K records provideinformation for tax regions or states participating in combined ling that have qualifying payments. The B records arefor suppliers with US 1099 payment amounts that equal or exceed the tax region reporting limit in qualifying states.

US 1099 Reporting Overview

The following gure shows the steps for US 1099 reporting from setup to reports.

Set up Payables for US 1099 reporting

Enter US 1099 details for suppliers

Enter, account, and pay US 1099

invoices

Optionally withhold tax from suppliers

Update US 1099 payment information

Generate US 1099 reports

Identify and resolve US 1099 exceptions

1. Set up Payables for US 1099 reporting: Refer to the following section for details.2. Enter US 1099 details for suppliers: On the Income Tax tab on the Supplier page, you can specify federal and

state information.



41

3. Enter, account, and pay US 1099 invoices: You can specify the income tax type and income tax region on eachapplicable invoice distribution, or accept the default values from the supplier.

To automatically create invoice distributions, you can enter a distribution set or match to a purchase order.If you're using a distribution set that doesn't have income tax types, the invoice distribution gets the incometax type from the supplier. If the distribution set has an income tax type that's dierent from the supplier, thedistribution set tax type is used. You can also enter distributions manually.

You can adjust the Income Tax Type and Income Tax Region on each invoice distribution. You can also clearthe Income Tax Type eld for distributions that aren't federally reportable. If you enabled the Use supplier taxregion tax option, the default region is the state in the supplier site address for the invoice. Alternatively, youcan also specify a default income tax region on the Manage Tax Options page. The income tax region is usedto group distributions by type and region on US 1099 reports. If you enable combined ling, when you run US1099 reports, all reportable distributions are grouped by state.

4. Identify and resolve US 1099 exceptions: Submit the US 1099 Invoice Exceptions and Supplier Exceptionsreports. Generate Tax Information Verication Leers for each supplier that hasn't furnished or conrmed thetax identication number or tax reporting region.

5. Optionally withhold tax from suppliers: You can withhold tax if Tax Identication Numbers (TIN) are invalid ormissing and if you haven't met legal requirements of requesting a valid TIN.

6. Update US 1099 payment information: You can adjust invoice distributions manually on the ManageDistributions page, or you can submit the Update and Report Income Tax Details process.

7. Generate US 1099 reports:

◦ US 1099 Forms: Reports the total US 1099 miscellaneous payments for US 1099 suppliers, and generatesUS 1099 forms for each tax reporting entity in an organization.

◦ US 1096 Form: Summarizes each US 1099 form type that's transmied on paper, as required by theUnited States Internal Revenue Service. The report is generated on a preformaed Internal RevenueService form.

◦ US 1099 Electronic Media: Generates summarized US 1099 information in electronic format as requiredby the United States Internal Revenue Service.

◦ US 1099 Payments Report: Lists payments made to US 1099 reportable suppliers.

Payables Setup for US 1099 Reporting



42

This gure shows the steps for seing up Payables US 1099 reporting.

Enable combined filing

Enable withholding tax distributions

Using combined filing?

Define income tax regions

Define reporting entities

No

Yes

1. Enable combined ling: To use combined federal and state US 1099 ling, select the Use combined lingprogram option on the Manage Tax Options page.

Note: If you le US 1099 tax information electronically and don't participate in the Combined FilingProgram, leave the combined ling option disabled.

2. Enable withholding tax distributions: To automatically create withholding tax distributions, select the Includewithholding distributions in income tax reports option on the Manage Tax Options page. The income taxtype for these distributions is automatically set to MISC4. If you use combined ling, the income tax region isalso provided.

3. Dene income tax regions: If you use combined ling, dene the tax regions on the Manage Tax Regions page.4. Dene reporting entities: Set up reporting entities on the Manage Reporting Entities page. For each reporting

entity, you assign one or more balancing segment values. When you submit US 1099 reports for a tax entity, thepaid invoice distributions with the balancing segment values in their accounts are added together.


Chapter 3Payables Conguration

43

3 Payables Conguration

Distribution SetsDistribution sets automatically create distributions for invoices that aren't matched to purchase orders. For example,you can create a distribution set for an advertising supplier that allocates the advertising expense on an invoice to fourdepartments.

You can specify a default distribution set on the Site Assignments tab on the Supplier Site page. If you don't assign adistribution set to a supplier site, you can still assign a set to an invoice during invoice entry.

A distribution set can include:

• Income tax types: If you're creating a distribution set for a federally reported supplier, you can enter an incometax type.

• Project information: If you use Oracle Fusion Project Costing, invoice distributions can include projectinformation. If you use a project-related distribution set, the project information is automatically entered on theinvoice distribution. You can override project elds on the distribution.

• Descriptive exelds: If you use a descriptive exeld with your distribution set lines, the descriptive exeldinformation is copied to the invoice distributions created by the set.

You can dene distribution sets for invoice business units with and without percentages.

Distribution Sets with PercentagesUse a 100 percent distribution set when you know the allocation percentages. For example, you can create a distributionset to allocate rent expense across two departments. You can allocate 70 percent of the invoice amount to the salesfacility expense account and 30 percent to the administration facility expense account.

Note: Percentage distribution sets can include both positive and negative percentages.

Distribution Sets Without PercentagesUse a 0 percent distribution set when you don't know the allocation percentages. For example, you might allocatefacility expenses based on monthly headcount. You can dene a zero percent distribution set that includes the expensedistributions for each department. You can then provide the distribution amounts during invoice entry.

Payment TermsPayment terms are used to automatically create invoice installments. You can dene payment terms to create multipleinstallments and multiple levels of discounts.

Payment terms consist of one or more lines, each of which creates one invoice installment. When you dene a paymentterm, you can specify either percentages or xed amounts. A payment term line can have up to three discounts. Eachline and corresponding installment have a due date and up to three discount dates. Each line and corresponding



44

installment also have due or discount amounts. You can assign a payment term to one or more sets to share thatpayment term across business units.

This gure shows the components of a payment term.

Payment Term Line

Payment Term Set

Discount 1 Discount 2 Discount 3

Tip: If you change the payment terms on an invoice, the installments are automatically recalculated and youmust reenter any manual adjustments made previously.

Payment Terms Due Dates and Discount DatesPayment terms due dates and discount dates are based on one of the following methods:

• Fixed Date: A specic day, month, and year that an installment is due for payment.

• Days: A number of days added to the invoice terms date.

• Calendar: A Payables calendar that's divided into periods. You can assign a due date to the period that includesthe invoice terms date. You can assign due dates to avoid weekends, holidays, and so on. You can't assigncalendar-based terms to an invoice if a period isn't dened for the terms date.

• Day of Month: A type of payment term with the following aributes:

◦ Day of Month: A specic day of the month when an installment is due for payment. For example, enter15 to schedule payment on the fteenth day of the month. Enter 31 to schedule payment for the last dayof the month, including months with less than 31 days.

◦ Cuto Day: The day of the month after which the installment due and discount dates advance to a futuremonth. If you don't specify a cuto day, the current accounting month is used to determine due anddiscount dates.



45

◦ Months Ahead: The number that's used to determine the month the installment is due. If you enter0 and the terms date is the same as, or later than, the cuto day, the installment is due the followingmonth.

For example, a payment term has a Cuto Day of 11, the Day of Month is 15, and Months Ahead is 0. Ifyou enter an invoice with a terms date of January 12, the installment is due February 15. If you enter aninvoice with a terms date of January 10, the installment is due January 15. If the terms date is January 12and Months Ahead is set to 1, the installment is due March 15.

Note: Only due dates, not discount dates, can be based on a calendar.

Default Payment TermsIf you enter an Identifying PO on an invoice, the purchase order provides the default payment terms for the invoice.If you don't enter an Identifying PO, the supplier site provides the default payment terms. If the supplier site doesn'thave payment terms, the payment terms from the Manage Invoice Options page are used. You can override the defaultpayment terms on any invoice.

This gure shows how payment terms ow to the invoice.

Supplier Site Payment Terms

Invoice

Invoice Entry Options Payment TermsIdentifying PO?

Payment Terms on Supplier Site?No

Yes

Purchase Order Payment Terms

Yes

No

Payment Terms Defaulting

Related Topics• How Invoice Installments Are Recalculated• Reference Data Sets and Sharing Methods

http://www.oracle.com/pls/topic/lookup?ctx=fa20a&id=8C8EAACABBBE2602E040D30A688175E7



46

Payment Terms and Reference Data SharingPayment terms are enabled for reference data sharing using the method of assignment to multiple sets, no commonvalues allowed. The predened reference group is called Payables Payment Terms and the determinant type for thereference group is business unit. Before you can use a payment term, you must assign the payment term to a referencedata set.



47

This gure provides an example of how the payment terms Net 45 and Net 30 are shared across dierent businessunits.

Payment TermsNet 30

Payment Terms Net 45

Reference Data Set North America

Reference Data Set Europe

Business UnitFrance

Business Unit Canada

Business Unit United States

Invoice 1 Net 30

Invoice 5 Net 30

Invoice 4 Net 45

Invoice 3 Net 30

Invoice 2 Net 45

The Net 45 payment term is assigned to the North America reference data set. The North America reference data setis assigned to the United States and Canada business units. Invoices for these business units can then use the Net 45payment term. The Net 30 payment term is assigned to the North America and Europe reference data sets. The Europereference data set is assigned to the France business unit. Invoices for the United States, Canada, and France businessunits can use the Net 30 payment term.



48

Seing up Payment Terms for Reference Data SharingThe setup for payment term reference data sharing includes:

• Assigning a reference data set to a business unit: When you dene a business unit, assign the business unit areference data set for the Payables Payment Terms reference group.

• Generating a data role for a reference data set: To assign a reference data set to a payment term, you must rstgenerate a data role for that reference data set. Generate the data role using the predened data role templatecalled Financials Common Module Template for SetID.

• Provisioning a data role to the implementor: Assign the reference data set data role to the implementor whocreates the payment terms.

• Creating a payment term: Assign one or more reference data sets to a payment term in the Set Assignmentsection on the Create Payment Terms page.

Tip: Before you dene common options for Payables and Procurement, you must assign the Immediatepayment term to the reference data set for the business unit.

Note: You can assign a payment term to the predened common set, which works like any other set. Unlessyou assign the payment term to other reference data sets, that payment term is available only to the businessunits with the common set.

Related Topics

• Reference Data Sets and Sharing Methods

• Reference Data Sharing

Example of Creating Payment Terms Based on DaysThis example demonstrates how to create payment terms that are based on a certain number of days from the invoiceterms date.

This table summarizes key decisions for the scenario.

Decisions to Consider In This Example

Are terms based on amounts or percentages?

Percentages

What are the due dates and discounts? The due dates and discounts are as follows:

• First installment: 40 percent due in 10 days, with a discountof 5 percent if paid in 7 days

• Second installment: 35 percent due in 20 days, with adiscount of 3 percent if paid in 15 days

• Third installment: 25 percent due in 30 days, with adiscount of 2 percent if paid in 25 days

http://www.oracle.com/pls/topic/lookup?ctx=fa20a&id=8C8EAACABBBE2602E040D30A688175E7

http://www.oracle.com/pls/topic/lookup?ctx=fa20a&id=966D5B632168B267E040D30A6881788E



49

Creating Payment Terms Based on Days1. Navigate to the Manage Payment Terms page.2. Click Create to open the Create Payment Terms page.3. In the Name eld, enter the payment term name.4. Click Add Row in the Installments section to create the rst installment.5. Complete the elds, as shown in this table.

Field Value

Due Percent40

Days10

First Discount Percent5

First Discount Days7

6. Click Add Row in the Installments section to create the second installment.7. Complete the elds, as shown in this table.

Field Value

Due Percent35

Days20



8. Click Add Row in the Installments section to create the third installment.9. Complete the elds, as shown in this table.

Field Value

Due Percent25

Days30



50

Field Value



10. Click Save.

Invoice TolerancesInvoice tolerances determine whether matching holds are placed on invoices for variances between invoices and thedocuments you match them to, such as purchase orders. When you run the invoice validation process for a matchedinvoice, the process checks that matching occurs within the dened tolerances. For example, if the billed amount of anitem exceeds a tolerance, a hold is placed on the invoice. You can't pay the invoice until the hold is released.

You can dene tolerances based on quantity or amount. For each type of tolerance, you can specify percentages oramounts. Once you dene the tolerances, assign them to a supplier site.

Note: If you specify a percentage tolerance of zero, variance isn't allowed. If you want a low tolerance, specifya small percentage. If an active tolerance doesn't have a value, then innite variance is allowed.

Quantity-Based TolerancesQuantity-based tolerances apply to invoices with a match basis of Quantity.

This table describes each quantity-based tolerance.

Tolerance Description

Ordered Percentage

The percentage dierence more than the ordered quantity on a purchase order schedule linethat you allow suppliers to invoice. Validation checks the billed quantity against the orderedquantity without considering price.

Maximum Ordered

The quantity dierence more than the ordered quantity on a purchase order schedule linethat you allow suppliers to invoice. Validation checks the billed quantity against the orderedquantity without considering price. You can use this tolerance if most of your purchase ordershave the same relative value.

Received Percentage

The percentage dierence more than the received quantity on a purchase order schedule linethat you allow suppliers to invoice. Validation checks the billed quantity against the receivedquantity without considering price.

Maximum Received

The quantity dierence more than the received quantity on a purchase order schedule linethat you allow suppliers to invoice. Validation checks the billed quantity against the receivedquantity without considering price. You can use this tolerance if most of your purchase ordershave the same relative value.



51


Price Percentage

The percentage dierence more than the unit price on a purchase order schedule line that youallow suppliers to invoice.

Conversion Rate Amount

The variance that you allow between an invoice amount and the amount of a purchase orderschedule. Validation compares the ledger currency amounts, using the invoice and purchaseorder conversion rates, respectively. You can use this tolerance if you create foreign currencyinvoices.

Schedule Amount

The variance that you allow between all invoice amounts in the entered currency and thepurchase order schedule amount.

Total Amount The total variance that you allow for both the Conversion Rate Amount and Schedule

Amount tolerances combined. You can use this tolerance if you create foreign currencyinvoices.

Consumed Percentage

The percentage dierence more than the consumed quantity on a consumption advice thatyou allow suppliers to invoice. Validation checks the billed quantity against the consumedquantity without considering price.

Maximum Consumed

The quantity dierence more than the consumed quantity on a consumption advice that youallow suppliers to invoice. Validation checks the billed quantity against the consumed quantitywithout considering price.

Amount-Based TolerancesAmount-based tolerances apply to invoices that have a match basis of Amount.

This table describes each amount-based tolerance.


Ordered Percentage

The percentage dierence more than the ordered amount on a purchase order schedule linethat you allow suppliers to invoice. Validation checks the billed amount against the orderedamount.

Maximum Ordered

The amount dierence more than the ordered amount on a purchase order schedule linethat you allow suppliers to invoice. Validation checks the billed amount against the orderedamount.

Received Percentage

The percentage dierence more than the received amount on a purchase order schedule linethat you allow suppliers to invoice. Validation checks the billed amount against the receivedamount.

Maximum Received

The amount dierence more than the received amount on a purchase order schedule linethat you allow suppliers to invoice. Validation checks the billed amount against the receivedamount.



52



The variance that you allow between the invoice amount and the amount on a purchase orderschedule. Validation compares the ledger currency amounts, using the invoice and purchaseorder conversion rates, respectively. You can use this tolerance if you create foreign currencyinvoices.

Total Amount The total variance that you allow for both the Conversion Rate Amount and Schedule

Amount tolerances combined. You can use this tolerance if you create foreign currencyinvoices.

Invoice Holds and ReleasesUse the Manage Invoice Holds and Releases page to dene holds and releases for invoices. You can assign the holdsthat you dene to invoices, and the invoices can't be paid until you release the holds.

Note: The invoice validation process uses the predened holds and releases, which you can query on theManage Invoice Holds and Releases page.

For each hold that you dene, you can indicate whether accounting entries can be created. For example, if you assigna hold that doesn't allow accounting to an invoice, you must remove the hold before accounting entries can be created.You can also indicate whether to use the holds and releases in the holds resolution workow process. The holdsresolution workow routes invoices with manually-releasable holds.

When you dene a hold or release, you must associate it with a hold or release type.

Hold TypesThis table lists the predened invoice hold types and indicates whether you can dene holds for them.

Hold Type Allows User-Dened Holds?

Account Hold Reason

No

Future Period Hold Type

No

Insucient Information

No

Invoice Hold Reason

Yes

Invoice Line Reason

Yes

Matching Hold Reason No



53

Hold Type Allows User-Dened Holds?

Variance Hold Reason

No

Release TypesThis table lists the predened invoice release types and indicates whether you can dene releases for them.

Release Type Allows User-Dened Releases?

Account Release Reason

No

Future Period Release

No

Hold Quick Release Reason

Yes

Invoice Quick Release Reason

Yes

Invoice Release Reason

Yes

Matching Release Reason

Yes

Sucient Information

No

Variance Release Reason

Yes

Considerations for Payables Calendar PeriodFrequenciesWhen you create a calendar using the Manage Payables Calendars task, you must select a period frequency. Periodfrequencies determine the number of periods per year and the period name format for the calendar.

Period FrequencyThe following table describes each period frequency.



54

Frequency Periods Per Year Description

4-4-5

12

All periods have four weeks except thethird, sixth, ninth, and twelfth periods,which have ve weeks.

4-5-4

12

All periods have four weeks except thesecond, fth, eighth, and eleventh periods,which have ve weeks.

5-4-4

12

All periods have four weeks except therst, fourth, seventh and tenth periods,which have ve weeks.

Monthly

12

Each month is a period.

Quarterly

4

Each period has three months.

Weekly

52

Each period has seven days.

Other

Specied by user

Periods are manually dened.

How Periods for Payables Calendars Are GeneratedYou can dene a Payables calendar to generate periods automatically.

Seings That Aect Period GenerationWhen you create a calendar or add years to an existing calendar, the following aributes control how the periods aregenerated:

• Period frequency

• Periods per year

• Start date

• Period name format

How Periods Are GeneratedThis table describes the aributes that are used to generate periods.



55

Calendar Aribute Description

Period frequency Type of period, such as Monthly or 5-4-4.

Note: If you select Other, you must enter periods manually

Periods per year

Calculated number of periods per year.

Start date

First day of the calendar and start date of the rst period.

Period name format

Naming convention for periods.

Note: For weekly or quarterly period frequencies, the generated period name is the frequency combined withthe number of periods per year, plus the year. For example, for a period frequency of Quarterly and a startdate of 1/1/2015, the period name for the rst quarter is Quarter1-15.

Example Calendar with a Period Frequency of 4-4-5This example shows the generated periods for a calendar with a:

• Period frequency of 4-4-5• Start date of 1/1/2015

• Period name format of MMM

Period NamePrex

Year Sequence Start Date End Date Period Name

Jan

2015

1

1/1/15

1/28/15

Jan-15

Feb

2015

2

1/29/15

2/25/15

Feb-15

Mar

2015

3

2/26/15

4/1/15

Mar-15

Apr

2015

4

4/2/15

4/29/15

Apr-15

May

2015

5

4/30/15

5/27/15

May-15

Jun

2015

6

5/28/15

7/1/15

Jun-15

Jul

2015

7

7/2/15

7/29/15

Jul-15

Aug 2015 8 7/30/15 8/26/15 Aug-15



56

Period NamePrex

Year Sequence Start Date End Date Period Name

Sep

2015

9

8/27/15

9/30/15

Sep-15

Oct

2015

10

10/1/15

10/28/15

Oct-15

Nov

2015

11

10/29/15

11/25/15

Nov-15

Dec

2015

12

11/26/15

12/30/15

Dec-15

How You Set Up Third-Party PaymentsA third-party payment is a payment that you make to a supplier on behalf of another supplier. Seing up third-partypayments includes the following tasks:

Creating the Third Party1. In the Suppliers work area, click Create Supplier.2. Complete the information on the Prole and Address tabs.

◦ Set the Address Purpose eld to Remit to.

◦ (Optional) Associate a bank account and default payment method with the address.

Note: You don't have to create a supplier site unless the third party is a supplier that sends you invoices.

Dening the Relationship Between the Third Party and the Supplier1. In the Suppliers work area, click Manage Suppliers.2. Search for the supplier on whose behalf the third party receives payment.3. Add the third party to the Third-Party Payment Relationship section on the Invoicing tab on the Edit Site page.

Consider marking the relationship as the default relationship for new invoices and payments.

This table describes each aribute of a third-party payment relationship.

Aribute Description

Remit-to Supplier

Enter the party designated to receive payment on behalf of the supplier on the invoice.

Address Name

Enter the address of the party designated to receive payment on behalf of the supplier onthe invoice.



57

Aribute Description

From Date, To Date

Specify an inclusive date range for the relationship. When you create an invoice or payment,the invoice and payment dates are used to identify valid third-party payment relationshipsfor the supplier site.

Note: When you end date an existing relationship, you must review all unpaid orpartially paid invoices for that relationship.

Description

Enter text to include in the payment le. For example, you can enter text to print on thepayment document as reference information.

Note: The Merge Supplier process doesn't merge third-party payment relationships.

(Optional) Seing the Remit-to Supplier Override Option1. In the Setup and Maintenance work area, go to the following:2. Oering: Financials3. Functional Area: Payables4. Task: Manage Invoice Options, with the business unit scope set5. Click Apply and Go to Task.6. Select the Allow remit-to supplier override for third-party payments option to allow override of the remit-to

supplier on the invoice.

(Optional) Seing the Payee Override Option1. In the Setup and Maintenance work area, go to the following:2. Oering: Financials3. Functional Area: Payables4. Task: Manage Payment Options, with the business unit scope set5. Click Apply and Go to Task.6. Select the Allow payee override for third-party payments option to allow override of the payee on the

payment.

Related Topics• Guidelines For Invoice Options• What's a third-party payment

Auditing Payables Business ObjectsYou can audit specic business objects and aributes in Oracle Fusion Payables to monitor user activity and datachanges. Auditing includes recording and retrieving information pertaining to the creation, modication, or removal ofbusiness objects. However, for transaction business objects the auditing will record modication, or removal of business

http://www.oracle.com/pls/topic/lookup?ctx=fa20a&id=F1B0D35ABEBAF5CDE040D30A68813C82



58

objects. All actions the user performs on an audited business object and its aributes are recorded and logged in a table.From the table, you can run a report that indicates changes made to aributes by users. Changes made by any user tothe audit-enabled aributes are recorded and retrievable.

To enable auditing on Payables business objects, navigate to: Setup and Maintenance > Search Tasks: Manage AuditPolicies > Manage Audit Policies page > Congure Business Object Aributes buon > Congure Business ObjectAributes page > Product choice list: Payables.

Payables Setup Business ObjectsAP_SYSTEM_PARAMETERS_ALL

Object name on the Congure Business Object Aributes page: General Payables Options

The AP_SYSTEM_PARAMETERS_ALL table stores the parameters and defaults you dene for operating your OracleFusion Payables application. This table contains information such as your set of books, functional currency andpayment terms. Your Oracle Fusion Payables application also uses this information to determine default values thatcascade down to supplier and invoice entry. This table corresponds to the Manage Invoice Options and ManagePayment Options tasks under Dene General Payables Options task. AP_SYSTEM_PARAMETERS_ALL_ is the audit tablefor AP_SYSTEM_PARAMETERS_ALL. The following table shows the elds that you can enable for auditing.

Audit Aribute Table Column Description Audit-Enabled by Default

Create interest invoices

AUTO_ CALCULATE_INTEREST_FLAG

Option that indicateswhether interest invoices areautomatically created for pastdue invoice payments (Y or N).

Yes

Invoice Currency

INVOICE_ CURRENCY_CODE

Default invoice currency codethat defaults on the suppliersites associated with thebusiness unit.

Yes

Always take discount

ALWAYS_ TAKE_ DISC_FLAG

Option that indicates ifan available discount fora supplier will be taken,regardless of when the invoiceis paid (Y or N).

Yes

Accounting Date Basis

GL_ DATE_ FROM_RECEIPT_FLAG

Date used as the accountingdate during invoice entry.

No

Exclude tax from calculation

DISC_ IS_ INV_LESS_TAX_FLAG

Option that indicates if taxamount excluded frominvoice amount when invoiceamount applicable to discountcalculated (Y or N).

Yes

Allow payment date before thesystem date

POST_ DATED_PAYMENTS_FLAG

Option that indicates if thepayment date can be prior tosystem date (Y or N).

Yes



59


Minimum interest amount

INTEREST_ TOLERANCE_AMOUNT

Minimum interest amountowed on past due invoicefor interest invoice to beautomatically created.

Yes

Interest Expense Distribution

INTEREST_ CODE_COMBINATION_ ID

Accounting Flexeld identierfor interest expense account.

Yes

Discount Allocation Method

DISCOUNT_ DISTRIBUTION_METHOD

Method for distributingdiscount amounts taken oninvoice payments.

Yes

Use combined ling program

COMBINED_ FILING_FLAG

Option that indicates whetheryour organization participatesin the Combined FilingProgram for income taxreporting.

Yes

Income Tax Region

INCOME_ TAX_REGION

Default income tax regionassigned to invoice lines for1099 suppliers.

Yes

Use supplier tax region

INCOME_ TAX_ REGION_FLAG

A value of Y indicates that youuse supplier tax region as thedefault Income Tax Region for1099. invoice lines.

Yes

Allow Final Matching

ALLOW_ FINAL_MATCH_FLAG

Option that indicates whetheryou allow nal matching topurchase orders.

Yes

Allow Matching distributionoverride

ALLOW_ FLEX_OVERRIDE_FLAG

Option that indicates whetheryou can override the matchingAccounting Flexeld foran invoice distributionmatched to a purchase orderdistribution line.

Yes

Allow adjustments to paidinvoices

ALLOW_ PAID_ INVOICE_ADJUST

Option that indicates whetheryou allow adjustments to paidinvoices.

Yes

Allow document categoryoverride

INV_ DOC_ CATEGORY_OVERRIDE

Option that indicateswhether you can override thedefault document category(Sequential Numbering) forinvoices.

Yes



60


Transfer PO distributionadditional information

TRANSFER_ DESC_FLEX_FLAG

A value of Y indicates theapplication will transferdescriptive exeldinformation from a purchaseorder shipment to an invoiceline and from the purchaseorder distribution to an invoicedistribution during purchaseorder matching.

Yes

Use withholding tax

ALLOW_AWT_FLAG

Option to indicate whetherAutomatic Withholding Tax isallowed (Y or N).

Yes

Withholding Tax Group

DEFAULT_ AWT_GROUP_ID

Default Withholding Taxgroup for new suppliers.

Yes

Allow manual withholding

ALLOW_ AWT_OVERRIDE

Option to indicate whetheroverride of withholding taxamount is allowed (Y, N, null).

Yes

Apply withholding tax

CREATE_ AWT_ DISTS_TYPE

Indicates when the applicationshould automatically createwithholding tax invoices.Possible values are Never,Validation, or Payment.

Yes

Create Withholding Invoice

CREATE_ AWT_INVOICES_TYPE

Indicates when the applicationshould automatically createwithholding tax invoices(Never, Invoice Validation,Payment).

Yes

Withholding Amount Basis toinclude discount amount

AWT_ INCLUDE_DISCOUNT_AMT

Option to indicate whether thediscount amount is included inwithholding tax calculation.

Yes

Withholding Amount Basis toinclude tax amount

AWT_ INCLUDE_ TAX_AMT

Option to indicate whether thetax amount is included in thewithholding tax calculation.

Yes

Allow override of supplier sitebank account

ALLOW_ SUPPLIER_BANK_OVERRIDE

Option to indicate whetheruser can charge remit-to bankat payment creation time.

Yes

Account for Payment

WHEN_ TO_ ACCOUNT_PMT

Denes when accountingentries for payments will becreated.

Yes



61


Enable invoice approval

APPROVAL_WORKFLOW_FLAG

Select this check box value toenable invoice approval.

Yes

Allow Force Approval

ALLOW_ FORCE_APPROVAL_FLAG

Select this check box value ifyou use the Invoice ApprovalWorkow Program and wantto allow accounts payableprocessors to override theworkow and manuallyapprove invoices.

Yes

Include withholdingdistributions in income taxreports

ENABLE_ 1099_ON_AWT_FLAG

Select this check box valueis you want to includeWithholding Distribution inIncome Tax Reports.

Yes

Quantity Tolerances

TOLERANCE_ID

A unique identier fortolerance template that's usedfor goods tolerance.

Yes

Amount Tolerances

SERVICES_ TOLERANCE_ID

Services tolerance templateidentier.

Yes

Receipt Acceptance Days

RECEIPT_ ACCEPTANCE_DAYS

Number of days in receiptacceptance period.

Yes

Exclude Freight from Discount

EXCLUDE_ FREIGHT_FROM_DISCOUNT

Exclude Freight From DiscountIdentier.

Yes

Interest Allocation Method

PRORATE_ INT_ INV_ACROSS_DISTS

Used to display the 'Interest'Allocation method inAccounting Option label.

Yes

Allow Unit Price change forQuantity-Based Matches

SS_ UPRICE_ CHANGE_FOR_QTYMATCH

Seing that indicates whetherunit price change is allowedfor purchase order matchedself-service invoice.

Yes

Allow invoice backdating

SS_ INVOICE_ BACKDATING_FLAG

Indicates whether a self-service invoice can haveinvoice date prior to systemdate.

Yes

Self Service Invoices to limitinvoices to a single purchaseorder

SS_ LIMIT_ TO_ SINGLE_PO_FLAG

Indicates whether a self-service invoice can bematched to multiple purchaseorders.

Yes



62


Require Invoice Grouping

REQUIRE_ INVOICE_GROUP_FLAG

Seing that indicates whetherinvoice group is mandatoryduring invoice entry.

Yes

Recalculate invoiceinstallments

RECALC_ PAY_SCHEDULE_FLAG

Option that indicateswhether Recalculate PaymentInstallments (Y or N).

Yes

Budget Date Basis

BUDGET_ DATE_BASIS

Budget Date Basis to defaultthe budget date on invoicetransactions.

Yes

FINANCIALS_SYSTEM_PARAMS_ALL

Object name on the Congure Business Object Aributes page: Common Options for Payables and Procurement

The FINANCIALS_SYSTEM_PARAMETERS_ALL table stores options and defaults you share between your OracleFusion Payables application, and your Oracle Fusion Purchasing and Oracle Fusion Assets applications. You candene these options and defaults according to the way you run your business. This table corresponds to the ManageCommon Options for Payables and Procurement task. FINANCIALS_SYSTEM_PARAMS_ALL_ is the audit table forFINANCIALS_SYSTEM_PARAMS_ALL. The following table shows the elds that you can enable for auditing.


Bill-to Location

BILL_ TO_ LOCATION_ID

Bill-to location identier,default used during supplierentry.

Yes

Liability Distribution

ACCTS_ PAY_ CODE_COMBINATION_ ID

Accounting Flexeld identierfor the accounts payableliability account and defaultused during supplier entry.

Yes

Prepayment Distribution

PREPAY_ CODE_COMBINATION_ ID

Accounting Flexeld identierfor the prepayment accountand default used duringsupplier entry.

Yes

Discount Taken Distribution

DISC_ TAKEN_ CODE_COMBINATION_ ID

Accounting Flexeld identierfor the discount takenaccount.

Yes

VAT Registration Number

VAT_ REGISTRATION_ NUM

Value-Added Tax registrationnumber for your organization.

Yes

VAT Registration MemberState

VAT_ COUNTRY_CODE

European Union (EU) memberstate for your organization.

Yes



63


Conversion Rate Variance Gain

RATE_ VAR_GAIN_CCID

Accounting Flexeld identierfor account used to recordexchange rate gains forinvoices matched to purchaseorders.

Yes

Conversion Rate Variance Loss

RATE_ VAR_LOSS_CCID

Accounting Flexeld identierfor account used to recordexchange rate losses forinvoices matched to purchaseorders.

Yes

Bill Payable Distribution

FUTURE_ DATED_PAYMENT_CCID

Accounting Flexeld identierfor future dated paymentaccount default for Suppliersand Bank accounts.

Yes

Miscellaneous Distribution

MISC_ CHARGE_CCID

Accounting exeld identierfor the accounts payablemiscellaneous account, whichis used for supplier portalInvoices.

Yes

Buying Company Identier

BUYING_ COMPANY_IDENTIFIER

A unique identier thatidenties the buying businessunit. The identier is includedon the invoice number ofinvoices created by the payon receipt process or debitmemos from return on receipttransactions.

Yes

Expense Accrual Distributions

EXPENSE_ ACCRUAL_CCID

Expense Accrual AccountCode Combination Identier.

Yes

Gapless Invoice Numbering

GAPLESS_ INV_NUM_FLAG

Gapless Invoice NumberingOption.

Yes

Accrue Expense Items

EXPENSE_ ACCRUAL_CODE

Denes accrue expense itemsoptions.

Yes

Conversion Rate type

DEFAULT_ EXCHANGE_RATE_TYPE

Species the defaultconversion rate type whenyou enter invoices or createpayments.

Yes

Automatic Osets

AUTOMATIC_ OFFSETS_FLAG

An option that allowsoverriding of either theprimary balancing segment

Yes



64


or all segments, except thenatural account segmentwhen creating the liabilityaccount.

Realized Gain Distribution

GAIN_ CODE_ COMBINATION_ID

Accounting Flexeld identierfor account to which realizedexchange rate gains areposted.

Yes

Realized Loss Distribution

LOSS_ CODE_COMBINATION_ ID

Accounting Flexeld identierfor account to which realizedexchange rate losses areposted.

Yes

Require conversion rate entry

MAKE_ RATE_ MANDATORY_FLAG

Option that indicates ifexchange rates must beentered for multiple currencyinvoices and payments (Y orN).

Yes

Freight Distribution

FREIGHT_ CODE_COMBINATION_ ID

Accounting Flexeld identierfor accounts payable freightaccount.

Yes

Prepayment Tax Dierence

PREPAY_ TAX_DIFF_CCID

Account to which anyprepayment tax dierenceamount will be charged.

Yes

Require Conversion Rate Entry

MAKE_ RATE_ MANDATORY_PMT_FLAG

Require Conversion RateInformation for Payments.

No

Payment Conversion RateType

DEFAULT_ PMT_ EXCHANGE_RATE_TYPE

Payment Conversion RateType.

No

AP_TOLERANCE_TEMPLATES

Object name on the Congure Business Object Aributes page: Invoice Tolerances

The AP_TOLERANCE_TEMPLATES table stores the tolerance levels you set for matching and invoice variance testing.Oracle Fusion Payables uses this information to determine during Invoice Validation to hold an invoice for exceedingtolerance. AP_TOLERANCE_TEMPLATES_ is the audit table for AP_TOLERANCE_TEMPLATES. The following tableshows the elds that you can enable for auditing.



65


Name

TOLERANCE_NAME

Name of the tolerancetemplate.

Yes

Description

DESCRIPTION

Description of the tolerancetemplate.

No

Price Percentage

PRICE_ TOLERANCE

Percentage based tolerancelevel for price variance.

Yes

Ordered Percentage

QUANTITY_ TOLERANCE

Percentage based tolerancelevel for quantity variance.

Yes

Received Percentage

QTY_ RECEIVED_ TOLERANCE

Percentage based tolerancelevel for quantity receivedtolerance.

Yes

Maximum Ordered

MAX_ QTY_ORD_TOLERANCE

Tolerance level for maximumquantity ordered variance.

Yes

Maximum Received

MAX_ QTY_ REC_TOLERANCE

Tolerance level for maximumquantity received variance.

Yes

Schedule Amount

SHIP_ AMT_TOLERANCE

Tolerance level for purchaseorder shipment amountvariance

Yes


RATE_ AMT_TOLERANCE

Tolerance level for exchangerate amount variance.

Yes

Total Amount

TOTAL_ AMT_TOLERANCE

Tolerance level for totalamount variance.

Yes

Type

TOLERANCE_TYPE

Designates the type oftolerance template as eitherGoods or Services.

Yes

Consumed Percentage

QTY_ CONSUMED_TOLERANCE

Tolerance level forcomparison of billed quantitywith consumed quantityexpressed as a percentage.

Yes

Maximum Consumed

MAX_ QTY_CON_TOLERANCE

Tolerance level forcomparison of billed quantitywith consumed quantityexpressed as an absolutevalue.

Yes



66


AP_REPORTING_ENTITIES_ALL

Object name on the Congure Business Object Aributes page: Reporting Entities

The AP_REPORTING_ENTITIES_ALL table stores the information about the reporting entities you dene for 1099reporting. This table corresponds to the Manage Reporting Entities task. AP_REPORTING_ENTITIES_ALL_ is the audittable for AP_REPORTING_ENTITIES_ALL. The following table shows the elds that you can enable for auditing.


Taxpayer ID

TAX_ IDENTIFICATION_ NUM

Tax identication number forreporting entity.

Yes

Name

ENTITY_NAME

Name of the reporting entityfor tax reporting.

Yes

Location

LOCATION_ID

Location identier forreporting entity.

Yes

Business Unit

ORG_ID

Indicates the identier of thebusiness unit associated to therow.

Yes

Global Aribute Category

GLOBAL_ ATTRIBUTE_CATEGORY

Global Descriptive Flexeld:structure denition of theglobal descriptive exeld.

No

Global Aribute 1

GLOBAL_ ATTRIBUTE1

Global Descriptive Flexeld:segment of the globaldescriptive exeld.

No

Global Aribute 2

GLOBAL_ ATTRIBUTE2


No

Global Aribute 3

GLOBAL_ ATTRIBUTE3


No

Global Aribute 4

GLOBAL_ ATTRIBUTE4


No



67


Global Aribute 5

GLOBAL_ ATTRIBUTE5


No

Global Aribute 6

GLOBAL_ ATTRIBUTE6


No

Global Aribute 7

GLOBAL_ ATTRIBUTE7


No

Global Aribute 8

GLOBAL_ ATTRIBUTE8


No

Global Aribute 9

GLOBAL_ ATTRIBUTE9


No

Global Aribute 10

GLOBAL_ ATTRIBUTE10


No

Global Aribute 11

GLOBAL_ ATTRIBUTE11


No

Global Aribute 12

GLOBAL_ ATTRIBUTE12


No

Global Aribute 13

GLOBAL_ ATTRIBUTE13


No

Global Aribute 14

GLOBAL_ ATTRIBUTE14


No

Global Aribute 15

GLOBAL_ ATTRIBUTE15


No

Global Aribute 16

GLOBAL_ ATTRIBUTE16


No



68


Global Aribute 17

GLOBAL_ ATTRIBUTE17


No

Global Aribute 18

GLOBAL_ ATTRIBUTE18


No

Global Aribute 19

GLOBAL_ ATTRIBUTE19


No

Global Aribute 20

GLOBAL_ ATTRIBUTE20


No

AP_REPORTING_ENTITY_LINES_ALL

Object name on the Congure Business Object Aributes page: Balancing Segment Values

The AP_REPORTING_ENTITY_LINES_ALL table stores the line information for the tax reporting entities youdene. This table corresponds to the Balancing Segment Values section of the Manage Reporting Entities task.AP_REPORTING_ENTITY_LINES_ALL_ is the audit table for AP_REPORTING_ENTITY_LINES_ALL. The following tableshows the elds that you can enable for auditing.


Primary Balancing SegmentValue

BALANCING_SEGMENT_VALUE

Balancing segment value forreporting entity AccountingFlexeld.

Yes

Business Unit

ORG_ID


Yes

AP_BANK_CHARGES

Object name on the Congure Business Object Aributes page: Bank Charges

The AP_BANK_CHARGES table stores header information that you enter on the bank charges page. This tablecorresponds to the Manage Bank Charges task. AP_BANK_CHARGES_ is the audit table for AP_BANK_CHARGES. Thefollowing table shows the elds that you can enable for auditing.



69


Transferring Bank Branch ID

TRANSFERRING_ BANK_BRANCH_ID

Transferring bank branchidentier.

Yes

Transferring Bank Name

TRANSFERRING_BANK_NAME

Bank of customer, whichtransfers payment to supplierbank.

Yes

Transferring Bank Option

TRANSFERRING_ BANK

Transferring bank. Validvalues are ONE for specicbank and ALL when bankcharge is applicable to alltransferring banks.

Yes

Transferring Branch Option

TRANSFERRING_ BRANCH

Transferring branch. Validvalues are ONE for specicbranch and ALL when bankcharge is applicable to alltransferring branches oftransferring bank specied.

Yes

Receiving Bank Branch ID

RECEIVING_ BANK_BRANCH_ID

Receiving bank branchidentier.

Yes

Receiving Bank Name

RECEIVING_ BANK_NAME

Bank of supplier, whichreceives payment fromcustomer bank.

Yes

Receiving Bank Option

RECEIVING_BANK

Receiving branch. Valid valuesare ONE for specic bank, ALLfor when charge is applicableto all receiving banks, andOTHER for bank other thanthe transferring bank.

Yes

Receiving Branch Option

RECEIVING_ BRANCH

Receiving branch. Validvalues are ONE for specicbranch, ALL for when chargeis applicable to all receivingbranches, and OTHERfor branch other than thetransferring branch.

Yes

Selement Priority

SETTLEMENT_ PRIORITY

Selement priority. Validvalues are EXPRESS andNORMAL.

Yes

Currency

CURRENCY_CODE

Currency used to dene bankcharges.

Yes



70


Aribute Category

ATTRIBUTE_ CATEGORY

Descriptive Flexeld: structuredenition of the userdescriptive exeld.

No

Aribute 1

ATTRIBUTE1

Descriptive Flexeld: segmentof the user descriptiveexeld.

No

Aribute 2

ATTRIBUTE2


No

Aribute 3

ATTRIBUTE3


No

Aribute 4

ATTRIBUTE4


No

Aribute 5

ATTRIBUTE5


No

Aribute 6

ATTRIBUTE6


No

Aribute 7

ATTRIBUTE7


No

Aribute 8

ATTRIBUTE8


No

Aribute 9

ATTRIBUTE9


No

Aribute 10

ATTRIBUTE10


No

Aribute 11

ATTRIBUTE11


No



71


Aribute 12

ATTRIBUTE12


No

Aribute 13

ATTRIBUTE13


No

Aribute 14

ATTRIBUTE14


No

Aribute 15

ATTRIBUTE15


No

Aribute Number 1

ATTRIBUTE_ NUMBER1


No

Aribute Number 2

ATTRIBUTE_ NUMBER2


No

Aribute Number 3

ATTRIBUTE_ NUMBER3


No

Aribute Number 4

ATTRIBUTE_ NUMBER4


No

Aribute Number 5

ATTRIBUTE_ NUMBER5


No

Aribute Date 1

ATTRIBUTE_ DATE1


No

Aribute Date 2

ATTRIBUTE_ DATE2


No

Aribute Date 3

ATTRIBUTE_ DATE3


No



72


Aribute Date 4

ATTRIBUTE_ DATE4


No

Aribute Date 5

ATTRIBUTE_ DATE5


No

Legal Entity

LEGAL_ ENTITY_ID

Legal entity identier.

Yes

AP_BANK_CHARGE_LINES

Object name on the Congure Business Object Aributes page: Bank Charges Details

The AP_BANK_CHARGE_LINES table stores ranges for bank charges. This table corresponds to the Bank Charge Detailssection of the Manage Bank Charges task. AP_BANK_CHARGE_LINES_ is the audit table for AP_BANK_CHARGE_LINES.The following table shows the elds that you can enable for auditing.


From Payment Amount

TRANS_ AMOUNT_FROM

The end payment amount(lower amount) for givenamount range.

Yes

To Payment Amount

TRANS_ AMOUNT_TO

The start payment amount(higher amount) for givenamount range.

Yes

Standard Bank ChargeAmount

BANK_ CHARGE_ STANDARD

The bank charge amount atstandard rate.

Yes

Negotiated Bank ChargeAmount

BANK_ CHARGE_NEGOTIATED

The bank charge amount atnegotiated rate.

Yes

From Date

START_DATE

The start date to apply thebank charge at the speciedamount.

Yes

To Date

END_DATE

The end date to apply thebank charge at the speciedamount.

Yes

Aribute Category

ATTRIBUTE_ CATEGORY


No



73


Aribute 1

ATTRIBUTE1


No

Aribute 2

ATTRIBUTE2


No

Aribute 3

ATTRIBUTE3


No

Aribute 4

ATTRIBUTE4


No

Aribute 5

ATTRIBUTE5


No

Aribute 6

ATTRIBUTE6


No

Aribute 7

ATTRIBUTE7


No

Aribute 8

ATTRIBUTE8


No

Aribute 9

ATTRIBUTE9


No

Aribute 10

ATTRIBUTE10


No

Aribute 11

ATTRIBUTE11


No



74


Aribute 12

ATTRIBUTE12


No

Aribute 13

ATTRIBUTE13


No

Aribute 14

ATTRIBUTE14


No

Aribute 15

ATTRIBUTE15


No

Aribute Number 1

ATTRIBUTE_ NUMBER1


No

Aribute Number 2

ATTRIBUTE_ NUMBER2


No

Aribute Number 3

ATTRIBUTE_ NUMBER3


No

Aribute Number 4

ATTRIBUTE_ NUMBER4


No

Aribute Number 5

ATTRIBUTE_ NUMBER5


No

Aribute Date 1

ATTRIBUTE_ DATE1


No

Aribute Date 2

ATTRIBUTE_ DATE2


No

Aribute Date 3

ATTRIBUTE_ DATE3


No



75


Aribute Date 4

ATTRIBUTE_ DATE4


No

Aribute Date 5

ATTRIBUTE_ DATE5


No

AP_INTEREST_PERIODS

Object name on the Congure Business Object Aributes page: Interest Rates

The AP_INTEREST_PERIODS table stores information about interest rates and periods that Payables uses to createinvoices to pay interest owed on overdue invoices. This interest is calculated in accordance with the U.S. PromptPayment Act. This table corresponds to the Manage Interest Rates task. AP_INTEREST_PERIODS is the audit table forAP_INTEREST_PERIODS. The following table shows the elds that you can enable for auditing.


Rate

ANNUAL_ INTEREST_RATE

Interest rate applicable for agiven period.

Yes

From Date

START_DATE

Start date of a given interestperiod.

Yes

To Date

END_DATE

End date of a given interestperiod.

Yes

AP_TERMS_B

Object name on the Congure Business Object Aributes page: Payment Terms

The AP_TERMS_B table stores header information about payment terms you dene. You need one row for each type ofterms you use to create scheduled payments for invoices. When you enter suppliers or invoices, you can select paymentterms you have dened in this table. Each terms must have one or more terms lines. This table corresponds to theManage Payment Terms task. AP_TERMS_B_ is the audit table for AP_TERMS_B. The following table shows the eldsthat you can enable for auditing.


Name

TERM_ID

A unique identier for thepayment term.

Yes



76


From Date

START_ DATE_ACTIVE

Date from which paymentterm is valid.

Yes

To Date

END_ DATE_ACTIVE

Date after which paymentterm is invalid.

Yes

Cuto Day

DUE_CUTOFF_DAY

Used for certain terms only,day of a month after whichOracle Fusion Payablesschedules payment using aday after the current month.

Yes

Rank

RANK

Unique rank to rate invoicepayment terms againstpurchase order paymentterms in accordance withPrompt Payment Act.

Yes

Aribute Category

ATTRIBUTE_ CATEGORY


No

Aribute 1

ATTRIBUTE1


No

Aribute 2

ATTRIBUTE2


No

Aribute 3

ATTRIBUTE3


No

Aribute 4

ATTRIBUTE4


No

Aribute 5

ATTRIBUTE5


No

Aribute 6

ATTRIBUTE6


No



77


Aribute 7

ATTRIBUTE7


No

Aribute 8

ATTRIBUTE8


No

Aribute 9

ATTRIBUTE9


No

Aribute 10

ATTRIBUTE10


No

Aribute 11

ATTRIBUTE11


No

Aribute 12

ATTRIBUTE12


No

Aribute 13

ATTRIBUTE13


No

Aribute 14

ATTRIBUTE14


No

Aribute 15

ATTRIBUTE15


No

AP_TERMS_LINES

Object name on the Congure Business Object Aributes page: Installments

The AP_TERMS_LINES table stores detail information about payment terms you dene. This table corresponds tothe Installments and Discount sections of the Manage Payment Terms task. AP_TERMS_LINES_ is the audit table forAP_TERMS_LINES. The following table shows the elds that you can enable for auditing.



78


Name

TERM_ID

A unique identier for thepayment term.

Yes

Sequence Number

SEQUENCE_NUM

Number of the payment termline.

Yes

Due Percentage

DUE_PERCENT

Percentage of payment due bya certain date.

Yes

Amount Due

DUE_AMOUNT

Maximum of payment amountdue by a certain date.

Yes

Days

DUE_DAYS

Number of days after termsdate, used to calculate duedate of invoice payment line.

Yes

Day of Month

DUE_ DAY_OF_MONTH

Day of month used tocalculate due date of invoicepayment line.

Yes

Months Ahead

DUE_ MONTHS_ FORWARD

Number of months ahead,used to calculate due date ofinvoice payment line.

Yes

First Discount Percentage

DISCOUNT_ PERCENT

Percentage used to calculatediscount available for invoicepayment line.

Yes

First Discount Days

DISCOUNT_DAYS

Number of days after termsdate, used to calculatediscount date for invoicepayment line.

Yes

First Discount Day of Month

DISCOUNT_ DAY_OF_MONTH

Day of month used tocalculate discount date forinvoice payment line.

Yes

First Discount Months Ahead

DISCOUNT_ MONTHS_FORWARD

Number of months aheadused to calculate discountdate for invoice payment line.

Yes

Second Discount Percentage

DISCOUNT_ PERCENT_2

Percentage used to calculatesecond discount available forinvoice payment line.

Yes

Second Discount Days

DISCOUNT_ DAYS_2

Number of days after termsdate, used to calculate second

Yes



79


discount available for invoicepayment line

Second Discount Day ofMonth

DISCOUNT_ DAY_OF_MONTH_2

Day of month used tocalculate second discountavailable for invoice paymentline.

Yes

Second Discount MonthsAhead

DISCOUNT_ MONTHS_FORWARD_2

Number of months ahead,used to calculate discountavailable for invoice paymentline.

Yes

Third Discount Percentage

DISCOUNT_ PERCENT_3

Percentage used to calculatethird discount available forinvoice payment line.

Yes

Third Discount Days

DISCOUNT_ DAYS_3

Number of days after termsdate, used to calculate thirddiscount for invoice paymentline.

Yes

Third Discount Day of Month

DISCOUNT_ DAY_OF_MONTH_3

Day of month used tocalculate third discount forinvoice payment line.

Yes

Third Discount Months Ahead

DISCOUNT_ MONTHS_FORWARD_3

Number of months ahead,used to calculate thirddiscount for invoice paymentline.

Yes

Aribute Category

ATTRIBUTE_ CATEGORY


No

Aribute 1

ATTRIBUTE1


No

Aribute 2

ATTRIBUTE2


No

Aribute 3

ATTRIBUTE3


No



80


Aribute 4

ATTRIBUTE4


No

Aribute 5

ATTRIBUTE5


No

Aribute 6

ATTRIBUTE6


No

Aribute 7

ATTRIBUTE7


No

Aribute 8

ATTRIBUTE8


No

Aribute 9

ATTRIBUTE9


No

Aribute 10

ATTRIBUTE10


No

Aribute 11

ATTRIBUTE11


No

Aribute 12

ATTRIBUTE12


No

Aribute 13

ATTRIBUTE13


No

Aribute 14

ATTRIBUTE14


No

Aribute 15

ATTRIBUTE15


No



81


Fixed Date

FIXED_DATE

Payment term aribute thatindicates the payment duedate.

Yes

Calendar

CALENDAR

Name of special calendarassociated with the term line.

Yes

AP_TERMS_ST

Object name on the Congure Business Object Aributes page: Set Assignments

The AP_TERMS_ST table stores Set ID information for the payment terms you dene. This table corresponds to the SetAssignments section of the Manage Payment Terms task. AP_TERMS_ST_ is the audit table for AP_TERMS_ST. Thefollowing table shows the elds that you can enable for auditing.


Name

TERM_ID

Payment term uniqueidentier.

Yes

Set Code

SET_ID

Identies a set of referencedata shared across businessunits and other entities. Alsoknown as Reference Data Sets,they're used to lter referencedata in transactional UIs.

Yes

AP_HOLD_CODES

Object name on the Congure Business Object Aributes page: Invoice Holds and Releases

The AP_HOLD_CODES table stores information about hold codes and release codes that you or your Oracle FusionPayables application can place on an invoice. This table corresponds to the Manage Invoice Holds and Releases task.AP_HOLD_CODES_ is the audit table for AP_HOLD_CODES. The following table shows the elds that you can enable forauditing.


Name

HOLD_ LOOKUP_CODE

Name of the hold code createdto be applied on an invoice.

Yes

Type

HOLD_TYPE

Hold type that's to be appliedon an invoice.

Yes



82


Allow Manual Release

USER_ RELEASEABLE_ FLAG

Indicates if a hold can bereleased by a user (Y or N).

Yes

Inactive Date

INACTIVE_DATE

Date when the hold will beinactive.

Yes

Allow Accounting

POSTABLE_FLAG

Indicates whether this holdshould prevent the invoicefrom being accounted.

Yes

Hold Instruction

HOLD_ INSTRUCTION

Instruction to resolve the hold.

Yes

Days Before Notifying

WAIT_ BEFORE_NOTIFY_DAYS

Specify the number of daysto wait before sending thenotication.

Yes

Days Before Reminding

REMINDER_DAYS

Specify the number of daysto wait before sending thereminder notication.

Yes

Allow Holds ResolutionRouting

INITIATE_ WORKFLOW_FLAG

Enable this to initiate the HoldNegotiation Workow for thehold.

Yes

AP_DISTRIBUTION_SETS_ALL

Object name on the Congure Business Object Aributes page: Distribution Sets

The AP_DISTRIBUTION_SETS_ALL table stores information about Distribution Sets you dene to distribute invoicesautomatically. AP_DISTRIBUTION_SETS_ALL_ is the audit table for AP_DISTRIBUTION_SETS_ALL. This tablecorresponds to the Manage Distribution Sets task. The following table shows the elds that you can enable for auditing.


Name

DISTRIBUTION_ SET_NAME

Name of invoice distributionset created.

Yes

Description

DESCRIPTION

Description of invoicedistribution set created.

Yes

Distribution Percentage

TOTAL_ PERCENT_DISTRIBUTION

Sum of the distributionpercents for each of thedistribution set lines.

Yes



83


Inactive Date

INACTIVE_DATE

Date by when the distributionset will become inactive.

Yes

Aribute Category

ATTRIBUTE_ CATEGORY


No

Aribute 1

ATTRIBUTE1


No

Aribute 2

ATTRIBUTE2


No

Aribute 3

ATTRIBUTE3


No

Aribute 4

ATTRIBUTE4


No

Aribute 5

ATTRIBUTE5


No

Aribute 6

ATTRIBUTE6


No

Aribute 7

ATTRIBUTE7


No

Aribute 8

ATTRIBUTE8


No

Aribute 9

ATTRIBUTE9


No

Aribute 10

ATTRIBUTE10


No



84


Aribute 11

ATTRIBUTE11


No

Aribute 12

ATTRIBUTE12


No

Aribute 13

ATTRIBUTE13


No

Aribute 14

ATTRIBUTE14


No

Aribute 15

ATTRIBUTE15


No

Business Unit

ORG_ID


Yes

AP_DISTRIBUTION_SET_LINES_ALL

Object name on the Congure Business Object Aributes page: Distribution Set Details

The AP_DISTRIBUTION_SET_LINES_ALL table stores detailed information about individual distribution lines you denefor a Distribution Set. This table corresponds to the Distribution Set Details section of the Manage Distribution Sets task.AP_DISTRIBUTION_SET_LINES_ALL_ is the audit table for AP_DISTRIBUTION_SET_LINES_ALL. The following tableshows the elds that you can enable for auditing.


Distribution Combination

DIST_ CODE_ COMBINATION_ID

Accounting Flexeld identierfor account associated withDistribution Set line.

Yes

Distribution

PERCENT_ DISTRIBUTION

Percent of invoice amount toallocate to Distribution Setline.

Yes

Income Tax Type

TYPE_1099

Type of 1099 tax associatedwith distribution line.

Yes



85


Description

DESCRIPTION

Description of distribution setline.

No

Line

DISTRIBUTION_ SET_LINE_NUMBER

Invoice Distribution Set lineidentier.

No

Aribute Category

ATTRIBUTE_ CATEGORY


No

Aribute 1

ATTRIBUTE1


No

Aribute 2

ATTRIBUTE2


No

Aribute 3

ATTRIBUTE3


No

Aribute 4

ATTRIBUTE4


No

Aribute 5

ATTRIBUTE5


No

Aribute 6

ATTRIBUTE6


No

Aribute 7

ATTRIBUTE7


No

Aribute 8

ATTRIBUTE8


No

Aribute 9

ATTRIBUTE9


No



86


Aribute 10

ATTRIBUTE10


No

Aribute 11

ATTRIBUTE11


No

Aribute 12

ATTRIBUTE12


No

Aribute 13

ATTRIBUTE13


No

Aribute 14

ATTRIBUTE14


No

Aribute 15

ATTRIBUTE15


No

Project Accounting Context

PROJECT_ ACCOUNTING_CONTEXT

Oracle Fusion ProjectsDescriptive Flexeld contextcolumn.

No

Task Number

TASK_ID

Identier for project task usedto build Accounting Flexeldfor Distribution Set line.

No

Project Number

PROJECT_ID

Identier for project used tobuild Accounting Flexeld forDistribution Set line.

No

Expenditure Organization

EXPENDITURE_ORGANIZATION_ ID

Identier for projectorganization used to buildAccounting Flexeld forDistribution Set line

No

Expenditure Type

EXPENDITURE_ TYPE

Project expenditure type usedto build Accounting Flexeldfor Distribution Set line.

No

Business Unit

ORG_ID


Yes



87


Award Number

AWARD_ID

If Oracle Fusion GrantsAccounting is installed, theaward ID is used with data inproject columns to track grantinformation.

No

AP_AGING_PERIODS

Object name on the Congure Business Object Aributes page: Aging Periods

The AP_AGING_PERIODS table stores aging periods that you dene for use in the Invoice Aging Report. This tablecorresponds to the Manage Aging Periods task. AP_AGING_PERIODS_ is the audit table for AP_AGING_PERIODS. Thefollowing table shows the elds that you can enable for auditing.


Aging Period ID

AGING_ PERIOD_ID

Unique identier of agingperiod dened in application.

Yes

Name

PERIOD_NAME

Name of aging period denedin system.

Yes

Description

DESCRIPTION

Description of aging perioddened.

No

Active

STATUS

Status of aging period.

Yes

Aribute Category

ATTRIBUTE_ CATEGORY


No

Aribute 1

ATTRIBUTE1


No

Aribute 2

ATTRIBUTE2


No

Aribute 3

ATTRIBUTE3


No



88


Aribute 4

ATTRIBUTE4


No

Aribute 5

ATTRIBUTE5


No

Aribute 6

ATTRIBUTE6


No

Aribute 7

ATTRIBUTE7


No

Aribute 8

ATTRIBUTE8


No

Aribute 9

ATTRIBUTE9


No

Aribute 10

ATTRIBUTE10


No

Aribute 11

ATTRIBUTE11


No

Aribute 12

ATTRIBUTE12


No

Aribute 13

ATTRIBUTE13


No

Aribute 14

ATTRIBUTE14


No

Aribute 15

ATTRIBUTE15


No



89

AP_AGING_PERIOD_LINES

Object name on the Congure Business Object Aributes page: Aging Period Details

The AP_AGING_PERIOD_LINES table stores information on individual aging periods. This table corresponds to theAging Period Details section of the Manage Aging Periods task. AP_AGING_PERIOD_LINES_ is the audit table forAP_AGING_PERIOD_LINES. The following table shows the elds that you can enable for auditing.


Aging Period Line ID

AGING_ PERIOD_ LINE_ID

Unique identier of agingperiod line dened as part ofaging period setup.

Yes

Column Order

PERIOD_ SEQUENCE_NUM

Order of this particular daterange within the entire period.

Yes

From

DAYS_START

Starting day number for agingperiod line.

Yes

To

DAYS_TO

Ending day number for agingperiod line.

Yes

First

REPORT_ HEADING1

First column heading for agingperiod line.

Yes

Second

REPORT_ HEADING2

Second column heading foraging period line.

Yes

Aribute Category

ATTRIBUTE_ CATEGORY


No

Aribute 1

ATTRIBUTE1


No

Aribute 2

ATTRIBUTE2


No

Aribute 3

ATTRIBUTE3


No

Aribute 4

ATTRIBUTE4


No



90


Aribute 5

ATTRIBUTE5


No

Aribute 6

ATTRIBUTE6


No

Aribute 7

ATTRIBUTE7


No

Aribute 8

ATTRIBUTE8


No

Aribute 9

ATTRIBUTE9


No

Aribute 10

ATTRIBUTE10


No

Aribute 11

ATTRIBUTE11


No

Aribute 12

ATTRIBUTE12


No

Aribute 13

ATTRIBUTE13


No

Aribute 14

ATTRIBUTE14


No

Aribute 15

ATTRIBUTE15


No

AP_INCOME_TAX_REGIONS



91

Object name on the Congure Business Object Aributes page: Tax Regions

The AP_INCOME_TAX_REGIONS table stores information about the tax regions you use to record payment informationfor 1099 suppliers when your organization participates in the Combined Filing Program. This table corresponds tothe Manage Tax Regions task. AP_INCOME_TAX_REGIONS_ is the audit table for AP_INCOME_TAX_REGIONS. Thefollowing table shows the elds that you can enable for auditing.


State

REGION_ SHORT_NAME

Abbreviated income tax regionname (identies income taxregion for 1099 supplier sites).

Yes

Description

REGION_ LONG_NAME

Full name of income taxregion applicable for 1099taxes.

Yes

Code

REGION_CODE

Region code for income taxregions participating in theCombined Filing Program.

Yes

Amount

REPORTING_ LIMIT

Minimum reporting amountfor income tax regionparticipating in the CombinedFiling Program.

Yes

From Date

ACTIVE_DATE

Date from when the incometax region is active.

Yes

To Date

INACTIVE_DATE

Date income tax regioninactive.

Yes

Method

REPORTING_ LIMIT_METHOD_CODE

Method for calculatingreporting limit for region.

Yes

AP_OTHER_PERIOD_TYPES

Object name on the Congure Business Object Aributes page: Payables Calendars

The AP_OTHER_PERIOD_TYPES table stores the period type you dene and use to create recurring invoice, automaticwithholding tax, key indicators and payment terms periods. This table corresponds to the Manage Payables Calendarstask. AP_OTHER_PERIOD_TYPES_ is the audit table for AP_OTHER_PERIOD_TYPES. The following table shows theelds that you can enable for auditing.



92


Name

CALENDAR_NAME

Name given to a calendarthat's used in Oracle FusionPayables.

Yes

To Date

EFFECTIVE_TO

Eective To date of thecalendar.

Yes

From Date

EFFECTIVE_FROM

Eective From date of thecalendar.

Yes

Calendar Type

CALENDAR_TYPE

Type of the calendar, eitherGENERAL or PAYMENTTERMS.

Yes

Description

DESCRIPTION

Statement, picture in words,or account that describes;descriptive representation.

No

Aribute Category

ATTRIBUTE_ CATEGORY


No

Aribute 1

ATTRIBUTE1


No

Aribute 2

ATTRIBUTE2


No

Aribute 3

ATTRIBUTE3


No

Aribute 4

ATTRIBUTE4


No

Aribute 5

ATTRIBUTE5


No

Aribute 6

ATTRIBUTE6


No



93


Aribute 7

ATTRIBUTE7


No

Aribute 8

ATTRIBUTE8


No

Aribute 9

ATTRIBUTE9


No

Aribute 10

ATTRIBUTE10


No

Aribute 11

ATTRIBUTE11


No

Aribute 12

ATTRIBUTE12


No

Aribute 13

ATTRIBUTE13


No

Aribute 14

ATTRIBUTE14


No

Aribute 15

ATTRIBUTE15


No

AP_OTHER_PERIODS

Object name on the Congure Business Object Aributes page: Period Information

The AP_OTHER_PERIODS table stores information about the time periods you dene for use in recurring invoices,withholding taxes, key indicators and payment terms. This table corresponds to the Period Information section of theManage Payables Calendars task. AP_OTHER_PERIODS_ is the audit table for AP_OTHER_PERIODS. The following tableshows the elds that you can enable for auditing.



94


Start Date

START_DATE

Date from when a record isn'tavailable for transacting. Usedate enabled entities whenhistory isn't stored.

Yes

End Date

END_DATE

Date from when a record isn'tavailable for transacting. Usedate enabled entities whenhistory isn't stored.

Yes

Sequence

PERIOD_NUM

Order of periods within apayables calendar.

Yes

Aribute Category

ATTRIBUTE_ CATEGORY


No

Aribute 1

ATTRIBUTE1


No

Aribute 2

ATTRIBUTE2


No

Aribute 3

ATTRIBUTE3


No

Aribute 4

ATTRIBUTE4


No

Aribute 5

ATTRIBUTE5


No

Aribute 6

ATTRIBUTE6


No

Aribute 7

ATTRIBUTE7


No

Aribute 8

ATTRIBUTE8


No



95


Aribute 9

ATTRIBUTE9


No

Aribute 10

ATTRIBUTE10


No

Aribute 11

ATTRIBUTE11


No

Aribute 12

ATTRIBUTE12


No

Aribute 13

ATTRIBUTE13


No

Aribute 14

ATTRIBUTE14


No

Aribute 15

ATTRIBUTE15


No

Due Date

DUE_DATE

Date associated with apayables calendar period thatindicates when an invoicepayment is due. This isonly applicable to payablescalendars with a type ofpayment terms.

Yes

Calendar Name

PERIOD_ID

Identier of the createdperiod.

Yes

Payables Transaction Business ObjectsAuditing takes into account update and delete operations performed by the user on an object and its aributes. It won'trecord the data that's not updated by the user. For example, data updated by a schedule process.

AP_INVOICES_INTERFACE



96

Object name on the Congure Business Object Aributes page: Correct Import Errors Invoice Headers

AP_INVOICES_INTERFACE stores header information about invoices that you create or load for import. Invoice datacomes from sources including: supplier invoices that you transfer through the Oracle XML Gateway, and invoices thatyou enter through the Invoice Gateway. There's one row for each invoice you import. Your Oracle Payables applicationuses this information to create invoice header information when you submit the Payables Open Interface program.AP_INVOICES_INTERFACE_ is the audit table for AP_INVOICES_INTERFACE. The following table shows the elds thatyou can enable for auditing.


Liability Distribution ID


Accounting Flexeld identierfor accounts payable liabilityaccount. If the identierisn't available, use theACCTS_ PAY_ CODE_CONCATENATED column.Validated against.GL_CODE_ COMBINATIONS.CODECOMBINATION ID.

No

Add Tax to Invoice Amount

ADD_ TAX_ TO_INV_AMT_FLAG

Indicates whether the invoiceamount should be grossedup by the calculated tax. Validvalues: Y, N, NULL.

No

Discountable Amount

AMOUNT_ APPLICABLE_TO_DISCOUNT

Amount of invoice applicableto a discount. Not validated.

No

Application ID

APPLICATION_ID

Oracle internal use only. ForOracle Fusion applicationsinterfacing to Oracle FusionPayables.

No

Aribute Category

ATTRIBUTE_ CATEGORY


No

Aribute 1

ATTRIBUTE1


No

Aribute 10

ATTRIBUTE10


No

Aribute 11

ATTRIBUTE11


No



97


Aribute 12

ATTRIBUTE12


No

Aribute 13

ATTRIBUTE13


No

Aribute 14

ATTRIBUTE14


No

Aribute 15

ATTRIBUTE15


No

Aribute 2

ATTRIBUTE2


No

Aribute 3

ATTRIBUTE3


No

Aribute 4

ATTRIBUTE4


No

Aribute 5

ATTRIBUTE5


No

Aribute 6

ATTRIBUTE6


No

Aribute 7

ATTRIBUTE7


No

Aribute 8

ATTRIBUTE8


No

Aribute 9

ATTRIBUTE9


No



98


Withholding Tax Group ID

AWT_GROUP_ID

Withholding tax groupidentier. If the identierisn't available, use the AWT_GROUP_NAME column.Validated against AP_ AWT_GROUPS.AWT_ GROUP_ID.

No

Bank Charge Bearer

BANK_ CHARGE_BEARER

Bearer of bank charge cost.Uses the Manage PayablesLookup task, lookup typeBANK BEARER CHARGE toidentify valid values.

No

Budget Date

BUDGET_DATE

Budgetary Calendar PeriodDate applicable for fundscheck.

No

Calculate Tax During Import

CALC_ TAX_ DURING_IMPORT_FLAG

Indicates whether tax shouldbe calculated for the invoiceduring import. Valid values:Y,N, NULL.

No

Tax Control Amount

CONTROL_AMOUNT

Total tax amount. Cannot bemore than the invoice amount.

No

Correction Period

CORRECTION_ PERIOD

Correction period for theinvoice being corrected. Notvalidated.

No

Correction Year

CORRECTION_ YEAR

Correction year for the invoice.Valid format: four numbers.Example: 2010.

No

Delivery Channel

DELIVERY_ CHANNEL_CODE

Information displayed foran electronic payment thatinstruct the bank aboutcarrying out the payment.Example: print a check andhold it for collection by thepayee. Use the ManagePayment Codes task toidentify valid values. Thecorresponding PaymentCode Type must be DeliveryChannel.

No

Description

DESCRIPTION

Invoice description. Free texteld. Not validated.

No

Document Category

DOC_ CATEGORY_CODE

Sequential numbering(voucher number) document

No



99


category. Use the ManagePayables DocumentSequences task to identifyvalid values. Validated againstFND_ DOC_ SEQUENCE_CATEGORIES. CODE.

Document Subtype

DOCUMENT_ SUB_TYPE

A document type requiredby a tax or governmentalauthority.

No

Conversion Date

EXCHANGE_DATE

Date exchange rate iseective. Usually theaccounting date of thetransaction. Date format:YYYY/MM/DD.

No

Conversion Rate

EXCHANGE_RATE

Exchange rate used for foreigncurrency invoices. Userentered conversion rate. Notvalidated.

No

Conversion Rate Type

EXCHANGE_ RATE_TYPE

Exchange rate type for foreigncurrency invoices. Use theManage Conversion RateTypes task to identify validvalues. Validated against GL_DAILY_ CONVERSION_ TYPES.CONVERSIONTYPE.

No

Pay Alone

EXCLUSIVE_ PAYMENT_FLAG

Indicates whether to payinvoice on a separate paymentdocument. Valid values: Y,N,NULL.

No

Remit-to Account

EXTERNAL_ BANK_ACCOUNT_ID

External bank accountidentier. Defaulted fromsupplier setup. Do notpopulate during interface.

No

First-Party Tax Registration ID

FIRST_ PARTY_REGISTRATION_ ID

First party tax registrationidentier.

No

First-Party Tax RegistrationNumber

FIRST_ PARTY_REGISTRATION_ NUM

First party tax registrationnumber.

No

Accounting Date

GL_DATE

Default accounting date forinvoice distributions. Dateformat: YYYY/MM/DD. Thedate must be in an open

No



100


or future open accountingperiod.




No

Global Aribute Date 1

GLOBAL_ ATTRIBUTE_ DATE1


No




No




No




No




No

Global Aribute Number 1

GLOBAL_ ATTRIBUTE_NUMBER1


No




No




No




No




No



101


Global Aribute 1

GLOBAL_ ATTRIBUTE1


No

Global Aribute 10

GLOBAL_ ATTRIBUTE10


No

Global Aribute 11

GLOBAL_ ATTRIBUTE11


No

Global Aribute 12

GLOBAL_ ATTRIBUTE12


No

Global Aribute 13

GLOBAL_ ATTRIBUTE13


No

Global Aribute 14

GLOBAL_ ATTRIBUTE14


No

Global Aribute 15

GLOBAL_ ATTRIBUTE15


No

Global Aribute 16

GLOBAL_ ATTRIBUTE16


No

Global Aribute 17

GLOBAL_ ATTRIBUTE17


No

Global Aribute 18

GLOBAL_ ATTRIBUTE18


No

Global Aribute 19

GLOBAL_ ATTRIBUTE19


No

Global Aribute 2

GLOBAL_ ATTRIBUTE2


No



102


Global Aribute 20

GLOBAL_ ATTRIBUTE20


No

Global Aribute 3

GLOBAL_ ATTRIBUTE3


No

Global Aribute 4

GLOBAL_ ATTRIBUTE4


No

Global Aribute 5

GLOBAL_ ATTRIBUTE5


No

Global Aribute 6

GLOBAL_ ATTRIBUTE6


No

Global Aribute 7

GLOBAL_ ATTRIBUTE7


No

Global Aribute 8

GLOBAL_ ATTRIBUTE8


No

Global Aribute 9

GLOBAL_ ATTRIBUTE9


No

Goods Received Date

GOODS_ RECEIVED_DATE

Date when goods on theinvoice were received. Dateformat: YYYY/MM/DD.Required if the terms datebasis is Goods Received.

No

Invoice Amount

INVOICE_AMOUNT

Invoice amount in transactioncurrency. Should be positivefor standard and prepaymentinvoices. Should be negativefor credit memos.

No

Invoice Currency


Currency of invoice. Use theManage Currencies task toidentify valid values. Use thethree character ISO currency

No



103


code. Example: US Dollars isUSD.

Invoice Date

INVOICE_DATE

Invoice date used to calculatedue date per payment terms.Date format: YYYY/MM/DD.

No

Invoice ID

INVOICE_ID

Invoice identier. Must beunique.

No

Invoice Includes Prepayment

INVOICE_ INCLUDES_PREPAY_FLAG

Prepayment included ininvoice amount. Valid values:Y,N, NULL.

No

Invoice Number

INVOICE_NUM

Supplier invoice number.Validation: must be unique forthe supplier site.

No

Invoice Received Date

INVOICE_ RECEIVED_DATE

Date when the invoice wasreceived. Also known as termsdate. Date format: YYYY/MM/DD. Required if the terms datebasis is Invoice Received Date.

No

Invoice Type

INVOICE_ TYPE_LOOKUP_CODE

Type of invoice. Use theManage Payables Lookupstask, lookup type INVOICETYPE to identify valid values.

No

Legal Entity ID

LEGAL_ ENTITY_ID

Unique identier of the legalentity. If the identier isn'tavailable, use the LEGAL_ENTITY_NAME column.

No

Legal Entity Name

LEGAL_ ENTITY_NAME

Name of the legal entity onthe invoice. Use the ManageLegal Entities task to identifyvalid values.

No

No Conversion RateAccounted Amount

NO_ XRATE_ BASE_AMOUNT

Invoice amount in thefunctional currency. Usedto calculate exchange rate.Used only when CalculateUser Exchange Rate option isenabled for foreign currencyinvoices with exchange ratetype of User.

No

Business Unit

OPERATING_UNIT

Business unit to which theinvoice refers.

No



104


Business Unit

ORG_ID

Identier of the business unitassociated with the row. Ifthe identier isn't available,use the OPERATING_ UNITcolumn.

No

Pay Group

PAY_ GROUP_LOOKUP_CODE

Groups suppliers or invoicesfor a single pay run. Examples:employees, merchandise,nonmerchandise. Use theManage Payables Lookupstask, lookup type PAY GROUPto identify valid values.

No

Payment Currency

PAYMENT_ CURRENCY_CODE

Oracle internal use only.

No

Payment Method

PAYMENT_ METHOD_CODE

Payment method, such ascheck, cash, or credit. Use theManage Payment Methodstask to identify valid values.

No

Payment Reason

PAYMENT_ REASON_CODE

Code to provide the paymentsystem or bank with additionaldetails for the payment. Usethe Manage Payment Codestask to identify valid values.The corresponding PaymentCode Type must be PaymentReason.

No

Payment Reason Comments

PAYMENT_ REASON_COMMENTS

Reason for the payment. Freetext eld. Not validated.

No

Customs Location Code

PORT_ OF_ENTRY_CODE

Identies the location or portthrough which the invoicedgoods entered the country.Free text eld. Not validated.

No

Prepayment ApplicationAmount

PREPAY_ APPLY_AMOUNT

Amount of prepayment toapply to the invoice. Mustbe positive. Cannot exceedthe unpaid invoice amountor the amount of availableprepayments.

No

Prepayment Accounting Date

PREPAY_GL_DATE

Accounting date for theprepayment application.If NULL, the value for thecolumn GL_DATE is used.Date format: YYYY/MM/DD.

No



105


Prepayment Line

PREPAY_ LINE_NUM

The invoice line of an existingprepayment to be applied tothe invoice.

No

Prepayment Number

PREPAY_NUM

Invoice number of an existing,fully paid prepayment forthe same supplier site tobe applied to the invoice.Validations: selement datemust be on or before thesystem date, if the type isTemporary, it must have thesame invoice and paymentcurrency as the invoice, theprepayment must not be fullyapplied.

No

Product Table

PRODUCT_TABLE

Name of the product sourcetable used to generate aninvoice. Free text eld. Notvalidated.

No

Reference Key 1

REFERENCE_KEY1

Captures invoice referenceinformation from non-Oracleapplication. Free text eld. Notvalidated.

No

Reference Key 2

REFERENCE_KEY2


No

Reference Key 3

REFERENCE_KEY3


No

Reference Key 4

REFERENCE_KEY4


No

Reference Key 5

REFERENCE_KEY5


No

Remit-to Address Name

REMIT_ TO_ ADDRESS_NAME

Remit-to address where thepayment should be sent

No



106


Remit-to Supplier

REMIT_ TO_ SUPPLIER_NAME

Third party supplier

No

Remit-to Supplier Number

REMIT_ TO_ SUPPLIER_NUM

Third party supplier number

No

Remiance Message 1

REMITTANCE_ MESSAGE1

Remiance message for use inpayment processing. Free texteld. Not validated.

No

Remiance Message 2



No

Remiance Message 3



No

Requester Employee Number

REQUESTER_EMPLOYEE_NUM


No

Requester First Name

REQUESTER_ FIRST_NAME

The rst name of theemployee who requestedgoods or services onthe invoice line. BothREQUESTER_ FIRST_NAMEand REQUESTER_LAST_NAME must bepopulated to determine avalid employee identier ifREQUESTER_ ID isn't used.

No

Requester ID

REQUESTER_ID

Requester of invoice: usedby the Invoice Approvalworkow process to generatethe list of approvers. If theidentier isn't available, usethe REQUESTOR_ NAMEcolumn.

No

Requester Last Name

REQUESTER_ LAST_NAME

The last name of theemployee who requestedgoods or services onthe invoice line. . BothREQUESTER_ FIRST_NAMEand REQUESTER_LAST_NAME must bepopulated to determine avalid employee identier ifREQUESTER_ ID isn't used.

No

Selement Priority


Priority to sele paymentfor the transaction. Use the

No



107


Manage Payables Lookupstask, lookup type IBY_SETTLEMENT_ PRIORITY toidentify valid values.

Supplier Tax InvoiceConversion Rate

SUPPLIER_ TAX_EXCHANGE_RATE

Supplier conversion rateentered in online invoicesto calculate the supplier taxamount for foreign currencyinvoices.

No

Supplier Tax Invoice Date

SUPPLIER_ TAX_INVOICE_DATE

Tax invoice date on thesupplier-issued tax invoice.Date format: YYYY/MM/DD.

No

Supplier Tax Invoice Number

SUPPLIER_ TAX_ INVOICE_NUMBER

The invoice number used toreport on a supplier issued taxinvoice that's distinct from theregular invoice. Free text eld.Not validated.

No

Internal Sequence Number

TAX_ INVOICE_INTERNAL_SEQ

Company-specic tax invoicenumber, in sequence, issuedby the company for a supplier-issued tax invoice. Free texteld. Not validated.

No

Internal Recording Date

TAX_ INVOICE_ RECORDING_DATE

If company-specic taxinvoice date and numberis captured, the date thecompany receives or recordsthe supplier-issued taxinvoice. Date format: YYYY/MM/DD.

No

Tax Related Invoice

TAX_ RELATED_ INVOICE_ID


No

Taxation Country

TAXATION_ COUNTRY

Sets the context for tax driverssuch as Product ClassicationCode. If no value is entered,it will display the legal entitycountry by default.

No

Terms Date

TERMS_DATE

Used with payment terms tocalculate scheduled paymentof an invoice. Date format:YYYY/MM/DD.

No

Payment Terms ID

TERMS_ID

Payment terms identier. Ifthe identier isn't available,use the TERMS_NAME

No



108


column. Validated against AP_TERMS_ TL.TERM_ID.

Payment Terms

TERMS_NAME

Name of payment term foran invoice. Use the ManagePayment Terms task toidentify valid values.

No

Supplier Tax Registration ID

THIRD_ PARTY_REGISTRATION_ ID

Third party tax registrationidentier.

No

Supplier Tax RegistrationNumber

THIRD_ PARTY_REGISTRATION_ NUM

Third party tax registrationnumber.

No

Unique Remiance Identier

UNIQUE_ REMITTANCE_IDENTIFIER

Unique remiance identierprovided by the payee. Notvalidated.

No

Unique Remiance IdentierCheck Digit

URI_ CHECK_DIGIT

Unique remiance identiercheck digit. Free text eld. Notvalidated.

No

Supplier

VENDOR_NAME

Supplier name. Use theManage Suppliers task toidentify valid values.

No

Supplier Number

VENDOR_NUM

Unique number to identifya supplier. Use the ManageSuppliers task to identify validvalues.

No

Supplier Site

VENDOR_ SITE_CODE

Physical location of thesupplier. Use the ManageSuppliers task to identify validvalues.

No

Voucher Number

VOUCHER_NUM

Unique internal identierassigned to a document.Required if documentcategory code has assignmenttype of manual.

No

AP_INVOICE_LINES_INTERFACE

Object name on the Congure Business Object Aributes page: Correct Import Errors Invoice Lines



109

AP_INVOICE_LINES_INTERFACE stores information used to create one or more invoice lines.AP_INVOICE_LINES_INTERFACE_ is the audit table for AP_INVOICE_LINES_INTERFACE. The following table shows theelds that you can enable for auditing.


Overlay Account Segment

ACCOUNT_ SEGMENT

Overrides account segmentof the default liability accountcombination for the invoiceline. Must be a valid value forthe accounting exeld.

No

Accounting Date

ACCOUNTING_ DATE

Date when the invoice line isto be accounted. Date format:YYYY/MM/DD.

No

Amount

AMOUNT

Amount of the invoice line.Validated against the invoicetype. Example: standardinvoices must have positiveamounts. Amount precision isvalidated against the currency.

No

Application ID

APPLICATION_ID

Oracle internal use only. Valuewill be derived.

No

Assessable Value

ASSESSABLE_ VALUE

Enter the amount to be usedas taxable basis. Free texteld. Not validated.

No

Book

ASSET_ BOOK_ TYPE_CODE

Default asset book fortransfers to Oracle FusionAssets. Use the ManageAssets Books task to identifyvalid values.

No

Track as Asset

ASSETS_ TRACKING_FLAG

A distribution line is trackedin Oracle Fusion Assets. Validvalues: Y, N.

No

Aribute Category

ATTRIBUTE_ CATEGORY


No

Aribute 1

ATTRIBUTE1


No

Aribute 10

ATTRIBUTE10


No



110


Aribute 11

ATTRIBUTE11


No

Aribute 12

ATTRIBUTE12


No

Aribute 13

ATTRIBUTE13


No

Aribute 14

ATTRIBUTE14


No

Aribute 15

ATTRIBUTE15


No

Aribute 2

ATTRIBUTE2


No

Aribute 3

ATTRIBUTE3


No

Aribute 4

ATTRIBUTE4


No

Aribute 5

ATTRIBUTE5


No

Aribute 6

ATTRIBUTE6


No

Aribute 7

ATTRIBUTE7


No



111


Aribute 8

ATTRIBUTE8


No

Aribute 9

ATTRIBUTE9


No

Withholding Tax Group ID

AWT_GROUP_ID

Withholding tax groupidentier. If the identierisn't available, use the AWT_GROUP_NAME column.Validated against AP_ AWT_GROUPS.GROUP_ ID.

No

Withholding Tax Group

AWT_GROUP_NAME

Used to apply multiplewithholding taxes to aninvoice line. Use the ManageWithholding Groups task toidentify valid values.

No

Overlay Primary BalancingSegment

BALANCING_ SEGMENT

Overrides balancing segmentof the default liability accountfor the invoice line. Must be avalid value for the accountingexeld.

No

Budget Date

BUDGET_DATE

Budgetary Calendar PeriodDate applicable for fundscheck

No

Consumption Advice LineNumber

CONSUMPTION_ ADVICE_LINE_NUMBER

Consumption adviceline number. Used forconsumption advice matching.

No

Consumption Advice

CONSUMPTION_ADVICE_NUMBER

Consumption advice number.Used for consumption advicematching.

No

Overlay Cost Center Segment

COST_ CENTER_ SEGMENT

Overrides cost center ofthe default liability accountcombination for the invoiceline. Must be a valid value forthe accounting exeld.

No

Multiperiod AccountingAccrual Account

DEF_ ACCTG_ ACCRUAL_CCID

Accrual account that's initiallydebited for deferred expenses

No



112


Multiperiod Accounting EndDate

DEF_ ACCTG_ END_DATE


No

Multiperiod Accounting StartDate

DEF_ ACCTG_ START_DATE


No

Distribution Combination ID


Valid account combinationfor the accounting exeldidentier distributionline. If the identier isn'tavailable, use the DIST_CODE_ CONCATENATEDcolumn. Validated againstGL_ CODE_ COMBINATIONS.CODECOMBINATION ID.

No

Distribution Set ID

DISTRIBUTION_ SET_ID

Distribution set identier. Ifthe identier isn't available,use the DISTRIBUTION_SET_NAME column.Validated against AP_DISTRIBUTION_ SETS_ ALL.DISTRIBUTIONSETID.

No

Distribution Set

DISTRIBUTION_ SET_NAME

Distribution set name. Use theManage Distribution Sets taskto identify valid values.

No

Location of Final Discharge

FINAL_ DISCHARGE_LOCATION_CODE

Final discharge location code.

No

Location of Final Discharge ID

FINAL_ DISCHARGE_LOCATION_ID

Final discharge locationidentier.

No

Final Match

FINAL_ MATCH_FLAG

Final match indicator fordistribution line matched topurchase order. Valid values:Y, N, NULL. NULL means N.

No

Fiscal Charge Type

FISCAL_ CHARGE_TYPE

Tax driver. Subclassicationfor invoice line type of Freightor Miscellaneous. Validvalues are from lookup ZX_CHARGE_TYPE.

No




No



113


Global Aribute 1

GLOBAL_ ATTRIBUTE1


No

Global Aribute 10

GLOBAL_ ATTRIBUTE10


No

Global Aribute 11

GLOBAL_ ATTRIBUTE11


No

Global Aribute 12

GLOBAL_ ATTRIBUTE12


No

Global Aribute 13

GLOBAL_ ATTRIBUTE13


No

Global Aribute 14

GLOBAL_ ATTRIBUTE14


No

Global Aribute 15

GLOBAL_ ATTRIBUTE15


No

Global Aribute 16

GLOBAL_ ATTRIBUTE16


No

Global Aribute 17

GLOBAL_ ATTRIBUTE17


No

Global Aribute 18

GLOBAL_ ATTRIBUTE18


No

Global Aribute 19

GLOBAL_ ATTRIBUTE19


No

Global Aribute 2

GLOBAL_ ATTRIBUTE2


No



114


Global Aribute 20

GLOBAL_ ATTRIBUTE20


No

Global Aribute 3

GLOBAL_ ATTRIBUTE3


No

Global Aribute 4

GLOBAL_ ATTRIBUTE4


No

Global Aribute 5

GLOBAL_ ATTRIBUTE5


No

Global Aribute 6

GLOBAL_ ATTRIBUTE6


No

Global Aribute 7

GLOBAL_ ATTRIBUTE7


No

Global Aribute 8

GLOBAL_ ATTRIBUTE8


No

Global Aribute 9

GLOBAL_ ATTRIBUTE9


No

Included in Taxable LineIndicator

INCL_ IN_ TAXABLE_LINE_FLAG

The amount in the tax line isincluded in the taxable line.Valid values: Y, N, NULL.

No

Income Tax Region

INCOME_ TAX_REGION

Reporting region fordistribution line for 1099supplier. Use the Manage TaxRegions task to identify validvalues. Validated against AP_INCOME_ TAX_ REGIONS.REGION SHORT_NAME.

No

Item ID

INVENTORY_ ITEM_ID

Oracle internal use only.Inventory item identier.

No



115


Item Description

ITEM_ DESCRIPTION

Item description. Free texteld. Not validated.

No

Landed Cost Enabled

LCM_ ENABLED_FLAG

Indicates whether invoice lineis enabled for landed costmanagement.

No

Line Group Number

LINE_ GROUP_NUMBER

Line group number. Usedto prorate charges acrossa group of lines. Must be apositive integer.

No

Line Number

LINE_NUMBER

Invoice line number. Must bea positive integer. Must beunique per invoice.

No

Line Type

LINE_ TYPE_ LOOKUP_CODE

Type of invoice line. Use theManage Payables Lookupstask, lookup type INVOICELINE TYPE to identify validvalues.

No

Manufacturer

MANUFACTURER

Name of a manufacturer of anasset or item. Free text eld.Not validated.

No

Match Option

MATCH_OPTION

The value of the Invoice Matchoption on the PO shipment.Valid values: P, R. P used forpurchase order. R used forreceipt.

No

Model

MODEL_NUMBER

Model number of the invoiceline item. Free text eld. Notvalidated.

No

Billable

PJC_ BILLABLE_FLAG

Oracle internal use only.Project-related item isavailable for customer billing.

No

Capitalizable

PJC_ CAPITALIZABLE_ FLAG

Oracle internal use only.Project-related item is eligiblefor capitalization.

No

Projects related

PJC_ CONTEXT_ CATEGORY

Oracle internal use only.Identies descriptive exeldapplication context forproject-related standardizedcode collection.

No



116


Purchase Order Distribution ID

PO_ DISTRIBUTION_ ID

Purchase order distributionline identier for matching. Ifthe identier isn't available,use the PO_ DISTRIBUTION_NUM column. Validatedagainst PO_ DISTRIBUTIONS_ALL.PO_ DISTRIBUTION_ ID.

No

Purchase Order DistributionNumber

PO_ DISTRIBUTION_ NUM

Purchase order distributionline number for matching. Usethe Manage Purchase Orderstask to identify valid values.

No

Purchase Order Header ID

PO_HEADER_ID

Purchase order headeridentier used for purchaseorder matching. If theidentier isn't available, usethe PURCHASE_ ORDER_NUMBER column. Validatedagainst PO_ HEADERS_ALL.PO_ HEADER_ID.

No

Purchase Order Line ID

PO_LINE_ID

Purchase order line identierfor matching. If the identierisn't available, use the PO_LINE_NUMBER column.Validated against PO_ LINES_ALL.PO_ LINE_ID.

No

Purchase Order Line LocationID

PO_ LINE_ LOCATION_ID

Purchase order line locationidentier for matching. If theidentier isn't available, usethe PO_ SHIPMENT_NUMcolumn. Validated against PO_LINE_ LOCATIONS_ ALL.LINE_LOCATION_ID.

No

Purchase Order Line Number

PO_LINE_NUMBER

Purchase order line numberfor matching. Use the ManagePurchase Orders task toidentify valid values.

No

Purchase Order

PO_NUMBER

Purchase order number formatching. Use the ManagePurchase Orders task toidentify valid values.

No

Purchase Order ScheduleNumber

PO_ SHIPMENT_NUM

Purchase order shipmentnumber for matching. Use theManage Purchase Orders taskto identify valid values.

No



117


Price Correction Invoice Line

PRICE_ CORRECT_INV_LINE_NUM

Invoice line dependent onprice correction. Use theManage Invoices task toidentify valid values.

No

Price Correction Invoice

PRICE_ CORRECT_ INV_NUM

Number of the invoice thatprice correction invoice isupdating. Use the ManageInvoices task to identify validvalues. Validated against AP_INVOICES_ ALL.INVOICE_NUM.

No

Price Correction Indicator

PRICE_ CORRECTION_ FLAG

Indicates if a line creates aprice correction. Valid values:Y, N, NULL.

No

Product Category

PRODUCT_ CATEGORY

Identies the taxable nature ofa noninventory item. Free texteld. Not validated.

No

Product Fiscal Classication

PRODUCT_ FISC_CLASSIFICATION

Product scal classicationfor tax. Free text eld. Notvalidated.

No

Product Table

PRODUCT_TABLE


No

Product Type

PRODUCT_TYPE

Override product type defaultfrom the inventory item fortax calculations. Valid values:GOODS, SERVICES.

No

Prorate Across All Item Lines

PRORATE_ ACROSS_FLAG

Prorate indicator: prorate alllines with the same LINE_GROUP_NUMBER. Validvalues: Y, N, NULL. NULLmeans Y.

No

Purchasing Category ID

PURCHASING_ CATEGORY_ID


No

Invoiced Quantity

QUANTITY_ INVOICED

Quantity invoiced againstpurchase order shipment.

No

Receipt Line Number

RECEIPT_ LINE_NUMBER

The receipt line numberwith which an invoice will bematched. Use the ReceiveExpected Shipments task toidentify valid values. Validated

No



118


against RCV_ SHIPMENT_LINES.LINE_ NUM.

Receipt Number

RECEIPT_NUMBER

The receipt number withwhich an invoice will bematched. Use the ReceiveExpected Shipments task toidentify valid values. Validatedagainst RCV_ SHIPMENT_HEADERS. RECEIPTNUM.

No

Reference Key 1

REFERENCE_KEY1

Captures referenceinformation for invoicesimported from non-Oracleapplications. Free text eld.Not validated.

No

Reference Key 2

REFERENCE_KEY2


No

Reference Key 3

REFERENCE_KEY3


No

Reference Key 4

REFERENCE_KEY4


No

Reference Key 5

REFERENCE_KEY5


No

Requester Employee Number

REQUESTER_EMPLOYEE_NUM


No

Requester First Name

REQUESTER_ FIRST_NAME


No

Requester ID

REQUESTER_ID


No

Requester Last Name REQUESTER_ LAST_NAME Oracle internal use only. No



119


Serial Number

SERIAL_NUMBER

Serial number for an item.Free text eld. Not validated.

No

Ship-from Location

SHIP_ FROM_LOCATION_CODE

Ship-from location code.

No

Ship-from Location ID

SHIP_ FROM_ LOCATION_ID

Ship-from location identier.

No

Ship-to Location

SHIP_ TO_ LOCATION_CODE

Location where goods arereceived from supplier. Usethe Manage Locations task toidentify valid values.

No

Ship-to Location ID

SHIP_ TO_ LOCATION_ID

Ship-to location identierfor tax calculations. Usedonly if the invoice line isn'tPO matched. If the identierisn't available, use the SHIP_TO_LOCATION column.

No

Tax Name

TAX

Classication of a chargeimposed by a government.Use the Manage Taxes task toidentify valid values.

No

Tax Classication

TAX_ CLASSIFICATION_ CODE

Classication code of theinvoice line in the interfacedata. Use the Manage TaxRates task to identify validvalues.

No

Tax Jurisdiction Code

TAX_ JURISDICTION_ CODE

Internal identier of a taxjurisdiction. Use the ManageTax Jurisdictions task toidentify valid values.

No

Tax Rate

TAX_RATE

The rate specied for a taxstatus in eect for a periodof time. Use the Manage TaxRates task to identify validvalues.

No

Tax Rate Code

TAX_RATE_CODE

Tax rate name associated withtax rate identier. The value ofthe identier is unique, but theTAX_RATE_CODE may havedierent tax rates based ondate ranges. Use the Manage

No



120


Tax Rates task to identify validvalues.

Tax Rate ID

TAX_RATE_ID

Oracle internal use only.Internal identier for tax rateeective on the invoice date.

No

Tax Regime Code

TAX_ REGIME_CODE

Set of tax rules for a taxauthority. Use the Manage TaxRegimes task to identify validvalues.

No

Tax Status Code

TAX_ STATUS_CODE

Tax status code. Examples:taxable standard rate, zerorated, exempt, nontaxable.Use the Manage Tax Statusestask to identify valid values.

No

Taxable Indicator

TAXABLE_FLAG

Indicates whether a line istaxable. Valid values: Y, N,NULL.

No

Transaction BusinessCategory

TRX_ BUSINESS_ CATEGORY

Transaction category for tax.Free text eld. Not validated.

No

Income Tax Type

TYPE_1099

Payments of type 1099 madeto a supplier. Use the IncomeTax Types task to identifyvalid values.

No

UOM

UNIT_ OF_ MEAS_LOOKUP_CODE

Unit of measure for thequantity on an invoice.Validated against purchaseorder matching option,unit of measure, andquantity. Codependency withQUANTITY_ INVOICED andUNIT_PRICE: all three columnsmust be consistent, eitherpopulated or not populated.Validated against INV_UNITS_ OF_ MEASURE.UNIT_OF_MEASURE.

No

Unit Price

UNIT_PRICE

Unit price for purchase ordermatched invoice items. Mustbe positive for standardinvoices; negative for creditand debit memos.

No



121


User-Dened FiscalClassication

USER_ DEFINED_ FISC_CLASS

Fiscal class for tax. Free texteld. Not validated.

No

Project Contract ID

PJC_ CONTRACT_ID

Oracle internal use only.Contract identier: usedwhen Oracle Fusion ProjectBilling or Oracle Fusion ProjectBilling or Oracle Fusion GrantsAccounting is installed.

No

Project Contract Name

PJC_ CONTRACT_NAME

Contract name used whenOracle Fusion Contract Billingor Oracle Fusion GrantsAccounting is installed.

No

Project Contract Number

PJC_ CONTRACT_ NUMBER

Contract number used whenOracle Fusion Contract Billingor Oracle Fusion GrantsAccounting is installed.

No

Project Expenditure Item Date

PJC_ EXPENDITURE_ITEM_DATE

Oracle internal use only. Dateon which project-relatedtransaction occurred. Dateformat: YYYY/MM/DD.

No

Project Expenditure Type ID

PJC_ EXPENDITURE_ TYPE_ID


No

Project Expenditure Type

PJC_ EXPENDITURE_TYPE_NAME

A classication of cost that'sassigned to each expenditureitem.

No

Project Funding Allocation ID

PJC_ FUNDING_ALLOCATION_ID

Oracle internal use only. Nameof project funding override.

No

Project Funding Source Name

PJC_ FUNDING_SOURCE_NAME

Name of the source fundingthe project.

No

Project Funding SourceNumber

PJC_ FUNDING_SOURCE_NUMBER

Number of the source fundingthe project.

No

Project ExpenditureOrganization ID

PJC_ ORGANIZATION_ ID

Oracle internal use only.Organization identier tobuild transaction descriptiveexeld for project-relatedtransaction distributions.

No



122


Project ExpenditureOrganization

PJC_ ORGANIZATION_ NAME

Organization to which theproject is assigned.

No

Project ID

PJC_PROJECT_ID


No

Project Name

PJC_ PROJECT_NAME

Name of the project towhich the invoice expense ischarged.

No

Project Number

PJC_ PROJECT_ NUMBER

Number of the project towhich the invoice expense ischarged.

No

Project Reserved Aribute 1

PJC_ RESERVED_ ATTRIBUTE1

Reserved for future project-related functionality.

No


PJC_ RESERVED_ATTRIBUTE10


No




No




No




No




No




No




No




No



123





No

Project Task ID

PJC_TASK_ID


No

Project Task Name

PJC_TASK_NAME

Name of the task used to buildthe transaction descriptiveexeld for project-relatedtransaction distributions.

No

Project Task Number

PJC_ TASK_NUMBER

A subdivision of projectwork. Task Number uniquelyidenties the element within aproject or structure.

No

Project User-Dened Aribute1

PJC_ USER_ DEF_ATTRIBUTE1

Reserved for user denableproject information.

No




No




No




No




No




No




No




No




No



124





No

Project Work Type

PJC_WORK_TYPE

Classication of project-related work performed.

No

Project Work Type ID

PJC_ WORK_TYPE_ID

Oracle internal use only.Identier for project-relatedclassication of the workedperformed.

No

Intended Use

PRIMARY_ INTENDED_USE

Tax driver: the purpose forwhich a product may be used.Free text eld. Not validated.

No

Purchasing Category

PURCHASING_ CATEGORY

Item category concatenatedsegments for derivingpurchasing categoryinformation. Use the ManageCatalogs task to identify validvalues.

No

Invoice Id

INVOICE_ID

Invoice identier. Must beunique.

No

Asset Category

ASSET_ CATEGORY_ID

Default asset category fortransfers to Oracle FusionAssets. Use the Manage AssetCategories task to identifyvalid values.

No

Consumption Advice

CONSUMPTION_ ADVICE_HEADER_ID

Consumption adviceheader identier. Used forconsumption advice matching.

No

Consumption Advice LineNumber

CONSUMPTION_ ADVICE_LINE_ID

Consumption adviceline identier. Used forconsumption advice matching.

No

AP_INVOICES_ALL

Object name on the Congure Business Object Aributes page: Invoice

AP_INVOICES_ALL contains records for invoices you enter. There's one row for each invoice you enter. An invoicecan have one or more lines and each line can have one or more distributions. An invoice can also have one or moreinstallments. AP_INVOICES_ALL_ is the audit table for AP_INVOICES_ALL. The following table shows the elds that youcan enable for auditing.



125


Liability Distribution


Accounting Flexeld identierfor accounts payable liabilityaccount.

No

Discountable Amount

AMOUNT_ APPLICABLE_TO_DISCOUNT

Amount of invoice applicableto a discount.

No

Aribute Category

ATTRIBUTE_ CATEGORY


No

Aribute 1

ATTRIBUTE1


No

Aribute 10

ATTRIBUTE10


No

Aribute 11

ATTRIBUTE11


No

Aribute 12

ATTRIBUTE12


No

Aribute 13

ATTRIBUTE13


No

Aribute 14

ATTRIBUTE14


No

Aribute 15

ATTRIBUTE15


No

Aribute 2

ATTRIBUTE2


No

Aribute 3

ATTRIBUTE3


No



126


Aribute 4

ATTRIBUTE4


No

Aribute 5

ATTRIBUTE5


No

Aribute 6

ATTRIBUTE6


No

Aribute 7

ATTRIBUTE7


No

Aribute 8

ATTRIBUTE8


No

Aribute 9

ATTRIBUTE9


No

Bank Charge Bearer

BANK_ CHARGE_BEARER

Bearer of bank charge cost.Bank charge bearers aredened as the lookup IBY_BANK_ CHARGE_ BEARER.

No

Invoice Group

BATCH_ID

Unique invoice groupidentier.

No

Budget Date

BUDGET_DATE


No

Control Amount

CONTROL_AMOUNT

Manually entered value toensure that the calculatedtax will be the same as on thephysical document.

No

Correction Period

CORRECTION_ PERIOD

The tax declaration period ofa purchase transaction that'sbeing corrected.

No

Correction Year

CORRECTION_ YEAR

The tax declaration year of apurchase transaction that'sbeing corrected.

No



127


First-Party Taxpayer ID

CUST_ REGISTRATION_NUMBER

Customer legal registrationnumber.

No

Delivery Channel

DELIVERY_ CHANNEL_CODE

Text on electronic paymentthat instructs the bank aboutthe execution of payment. Forexample, print a check andhold it for collection by thepayee.

No

Description

DESCRIPTION

Statement that describes theinvoice.

No

Document Category

DOC_ CATEGORY_CODE

Sequential Numbering(voucher number) documentcategory.

No

Document Fiscal Classication

DOCUMENT_ SUB_TYPE

Classication to categorizea document associated witha transaction for tax. Thisaects the taxability of thetransaction.

No

Apply After

EARLIEST_ SETTLEMENT_DATE

Date associated with aprepayment after which youcan apply the prepaymentagainst invoices. Only usedfor temporary prepayments.Column is null for permanentprepayments and otherinvoice types.

No

Conversion Date

EXCHANGE_DATE

Date when a conversion rateis used to convert an amountinto another currency for aninvoice.

No

Conversion Rate

EXCHANGE_RATE

Ratio at which the principalunit of one currency isconverted into anothercurrency for an invoice.

No

Conversion Rate Type

EXCHANGE_ RATE_TYPE

Source of currency conversionrate for an invoice. Forexample, user dened, spot, orcorporate.

No



128


Pay Alone

EXCLUSIVE_ PAYMENT_FLAG

Indicator to pay the invoiceon a separate paymentdocument.

No

First-Party Tax RegistrationNumber

FIRST_ PARTY_REGISTRATION_ ID

First party tax registrationidentier.

No

Accounting Date

GL_DATE

Accounting date to default toinvoice distributions.

No




No

Global Aribute 1

GLOBAL_ ATTRIBUTE1


No

Global Aribute 10

GLOBAL_ ATTRIBUTE10


No

Global Aribute 11

GLOBAL_ ATTRIBUTE11


No

Global Aribute 12

GLOBAL_ ATTRIBUTE12


No

Global Aribute 13

GLOBAL_ ATTRIBUTE13


No

Global Aribute 14

GLOBAL_ ATTRIBUTE14


No

Global Aribute 15

GLOBAL_ ATTRIBUTE15


No

Global Aribute 16

GLOBAL_ ATTRIBUTE16


No



129


Global Aribute 17

GLOBAL_ ATTRIBUTE17


No

Global Aribute 18

GLOBAL_ ATTRIBUTE18


No

Global Aribute 19

GLOBAL_ ATTRIBUTE19


No

Global Aribute 2

GLOBAL_ ATTRIBUTE2


No

Global Aribute 20

GLOBAL_ ATTRIBUTE20


No

Global Aribute 3

GLOBAL_ ATTRIBUTE3


No

Global Aribute 4

GLOBAL_ ATTRIBUTE4


No

Global Aribute 5

GLOBAL_ ATTRIBUTE5


No

Global Aribute 6

GLOBAL_ ATTRIBUTE6


No

Global Aribute 7

GLOBAL_ ATTRIBUTE7


No

Global Aribute 8

GLOBAL_ ATTRIBUTE8


No

Global Aribute 9

GLOBAL_ ATTRIBUTE9


No



130


Goods Received

GOODS_ RECEIVED_DATE

Date when goods on theinvoice were received.

No

Intercompany invoice

INTERCOMPANY_ FLAG

Intercompany indicator addedto incorporate FUN team'sintercompany feature.

No

Amount

INVOICE_AMOUNT

Invoice amount in transactioncurrency.

No

Invoice Currency


Currency code used on theinvoice.

No

Date

INVOICE_DATE

Date when an event will occuror occurred.

No

Invoice ID

INVOICE_ID

Unique invoice identier.

No

Number

INVOICE_NUM

Unique number for supplierinvoice.

No

Invoice Received

INVOICE_ RECEIVED_DATE

Date when the invoice wasreceived. This is used tocalculate when the invoice isdue.

No

Type

INVOICE_ TYPE_LOOKUP_CODE

Invoice category, such asstandard, credit memo, orprepayment.

No

Legal Entity

LEGAL_ ENTITY_ID

Unique identier of the legalentity.

No

Pay Group

PAY_ GROUP_LOOKUP_CODE

Groups a category ofsuppliers or invoices forsingle pay run. For example,employees, merchandise,nonmerchandise, government,domestic, and international.

No

Payment Currency

PAYMENT_ CURRENCY_CODE

Currency code of payment(must be same as INVOICE_CURRENCY_ CODE or have axed rate relationship).

No

Payment Reason

PAYMENT_ REASON_CODE

Codes provided by thegovernment or central bank

No



131


of a country. These codesprovide the payment systemor bank with additional detailsabout the reason for thepayment and are used forregulatory reporting purposes.

Payment Reason Comments

PAYMENT_ REASON_COMMENTS

Free text eld available forentering a reason for thepayment.

No

Customs Location Code

PORT_ OF_ENTRY_CODE

Code that identies thelocation or port through whichthe invoiced goods enteredthe country.

No

Requester

REQUESTER_ID

Requester of invoice is usedby the Invoice ApprovalWorkow process to generatethe list of approvers.

No

Routing Aribute 2

ROUTING_ ATTRIBUTE2

Captures additional aributesinformation that may havebeen used for routingpayables invoice images.

No

Routing Aribute 3

ROUTING_ ATTRIBUTE3


No

Routing Aribute 4

ROUTING_ ATTRIBUTE4


No

Selement Priority


The priority that the nancialinstitution or payment systemshould sele payment forthis document. The availablevalues for this column comefrom the FND lookup IBY_SETTLEMENT_ PRIORITY.

No

Supplier Tax InvoiceConversion Rate

SUPPLIER_ TAX_EXCHANGE_RATE

Conversion rate for taxes on asupplier invoice.

No

Supplier Tax Invoice Date

SUPPLIER_ TAX_INVOICE_DATE

Date when the suppliercharged tax, as shown on thepurchase order.

No



132


Supplier Tax Invoice Number

SUPPLIER_ TAX_ INVOICE_NUMBER

Invoice supplier tax invoicenumber.

No

Internal Sequence Number

TAX_ INVOICE_INTERNAL_SEQ

Invoice internal sequencenumber.

No

Internal Recording Date

TAX_ INVOICE_ RECORDING_DATE

Date when the invoice wasrecorded.

No

Related Invoice

TAX_ RELATED_ INVOICE_ID

Tax related to an invoice.

No

Taxation Country

TAXATION_ COUNTRY

Country in which thetransaction occurred. OracleFusion tax sets the contextof other tax drivers, such asProduct Fiscal Classicationbased on this value.

No

Terms Date

TERMS_DATE

Date used with paymentterms to calculate scheduledpayment of an invoice.

No

Payment Terms

TERMS_ID

Payment terms identier usedon the invoice.

No

Supplier Tax RegistrationNumber

THIRD_ PARTY_REGISTRATION_ ID

Third party tax registrationidentier.

No

Transaction Deadline

TRANSACTION_ DEADLINE

Number of days to perform anintra-EU transaction. Used forModelo reports for Spain.

No

Unique Remiance Identier

UNIQUE_ REMITTANCE_IDENTIFIER

Unique remiance identierby the payee.

No

Unique Remiance IdentierCheck Digit

URI_ CHECK_DIGIT

Unique remiance identiercheck digit.

No

Supplier

VENDOR_ID

Invoice supplier identier.

Yes

Supplier Site

VENDOR_SITE_ID

Physical location of thesupplier.

Yes

Voucher Number

VOUCHER_NUM

Voucher number; validated(Sequential Numberingenabled) or non-validated

No



133


(Sequential Numbering notenabled).

AP_INVOICE_LINES_ALL

Object name on the Congure Business Object Aributes page: Invoice Lines

AP_INVOICE_LINES_ALL contains records for invoice lines entered manually, generated automatically or importedfrom the Open Interface. An invoice can have one or more invoice lines. An invoice line can have one or more invoicedistributions. An invoice line represents goods (direct or indirect materials), service or services, and either associatedtax, freight, or miscellaneous charges invoiced from a supplier. AP_INVOICE_LINES_ALL_ is the audit table forAP_INVOICE_LINES_ALL. The following table shows the elds that you can enable for auditing.


Overlay Account Segment

ACCOUNT_ SEGMENT

Account segment value foroverlay in generation ofaccounting exeld duringdistribution generation

No

Accounting Date

ACCOUNTING_ DATE

Accounting date for invoiceline. Used for defaulting todistributions

No

Amount

AMOUNT

Line amount in invoicecurrency

No

Assessable Value

ASSESSABLE_ VALUE

User-enterable amount to beused as taxable basis.

No

Asset Book


Asset Book. Defaults to thedistributions candidate fortransfer to Oracle Assets

No

Asset Category

ASSET_ CATEGORY_ID

Asset Category. Defaults tothe distributions candidate fortransfer to Oracle Assets

No

Track as Asset


Y indicates that the itemshould be treated as an asset

No

Aribute Category

ATTRIBUTE_ CATEGORY


No



134


Aribute 1

ATTRIBUTE1


No

Aribute 10

ATTRIBUTE10


No

Aribute 11

ATTRIBUTE11


No

Aribute 12

ATTRIBUTE12


No

Aribute 13

ATTRIBUTE13


No

Aribute 14

ATTRIBUTE14


No

Aribute 15

ATTRIBUTE15


No

Aribute 2

ATTRIBUTE2


No

Aribute 3

ATTRIBUTE3


No

Aribute 4

ATTRIBUTE4


No

Aribute 5

ATTRIBUTE5


No

Aribute 6

ATTRIBUTE6


No



135


Aribute 7

ATTRIBUTE7


No

Aribute 8

ATTRIBUTE8


No

Aribute 9

ATTRIBUTE9


No

Withholding

AWT_GROUP_ID

Withholding tax groupidentier

No

Overlay Primary BalancingSegment

BALANCING_ SEGMENT

Balancing segment valuefor overlay in generation ofaccounting exeld duringdistribution generation

No

Budget Date

BUDGET_DATE


No

Tax Control Amount

CONTROL_AMOUNT

Optional, user-enterable valueto ensure that the calculatedtax will be the same as on thephysical document.

No

Corrected Invoice Line

CORRECTED_ LINE_NUMBER

Invoice line number for invoiceline corrected via current line.For price, quantity, or invoiceline corrections.

No

Overlay Cost Center Segment

COST_ CENTER_ SEGMENT

Cost Center segment valuefor overlay in generation ofaccounting exeld duringdistribution generation

No



Accrual account that's initiallydebited for deferred expenses.

No



The end date of the deferredexpense period

No



The start date of the deferredexpense period

No



136



DEFAULT_ DIST_CCID

Account to be used forautomatic generation of asingle distribution

No

Description

DESCRIPTION

Description of the invoice line.

No

Distribution Set

DISTRIBUTION_ SET_ID

Distribution set identier tobe used in the generation ofdistributions for a line

No

Location of Final Discharge

FINAL_ DISCHARGE_LOCATION_ID

Final discharge locationidentier.

No

Final Match

FINAL_ MATCH_FLAG

Indicates if an invoice is thelast one being matched to aPO, so that the PO is no longeravailable for matching.

No

Fiscal Charge Type

FISCAL_ CHARGE_TYPE

Tax driver. Subclassicationfor invoice line type of Freightor Miscellaneous. Validvalues are from lookup ZX_CHARGE_TYPE.

No




No

Global Aribute 1

GLOBAL_ ATTRIBUTE1


No

Global Aribute 10

GLOBAL_ ATTRIBUTE10


No

Global Aribute 11

GLOBAL_ ATTRIBUTE11


No

Global Aribute 12

GLOBAL_ ATTRIBUTE12


No

Global Aribute 13

GLOBAL_ ATTRIBUTE13


No



137


Global Aribute 14

GLOBAL_ ATTRIBUTE14


No

Global Aribute 15

GLOBAL_ ATTRIBUTE15


No

Global Aribute 16

GLOBAL_ ATTRIBUTE16


No

Global Aribute 17

GLOBAL_ ATTRIBUTE17


No

Global Aribute 18

GLOBAL_ ATTRIBUTE18


No

Global Aribute 19

GLOBAL_ ATTRIBUTE19


No

Global Aribute 2

GLOBAL_ ATTRIBUTE2


No

Global Aribute 20

GLOBAL_ ATTRIBUTE20


No

Global Aribute 3

GLOBAL_ ATTRIBUTE3


No

Global Aribute 4

GLOBAL_ ATTRIBUTE4


No

Global Aribute 5

GLOBAL_ ATTRIBUTE5


No

Global Aribute 6

GLOBAL_ ATTRIBUTE6


No



138


Global Aribute 7

GLOBAL_ ATTRIBUTE7


No

Global Aribute 8

GLOBAL_ ATTRIBUTE8


No

Global Aribute 9

GLOBAL_ ATTRIBUTE9


No

Income Tax Region

INCOME_ TAX_REGION

Reporting region for invoiceline for 1099 supplier. Defaultsdown to distributions

No

Intended Use

INTENDED_ USE_ CLASSIF_ID

Tax Driver: Intended useidentier.

No

Inventory Item

INVENTORY_ ITEM_ID

Inventory item identier.Validated againstEGP_ SYSTEM_ ITEMS.INVENTORYITEMID

No

Invoice Id

INVOICE_ID


No

Landed Cost Enabled

LCM_ ENABLED_FLAG

Indicates whether invoice lineis enabled for landed costmanagement.

No

Line Type


Type of invoice line. Validvalues from INVOICE LINETYPE lookup codes.

No

Manufacturer

MANUFACTURER

Manufacturer of an asset oritem.

No

Model Number

MODEL_NUMBER

Model number of the invoiceline item.

No

Overlay DistributionCombination

OVERLAY_ DIST_CODE_CONCAT

Concatenated segmentsfor overlay in generation ofaccounting exeld duringdistribution generation

No

Project Billable

PJC_ BILLABLE_FLAG

Option that indicates ifa project related item is

No



139


available to be billed tocustomers.

Project Capitalizable


Option that indicates if aproject related item is eligiblefor capitalization.

No

Project Contract Number

PJC_ CONTRACT_ID

Contract Identied. Used whenOracle Contract Billing orOracle Grants Accounting isinstalled.

No

Expenditure Item Date


Date on which a projectrelated transaction is incurred.

No

Expenditure Item Type


Identier of the expenditureused to build the transactiondescriptive exeld forproject related transactiondistributions.

No



Organization identier usedto build the transactiondescriptive exeld forproject related transactiondistributions.

No

Project Number

PJC_PROJECT_ID

Identier of the project usedto build the transactiondescriptive exeld forproject related transactiondistributions.

No

Task Number

PJC_TASK_ID

Identier of the task usedto build the transactiondescriptive exeld forproject related transactiondistributions.

No




No




No




No



140





No




No




No




No




No




No




No

Project Work Type

PJC_ WORK_TYPE_ID

Identier for project relatedclassication of the workedperformed.

No

Product Fiscal Classication

PROD_ FC_CATEG_ID

Tax Driver: Product scalclassication identier.

No

Product Category

PRODUCT_ CATEGORY

Identies the taxable natureof a non-inventory based itemfor tax determination or taxreporting.

No

Product Type

PRODUCT_TYPE

Tax Driver: Type of product.Possible values are: Goods,Service. This value will defaultfrom Inventory Item aributes.Otherwise value will beentered by user.

No

Prorate Across All Items

PRORATE_ ACROSS_ALL_ITEMS

A value of Y indicates that theFreight or Miscellaneous typeline should be prorated acrossall Item type lines

No

Quantity

QUANTITY_ INVOICED

Quantity invoiced. Quantityof items for matched invoice

No



141


lines, price corrections,quantity corrections orunmatched invoice lines

Requester

REQUESTER_ID

The name of the personwho the requested items areintended for.

No

Serial Number

SERIAL_NUMBER

Number indicating place in aseries, used for identication.

No

Ship-from Location

SHIP_ FROM_ LOCATION_ID

Ship-from location identier.

No

Ship-to Location

SHIP_ TO_ CUST_LOCATION_ID

Location where the suppliershould ship the goods.

No

Ship-to Location

SHIP_ TO_ LOCATION_ID

Tax Driver: Ship to location ID.Value entered by user only ifline isn't PO matched.

No

Tax Classication

TAX_ CLASSIFICATION_ CODE

Tax classication code used byProcure To Pay products.

No

Transaction BusinessCategory

TRX_ BUSINESS_ CATEGORY

Tax Driver: Transactionscategory assigned by user.

No

Income Tax Type

TYPE_1099

Indicates the category of thewithholding tax rates.

No

UOM

UNIT_ MEAS_ LOOKUP_CODE

Unit of measure forQUANTITY_ INVOICED.Validated against INV_UNITS_ OF_ MEASURE.UNIT_OF_MEASURE

No

Unit Price

UNIT_PRICE

Price charged per unit of agood or service.

No

User-Dened FiscalClassication

USER_ DEFINED_ FISC_CLASS

Tax Driver: FiscalClassication.

No

AP_INVOICE_DISTRIBUTIONS_ALL

Object name on the Congure Business Object Aributes page: Invoice Distributions



142

AP_INVOICE_DISTRIBUTIONS_ALL holds the distribution information that's manually entered or system-generated. There's one row for each invoice distribution. A distribution must be associated with an invoiceline. An invoice line can have multiple distributions. AP_INVOICE_DISTRIBUTIONS_ALL_ is the audit table forAP_INVOICE_DISTRIBUTIONS_ALL. The following table shows the elds that you can enable for auditing.


Accounting Date

ACCOUNTING_ DATE

Accounting date for invoiceline. Used for defaulting todistributions

No

Amount

AMOUNT

Line amount in invoicecurrency

No

Asset Book


Asset Book. Defaults to thedistributions candidate fortransfer to Oracle Assets

No

Track as Asset


Y indicates that the itemshould be treated as an asset

No

Aribute Category

ATTRIBUTE_ CATEGORY


No

Aribute 1

ATTRIBUTE1


No

Aribute 10

ATTRIBUTE10


No

Aribute 11

ATTRIBUTE11


No

Aribute 12

ATTRIBUTE12


No

Aribute 13

ATTRIBUTE13


No

Aribute 14

ATTRIBUTE14


No



143


Aribute 15

ATTRIBUTE15


No

Aribute 2

ATTRIBUTE2


No

Aribute 3

ATTRIBUTE3


No

Aribute 4

ATTRIBUTE4


No

Aribute 5

ATTRIBUTE5


No

Aribute 6

ATTRIBUTE6


No

Aribute 7

ATTRIBUTE7


No

Aribute 8

ATTRIBUTE8


No

Aribute 9

ATTRIBUTE9


No

Budget Date

BUDGET_DATE


No



Accrual account that's initiallydebited for deferred expenses.

No



Deferred accounting end date.

No



144




Deferred accounting startdate.

No

Description

DESCRIPTION

Statement that describes thedistribution.

No



Accounting Flexeld identierfor account associated with adistribution

No




No

Global Aribute 1

GLOBAL_ ATTRIBUTE1


No

Global Aribute 10

GLOBAL_ ATTRIBUTE10


No

Global Aribute 11

GLOBAL_ ATTRIBUTE11


No

Global Aribute 12

GLOBAL_ ATTRIBUTE12


No

Global Aribute 13

GLOBAL_ ATTRIBUTE13


No

Global Aribute 14

GLOBAL_ ATTRIBUTE14


No

Global Aribute 15

GLOBAL_ ATTRIBUTE15


No

Global Aribute 16

GLOBAL_ ATTRIBUTE16


No



145


Global Aribute 17

GLOBAL_ ATTRIBUTE17


No

Global Aribute 18

GLOBAL_ ATTRIBUTE18


No

Global Aribute 19

GLOBAL_ ATTRIBUTE19


No

Global Aribute 2

GLOBAL_ ATTRIBUTE2


No

Global Aribute 20

GLOBAL_ ATTRIBUTE20


No

Global Aribute 3

GLOBAL_ ATTRIBUTE3


No

Global Aribute 4

GLOBAL_ ATTRIBUTE4


No

Global Aribute 5

GLOBAL_ ATTRIBUTE5


No

Global Aribute 6

GLOBAL_ ATTRIBUTE6


No

Global Aribute 7

GLOBAL_ ATTRIBUTE7


No

Global Aribute 8

GLOBAL_ ATTRIBUTE8


No

Global Aribute 9

GLOBAL_ ATTRIBUTE9


No



146


Income Tax Region

INCOME_ TAX_REGION

Reporting region fordistribution for 1099 supplier.

No

Intended Use

INTENDED_ USE_ CLASSIF_ID

Tax Driver: Intended useidentier.

No

Distribution Line Type


Distribution type. Validatedagainst AP_ LOOKUP_ CODES.Lookup type is INVOICEDISTRIBUTION TYPE

No

Project Billable

PJC_ BILLABLE_FLAG

Option that indicates ifa project related item isavailable to be billed tocustomers.

No

Project Capitalizable


Option that indicates if aproject related item is eligiblefor capitalization.

No

Project Context Category

PJC_ CONTEXT_ CATEGORY

Segment used to identifythe descriptive exeldapplication context for projectrelated standardized codecollection.

No

Contract Number

PJC_ CONTRACT_ID

Contract Identied. Used whenOracle Contract Billing orOracle Grants Accounting isinstalled.

No

Expenditure Item Date


Date on which a projectrelated transaction is incurred.

No

Expenditure Item Type


Identier of the expenditureused to build the transactiondescriptive exeld forproject related transactiondistributions.

No



Organization identier usedto build the transactiondescriptive exeld forproject related transactiondistributions.

No

Project Number

PJC_PROJECT_ID

Identier of the project usedto build the transactiondescriptive exeld for

No



147


project related transactiondistributions.

Task Number

PJC_TASK_ID

Identier of the task usedto build the transactiondescriptive exeld forproject related transactiondistributions.

No




No




No




No




No




No




No




No




No




No




No

Work Type

PJC_ WORK_TYPE_ID

Identier for project relatedclassication of the workedperformed.

No

Invoiced Quantity

QUANTITY_ INVOICED

Quantity billed for purchaseorder or receipt matchedinvoice distributions.

No



148


Statistical Quantity

STAT_AMOUNT

Amount associated with adistribution for measuringstatistical quantities.

No

Income Tax Type

TYPE_1099

Payments of type 1099 madeto a supplier. A 1099 suppliermay receive payments ofmore than one type.

No

AP_PAYMENT_SCHEDULES_ALL

Object name on the Congure Business Object Aributes page: Invoice Installments

AP_PAYMENT_SCHEDULES_ALL contains information about installments for an invoice. Your Oracle Payablesapplication uses this information to determine when to make payments on an invoice and how much to pay.AP_PAYMENT_SCHEDULES_ALL_ is the audit table for AP_PAYMENT_SCHEDULES_ALL. The following table shows theelds that you can enable for auditing.


Aribute Category

ATTRIBUTE_ CATEGORY


No

Aribute 1

ATTRIBUTE1


No

Aribute 10

ATTRIBUTE10


No

Aribute 11

ATTRIBUTE11


No

Aribute 12

ATTRIBUTE12


No

Aribute 13

ATTRIBUTE13


No



149


Aribute 14

ATTRIBUTE14


No

Aribute 15

ATTRIBUTE15


No

Aribute 2

ATTRIBUTE2


No

Aribute 3

ATTRIBUTE3


No

Aribute 4

ATTRIBUTE4


No

Aribute 5

ATTRIBUTE5


No

Aribute 6

ATTRIBUTE6


No

Aribute 7

ATTRIBUTE7


No

Aribute 8

ATTRIBUTE8


No

Aribute 9

ATTRIBUTE9


No

First Discount Amount

DISCOUNT_ AMOUNT_AVAILABLE

Discount amount available atrst discount date.

No

First Discount Date

DISCOUNT_DATE

Date rst discount is available.

No



150


Due Date

DUE_DATE

Date when the invoiceor installment is due forpayment.

No

Bank Account

EXTERNAL_ BANK_ACCOUNT_ID

External bank accountidentier.

No




No



Segment of the globaldescriptive exeld used tohold user-dened informationon invoice installments.

No




No




No




No




No




No




No



Segment of the globaldescriptive exeld used to

No



151


hold user-dened informationon invoice installments.




No




No

Global Aribute 1

GLOBAL_ ATTRIBUTE1


No

Global Aribute 10

GLOBAL_ ATTRIBUTE10


No

Global Aribute 11

GLOBAL_ ATTRIBUTE11


No

Global Aribute 12

GLOBAL_ ATTRIBUTE12


No

Global Aribute 13

GLOBAL_ ATTRIBUTE13


No

Global Aribute 14

GLOBAL_ ATTRIBUTE14


No

Global Aribute 15

GLOBAL_ ATTRIBUTE15


No

Global Aribute 16

GLOBAL_ ATTRIBUTE16


No

Global Aribute 17

GLOBAL_ ATTRIBUTE17


No



152


Global Aribute 18

GLOBAL_ ATTRIBUTE18


No

Global Aribute 19

GLOBAL_ ATTRIBUTE19


No

Global Aribute 2

GLOBAL_ ATTRIBUTE2


No

Global Aribute 20

GLOBAL_ ATTRIBUTE20


No

Global Aribute 3

GLOBAL_ ATTRIBUTE3


No

Global Aribute 4

GLOBAL_ ATTRIBUTE4


No

Global Aribute 5

GLOBAL_ ATTRIBUTE5


No

Global Aribute 6

GLOBAL_ ATTRIBUTE6


No

Global Aribute 7

GLOBAL_ ATTRIBUTE7


No

Global Aribute 8

GLOBAL_ ATTRIBUTE8


No

Global Aribute 9

GLOBAL_ ATTRIBUTE9


No

Gross Amount

GROSS_AMOUNT

Gross amount due for ascheduled payment.

No



153


On Hold

HOLD_FLAG

Indicates if scheduledpayment is on hold (Y or N).

No

Hold Reason

IBY_ HOLD_REASON

An explanation or justicationthat explains the reason forperforming actions, such ascancellation, apply hold, orclose out.

No

Invoice Id

INVOICE_ID


No

Payment Method


Indicates the paymentmethod, such as check, cash,or credit.

No

Payment Priority

PAYMENT_ PRIORITY

Number representingpayment priority of ascheduled payment (1 to 99).

No

Remit-to Address Name

REMIT_ TO_ ADDRESS_NAME

Remit-to address wherepayment should be sent.

No

Remit-to Supplier

REMIT_ TO_ SUPPLIER_NAME

Third party supplier.

No

Remiance Message 1


Remiance message for use inpayment processing.

No

Remiance Message 2



No

Remiance Message 3



No

Second Discount Amount

SECOND_ DISC_AMT_AVAILABLE

Discount amount available atsecond discount date.

No

Second Discount Date

SECOND_ DISCOUNT_DATE

Date second discount isavailable.

No

Third Discount Amount

THIRD_ DISC_AMT_AVAILABLE

Discount amount available atthird discount date.

No

Third Discount Date

THIRD_ DISCOUNT_DATE

Date third discount isavailable.

No



154


AP_PAYMENT_TEMPLATES

Object name on the Congure Business Object Aributes page: Payment Process Request Templates

The AP_PAYMENT_TEMPLATES contains the user dened Payment Process Request Templates.AP_PAYMENT_TEMPLATES_ is the audit table for AP_PAYMENT_TEMPLATES. The following table shows the elds thatyou can enable for auditing.


Template ID

TEMPLATE_ID

System generated primary keyfor payment template.

No

Name

TEMPLATE_NAME

Payment Process RequestTemplate Name

No

Type

TEMPLATE_TYPE

Payment Process RequestTemplate Type. Values,from the lookup PAYMENT_TEMPLATE_TYPE

No

Description

DESCRIPTION

Payment Process RequestTemplate Description

No

Inactive Date

INACTIVE_DATE

End Date for the PaymentProcess Request Template

No

Pay from Days

ADDL_ PAY_FROM_DAYS

Number of pay from daysdened in the paymenttemplate. The value canbe either zero or a positivenumber.

No

Pay Through Days

ADDL_ PAY_THRU_DAYS

End date in a date range thatindicates the date until whenthe invoices are selected.

No

To Payment Priority

HI_ PAYMENT_ PRIORITY

Highest payment priority ofthe documents to select

No

From Payment Priority

LOW_ PAYMENT_ PRIORITY

Lowest payment priority of thedocuments to select

No



155


Date Basis

PAY_ ONLY_WHEN_DUE_FLAG

Option that indicates ifdocuments will be selected bytheir due date only (Y or N)

No

Include Zero Amount Invoices

ZERO_ INV_ ALLOWED_FLAG

Option indicating whetherscheduled payments withzero amount remaining will beselected during a pay run

No

Supplier Type

VENDOR_ TYPE_LOOKUP_CODE

Supplier Type. Based on POLookup Type VENDOR TYPES

No

Supplier

VENDOR_ID

Unique supplier identier fromthe supplier tables.

No

Party

PARTY_ID

Party identier of the paymenttemplate.

No

Payment Method


Indicates the paymentmethods, such as check, cash,or credit.

No

Invoice Conversion Rate Type

INV_ EXCHANGE_ RATE_TYPE

Type of conversion ratebetween the payment andyour ledger currency.

No

Pay Group Selection Criteria

PAY_ GROUP_OPTION

Pay Group Options, All andSpecify

No

Currency Selection Criteria

CURRENCY_ GROUP_OPTION

Currency Options, All andSpecify

No

Legal Entity Selection Criteria

LE_ GROUP_OPTION

Legal Entity Options, All andSpecify

No

Business Unit SelectionCriteria

OU_ GROUP_OPTION

Business Unit Options, All andSpecify

No

Payment Date

PAYMENT_ DATE_OPTION

Payment Date Options, Sameas the Request Date, ExtraDays

No

Additional Payment Days

ADDL_ PAYMENT_DAYS

Extra payment days in thepayment template.

No



156


Disbursement Bank Account

BANK_ ACCOUNT_ID

The Internal bank accountidentier

No

Bank Charge Bearer Override

BANK_ CHARGE_BEARER

Bearer of bank charge cost.Bank charge bearers aredened as the lookup IBY_BANK_ CHARGE_BEARER

No

Selement Priority Override


Overrides the invoice valuefor Oracle Payments' bankcharges feature.

No

Starting Voucher Number

FIRST_ VOUCHER_ NUMBER

First available voucher numberin document sequence forpayment batch documentcategory

No

Transfer Priority

TRANSFER_ PRIORITY

Transfer priority dened inpayment template. This can beexpress, normal, and any.

No

Payment Conversion RateType

PAYMENT_ EXCHANGE_RATE_TYPE

Exchange rate type for aforeign currency payment

No

Payment Process Prole

PAYMENT_ PROFILE_ID

Payment process proleidentier

No

Apply credits up to zeroamount payment

ZERO_ AMOUNTS_ ALLOWED

Option indicating whetherzero payments allowed in run.Helps in Maximizing credits

No

Review installments

PAYABLES_ REVIEW_SETTINGS

Stop Process for Review AfterInvoice Selection

No

Calculate Withholding andInterest

CALC_ AWT_INT_FLAG

Option to indicate CalculatePayment Withholding andInterest During ScheduledPayment Selection

No

Review proposed payments

PAYMENTS_ REVIEW_SETTINGS

If this check box is selected,the Build Payments programruns to group the invoicesinto payments and the payrun pauses after paymentshave been built to allowyou to review the proposedpayments.

No



157


Create payment lesimmediately

CREATE_ INSTRS_FLAG

Payment Instruction CreationProgram. This seing requiresthe user to select a paymentprocess prole. This seingwill also ensure that paymentsfrom this payment processrequest aren't combinedwith payments from otherpayment process requestswhen the application createsthe payment instructions

No

Document

DOCUMENT_ REJECTION_LEVEL_CODE

Indicates the validation failurehandling option for payabledocuments. Possible valuesare: Reject All Documents forPayee, Reject All Documentsin Request, Stop Process forReview

No

Payment

PAYMENT_ REJECTION_LEVEL_CODE

Document used to pay aninvoice.

No

Aribute Category

ATTRIBUTE_ CATEGORY


No

Aribute 1

ATTRIBUTE1


No

Aribute 2

ATTRIBUTE2


No

Aribute 3

ATTRIBUTE3


No

Aribute 4

ATTRIBUTE4


No

Aribute 5

ATTRIBUTE5


No

Aribute 6

ATTRIBUTE6


No



158


Aribute 7

ATTRIBUTE7


No

Aribute 8

ATTRIBUTE8


No

Aribute 9

ATTRIBUTE9


No

Aribute 10

ATTRIBUTE10


No

Aribute 11

ATTRIBUTE11


No

Aribute 12

ATTRIBUTE12


No

Aribute 13

ATTRIBUTE13


No

Aribute 14

ATTRIBUTE14


No

Aribute 15

ATTRIBUTE15


No

Payment Document

PAYMENT_ DOCUMENT_ID

A set of documents, such ascheck stock, on which checksand promissory notes can beprinted or wrien.

No

Cross-Currency Rate Type

X_ CURR_ RATE_TYPE

The conversion rate typeused to convert the invoicecurrency to payment currency.

No



159


First Approver

FIRST_ APPROVER_ID

First approver identier forpayment process requeststhat the payments approvalworkow uses to generate thelist of approvers.

No

Source Selection Criteria

SOURCE_ GROUP_OPTION

Options on how to selectinvoices for payment witheither all or specic values.

No

Select Early Payment Invoices

ACCELERATED_INVOICES_CODE

Dynamic discount invoicecode. Values are from lookupACCELERATED_ INVOICES.Possible values are INCLUDE,EXCLUDE and EXCLUSIVE.

No

AP_OU_GROUP

Object name on the Congure Business Object Aributes page: Business Units

The AP_OU_GROUP contains the user selected values for the operating units for the Payment Process RequestTemplate or the Payment Process Request. AP_OU_GROUP_ is the audit table for AP_OU_GROUP. The following tableshows the elds that you can enable for auditing.


Business Unit

ORG_ID


No

Business Unit Group ID

OU_GROUP_ID

Business unit group uniqueidentier.

No

AP_CURRENCY_GROUP

Object name on the Congure Business Object Aributes page: Currencies

The AP_CURRENCY_GROUP contains the user selected values for the payment currencies for the PaymentProcess Request Template or the Payment Process Request. AP_CURRENCY_GROUP_ is the audit table forAP_CURRENCY_GROUP. The following table shows the elds that you can enable for auditing.


Currency

CURRENCY_CODE

Currency code of invoices thatare selected for a paymenttemplate.

No



160


Currency Group ID

CURRENCY_ GROUP_ID

Unique identier for everycurrency selected in thepayment template.

No

AP_LE_GROUP

Object name on the Congure Business Object Aributes page: Legal Entities

The AP_LE_GROUP contains the user selected values for the legal entities for the Payment Process Request Template orthe Payment Process Request. AP_LE_GROUP_ is the audit table for AP_LE_GROUP. The following table shows the eldsthat you can enable for auditing.


Legal Entity Group ID

LE_GROUP_ID

Legal entity group uniqueidentier.

No

Legal Entity

LEGAL_ ENTITY_ID

Legal entity unique identier.

No

AP_PAY_GROUP

Object name on the Congure Business Object Aributes page: Pay Groups

The AP_PAY_GROUP contains the user selected values for the pay groups for the Payment Process Request Templateor the Payment Process Request. AP_PAY_GROUP_ is the audit table for AP_PAY_GROUP. The following table showsthe elds that you can enable for auditing.


Pay Group ID

PAY_GROUP_ID

Pay group unique identier.A pay group is a method forcategorizing suppliers forpayment processing.

No

Pay Group

VENDOR_ PAY_GROUP

Supplier pay group used in theselection criteria for invoicesto be paid.

No

AP_SOURCE_GROUP



161

The AP_SOURCE_GROUP table stores the source group selection criteria information for the Payment Process Requesttemplate. AP_SOURCE_GROUP_ is the audit table for AP_SOURCE_GROUP. The following table shows the elds that youcan enable for auditing.


Source Group ID

SOURCE_ GROUP_ID

Unique identier for thesource group.

No

Sources

INVOICE_ SOURCE_CODE

Source for creation of invoiceused as the selection criteriafor the invoices to be paid.Values are from SOURCElookup type.

No

AP_DISCOUNT_OFFERS_B

Object name on the Congure Business Object Aributes page: Early Payment Oers

The AP_DISCOUNT_OFFERS_B table stores discount oers. AP_DISCOUNT_OFFERS_B_ is the audit table forAP_DISCOUNT_OFFERS_B. The following table shows the elds that you can enable for auditing.


Rate

DISCOUNT_RATE

Active discount percent ratefor the dynamic discountcalculation.

No

Oer Start Date

START_ DATE_ACTIVE

Date at the start of the oerperiod range.

No

Expiration Date

END_ DATE_ACTIVE

Date at the end of the oerperiod range.

No

Initiated

ENABLED_FLAG

Indicates the record is activeand in use.

No

Oer Description

DESCRIPTION

Description of the discountoer.

No

AP_DISCOUNT_OFFERS_ASSIGN

Object name on the Congure Business Object Aributes page: Early Payment Oer Assignments



162

The AP_DISCOUNT_OFFERS_ASSIGN table stores information about the supplier assigned to the discount oer.AP_DISCOUNT_OFFERS_ASSIGN_ is the audit table for AP_DISCOUNT_OFFERS_ASSIGN. The following table shows theelds that you can enable for auditing.


Rate

DISCOUNT_RATE

Active discount percent ratefor the dynamic discountcalculation.

Yes

Supplier

VENDOR_ID

Unique identier of thesupplier.

No

Supplier Site

VENDOR_SITE_ID

Supplier site unique identier.

Yes

Business Unit

BILL_TO_BU_ID

Bill-to business unit assignedto the supplier site.

No

Oer Start Date

START_ DATE_ACTIVE

Date at the start of the oerperiod range.

No

Expiration Date

END_ DATE_ACTIVE

Date at the end of the oerperiod range.

Yes

Comments

COMMENTS

Manually entered commentsfor an assignment.

Yes

Email

EMAIL_ADDRESS

Supplier contact emailaddress.

No

Initiated

ENABLED_FLAG

Indicates the record is activeand in use.

No

Related Topics

• Audit Conguration for Business Object Aributes

• Audit Policies

FAQs for Payables Conguration

http://www.oracle.com/pls/topic/lookup?ctx=fa20a&id=9284AC376010D23DE040D30A6881531D

http://www.oracle.com/pls/topic/lookup?ctx=fa20a&id=D02C82F595D5648DE040D30A688140EF



163

What's a Payables calendar?Use Oracle Fusion Payables calendars for automatic withholding tax, payment terms, key indicator reporting, andrecurring invoices. You create Payables calendars on the Manage Payables Calendars page.

Periods in Payables calendars are separate from the accounting periods that you dene on the Manage AccountingCalendars page.



164


Chapter 4Payables Tax and Withholding

165

4 Payables Tax and Withholding

Guidelines for Reporting Limit Methods for Income TaxRegionsThe reporting limit is the minimum amount used to determine whether to report on payments to a supplier. If you'redoing business within the United States (US), refer to federal or state tax publications for information on US 1099reporting requirements.

Select from one the following methods to compare payments to the reporting limit amount:

• Same as federal

• Compare individually

• Compare sum

Note: If you don't specify a reporting limit, the limit is assumed to be zero.

Same as FederalThis seing uses the federal reporting limit, which is predened in the application as 600 USD.

Compare IndividuallyThis seing compares the reporting limit to the sum of the payments for each US 1099 miscellaneous income tax type.

For example, the reporting limit for region X is 600 USD. You make two 400 USD payments to a supplier in region Xand classify each payment with a dierent US 1099 miscellaneous type. The supplier isn't reported to the region taxauthority because the total for each tax type is less than the reporting limit of 600 USD. In this case, the supplier isreported only to the federal tax authorities.

Compare SumThis seing compares the reporting limit to the sum of the payments for all US 1099 miscellaneous income tax types.

For example, the reporting limit for region X is 600 USD. You make two 400 USD payments to a supplier and classifyeach payment with a dierent 1099 miscellaneous income tax type. The supplier is reported to the region tax authoritybecause the sum of the payments, which is 800 USD, exceeds the reporting limit. In this case, the supplier is reported toboth federal and region tax authorities.

Reporting EntitiesA reporting entity is any person or organization with a unique tax identication number. Oracle Fusion Payables usesreporting entities for United States (US) 1099 reporting.



166

Primary Balancing Segment ValuesFor each reporting entity of an invoice business unit, assign one or more primary balancing segment values. Typicallyprimary balancing segment values represent dierent legal entities.

For example, you dene a reporting entity called Headquarters, which comprises companies 1, 2, and 3. Each companyis represented by a primary balancing segment value. When you submit a US 1099 report, you specify Headquartersfor the reporting entity parameter. The report accumulates payments for companies 1, 2, and 3, and sums up the paidinvoice distributions that have the companies balancing segment values.

Note: Primary balancing segment values must be unique across reporting entities.

ReportsYou can submit the following US 1099 reports for a specic reporting entity:

• US 1096 Report

• US 1099 Report

• US 1099 Invoice Exceptions Report

• US 1099 Supplier Exceptions Report

• US 1099 Payments Report

• US 1099 Electronic Media Report

Dene Payables Setup for Withholding TaxYou may be required to withhold tax from your supplier invoices and pay it to a tax authority on behalf of the supplier.Set withholding tax options on the Manage Tax Reporting and Withholding Tax Options page and on the supplier setup.

The withheld amount is calculated according to how you set the Calculation Point option. If you apply withholding taxat invoice validation, then the withheld amount is based on the invoice amount. However, if you apply withholding tax atpayment, then the withheld amount is based on the payment amount.

Review withheld amounts online or run the standard reports.

Seing Up Automatic Withholding TaxTo automatically withhold tax, perform the following steps:

1. Enable the Apply Withholding option and set the other withholding tax options in the Withholding TaxOptions section on the Manage Tax Reporting and Withholding Tax Options page.

2. Create each tax authority as a supplier with a supplier type of Tax Authority.3. Create withholding tax codes.4. Create withholding tax classications.5. Specify withholding tax details for suppliers.6. Dene withholding tax certicates to handle rate exceptions.



167

Withholding Tax AutomaticallyTo perform automatic withholding, you assign a withholding tax classication to an invoice line. You can accept thedefault withholding tax classication or select another classication. When applying withholding tax, Oracle Fusion Taxcreates one or more withholding tax type invoice lines, updates the withheld amount on the invoice, and updates theunpaid amount on the installment.

For example, if an invoice for 100 USD has withholding tax of 20 USD, Oracle Fusion Tax creates a withholding tax typeinvoice line for -20 USD. The withheld amount is -20 USD, and the unpaid amount on the installment is 80 USD.

Caution:• Automatic withholding tax is calculated only once.• Automatic withholding tax isn't calculated:

◦ For a specic tax after you enter a manual withholding line for that tax.

◦ If you pay an invoice with a manual payment or a refund, and the option to apply withholding is atpayment time.

Creating Withholding InvoicesAfter you deduct withholding tax from an invoice, you can optionally create invoices to remit the withheld tax to a taxauthority. Oracle Fusion Tax can automatically create withholding tax invoices, or you can perform this task manually.To create withholding tax invoices automatically, set the Tax Invoice Creation Point option to specify whether to createwithholding invoices at invoice validation or payment.

Reporting on Withheld TaxYou can run the following reports to satisfy tax authority, supplier, and management reporting requirements:

• Withholding Tax Reports by Invoice, Payment, and Supplier

• Payables Withholding Tax by Tax Authority Report

• Payables Withholding Tax Leer

Related Topics

• Withholding Tax Options

Withholding Tax CodesA withholding tax code is the name for a withholding tax rate. Withholding tax codes use Oracle Fusion Tax's regime torate setup structure.

Regime to rates include:

• Tax regime: The set of tax rules that determines the treatment of one or more taxes administered by a taxauthority. The common tax regime setup is one tax regime per country per tax type. The tax requirements areadministered by a government tax authority for the entire country.

• Tax: The details for the taxes of a tax regime. Each separate tax in a tax regime includes records for the taxstatuses and tax rates that are used to calculate and report on the tax.



168

• Tax status: The taxable nature of a product or service in the context of a transaction and specic tax on thetransaction. For example, one tax can have separate tax statuses for standard, zero, exemptions, penalty, andreduced rates. You dene all applicable tax rates and their eective periods for the tax status.

• Tax rate: The rate specied for a tax status and is eective for a period of time. Set up a tax rate record withapplicable tax rate detail information per rate period. Rate periods account for changes in tax rates over time.

Creating Withholding Tax CodesEach tax code is dened within the context of a business unit, country, tax regime code, tax, and tax status code.

For a tax regime and tax, you can select an existing record or create a new record by clicking Create in the list of values.The following table describes the regime to rate options:

Option Description

Tax RegimeSelect an existing tax regime code for the country or create one from within the list of valuesoptions. To create a new tax regime record, enter the tax regime code, name, and start date.

TaxSelect an existing tax for the tax regime code or create one from within the list of valuesoptions. To create a new tax record, enter the tax, start date, tax currency, tax liability account, taxauthority, and tax authority site. For tax authority details, you must associate a supplier witha type of Tax Authority to a withholding tax. You can then create withholding invoices to paytaxes you withheld from your suppliers.

Tax Status Select a tax status code from the list of:

• Exempt from tax• Tax penalty• Reduced tax rate• Standard tax rate• Zero tax rate

Tax Rate Enter a unique tax rate code and select a tax rate type of:

• Percentage• Gross amount rate schedule• Withheld amount rate schedule

Using Withholding Tax CodesTo use withholding tax codes, assign them to one or more withholding tax classications. When you dene awithholding tax code, you can enable the Create withholding tax classication option to automatically create aclassication for that tax code. To handle rate exceptions, dene withholding tax certicates for a withholding tax.



169

Withholding Tax Code Rate TypesWhen you dene a withholding tax code, specify the tax rate type to base the withholding tax calculation on apercentage or rate schedule.

The tax rate type values are:

• Percentage

• Gross amount rate schedule

• Withheld amount rate schedule

For each rate type, the same withholding tax code can have dierent rate period details based on eective periods. Forexample, the withholding tax rate is 10 percent one year and 11 percent the following year.

PercentageSelect Percentage if a at rate percentage is required rather than dierent rates for dierent amount ranges. Forexample, if withholding tax is deducted at a specied rate of 10 percent, create a percentage tax rate code with a tax rateof 10 percent.

You can use percentage rates in conjunction with tax threshold controls that are dened at the tax level. For example,withholding for a specic tax is restricted to no more than 10,000 USD for a withholding tax period.

Gross Amount Rate ScheduleSelect Gross amount rate schedule to apply dierent tax rate percentages for dierent invoice amount ranges. Youcan dene the rate schedule at the document level or period level to include all invoice amounts from a supplier for aspecied period. For example, dene a tax code that for each year withholds at a rate of 10 percent for the rst 10,000USD in invoice amounts from a supplier. Then, dene a rate of 15 percent after the rst 10,000 USD.

You can build document or period limits into the rate schedule if necessary, by dening a To amount for the highestamount range.

Withheld Amount Rate ScheduleSelect Withheld amount rate schedule to apply dierent tax rate percentages for dierent withheld amount ranges.You can dene the rate schedule at the document level or period level to include all invoice amounts from a supplier fora specied period. For example, dene a tax code that for each year withholds at a rate of 10 percent for the rst 1,000USD in withheld amounts from a supplier. Then, dene a rate of 15 percent after the rst 1,000 USD.

You can build document or period limits into the rate schedule if necessary, by dening a To amount for the highestamount range.

Related Topics

• What's a Payables calendar



170

Withholding Tax ClassicationsWithholding tax classications include one or more withholding tax codes. Dene withholding tax classications toassociate one or more withholding tax codes to a single transaction. For example, assign a withholding tax classicationto an invoice line to withhold two taxes, each tax withheld at dierent rates and remied to dierent tax authorities.

You can edit a withholding tax classication to add more tax codes if needed.

Compounding Withholding Tax CodesOptionally, tax codes can be compounded in order of precedence within a withholding tax classication. When youenter an invoice with a withholding tax classication that consists of multiple compounded tax codes, taxes arecalculated in order of precedence.

Lower precedence taxes are applied to the amount of the invoice less the previous withholding tax amounts. Thehighest precedence is 1. For example, dene a withholding tax classication with two tax codes. Tax A for 10 percent hasa precedence of 1, and tax B for 5 percent has a precedence of 2. Oracle Fusion Tax calculates the withholding tax for a100 USD invoice as follows: tax A is 10 USD, tax B is 4.50 USD (.05(100 - (100 * .10))).

If compounding details aren't entered for a withholding tax classication, the gross invoice amount is used to calculatewithholding amounts for each tax code. For example, dene a tax classication with two codes that each have a rateof 10 percent, and don't dene compounding details. On an invoice for 100 USD, two automatic withholding tax lines,each for 10 USD are generated. Two lines are generated because both automatic withholding tax codes of 10 percent areapplied to 100 USD.

Applying Withholding Tax Classications to an InvoiceFor supplier sites that use withholding tax, the withholding tax classication that you dene at the supplier siteassignment level is used to populate the default tax classication on the invoice. You can override any defaultwithholding tax classication.

Withholding Tax Certicates and ExceptionsWithholding tax certicates specify withholding tax rate exceptions that are granted by a tax authority. You can denewithholding tax rate exceptions for all invoices of a supplier site or for specic invoices of that site. A tax can have oneor more certicates.

Before dening withholding tax certicates and exceptions, you must:

• Enable the Apply Withholding option.

• Create withholding tax codes.

• Enter withholding details for suppliers.



171

CerticatesTo dene a withholding certicate, you must specify a certicate number, type, priority, and rate for a tax regime andtax.

A certicate number can be user-dened or it can be a number assigned to a certicate issued to a supplier by the taxauthority.

Oracle Fusion Payables predenes a certicate type of Standard. You can dene additional certicate types on theManage Tax Lookup Codes page.

Only one certicate can be enforced at a time. If you have one or more certicates for the same tax regime and tax andthe date ranges overlap, Oracle Fusion Tax applies the certicate with the highest priority, where 1 is the highest priority.If a certicate species that the supplier site is exempt from the tax regime and tax, then enter 0 as the tax rate.

Note: The tax rate for a withholding certicate overrides all rates for the withholding tax.

ExceptionsTo dene an exception for an invoice, specify the invoice number and rate for a tax regime and tax.

Note: The tax rate for an exception overrides all rates for the withholding tax.

FAQs for Payables Tax and Withholding

How can I set thresholds for withholding taxes?Use the Create or Edit Withholding Tax Code pages to dene withholding tax thresholds at the tax level for percentagetax rate types. You can dene thresholds based on the taxable amount or the tax amount. Base thresholds oneach specic document or for a dened period. In each case, you can specify a minimum value or maximum value.Thresholds can have dierent details based on eective periods.

For example, if a withholding tax on a document should not be deducted if it's less than 10 USD, create a document-based tax amount threshold with a minimum value of 10 USD.



172


Chapter 5Approving Invoices

173

5 Approving Invoices

How Invoices Are ApprovedYou can congure predened workows to manage invoice approvals.

When the invoice approval process starts, a workow builds the list of approvers based on the dened rules. Approvalnotications are sent to the rst set of approvers on the list. When the approvers respond, notications are sent to thenext set of approvers. This process repeats until all approvals are complete.

Note: Approvers can respond from the e-mail notication, the Worklist notications page, the Invoiceslanding page, or the Edit Invoice page.

Invoice Header ApprovalThe Approval workow can be congured at the invoice header level. When the header level approval is setup, approvalnotications are sent containing the invoice. The approvers can either approve or reject the entire invoice.

Approval FlowThis table describes the steps in the approval ow.

Step Description

Enable invoice approval Enable the Invoice Approval option on the Manage Invoice Options page to enable approvals

for a business unit. You can use the default approval conguration or you can congure therules to meet your requirements. Use the Manage Task Conguration for Financials task tonavigate to the routing rules and controls.

Enter invoices

Create invoices through import, invoice imaging, spreadsheets, or manual entry.

Submit invoice approval Initiate the approval invoice action or schedule the Initiate Invoice Approval Workow process

to run on a regular basis.

Approve invoice document

Respond to the approval notication for the invoice.

Predened RulesThe invoice approval workow includes the following predened rules:

• Invoices having amounts greater than or equal to 1000 require approval by the immediate supervisor of therequester on the invoice.

• Invoices having amounts less than 1000 are automatically approved.


Chapter 5Approving Invoices

174

Related Topics

• Overview of Approval Management

• Considerations for Approval Actions

http://www.oracle.com/pls/topic/lookup?ctx=fa20a&id=98A688C1E5209503E040D30A688132B9

http://www.oracle.com/pls/topic/lookup?ctx=fa20a&id=9E3C38FFA719C953E040D30A68817D6B


Chapter 6Conguration for Rapid Implementation

175

6 Conguration for Rapid Implementation

Overview of Invoice and Payment Conguration forRapid ImplementationThe Dene Invoicing and Payments Conguration for Rapid Implementation task list provides the setup tasks that arecritical for Oracle Fusion Payables. These tasks are either mandatory or frequently used.

Invoice and payment options are automatically created with default values when the common options for Payables andProcurement are dened for a new business unit. To change the default values, you can access the invoice and paymentoptions setups from the standard implementation template. You can also use the standard implementation template toaccess the setups that aren't listed in the rapid implementation task list.

Related Topics

• Guidelines for Common Options for Payables and Procurement


Chapter 6Conguration for Rapid Implementation

176


Chapter 7Disbursements

177

7 Disbursements

Electronic PaymentsWatch video

To pay your suppliers, you can make payments through electronic funds transfer by transmiing payment les to yourbank or payment system.

This topic includes the following tasks:

• Creating an ISO payment process prole

• Submiing a payment process request

• Reviewing selected invoices

• Reviewing proposed payments

• Transmiing payment les

• Viewing payments and invoices

Creating an ISO Payment Process ProleThe rst step is to set up a payment process prole that contains all the necessary details to manage the paymentprocess. You will create an ISO payment process prole. ISO is a global standard for nancial payment formats andmessages, which is accepted by most banks. ISO has two versions: SEPA for European countries and CGI for non-European countries.

To create an ISO payment process prole, complete these steps:

1. Sign in as a setup user.2. In the Setup and Maintenance work area, go to the following:

◦ Oering: Financials

◦ Functional Area: Payments

◦ Task: Manage Payment Process Proles

3. On the Manage Payment Process Proles page, in the Search Results section, click Add.4. On the Create Payment Process Prole page in the Name eld, enter ISO_PPP_XXX.5. In the Code eld, enter ISO_Code_XXX.

Tip: In place of XXX, enter the appropriate number.

6. In the From Date eld, accept the default seing of today's date.7. From the Payment File Format choice list, search and select the ISO20022 Common Global Implementation

Format.8. From the Processing Type choice list, select Electronic.9. From the Payment Conrmation Point choice list, select When the payment le is transmied.





178

10. Select the Usage Rules tab.11. Click the All option for Payment Methods, Disbursement Bank Accounts, Business Units, and Currencies so that

the payment process prole can be used with any payment.

Note: You can click the Specify option to limit the use of this prole to payments that havespecic payment methods, disbursement bank accounts, business units, or currencies.

12. Select the Payment System tab.

You can specify that the payment le is automatically transmied after formaing. You can also congure thepayment le transmission to allow payment le downloading to the Universal Content Management folder afterthe payment le is transmied.

13. From the Payment System choice list, select ISO20022 Payment System.14. Select the Automatically transmit payment le after formaing check box.15. In the Payment System Accounts section, for the payment system account of Seings_CGI, select

ISO_UCM_Upload from the Payment File Transmission Conguration choice list.16. For the payment system account of Seings_SEPA, enter today's date in the To Date eld.17. Select the Payment tab.

On the Payment tab, you can specify aributes for grouping invoices in the same payment if they share thesame aribute.

18. In the Document Grouping Rules section, select these check boxes: Due date, Selement priority, andDelivery channel.

19. Select the Payment File tab.

On the Payment File tab, you can specify rules for grouping payments into payment les.20. In the Overrides section, from the Service Level choice list, select the type of payment.21. From the Delivery Channel choice list, select the delivery type.22. Select the Grouping tab.

Since you're creating an ISO payment process prole, you must select transaction grouping rules onthe Grouping tab. Grouping is based on the ISO standardized method of grouping transactions in eachtransmission le.

23. In the Transaction Grouping Rules section, select these check boxes: Payment Date, Disbursement BankAccount, Service Level and Delivery Channel.

24. Select the Reporting tab.

On the Reporting tab, you can specify the timing and types of reports to generate.25. In the Payment File Register section, from the Format choice list, select Payment File Register Format with

Document Detail.26. Select the Automatically submit when payments are conrmed check box.27. In the Separate Remiance Advice section, from the Format choice list, select Separate Remiance Advice

Format.28. Select these check boxes: Automatically submit when payments are conrmed and Allow multiple copies

for payment le.29. From the Condition choice list, select All payments.30. From the Delivery Method choice list, select E-Mail.31. Click Save and Close. A Conrmation message appears.32. Click OK.33. Click Done.



179

34. Sign out.

Submiing a Payment Process RequestThe second step is to submit a payment process request. A payment process request is a grouping of documentspayable for which a source product requests payment. The payment process request will make payments of threeinvoices with dierent due dates.

To submit a payment process request, complete these steps:

1. Sign in as a transaction user.2. On the Home page, click Payables > Payments.3. On the Overview page, click the Tasks icon and then click the Submit Payment Process Request link.4. On the Submit Payment Process Request page, select the Selection Criteria tab.5. In the Name eld, enter ISO_PPRXXX.6. From the Invoice Group choice list, search and select 129Group.


7. Select the Payment and Processing Options tab.

On the Payment and Processing Options tab, you can specify payment aributes and processing options.You can select the disbursement bank account from which invoices will be paid, the payment process proleyou just created, and several processing options to stop the process for review. If the reviews are satisfactory,payment les are created immediately.

8. From the Disbursement Bank Account choice list, search and select BofA-204.

Note: Choose the BofA-204 bank account that has Account Number: 10271-17621-619.

9. From the Payment Process Prole choice list, search on ISO and select ISO_PPP Seings_CGI .10. From the Payment Conversion Rate Type choice list, select Corporate.11. In the Processing Options subsection, select these check boxes: Review installments, Review proposed

payments, and Create payment les immediately.12. In the Validation Failure Handling subsection, from the Document choice list, select Stop process for review.13. From the Payment choice list, select Stop process for review.14. Click Submit.

A Conrmation message appears with the process number.15. Click OK.16. Scroll down to the Schedule Requests section to check the status of the request.17. Click the Refresh icon until Succeeded displays in the Status column for both Initiate Payment Process Request

and Payables Selected Installments Report processes that correspond to your process ID.18. On the Overview page, click the Tasks icon.19. Click the Manage Payment Process Requests link.20. On the Manage Payment Process Requests page, enter ISO_PPRXXX in the Name eld.

Note: In place of XXX, enter the appropriate number.



180

21. Click Search.

Note: The payment process request shows a Status of Pending installment review.

22. Click the Action icon.

On the Selected tab, three invoices were selected by the payment process request. Since the selectedinstallments look ne, the process continues.

Reviewing Selected InvoicesThe third step is to review selected invoices.

To review selected invoices, complete these steps:

1. On the Review Installments page, click Submit.

A Conrmation message appears that states your process ID.2. Click OK.3. Expand the Search section.4. The Name eld contains the name of the payment process request, ISO_PPRXXX.5. Click Search.

Note: The status of the payment process request changes to Pending proposed paymentreview.


Reviewing Proposed PaymentsThe fourth step is to review proposed payments.

To review proposed payments, complete these steps:

1. On the Review Proposed Payments page, click Resume Payment Process.

A Conrmation message appears that states the process was submied and species a process ID.2. Click OK.

Note: In the Payment Summary section, two payments were created and none were rejectedor removed. Since the proposed payments are ne, you can continue.

Transmiing Payment FilesThe fth step is to transmit payment les.

To transmit payment les, complete these steps:

1. Expand the Search section.2. Click Search.



181

Note: The status of the payment process request is Payments completed. The status of thepayment le is now Transmied. The payment process request completed and the paymentles were transmied to the payment system.

3. In the Name eld, enter the payment process request name, ISO_PPR_XXX.


4. Click the payment le number.

The Payment File page appears.5. In the Payments section, click the Eye glasses icon to view the invoices.

Viewing Payments and InvoicesThe nal step is to view payments and invoices.

To view payments and invoices, complete these steps:

1. On the Manage Payment Process Requests page, click the payment le number link.2. Scroll down the Payment File page to the Payments section.

The Payments section contains two payments.3. Click the Eye Glasses icon for the $800.00 USD payment.4. On the Payment page, select the Documents Payable tab.

The two invoices within Payment XXX are visible.5. Click Done.

Check PaymentsWatch video

To pay your suppliers, you can make payments by printing checks.

This topic includes the following tasks:

• Creating the payment document

• Seing up a payment process prole

• Submiing the payment process request

• Reviewing installments and proposed payments

• Printing checks

• Recording the print status

• Reviewing a check





182

Creating the Payment DocumentTo make check payments, you must rst set up a payment document, or check stock, at the disbursement bank accountlevel.

To create a payment document at the disbursement bank account level, complete these steps:

1. Sign in as a Cash manager.2. In the Setup and Maintenance work area, go to the following:


◦ Functional Area: Cash Management and Banking

◦ Task: Manage Bank Accounts

3. On the Manage Bank Accounts page, in the Account Name eld, enter BofA-204 and click Search.

The record of the bank account appears in the Search Results section.4. Select the account and click the Edit icon.

On the Edit Bank Account page, you can view payment documents that have been previously created for thedisbursement bank account. To create a payment document, you must provide a name, select the type of paperstock, format, and specify rst and last check numbers.

5. On the Edit Bank Account page, Payment Documents section, click Create.6. In the Create Payment Document dialog box, in the Payment Document eld, enter Payments Numbered

Check Stock.7. From the Paper Stock Type choice list, select Numbered Stock.8. From the Format choice list, search and select Standard Check Format (Stub after Payment).9. In the First Available Document Number eld, enter 373001.

10. In the Last Available Document Number eld, enter 373100.11. Click OK.12. Click Save and Close.

An Information message is displayed.13. Click OK.14. Click Done.15. Click Done.16. Sign out.

Seing Up a Payment Process ProleA payment process prole is a setup that contains all the necessary details to manage the payment process. To printchecks, you must create a payment process prole with a Processing Type of Printed. You name the prole and enter acode. Then, you select the same disbursement payment le format that you used to create the payment document.

To create a payment process prole for printing checks, complete these steps:

1. Sign in as a setup user.2. In the Setup and Maintenance work area, go to the following:



◦ Task: Manage Payment Process Proles



183

3. On the Manage Payment Process Prole page in the Search results section, click the Add icon.4. On the Create Payment Process Prole page, in the Name eld, enter PPP_XXX.5. In the Code eld, enter PPP_XXX_Code.


6. In the From Date eld, accept the default seing of today's date.7. From the Payment File Format choice list, search and select Standard Check Format (Stub after Payment).8. From the Processing Type choice list, select Printed.9. For the Pay File option, accept Send to printer.

10. Select the Usage Rules tab.11. Click the All option for Payment Methods, Disbursement Bank Accounts, Business Units, and Currencies so that

the payment process prole can be used with any payment.

Note: You can click the Specify option to limit the use of this payment process prole topayments that have specic payment methods, disbursement bank accounts, business units,or currencies.

12. Select the Payment System tab.You can congure the payment le transmission to allow electronic transmission of the positive pay report tothe payment system or bank.

13. From the Payment System choice list, select BofA File System.14. From the Payment File Transmission Conguration choice list, select UCMPut.15. In the From Date eld, accept the default value of today's date.16. Select the Payment tab.

On the Payment tab, you can specify aributes for grouping invoices in the same payment if they share thesame aribute.

17. In the Document Grouping Rules section, select the Due date check box.18. In the Document Limits section, in the Maximum Documents per Payment eld, enter 5.19. Select the Reporting tab.

On the Reporting tab, you can specify parameters for the positive pay report. This report lists checks issued byyour company with payee names, amounts, and currency. Transmission of the report to your payment systemor bank prevents the payment of fraudulent checks, since unauthorized payments are not listed on the report.

20. In the Positive Pay section, from the Format choice list, select Positive Pay File Format.21. Select the Automatically transmit le check box.22. Click Save and Close.

A Conrmation message appears.23. Click OK.24. Click Done.25. Click Done.26. Sign out.

Submiing a Payment Process RequestA payment process request is a grouping of documents payable, for which a source product requests payment. You canname the payment process request and select the invoice group.



184

To submit a payment process request, complete these steps:

1. Sign in as a transaction user.2. Click the Payables icon and select Payments.3. On the Overview page, click the Tasks icon and select Submit Payment Process Request.4. On the Submit Payment Process Request page in the Name eld, enter PPR_XXX.5. Select the Selection Criteria tab.6. From the Invoice Group choice list, search and select XXXGroup.


7. Select the Payment and Processing Options tab.On the Payment and Processing Options tab, you can specify payment aributes, processing options, andvalidation failure handling. You select the disbursement bank account from which the invoices are paid, thepayment document and payment process prole you created and other options to stop the process for reviewand to take action if validations fail. If the reviews are satisfactory, a payment le is created.

8. From the Disbursement Bank Account choice list, search and select BofA-XXX.9. From the Payment Document choice list, select Payments Numbered Stock.

10. From the Payment Process Prole choice list, select PPP_XXX Positive Pay.11. From the Payment Conversion Rate Type choice list, accept Corporate.12. In the Processing Options subsection, select these check boxes: Review installments, Review proposed

payments, and Create payment les immediately.13. In the Validation Failure Handling subsection, from the Document choice list, accept Stop process for review.14. From the Payment choice list, accept Stop process for review.15. Click Submit.

A Conrmation message with the process number of the payment process request is displayed.16. Click OK.17. Scroll down to the Schedule Requests section to check the status of the payment process request.18. Click the Refresh icon until Succeeded is displayed in the Status column for the Initiate Payment Process

Request and the Payables Selected Installments Report processes that correspond to your process ID.The invoice selection process was successfully completed and the Payables Selected Installments report wasgenerated.

Reviewing Installments and Proposed PaymentsYou opted to stop the process to review invoices and proposed payments.

To review installments and proposed payments, complete these steps:

1. On the Overview page, Requiring Aention tab, click the Refresh icon. The payment process request appears.

Note: The payment process request shows a Status of Pending installments reviewbecause you opted to stop the process to review the invoices. In the Selected Installmentssection, ve invoices were selected by the payment process request. Since the selection looksne, you can continue.

2. Click the Action icon.3. On the Review Installments page, review the invoices.4. Click Submit.



185

A Conrmation message is displayed.5. Click OK.6. On the Overview page, Requiring Aention tab, click the Refresh icon.

Note: The payment process request displays the status of Pending proposed paymentreview because you opted to stop the process to review the proposed payment. Since theproposed payment looks ne, you can continue.


The Payment Summary section on the Review Proposed Payments page, contains the number of paymentscreated with the total payment amount. Since the payments look ne, you can continue.

8. On the Review Proposed Payments page, click Resume Payment Process.

A Conrmation message is displayed.9. Click OK.

Printing ChecksThe payment process request nished processing. The payment le was automatically formaed and is now ready toprint.

To print checks, complete these steps:

1. On the Overview page, Requiring Aention tab, expand the payment process request icon to display thepayment le.

2. Click the Refresh icon.

Note: The status of the payment process request is Waiting for payments le processingand the status of the payment le is Formaed and ready for printing.

3. Click the Action icon.4. On the Print Payment Documents page, from the Printer choice list, select PO 407.5. Click Print.

A Conrmation message is displayed.6. Click OK.7. On the Overview page, Requiring Aention tab, click Refresh to requery the payment process request.

The payment le status changes to Submied for printing.8. Click the Action icon.

Recording the Print StatusAfter you print checks, you must examine the printed checks to conrm that they're not spoiled or skipped. If a check isspoiled or skipped, you record the print status.

To record the print status, complete these steps:

1. On the Payment File page, review the payments and their check numbers. If your checks look ne, click RecordPrint Status.

2. On the Record Print Status: Payment File page, click Submit.



186

A Warning message is displayed.3. Click Record the Print Status.

A Conrmation message is displayed.4. Click OK.5. Click Done.

Note: On the Manage Payment Process Requests page, the payment process request statusis Waiting for payment le processing. The payment le status is Printed.

6. Click Done.

The Overview page appears.

Reviewing a CheckAfter printing checks, you can review them.

To review a check, complete these steps:

1. On the Overview page, scroll down to the Schedule Requests section.

You can review the schedule requests to verify the status of the positive pay le.2. Click Refresh.3. On the Create Positive Pay File process row, click the View Output icon to see the output that was transmied

to the payment system or bank.

A Create Positive Pay File, XXXXX, Output dialog box appears.4. Click the ESS link.

A .txt of the positive pay report is displayed.5. On the Format Payment Files process row, click the View Output icon to review the .pdf le of the printed

checks.

A Format Payment Files, XXXXX, Output dialog box appears.6. Click the ESS link.

A .pdf of the check is displayed.

How Disbursements Are ProcessedThe disbursement process starts when a source product calls Oracle Fusion Payments to process disbursements. Forexample, Oracle Fusion Payables uses the disbursement process to pay supplier invoices and Oracle Fusion Receivablesuses it to pay customer refunds. The disbursement process ends when either electronic payments are transmied to apayment system or nancial institution or paper payment documents, such as checks or promissory notes, are printed.

Electronic processing creates a payment le that is transmied to a payment system or other nancial institution. Thele contains instructions that tell the payment system or nancial institution how to remit funds. In some cases, fundsare remied electronically by an automatic deposit to a bank account. In other cases, the payment le can instruct thepayment system or nancial institution to issue a check for payment.



187

Seings That Aect DisbursementsThe following seings in the header region on the Create Payment Process Prole page impact electronicdisbursements:

• Payment File Format choice list: You specify the payment le format to use for the electronic payment le.

• Processing Type choice list: Electronic.

• Payment Conrmation Point choice list: Point at which a payment is conrmed. Payments can beautomatically conrmed, either when the payment le is formaed or when the payment le is transmied tothe payment system.

• Allow Manual Seing of Payment Conrmation check box: You can manually conrm payments on thefollowing pages:

◦ Manage Payment Files

◦ Payment File

◦ Overview page in the Payments work area

The following seings in the header region on the Create Payment Process Prole page impact printed disbursements:

• Payment File Format choice list: You specify the payment le format to use for the printed payment le.

• Processing Type choice list: Printed.

• Default Payment Document choice list

• Send to File radio buon: Produces a formaed output le, which is printed outside of Oracle FusionApplications.

• Send to Printer radio buon

• Automatically Print After Formaing check box

• Default Printer choice list



188

How Disbursements Are ProcessedThe following gure illustrates the ow of the disbursement process.

Start Select invoice installments for payment

Submit payment process request

Assign disbursement bank account and payment process profile to each

document payable

Validate documents payable

Build documents payable into payments

Review or modify proposed payments?

Build payments into payment files

Validate payment files Create data extract and format payment file

Format type?

Transmit payment file to bank or financial

institution

Print payment documents in payment file

Record print status

Send separate remittance advices

conditional

Review proposed payments

Electronic

Yes Payments modified?

Yes

No

No

Create and transmit positive pay file

conditional

Printed

Validate payments

The following gure illustrates the ow of the payment approval process within the disbursement process.



189

Review or modify proposed payments?

Review proposed paymentsYes Payments

modified?

No

Payment approval enabled

Proceed with existing payments

Yes

Notify approver with payment details

Build payments into payment files

Yes

No

Approved payment process request No Terminate payment

process request

Payments removedfrom payment process

request?Yes Proceed with

remaining payments

No

oNThe following table describes the action steps performed by the disbursement process, which starts in Payables andends in Payments.

Action Description

Create documents

Source product creates documents payable, such as invoices.

Select documents

Source product selects documents. Selected documents are grouped into a payment processrequest.



190

Action Description

Submit payment process request

Payment process request is submied to Payments for processing.

Assign bank account and paymentprocess prole

Disbursement bank accounts, which are your company's bank accounts, and payment processproles are assigned to documents payable within the payment process request. Paymentsautomatically assigns these values when possible. When not possible, the application asks youto supply the values on the Assign Payment Process Aributes page.

Validate documents

Payments executes any document level validations set up on the payment method or format.Documents payable that fail validation can be automatically removed and returned to thesource product. Valid documents payable continue in the disbursement process, or thepayment process request can be stopped for resolution, depending on options set during thesubmission of the payment process request.

Create and validate payments

Payments groups like documents payable into payments, according to rules set up in thepayment process prole. It then executes any payment level validations set up on thepayment method or format. Payments that fail validation can be automatically removedand the documents payable returned to the source product. Valid payments continue inthe disbursement process, or the payment process request can be stopped for resolution,depending on options set during the submission of the payment process request.

Review and modify payment processrequest

When the payment process request is submied, it can be set to stop for review as soon as allpayments pass validation. During the review, you can optionally remove payments from thepayment process request or documents payable from payments. If you make any changesduring the review, validations are executed again.

Approve or reject payment processrequest

When payment approval is enabled, the payment process stops at the Review ProposedPayments stage, and approvers can optionally remove payments directly from a paymentprocess request and then approve it. The approval process generates and routes paymentapproval notications to approvers. Approvers can approve or reject payment processrequests directly from e-mails or from the Review Proposed Payments page.

Create payment le

Payments processes payments within each payment process request and groups themaccording to their disbursement bank accounts, payment process proles, and other groupingrules to create payment les.

Validate payment le

Payments executes any payment le level validations set up on the format. Payment les thatfail validation can be corrected by removing payments or the validation can be overridden.

Create extract and format

An extract, or XML le, is created that contains the data relevant to the payment le. Oracle BIPublisher applies a format template to the data in the extract. The result is a formaed le thatcontains data specied by the format.

Transmit payment le

If the payment process prole for a formaed payment le species electronic processing, thepayment le is transmied to the payment system. The payment system is a bank or othernancial institution that processes the le and moves funds from the disbursement bankaccount to the payee bank account.



191

Action Description

Print payment documents

If the payment process prole for a formaed payment le species printed processing,the payment le is printed onto payment documents, such as checks. If any checks printincorrectly, they can be reprinted. After checks print successfully, you can record the printstatus, which allows Payables to account for the payments.

Perform post-processing After creating payments, you can optionally use reports as follows:

• Separate Remiance Advice reports can be sent to suppliers, which lists the invoices youpaid.

• Positive Pay reports can be sent to banks to prevent fraud since unauthorized paymentsare not listed on the Positive Pay report.

• Payment le registers can be created for internal use. They display details of paymentsthat are included in a payment le. You can retain this report for your records.

Payment MethodsA disbursement payment method is a method of payment that your company uses to pay a supplier, customer, oremployee. The payment method can be electronic, such as EFT, bill payable, or wire, or printed, such as a check. Youcan use a payment method to pay one or multiple third-party payees.

The purpose of creating disbursement payment methods is to:

• Dene the disbursement payment methods you want to use to make payments

• Dene usage rules to limit the use of disbursement payment methods to specic business units, legal entities,and other aributes.

• Assign validations to disbursement payment methods for running on documents payable, payments, andpayment les

The level of granularity that you need for your disbursement payment methods is a factor to consider before youdene them. You must decide whether to set up more or less granular disbursement payment methods. The leastgranular payment methods are those that are predened in Oracle Fusion Payments, such as Check or Electronic. Withthis setup, you can associate each payment method with many payment process proles and payment formats. Thisapproach requires less knowledge from source product users, such as invoice entry clerks, but may involve more worklater in the payment process.

Alternately, you can dene more granular payment methods. When you do this, you can benet from adding validationsto the payment method, which are very targeted for specic transactions. An example of a very granular paymentmethod is Italian EFT to which you might add a validation that's specic to Italy. With this kind of setup, validations arerun as early as during invoice entry and thus, errors can be xed more quickly.

Since creating very granular payment methods lead to more payment methods, it's important to also set up paymentmethod defaulting rules. Payment method defaulting rules eliminate the burden during invoice entry of manuallyselecting one appropriate payment method from the many available. You can also use supplier-specic defaults, anoption which is enabled on the Payment Method Default Basis section on the Manage Disbursement System Optionspage.



192

Creating a disbursement payment method in Payments is composed of the following major tasks:

• Creating usage rules

• Creating or assigning validations

Creating Usage RulesUsage rules specify when a disbursement payment method is available for use by source products for documentspayable. By creating usage rules, you enable or disable payment methods for each source product integrated withOracle Fusion Payments. You can provide dierent usage rules for dierent source products and change whether andwhen the payment method is available.

In the Usage Rules tab on the Create Payment Method page, you decide whether to assign the payment method to oneof the following:

• All payees

• Specic business units, legal entities, and payment process transaction types for Oracle Fusion Payables

• Specic business units, legal entities, and payment process transaction types for Oracle Fusion Receivables

• Specic payment process transaction types for Oracle Fusion Cash Management

Creating or Assigning ValidationsIn the Validations tab on the Create Payment Method page, you can assign predened validations to this paymentmethod or create user-dened validations. Validations are rules that check the validity of documents payable,payments, or payment les.

Usage RulesUsage rules specify when a payment method or a payment process prole can be used on a document payable.

You can specify:

• Usage rules for payment methods

• Usage rules for payment process proles

Usage Rules for Payment MethodsA payment method is the medium by which the rst-party payer, or deploying company, pays a supplier invoice,customer refund, or employee expense report.

By default, payment methods are available on all transactions. By creating usage rules, you can limit the use of apayment method based on the following transaction conditions:

• Source product

• Business unit

• First-Party legal entity

• Transaction type

• Whether domestic or foreign currency or payee location



193

Not all source products that are integrated with Oracle Fusion Payments have usage rule options. Some products, suchas Oracle Fusion Fixed Assets, create transactions that are imported into Oracle Fusion Payables, and are included inPayables usage rules. Other products, such as Oracle Fusion Expenses, have xed usage rules on supported paymentmethods.

The payment method that the source product user sees depends on the usage rules specied on the Create PaymentMethod page, Usage Rules tab. For example, suppose you have a payment method that is specic to one country. Youcould create a usage rule so that the payment method is available for only the one business unit associated with thatcountry. A user entering an invoice for any other business unit wouldn't see that payment method available to select.Usage rules, combined with payment method defaulting rules and user-denable validations, make straight-thoughprocessing possible.

Usage Rules for Payment Process ProlesA payment process prole species the details of the disbursement payment process, such as specications fordocument payable grouping, payment grouping, and payment le formaing.

By default, payment process proles are available on all transactions. By creating usage rules, you can limit the use of apayment process prole based on the following transaction conditions:

• Payment method

• Business unit

• Disbursement bank account

• Currency

The prole that is applied to a document payable depends on the usage rules specied on the Create Payment ProcessProle page, Usage Rules tab. When you submit a payment process request, Payments compares the aributes of eachtransaction to the prole provided on the Submit Payment Process Request page. Any transaction fails validation whoseaributes are in conict with the prole's usage rules. If no prole is selected, Payments compares each transaction'saributes to all existing proles to nd one with usage rules that match the transaction aributes. If a match doesn'toccur, user intervention is required to determine the appropriate payment process prole to use.

To enable straight-through processing, it's important that usage rules are no broader than necessary. For example,having two proles in which both sets of usage rules could apply to the same document payable leads to userintervention. However, if one prole is specic to business unit X and the other to business unit Y, then there is noambiguity. The application can uniquely identify which payment process prole to apply to the document payablewithout user intervention.

Payment Method DefaultingA payment method defaulting rule determines which payment method automatically populates an invoice or customerrefund. During setup of payment method defaulting rules, you specify conditions under which a payment method actsas a default.

Payment method defaulting can be based on:

• Source product

• Business unit

• First-party legal entity

• Transaction type



194

• Domestic or foreign currency or payee location

Oracle Fusion Payments applies the payment method defaulting rules in the prioritized order you specify. For example,if the rst rule is a match, Payments stops and automatically populates that rule's corresponding payment method ontothe invoice. Suppose you specify that the payment method for all documents processed by Oracle Fusion Payables isrst, Check, and second, EFT. In this case, if the conditions for payment method Check match those on the invoice, thenpayment method Check automatically populates the invoice.

If the conditions for payment method Check don't match those on the invoice, Payments determines whether theconditions for payment method EFT matches. If the conditions for payment method EFT match those on the invoice,then payment method EFT automatically populates the invoice.

The following factors may, depending on setup and data, inuence payment method defaulting:

• Whether the option Based Only on Payment Method Defaulting Rules Setup or Override DefaultingRules when Default Method Set for Payee is selected as the payment method default basis on the ManageDisbursement System Options page

• Prioritized order of the payment method defaulting rules

• Content of the payment method defaulting rules

• Default payment method set at supplier site, address, or supplier level

Payment Process ProlesA payment process prole is a setup entity that controls payment processing. The payment method and other invoiceaributes drive the assignment of a payment process prole to each document payable. Assigning a payment processprole to each documents payable tells Oracle Fusion Payments how to handle invoices, promissory notes, payments,and payment les during each step of the payment process.

A payment process prole controls payment processing for the disbursement ow. It provides the blueprint to:

• Link setups

• Control usage

• Specify payment formaing, printing, and transmission behavior

• Control creation of payments and payment les

• Automate report generation

To set up a payment process prole, in the Setup and Maintenance work area, go to the following:

• Oering: Financials

• Functional Area: Payments

• Task: Manage Payment Process Proles

Then, on the Manage Payment Process Proles page, click Create. The Create Payment Process Prole page appears.

Link SetupsBefore you can set up a payment process prole, you must set up the following:

• Payment formats

• Payment system and its payment system account



195

• Transmission conguration

Control UsageYou can set up a payment process prole to be used only with specic variables that appear on the Usage Rules tab:

• Payment method

• Disbursement bank account

• Business unit

• Currency

For example, if the payment format associated with the payment process prole only allows a specic currency, thenyou can specify that currency in the usage rules. The payment process prole is then only used on documents payableof the applicable currency.

Specify Payment Formaing, Printing, and Transmission BehaviorIn the header of the Create Payment Process Prole page, you can specify the following aributes:

• Whether the payment process prole can be used for electronic or printed payment processing

• Payment le format to be used with the payment process prole

• Payment conrmation point

If the payment process prole is used for electronic payments, you select a payment system and enter details for thepayment system account. This action allows Payments to electronically transmit les to the payment system.

If the payment process prole is used for printed payments, a payment system isn't required, but you can optionallyselect a payment system and transmission details so that Payments can electronically transmit positive pay les to yourbank.

Control Creation of Payments and Payment FilesOn the Payment and Payment File tabs of the Create Payment Process Prole page, you can control the creation ofpayments and payment les by:

• Grouping invoices into payments

• Grouping payments into payment les

On the Payment tab, an enabled grouping rule for an aribute means that two documents payable that share the samevalue for an aribute are grouped into the same payment. If values are dierent, the documents payable are in separatepayments. A disabled grouping rule for an aribute means that the aribute won't apply when documents payable arebuilt into payments.

On the Payment File tab, you specify payment grouping rules that determine which aributes are considered whengrouping payments into payment les.

Additionally, you can specify the following.

• Batch booking: One debit entry is posted for a group, rather than for each credit transaction

• Overrides: If you select an override option, the payment le contains the service level and delivery channelcombination you select, rather than those specied in supplier setup. If you don't select any override options,the payment le can contain multiple combinations.



196

• Payment limits: Limit for the number of payments in a payment le

• Payment sorting: Payments within a payment le are ordered as specied, which also determines the orderingof payments in the payment le register

• Bank instructions: Text that you want to include in all payment les created using this payment process prole

• Periodic sequences in format: Sequential numbering of payment les according to a payment system or bank'srequirements.

Automate Report GenerationOn the Reporting tab, you can specify whether you want the following reports to be automatically generated:

• Payment le register

• Positive pay

• Separate remiance advice

How You Set Up Payment ApprovalPayment approval allows management to control payments by prioritizing available funds. You can send payments toapprovers for review before nal payments are made to suppliers or employees. If enabled, the payment process stopsat the Review Proposed Payments stage. Approvers can then optionally remove payments directly from a paymentprocess request and approve it. Payment approval supports payments created only by the payment process requestprocess and not those created on the Create Payments page.

The approval process generates and routes payment approval notications to approvers. Approvers can approve orreject payment process requests directly from e-mails. They can also perform other approval actions from paymentapproval worklist notications.

Seing up payment approval includes the following actions.

• Enabling payment approval

• Dening payment approval policy

• Conguring payment approval rules

Enabling Payment ApprovalOn the Manage Disbursement System Options page, select the Enable payment approval option.

To enable payment approval, in the Setup and Maintenance work area, use the following:



• Task: Manage Disbursement System Options



197

Dening a Payment Approval PolicyBefore you can congure payment approval rules, your company must dene a payment approval policy. The paymentapproval policy denes:

• When to initiate the payment approval process

• Criteria for triggering the payment approval process, such as payment amount, bank account, or pay group

• A list of approvers who review payments and make nal payment decisions

Your company's payment approval policy:

• Determines which payments must go through the payment approval process

• Allows approvers to review payments and decide whether or not to approve the payment.

Conguring Payment Approval RulesTo congure payment approval rules, navigate to the BPM Worklist. In the Setup and Maintenance work area, use thefollowing:


• Task: Manage Task Congurations for Financials

Complete these steps:

1. Click the Task Conguration buon.2. In the Tasks to be congured pane, click the PaymentApproval (11.1.12.0.0) task.3. Click the Assignees tab.4. Click the Switch to Vertical Layout link.5. Click the diamond icon in the Payment Approval box.6. Click Go to rule.7. Click the Edit task icon to create the payment approval rules.

Note: Payment approval rules are congured to route payment approval notications to approvers insequential order only.

How You Implement the Granting Payment FunctionAccess Setup TaskGranting Payment Function Access is an optional Oracle Fusion Payments setup task in Setup and Maintenance. Todisburse payments, the Oracle Fusion Payables administrator grants you access to the predened duty role calledDisbursement Process Management Duty. You perform the Granting Payment Function Access set up task only torestrict the Disbursement Process Management Duty role.

With access to the Disbursement Process Management Duty, you can make the following types of payments:

• Customer refunds

• Supplier payments

• Reimbursement of employee expense reports



198

When you're granted access to the Disbursement Process Management Duty, you can perform the following actions inAuthorization Policy Manager:

• View the Disbursement Process Management Duty.

• View children duty roles of the Disbursement Process Management Duty.

• Restrict or expand the Disbursement Process Management Duty.

• Assign the Disbursement Process Management Duty to job roles.

To restrict the Disbursement Process Management Duty role for an employee, you must rst perform the followinghigh-level prerequisite steps in Oracle Identify Manager. Then perform the steps listed in this topic in APM:

1. Create a new user.2. Assign existing job roles to the new user.3. Create a new job role.4. Assign new job roles to the new user.

After you perform the steps listed in this topic in APM, then complete the steps by assigning the role of fscm to theDisbursement Process Management Duty role in APM.

Note: Oracle Fusion Applications and APM use dierent terms to describe the same security elements.

The following table lists two equivalent security terms.

Oracle Fusion Applications SecurityReference Manuals

Authorization Policy Manager

Job role

External role

Duty role

Application role

View the Disbursement Process Management DutyTo view the Disbursement Process Management Duty, perform the following steps in APM:

1. Sign in to your home page.2. In the address bar of your browser, delete all characters after the domain name and append the URL with /apm.3. Select the Authorization Management tab.4. In the Search section, select Application Roles from the For choice list.5. In the Search section, select fscm from the In choice list.6. In the blank search eld, enter Disbursement Process Management Duty and click the arrow icon.7. In the Search Results section, the following duty roles display:

◦ Disbursement Process Management Duty for Employee PII

◦ Disbursement Process Management Duty

8. In the Search Results section, select Disbursement Process Management Duty.9. Click the Actions list and select Open.



199

10. The Disbursement Process Management Duty displays in the General tab, along with its role name anddescription as follows:

◦ Display Name = Disbursement Process Management Duty

◦ Role Name = IBY_DISBURSEMENT_PROCESS_MANAGEMENT_DUTY

◦ Description = Assigns payment process aributes to documents payable, resolves document andpayment validation errors, and reviews proposed payments. Views items that were rejected or removedfrom a payment process request.

View Children Duty Roles of the Disbursement Process Management DutyThe Disbursement Process Management Duty contains children duty roles. If you have access to the DisbursementProcess Management Duty, you can also perform the duties of each of its children.

To view the children duty roles of the Disbursement Process Management Duty, perform the following steps in APM:

1. Select the Application Role Hierarchy tab.2. Click the Inherits link. The following children duty roles display:

◦ Party Information Inquiry Duty (FSCM)

◦ Disbursement for Customer Refund Data Management Duty: Allows customer refunds

◦ Disbursement for Employee Expense Data Management Duty: Allows employee expense reportpayments

◦ Disbursement for Payables Data Management Duty: Allows supplier payments

To view the parent duty roles that inherit the Disbursement Process Management Duty, click the Is Inherited By link.

Note: The Disbursement Process Management Duty role doesn't have a parent duty role.

Restrict or Expand the Disbursement Process Management DutyGiven your company's security needs, you can restrict or expand the Disbursement Process Management Duty byperforming the following steps:

1. Remove child duty roles from or add child duty roles to the predened Disbursement Process ManagementDuty.

2. Remove privileges from or add privileges to the predened Disbursement Process Management Duty.3. Create a new Disbursement Process Management Duty role. The new Duty role can have more or less child

duty roles or privileges as compared with the predened Disbursement Process Management Duty.

Assign the Disbursement Process Management Duty to Job RolesA job role consists of multiple duty roles. Duty roles determine access to functions appropriate to the job role. Forexample, the job roles of Accounts Payables Manager and Accounts Payable Supervisor inherit the DisbursementProcess Management Duty. You can add job roles to or remove job roles from the Disbursement Process ManagementDuty.

To view the predened job roles that are assigned to the Disbursement Process Management Duty, select the ExternalRole Mapping tab in APM.



200

The Disbursement Process Management Duty is assigned to the following predened job roles:

• Accounts Payable Supervisor

• Accounts Payable Manager

Any user who is assigned the preceding job roles has access to the following payment functions that are associated withthe Disbursement Process Management Duty:

• Customer refunds

• Supplier payments

• Reimbursement of employee expense reports

How You Use Oracle BI Publisher Enterprise to ModifyTemplates for Use with FormatsEach format in Oracle Fusion Payments corresponds to one Business Intelligence Publisher Enterprise (BI PublisherEnterprise) template. Payments uses BI Publisher Enterprise templates to format funds capture and funds disbursementtransactions according to the formaing requirements of nancial institutions and payment systems. Each templatecontains prescribed formaing aributes, such as data location. Banks, payment systems, and countries have specicelectronic formaing requirements for payment les and selement batches.

You can use existing BI Publisher Enterprise templates or modify them with minimal eort by using a standard texteditor, such as Microsoft Word. For example, when a payment system requires a change to its payment le format, youcan quickly make the change by modifying the appropriate template.

Whether you modify an existing template or create a new one, determines whether you also create a new format anda new payment process prole. Each payment process prole is associated with a format. The following table lists twotemplate scenarios and indicates the resulting action you take.

Actions Scenario 1 Scenario 2

Create a new template or modify anexisting template.

Create a new template.

Modify an existing template.

Name the template.

Rename the template.

Keep the same name.

Where to save the new or modiedtemplate.

Payments folder by the Custom folder orPayments folder by the Financials folder.

Payments folder by the Custom folder.

Create a new format.

Yes

No

Create a new payment process prole.

Yes

No



201

To modify a template, you can:

• Download a copy of the applicable template.

• Upload a copy of the modied template.

Download a Copy of the Applicable TemplateTo download a copy of a predened template, perform the following steps:

1. Sign in to Oracle BI Publisher Enterprise.2. On the Home tab, click the Catalog Folders link. The Catalog tab appears with a hierarchy of folders.3. Expand the Financials folder.4. Expand the Payments folder.5. Locate the predened template type that you want to modify and click the More link.6. From the menu, select Customize. All the templates that are associated with the predened template type that

you want to modify are copied to a folder by the Custom folder.7. You can now download the les from the Custom folder and modify them or you can continue with step 8.

Note: Do not modify predened templates. When you apply a new patch or a new release,it overrides any changes you made to the predened template. You can, however, copy apredened template and then modify it.

8. On the Data Model tab, to copy a predened template and save it to your local drive as a RTF le, click the Editlink of the applicable template. Then click the Save buon.

9. Navigate to the location where you want to save the copy of the template and click the Save buon.10. Navigate to the saved RTF le and open it.

Upload a Copy of the Modied TemplateTo upload a copy of a modied template, perform the following steps:

1. Using a text editor, modify the RTF le on your local drive.2. Save as Other Formats, change the le name, click the Save buon, and close the le.3. To upload a copy of your modied template to Oracle BI Publisher Enterprise, navigate to the applicable tab,

and click the Add New Layout link.4. Click the Upload icon. The Upload Template File dialog box appears.5. In the Layout Name eld, enter a name for the template you modied.6. In the Template File eld, browse to the location of the modied template on your local drive and click the

Open buon.7. From the Type choice list, select RTF Template.8. From the Locale choice list, select the language for the modied template.9. Click the Upload buon. The modied template appears on the Data Model tab of the applicable tab.

Note: The modied template is also copied to the Payments folder that is within the Customfolder.

10. To open the modied template, click the Edit link.11. To conrm that the modied template is saved, click the Catalog link. The Catalog tab appears with a hierarchy

of folders.12. Navigate as follows: Custom folder > Financials folder > Payments folder.13. Select the Payments folder.14. For the applicable template, click the Edit link. Your modied template appears.



202

Example of Seing Up User-Dened Validations forPayment Methods or for Payment FilesThis example demonstrates how to set up two user-dened validations. You must set up two validations when you wantyour user-dened validations to:

• Compare values

• Ensure that a value always appears in the eld you want to validate

The rst condition ensures that the validation checks a value, which meets your specied condition and value. Thesecond condition ensures that the eld the validation checks is not empty.

Note: You aren't required to set up two user-dened validations. A scenario can exist where you only want tocreate a user-dened validation that ensures that the eld the validation checks is not empty.

The following table summarizes key decisions to consider before seing up a user-dened validation.

Decisions to Consider In This Example

Do you want to compare a value that the user enters against aspecied condition and value?

You want to validate that the Document pay group eld is equalto the string Domestic when generating an invoice.

Do you want to ensure that the validated eld is not empty? You want to validate that the Document pay group eld is not

empty when generating an invoice.

User-Dened Validation That Checks a Specic Condition andValue

1. In the Setup and Maintenance work area, go to the following:



◦ Task: Manage Payment Methods

Then, on the Manage Payment Methods page, click the Create icon.2. On the Create Payment Method page in the User-Dened Validations section, complete the elds as shown in

this table for Validation 1.

If you save the invoice without entering any value in the Document pay group eld, Validation 1 alone, won'tkeep the invoice on hold.



203

Field Value

Field

Document pay group

Condition

Equal to String

Value

Domestic

User-Dened Validation That Checks for an Empty Field1. On the Create Payment Method page in the User-Dened Validations section, complete the elds as shown in

this table for Validation 2.

To include the scenario in the validation where no value is entered in the Document pay group eld, you mustset up a second validation. If you save the invoice without entering any value in the Document pay group eld,the application then keeps the invoice on hold.

Field Value

Field

Document pay group

Condition

Required

Value

Not applicable

FAQs for Disbursements

What's a payment code?Oracle Fusion Payments enables you to specify payment codes that are required by nancial institutions. Paymentcodes can provide details to banks or payments systems about transaction handling, bank charges, or payment reasonsfor regulatory reporting purposes.

Payment code types include:

• Bank instruction codes

• Delivery channel codes

• Payment reason codes



204

What's a bank instruction code?Bank instruction codes are values that contain instructions that must be passed to a bank or nancial institution atthe payment le level. Up to two bank instructions can be entered on a payment process prole. When that paymentprocess prole is used during the creation of a payment le, the bank instruction values are copied directly to it. Thevalues are made available to the formaing process by the extract. If the payment format species the use of bankinstructions, the values are passed to the bank in the header level of the payment le.

Oracle Fusion Payments provides many predened bank instruction codes.

What's a delivery channel code?Delivery channels are instructions that tell the bank how to make the payment to the payee. A default delivery channelvalue can be set on the supplier, supplier address, or supplier site. A value automatically populates from the lowestof these levels to the invoice in Oracle Fusion Payables. On the invoice, it's displayed with the installments and can bemanually overridden there.

When an installment is paid, the delivery channel is copied from the document payable to the payment when paymentdocuments have the same delivery channel. If you select delivery channel as a grouping rule on the prole, alldocuments that share the same delivery channel are grouped into a payment.

Oracle Fusion Payments provides many predened delivery channel codes.

What's a payment reason code?Payment reason codes are generally country-specic identiers provided by a country's government or centralbank. These codes provide the payment system or bank with additional details about the reason for the payment forregulatory reporting purposes. The purpose of entering payment reason codes required by a country's payment systemor central bank is to specify the reason for the payment.

Oracle Fusion Payments provides many predened payment reason codes.

When do I need to add a second condition to a user-denedvalidation that runs against a payment le format or a paymentmethod?If you want your eld validation to raise an error when the eld is empty, you must select Required from the Conditionchoice list. Then, if applicable, create a second validation for the same eld and select any other condition.


Chapter 8Payment System Connectivity

205

8 Payment System Connectivity

Options for ValidationsValidations are rules that ensure that transactions are valid before they are printed or submied electronically topayment systems. You use validations to ensure that disbursement transactions, such as invoices, payments, andpayment les meet specic conditions before they can be paid. You can assign validations to payment methods andpayment formats. A validation can be executed at the document payable, payment, or payment le level.

In payment processing, it's critical that payment les sent to payment systems and nancial institutions are valid andcorrectly formaed. If this is not done, the payment process is slowed, which results in additional time and cost due toproblem resolution. Oracle Fusion Payments helps you achieve straight-through processing by ensuring that payment-related details are valid. To assign validations, you can select from the following options:

• Assigning validations

• Creating user-dened validations

• Selecting from a predened library of validations

The following table lists the objects you can validate and when validations are executed for the applicable setup.

Object Payment Method-Driven Validationsare Enforced When...

Payment File Format-Driven Validationsare Enforced When...

Document Payable

The invoice is saved in the source product. The invoice installment is selected forpayment.

The invoice installment is selected forpayment.

Payment

The payment is created by building relateddocuments payable together.

The payment is created by building relateddocuments payable together.

Payment File

Not applicable.

The payment le is created.

Assigning ValidationsYou can assign user-dened validations to any:

• Payment method

• Payment le format

You can assign a validation to whichever object drives the requirement for validation. For example, if your bankformat requires a limited number of characters in a specic eld, you can assign that validation to the bank format. Bydoing this, you ensure that the validation is enforced only when applicable. However, if you want to enforce a generalvalidation that isn't specic to the payment method or format, you can consider timing in your decision.



206

Payments always validates as early as possible for a given object and setup. Document payable validations that areassociated with payment methods are enforced earlier in the process than those associated with formats. If you wantvalidation failures handled by the same person who is entering the invoice, you can associate the validation with thepayment method. This method is ideal for business processes where each person has full ownership of the itemsentered. However, if you want focused invoice entry with validation failures handled centrally by a specialist, you canassociate the validation with the format. This method is ideal for some shared service centers.

Creating User-Dened ValidationsA user-dened validation explicitly species the object to which the validation applies:

• Document payable

• Payment

• Payment le

User-dened validations are basic validations that correspond to simple operations. These validations can be usedas components, or building blocks, to build more complex validations. They enable you to validate, for example, thefollowing conditions:

• Length of a value. Example: Payment Detail must be fewer than 60 characters for your bank-specic paymentle format.

• Whether a eld is populated. Example: Remit to bank account is required when payment method is Electronic.

• Whether content of a eld is allowed. Example: Currency must be USD when using your domestic payment leformat.

Selecting From a Predened Library of ValidationsPayments provides a library of predened validations. You can associate these predened validations with anypayment method or payment le format you create. Many of the payment formats provided by Oracle have predenedvalidations associated with them by default.

Predened validations are groups of individual validations that are together for a specic purpose. Many of thepredened validations that you can associate with payment formats are country-specic. Predened validations cannotbe modied, although some have parameters you can set to dene specic values.

How You Set Up FormatsSeing up formats is a mandatory task in Oracle Fusion Payments. A format is a disbursements or a funds capturedata le to which an Oracle Business Intelligence Publisher (Oracle BI Publisher) template is applied. Oracle BI Publishertemplates contain formaing aributes that format data les. Formaed outputs include printed checks, electronicallytransmied payment les, selement batches, and reports.

The purpose of seing up formats is to enable payment systems, nancial institutions, or countries to understand yourcompany's messages, given their specic formaing requirements for disbursements or funds capture transactions.Inbound messages come from a payment system or nancial institution to your company. Outbound messages leaveyour company to your payment system or nancial institution.

Seing up formats involves the following actions:

• Using Oracle BI Publisher templates



207

• Using data extracts

• Using the identity format

• Considering best practices

• Seing up formats

• Understanding associations between format entities

• Assigning validations to formats

Note: Before you can set up formats, you must set up the corresponding templates in Oracle BI Publisher. Formore information on seing up templates, see Oracle Fusion Middleware Report Designer's Guide for OracleBusiness Intelligence Publisher at hp://docs.oracle.com/cd/E25054_01/bi.1111/e13881/toc.htm.

Using Oracle BI Publisher TemplatesEach Payments format corresponds to one Oracle BI Publisher template. BI Publisher templates specify exactly howformaed output is to be generated. BI Publisher templates can also be used to generate xed-position, machine-readable les through BI Publisher's eText functionality.

Using Data ExtractsEach disbursement or funds capture format is also associated with a disbursement or funds capture Payments' dataextract. Each data extract contains transactional data. Oracle BI Publisher templates use data extracts to formattransactional data. Transactional data is extracted from Payments' or Oracle Fusion Receivables' transactional tables.

For a disbursements extract, data comes from:

• Payments

• Payment les

• Documents payable tables

For a funds capture extract, data comes from:

• Funds capture transactions

• Selement batches

• Receivables transactions

For more information on Payments' XML extracts, see How To Generate and View Fusion Payments XML Extract ,Document ID 1428249.1, on My Oracle Support.

Using the Identity FormatThe Identity format outputs the XML extract provided by Payments. It's intended for diagnostic purposes, but you canalso use it to understand how extract elds are populated from transactional and setup entities. This is especially helpfulif you intend to create complex congurations using other templates.

The Identity format is an Oracle BI Publisher template called IBY_IDENTITY. It's part of the Funds Capture Authorizationand Selement report. If you want to use the Identity format for a disbursements report, you must download theRTF template and upload it as part of the intended disbursements report. Then, you can set up a modied formatin Payments using the newly created format with a payment process prole or a funds capture process prole, andexamine the XML output.



208

Considering Best PracticesBefore seing up formats, nd out what payment formats your processing bank supports. Consider using 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, or PPD

Seing Up FormatsIn the Setup and Maintenance work area, use the following to select a predened format type on the Manage Formatspage:



• Task: Manage Formats

The format type you select species:

• Type of message that is created

• Oracle BI Publisher template that is used to format the data le

• Data extract that is used

On the Create Format page, associate an Oracle BI Publisher template with the format type you selected.

Understanding Associations Between Format EntitiesThe following table describes the association between format types, templates, and data extracts.

Format Types Oracle BI Publisher Template Data Extracts

Disbursement Payment File Formats

Disbursement Payment File Formats

Disbursement Extract

Disbursement Positive Pay File Formats

Disbursement Positive Pay Formats

Disbursement Positive Pay Extract

Disbursement Separate Remiance AdviceFormats

Disbursement Separate Remiance AdviceFormats


Disbursement Accompanying LeerFormats

Disbursement Accompanying LeerFormats


Disbursement Payment Process RequestStatus Report Formats

Disbursement Payment Process RequestStatus Report

Disbursement Payment Process RequestExtract

Disbursement Payment File RegisterFormats

Disbursement Payment File Register




209

Format Types Oracle BI Publisher Template Data Extracts

Funds Capture Selement Format

Funds Capture Authorization AndSelement Formats

Funds Capture Extract

Funds Capture Accompanying LeerFormats

Funds Capture Accompanying LeerFormats


Funds Capture Payer Notication Formats

Funds Capture Payer Notication Formats


Assigning Validations to FormatsAfter you create a format, you can optionally assign predened or user-dened payment validations to it on the EditFormat page. Validations ensure that disbursements or funds capture transactions execute according to speciedconditions.

Transmission ProtocolsComputers use transmission protocols to communicate with each other across a network. To transmit data, such aspayment les from Oracle Fusion Payments to a payment system, the implementor denes protocols that the paymentsystem can receive.

Payments oers industry-standard transmission protocols, such as FTP, HTTP, and HTTPS, predened. They arecomposed of the following:

• A code entry point, which the payment system servlet uses to accomplish transmission

• A list of parameters, such as network address and port, for which the transmission conguration must supplyvalues

• Transmission protocol entry points, which are independent of payment servlets and may be called from thePayments engine

While the transmission protocol denes which parameters are expected in the communication, the transmissionconguration denes what value is supplied for each parameter. Transmission congurations and payment systems areassociated on the funds capture process prole for funds capture or on the payment process prole for disbursements.

Note: This note applies only to on-premises customers, and never to Oracle Cloud customers. The preferredle-based transmission protocol is Secure File Transfer Protocol (SFTP). File Transfer Protocol (FTP) isunsecured and should only be used to meet legacy third-party requirements. FTP must be used over a securelink such as a virtual private network or a leased line with data link level encryption enabled.



210

Transmission CongurationsA transmission conguration is a group of specic transmission details. A transmission conguration denes a valuefor each parameter in a transmission protocol. The values in a transmission conguration are specic to one paymentsystem or nancial institution.

For example, suppose a transmission protocol requires parameter values for a Socket IP Address and a SocketPort Number. Your payment system that accepts that protocol will give you the values that it expects to receive forthese parameters. You enter the applicable values in the Socket IP Address and Socket Port Number elds forthe transmission conguration. The transmission conguration is then assigned to the payment system within thefunds capture process prole for funds capture transactions or within the payment process prole for disbursementtransactions.

In the Setup and Maintenance work area, use the following to transmit les to your payment system by seing uptransmission congurations:



• Task: Manage Transmission Congurations

On the Manage Transmission Congurations page, click Create. The Create Transmission Conguration page appears.

How You Set Up Transmission CongurationsIn Oracle Fusion Payments, seing up transmission congurations is mandatory if your company wants to transmitpayments to a payment system or a bank. To enable your company to exchange information with your payment systemor bank, a preexisting agreement must exist as to how information will be structured and how each side will send andreceive it.

Seing up transmission congurations involves the following actions:

• Understanding protocols

• Understanding transmission congurations

• Understanding tunneling congurations


• Seing up transmission congurations

Understanding ProtocolsA transmission protocol is a set of rules or procedures for transmiing data between electronic devices, such ascomputers. To transmit data, such as a payment le or a selement batch from Payments to an external paymentsystem, you must dene the transmission protocols that the payment system can receive.

Payments oers industry-standard predened transmission protocols, such as SFTP, HTTP, HTTPS, and AS2. Theseprotocols include the following:

• A protocol implementation class, which implements the technical details of communication in a generic manner



211

• A list of parameters, such as network address and port, for which the transmission conguration must supplyvalues

The transmission protocol denes which parameters are expected in the communication between your company and itspayment system or bank.

Understanding Transmission CongurationsA transmission conguration is a group of specic transmission details, which is associated with a specic transmissionprotocol. A transmission conguration denes a value for each parameter in a transmission protocol. The values ina transmission conguration are specic to one payment system or nancial institution. For example, a transmissionprotocol may require parameters, as well as a Socket IP Address, and a Socket Port Number. Your payment system,which accepts that protocol, will give you the values that it expects to receive for those parameters. You enter thosevalues in the Socket IP Address and Socket Port Number elds.

Understanding Tunneling CongurationsA tunneling conguration is a type of transmission conguration that helps transmit data through a transmissionservlet that can securely connect to your payment system or bank without exposing internal data. The transmit servletacts as a relay or bridge between the dierent segments of your network infrastructure, some of which are moresuitable, such as a DMZ zone, from which to open connections to external systems.

Considering Best PracticesBefore selecting a protocol for payment processing, do the following:

• Find out what your processing bank supports.

• Favor transmission protocols that are predened in Payments.

• Use funds capture process proles or payment process proles for greater ease in conguring transmissionand formaing.

Before selecting a transmission conguration for payment processing, note the following:

You may need two transmission congurations as follows if you use a protocol that is normally blocked by your networksecurity rules:

• A tunneling conguration to exit the re wall

• A transmission conguration for the payment system server

Your transmission conguration must point to the tunneling conguration.

Caution: It is always a conguration error for the tunneling conguration to point to any other tunnelingconguration, including itself.

Seing Up Transmission CongurationsIn the Setup and Maintenance work area, use the following to select a protocol, which is the method of transmission,and click Create on the Manage Transmission Congurations page.



• Task: Manage Transmission Congurations



212

On the Create Transmission Conguration page, enable electronic connectivity with your payment system or bank byspecifying values for each parameter for the protocol you selected.

The transmission conguration is subsequently assigned to a payment system or bank in the funds capture processprole for funds capture transactions or in the payment process prole for disbursements.

How You Congure Prey Good Privacy (PGP)Encryption and Digital Signature for Outbound andInbound MessagesYou can secure both outbound and inbound messages using payload security. Payload security is the securing ofpayment les and other les using payment le encryption and digital signature based on the open PGP standard. Youcan update existing transmission congurations to use encryption and digital signature for your existing connectivitywith banks

For outbound messages, Oracle Payments Cloud supports encryption and digital signature for:

• Payment les and positive pay les for disbursements

• Selement batch les for funds capture

For inbound messages, the application supports decryption and verication of digitally signed encrypted les for:

• Funds capture acknowledgment les

• Bank statements

You can also secure payment data using secured transmission protocols, such as SFTP or HTTPS.

Note: Oracle Applications Cloud supports decryption of payment les that are encrypted using version BCPG1.45 or lower of the OpenPGP standard.

Conguring encryption and digital signature for outbound and inbound messages includes the following actions:

• Generating keys

• Seing up outbound transmission conguration

• Seing up inbound transmission conguration

• Uploading the bank-provided public key le

• Downloading the system-generated public key le

Generating KeysEncryption and digital signature verication requires a public key. Conversely, decryption and signing a digital signaturerequires a private key. The party who generates the public key and the private key, known as the key pair, retains theprivate key and shares the public key with the other party. You can generate or receive a public key subject to theagreement with your bank.

The following table provides typical generation details of the public and private key pair:



213

Key Pair Generated Generates Outbound Messages fromPayments

Generates Inbound Messages toPayments

PGP Public Encryption Key and PGPPrivate Signing Key

Bank

Deploying company

PGP Public Signature Verication Key andPGP Private Decryption Key

Deploying company

Bank

If you're generating the key pair, you can automatically generate them within Oracle Applications Cloud.

If you receive either the PGP Public Encryption Key or the PGP Public Signature Verication Key, you must import it intoOracle Applications Cloud using UCM.

Seing Up Outbound Transmission CongurationFor outbound messages, such as payment les, positive pay les, and selement batch les, you must:

• Encrypt your payment le using the bank-provided public encryption key.

• Optionally, sign the payment le digitally using the private signing key that you generate.

On the Create Transmission Conguration page, you can see the outbound parameters as described in the followingtable.

Outbound Parameters Description

PGP Public Encryption Key

A key given to you by your bank that you use to encrypt your outbound payment le. To upload the bank-provided public encryption key, use UCM by navigating to Tools > FileImport and Export. Lastly, on the Create Transmission Conguration page for the PGP Public Encryption Keyparameter, select the public encryption key le from the Value choice list.

PGP Private Signing Key A key generated by you to digitally sign the outbound payment le.

To generate the private signing key, select the Create option from the Value choice list for thePGP Private Signing Key parameter. The application:

• Automatically generates the private signing key and links it to your transmissionconguration.

• Generates a public encryption key le that you can download from UCM and share withyour bank. The bank uses your public encryption key le to verify the digital signature ofthe payment les that you transmit to the bank.



214

Seing Up Inbound Transmission CongurationFor inbound payment messages, such as acknowledgments and bank statements, you must:

• Verify the digital signature using the bank-provided public signature verication key.

• Decrypt the le using the private decryption key that you generate.

On the Create Transmission Conguration page, you can see the inbound parameters as described in the followingtable.

Inbound Parameters Description

PGP Public Signature Verication Key

A key given to you by your bank that you use to validate the digital signature of inboundacknowledgment les or bank statements. To upload the bank-provided public signature verication key, use UCM by navigating to Tools> File Import and Export. After you upload the bank-provided public signature verication key using UCM, you canselect the key le from the Value choice list for the PGP Public Signature Verication Keyparameter on the Create Transmission Conguration page. After you select the publicsignature verication key le, it's automatically imported.

PGP Private Decryption Key A key generated by you to decrypt the inbound encrypted le. To generate the private

decryption key, select the Create option from the Value choice list for the PGP PrivateDecryption Key parameter. The application:

• Generates the private decryption key and links it to your transmission conguration.• Generates a public signature verication key le that you can download from UCM and

share with your bank. The bank uses your public signature verication key le to encryptacknowledgments and bank statements.

Uploading the Bank-Provided Public Key FileTo upload, or import, either the bank-provided PGP Public Encryption Key or the PGP Public Signature Verication Keyinto Oracle Applications Cloud, perform the following steps:

1. Rename the bank-provided key le by including _public.key as the sux. Ensure that the key le name doesn'thave any special characters other than the underscore.

2. Navigate to: Navigator > Tools > File Import and Export.3. Import the bank-provided key le into account n/payments/import.4. Navigate to the Create Transmission Conguration page.5. From the Value choice list for the applicable parameter, select the uploaded key le.

Tip: The key name in the choice list is the same as the one you uploaded using UCM.

6. After you select the key and save the transmission conguration, the key is automatically imported into thePayments.



215

Downloading the System-Generated Public Key FileTo download the system-generated public key le from Payments to share with your bank, perform the follow steps:

1. On the Create Transmission Conguration page, select the Create option for the applicable parameter.2. Click the Save and Close buon.3. Navigate to: Navigator > Tools > File Import and Export.4. From the Account choice list, select n/payments/import and search for the system-generated public key le.5. Download the system-generated public key le.

Tip: The le name is similar to the private key le that was generated and aached to thetransmission conguration.

Note: SSH (Secure Socket Shell) key-generation for SFTP two-factor authentication is generated by OracleSupport based on a service request.

How You Test the Transmission CongurationThe transmission conguration setup is used to transmit outbound payment les, selement batch les, and positivepay les to your payment system or nancial institution. It's also used to pull funds capture acknowledgment les.The setup captures various parameters, which may be dierent for dierent protocols. You can test your transmissionconguration to conrm whether your setup of outbound and inbound transmission protocols is correct.

To conrm the accuracy of the setup, click the Test buon on the Create or Edit Transmission Conguration page.The Test buon is active only when the values associated with all the mandatory parameters are present. Typicaltransmission conguration parameters that are available to test include:

• Destination server URL

• Destination server IP address

• Destination server port number

• Remote le directory

• User credentials

Testing the transmission conguration setup includes reviewing return messages.

Reviewing Return MessagesThe Test buon action contacts the destination server with the specied parameters, which results in a return message.The return message is a combination of functional text and raw message text. This occurs so both functional andtechnical users can benet from the message. For example, suppose the remote le directory is invalid. The returnmessage is: Incorrect remote directory (IBY_Trans_Test_Remote_Dir_Fals).



216

The following table describes transmission conguration connection tests and test results with their associated returnmessages.

Test Test Result Return Message

Whether the connection is correct.

• Connection is successful.• Remote le directory is present.

Success (raw message)

Whether the remote le directory is valid.

• Connection is successful.• Remote le directory isn't present

or incorrect.

Incorrect remote directory (raw message)

Whether user credentials are correct.

• Connection is unsuccessful.• Destination IP address and port is

correct.• Incorrect login credentials.

Incorrect user credentials (raw message)

Whether IP address or port is correct.

• Connection is unsuccessful.• Incorrect IP address or port.

Incorrect destination server details (rawmessage)

Whether two factor key le-basedauthentication is successful.

• Connection is unsuccessful.• Unsuccessful key le-based

authentication.

Unsuccessful authentication (rawmessage)

Whether the destination server isresponsive.

Destination server is down.

Destination server is not responding (rawmessage)

Not applicable.

Any other failure.

(raw message)

How You Set Up a Payment SystemIn Oracle Fusion Payments, seing up a payment system is mandatory if your company wants to transmit electronicpayments or funds capture transactions to a payment system or a bank. The payment system can be the bank whereyour company has its bank accounts or it can be a third-party processor or gateway that connects your company to anancial network. The purpose of seing up a payment system is to dene the external organization that Paymentsuses to process your funds capture and disbursement transactions.

Payment systems aren't required for printed disbursement payments, such as checks, but may be required for relatedservices, such as a positive pay report.

Seing up a payment system includes the following actions:

• Selecting a gateway or processor payment system


• Dening a payment system



217

• Specifying payment system seings

• Understanding payment system accounts

Selecting a Gateway or Processor Payment SystemPayments supports both gateway and processor payment systems. A gateway is a service provider that acts as anintermediary between a rst party payee and a payment processor. A processor is a service provider that interactsdirectly with banks and card institutions to process nancial transactions. Examples of payment processors include Visa,MasterCard, and American Express.

Your choice of integrating with a gateway or a processor payment system is generally determined by your:

• Type of business

• Number of transactions per day

• Your bank

The following table describes the dierences between gateway and processor payment systems.

Factors Gateways Processors

Connectivity and Security

Provide easy connection, often using SSL-based internet connectivity.

Provide more rigorous security,connectivity, and testing requirements.

Additional Fees

Charge additional fees, including per-transaction fees, beyond what processorscharge.

Not applicable.

Volume of Transactions

Favor lower-volume merchants ormerchants who are willing to pay a per-transaction premium for easier setup andconnectivity.

Often favor higher-volume merchantswho are willing to exert more eort forprocessor connectivity.

Online or Oine

Takes all transactions online. Allows authorizations in real-time

and follow-up transactions, such asselements and credits oine.

• Oine transactions must bebatched together and sent as asingle request to the paymentsystem.

• All transactions other thanauthorizations are, by default,performed oine.

• Oine transactions are sent whenthe next selement batch operationis aempted.



218

Considering Best PracticesBefore you set up a payment system, leverage your current banking or processing relationship. Determine whether yourbank or processor can process transactions or has a partnership with a processor.

Dening a Payment SystemIn the Setup and Maintenance work area, use the following to dene a payment system:



• Task: Manage Payment Systems

On the Manage Payment Systems page, click Create. The Create Payment System page appears.

When you set up a payment system on the Create Payment System page, specify the following:

• Types of payment instruments the payment system supports for funds capture transactions

• Data le formats and transmission protocols accepted by the payment system

• Seings required by the payment system

• Seings required by the tokenization provider if your company has enabled tokenization

Note: Seing up a payment system may be required, even for transmiing a payment le oine bydownloading it to your local drive and then emailing it to your payment system or bank. The payment systemand payment system account setup capture several aributes, which are passed in the payment le orselement batch message. Without these aributes, a payment le is invalid and rejected by bank.

Specifying Payment System SeingsIn the Seings Required by Payment System section, specify the seings that the payment system requires from eachinternal payer or payee. These seings can be used to identify the internal payer or payee as a client of the paymentsystem or to provide other processing information. You can specify the type of data required for each seing anddecide whether it's advisable to secure the seing's values by masking.

Tip: The payment system generally provides the values for the payment system seings, which you enter aspart of the payment system account.

Understanding Payment System AccountsYou dene your company's account with the payment system on the Edit Payment System Accounts page. Thepayment system account contains a value for each of the aributes required by the payment system. For example, thepayment system may require a Submier ID and Submier Password to be included in any message sent to it.

You can congure a secure payment system account by entering a password. For secured seings, the values capturedin the payment system account are masked.

Tip: You can set up multiple payment system accounts in Payments for a single payment system.



219

Payment System AccountsA payment system account is an account identier that's composed of values for parameters. The payment systemprovides you with the values that it requires to identify each payment or selement batch le. Stored in the paymentsystem account are values for seings and your company's identiers. Your company can have multiple paymentsystem accounts with a single payment system.

Payment system accounts are associated with the following setup objects:

• Internal payees

• Funds capture process proles

• Payment process proles

The following table lists setup objects and the action they perform relative to the payment system.

Setup Object Setup Object Action

Payment system

• Tells Payments where to send the funds capture transactions.• Tells Payments where to send the disbursements transaction.

Payment system account

Tells Payments how to identify itself to the payment system

Transmission conguration

Tells Payments how to transmit the transaction to the payment system

Internal PayeesYou can set up routing rules that are assigned to an internal payee. Routing rules specify which payment systemaccount a transaction is transmied to, based on the values of various transaction aributes.

If you don't need granular routing rules to determine which payment system account is the right one for a transaction,or if you want a fallback value should none of the routing rules apply, you can set up one default payment systemaccount on each internal payee for each payment method.

Funds Capture Process ProlesThe funds capture process prole tells Oracle Fusion Payments how to process a funds capture transaction and howto communicate with the payment system. A funds capture process prole is specic to one payment system and itspayment system accounts.

For each payment system account that's enabled on the funds capture process prole, you can select up to threetransmission congurations, one each for authorization, selement, and acknowledgment.

Payment Process ProlesThe payment process prole tells Payments how to process a disbursement transaction and how to communicate withthe payment system to transmit a payment le or a positive pay le. When an electronic transmission is required, a



220

payment process prole is specic to one payment system and its payment system accounts. For each payment systemaccount that's enabled on the payment process prole, you select a transmission conguration.

Import a Security Credential FileTo secure your electronic transmissions, you can upload, import, and assign a security credential le to transmissioncongurations. A security credential le is a digital le that stores your security key, which the application uses toencrypt or authenticate data transmied to remote third-party systems such as banks. Once your security credentialle with its secret key is assigned to a specic transmission conguration, any future process that runs and referencesthis transmission conguration will use the le with its key for transmission security. The application understands whichcredential les are used by which protocols and displays only the appropriate ones in the setup pages.

Payments supports a variety of security-related credential les, including wallet les, trust store les, and digitalcerticates.

Note: This procedure is applicable to Oracle Cloud implementations only.

Before you can import a security credential le with its key into Payments, you must rst create a Payments masterencryption key.

Creating a Wallet File and a Master Encryption Key AutomaticallyTo create a wallet le and a master encryption key automatically, complete these steps:




◦ Task: Manage System Security Options

2. On the Manage System Security Options page, click Apply Quick Defaults.3. Select the Automatically create wallet le and master encryption key check box.4. Click the Save and Close.

Uploading the Wallet Security Credential FileBefore you can import the security credential le, you must rst upload it to Payments.

Caution: Ensure the credential le is password-protected when you create it and that it is immediately deletedfrom Oracle Fusion Applications upon completion of the import process.

1. Navigation: Tools > File Import and Export.2. Click the Upload icon to open the Upload File dialog box3. Browse to the le you created and stored locally.4. From the Account choice list, select n/payments/import.5. Click the Save and Close buon.



221

Importing the Wallet Security Credential FileTo import security-related credential les, such as wallets and private keys for use in advanced security features, youcan use the Import Security Credential Job process.

1. Navigation: Tools > Scheduled Processes to open the Scheduled Processes page.2. Click the Schedule New Process buon to open the Schedule New Process dialog box.3. Search and select the case sensitive Import Security Credential Job to open the Process Details dialog box.4. From the Credential File Type choice list, select the appropriate le type for your credential.5. In the Security Credential Name eld, enter a name for the credential le.6. From the UCM (Universal Content Management) File Name choice list, select the le you previously uploaded.7. Click the Submit buon.

A conrmation message indicates the process ran successfully.8. Click the Close buon.9. Click the Refresh icon. The Import Security Credential Job appears in the Search Results section with a status of

Succeeded.

Assigning the Wallet File to a Transmission CongurationTo assign the credential le to a transmission conguration, complete these steps:




◦ Task: Manage Transmission Congurations

2. On the Manage Transmission Congurations page in the Search section, select your protocol from the Protocolchoice list and click Search.

3. In the Search Results section, click the applicable conguration link to open the Edit TransmissionConguration page.

4. In the Value eld for your protocol's applicable parameter, select the le you created, uploaded, and imported.

The name of the specic parameter used to import a security credential le depends upon the protocol.

You can now securely transmit electronic les using this transmission conguration.

FAQs for Payment System Connectivity

What's a format type?A type or categorization that indicates what a format is used for. Examples of format types include payment le,remiance advice, and bank statement. Each format that you create in Oracle Fusion Payments is associated with aformat type so the application knows how the format is used. Format types are either disbursement formats that relateto payment les or funds capture formats that relate to selements or reports.

The following table lists several examples of format types.



222

Disbursement Format Types Funds Capture Format Types

Disbursement separate remianceadvice

Funds capture authorization and selement

Disbursement positive pay le

Funds capture accompanying leer

Disbursement payment processrequest status report

Funds capture payer notication

The format type you associate with a format species the following:

• Type of message that is created

• Data extract that is used by the template to format the transaction data

Related Topics

• How You Use Oracle BI Publisher Enterprise to Modify Templates for Use with Formats


Chapter 9Payments Security

223

9 Payments Security

System Security Options: Critical ChoicesYou can implement application security options on the Manage System Security Options page as part of a completesecurity policy that's specic to your organization. Security options can be set for encryption and tokenization of creditcards and bank accounts, as well as for payment instrument masking. Security options are used for both funds captureand disbursement processes.

Note: Credit card services are currently not available in Oracle Financials Cloud implementations.

Note: Before you can import credit cards into Expenses, you must enable encryption or tokenization of creditcards in Payments.

To secure your sensitive data, consider the following security questions:

• Which security practices do you want to employ?

• Do you want to tokenize your credit card data?

• Do you want to encrypt your bank account data?

• Do you want to encrypt your credit card data?

• How frequently do you want to rotate the master encryption key and the subkeys?

• Do you want to mask credit card and bank account numbers, and if so, how?

In the Setup and Maintenance work area, use the following to set up application security options:



• Task: Manage System Security Options

Best Security PracticesThe following actions are considered best security practices for payment processing:

• Comply with the Payment Card Industry Data Security Standard (PCI DSS). PCI DSS is the security standard thatis required for processing most types of credit cards.

◦ Comply with all requirements for accepting credit card payments.

◦ Minimize the risk of exposing sensitive customer data.

• Create the master encryption key.

◦ Rotate the master encryption key periodically.



224

Implementation Process of Master Encryption Key and EncryptionBefore you can enable encryption for credit card or bank account data, you must automatically create a masterencryption key. The master encryption key exists on the le system of Oracle Platform Security Services (OPSS). OPSSstores your master encryption key. The application uses your master encryption key to encrypt your sensitive data.

Automatic creation of the master encryption key ensures that it is created and stored in the proper location and with allnecessary permissions.

Credit Card TokenizationIf you tokenize your credit card data, you are complying with PCI DSS requirements. PCI DSS requires companies to usepayment applications that are PCI DSS compliant.

Tokenization is the process of replacing sensitive data, such as credit card data, with a unique number, or token, thatisn't considered sensitive. The process uses a third-party payment system that stores the sensitive information andgenerates tokens to replace sensitive data in the applications and database elds. Unlike encryption, tokens can't bemathematically reversed to derive the actual credit card number.

You can set up your tokenization payment system by clicking Edit Tokenization Payment System on the ManageSystem Security Options page. Then, to activate tokenization for credit card data, click Tokenize in the Credit Card Datasection.

Credit Card Data EncryptionYou can encrypt your credit card data to assist with your compliance of cardholder data protection requirements withthe following:

• Payment Card Industry (PCI) Data Security Standard

• Visa's PCI-based Cardholder Information Security Program (CISP)

Credit card numbers entered in Oracle Receivables and Oracle Collections are automatically encrypted. Encryption isbased on the credit card encryption seing you specify on the Manage System Security Options page.

Note: If you bring card numbers into Payments through import, it's advisable to run the Encrypt Credit CardData program immediately afterward.

Bank Account Data EncryptionYou can encrypt your supplier and customer bank account numbers.

Bank account encryption doesn't aect internal bank account numbers. Internal bank accounts are set up in OracleCash Management. They are used as disbursement bank accounts in Oracle Payables and as remit-to bank accounts inReceivables.

Supplier, customer, and employee bank account numbers entered in Oracle applications are automatically encrypted.Encryption is based on the bank account encryption seing you specify on the Manage System Security Options page.

Note: If you bring bank account numbers into Payments through import, it's advisable to run the EncryptBank Account Data program immediately afterward.



225

Master Encryption Key and Subkey RotationFor payment instrument encryption, Payments uses a chain key approach. The chain key approach is used for datasecurity where A encrypts B and B encrypts C. In Payments, the master encryption key encrypts the subkeys and thesubkeys encrypt the payment instrument data. This approach allows easier rotation of the master encryption key.

The master encryption key is stored on OPSS. OPSS stores data in an encrypted format. The master encryption key canbe rotated, or generated, which also encrypts subkeys, but doesn't result in encrypting the bank account numbers again.

If your installation has an existing master encryption key, you can automatically generate a new one by clicking Rotate.

Note: To secure your payment instrument data, you're advised to annually rotate the master encryption keyor rotate it according to your company's security policy.

You can also select the frequency with which new subkeys are automatically generated, based on usage or on themaximum number of days. To specify a subkey rotation policy, click Edit Subkey Rotation Policy.

Note: To secure your payment instrument data, you are advised to schedule regular rotation of the subkeys.

The security architecture for credit card data and bank account data encryption is composed of the followingcomponents:

• OPSS

• Payments master encryption key

• Payments subkeys

• Sensitive data encryption and storage



226

The following gure illustrates the security architecture of the OPSS repository, the master encryption key, and thesubkeys.

Master Encryption Key Automatically Created by

Payments

IBY_SYS_SECURITY_SUBKEYSTable

SubkeysGenerated by Payments

Oracle Platform Security Services

IBY_SECURITY_SEGMENTSTable

Payments Credit Card Numbers

Credit Card and Bank Account Number MaskingPayments serves as a payment data repository for customer and supplier information. Payments stores all of thecustomer and supplier payment information and their payment instruments, such as credit cards and bank accounts.Payments provides data security by allowing you to mask bank account numbers.

On the Manage System Security Options page, you can mask credit card numbers and external bank account numbers.To do it, select the number of digits to mask and display. For example, a bank account number of XXXX8012 displaysthe last four digits and masks all the rest. These seings specify masking for payment instrument numbers in the userinterfaces of multiple applications.

Enable Encryption of Sensitive Payment InformationFinancial transactions contain sensitive information, which must be protected by a secure, encrypted mode. To protectyour credit card and external bank account information, you can enable encryption. Encryption encodes sensitive data,so it can't be read or copied. To enable encryption, you must create a master encryption key. Oracle Platform SecurityServices is a repository that stores your master encryption key. The application uses your master encryption key toencrypt your sensitive data.

Note: Before you can import credit cards into Expenses, you must enable encryption or tokenization ofcredit cards in Payments. If you are using credit card data anywhere other than Expenses, you must enabletokenization in Payments.



227

To secure your credit card or bank account data, complete these steps:




◦ Task: Manage System Security Options

2. On the Manage System Security Options page, click Apply Quick Defaults.3. Select all the check boxes:

◦ Automatically create wallet le and master encryption key

◦ Encrypt credit card data

◦ Encrypt bank account data4. Click Save and Close.

Set Up a Supplier's Bank AccountIf any of your suppliers want to receive payments by EFT to their bank accounts, you can set up a supplier bank account.A supplier bank account can be created at the following levels:

• Supplier level

• Supplier address level

• Supplier site level

Each bank account assignment is comprised of the following entities:

• Supplier

• Bank account

• Bank account assignment

You can set up a bank account by doing the following:

• Find your existing supplier.

• Set up a bank account at the supplier, supplier address, or supplier site level.

• Provide additional information that is relevant to the bank account.

• Optionally, add joint bank account owners.

• Optionally, specify intermediary accounts.

• Optionally, assign a joint bank account to a supplier.

Find Your Existing SupplierOn the Manage Suppliers page, you can search for an existing supplier.

1. On the Manage Suppliers page, in the Search region, enter your supplier name or supplier number in theSupplier or Supplier Number eld and click the Search buon. Supplier details appear in the Search Resultsregion.

2. In the Search Results region, select the supplier name and click the Edit icon. The Edit Supplier: <SupplierName> page appears.



228

Set Up a Bank Account at the Supplier, Supplier Address, or Supplier SiteLevelYou can set up a supplier's bank account at the supplier, supplier address, or supplier site level.

1. To set up a bank account at the supplier level, on the Edit Supplier: <Supplier Name> page, select the Proletab. Select the Payments tab. Select the Bank Accounts subtab. Go to step 8 and continue.

2. To set up a bank account at the supplier address level, on the Edit Supplier: <Supplier Name> page, select theAddresses tab. Click a specic address name link. On the Edit Address: <Location> page, select the Paymentstab. Select the Bank Accounts subtab. Go to step 8 and continue.

3. To set up a bank account at the supplier site level, on the Edit Supplier: <Supplier Name> page, go to step 4 andcontinue.

4. Select the Sites tab. The supplier's various sites display.5. Click a specic site link. The Edit Site: <Supplier Site Name> page appears.6. Select the Payments tab.7. Select the Bank Accounts subtab.8. On the Bank Accounts subtab, click the Create icon. The Create Bank Account page appears. On the Create

Bank Account page in the Bank Account region, you set up basic information about the bank account.9. In the Bank Account region, select an option from the Country choice list.

Note: Validation of the bank account is based on the country for which the bank account isset up.

10. In the Account Number eld, enter the bank account number.11. From the Bank Name choice list, select a bank.

Note: If the country of the supplier's bank account and the country of the bank account'sbranch through which the payment is made is the same, then the payment is considered adomestic payment.

12. From the Branch choice list, select the branch where the bank account will reside.

Note: You can set up a supplier's bank account for making domestic payments by checkwithout specifying a bank or branch. To make electronic international payments, however,you must specify both a bank and a branch.

Note: If the country of the supplier's bank account and the country of the bank account'sbranch through which the payment is made is not the same, then the payment is consideredan international payment.

13. To make international payments to a supplier's bank account, select the Allow international payments checkbox.

Note: The Allow international payments check box can be selected only when you providebank and branch details. If you do not select the Allow international payments check box,international payments are not created.

14. If you are seing up a supplier's bank account in a European country, enter the International Bank AccountNumber (IBAN) in the IBAN eld.



229

Note: Validation of the IBAN is based on the country for which the bank account is set up.

15. From the Currency choice list, select the currency in which payments are made.

Note: If you select a currency, then the supplier's bank account is used to pay invoices in thatcurrency only. If you do not select a currency, then the supplier's bank account is consideredmulticurrency and can be used to pay invoices in any currency.

Provide Additional Information That is Relevant to the Bank AccountOn the Create Bank Account page, in the Additional Information region, you can enter additional information that isrelevant to the bank account you are seing up.

1. In the Account Sux eld, enter the value that appears at the end of the bank account number, if applicable.

Note: An account sux is required in some countries.

2. From the Conversion Rate Agreement Type choice list, select the type of conversion rate agreement you havewith the supplier.

3. In the Conversion Rate eld, enter the conversion rate for which one currency can be exchanged for another ata specic point in time.

4. In the Conversion Rate Agreement Number eld, enter the number of the conversion rate agreement with thesupplier that species the currency in which payments are made.

5. In the Check Digits eld, enter one or multiple digits used to validate a bank account number.6. In the Secondary Account Reference eld, you can optionally enter additional account information.7. In the Agency Location Code eld, enter the eight-digit value that identies a Federal agency as the supplier.8. Select the Factor account check box if the purpose of the bank account is to receive funds that are owed to

the supplier, but are being collected on behalf of the supplier by the bank or a third party. The supplier receivespayments from the funds collected, minus a commission.

Note: If you select the Factor account check box, then you must select the account ownerthat provides the factoring services. A factor bank account can be assigned to any supplierwithout rst adding that supplier as a joint owner.

Optionally, Add Joint Bank Account OwnersOn the Create Bank Account page, in the Account Owners region, you can optionally add other suppliers to thesupplier's bank account as joint bank account owners.

1. In the Account Owner eld, select a joint bank account owner from the list.2. In the From Date eld, select a starting date for the joint bank account owner.



230

Note: Every supplier's bank account has one or more owners. If the supplier wants to sharethe bank account with another supplier, then there will be multiple owners of the bankaccount. For multiple bank account ownership, you must specify one owner as the primaryowner. The primary owner is the supplier for whom you set up the bank account.

3. To specify the primary bank account owner among multiple owners, click the check mark icon and then clickthe Primary eld in the applicable bank account row. The check mark icon appears in the row you selected.

4. To add a row from which to select another joint bank account owner, click the Create icon.

Optionally, Specify Intermediary AccountsOn the Create Bank Account page in the Intermediary Accounts region, you specify intermediary bank accounts for thissupplier. If there are restrictions on the transfer of funds between two countries, you can specify an intermediary bankaccount. An intermediary account is used to transfer funds between the originator's bank and the beneciary's bank.

Optionally, Assign a Joint Bank Account to a SupplierFrom the Bank Accounts subtab at the supplier, supplier address, or supplier site level, you can optionally assign a jointbank account to a supplier.

1. On the Bank Accounts subtab, select the Create icon. The Search and Select: Bank Account dialog boxappears.

2. In the Search and Select: Bank Account dialog box, select the applicable joint bank account you want to assignto your supplier and click the OK buon. The bank account you selected now appears in the Bank Accountssubtab.

How You Update Bank, Branch, and Bank AccountNumbers on External Bank AccountsYou can now edit the bank account number of external bank accounts in these modules:

• Suppliers

• Customers

• Expenses

• Payroll

• Bill Management

• Higher Education

• Human Capital Management

On the simplied bank account page, you can also update the bank and branch if you created the bank account with theOracle Cash Management prole option named Use Existing Banks and Branches set to Yes. When you update the bankand branch, you must select the same prole option.



231

How Supplier Bank Account Import Data is ProcessedUse the Import Supplier Bank Accounts process to import supplier bank accounts and associated data into OraclePayments. You can download a spreadsheet template to enter your supplier bank account data. The template containsan instruction sheet to guide you through the process of entering your data. The template also provides eld-levelbubble help.

Tip: Service administrators, on-premise administrators, and on-premise users can run the Import SupplierBank Accounts process in the Scheduled Processes area.

Before you can import supplier bank accounts and associated data, you must create suppliers.

If the suppliers bank account is used for international payments, you must also create the following entities:

• Banks

• Bank Branches



232

This gure illustrates the ow of importing supplier bank accounts into the application, as well as correcting errors.

Start

SupplierBankAccountImportTemplate.xlxm

Correct Errors

End

Yes

Enter Data in Spreadsheet Template

Generate CSV File that is Compressed into a ZIP File

Submit Import Supplier Bank Accounts Process

Import Data into Payments Tables

Upload ZIP File to UCM

Load Data to Payments

Interface Tables

Errors?

Supplier Bank Account Data Uploaded to Payments

Tables

No

No

Yes Errors?

To access the SupplierBankAccountImportTemplate.xlsm spreadsheet template, complete these steps:

1. Navigate to the File-Based Data Import for Oracle Financials Cloud guide.2. In the Table of Contents, click the File-Based Data Imports link.3. Click the Supplier Bank Account Import link.4. In the File Links section, click the link to the Excel template.

Follow these guidelines when preparing your data in the worksheet:

1. Enter the required information for each column. Refer to the tool tips on each column header for detailedinstructions.



233

2. Don't change the order of the columns in the template.3. You can hide or skip the columns you don't use, but don't delete them.

Tabs That Aect the Import Supplier Bank Accounts ProcessThe Supplier Bank Account Import spreadsheet template contains an Instruction tab, plus additional tabs that representthe interface tables where the data is loaded.

The following table contains the names of the tabs in the Supplier Bank Account Import spreadsheet template and adescription of their contents.

Spreadsheet Tab Description

Instructions and CSV Generation Contains instructions and information about:

• The format of the template• The buon that you click to generate the CSV le

Additional information includes the following:

• Preparing and loading data• Submiing the Import Supplier Bank Accounts process• Correcting import errors

IBY_ TEMP_ EXT_PAYEES

Enter information about the supplier payees.

IBY_ TEMP_ EXT_ BANK_ACCTS

Enter information about the supplier bank accounts.

IBY_ TEMP_ PMT_ INSTR_USES

Enter information about the supplier bank account assignments.

How Import Supplier Bank Accounts Data Is ProcessedThis table describes the ow of data when you import supplier bank accounts into Payments:

Sequence Action Result

1. From the guide titled File-

Based Data Import for OracleFinancials Cloud, download thespreadsheet template namedSupplierBankAccountImportTemplate.xlsm.It is located in the File-Based Data Importschapter, Supplier Bank Account Importsection.

The File-Based Data Import spreadsheet isdownloaded.



234


2.

Enter data in the spreadsheet template. Follow the instructions on the Instructionsand CSV Generation tab under the sectiontitled Preparing the Table Data.

Follow the instructions on the Instructionsand CSV Generation tab under the sectiontitled Preparing the Table Data.

3. Click Generate CSV File.

Follow the instructions on the Instructionsand CSV Generation tab under the sectiontitled Loading the Data in the Instructionsand CSV Generation tab.

A CSV le is generated that is compressedinto a ZIP le.

4. To upload the ZIP le:

1. Navigate: Tools > File Import andExport.

2. In the File Import and Export page,click the "+" (Upload) icon. TheUpload File dialog box appears.

3. In the File eld, browse for andselect your ZIP le.

4. From the Account choice list, selectn/payables/import.

5. Click Save and Close.

The ZIP le is uploaded. Data isloaded into Payments interface tablessuccessfully or with errors.

5. To submit the Load Interface File for

Import process:

1. Navigate: Tools > ScheduledProcesses.

2. Click Schedule New Process.

The Schedule New Process dialogbox appears.

3. From the Name choice list, selectLoad Interface File for Import.

4. Click OK. The Process Details dialogbox appears.

5. From the Import Process choicelist, select Import Supplier BankAccounts.

6. From the Data File choice list, selectyour ZIP le.

7. Click Submit.

Data is loaded into Payments interfacetables.

6.

Follow the instructions on the Instructionsand CSV Generation tab under the sectiontitled Importing the Loaded Data

Load process purges Payments interfacetables.



235


7. To submit the Import Supplier Bank

Accounts Process:

1. Navigate: Tools > ScheduledProcesses.

The Scheduled Processes pageappears.

2. Click Schedule New Process.

The Schedule New Process dialogbox appears.

3. From the Name choice list, selectImport Supplier Bank Accounts.

4. Click OK.

The Process Details dialog boxappears.

5. From the Feeder Batch Identierchoice list, select the batchidentier that you indicatedin the File-Based Data Importspreadsheet.

6. Click Submit.

The Import Supplier Bank Accountsprocess rst validates the supplier bankaccounts and associated data and thenimports the data from the Paymentsinterface tables into the followingPayments tables:

• IBY_EXT_BANK_ACCOUNTS• IBY_EXTERNAL_PAYEES_ALL• IBY_PMT_INSTR_USES_ALL

After you submit the Import SupplierBank Accounts process, the following dataappears in Payments:

• Supplier bank accounts• Payment preferences:

◦ payment delivery

◦ payment specications

◦ separate remiance advicedelivery method

• Relationship of supplier withsupplier bank account

The log output of the Import SupplierBank Accounts process reports thenumber of successful and rejectedrecords.

8. To correct import errors:

1. Identify the rejected records basedon details provided in the log le.

2. Create a new spreadsheet thatcontains only rejected recordsthat are copied from the oldspreadsheet.

3. For the Import Batch Identiercolumn, enter a dierent FeederBatch ID.

4. Make necessary corrections to thedata.

5. Load the data using a newspreadsheet.

6. Generate the CSV File, upload theZIP le, and continue.

7. Failed records remain in thePayments interface table and arenot purged automatically.

Failed records remain in the Paymentsinterface table and are not purgedautomatically.



236


9. Import supplier bank account data at one

of the following levels if you have theirassociated identiers:

• Supplier level requires the SupplierNumber.

• Supplier site level requires theSupplier Site Code.

If only the Supplier Number is provided,the supplier bank account is created at thesupplier level. If the Supplier Number and the SupplierSite Code are provided, the supplier bankaccount is created at the supplier sitelevel.

10.

Set the Primary indicator in the SQL loaderle for only one bank account per supplierper level.

If the Primary indicator is set for multiplebank accounts, then Payments acceptsonly the rst bank account with theindicator set to be the primary account atthat level. If the Primary indicator isn't set for anybank account, Payments accepts the rstbank account as the primary.

11.

Manage intermediary account details andcreate factor accounts manually using theManage Suppliers page.

The Import Supplier Bank Accountsprocess doesn't allow you to import thefollowing data:

1. Intermediary accounts2. Factor accounts

Related Topics• File Based Data Import for Oracle Financials Cloud• Overview of External Data Integration Services for Oracle Cloud

Removal of Personally Identiable InformationThe General Data Protection Regulation is a regulation in European Union (EU) law about data protection and privacyfor all individuals within the EU and the European Economic Area. Your organization can comply with the GDPRregarding the collection and use of personal data of EU residents.

You can remove an individual's personal data:

• If requested by an individual

• If the individual is no longer employed with your organization

Caution: If you remove personally identiable information, it can't be retrieved.

To run the removal process, you must have the duty role of Financial Application Administrator.

To remove an individual's personally identiable information for any product in Oracle Financials applications, yousubmit the Remove Personally Identiable Information in Financials process.

1. Navigate: Navigator > Tools > Scheduled Processes.

http://docs.oracle.com/cloud/latest/financialscs_gs/OEFBF

http://www.oracle.com/pls/topic/lookup?ctx=fa20a&id=C260011EE39AD9F3E040D30A6881341B



237

2. On the Scheduled Processes page, click Schedule New Process.3. Search and select Remove Personally Identiable Information in Financials.4. From the Party choice list, select the person's name for whom you want to remove personally identiable

information.5. Click Submit.

Table and Column Details for Potential Removal of Personally IdentiableInformationThis table lists applications and their corresponding tables and columns that store sensitive data, the data type that isstored in each column, whether you can redact the data from the column, and the reason for redaction.

SequenceNumber andProduct

Table Column Data Type Redact? Reason forRedaction

1 Oracle Payments

IBY_CREDITCARD

CC_NUMBER_HASH1

VARCHAR2(64CHAR)

No

Unreadable data.

2 Oracle Payments

IBY_CREDITCARD

CC_NUMBER_HASH2

VARCHAR2(64CHAR)

No

Unreadable data.

3 Oracle Payments

IBY_CREDITCARD

CCNUMBER

VARCHAR2(30CHAR)

No

Tokenized orencrypted data.

4 Oracle Payments

IBY_CREDITCARD

CHNAME

VARCHAR2(80CHAR)

No

Nonsensitive sincecard is secured.

5 Oracle Payments

IBY_CREDITCARD

EXPIRYDATE

DATE

No


6 Oracle Payments

IBY_CREDITCARD

MASKED_CC_NUMBER

VARCHAR2(30CHAR)

No


7 Oracle Payments

IBY_ EXT_BANK_ACCOUNTS

BANK_ACCOUNT_NAME

VARCHAR2(80CHAR)

Yes

Sensitive data.

8 Oracle Payments


BANK_ACCOUNT_NAME_ALT

VARCHAR2(320CHAR)

Yes

Sensitive data.



238



9 Oracle Payments


BANK_ACCOUNT_NUM

VARCHAR2(100CHAR)

Yes

Sensitive whenbank accountisn't encrypted ormasked.

10 Oracle Payments


BANK_ACCOUNT_ NUM_ELECTRONIC

VARCHAR2(100CHAR)

Yes


11 Oracle Payments


BANK_ACCOUNT_NUM_HASH1

VARCHAR2(64CHAR)

No

Unreadable data.

12 Oracle Payments


BANK_ACCOUNT_NUM_HASH2

VARCHAR2(64CHAR)

No

Unreadable data.

13 Oracle Payments


IBAN

VARCHAR2(50CHAR)

Yes


14 Oracle Payments


IBAN_HASH1

VARCHAR2(64CHAR)

No

Unreadable data.

15 Oracle Payments


IBAN_HASH2

VARCHAR2(64CHAR)

No

Unreadable data.

16 Oracle Payments


MASKED_ BANK_ACCOUNT_NUM

VARCHAR2(100CHAR)

Yes

Denormalizedvalue. Sensitivewhen bankaccount isn'tencrypted ormasked.

17 Oracle Payments


MASKED_IBAN

VARCHAR2(50CHAR)

Yes


18 Oracle Payments

IBY_ FNDCPT_TX_EXTENSIONS

INSTRUMENT_SECURITY_CODE

VARCHAR2(10CHAR)

No

No longer storecard vericationvalue.



239



19 Oracle Payments

IBY_ TRXN_SUMMARIES_ALL

DEBIT_ADVICE_EMAIL

VARCHAR2(255CHAR)

Yes

Denormalizedvalue. Sensitivedata.

20 Oracle Payments

IBY_PAYMENTS_ALL

EXT_ BANK_ACCOUNT_NAME

VARCHAR2(360CHAR)

Yes

Nonsensitive whenperson data isredacted.

21 Oracle Payments

IBY_PAYMENTS_ALL

EXT_ BANK_ACCOUNT_NUMBER

VARCHAR2(100CHAR)

Yes


22 Oracle Payments

IBY_PAYMENTS_ALL

EXT_ BANK_ACCOUNT_IBAN_NUMBER

VARCHAR2(50CHAR)

Yes


23 Oracle Payments

IBY_PAYMENTS_ALL

PAYEE_NAME

VARCHAR2(360CHAR)

Yes

Payee name issensitive data.

24 Oracle Payments

IBY_PAYMENTS_ALL

PAYEE_ADDRESS1

VARCHAR2(240CHAR)

Yes

Address data.

25 Oracle Payments

IBY_PAYMENTS_ALL

PAYEE_ADDRESS2

VARCHAR2(240CHAR)

Yes

Address data.

26 Oracle Payments

IBY_PAYMENTS_ALL

PAYEE_ADDRESS3

VARCHAR2(240CHAR)

Yes

Address data.

27 Oracle Payments

IBY_PAYMENTS_ALL

PAYEE_ADDRESS4

VARCHAR2(240CHAR)

Yes

Address data.

28 Oracle Payments

IBY_PAYMENTS_ALL

PAYEE_CITY

VARCHAR2(60CHAR)

Yes

Address data.



240



29 Oracle Payments

IBY_PAYMENTS_ALL

PAYEE_POSTAL_CODE

VARCHAR2(60CHAR)

Yes

Address data.

30 Oracle Payments

IBY_PAYMENTS_ALL

PAYEE_STATE

VARCHAR2(120CHAR)

Yes

Address data.

31 Oracle Payments

IBY_PAYMENTS_ALL

PAYEE_PROVINCE

VARCHAR2(120CHAR)

Yes

Address data.

32 Oracle Payments

IBY_PAYMENTS_ALL

PAYEE_COUNTY

VARCHAR2(120CHAR)

Yes

Address data.

33 Oracle Payments

IBY_PAYMENTS_ALL

PAYEE_COUNTRY

VARCHAR2(60CHAR)

Yes

Address data.

34 Oracle Payments

IBY_PAYMENTS_ALL

REMIT_ADVICE_EMAIL

VARCHAR2(255CHAR)

Yes

Address data.

35 Oracle Payments

IBY_PAYMENTS_ALL

PAYEE_PARTY_NAME

VARCHAR2(360CHAR)

Yes

Party name issensitive data.

36 Oracle Payments

IBY_PAYMENTS_ALL

PAYEE_ LE_REGISTRATION_NUM

VARCHAR2 (50CHAR)

Yes


37 Oracle Payments

IBY_PAYMENTS_ALL

PAYEE_ TAX_REGISTRATION_NUM

VARCHAR2 (50CHAR)

Yes


38 Oracle Payments

IBY_PAYMENTS_ALL

PAYEE_ADDRESS_CONCAT

VARCHAR2 (2000CHAR)

Yes

Address data.

39 Oracle Payments

IBY_PAYMENTS_ALL

BENEFICIARY_NAME

VARCHAR2 (360CHAR)

Yes

Beneciary nameis sensitive data.



241



40 Oracle Payments

IBY_PAYMENTS_ALL

PAYEE_ALTERNATE_NAME

VARCHAR2 (360CHAR)

Yes

Payee alternatename is sensitivedata.

41 Oracle Payments

IBY_PAYMENTS_ALL

EXT_ BANK_ACCOUNT_ALT_NAME

VARCHAR2 (320CHAR)

Yes

Bank accountalternate name issensitive data.

42 Oracle Payments

IBY_PAYMENTS_ALL

EXT_ BANK_ACCOUNT_NUM_ELEC

VARCHAR2 (100CHAR)

Yes


43 Oracle Payments

IBY_PAYMENTS_ALL

EXT_ BANK_ACCT_ OWNER_PARTY_NAME

VARCHAR2 (360CHAR)

Yes

Owner party nameis sensitive data.

44 Oracle Payments

IBY_ EXTERNAL_PAYEES_ALL

REMIT_ADVICE_EMAIL

VARCHAR2(255CHAR)

Yes

Sensitive data.

45 Oracle Payments

IBY_ EXTERNAL_PAYERS_ALL

DEBIT_ADVICE_EMAIL

VARCHAR2(255CHAR)

Yes

Sensitive data.

46 Oracle Payables

AP_CHECKS_ALL

ADDRESS_LINE1

VARCHAR2(240CHAR)

Yes

Address data.

47 Oracle Payables

AP_CHECKS_ALL

ADDRESS_LINE2

VARCHAR2(240CHAR)

Yes

Address data.

48 Oracle Payables

AP_CHECKS_ALL

ADDRESS_LINE3

VARCHAR2(240CHAR)

Yes

Address data.

49 Oracle Payables

AP_CHECKS_ALL

CITY

VARCHAR2(60CHAR)

Yes

Address data.

50 Oracle Payables

AP_CHECKS_ALL

COUNTRY

VARCHAR2(60CHAR)

Yes

Address data.



242



51 Oracle Payables

AP_CHECKS_ALL

ZIP

VARCHAR2(60CHAR)

Yes

Address data.

52 Oracle Payables

AP_CHECKS_ALL

VENDOR_NAME

VARCHAR2(240CHAR)

Yes

Supplier name issensitive data.

53 Oracle Payables

AP_CHECKS_ALL

BANK_ACCOUNT_NUM

VARCHAR2(30CHAR)

Yes

Denormalizedvalue.

54 Oracle Payables

AP_CHECKS_ALL

ADDRESS_LINE4

VARCHAR2(240CHAR)

Yes

Address data.

55 Oracle Payables

AP_CHECKS_ALL

COUNTY

VARCHAR2(150CHAR)

Yes

Address data.

56 Oracle Payables

AP_CHECKS_ALL

IBAN_NUMBER

VARCHAR2(40CHAR)

Yes

Denormalizedvalue.

57 Oracle CashManagement

CE_PAYEES

TAX_REGISTRATION_NUMBER

VARCHAR2(20CHAR)

Yes

Sensitive data.

58 Oracle Receivables

AR_ CUSTOMER_ALT_NAMES

ALT_NAME

VARCHAR2(320CHAR)

Yes

Alternatecustomer nameusing Zengincharacters.


AR_ PAYMENT_SCHEDULES_ALL

DEL_ CONTACT_EMAIL_ADDRESS

VARCHAR2(1000CHAR)

Yes

Email of thecustomer bill-to contact whoreceives printedtransactions.


RA_ CUSTOMER_TRX_ALL

DEL_ CONTACT_EMAIL_ADDRESS

VARCHAR2(1000CHAR)

Yes

Email of thecustomer bill-to contact whoreceives printedtransactions.



243



61 Oracle AdvancedCollections

IEX_DUNNINGS

CONTACT_DESTINATION

VARCHAR2(240CHAR)

Yes

Contact whoreceives thedunning.

FAQs for Payment Security

What happens if I create a corporate card and didn't enableencryption?If you created corporate cards in Oracle Expenses without rst enabling encryption in Oracle Payments, encryptionof your credit card numbers is automatically enabled. Payments doesn't allow credit card creation without enablingsecurity. You can secure your credit cards with encryption or tokenization.



244


Chapter 10Cash Management and Banking Conguration

245

10 Cash Management and BankingConguration

How Bank, Branch, and Account Components WorkTogetherBanks, branches, and accounts t together on the premise of the Bank Account model.

The model enables you to dene and keep track of all bank accounts in one place and explicitly grant account access to:

• multiple business units

• functions

• users

This eliminates the redundant duplicate bank account setup in dierent business units when these business units sharethe same bank account.

BanksCreating a bank is the rst step in the bank account creation. You can:

• Search for existing banks to view and update

• Create a new bank from an existing party

Consider the following:

• The option to create from an existing party is implicitly implemented by the matching option.

• The option is available only after the existing party has been found with the same bank.

• If you select the matching option, the page repopulates the information from the matched party.

BranchesOnce you have created your bank, the next step is creating a branch or branches associated to the bank. The matchingoption is also available when creating branches. To create a new branch without using the matching option, manuallyenter the required information. You can also dene other branch- related aributes in the same page.

If you don't use the matching option when an existing party is found, a branch with the same party name is created.

AccountsThe four areas associated with dening an account are:

• General information

• Control of the account

• Security and access to the account



246

• Business unit assignment

Once the bank and branch are created, proceed to the bank account setup by doing the following:

• Select the bank branch you want to associate to your bank account.

• Assign the owner of the bank account.

Note: To create a bank account for Payables or Receivables, add the Business Unit Access rst forthe business units to use the bank account.

Consider the following:

• The Oracle Fusion Account Payables or Receivables accounts are identied by the business unit.

• The Oracle Fusion Payroll accounts are identied by the legal entity.

• The program, Inactivates Banks and Bank Branches enables you to inactivate all banks and bank branches thathave no active internal and external bank accounts.

Considerations When You Create AccountsBanks, branches and accounts t together on the premise of the Bank Account model. The Bank Account modelenables you to dene and keep track of all bank accounts in one place.

The Bank Account Model can explicitly grant account access to multiple business units, functions, and users. Considerthe following when you set up bank accounts:

• Assign a unique general ledger cash account to each account, and use it to record all cash transactions for theaccount. This facilitates book to bank reconciliation.

• Grant bank account security. Bank account security consists of bank account use security, bank account accesssecurity, and user and role security.

Account UseAccount Use refers to accounts created for:

• Oracle Fusion Payables

• Oracle Fusion Receivables

• Oracle Fusion Payroll

Select the appropriate use or uses when creating an account in one or more of these applications.

Account AccessPayables and Receivables account access is secured by business unit. Before the bank account is ready for use byPayables or Receivables, you must:

1. Select the appropriate use for the application.2. Grant access to one or more business units.

Note: You can only assign access to the business units that use the same ledger as the bank accounts owningthe legal entity,



247

User and Role SecurityYou can further secure the bank account so that it can only be used by certain users and roles. The default value forsecure bank account by users and roles is No. For Payables and Receivables, you must have the proper business unitassigned to access a bank account even if the secure bank account by users and roles is No. If the secure bank accountby users and roles is set to Yes, you must be named or carry a role assigned to the bank account to use it.

• You must assign the security duty role Cash Management Administration to the Cash Manager job role toprovide access for seing up banks, branches, and accounts. You must have the assigned Manage BankAccount Security privilege to modify the User and Role Security.

• If you want to restrict the access to the Security tab, you must create a customized role and remove theprivilege Manage Bank Account Security. For example, you would copy the Cash Management Administrationduty role, rename it, and remove the privilege.

GL Cash Account SegmentsConsider selecting the option to enable multiple cash account combinations for reconciliation if you want to reconcilejournal lines of multiple cash account combinations matching the same natural account and other specied segmentvalues.

For example, if you set up 01-000-1110-0000-000 as your cash account, and select Account and Sub-Account as GLCash Account Segments, you're able to manually or automatically reconcile journal lines entered on dierent accountcode combinations matching the same natural account '1110' and sub-account '0000'.

Cash Management Prole OptionsProle options in Oracle Fusion Cash Management provide ways to improve and promote eciency in your businesspractices. How you congure these prole options can aect the interaction with other applications. Enabling theseprole options can streamline your processes between those applications.

The following table lists and describes the Cash Management prole options:

Prole Option Prole Display Name Applies To Default Seing

CE_ DISABLE_ BANK_VAL

Disable Country Specic BankValidations

Internal Bank Accounts External Bank Accounts

No

CE_ GL_ RECON_ENABLED

Journal Reconciliation Enabled

Bank Reconciliation

Yes

CE_ MASK_ INTERNAL_BANK_ACCT_NUM

Mask Internal Bank AccountNumbers

Internal Bank Accounts

No Masking

CE_ USE_ EXISTING_BANK_BRANCH

Use Existing Banks andBranches

Employee Bank Accounts Payee Bank Accounts

No



248

Note: Internal bank accounts are set up in Oracle Fusion Cash Management. Assign the disbursementbank account to Oracle Fusion Account Payables and the remit-to bank accounts to Oracle Fusion AccountReceivables.

Note: External bank accounts are set up and used for suppliers, customers, ad hoc payees, and employees.

Enabling Prole Options: Points to ConsiderThe following information provides details on conguring prole options, how they inuence other applications, andhow they can streamline your business practices.

1. Disable Country Specic Validations

This prole option manages the country-specic validations for the bank code, branch number, accountnumber, check digit, and IBAN. You can set this prole option at the site or user level. The prole option defaultis set to No at the site level. If the prole option is set to Yes, this eliminates the country-specic validationprocess for the bank code, branch number, account number, check digit, and IBAN. This prole option aectsinternal and external bank accounts. It doesn't aect the checks for unique banks, branches, accounts, and themandatory requirement of the bank account number.

2. Journal Reconciliation Enabled

This prole option enables the manual and automatic reconciliation of bank statement lines directly from GLJournal manual entries. You can set this prole option at the site level. The prole option default is set to Yes. Ifthe prole option is set to No, it disables the journal source transaction on the Manage Reconciliation MatchingRules, the Manual Reconciliation page, and the reconciliation processes. Note: This prole can only be set to Noif there are zero Journal Entries that have been reconciled.

3. Mask Internal Account Numbers

This prole option allows the masking of the internal bank account number. You can set this prole option atthe site or user level. The prole option default is set to No Masking at the site level. You can select Display rstfour or Display last four digits. For example, an internal bank account number of XXXX8012 displays the lastfour digits and masks all the rest. This prole option aects only the internal bank accounts.

4. Use Existing Banks and Branches

Enable this prole option to pre-load the bank branch data information when creating an employee or ad hocpayee bank account. You can choose to pre-load the bank branch data and have your employees select thepre-loaded data when entering their bank accounts. Alternatively, you can have your employees enter all thebank, branch, and account information related to their account. Customers can set their preference to pre-loadthe bank branch data through this prole. You can set this prole option at the site or user level. By default, theprole option is set to No and that means pre-loaded information can't be used. In this case, the Bank, BankCode, Bank Branch, Branch Number, and BIC Code elds will be displayed as free text eld, and a new bank andbank branch will be created for the bank account.

If the bank name isn't entered, the default name CE_EMP_UNSPECIFIED_BANK will be used. If the branch nameisn't entered, the default name CE_EMP_UNSPECIFIED_BRANCH will be used.

If you set the prole option to Yes, the existing bank and branch information is available and displayed in thelist of values when creating the employee or ad hoc payee bank account.



249

Overview of Parse Rule SetsOracle Fusion Cash Management supports parse rule sets to transform data during the bank statement import process.Parse rules are used to move data from one eld to another. The parse rule set is associated to a bank account in thebank account setup. The parse rule set is most commonly used to parse data from the statement line addenda eld intomore specic statement line elds. Each parse rule within a parse rule set consists of the following elds:

• Sequence: Determines the order in which to process the rules.

• Transaction Code: The code used to determine the statement line type.

• Source Field: The interface table eld that contains the data to be parsed.

• Target Field: The statement line eld that the data is to be parsed to.

• Rule: Contains the syntax for determining the data within the source eld to be parsed.

• Overwrite: Used to control whether to overwrite existing data in a target eld or skip parsing the data.

The parse rule syntax is described in the following:

[LITERAL](<[MATCHING TOKEN],[START-END]>)[LITERAL]

Where

LITERAL represents a string or character value represented by an identier that should match the source data exactly.

MATCHING TOKEN represents a token (or set of tokens) which describes the data to extract. The following table lists thevalid tokens with their descriptions:

Token Description

N

Extract a valid number

.

Decimal position

X

Extract an alphanumeric

~

Extract everything in the source eld from the parse position to either the end of the data or upto the next literal.

START

A position to begin extracting data, oset 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.

The following table lists some examples:



250

Description Source Data Rule Target Data

Extract numeric rate data froma source eld

EST/TRX RTE 3.76 USD/LIBOR CPTY: PRU

RTE (N.NN)

3.76

Extract value date from asource eld

Dt.01/01/2011? Receipt

Dt.(1-10)? Receipt

01/01/2011

Extract check number from asource eld

Account Number 1005

Account Number.(X~)

1005

Extract currency from a sourceeld

$^EUR:Dt

$^(1-3):Dt.

EUR

Extract the counterparty of anunknown string length fromthe same source eld

EST/TRX RTE 3.76 USD/LIBOR CPTY:PRU

CPTY: (X~)

PRU

Extract the currency fromthe same source eld usingpositional matching

PRU EST/TRX RTE 3.76 USD/LIBOR CPTY PRU

RTE(7-9)

USD

Extract Contract ID fromAdditional Entry Information

TXT:AR:ReceiptNum: CEF-1: For:2010$^USD:Dt01/01/2011ReceiptMethod: CE-Foreign: ReceiptType: Standard: BU:VisionOperations: Customer: Worldof Business: Account No.1001

Account Number(NNNN)

1001

Extract Transaction ID fromCustomer Reference

CustRef # [email protected]

CustRef (X~).com

# A.23@orlc

Overview of Transaction Type MappingThe transaction type mapping enables you to associate a cash transaction type to an application transaction.

The following must be created to associate and mapped to cash transaction types:

• Oracle Fusion Account Payables payment methods

• Oracle Fusion Account Receivables payment methods

• Oracle Fusion Payroll payment types

Assigning cash transaction types to application transactions result in a more ecient bank statement reconciliationprocess.



251

Bank statement lines are also associated with cash transaction types and matching rules can be created using thiscommon aribute.

Overview of Tolerance RulesTolerance rules enables you to specify date and amount tolerances that prevent or warn you when reconciliation wouldbe a breach of a dened tolerance.

• Amount tolerances are most often used when reconciling foreign currency transactions where there may bedierences due to rounding or uctuations in the conversion rate. They can also be used if a bank includes aprocessing fee in the bank statement line amount.

• Date tolerances are primarily used for checks that may be issued on one day and not clear the bank until daysor weeks later.

Consider the following when dening your tolerance rules:

• Applying tolerances you can automate the reconciliation and accounting for these types of transactions.

• If no date or amount tolerance is dened within a rule, it requires an exact match.

• For manual reconciliation, a tolerance rule can optionally be assigned to a bank account.

• For automatic reconciliation, a tolerance rule can be associated with a matching rule in the Rule Set setupand can be applied if the matching rule matches on date and amount or both. However, when you assigna tolerance rule that includes amount tolerances to a matching rule that isn't a one to one match type, theamount tolerance is ignored.

Date ToleranceReconciliation date tolerances are dened as day ranges. The date tolerances are to validate that the source transactiondate 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 specied in the tolerance rule assigned to the bank account it applies to allmatching scenarios. In the event of a date tolerance breach, a warning message is displayed, but the user is allowed toreconcile the statement line or lines and the transaction or transactions. If no date tolerance is assigned or specied it'srequired 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 thematching rule matches on the date, then the date tolerance is applied. In this scenario a date tolerance breach preventsreconciliation.

Amount ToleranceReconciliation amount tolerances can only be used in one to one matching scenarios for both manual and automaticreconciliation. No reconciliation amount tolerances are allowed in one to many, many to one, or many to manymatching scenarios. In these scenarios the amount of the bank statement line or lines must be equal to the amount ofthe transaction or transactions. Reconciliation amount tolerances can be dened as percentage or amount ranges or



252

both. If both percentages and amounts are applied, the application uses the most conservative tolerance dependingupon 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 rst calculates the percentage amount (1% of $100 dollars =$1). It then compares this to the $5 amount and uses the smaller amount. In this case it's $1 dollar, so to reconcile atransaction to this line it must be between $99 and $101.

In automatic reconciliation, a tolerance rule that includes percentage, amount, or both types of tolerance ranges can beassociated with a matching rule. But the tolerance can only be applied if the matching rule is a one to one match typerule. In this scenario of a one to one type match, any amount dierence within tolerance is automatically created as anexternal transaction in cash management.

Reconciliation Matching RulesReconciliation Matching rules help you match bank statement lines and system transactions to minimize the need formanual intervention.

Dene bank statement automatic reconciliation matching rules and assign them to bank statement automaticreconciliation rule sets. After you assign the rule sets to the bank account, the Autoreconciliation process picks up thereconciliation matching rules to achieve a higher match rate.

Specify the following for each matching rule:

• Transaction Sources: Payables, Receivables, Payroll, Journals or External.

• Matching Type: One to One, One to Many, Many to One, or Many to Many. The following table explains thedierent matching types available in Oracle Fusion Cash Management:

Matching Type Description

One to One

A bank statement line is matched with a system transaction and reconciled against eachother

One to Many

A bank statement line is reconciled against many system transactions

Many to One

Many bank statement lines are grouped and reconciled against a system transaction

Many to Many

Many statement lines are grouped and reconciled against many system transactions

• Grouping Aributes: Used to group bank statement lines and system transactions based on the matching typeyou select. The combination of the aributes you select also determine what you can use as the matchingcriteria. You can use date, transaction type, and reconciliation reference as matching criteria only after youselect these as grouping aributes. The following table displays the required grouping aributes for a selectedmatching type:



253

Matching Type Statement Line Grouping Aributes System Transaction GroupingAributes

One to One

Not applicable

Not applicable

One to Many

Not applicable

Grouping aributes required

Many to One


Not applicable

Many to Many



In Many to One matching the grouping aributes are used to group bank statement lines. In One to Manymatching the grouping aributes are used to group system transactions.

The following is a list of common grouping aributes that can be used to group bank statement lines:

◦ Transaction date

◦ Structured payment reference

◦ Transaction currency

◦ Transaction type

◦ Reconciliation reference

◦ Bank transaction code

◦ Transaction code identier

◦ Counterparty bank account

The following is a list of common grouping aributes that can be used to group system transactions:

◦ Bank deposit number

◦ Transaction date

◦ Business unit

◦ Counterparty bank account

◦ Counterparty name

◦ Journal batch name

◦ Journal line description

◦ Journal name

◦ Payment le identier

◦ Payment process request name

◦ Payment instruction identier

◦ Payment server order number



254

◦ Logical group number

◦ Payment method

◦ Structured payment reference

◦ Receipt batch number

◦ Receipt class

◦ Reconciliation match date


◦ Remiance batch number

◦ Unique remiance identier

◦ Transaction currency

◦ Transaction Type

◦ Transaction source

• Matching Criteria: Includes a list of commonly used matching aributes. You can simply select the aributes toinclude them in the matching rule you selected. The selected aributes dene the matching conditions betweenthe bank statement lines and the system transactions to be matched successfully when they're reconciled.

Note: On the Create Reconciliation Matching Rule page the delivered seing for the matching typeis One to One, and the check boxes for Reconciliation Reference, Date and Transaction Type areenabled. When you change the matching type to One to Many or Many to One or Many to Many, thecheck boxes are disabled.

The matching criteria aributes are:

◦ Amount

◦ Date


◦ Transaction type

• Advanced Matching Criteria: Enables you to specify additional matching logic or ltering conditions that mustbe true for the bank statement lines and system transactions to match successfully. Consider the following:

◦ You have the option to enable or disable the Case Sensitive Comparison check box while creating acondition.

◦ The data types on either side of the expressions, must be the same and correspond to each other whenselected to match in the criteria. For example, if the aribute Statement Booking Date is selected on oneside, then Transaction Date can be selected as the matching criteria. Date is the data type that's the sameand corresponds to your search.

◦ For literal expression type, the operand value should match the database value. For example:Statement.Transaction Type equals ACH



255

The list of statement aributes available in the Create Condition page diers according to the matching typeyou select. The following lists some of the common statement aributes:

◦ Statement.Account servicer reference

◦ Statement.Additional entry information

◦ Statement.Booking date

◦ Statement.Check number

◦ Statement.Clearing system reference

◦ Statement.Contract ID

◦ Statement.Counterparty bank account

◦ Statement.Customer reference

◦ Statement.End to End ID

◦ Statement.Instruction ID

◦ Statement.Instruction ID

◦ Statement.Reconciliation match amount

◦ Statement.Reconciliation reference

◦ Statement Structured Payment reference

◦ Statement.Transaction ID

◦ Statement.Transaction currency

◦ Statement.Transaction type

◦ Statement.Value date



256

The list of transaction aributes available in the Create Condition page diers according to the matching typeyou select. The following lists some of the common transaction aributes:

◦ Transaction.Bank deposit number

◦ Transaction.Business unit

◦ Transaction.Counterparty name

◦ Transaction.Counterparty site

◦ Transaction.Journal Batch Name

◦ Transaction.Journal Line Number

◦ Transaction.Journal Name

◦ Transaction.Payment reference

◦ Transaction Payment Process Request Name

◦ Transaction Payment le identier

◦ Transaction Payment instruction identier

◦ Transaction.Receipt batch number

◦ Transaction.Reconciliation match amount

◦ Transaction.Reconciliation match date

◦ Transaction.Remiance batch number

◦ Transaction Structured Payment reference

◦ Transaction.Status

◦ Transaction.Transaction currency

◦ Transaction.Transaction date

◦ Transaction.Transaction number

◦ Transaction.Transaction source

◦ Transaction.Transaction type

◦ Transaction.Logical Group Number

◦ Transaction.Payment Server Order Number

◦ Transaction.Payment Reference

◦ Transaction.Unique Remiance Identier

◦ Transaction.Party bank account

You can select one or multiple transaction sources in a rule. Consider the following:

• If multiple sources are selected in a one to one or many to one matching rule, the autoreconciliation programlooks for a matching transaction across the selected sources.

• If multiple sources are selected in a one to many or many to many matching rule, the program rst nds allavailable transactions across the selected sources and then applies grouping rule to the whole data pool. Thismeans that the statement lines can be reconciled to a group that includes transactions across the dierentsources.

• If you want transactions included in a group to be from the same transaction source then you can specifyTransaction Source as a grouping aribute.



257

Note

Cash Management supports the journal reconciliation reference import using spreadsheet based tools such as,le-based data import and the Oracle Fusion ADF Desktop Integration.

Once the required setups are completed the reconciliation reference is uploaded and stored to the journal lines.

Related Topics

• Automatic Reconciliation

• Set Up Clearing Accounts Reconciliation

• Reconciliation References and Journal Lines

Overview of Reconciliation Rules SetsBank statement reconciliation rule sets are a group of matching rules and tolerance rules. They are assigned to a bankaccount and used to reconcile bank statement lines with transactions.

Consider the following when creating your rules:

• Build the rule set and the rule set detail as a parent-child relationship.

• Each rule set consists of one or more matching rules that can be prioritized or sequenced.

• The rules should be ordered to achieve a greater reconciliation success rate. It's strongly recommended thatone to one rules be sequenced ahead of rules of other types.

• To provide an optimum reconciliation rate, you should change the sequence number depending on howaccurately 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 higherreconciliation rate. These rules should be placed at the beginning with a lower sequence number. Conversely,transactions with no reference ID are likely to have duplicates or lower reconciliation rates, and you should place themat the end with a higher sequence number.

Automatically Reconciling Rejected Payments

You must enable the Opt in feature, Automatic Reconciliation of Reject Payments to automatically reconcile rejectedpayments reported on the imported bank statement. Follow these steps to enable the feature:

• Select the transaction type as Reversal in the bank transaction code.

• The application identies the rejections on the bank statement lines with this transaction code and reversalindicator.

• The autoreconciliation process identies the rejection and un-reconciles the original seled payment andreconciles the original statement line with the rejected statement line.

http://www.oracle.com/pls/topic/lookup?ctx=fa20a&id=8DF472C3EBFBFB78E040D30A68816F6C

http://www.oracle.com/pls/topic/lookup?ctx=fa20a&id=4C47C0F879555584E05362C3F00A73E0

http://www.oracle.com/pls/topic/lookup?ctx=fa20a&id=4C4A6AB0ED5D51DEE05362C3F00A38FB



258

Overview of Bank Statement Transaction CodesBank statement transaction codes are the internal codes that are used on a bank statement line to identify the type oftransaction being reported. These are also referred to as:

• Transaction codes

• Statement codes

The following codes are examples:

• 115- Lockbox Deposit

• 475- Check paid

• 698- Miscellaneous Fee

Oracle Fusion Cash Management maintains a single set of these codes and transform externally reported transactioncodes from other formats into this single normalized set. You can use code map groups to map transaction codesreported on the external data le to the ones dened internally in the application. This conguration is done throughOracle Fusion Payments Code map group setup.

How You Map Congurable BAI2 Transaction CodesWhen importing BAI2 bank statements, the ow indicator (DR/CR) of the bank statement line is determined by thetransaction code associated to that line.

Congurable BAI2 transaction codes can be mapped to standard BAI2 codes to derive the desired statement line owindicator when the le is imported.

Mapping Congurable BAI2 Transaction CodesIn this example, a credit code of 856 and a debit code of 868 are mapped as transaction codes using the following steps:

1. In the Setup and Maintenance work area, go to the following:2. Oering: Financials3. Functional Area: Payments or Customer Payments4. Task: Manage Code Map Groups5. Search for the Name: BAI2 Bank Statements and click edit.6. In Mappings, enter a new record Field: CE_TRX_CODE.7. For the parent CE_TRX_CODE, add 2 rows in the Field values enter the following:

Line Number Input and Output Values

Line 1

Enter Input Value: 856, Output Value: 275 (standard CREDIT BAI2 code).

Line 2 Enter Input Value: 868, Output Value: 575 (standard DEBIT BAI2 code).



259

Line Number Input and Output Values

8. Save and Close.9. After loading and importing the BAI2 format bank statement, result in the following:

Transaction Code Results

Dened Input Value: 856

Are imported with code 275 and the ow indicator as CREDIT.

Dened Input Value: 868

Are imported with code 575 and the ow indicator as DEBIT.

Overview of Bank Statement Transaction Creation RulesBank Statement Transaction Creation Rules are used by Oracle Fusion Cash Management to identify an unreconciledbank statement line or lines and create and account for a transaction.

Congure Bank Statement Transaction Creation Rules by specifying some of the aributes and characteristics of thecreated transactions. Consider the following when conguring your rules:

• Create as a separate business object.

• Assign to a bank account in the Manage Bank Account page.

• Arrange in order and group to be processed sequentially.

The group of sequenced rules on the bank account constitutes the bank accounts rule set that's used when running theBank Statement Transaction Creation program.

Process the Bank Statement Transaction Creation Rules by running the Bank Statement Transaction Creationprogram to create transactions from unreconciled bank statement lines. The program is used to create transactions andaccount for rst notice items such as bank charges, fees, or interest. You must perform the following prior to runningthe program.

• Run autoreconciliation for the bank statement.

• Perform any manual reconciliation on the bank statement.

This avoids creating external transaction from bank statement lines that already have transactions recorded in theapplication.

Create Banks, Branches, and Accounts in Spreadsheet



260

Overview of Cash Management Rapid ImplementationUse Microsoft Excel templates to rapidly implement the following setup objects:

• Banks

• Bank Branches

• Bank Accounts

Functional Setup Manager TasksThe following are the Functional Setup Manager tasks that are required to be performed to rapidly create the setupobjects data. To access these tasks, create an implementation project that includes the Dene Financials Congurationfor Rapid Implementation task list:

• Create Banks, Branches, and Accounts in Spreadsheet: Downloads the rapid implementation excel spreadsheettemplate. Enter the bank, branch, and bank account data in this spreadsheet, and generate the data le to beloaded.

• Upload Banks, Branches, and Accounts: Launches the Upload Banks, Branches, and Accounts process with thedata le to be uploaded as the parameter. You must upload the data le generated from the previous task.

Preparing DataPrepare your bank, branch, and account information to enter into the spreadsheet template.

• Bank information requires the country, name, and number.

• Branch information requires name, number, BIC code, and alternate name.

• Account information requires name, number, currency, legal entity, type, and IBAN.

After you nish preparing the data in the spreadsheet, click the Generate Banks, Branches, and Accounts File buon.Save the generated XML le.

Loading DataUse the following steps to load your data.

• In the Setup and Maintenance work area, create an implementation project that includes the Dene FinancialsConguration for Rapid Implementation task list. From your implementation project, go to the Upload Banks,Branches, and Accounts task. This task launches the Upload Banks, Branches, and Accounts process.

• Select the XML le you have saved earlier and submit the process.

• Verify in the process monitor that the process completed successfully.

• Review the banks, branches, and accounts created.

Best PracticesThe following are recommended best practices:

• Determine the Legal Entity for each bank account. The Legal Entity must be associated to a primary ledger.

• Determine the use for each bank account: Payable, Receivable, or both.

• Determine the Cash and Cash Clearing account for each bank account. Enter the entire account combinationbased on your chart of accounts, for example 01-000-1110-0000-000.



261

Related Topics

• How You Process Electronic Bank Statements

Seing Up Cash Positioning and Forecasting

How You Set Up Oracle Fusion Payments for Cash ManagementTo make ad hoc payments you must do the following:

• Create a payee in Oracle Fusion Cash Management.

• Review the Payment Methods in the tab; Usage Rules, for Cash Management in Oracle Fusion Payments.

• Review the payment method defaulting rules in Oracle Fusion Payments and prioritize the Cash ManagementPayment Method accordingly.

Creating a payee in Cash Management is a separate task than seing up suppliers in procurement. The setup done inCash Management is strictly used for making ad hoc payments from the application. You must also review and edit theset ups in Payments to successfully make payments.

Creating a Payee in Cash Management1. Create the payee in Cash Management. Enter the following payee information:

Field Required Description

Name

Yes

Name of the payee.

Tax Registration Number

No

Description of the payee.

Tax Registration Number

No

Unique identier assigned to a payee bya tax authority.

Active

No, but recommended.

Check box indicating if the payee is activeor inactive.

2. Create the bank account information. Enter the following bank account information:

Field Description

Country

Country of the bank where the bank account belongs.

Account Number

Bank account number of the payee bank account.

Currency Currency of the payee bank account

http://www.oracle.com/pls/topic/lookup?ctx=fa20a&id=9D59AD565DB80ED6E040D30A6881685C



262

Field Description

Account Type

Type of payee bank account. For example, checking or savings.

Check Digit

The account number validation.

Account Name

Name of the bank account holder.

Secondary Account Reference

Additional account reference such as the Building Society Role Number in the UK.

Bank

Name of the payee bank.

Bank Branch

Name of the payee bank branch.

Routing Transit Number

The routing transit number for electronic transfers.

BIC Code

The code used to SWIFT to identify the bank or bank branch.

Active

Check to indicate the bank account is active. The default is set to active.

3. Click the Save and Close buon to save your information.

Seing Up Usage Rules in Oracle Fusion Payments for Cash Management1. Navigate to Oracle Fusion Payments and the Create Payment Methods page.2. Enter the following required elds: Name, Code, and From Date.3. Select the Usage Rules tab.4. Select the Cash Management tab5. Select the check box Enable for use in Cash Management.6. Determine select All or Specic.7. Review the delivered Payment Process Transaction Types for Cash Management. Apply the appropriate

payment types. The valid values are:

◦ Bank Account Transfer

◦ Ad Hoc Payment

8. Review the payment method defaulting rules in Oracle Fusion Payments and prioritize the Cash ManagementPayment Method accordingly.

Related Topics

• Payment Methods

• Payment Method Defaulting

• Usage Rules



263

How You Set Up Cash Positioning and ForecastingUse the following to set up your cash positioning and forecasting reporting requirements:

• Specify Cash Positioning and Forecasting Options

• Manage Cash Positioning and Forecasting Transaction Grouping

Specify Cash Positioning and Forecasting OptionsUse the options page to dene the extraction period used to transfer data to the Essbase cube. Transactions withtransaction dates within that period are extracted to the cube. You can also select dierent GL accounting calendars tolay out the time dimension structure in the cubes.

Congure the following options:

Field Name Available Values Default Value

Extraction Duration

• Last 3 months• Last 6 months• Last 1 year• Last 2 years• Last 3 years

Last 2 years

Reporting Currency

List of currencies dened in theapplication

USD - US Dollars

Balance Code

Internal Balance Codes lookups (LOV)

Closing booked

Balance Date Threshold Days

Number days dened before a missingbank statement is reported

2

Transaction Calendar

List of transaction calendars dened in theapplication, if not dened, everyday (7) isconsidered a business day.

No default

Time Periods

List of accounting calendars dened in theapplication

No default

Note: Once the cube is created and locked, the update is disabled in this page. You can't update the cube untilyou submit the Cash Position Data Deletion program to clear the details in the cube.

Manage Cash Positioning and Forecasting Transaction GroupingYou create or edit congurable dimensions for cash positioning and forecasting from this page. You must have theManage Cash Positioning and Forecasting Transaction Grouping privilege to access the Create or Edit Cash PositionDimension page:

• Search for the congurable dimensions dened in the application.



264

• Create congurable dimensions to meet your company-specic requirements

• Modify and edit congurable dimensions to meet reporting requirements.

• Entering a description is optional but recommended.

The following table contains the elds to be completed:

Field Name Description

Name

Required and must be unique

Application

Required and valid values are Oracle Fusion Applications or Other.

Source Required and the following are possible values:

• Payables invoices• Payables payments• Receivables receipts• Receivables transactions• Bank statement• External cash transactions

Source Table

List of tables from the selected Application and Source

Source Column

List of the columns from the selected Source Table.

Note: Once the cube is created and locked, you can't update this page. You must submit the Cash PositionData Deletion program to clear the details in the cube to do an update.

Related Topics• Overview of Cash Positioning and Forecasting• Cash Positioning• Considerations for Cash Forecasting

Bank Account Validation

Bank Account Validation by Country: Albania to GuatemalaThis outlines the country specic bank account validation rules performed in Oracle Fusion Cash Management.

The following countries have country specic validations:

• Albania

• Algeria

• Andorra

http://www.oracle.com/pls/topic/lookup?ctx=fa20a&id=1C18AEB34C6C5DF9E05362C3F00A2F78

http://www.oracle.com/pls/topic/lookup?ctx=fa20a&id=1C18AEB34C6D5DF9E05362C3F00A2F78

http://www.oracle.com/pls/topic/lookup?ctx=fa20a&id=1C18AEB34C6E5DF9E05362C3F00A2F78



265

• Argentina

• Australia

• Austria

• Azerbaijan

• Bahrain

• Belarus

• Belgium

• Bosnia and Herzegovina

• Brazil

• British Virgin Islands

• Bulgaria

• Canada

• Columbia

• Costa Rica

• Croatia

• Cyprus

• Czech Republic

• Denmark

• Dominican Republic

• Egypt

• El Salvador

• Estonia

• Faroe Islands

• Finland

• France

• French Guiana

• Georgia

• Germany

• Gibraltar

• Greece

• Greenland

• Guadeloupe

• Guatemala

When entering bank accounts, dierent countries can have certain rules governing the format and content of thefollowing related elds:

1. Bank Code2. Branch Number



266

3. Account Number4. Check Digit5. IBAN

Use the Disable Country Specic Bank Validations prole option to disable the country-specic validations pertainingto the bank code, branch number, account number, check digit, and IBAN. You can set this prole option at the siteor user level. The prole is predened with a default value of No at the site level. If the prole is set to Yes, thesevalidations aren't performed. The checks for unique banks, branches, accounts, and the mandatory requirement ofbank account number aren't aected by this prole.

AlbaniaValidation Rules

The elds are checked for validity by adopting the following rules:

Field Rule

Bank Code• Optional

Branch Number• Optional

Account Number• Mandatory

Check Digit• Optional

IBAN• Optional, if entered, the following rules apply.• The modulus-97 rule is used to calculate the validity of the IBAN.• Length can't be more than 28 characters. Spaces are removed from the left and right.

Spaces in the middle aren't removed.• The rst 2 characters are leers.• The third and fourth characters are numbers.

AlgeriaValidation Rules



267


Field Rule







AndorraValidation Rules


Field Rule





IBAN• Optional, if entered, the following rules apply.• The modulus-97 rule is used to calculate the validity of the IBAN.• Length should be 24 characters. Spaces are removed from the left and right. Spaces in

the middle aren't removed.• The rst 2 characters are leers.• The third and fourth characters are numbers.

ArgentinaValidation Rules



268


Field Rule



Account Number• Mandatory• Length should be a maximum of 22 characters.• Spaces and hyphens are allowed.


IBAN• Optional

AustraliaValidation Rules


Field Rule

Bank Code• Optional• If entered, the length should be either 2 or 3 numeric characters.

Branch Number• Mandatory• The combined length of the Branch Number and Bank Code should be 6 numeric

characters. Hence, the valid length values (3,4,6) depend upon the Bank Code (3,2,0).• This eld is labeled as Bank State Branch.

Account Number• Mandatory• Length should be between 5 to 10 characters.• If the account currency is Australian Dollar, account number should be numeric. For

foreign currencies, alphanumeric values are allowed






269

AustriaValidation Rules


Field Rule

Bank Code• Optional• Length should be of 5 numeric characters.

Branch Number• Optional• Length should be of 5 numeric characters.

Account Number• Mandatory• Length should be between 4 to 11 numeric characters.


IBAN• Mandatory• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.

This bank account is dened in a country that requires IBAN for paymentprocessing.

• The modulus-97 rule is used to calculate the validity of the IBAN• Length should be 20 characters. Spaces are removed from the left and right. Spaces in


AzerbaijanValidation Rules


Field Rule





IBAN• Optional, if entered, the following rules apply.• The modulus-97 rule is used to calculate the validity of the IBAN.



270

Field Rule

• Length can't be more than 28 characters. Spaces are removed from the left and right.Spaces in the middle aren't removed.

• The rst 2 characters are leers.• The third and fourth characters are numbers.

BahrainValidation Rules


Field Rule







BelarusValidation Rules



271


Field Rule







BelgiumValidation Rules


Field Rule



Account Number• Mandatory• Length should be of 12 numeric characters.• It should be in the format 999-9999999-99.• A check algorithm is applied on the Account Number.




• The modulus-97 rule is used to calculate the validity of the IBAN.• Length should be 16 characters. Spaces are removed from the left and right. Spaces in

the middle aren't removed.• The rst 2 characters are leers.



272

Field Rule

• The third and fourth characters are numbers.

Check Algorithm for Account Number

1. The entered check digit CD1, is the last two digits of the Account Number2. The calculated check digit CD2, is derived by concatenating the rst two sections of the Account Number and

calculating the remainder on dividing this by 97. If the remainder is equal to 0, then the calculated check digit'staken to be 97.

3. If the entered check digit (CD1) and calculated check digit (CD2) are equal, then the Account Number is valid,else the check has failed.

4. Additionally, if the entered check digit (that's, the last section) is '00', then the Account Number is invalidbecause the calculated check digit can never be 00 as per the 3rd point.

Example using account number 123-4567890-78

◦ The entered check digit (CD1) is '78'. The concatenation of the rst two sections gives '1234567890'

◦ Divide the result by '97'. 1234567890 / 97 = 12727504

◦ Derive the remainder. 1234567890 - (12727504 * 97) = 2 Therefore CD2 = 2

◦ Here CD1 <> CD2, therefore the Account Number isn't valid.

In this case, a valid Account Number would be '123456789-02'.

Bosnia and HerzegovinaValidation Rules


Field Rule











273

BrazilValidation Rules


Field Rule

Bank Code• Mandatory• Length should be a maximum of 3 numeric characters.• If the length is less than 3, then it's converted to a 3 digit number by prexing it with as

many leading zeroes as is necessary.

Branch Number• Mandatory• Length should be a maximum of 5 numeric characters.



Company Code• Optional.• This is entered in the Account Creation form.• If entered, length should be a maximum of 15 numeric characters

Secondary Account Reference• This eld is labeled as Company Code.



British Virgin IslandsValidation Rules



274


Field Rule





IBAN• Optional, if entered, the following rules apply.• The modulus-97 rule is used to calculate the validity of the IBAN.• Length can’t be more than 24 characters. Spaces are removed from the left and right.


BulgariaValidation Rules


Field Rule











275

CanadaValidation Rules


Field Rule


Branch Number• Optional• This eld is labeled as Routing Transit Number.





ColumbiaFor Colombia, there are no validations for Bank Code, Branch Number, Account Number, or Check Digit elds asillustrated in the following table:

Field Rule





Tax Payer ID• Optional• Length should be a maximum of 15 numeric characters 14 digits for Tax Payer ID plus

the last digit for check digit.• it's unique within the country.• Cross Validations of Tax Payer ID in Customers, Suppliers, and Companies. If the Tax

Payer ID is used by a Customer, Supplier, or a Company, then the Customer name,Supplier name, or the Company name should match with the Bank name.



276

Field Rule

• A check digit's applied on the Tax Payer ID.



Check Algorithm for Tax Payer ID

The rst 15 digits are multiplied by the associated factor, as illustrated in the following table.

Digit Factor

1st

71

2nd

67

3rd

59

4th

53

5th

47

6th

43

7th

41

8th

37

9th

29

10th

23

11th

19

12th

17

13th

13



277

Digit Factor

14th

7

15th

3

1. These 15 products are added and the sum is divided by 11.2. If the remainder is 1 or 0, then the Check Digit should be 1 or 0 respectively.3. If the remainder isn't 1 or 0, then the remainder is subtracted by 11 and that should be the Check Digit.

Costa RicaValidation Rules


Field Rule







CroatiaValidation Rules



278


Field Rule









CyprusValidation Rules


Field Rule











279

Field Rule


Czech RepublicValidation Rules


Field Rule









DenmarkValidation Rules



280


Field Rule



Account Number• Length should be a maximum of 10 numeric characters






Dominican RepublicValidation Rules


Field Rule









281

EgyptValidation Rules


Field Rule







El Salvador.Validation Rules


Field Rule









282

EstoniaValidation Rules


Field Rule









Faroe IslandsValidation Rules


Field Rule






Spaces in the middle aren't removed.• The rst 2 characters are leers.



283

Field Rule


FinlandValidation Rules


Field Rule


Branch Number• Optional• If entered, it should be 6 numeric characters.

Account Number• Mandatory• Length should be between 8 to 14 numeric characters.• A check algorithm is applied on the Account Number.

Check Digit• Optional• If entered, it should be 1 numeric digit.





If 1st digit of Account Number is: Check Value Method

1

1

2

1

3

1

4

2

5

2



284

If 1st digit of Account Number is: Check Value Method

6

1

7

2

8

1

9

1

Method 1

The check is formed in the following two parts:

• The rst part of the check is formed from the rst 6 digits of the Account Number. To illustrate, if the accountnumber is 123456789, then the rst part of check would be created as 123456.

• The second part of check is formed as an eight digit value, comprising the 8th to 15th digits of the AccountNumber. If the length is less than 8, then it's converted to an 8 digit number by prexing it with as manyleading zeroes as is necessary. Using the same example, the second part of check would be created as00000089. check is then formed by concatenating the two parts. So, in our example the check is formed as12345600000089.

Method 2

The check is formed in the following three parts:

• The rst part of the check is formed from the rst 6 digits of the Account Number. To illustrate, if the accountnumber is 123456789, then the rst part of check would be created as 123456.

• The second part of check is formed as the 8th digit of the Account Number. Using the same example, thesecond part of check would be created as 8.

• The third part of check is formed as a seven digit value, comprising the 9th to 15th digits of the AccountNumber. If the length is less than 7, then it's converted to a 7 digit number by prexing it with as many leadingzeroes as is necessary. Using the same example, the second part of check would be created as 0000009.The check is then formed by concatenating the three parts. So, in our example the check is formed as12345680000009.

A computed sum is then calculated based on the value of the check. Dierent calculations are performed depending onthe rst two digits of the formed check value.

If the rst two digits of the check are '88', then:

• The Finnish government provides the following factor table. The 8th to 13th digits of the check number aremultiplied by the associated factor. The computed sum is then calculated by summing the totals.

Digit Factor

8th

1

9th 3



285

Digit Factor

10th

7

11th

1

12th

3

13th

7

Example using check number 88345600000089: Multiply the given digits with the given factor.

Digit Value Factor Result

8th Digit

0

1

0

9th Digit

0

3

0

10th Digit

0

7

0

11th Digit

0

7

0

12th Digit

0

3

0

13th Digit

8

7

56

TotalN/A

N/A

56

So the computed sum for this example is 56.

The test fails unless either of the following applies:

• The 14th digit of the check should equal the value of 10 minus the last digit of the computed sum. For the checkvalue is '88345600000089', the last digit of the computed sum is 6. So 10 - 6 = 4. So, the 14th digit of the checkshould equal 4. The test fails here as the 14th digit's 9.

• Both the 14th digit of the check and the last digit of the computed sum are 0. Using the same example, the testfails here as both values aren't 0.

If the rst two digits of the check aren't '88', then the computed sum is calculated for each of the rst 13 digits by addingthe even numbered digits to the following calculated sum for each odd numbered digit :

• Multiply the digit by 2.



286

• Divide the result by 10.

• From the result add the integer to the remainder.

Example using account number 123456800000089:

Digit Value Multiply (a) Divide (b) Integer Remainder Result

1st

1

2

0.2

0

2

2

2nd

2

N/A

N/A

N/A

N/A

2

3rd

3

6

0.6

0

6

6

4th

4

N/A

N/A

N/A

N/A

4

5th

5

10

1

1

0

1

6th

6

N/A

N/A

N/A

N/A

6

7th

0

16

1.6

1

6

0

8th

0

N/A

N/A

N/A

N/A

0

9th

0

0

0

0

0

0

10th

0

N/A

N/A

N/A

N/A

0

11th

0

0

0

0

0

0

12th

0

N/A

N/A

N/A

N/A

0

13th

8

16

1.6

1

6

7

TotalN/A

N/A

N/A

N/A

N/A

28

The computed sum is then converted using the following process, before being used to see if the Account Number isvalid:

1. Computed sum is added to 9.2. The result is divided by 10.3. The integer result is multiplied by 10.4. The result is subtracted by the original computed sum.



287

So the computed sum '282 is converted to '2' as:

1. 28 + 9 = 372. 37/10 = 3.7. Integer result therefore = 33. 3 * 10 = 304. 30 - 28 = 2

This number is then compared to the 14th digit of the Account Number. If it matches, then the test is passed, else it'sfailed.

In our example, the test fails as the 14th digit of the account number is 9. If the 14th digit had been 2, then the test wouldhave been passed.

FranceValidation Rules


Field Rule

Bank Code• Mandatory• Length should be a maximum of 5 numeric characters.• If the length is less than 5, then it's converted to a 5 digit number by prexing it with as


Branch Number• Mandatory• Length should be a maximum of 5 numeric characters.• If the length is less than 5, then it's converted to a 5 digit number by prexing it with as


Account Number• Mandatory• Length should be a maximum of 11 numeric characters• Special characters and spaces aren't allowed

Check Digit• Optional• If entered, length should be a maximum of 2 numeric characters.• A check algorithm is applied on the check digit.

Account Type• This eld is labeled as Deposit Type.





Check Algorithm for Check Digit



288

A check digit's calculated (CD1) from the Account Number, Bank Code, and Branch Number in the following manner.This is then used as the basis for the check digit validity test.

CDI

For the check algorithm, the digits of the Account Number entered as characters A to Z. are converted to numericvalues, the French government provides the following conversion table:

Value Conversion

A, J

1

B, K, S

2

C, L, T

3

D, M, U

4

E, N, V

5

F, O, W

6

G, P, X

7

H, Q, Y

8

I, R, Z

9

Example using account number A1234567890:

The leer A is converted by applying the table to 1, so the account number becomes 11234567890.

A value for CD1 is formed by joining together the bank elds in the following way:

• The Bank Code is concatenated with Branch Number concatenated to the converted Account Number. Toillustrate with the Bank Code as 12345, the Branch Number as 67890 and the converted Account Number as11234567890. Then CD1 is created as 123456789011234567890.

• To this concatenated value, 00 is added as a sux and the resulting value is divided by 97. The remainderobtained as result of this division is then subtracted from 97. The result of this subtraction is the calculatedcheck digit.

• In our example, suxing 00 gives 12345678901123456789000. Dividing by 97 and deriving the remainder. Mod(12345678901123456789000, 97) = 86 Subtract from 97. 97 - 86 = 11

• If the user entered Check Digit's equal to this calculated value, then the validation is successful.

In the given example, as the user entered check digit'sn't 11, the check isn't valid.



289

French GuianaValidation Rules


Field Rule









GeorgiaValidation Rules


Field Rule









290

Field Rule


GermanyValidation Rules


Field Rule

Bank Code• Optional• If entered, then the length should be 8 numeric characters.

Branch Number• Optional• If entered, then the length should be 8 numeric characters.• If the Bank Code and Branch Number are entered, then both values must match.

Account Number• Mandatory• Length should be a maximum of 10 numeric characters.

Check Digit• Optional• If a value is entered for the check digit, then it must be a single digit and must match the

last digit of the Account Number.





GibraltarValidation Rules



291


Field Rule









GreeceValidation Rules


Field Rule

Bank Code• Optional• If entered, then the length should be of 3 numeric characters.

Branch Number• Optional• If entered, then the length should be of 4 numeric characters.

Account Number• Mandatory• Length should be between 8 to 16 alphanumeric characters.

Check Digit• Optional• If a value is entered, then it must be one numeric character.




the middle aren't removed.



292

Field Rule


GreenlandValidation Rules


Field Rule







GuadeloupeValidation Rules


Field Rule





IBAN• Mandatory



293

Field Rule

• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.This bank account is dened in a country that requires IBAN for paymentprocessing.

• The modulus-97 rule is used to calculate the validity of the IBAN.• Length should be 34 characters. Leading and trailing spaces are ignored. There should

be no spaces in the middle. .• The rst 2 characters are leers.• The third and fourth characters are numbers.

GuatemalaValidation Rules


Field Rule







Bank Account Validation by Country: Hungary to NorwayThis outlines the country-specic bank account validation rules performed in Oracle Fusion Cash Management.

The following countries have country-specic validations:

• Hungary

• Iceland

• India

• Ireland

• Israel



294

• Iran

• Iraq

• Italy

• Ivory Coast

• Japan

• Jordan

• Kazakhstan

• Kosovo

• Kuwait

• Latvia

• Lebanon

• Liechtenstein

• Lithuania

• Luxembourg

• Malta

• Martinique

• Mauritania

• Mauritius

• Mayoe

• Mexico

• Moldova

• Monaco

• Montenegro

• Morocco

• Netherlands

• New Zealand

• Norway


1. Bank Code2. Branch Number3. Account Number4. Check Digit5. IBAN

Use the Disable Country Specic Bank Validations prole option to disable the country-specic validations pertainingto the bank code, branch number, account number, check digit, and IBAN. You can set this prole option at the siteor user level. The prole is predened with a default value of No at the site level. If the prole is set to Yes, these



295

validations aren't performed. The checks for unique banks, branches, accounts, and the mandatory requirement ofbank account number aren't aected by this prole.

HungaryValidation Rules


Field Rule









IcelandValidation Rules


Field Rule

Bank Code• Optional• If entered, then the length should be of 4 numeric characters.• If the length is less than 4, then it is converted to a 4 digit number by prexing it with as


Branch Number• Optional• If entered, then the length should be of 4 numeric characters.• If the Bank Code and Branch Number are entered, then both values must match.




296

Field Rule

• If the length is less than 18, then it is converted to an 18 digit number by prexing it withas many leading zeroes as is necessary.

• A check algorithm is applied on the Account Number.

Check Digit• Optional• If a value is entered for the check digit, then it must be a single digit and must match the

seventeenth digit of the Account Number.






1. Check algorithm is performed against the Account Number (from digit 9 to 16). Each of these digits is multipliedwith the factors as given in the following table:

Digit Factor

9th

3

10th

2

11th

7

12th

6

13th

5

14th

4

15th

3

16th

2

These products are added and the sum is divided by 11. The remainder obtained as a result of this division is subtractedfrom 11 to obtain the calculated check digit. If remainder is 0, then calculated check digit is taken as 0.



297

This calculated check digit should match the entered check digit (seventeenth digit of the Account Number), else theAccount Number isn't valid.

IndiaValidation Rules


Field Rule


Branch Number• Optional• This eld is labeled as the IFSC Code





IrelandValidation Rules


Field Rule

Bank Code• Optional• If entered, then the length should be of 6 numeric characters.

Branch Number• Optional• If entered, then the length should be of 6 numeric characters.• If the Bank Code and Branch Number are entered, then both values must match.

Account Number• Mandatory• Length should be 8 numeric characters.


IBAN• Mandatory



298

Field Rule

• If the IBAN isn't entered, a warning message is displayed: IBAN hasn't been entered.This bank account is dened in a country that requires IBAN for paymentprocessing.



IsraelValidation Rules


Field Rule

Bank Code• Mandatory• If entered, the length should be a maximum 2 numeric characters

Branch Number• Mandatory• Length should be 3 numeric characters.

Account Number• Mandatory• Length should be a maximum of 13 numeric characters.• Spaces aren't allowed.




IranValidation Rules



299


Field Rule







IraqValidation Rules


Field Rule







ItalyValidation Rules



300


Field Rule

Bank Code• Mandatory• Length should be a maximum of 5 numeric characters.

Branch Number• Mandatory• Length should be a maximum of 5 numeric characters.

Account Number• Mandatory• Length should be a maximum of 12 alphanumeric characters.• If the length is less than 12, then it is converted to a 12 digit number by prexing it with

as many leading zeroes as is necessary.

Check Digit• Optional• If entered, length should be a single alphabetic character and a check algorithm is

applied on the Check Digit.






The check digit is used to validate against the Bank Code, Branch Number, and Account Number. These areconcatenated to obtain a 22 character string.

Each character is assigned a value depending upon whether the character is in an odd position or an even position inthe string as given in the following table:

Even Position Values Odd Position Values

A/0 = 0

A/0 = 1

B/1 = 1

B/1 = 0

C/2 = 2

C/2 = 5

D/3 = 3

D/3 = 7

E/4 = 4 E/4 = 9



301


F/5 = 5

F/5 = 13

G/6 = 6

G/6 = 15

H/7 = 7

H/7 = 17

I/8 = 8

I/8 = 19

J/9 = 9

J/9 = 21

K = 10

K = 2

L = 11

L = 4

M = 12

M = 18

N = 13

N = 20

O = 14

O = 11

P = 15

P = 3

Q = 16

Q = 6

R = 17

R = 8

S = 18

S = 12

T = 19

T = 14

U = 20

U = 16

V = 21

V = 10

W = 22

W = 22

X = 23 X = 25



302


Y = 24

Y = 24

Z = 25

Z = 23

The rst character is an odd position. The values assigned are added up and the sum is divided 26.

The remainder obtained as a result of this division is converted into an alphabet as given in the following table:

Transformation Algorithm

Calculation Calculation Calculation

0 = A

9 = J

18 = S

1 = B

10 = K

19 = T

2 = C

11 = L

20 = U

3 = D

12 = M

21 = V

4 = E

13 = N

22 = W

5 = F

14 = O

23 = X

6 = G

15 = P

24 = Y

7 = H

16 = Q

25 = Z

8 = I

17 = R

N/A

This value should be the same as the user entered check digit or else the Check Digit validation fails.

Ivory CoastValidation Rules



303


Field Rule







JapanValidation Rules


Field Rule

Bank Code• Mandatory• Length should be 4 numeric characters

Alternate Bank Name• Optional


Alternate Branch Name• Optional


Account Type

• Mandatory• This eld is labeled as Deposit Type.


IBAN• Optional, if entered, the following rules apply.• The modulus-97 rule is used to calculate the validity of the IBAN.



304

Field Rule



JordanValidation Rules


Field Rule







KazakhstanValidation Rules



305


Field Rule







KosovoValidation Rules


Field Rule







KuwaitValidation Rules



306


Field Rule



Account Number• Mandatory• Length should be a maximum of 22 characters.• Spaces and hyphens are allowed.


IBAN• Optional, if entered, the following rules apply.• The modulus-97 rule is used to calculate the validity of the IBAN• Length can't be more than 30 characters. Spaces are removed from the left and right.


LatviaValidation Rules


Field Rule











307

LebanonValidation Rules


Field Rule







LiechtensteinValidation Rules


Field Rule











308

Field Rule


LithuaniaValidation Rules


Field Rule









LuxembourgValidation Rules


Field Rule


Branch Number• Optional• If entered, then the length should be 3 numeric characters.• If the Bank Code and Branch Number are entered, then both values must match.




309

Field Rule

• Length should be a maximum of 13 characters.

Check Digit• Optional• If entered, then the length should be 2 numeric characters





MaltaValidation Rules


Field Rule









MartiniqueValidation Rules



310


Field Rule









MauritaniaValidation Rules


Field Rule









311

MauritiusValidation Rules


Field Rule









MayoeValidation Rules


Field Rule







• The modulus-97 rule is used to calculate the validity of the IBAN



312

Field Rule

• Length should be 34 characters. Spaces are removed from the left and right. Spaces inthe middle aren't removed.


MexicoValidation Rules


Field Rule



Account Number• Mandatory• Length should be between 10 to 11 numeric characters.• Spaces and hyphens are allowed.


IBAN• Optional

Secondary Account Reference

• Optional• If entered:

◦ Should be of 18 digits

◦ Should be numeric

MoldovaValidation Rules



313


Field Rule







MonacoValidation Rules


Field Rule







• The modulus-97 rule is used to calculate the validity of the IBAN• Length can't be more than 27 characters. Spaces are removed from the left and right.




314

MontenegroValidation Rules


Field Rule









MoroccoValidation Rules


Field Rule









315

Field Rule


NetherlandsValidation Rules


Field Rule



Account Number• Mandatory• Two types of account numbers are validated:• If the bank account number is numeric and consists of one of the following then bank

account will be considered as Post or Giro Account.

◦ length is 7 digits or less, or

◦ prexed with 000, or

◦ prexed with P or G

There is no check digit validation for Post or Giro accounts.• For other account numbers, the length should be between 9 and 10 numeric characters.

A check algorithm is applied on the Account Number.






Check Algorithm for Non-Post or Giro Account Number

1. If the length is less than 10, then it is converted to a 10 digit number by prexing it with as many leading zeroesas is necessary.

2. The Netherlands government provides the following factor table for each of the 10 digits:

Digit Factor

1st 10



316

Digit Factor

2nd

9

3rd

8

4th

7

5th

6

6th

5

7th

4

8th

3

9th

2

10th

1

These are multiplied and the sum of the products is calculated 4.

If the result so obtained is perfectly divisible by 11 (that's, no remainder on division by 11), then the test is successful,otherwise the account number entered isn't valid.

New ZealandValidation Rules


Field Rule

Bank Code• Mandatory• Length should be 2 numeric characters.

Branch Number• Mandatory• Length should be 4 numeric characters.• This eld is labeled Bank State Branch.




317

Field Rule

• Account Sux should be between 2 to 4 numeric characters.


Description• This eld is labeled Reference.



NorwayValidation Rules


Field Rule



Account Number• Mandatory• Length should be of 11 numeric characters.• A check algorithm is applied on the Account Number, if the 5th and 6th digits of the

account number aren't 00.

For example, for Account Number, 1234001234, the check algorithm will not be applied but forAccount Number 02056439653, the check algorithm will be applied as outlined in the CheckAlgorithm for Account Number, following this table.









318

1. The check digit is set as the last (that's, the 11th digit) of the Account Number. For example, if the account number is02056439653, then the check digit is set to 3.

2. The Norwegian government provides the following factor table:

Digit Factor

1st

5

2nd

4

3rd

3

4th

2

5th

7

6th

6

7th

5

8th

4

9th

3

10th

2

The rst ten digits of the account number are multiplied by the associated factor. The computed sum is then calculatedby summing the totals.

3. Example using account number 02056439653:

Multiply each digit with the given factor. The following table illustrates the factors that determine validation:


1st

0

5

0

2nd

2

4

8

3rd

0

3

0



319


4th

5

2

10

5th

6

7

42

6th

4

6

24

7th

3

5

15

8th

9

4

36

9th

6

3

18

10th

5

2

10

TotalN/A

N/A

163


4. The computed sum is then added to the check digit. In the example, 163 + 3 = 166.

5. Divide the result by 11. 166 / 11 = 15 6.

6. Derive the remainder. 166 - (11 * 15) = 1.

7. If the remainder is '0', then the validation is successful, else the check fails.

8. In the given example, the check fails the Account Number as the remainder is 1. If the 11th digit of the AccountNumber was 2 (that's, the check digit would be 2), then the remainder would be 165 - (11 * 15) = 0 and the check on theAccount Number would be successful.

Bank Account Validation by Country: Pakistan to the United StatesThis outlines the country specic bank account validation rules performed in Oracle Fusion Cash Management.

The following countries have country specic validations:

• Pakistan

• Palestine

• Poland

• Portugal



320

• Qatar

• Reunion

• Romania

• Saint Barthelemy

• Saint Lucia

• San Marino

• Saint Martin

• Saint Pierre and Miquelon

• Saudi Arabia

• Serbia

• Serbia and Montenegro

• Senegal

• Seychelles

• Singapore

• Slovakia

• Slovenia

• Spain

• Sweden

• Switzerland

• The Former Yugoslav Republic of Macedonia

• Tunisia

• Turkey

• Ukraine

• United Arab Emirates

• United Kingdom

• United States


1. Bank Code2. Branch Number3. Account Number4. Check Digit5. IBAN

Use the Disable Country Specic Bank Validations prole option to disable the country-specic validations pertainingto the bank code, branch number, account number, check digit, and IBAN. You can set this prole option at the siteor user level. The prole is predened with a default value of No at the site level. If the prole is set to Yes, these



321

validations aren't performed. The checks for unique banks, branches, accounts, and the mandatory requirement ofbank account number aren't aected by this prole.

PakistanValidation Rules


Field Rule






Spaces in the middle aren't removed..• The rst 2 characters are leers.

PalestineValidation Rules


Field Rule









322

PolandValidation Rules


Field Rule

Bank Code• Optional• If entered, the length should be of 8 numeric characters.

Branch Number• Optional• If entered, the length should be of 8 numeric characters.• If the Bank Code and Branch Number are entered, then both values must match

Account Number• Mandatory• Length should be a maximum of 16 alphanumeric characters.






PortugalValidation Rules


Field Rule

Bank Code• Mandatory• Length should be of 4 numeric characters.

Branch Number• Mandatory• Length should be of 4 numeric characters.


Check Digit• Optional• Length should be of 2 numeric characters.



323

Field Rule

• If entered, a check algorithm is applied on the Check Digit.






• A check digit's formed (CD1) from the Bank Code, Branch Number, and Account Number by concatenating thethree numbers.

• For example, using Bank Code 1234, Branch Number 5678, and Account Number 12345678901. Then CD1 is setas 1234567812345678901.

• The Portuguese government provides the following factor table:

Digit Factor

1st

73

2nd

17

3rd

89

4th

38

5th

62

6th

45

7th

53

8th

15

9th

50

10th

5

11th 49



324

Digit Factor

12th

34

13th

81

14th

76

15th

27

16th

90

17th

9

18th

30

19th

3

The nineteen digits of the created check digit (CD1) are multiplied by the associated factor. The multiple sum is thencalculated by summing the totals.

Example using the value for CD1:


1st

1

73

73

2nd

2

17

34

3rd

3

89

267

4th

4

38

152

5th

5

62

310

6th

6

45

270

7th

7

53

371

8th 8 15 120



325


9th

1

50

50

10th

2

5

10

11th

3

49

147

12th

4

34

136

13th

5

81

405

14th

6

76

456

15th

7

27

189

16th

8

90

720

17th

9

9

81

18th

0

30

0

19th

1

3

3

TotalN/A

N/A

3794

• Divide the result by 97. 3794 / 97 = 39

• Derive the remainder. 3794 - (39 * 97) = 11

• CD1 is then derived by subtracting the remainder from 97. 97 - 11 = 86. So for this example CD1 = 86

• If the calculated value for CD1 isn't the same as the user entered check digit, then the check digit fails thevalidation. In the given example, unless the user entered check digit's 86, the validation will fail.

QatarValidation Rules



326


Field Rule







ReunionValidation Rules


Field Rule











327

RomaniaValidation Rules


Field Rule









Saint BarthelemyValidation Rules


Field Rule







• The modulus-97 rule is used to calculate the validity of the IBAN



328

Field Rule



Saint LuciaValidation Rules


Field Rule







San MarinoValidation Rules



329


Field Rule






This bank account is dened in a country that requires IBAN for payment processing.• The modulus-97 rule is used to calculate the validity of the IBAN.• Length can't be more than 27 characters. Spaces are removed from the left and right.


Saint Martin (French Section)Validation Rules


Field Rule











330

Saint Pierre and MiquelonValidation Rules


Field Rule









Saudi ArabiaValidation Rules


Field Rule

Bank Code• Optional• If entered, then the length should be a maximum of 4 characters


Account Number• Mandatory• Length should be a maximum of 25 characters.


IBAN• Optional, if entered the following rules apply.• The modulus-97 rule is used to calculate the validity of the IBAN• Length can't be more than 24 characters. Spaces are removed from the left and right.

Spaces in the middle aren't removed.



331

Field Rule

• The rst 2 characters are leers.

SenegalValidation Rules


Field Rule







SerbiaValidation Rules


Field Rule



Account Number• Mandatory.



the middle aren't removed.



332

Field Rule


Serbia and MontenegroValidation Rules


Field Rule









SeychellesValidation Rules



333


Field Rule







SingaporeValidation Rules


Field Rule

Bank Code• Mandatory• Length should be 4 numeric characters.




IBAN• Optional, if entered, the rules following apply.• The modulus-97 rule is used to calculate the validity of the IBAN• Length can't be more than 34 characters. Spaces are removed from the left and right.


SlovakiaValidation Rules



334


Field Rule









SloveniaValidation Rules


Field Rule











335

Field Rule


SpainValidation Rules


Field Rule

Bank Code• Mandatory• Length should be a maximum of 4 numeric characters.• If the bank code is less than 4 digits, then it's converted to a 4 digit number by prexing

it with as many leading zeroes as is necessary.

Branch Number• Mandatory• Length should be a maximum of 4 numeric characters.• If the bank code is less than 4 digits, then it's converted to a 4 digit number by prexing

it with as many leading zeroes as is necessary.

Account Number• Mandatory• Length should be 10 numeric characters.

Check Digit• Optional• If entered, length should be a maximum of 2 numeric characters.• A check algorithm is applied on the Check Digit.






Two check digits are calculated, CD1 from the Bank Code and Branch Number and CD2 from Account Number in thefollowing manner; these are then used as the basis for the check digit validity test:

CD1

1. For the Bank Code, the Spanish government provides the following factor table:

Digit Factor

1st 4



336

Digit Factor

2nd

8

3rd

5

4th

10

The four digits of the Bank Code are multiplied by the associated factor. The computed sum is then calculated bysumming the totals.

Example using Bank Code '1234':

Multiply each digit with the given factor.

Digit Value Factor Result Digit Value Factor Result Digit Value Factor Result Digit Value Factor Result

1st

1

4

4

2nd

2

8

16

3rd

3

5

15

4th

4

10

40

TotalN/A

N/A

75


2. For the Branch Number, the Spanish government provides the following factor table:

Digit Factor

1st

9

2nd

7

3rd

3

4th

6



337

The four digits of the Branch Number are multiplied by the associated factor. The computed sum is then calculated bysumming the totals.

Example using Branch Number '5678':



1st

5

9

45

2nd

6

7

42

3rd

7

3

21

4th

8

6

48

TotalN/A

N/A

156


3. The computed sums from both the Bank Code and Branch Number calculations are then summed up. According tothe example, it's 75 + 156 = 231.

4. Divide the result by 11.

231 / 11 = 21

5. Derive the remainder

231 - (11 * 21) = 0.

6.CD1 is then derived by subtracting the remainder from 11. If dierence is 11, then CD1 is 0 and if dierence is 10, thenCD1 is 1 11 - 0 = 11. So for this example, CD1 = 11 = 0.

CD2

1. For the Account Number, the Spanish government provides the following factor table:

Digit Factor

1st

1

2nd

2

3rd

4

4th 8



338

Digit Factor

5th

5

6th

10

7th

9

8th

7

9th

3

10th

6

The ten digits of the bank number are multiplied by the associated factor. The computed sum is then calculated bysumming the totals.

Example using account number '1234567890':



1st

1

1

1

2nd

2

2

4

3rd

3

4

12

4th

4

8

32

5th

5

5

25

6th

6

10

60

7th

7

9

63

8th

8

7

56

9th 9 3 27



339


10th

0

6

0

TotalN/A

N/A

280


2. Divide the result by 11

280 / 11 = 25

3. Derive the remainder.

280 - (11 * 25) = 5

4. CD2 is then derived by subtracting the remainder from 11. 11 - 5 = 6. So for this example CD2 = 6.

Check Digit Validity Test

The value in the user entered check digit eld is compared to the calculated CD1 and CD2 using the following checks, ifboth of the checks are true, then the validation is unsuccessful.

Check Description

1

CD1 is compared to the rst digit of the entered check digit eld.

2

CD2 is compared to the second digit of the entered check digit eld.

Example of the test using the previously calculated CD1 and CD2:

Where CD1 = 0 and CD2 = 6 and suppose the user entered Check Digit Value is '05'. As CD2 does not match, the checkdigit's invalid.

SwedenValidation Rules


Field Rule

Bank Code• Optional• If entered, then the length should be between 4 to 5 numeric characters.

Branch Number• Optional• If entered, then the length should be between 4 to 5 numeric characters.



340

Field Rule

• If the Bank Code and Branch Number are entered, then both values must match.


Check Digit• Optional• Length should be a single numeric character.





SwitzerlandValidation Rules


Field Rule

Bank Code• Optional• If entered, then the length should be between 3 to 5 numeric characters.

Branch Number• Optional• If entered, then the length should be between 3 to 9 numeric characters.



Account Type• Optional







341

The Former Yugoslav Republic of MacedoniaValidation Rules


Field Rule









TunisiaValidation Rules


Field Rule









342

Field Rule


TurkeyValidation Rules


Field Rule





IBAN• Mandatory• If the IBAN isn't entered, a warning message is displayed, IBAN hasn't been entered.




UkraineValidation Rules



343


Field Rule







United Arab EmiratesValidation Rules


Field Rule

Bank Code• Optional• If entered, the length should be a maximum of 4 characters.


Account Number• Mandatory• Length should be a maximum of 21 characters.




United KingdomValidation Rules



344


Field Rule


Branch Number• Mandatory• it's unique within the country.• Length should be a maximum of 6 numeric characters.• If the length is less than 6, then it's converted to a 6 digit number by prexing it with as

many leading zeroes as is necessary.• This eld is labeled as Sort Code.

Account Number• Mandatory• Length should be between 7 to 8 characters.• If the length is 7 characters, it's converted to 8 characters, by adding a zero as the lead

or rst character.


Secondary Account Reference• Optional• If entered, length should be a maximum of 18 characters.• This eld is labeled as Building Society Roll Number.

IBAN• Mandatory• If the IBAN isn't entered, a warning message is displayed, IBAN hasn't been entered.




United StatesValidation Rules


Field Rule

Bank Code• Optional.

Branch Number• This eld is labeled as Routing Transit Number.• Length should be a maximum of 9 numeric characters.• If the length is less than 9, then it's converted to a 9 digit number by prexing it with as

many leading zeroes as is necessary.• Note that on padding the number to 9 digits, the rst 8 digits can't be all zeroes.



345

Field Rule

• For example, 001 and 000007 are invalid Routing Transit Numbers because on paddingto 9 digits, they become - 000000001, 000000007, and thus having 8 leading zeroes.

• A check algorithm is applied on the Routing Transit Number.





Check Algorithm for Routing Transit Number

1. The ninth digit of the Number eld is used to represent the Check Digit.2. A calculated Check Digit's computed from the remaining 8 digits using Modulus 10 algorithm.3. Multiply each digit in the Routing Transit Number by a weighting factor. The weighting factors for each digit

areas given in the following table:

Digit 1st 2nd 3rd 4th 5th 6th 7th 8th

Factor

3

7

1

3

7

1

3

7

• The digits of the Routing Transit Number are multiplied by the associated factor. The computed sum is thencalculated by summing the totals.

• Subtract the sum from the next highest multiple of 10. The result is the calculated Check Digit. This should bethe same as the 9th digit of the Branch Number or Routing Transit Number; otherwise the Branch Number orRouting Transit Number is invalid.

For Example:

RoutingNumber

0 7 6 4 0 1 2 5 Total

Multiplyby

3

7

1

3

7

1

3

7

N/A

Sum

0

49

6

12

0

1

6

35 = 109

So the Check Digit = 1 (110 minus 109).

In this example, the Routing Transit Number 076401251 passes validation.



346


Chapter 11Business Events

347

11 Business Events

Overview of Public Business EventsA public event, also known as business event, is a denable logical occurrence in a business scenario. It can be a high-level occurrence such as payables invoice creation or a specialized event such as status change.

If you want to perform operations in other systems based on public events in Oracle Financials Cloud, then you can usepublic event features. You must enable the business event if it isn't enabled by default.

After you enable these features, the application sends a signal, along with a payload containing information about thepublic event, whenever an event occurs. The public event signal is also known as a public event.

The application sends signals irrespective of the source or cause of the event. For example, the application sends apayables invoice creation signal when an invoice is created using a user interface or REST API.

Integration developers and administrators can subscribe to public events from the Oracle Integration Cloud using theOracle ERP Cloud Adapter. Then, they can use the information in the payload to congure event handlers that performbusiness operations. For more information, refer to Oracle ERP Cloud Adapter Capabilities and Developing Integrationswith Oracle Integration Cloud Service.

Related Topics• Using the Oracle ERP Cloud Adapter with Oracle Integration

Business Events for PayablesFor Oracle Payables Cloud business events, Payables sends an event occurrence signal when the event has happenedusing a user interface or by a REST API.

Note: A signal isn't raised when the event occurs using a scheduled process, such as the Import PayablesInvoices process, or by using a SOAP web service, such as the Payables Invoice Management web service.

This table describes the business events supported by Payables.

Supported BusinessEvent

Description Enable By Using First ReleaseAvailable

Event Initiation

Payables InvoiceApproved

Signals when aninvoice is approved.

AP: Enable BusinessEvents prole option atthe site level

18C

• Force Approvebuon onPayablesDashboard

• Force Approvebuon onInvoices landingpage

• Force Approvebuon onManage Invoicespage

https://docs.oracle.com/en/cloud/paas/integration-cloud/erp-adapter/index.html



348



Event Initiation

• Force Approveaction on Createand Edit Invoicepages

Payables InvoiceCancelled

Signals when aninvoice is canceled.


18C

• Cancel invoiceoption usingthe VoidPayment buonon PayablesDashboard

• Cancel buon onInvoices landingpage

• Cancel Invoiceaction on Createand Edit Invoicepages

• Cancel Invoiceaction onManage Invoicespage

• Cancel Invoiceaction on InvoiceDetails page

• Cancel invoiceoption usingthe VoidPayment buonon ManagePayment page

• Cancel aninvoice usingInvoices RESTAPI

Payables InvoiceCreated

Signals when aninvoice is created.


18C

• Create Invoicepage

• Create Invoicebuon onInvoices landingpage

• Create Invoicepage fromSupplier Portal

• Create InvoiceWithout PO pagefrom SupplierPortal

• Issue Refundaction in EditReceipt pagein OracleReceivablesCloud

• Create aninvoice using



349



Event Initiation

Invoices RESTAPI

Invoice Hold Applied

Signals when aninvoice hold is placed.


18B

• Manage Holdspage from theCreate and EditInvoice pages

• Holds on InvoiceDetails page

• Validate buonon Invoicelanding page

• Validate actionon Create andEdit Invoicepages

• Validate buonon ManageInvoices page

• Place hold oninvoice optionusing the VoidPayment buonon PayablesDashboard

• Place holdon invoiceoption usingthe Void actionon ManagePayments page

• Validate aninvoice usingInvoices RESTAPI

• Create aninvoice holdusing InvoiceHolds REST API

Invoice Hold Released

Signals when aninvoice hold is released.


18B

• Release buonon PayablesDashboard

• Release buonon Invoiceslanding page

• Release Holdsaction onManage Invoicespage

• Release buonon InvoiceDetails page

• Manage Holdsinvoice action onCreate and EditInvoice pages



350



Event Initiation

• Invoice hold isreleased usingHold resolutionworkow


• Validate aninvoice usingInvoices RESTAPI

• Release aninvoice holdusing InvoiceHolds REST API

Payables InvoiceValidated

Signals when aninvoice is validatedonline.


18C

• Validate buonon Invoiceslanding page


• Validate buonor action onManage Invoicespage

• Validate actionon InvoiceDetails page

• Holds resolutionworkow whenan invoice holdis released andthe invoicestatus is updatedto Validated

• Release buonon PayablesDashboard

• Release buonon Invoiceslanding page

• Release Holdson ManageInvoices page

• Release buonon InvoiceDetails page

• Manage Holdson Create andEdit Invoicepages

• Validate aninvoice using



351



Event Initiation

Invoices RESTAPI

Payables PaymentCreated

Signals when a singlepayment is created.


18C

• Pay buon onInvoices landingpage

• Pay in Full actionon Create andEdit Invoicepages

• Pay in Full actionon ManageInvoices page

• Pay in Fullbuon onManage Invoicespage

• Pay in Full actionon InvoiceDetails page

• Create Paymentpage

• Create paymenticon on ManagePayments page

• Create apaymentusing PayablesPayments RESTAPI

Payables PaymentVoided

Signals when apayment is voided.


19A

• Void Paymentbuon onPayablesDashboard

• Void Paymentbuon onPaymentslanding page

• Void actionon ManagePayments page

• Reissue actionson ManagePayments page

• Void Paymentaction onPayment page

• Reissue actionon Paymentpage

• Void a paymentusing PayablesPayments RESTAPI



352

Enable the Payables Business Events Prole OptionIf you want Oracle Payables Cloud to signal when a dened business event occurs, then enable the AP: Enable BusinessEvents prole option.

You must have one of these roles to enable business events for Payables:

• Application Implementation Consultant

• Financial Administrator

Enable the Prole Option ValueTo enable the prole option value, complete these steps:

1. In the Setup and Maintenance work area, go to the Manage Administrator Prole Values task.2. On the Manage Administrator Prole Values page in the Search: Prole Option section, enter AP: Enable

Business Events in the Prole Display Name eld.3. Click Search.4. In the Search Results: Prole Options section, select the prole option.5. In the Prole Values section, select Yes in the Prole Value eld for the site level.6. Click Save and Close.

Business Events for PaymentsFor Oracle Payments Cloud business events, Payments sends an event occurrence signal when the event has happened.This table describes the business event supported by Payments.



Event Initiation

Payment File Created

Signals when apayment le is created.

IBY: Enable BusinessEvents prole option atthe site level

18C

Upon completion ofpayment le

Enable the Payments Business Events Prole OptionIf you want Oracle Payments Cloud to signal when a dened business event occurs, then enable the IBY: EnableBusiness Events prole option.

You must have one of these roles to enable business events for Payments:

• Application Implementation Consultant

• Financial Administrator



353

Enable the Prole Option ValueTo enable the prole option value, complete these steps:

1. In the Setup and Maintenance work area, go to the Manage Administrator Prole Values task.2. On the Manage Administrator Prole Values page in the Search: Prole Option section, enter IBY: Enable

Business Events in the Prole Display Name eld.3. Click Search.4. In the Search Results: Prole Options section, select the prole option.5. In the Prole Values section, select Yes in the Prole Value eld for the site level.6. Click Save and Close.



354


Glossary

355

Glossary

accounting flexfield

The structure that determines the chart of accounts, including the number and order of the individual segments, as wellas assigning the value sets to the segments.

automatic offset

A method for balancing invoice and payment journal entries that cross primary balancing segment values.

balancing segment

A chart of accounts segment used to automatically balance all journal entries for each value of this segment.

balancing segment value

The value of a balancing segment used to automatically balance journal entries.

bill payable

Payment documents that are payable at maturity.

business unit

A unit of an enterprise that performs one or many business functions that can be rolled up in a management hierarchy.

data role template

A set of instructions that specifies which base roles to combine with which dimension values to create a set of datasecurity policies.

descriptive flexfield

Expandable fields used for capturing additional descriptive information or attributes about an entity, such as a customercase. You may configure information collection and storage based on the context.

destination type

The destination type, expense or inventory, determines the accounting behavior of the transaction line.

determinant type

The value that affects sharing of reference data in a transaction across organizations, such as a business unit or a costorganization.


Glossary

356

disbursement bank account

The deploying company's bank account.

distribution set

A predefined set of accounts, with or without percentages, that automatically creates invoice distributions for invoicesthat aren't matched to purchase orders.

document category

A high level grouping of person documents such as visas, licenses, and medical certificates. Document subcategoriesprovide further grouping of document categories.

document payable

An item that is ready to be paid. Equivalent to an installment in Oracle Fusion Payables.

EFT

Acronym for Electronic Funds Transfer. A direct transfer of money from one account to another, such as an electronicpayment of an amount owed a supplier by transferring money from a payer's disbursement bank account into thesupplier's bank account.

extract

An XML file that contains the superset of data relevant to a payment file.

first party payer

The deploying company making disbursements. The first party payer disburses funds to pay suppliers, customerrefunds, and to reimburse employee expenses.

format

A key setup entity in Oracle Fusion Payments, which ties together formatting attributes, such those used by OracleFusion Business Intelligence Publisher (BI Publisher) templates and validations to execute during transactionprocessing.

FTP

Acronym for File Transfer Protocol. A system for transferring computer files, generally by the Internet.

funds capture payment profile

A key setup entity that holds rules for funds capture processing.

HTTP

Acronym for Hypertext Transfer Protocol. A request and response standard typical of client-server computing. In HTTP,web browsers or spiders act as clients, while an application running on the computer hosting the web site acts as aserver. The client, which submits HTTP requests, is also referred to as the user agent. The responding server, whichstores or creates resources such as HTML files and images, may be called the origin server. In between the user agentand origin server may be several intermediaries, such as proxies, gateways, and tunnels.


Glossary

357

HTTPS

Acronym for Hyper Text Transfer Protocol Secure. A protocol primarily developed for secure, safe Internet transactions.HTTPS allows secure e-commerce transactions, such as online banking.

installment

Any of several parts into which a debt or other sum payable is divided for payment at successive fixed times.

internal payee

The deploying company or any of its business units that receive funds from their customers, the payers. Payees receivefunds from their customers by credit card payments, debit card payments, direct debits to bank accounts, or billsreceivable transactions sent to banks.

invoice business unit

Business unit with the Payables Invoicing business function that is responsible for processing invoice transactions.

invoice distribution

Accounting information for an invoice line, such as accounting date, amount, and distribution combination.

job role

A role, such as an accounts payable manager or application implementation consultant, that usually identifies andaggregates the duties or responsibilities that make up the job.

key flexfield structure

The arrangement of segments in a key flexfield. In some cases, you can define multiple structures for a single keyflexfield.

lookup code

An option available within a lookup type, such as the lookup code BLUE within the lookup type COLORS.

lookup type

The label for a static list that has lookup codes as its values.

lossy

A data encoding method that compresses data by discarding some of it.

natural account

Categorizes account segment values by account type, asset, liability, expense, revenue, or equity, and sets posting,budgeting, and other options.

natural account segment

A chart of accounts segment used to categorize your accounting transactions by account type: asset, liability, owner'sequity, revenue, or expense.


Glossary

358

payee

A supplier or employee who receives payment.

payment document

A set of documents, such as check stock, on which checks and promissory notes can be printed or written. This termcan also refer to an individual document upon which a payment is printed.

payment process profile

A setup entity which drives processing behavior for each document payable, payment, and payment file.

payment process request

A grouping of documents payable, for which a calling product requests payment. Synonymous with Pay Run in OracleFusion Payables.

payment system

An external organization that provides financial settlement services. The payment system can be the bank at which thedeploying company has its bank accounts or it can be a third-party processor that connects companies and financialnetworks.

payment system account

In the funds capture flow, a representation of the relationship between a payment system and the internal payee, thatallows an authorization, settlement, or settlement batch to be transmitted to a payment system. In the disbursementflow, a representation of the relationship between a payment system and the internal payer that allows a payment file orpositive pay file to be transmitted to a bank or other payment system.

primary balancing segment value

A segment value used to represent a legal entity in the chart of accounts and automatically balance all intercompanyand intracompany transactions and journal entries.

quick payment

A single payment that you create for one more invoices without submitting a payment process request.

reference data sharing

Facilitates sharing and reuse of common transactional data entities within the parts of a business flow or acrossorganizations.

reference group

A logical collection of reference data sets that correspond to logical entities, such as payment terms defined acrossmultiple tables or views. Based on the common partitioning requirements across entities, the reference data sets aregrouped to facilitate data sharing among them.


Glossary

359

reporting entity

A person or organization that has a unique tax identification number for United States 1099 tax reporting.

separate remittance advice

A notice sent to a payee that lists the invoices that the deploying company has paid electronically to that payee's bankaccount.

servlet

A Java programming language class used to extend the capabilities of servers that host applications accessed via arequest-response programming model. Although servlets can respond to any type of request, they are commonly usedto extend the applications hosted by Web servers. For such applications, Java Servlet technology defines HTTP-specificservlet classes.

settlement batch

A group of transactions, typically settlements and credits, that are sent to the payment system together in a file.Settlement batches are generally used with a processor-model payment system.

source product

The product that owns a transaction and submits the request for disbursement or funds capture to Oracle FusionPayments.

transmission configuration

Configuration for transmitting files such as payment files.

transmission protocol

A method used to electronically transmit data, such as FTP and Secure HTTP.

usage rules

Rules that determine when payment methods and payment process profiles can be assigned for use on documentspayable.

validations

Rules that ensure that transactions are valid before they are printed or submitted electronically to payment systems.You use validations to ensure that disbursement transactions, such as invoices, payments, and payment files meetspecific conditions before they can be paid.

value-added tax (VAT)

An indirect tax on consumer expenditures that is collected on business transactions and imported goods. Value-added tax (VAT) is added to products at each stage of their production. If customers are registered for VAT and use thesupplies for taxable business purposes, then they typically receive credit for the VAT that is paid.

withholding tax classification

A collection of one or more withholding tax codes.


Glossary

360