This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
Date | Update Version | Notes |
---|---|---|
28 AUG 2020 | Update 18C | Revised update 18C. |
20 APR 2018 | Update 18B | Delivered new features in update 18B. |
25 MAY 2018 | Update 18A | Revised update 18A. |
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
Date | Feature | Notes |
---|---|---|
28 AUG 2020 | Updated document. Added opt in expiry for this feature. | |
29 NOV 2018 | Usability Enhancements on Invoice Pages | Updated document. Added additional examples and screenshots. |
01 OCT 2018 | Related Value Sets | Updated document. The Related Value Sets feature was originally targeted for delivery in 18C, but it is currently postponed to a future release. |
21 SEP 2018 | Created initial document. |
This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.
JOIN ORACLE CLOUD CUSTOMER CONNECT
Please take a moment to join the Cloud Customer Connect forums for Financials Cloud. Oracle Cloud Customer Connect is a community gathering place for members to interact and collaborate on common goals and objectives. This is where you will find the latest release information, upcoming events, or answers to use-case questions. Joining takes just a few minutes. Join now!
https://cloud.oracle.com/community
GIVE US FEEDBACK
We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com
Column Definitions:
Report = New or modified, Oracle-delivered, ready to run reports.
UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
Opt In Only = These features are made available for use via Opt In. No additional setup steps are required.
Opt In, Plus Additional Steps Required = To use these features you must first Opt In, then perform additional setup steps.
Steps Required (No Opt In) = Setup steps must be performed before these features can be used. For example, new or expanded BI subject areas need to first be incorporated into reports. Integration is required to utilize new web services.
Common Technology and User Experience
You can now use the Approval Groups Report to view details of approval groups defined in Oracle Business Process Management (BPM), such as the group name, the approvers, and the sequence in which the approvers appear in the approval group.
Steps to submit report:
- Navigate to the Schedule Processes page.
- Click Schedule New Process.
- Search and select Approval Groups Report.
- Click OK.
- Click Submit.
Steps to Enable
No steps are required to enable this feature.
Role Information
- Financial Application Administrator
Oracle Financials Cloud currently supports audit history on several key business objects. You can individually configure and enable auditing of each business object. With this release, we have expanded the list of supported business objects to include:
Area |
Object |
---|---|
Payables |
|
Receivables |
|
Bill Management |
|
Cash Management |
|
Expenses |
|
Assets |
|
Intercompany |
|
Financials Common Module |
|
General Ledger |
|
Payments |
|
Advanced Collections |
|
Regional Localizations |
|
Financials for Americas |
|
Budgetary Control |
|
Subledger Accounting |
|
Legal Entity Configurator |
|
Revenue Management |
|
Tax |
|
Steps to Enable
You must configure the business objects and select the attributes before enabling audit. If you enable audit without configuring the business objects, auditing remains inactive. By default, auditing is disabled for all applications.
To enable and manage audit, use the Manage Audit Policies task from the Application Extensions functional area within your offering. Ensure that you have a role with the assigned privilege Manage Audit Policies.
To view the history or to create a report, you must have a role with the assigned privilege View Audit History. To open the Audit History work area, from the Navigator menu, select Audit Reports.
Tips And Considerations
Audit enables tracking the change history of particular attributes of a business object. However, those objects and their attributes must be selected for audit and auditing must be enabled for that application. Your configuration settings determine which attributes to audit for a given object, and when the audit starts and ends. Auditing takes into account all the operations performed on an object and its attributes, such as create, update, and delete.
Oracle Financials Cloud currently supports automatic provisioning of roles to users. As data security assignment is an integral part of the security model in Oracle Financials Cloud, with this release you will now be able to automatically assign data security contexts to users at the same time roles are automatically provisioned to users. These automatic assignments are based on rules similar to role mappings.
Automatic data provisioning occurs if:
- At least one of the user’s assignments matches all data-mapping conditions on a Data Provisioning Rule
- At least one role is automatically provisioned to the user using Role Provisioning Rules
- The matched Data Provisioning Rule includes data assignments for a role that is automatically provisioned to the user.
The process of automatic data provisioning and deprovisioning is very similar to automatic role provisioning and deprovisioning.
Users acquire a data assignment automatically when at least one of their work assignments satisfies the conditions in the relevant data provisioning rule and the corresponding role in the applicable data assignment is also automatically provisioned. For example, if a worker is hired into the Finance Department of the London office, the worker acquires the relevant data assignments automatically if an appropriate role provisioning rule exists for Finance Department and/or London office, provided that at least one of the affected roles in the role provisioning rule is also automatically provisioned to the user. Provisioning occurs when you create or update worker assignments. All changes to work assignments cause review and update of a worker's automatically provisioned roles as well as data assignments.
Users lose automatically provisioned data assignments when they no longer satisfy the data provisioning conditions. For example, if a worker is relocated from the London office to another office, data assignments that were automatically provisioned for workers working at the London office will be lost automatically. You can also manually deprovision automatically provisioned data assignments at any time.
When you terminate a work relationship, the user automatically loses all automatically provisioned data assignments, similar to how the user would automatically lose all automatically provisioned roles.
Steps to Enable
To enable Automatic Data Provisioning, you must first opt-in the feature Data Security Auto-Provisioning for ERP.
Through the Manage Data Access for Users task accessible from the Setup and Maintenance work area, click the new Data Provisioning Rules button to access the page to create Data Provisioning Rules.
Once a data provisioning rule is defined, users will acquire data assignments automatically when at least one of their work assignments satisfies the conditions in the data provisioning rule and the corresponding roles in the applicable data assignments are also automatically provisioned.
Tips And Considerations
Automatic Data Provisioning requires the use of Automatic Role Provisioning. Data security assignments would only be automatically provisioned to users for roles that are automatically provisioned to users.
Simplified Workflow Rules Configuration
With the Simplified Workflow Rules Configuration feature, you can now create rules for Payables Invoice Approval and General Ledger Journal Approval workflows using spreadsheets. Download the spreadsheet template, enter data, and upload it using the Manage Workflow Rules in Spreadsheet task to create and manage workflow rules as per your approval policies.
MANAGE WORKFLOW RULES IN SPREADSHEET PAGE
You can download the spreadsheet template, upload the generated rule file, and view the upload history on the Manage Workflow Rules in Spreadsheet page.
To download a template, select the required workflow and click the Download icon.
In the Rule Templates section, each workflow record stores a copy of the template used for the last successful rule upload. You can use this template to review and modify the existing rules. This simplifies the process of creating and managing workflow rules.
The Upload History section displays the status of the past uploads. The upload history details are specific to the workflow selected in the Rule Templates section.
RULE TEMPLATES
The templates provide a simple layout for defining workflow rules in accordance with your organization’s approval policy.
Refer to the tooltips on each column header for instructions on how to enter the rule information. You can define approval rules to send approval notifications to:
- Approval groups
- Members of supervisory or job based hierarchies
- Specific users
- Users with specific application roles
You can also create rules to autoreject or autoapprove transactions based on the rule conditions.
DATA SETS
If the approver for a transaction varies depending on certain transaction attributes, you can use Data Sets while defining the approval rule. Using Data Sets, you can define a mapping between the approver and relevant transaction attributes.
NOTE: You can use Data Sets for Payables Invoice Approval templates only.
In this example, transactions require approval by an approval group. However, the approval group varies based on the combination of business unit on the invoice and the cost center segment value on the invoice distributions. For rules created using this data set, the approval notification is sent to the appropriate approval group for each invoice. Data sets simplify the rule creation and maintenance process. For instance, if new cost centers are added to your organization, then you just need to add more rows in the data set and upload the rule file again.
Steps to Enable
No steps are required to enable this feature.
Tips And Considerations
- Before defining rules in the template, you must analyze your approval policy and identify the approval requirements. Each distinct approval requirement can be considered as a business rule.
While preparing the rules for entering into the spreadsheet, consider the following aspects of the business rule:
- Which transactions require approval and who should approve them?
- Which transactions require auto approval or auto rejection?
- Do you need to send FYI notifications for approvals under this rule?
- Which transactions do not require approval under this rule, that is, the transactions for which this approval rule is not applicable.
NOTE: While defining business rules, make sure that you define all aspects of a business rule in one rule block. A rule block is a group of rows in the workflow rules spreadsheet wherein you define all aspects of the business rule. Each subsequent business rule should be defined in a new rule block.
- While all rule aspects defined within a rule block are processed simultaneously, rule blocks are processed in sequence. Therefore, you must consider the sequence in which the rules should be processed before defining the rules.
- When using data sets for defining Payables Invoice Approval rules, you must add a reference to the data set name in the rule definition by adding a prefix of ‘$’ to the data set name. For example, $FIN APPROVAL GROUPS.
- A copy of the rule template of the last successful rule upload is stored on the Manage Workflow Rules in Spreadsheet page for each workflow. You can download this template to review or modify the rules.
- Once you create rules using the rule templates, we recommend you use the spreadsheet method only for any future maintenance of rules.
CAUTION: Every successful rule upload using a spreadsheet template overrides the existing rules for the workflow.
Key Resources
- Refer to the Manage Workflow Rules using a Spreadsheet topic on Oracle Help Center.
Role Information
- Financial Application Administrator
You can now use the Workflow Rules Report to view the workflow rules configured in Oracle Business Process Management (BPM) for Payables Invoice Approval, General Ledger Journal Approval, and Expense Report Approval workflows. You can also use this report to obtain details of rule conditions and approval routing for each rule. You can view the report output in both spreadsheet and XML format.
Steps to submit report:
- Navigate to the Schedule Processes page.
- Click Schedule New Process.
- Search and select Workflow Rules Report.
- From the Workflow list, select the required workflow.
- Click Submit.
Steps to Enable
No steps are required to enable this feature.
Role Information
- Financial Application Administrator
REST APIs for Collections Strategy
Use the Collections Strategy REST API resource to create and manage strategies assigned to customers. You can:
- Create new strategy assignments and their tasks in bulk.
- Migrate in-progress strategy assignments and their tasks from another application to Advanced Collections.
- Update strategy status and task status based on triggers from third-party applications.
- Assign strategy tasks to collectors in bulk.
Steps to Enable
FEATURE ENABLEMENT
- Click Navigator > My Enterprise > Offerings.
- In the Offerings page, select Financials.
- Click the Opt In Features button.
- On the Opt In: Financials page, click the Features icon for Collections.
- A list of Collections features is displayed. Select the Enable check box for the Automatically Initiate or Fulfill Collections Tasks in Third-Party Systems feature and save the changes.
DEFINE PREFERRED SETTING FOR STRATEGY BATCH PROCESSING
Optionally, you can update the default values for the number of parallel processors and batch size. The Process Strategy Tasks process launches multiple child processes based on these two preferences to achieve parallel processing.
- From the Setup and Maintenance work area, access the Manage Collections Preferences task.
-
Use the Manage Collections Preferences page to update the values for the number of parallel processors and batch size. The default value for the number of parallel processors is 1, and the default value for batch size is 1000.
SCHEDULE THE PROCESS STRATEGY TASKS PROCESS
- Go to the Scheduled Processes work area.
- Schedule the Process Strategy Tasks process to run regularly based on your business needs. It should be run at the same frequency as your other Collections background processes for delinquency management, scoring, and strategy assignment.
Key Resources
- For an overview of REST APIs and the technical details, see the REST API for Oracle Financials Cloud guide in the Oracle Help Center (http://docs.oracle.com).
Use the Banks REST API resource to manage details about banks. You can:
- Create and manage bank details including the bank code, bank number, description, Taxpayer ID, and Tax Registration Number.
- Retrieve and update bank information.
- Delete banks.
The country-specific bank code validation is based on the configuration of the Cash Management profile option: Disable Country Specific Bank Validations.
Steps to Enable
No steps are required to enable this feature.
Tips And Considerations
Consider the following when deleting a bank:
- The bank is end dated using the current date.
- Once the bank is deleted you cannot access any of the bank information the next day.
Key Resources
- For an overview of REST APIs and the technical details, see the REST API for Oracle Financials Cloud guide in the Oracle Help Center (http://docs.oracle.com).
Use the Bank Accounts REST API resource to manage details about internal bank accounts. You can:
- Create and manage bank account details such as bank account uses, accounting flexfield combinations, payment documents, checkbooks, target balances, bank statement transaction creation rules, reconciliation matching rules, parsing rules, descriptive flexfields, and global descriptive flexfields.
- Manage security and access to the bank account.
- Manage the business unit assignments, payment document categories, and accounting combinations for each business unit.
- Inactivate bank accounts.
The country-specific bank account, check digit, and IBAN validation is based on the configuration of the Cash Management profile option: Disable Country Specific Bank Validations.
Steps to Enable
No steps are required to enable this feature.
Key Resources
- For an overview of REST APIs and the technical details, see the REST API for Oracle Financials Cloud guide in the Oracle Help Center (http://docs.oracle.com).
Use the Bank Branches REST API resource to manage details about bank branches. You can:
- Create and manage details about bank branches.
- Retrieve and update bank branches.
- Delete bank branches.
The country-specific branch number validation is based on the configuration of the Cash Management profile option: Disable Country Specific Bank Validations.
Steps to Enable
No steps are required to enable this feature.
Tips And Considerations
Consider the following when deleting a bank branch:
- The bank branch is end dated using the current date.
- Once the bank branch is deleted you cannot access any of the bank branch information the next day.
Key Resources
- For an overview of REST APIs and the technical details, see the REST API for Oracle Financials Cloud guide in the Oracle Help Center (http://docs.oracle.com).
REST APIs for External Cash Transactions
Use the External Cash Transactions REST API resource to manage details about external cash transactions. You can:
- Create and manage details about external cash transactions such as bank account, transaction date, transaction amount, transaction type, reconciliation reference, accounting combinations, descriptive flexfields, and attachments.
- Determine whether the accounting event is raised when the external cash transaction is reconciled.
- Retrieve and update key information to improve the performance of the reconciliation process.
- Void external cash transactions.
Steps to Enable
No steps are required to enable this feature.
Key Resources
- For an overview of REST APIs and the technical details, see the REST API for Oracle Financials Cloud guide in the Oracle Help Center (http://docs.oracle.com).
Use the Expenses REST APIs to create and manage expense reports and expense items. You can perform the following operations with the REST APIs:
- Create expense reports with cash expenses and itemizations for the signed in user and his or her delegates. Create expense distributions to allocate expense items to accurate accounts.
- Optionally, add project information, descriptive flexfields for the report and for the lines, and expense attendees for expense items.
- Create expense reports and expense items in batch and expense items in batch outside of a report.
- Add attachments to expense reports and expense items based on policies. You can add attachments, one by one, for each report or in batch for one or more expense reports.
- Select and update expense reports, expense items, distributions, project information, descriptive flexfields, and expense attendees. When applicable, modify attachment properties.
- Retrieve expense reports and expense items for further processing. Data retrieved by the find operations are restricted by your data access role. You can find the following:
- All expense reports or expense reports for a specific business unit
- All expense reports for corporate cards issuers
- All short-paid expense reports
- An expense report matching an expense report identifier
- All corporate card expenses not included in any reports for an employee
- All corporate card transactions for an employee
- An expense item matching an expense item identifier
- Attendees for an expense item identifier or an expense attendee identifier
- Expense distributions for an expense distribution identifier
- Project information for an expense distribution identifier
- Expense itemization for an expense item identifier
- Expense descriptive flexfields for an expense item identifier
- Attachment for a document identifier
- Expense report for a specific expense report identifier
Steps to Enable
No steps are required to enable this feature.
Tips And Considerations
Delete operation is not supported for expense reports, expense items, or related information.
Use the Payables Payments REST API resource to manage details about payments. You can:
- Retrieve payment and paid invoice information.
- Void a payment.
Steps to Enable
No steps are required to enable this feature.
Key Resources
- For an overview of REST APIs and the technical details, see the REST API for Oracle Financials Cloud guide in the Oracle Help Center (http://docs.oracle.com).
REST APIs for Supplier Invoices
Use the Invoices and Invoice Holds REST API resources to manage details about supplier invoices. You can:
- Create and manage details about unmatched supplier invoices, including header, lines, distributions, installments, descriptive flexfields, and attachments.
- Create unmatched supplier invoices with types such as Standard, Prepayment, Credit Memo, and Debit Memo.
- Update key invoice information and perform actions on an invoice, such as validate, cancel, and delete.
- Place or release holds on invoices.
You can also construct integrations based on your requirements:
- For retainage or reverse factoring arrangements. For example:
- Update invoice information, including pay group and other information, such as due date, payment method, bank account, and third-party payment on installments.
- Split installments.
- Place or release a hold on installments.
- To place invoices on hold until an external process is complete. For example, pending approvals or confirmation on reverse factoring, before the hold is released for further processing.
Steps to Enable
No steps are required to enable this feature.
Key Resources
- For an overview of REST APIs and the technical details, see the REST API for Oracle Financials Cloud guide in the Oracle Help Center (http://docs.oracle.com).
REST APIs for Receivables Invoices
Use the Receivables Invoices REST resource to create, find, and delete invoices. You can:
- Create Receivables invoices, with header information such as transaction type, payment terms, and remit-to address, and with invoice lines for goods delivered and services rendered to the customer.
- Capture additional information for the invoice and invoice lines with descriptive flexfields and global descriptive flexfields. In addition, append notes and attachments to the invoice.
- Get and Find details of one or more Receivables invoices. Optionally delete an invoice.
Steps to Enable
The Receivables Invoices REST Service is available by default.
Key Resources
- The REST API for Oracle Financials Cloud document on Oracle Help Center includes the overview of REST services and the technical details of the REST APIs that you can implement. Please refer to the REST Service Usage Notes for the Receivables Invoices REST service for examples and use case references.
REST APIs for Standard Receipts
Use the Standard Receipts REST resource to create, find, and delete standard receipts. You can:
- Create standard receipts in Receivables to record payments from customers against their open invoices. Add one or more remittance references to the standard receipt. The Apply Receipts Using AutoMatch process runs asynchronously to apply the receipt to one or more invoices.
- Capture additional information to the standard receipt with descriptive flexfields and global descriptive flexfields. In addition, append attachments to the receipt.
- Get and Find details of one or more standard receipts. Optionally delete a standard receipt.
Steps to Enable
The Standard Receipts REST Service is available by default.
Tips And Considerations
- Use the batch operation to create multiple standard receipts.
- Attributes in the resource payload are organized to have similar attributes listed together.
Key Resources
- The REST API for Oracle Financials Cloud document on Oracle Help Center includes the overview of REST services and the technical details of the REST APIs that you can implement. Please refer to the REST Service Usage Notes for the Receivables Standard Receipt REST service for examples and use case references.
Assignment of Collections Activities to Collector Groups
Advanced Collections now supports the setup and use of collector groups. You can use this feature to assign one or more collectors along with the primary collector to form a collector group. All collectors belonging to a collector group can perform the same collections activities. This feature contains the following components:
- Creation of collector groups on the Manage Resources page.
In the Manage Resources page, create a collector group and provide a unique collector group name. Add individual collectors to the group by selecting them from the list of values. A collector can belong to only one active collector group for a specified date range. Designate a collector as either a group member or a backup collector for the specified date range.
- Enhanced Collections work area to support collector group usage.
All collectors belonging to a collector group now have the same visibility to the delinquent customers and strategy tasks on the Collections work area. The Strategy Tasks info tile shows the list of open manual strategy tasks for the group collectors. Collectors from the group can work on a strategy task by using the Reassign button to reassign the task either to themselves or to another collector in the group. The Strategy Task list displays the primary collector and the assigned collector to indicate who from the collector group is assigned the task.
Steps to Enable
This feature is automatically available through the release update. To enable it, configure collector group as per your business requirements. Following are the steps to set up a new collector group:
- Navigate to the Manage Resources Page.
- Select a primary collector for the collector group you want to set up.
- Navigate to the Collector Group section of the page.
- Click the New icon to add a new collector group.
- Enter a unique collector group name. The Enabled field is set to Yes by default.
- Add members to the group by selecting their names from the Collector list. The Enabled field is set to Yes by default along with the start date.
- After adding all collectors to the group, click Save or Save and Close to save the collector group definition.
Tips And Considerations
- You can disable the current definition of a backup collector if this collector needs to be assigned to a collector group.
- You can disable a group name that is not needed.This disables all the collector assigned to that group.
Automatically Initiate or Fulfill Collections Tasks in Third Party Systems
You can automatically initiate or fulfill Collections tasks in third party applications, such as updating strategies and tasks based on external requests, assigning strategies to customers without delinquencies, and migrating strategies with in-progress tasks.
REST API FOR COLLECTIONS STRATEGY
Use the Collections Strategy REST API resource to create and manage strategies assigned to customers. You can:
- Create new strategy assignments and their tasks in bulk.
- Migrate in-progress strategy assignments and their tasks from another application to Advanced Collections.
- Update strategy status and task status based on triggers from third-party applications.
- Assign strategy tasks to collectors in bulk.
For an overview of REST APIs and the technical details, see the REST API for Oracle Financials Cloud guide in the Oracle Help Center (http://docs.oracle.com).
COLLECTIONS STRATEGY BUSINESS EVENTS
Business events are raised upon opening of a strategy task or completion of a strategy. You can subscribe to the events and automate the subsequent processing of any external strategy tasks. Examples of an external strategy task include a telecommunication company suspending or activating customers’ phone accounts maintained outside Advanced Collections.
STRATEGY TASK TYPE
In addition to the existing task types Automatic and Manual, a new strategy task type External is now available to indicate that a strategy task needs external processing.
STRATEGY TYPE
In addition to the existing strategy types Delinquent and Predelinquent, a new strategy type Current is now available to identify a strategy that can be assigned to customers without delinquencies or pre-delinquencies.
BACKGROUND PROCESS FOR STRATEGY TASKS
To improve efficiency and performance of strategy processing, a new background process is available to process optional strategy tasks, tasks that have execution start time or post execution wait time defined, and tasks that need to be escalated. If you enable the Automatically Initiate or Fulfill Collections Tasks in Third Party Systems feature, you must run the new process on a regular basis to ensure that strategy tasks are processed timely. The new process does not replace any of your existing Collections background processes.
Steps to Enable
- Feature Enablement
- Click Navigator > My Enterprise > Offerings.
- In the Offerings page, select Financials.
- Click the Opt In Features button.
- On the Opt In: Financials page, click the Features icon for Collections.
- A list of Collections features is displayed. Select the Enable check box for the Automatically Initiate or Fulfill Collections Tasks in Third-Party Systems feature and save the changes.
- Define External Strategy Tasks
If you have strategy tasks that require processing by third party applications, define them first in Advanced Collections.
- From the Setup and Maintenance work area, access the Manage Collections Strategy Tasks task.
- Use the Manage Strategy Tasks page to create a strategy task with the type of External.
- Define Nondelinquent Strategy Groups
To assign strategies to nondelinquent customers, you must first define the strategies.
- From the Setup and Maintenance work area, access the Manage Collections Strategies task.
- Use Manage Collections Strategies page to create a strategy group with the type of Current for the strategy level you use.
- Define Preferred Setting for Strategy Batch Processing
Optionally, you can update the default values for the number of parallel processors and batch size. The Process Strategy Tasks process launches multiple child processes based on these two preferences to achieve parallel processing.
- From the Setup and Maintenance work area, access the Manage Collections Preferences task.
-
Use the Manage Collections Preferences page to update the values for the number of parallel processors and batch size. The default value for the number of parallel processors is 1, and the default value for batch size is 1000.
- Schedule the Process Strategy Tasks Process
- Go to the Scheduled Processes work area.
- Schedule the Process Strategy Tasks process to run regularly based on your business needs. It should be run at the same frequency as your other Collections background processes for delinquency management, scoring, and strategy assignment.
Key Resources
- For an overview of REST APIs and the technical details, see the REST API for Oracle Financials Cloud guide in the Oracle Help Center (http://docs.oracle.com).
Send Invoices with Collections Dunning Letters
The Store Printed Receivables Transactions as Attachments feature stores copies of transactions in the attachment category "Printed Transaction Copy". The Send Dunning Letters background process retrieves the transaction copies stored in this attachment category and sends them together with the dunning letters.
You can control the number of transaction copies to include with one dunning letter using the new Collections preference "Maximum number of transactions to send with dunning letters". Once this limit is reached, no more copies of transactions will be sent with the dunning letter.
Steps to Enable
Using the Manage Collections Preferences setup task, set up the desired value for the "Maximum number of transactions to send with dunning letters". The default value is 0.
Tips And Considerations
The Receivables feature Store Printed Receivables Transactions as Attachments needs to be enabled as the prerequisite.
Asset Cost and Depreciation Report
The Asset Cost and Reserve Report list the asset cost and depreciation reserve balances at the asset level. The report sorts and totals by category, asset type, asset cost account, and cost center.
Specify cost account and category filters and the report detail to meet your business needs
Steps to Enable
You need to opt-in this feature from the offerings page. Once you have opted-in, the report becomes automatically available.
Tips And Considerations
You can specify any of the closed depreciation periods for your asset book.
Role Information
- Asset Accounting Manager
Search by Project Asset Name While Preparing Source Lines in Fixed Assets
A new field has been added to allow you to sort asset lines for projects by Project Asset Name when performing Mass Addition on the Prepare Source Lines page.
Steps to Enable
No steps are required to enable this feature.
Audit Budgetary Control Setup Changes
You can now audit changes in setup for the following budgetary control tasks
- Manage Budgetary Control
- Manage Encumbrance Accounting
- Manage Control Budget
Configure audit rules from the Setup and Maintenance work area using the Manage Audit Policies task to enable and disable audit for the Budgetary Control product business objects and their attributes. After configuration is complete, you can track changes to attributes of these business objects using the Audit Report.
Steps to Enable
ENABLE AUDIT FOR BUDGETARY CONTROL BUSINESS OBJECTS
To enabled audit policies for Budgetary Control business objects:
- Navigate to the Setup and Maintenance work area.
- Select the Manage Audit Policies task.
- Select Oracle Fusion Applications Configure, Business Object Attributes.
- Select the Product = Budgetary Control
- Select the business object to be audited and its attributes.
- Save the selection.
VIEW AUDIT REPORTS
To view the audit data collected for a specific user, access the Audit Reports for the related Budgetary Control business objects:
- From the Navigator, select Tools > Audit Reports
- In the search region, select the user you want to audit
- Choose the date or date range that you want to review the changes made by a user.
- Set the product = Budgetary Control and search to return the desired audit reports.
Tips And Considerations
A role containing the Manage Audit Policies (FND_MANAGE_AUDIT_POLICIES_PRIV) privilege is required to use the Audit feature.
Key Resources
- See the Maintain Audit Policies chapter in Oracle Financials Cloud Implementing Common Features for Financials
Role Information
- Manage Audit Policies (FND_MANAGE_AUDIT_POLICIES_PRIV)
Cash to General Ledger Reconciliation Report
The Cash to General Ledger Reconciliation report compares GL cash account balances against the bank account balance, and displays unreconciled GL cash account journal entries and unreconciled bank statement lines to help identify any discrepancies between balances.
This report can now be generated based on multiple periods to properly match items from prior periods to the current bank statement.
Steps to Enable
There are no steps necessary to enable this enhancement. This report is controlled by the existing privilege Submit Cash to General Ledger Reconciliation Report. This report can be submitted from Scheduled Processes or from the Panel Drawer icon to the right of the Bank Statements and Reconciliation dashboard.
Tips And Considerations
- The Cash to General Ledger Reconciliation Report lists unreconciled bank statement lines and subledger transactions that are accounted in GL but are not reconciled in Cash Management.
- Consider submitting the report for multiple periods to properly match items from prior periods to the current bank statement.
- Consider assigning a unique GL cash account for each bank account and using it to record all cash transactions to facilitate this book to bank reconciliation.
Key Resources
- For more information on Cash to General Ledger Reconciliation report, refer to Oracle Financials Cloud Using Payables Invoice to Pay, or Oracle Financials Cloud Using Receivables Credit to Cash.
Create External Transaction for Foreign Exchange Gain or Loss
The External Transactions for Foreign Exchange Gain or Loss creation process is enhanced to segregate reconciliation differences into exchange gain or loss or bank charges. Separate external transactions are created for exchange differences and bank charges using offset accounts from the bank account.
Steps to Enable
Enable the feature from the Functional Setup Manager Feature Opt In page. The steps are:
- Go to the Setup and Maintenance work area.
- Select Financials in the drop-down list at the top of the page
- Click Change Feature Opt In
- On the Opt In: Financials page, click the Features icon for Cash Management
- On the Edit Features: Cash Management page, select the Enable icon for Create External Transactions for Exchange Gain or Loss feature.
Overdue Invoices in Cash Forecast
Cash Forecasting is the estimation of cash position on the basis of sources that affect cash position such as: Payables (Payables Invoices, Payables Payments), Receivables (Receivables Invoices, Receivables Receipts), Payroll (Payroll payments), and External transactions.
The Cash Forecast reports now include open and overdue Payables and Receivables invoices, including invoices unpaid or partially paid. This additional information provides an improved measure of your liquidity and your cash outflows.
The overdue invoice amounts are displayed in the current date columns. By drilling down to the transaction, you can find the detail information such as invoice date and due date.
The Cash Positioning and Forecasting solution utilizes Oracle’s Smart View and Financial Reporting on Essbase cube technology. Two new source transactions (AP Overdue Invoices and AR Overdue Invoices) are available out of the box as cube dimensions of the Transactions cube CashPositionTrxApp:
The dimensions delivered include Bank, Legal Entity, Currency, Currency Type, Transaction Type, Source of the Transaction (Bank Statements, AP Invoices, AP Overdue Invoices, AP Payments, AR Invoices, AR Overdue Invoices, AR Receipts, Payroll, and External Transactions), Reconciliation Status of the transaction, Time, and Flow indicator for the bank statement line.
Steps to Enable
- Navigate to the Scheduled Processes page.
- Click on Schedule New Process.
- Submit “Cash Position Data Deletion” process to delete existing data from the cube.
After Cash Position Data Deletion completes successfully:
- Click on Schedule New Process.
- Submit “Cash Position Data Extraction” process to create the cube with the new source transactions AP Overdue Invoices and AR Overdue Invoices. The Cash Position Data Transfer process runs automatically when you submit the process.
The Cash Position Data processes are controlled by the existing privileges Submit Cash Positioning and Forecasting Data Deletion, Submit Cash Positioning and Forecasting Data Extraction, and Submit Cash Positioning and Forecasting Data Transfer.
Tips And Considerations
- On the Specify Cash Positioning and Forecasting Options setup page, the extraction duration parameter is used to transfer data to the Essbase cube. Transactions with transaction dates within that period are extracted to the cube. For example, Last 3 months, Last 2 years or Last 3 years.
- The Cash Position Data Deletion process deletes data from Transactions cube (CashPositionTrxApp) and Manual cube (CashPositionManualApp).
- The Transactions cube provides you with the ability to perform ad hoc analysis in a spreadsheet using Oracle Hyperion Smart View (Smart View).
- Using Smart View and Financial Reporting, users can perform drilldowns, aggregations and pivoting on the cash positioning and forecasting.
Key Resources
- For more information on Cash Positioning and Forecasting solution, refer to Oracle Financials Cloud Using Payables Invoice to Pay, or Oracle Financials Cloud Using Receivables Credit to Cash.
Companies often require their employees to get approval for high value expenses before they are incurred. A spend authorization is a request by an employee for approval of anticipated expenses for a future activity. You can now request spend authorizations, approve them, and associate them to expense reports.
REQUESTING A SPEND AUTHORIZATION
You can now request a spend authorization in the Expenses work area. The Request Authorization link is available from the Actions menu on the Expenses work area. If you are a new user, you can request a spend authorization from the Welcome page.
A new Authorizations infotile has been added to the Expenses work area to display existing spend authorizations. The Authorizations infotile highlights three actionable links.
- In Progress
Number of authorizations that are in Saved, Rejected, or Withdrawn status.
- In Approval
Number of authorizations awaiting approval from managers or other approvers.
- Approved
Number of approved authorizations that are available for association to expense reports.
When you request a spend authorization, you enter key information about your trip, such as location, start date, end date and estimate the anticipated expenses. A spend authorization consists of one or more estimated expenses. When creating a spend authorization, you use the same expense templates and expense types as in expense entry.
Delegates can submit spend authorizations on behalf of the persons for whom they enter expense reports.
APPROVING SPEND AUTHORIZATION
You can use the predefined approval rules for spend authorization or configure the rules to support your specific business needs. The approval rules identify the approver based on the defined criteria and routes the authorization to the approver.
When you submit a spend authorization, your manager or approver receives a notification. Approvers can approve the authorization from the approval email or from the online notification. Spend authorization approvals are also accessible from the Approvals infotile in the Expenses work area. Approvers can approve, reject, or request more information from an employee. When a spend authorization is rejected, it is returned to the employee.
ASSOCIATING A SPEND AUTHORIZATION TO AN EXPENSE REPORT
You can associate an approved spend authorization to an expense report to support the expenses incurred. If your company allows you to request spend authorizations, a new Authorization choice list is available for selecting a spend authorization when you create an expense report. Your company can also require you to attach an authorization for each expense line of the expense report.
Steps to Enable
To enable spend authorization, follow these steps:
- In the Setup and Maintenance work area, navigate to the Manage Cash Advance Policies task.
- To enable spend authorization for the company, select Yes from the Enable Authorizations choice list in the All Business Units section.
- Based on your business needs, select Header Only or Lines Only from the Attach Authorization choice list.
- To enable spend authorizations for a specific business unit, select the Create icon in the Specific Business Units section.
- In the Create Business Unit-Specific Cash Advance Policies dialog box, select the applicable business unit from the Business Unit choice list.
- On the Authorizations tab, select the applicable values for the Enable Authorizations and the Attach Authorization choice lists. To use the settings applicable to all business units, select the Use setup from all business units option.
- Click Save and Close.
Key Resources
For more information about spend authorizations, refer to the following topics in Oracle Applications online help:
- Spend Authorizations: Explained
- Setting Up Spend Authorizations: Points to Consider
Role Information
To enable spend authorizations, you must have one of the following roles:
- Expense Manager
- Application Implementation Consultant
- Financials Administrator
Import and Update Account Combinations
Use the Import Account Combinations file-based data import (FBDI) to create account combinations as well as update existing account combinations. Insert rows into the GL_BULK_COMBINATIONS_INT table using the FBDI template and then submit the Import Account Combinations process. If the process finds that an account combination with the same segment values already exists, the following attributes are updated to reflect the imported values:
- Enabled
- Allow Posting
- From Date
- To Date
- Alternate Account
- Preserve Attributes
Steps to Enable
No steps are required to enable this feature.
Key Resources
- For information about preparing the data and loading the CSV files into the interface table, see the File-Based Data Import for Oracle Financials Cloud guide on the Oracle Help Center (https://docs.oracle.com).
Use the Match in Full feature to create an invoice by matching in full to the purchase order. You use this feature when the supplier sends an invoice for the full amount of the purchase order. You only need to enter the purchase order number, invoice date, and invoice number to create the invoice. This new feature is in addition to the existing functionality of matching invoice lines to the purchase order
Steps to Enable
No steps are required to enable this feature.
Tips And Considerations
You cannot use Match in Full in these cases:
- Invoice match option is receipt
- Supplier or Purchase Order is setup for self-billing
- Purchase order is already partially matched to an invoice
Payables provides two new Accounts Payable job roles: Accounts Payable Invoice Supervisor and Accounts Payable Payment Supervisor. These new job roles help to ensure compliance with the segregation of duties. The Accounts Payable Invoice Supervisor job role allows you to create and manage invoices but does not allow the processing of payments. Similarly, the Accounts Payable Payment Supervisor job role allows you to create and manage payments but does not allow you to process invoices. The new job roles provide access to the Payables transactions only and not to the Payables setups.
Steps to Enable
No steps are required to enable this feature.
Usability Enhancements on Invoice Pages
To improve the user’s efficiency, the scanned invoice images automatically open in a new separate window. This new window automatically refreshes when you move to the next invoice. Similarly, it closes when you move out of the invoice pages. With the image being moved out to a separate window, the contextual region in the invoice pages has been removed and the invoice status details are now available next to the invoice actions. This improves the user experience by displaying only the invoice header, lines, and totals sections. The invoice status by default displays the invoice validation status and when the hyperlink is clicked the other invoice statuses information such as accounting and payment is displayed.
Similar enhancements are made in Manage Invoices (search results section) and Invoice Details pages. You can view the invoice summary by clicking the hyperlink on the validation status and the invoice totals by clicking the hyperlink on the invoice amount.
Steps to Enable
No steps are required to enable this feature.
Derive Bank Account Number from IBAN
When you create an external bank account, you must provide a bank account number. The IBAN (International Bank Account Number) has replaced the bank account number as the identifier of a bank account in the majority of the European, Middle Eastern, and Caribbean countries. The IBAN structure and length varies from country to country.
For countries where the IBAN is used according to SWIFT (Society for Worldwide Interbank Financial Telecommunication) guidelines, you can now create an external bank account by entering only the IBAN instead of both the bank account number and the IBAN. When you save the external bank account, the bank account number will automatically be derived from the IBAN according to the structure prescribed by SWIFT and populates the Account Number field.
Steps to Enable
Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.
Offering: Financials No Longer Optional From: Update 20D
Tips And Considerations
- On the Opt In: Financials page, click the Features icon for Payments.
- On the Edit Features: Payments page, select the Enable check box for the feature named Derive bank account number from IBAN.
- Click Done to return to the Opt In: Financials page.
Pricing and Billing for Subscriptions
You can now automate your entire subscription billing process and post billing activities using the new integration with Subscription Management Cloud. Generate invoices or credits for new, renewed, amended, or terminated subscriptions and usage-based products sold to customers.
The integration between Receivables and Subscription Management provides the following functionality:
- Import subscription line and credit information.
- Generate invoices in Receivables automatically for the bill and credit lines generated in Subscription Management.
- Bill your customers in advance or in arrears for one time and recurring charges to reflect different, comprehensive pricing models maintained in Subscription Management (with price plan, usage tiers, allowances and overages, automatic and manual discounts, promotions, and anniversary pricing).
- Capture prepayments at the subscription product-specific charge levels to reduce the invoice amount by the prepaid amount.
- Configure individual descriptions for invoice line items in Subscription Management.
Take full advantage of standard Cloud ERP capabilities for all downstream processing of subscription invoices:
- Configure and deliver customer invoices using multiple delivery channels - printed, email, XML.
- Process customer payments, and manage accounts receivable balances and period close reconciliation using Receivables.
- Manage the collections process, assign collectors, and manage disputes, payments, and all collections activities using Advanced Collections.
- Provide self-service customer led bill management capabilities to your customers using Bill Management.
- Manage revenue in a centralized and automated fashion to address the ASC 606 and IFRS 15 accounting standards using Revenue Management.
Steps to Enable
No steps are needed to enable this feature.
The following setups are predefined to enable this feature:
- Predefined Transaction Source ‘ORA_Subscriptions’ has been introduced as the Transaction Source for transactions from Subscription Management.
- Predefined Transaction Types ‘ORA_OSS_Invoice’ and ‘ORA_OSS_Credit Memo’ have been introduced as the transaction types for the transactions from Subscription Management.
Tips And Considerations
- Initiate the 'Send Service Contract Billing Information to Receivables' process to send the subscription line and covered asset billing and credit information to the Receivables interface tables.
- Initiate the 'Fetch Service Contract Invoice Information from Receivables' process to retrieve the invoice and credit memo information for subscription lines and covered assets from Receivables.
Print Attachments Along with Receivables Transactions
Use the Print Receivables Transactions process to print attachments to Receivables transactions along with the transactions.
The Print Receivables Transactions process prints transaction attachments that satisfy the following criteria:
- The transaction delivery method is Paper or Email.
- The attachment is in PDF format.
- The attachment is attached to the transaction header.
- The attachment category is defined as an active lookup code of the AR_PRINT_ATTACHMENT_CATEGORIES lookup type (Categories of Attachments to be Printed).
The following example illustrates which attachments are printed and not printed during a run of the Print Receivables Transactions process.
You set up the AR_PRINT_ATTACHMENT_CATEGORIES lookup type with two active lookup codes EXP_CHARGES and ADDITIONAL_INFO. (These lookup codes are also the attachment category names.) There are four invoices:
- Invoice 1000, which has the following attachments:
- Header level:
- Attachment A, PDF file, Category is Additional Information to Customer (whose category name is ADDITIONAL_INFO)
- Line level:
- Attachment B, PDF file, Category is Explanation of Charges (whose category name is EXP_CHARGES)
- Header level:
- Invoice 1001, which has the following attachments:
- Header level:
- Attachment C, PDF file, Category is Explanation of Charges
- Line level:
- Attachment D, PDF file, Category is Customer Transactions
- Header level:
- Invoice 1002, which has the following attachments:
- Header level:
- Attachment E, PDF file, Category is Internal Notes
- Line level:
- Attachment F, PDF file, Category is Additional Information to Customer
- Header level:
- Invoice 1003, which has the following attachment:
- Header level:
- Attachment G, txt file, Category is Additional Information to Customer
- Header level:
The output file of the Print Receivables Transactions process will include the following:
- Invoice 1000 with Attachment A
- Invoice 1001 with Attachment C
- Invoice 1002 with no attachment
- Invoice 1003 with no attachment
Steps to Enable
- Create the attachment category to be printed using the Manage Attachment Categories setup task, for the module "Transactions" (Module Key = FinArTransactionsMain). Alternatively, you can use existing attachment categories.
- Add a new lookup type using the Manage Standard Lookups setup task with the following information:
- Lookup Type: AR_PRINT_ATTACHMENT_CATEGORIES
- Meaning: Categories of Attachments to be Printed
- Description: Specifies the categories of attachments to be printed by the Print Receivables Transactions process.
- User Module Name: Transaction (Module Key = FinArTransactionsMain).
- Save the lookup type. Add the lookup codes that match the category user names as defined in Manage Attachment Categories.
Tips And Considerations
There is no limit to the file size of the attachments to be printed.
Processing of Late Charges by Legal Entity
Use the Create Late Charges Batch process to generate separate late charges for each legal entity associated with an overdue transaction. This feature only applies to late charges presented as an interest invoice (Late Charge Type = Invoice).
When this feature is set up, the Create Late Charges Batch process generates a separate late charge interest invoice for each legal entity associated with the active ledger of the business unit of the overdue transaction. The process also replaces the balancing segment value of the receivable and revenue account code combinations of the late charge interest invoice with the balancing segment value assigned to the legal entity of the overdue transaction.
NOTE: If multiple balancing segment values are assigned to the legal entity of the overdue transaction, then the Create Late Charges Batch process does not replace the balancing segment value of the receivable and revenue account code combinations. The receivable and revenue accounts are retained that you defined in the Interest Invoice transaction type and assigned to Receivables System Options for the applicable business unit.
The following example illustrates how the Processing of Late Charges by Legal Entity generates interest invoices and manages balancing values.
The Interest Invoice Transaction Type defined at the Receivables System Options for a business unit has the receivable and revenue account defined as below (Company-Account-Activity-Cost Center- Interco- Project- Site- SubAccount with Company Segment defined as the Primary Balancing Segment):
Receivable Account: 01-1410000-3-1010-00-000-C-0
Revenue Account: 01-210000-3-1010-00-000-C-0
This table describes a customer's overdue transactions as of the date the late charges are calculated (the transactions belong to the same business unit):
Transaction Number |
Transaction Class |
Transaction Date |
Due Date |
Legal Entity Name |
BSV Assigned to Legal Entity |
---|---|---|---|---|---|
I-101 |
Invoice |
4/9/18 |
5/9/18 |
Vision Operations |
01 |
I-102 |
Invoice |
3/19/18 |
4/3/18 |
Vision Services |
02 |
I-103 |
Invoice |
4/22/18 |
5/21/18 |
Vision Services |
02 |
I-104 |
Invoice |
3/5/18 |
4/19/18 |
Vision Foods |
03, 04 |
This table describes the resulting interest invoices generated for each legal entity after a run of the Create Late Charges Batch process:
Late Charges Batch Name |
Interest Invoice Number |
Legal Entity of the Interest Invoice |
Overdue Transactions on which late charges calculated |
Receivable Account of Interest Invoice |
Revenue Account of Interest Invoice |
---|---|---|---|---|---|
Late charge batch 2030 31-05-2018 |
2001 |
Vision Operations |
I-101 |
01-1410000-3-1010-00-000-C-0 |
01-210000-3-1010-00-000-C-0 |
Late charge batch 2030 31-05-2018 |
2002 |
Vision Services |
I-102, I-103 |
02-1410000-3-1010-00-000-C-0 |
02-210000-3-1010-00-000-C-0 |
Late charge batch 2030 31-05-2018 |
2003 | Vision Foods | I-104 |
01-1410000-3-1010-00-000-C-0 | 01-210000-3-1010-00-000-C-0 |
Interest Invoice 2001 will have the balancing segment value assigned as 01 with the legal entity as Vision Operations. Interest Invoice 2002 will have the balancing segment value replaced as 02 with the legal entity as Vision Services. Interest Invoice 2003 will have the balancing segment value retained as 01 with the legal entity as Vision Foods.
Steps to Enable
The Processing of Late Charges by Legal Entity feature is enabled by default in the Functional Setup Manager feature opt-in page.
Additional setup is required to enable this feature. Follow these steps:
- Navigate to the Setup and Maintenance work area.
- Search for the setup task Manage Receivables Lookups.
- In the Manage Receivables Lookups page, search for the AR_FEATURES lookup type. (If the lookup type AR_FEATURES does not exist, create it first using the setup task Manage Standard Lookups.)
- Add the lookup code AR_LATE_CHARGE_BSV_OPTION to the AR_FEATURES lookup type and check the Enabled box to activate the replacement of the legal entity balancing segment value.
- Save the changes.
Tips And Considerations
This feature only applies to late charges presented as an interest invoice (Late Charge Type = Invoice).
Receivables Invoice Delivery in Universal Business Language 2.1 XML Format
You can now generate Receivables XML invoices in Universal Business Language (UBL) 2.1 format. The UBL 2.1 format is now required for business-to-government electronic invoicing in certain European countries.
Steps to Enable
The Receivables XML invoices in Universal Business Language (UBL) 2.1 format feature is enabled by default.
NOTE: The prerequisite for using this feature is to enable the Receivables Invoice Delivery in Open Applications Group Integration Specification (OAGIS) 10.1 XML Format feature in the Feature Opt-in page in Functional Setup Manager.
Tips And Considerations
The following modifications and restrictions apply to using the Receivables Invoice Delivery in Universal Business Language 2.1 XML Format feature:
- The collaboration message definition in Collaboration Messaging Framework (CMK) for UBL 2.1 format is UBL_2.1_INVOICE_OUT.
- The supported delivery method types in CMK for UBL 2.1 XML invoice delivery are B2B Adapter and Email.
- If you need to deliver UBL 2.1 invoices using any delivery method other than those supported by CMK, or if you need to add certificates and signatures to the UBL 2.1 invoice, you must use a third party service provider.
- You can add additional attributes to the UBL 2.1 invoice XML using the User-Defined Attributes of the Receivables XML feature. You map additional attributes to the UBL 2.1 invoice XML by modifying the delivered UBL 2.1 XSLT using the Manage Collaboration Message Definitions task, available from the Collaboration Messaging Framework work area.
Key Resources
Refer to the following topics in the Receivables documentation for further information on: How to setup Receivables and Collaboration Messaging Framework for delivering XML invoices; how to reprocess messages in error; and how to add user-defined attributes to XML invoices:
- Setting Up Receivables for OAGIS 10.1 XML Transaction Delivery: Procedures
- Setting Up Collaboration Messaging for OAGIS 10.1 XML Transaction Delivery: Procedures
- Setting Up OAGIS 10.1 XML Transaction Delivery Using the Customer Import FBDI: Explained
- Managing OAGIS 10.1 XML Delivery Errors: Explained
- Adding User-Defined Attributes to OAGIS 10.1 XML Receivables Transactions: Procedure
Role Information
- Users with the Accounts Receivable Manager or Accounts Receivable Specialist role can access the Collaboration Messaging work area tasks, and import CMK setup using the Customer Import FBDI process.
- Users with access to Receivables Administration Duty will have access to the Manage Collaboration Messaging Configuration and Manage Collaboration Messaging Service Providers tasks under the Setup and Maintenance work area.
Segregated Roles for Receivables
The existing Accounts Receivable Manager and Specialist roles are designed to optimize deployment efficiencies. The following new Receivables roles are now available to provide segregation of access:
- Accounts Receivable Manager Segregated Role
- Accounts Receivable Specialist Segregated Role
- Billing Manager Segregated Role
- Billing Specialist Segregated Role
- Customer Account Administrator Segregated Role
Here are the details of each of the new Receivables segregated roles:
- Accounts Receivable Manager Segregated Role: This role is the same as the existing Accounts Receivable Manager Role except it does not inherit the following privileges:
- Create Customer
- Manage Customers
- Create Receivables Invoice
- Manage Receivables Invoice
- Submit AutoInvoice Import Process
Use the Accounts Receivable Manager Segregated Role if you want to segregate the accounts receivable manager activities from:
- Creation and management of customers
- Creation and management of invoices
- Accounts Receivable Specialist Segregated Role: This role is the same as the existing Accounts Receivable Specialist Role except it does not inherit the following privileges:
- Create Customer
- Manage Customers
- Create Receivables Invoice
- Manage Receivables Invoice
- Submit AutoInvoice Import Process
Use the Accounts Receivable Specialist Segregated Role if you want to segregate the accounts receivable specialist activities from:
- Creation and management of customer
- Creation and management of invoices
- Billing Manager Segregated Role: This role is the same as the existing Accounts Receivable Manager Role except it does not inherit the following privileges:
- Create Customer
- Manage Customers
- Create Receivables Automatic Receipt Batch
- Create Receivables Receipt
- Import Receivables Receipt Batch
- Import Receivables Receipt through Lockbox
- Submit Receivables Automatic Receipt Creation Process
Use the Billing Manager Segregated Role if you want to segregate the accounts receivable manager activities from:
- Creation and management of customers
- Creation of customer receipts
- Billing Specialist Segregated Role: This role is the same as the existing Accounts Receivable Specialist Role except it does not inherit the following privileges:
- Create Customer
- Manage Customers
- Create Receivables Automatic Receipt Batch
- Create Receivables Receipt
- Import Receivables Receipt Batch
- Import Receivables Receipt through Lockbox
- Submit Receivables Automatic Receipt Creation Process
Use the Billing Specialist Segregated Role if you want to segregate the accounts receivable specialist activities from:
- Creation and management of customers
- Creation of customer receipts
- Customer Account Administrator Segregated Role: Use this role for customer maintenance activities. Access the customer maintenance tasks via the Setup and Maintenance work area. This role segregates the customer maintenance duties from:
- Billing activities, such as creation and management of invoices
- Accounts Receivable activities, such as creation and management of receipts and remittances
Steps to Enable
No steps are required to enable this feature.
Structured Payment Reference on Receivables Transactions and Receipts
Use this feature to capture a structured payment reference on Receivables transactions and receipts. Include this reference on customer invoices as text and matrix bar code. Your customers can provide this reference with their payments, improving the receipt application process and receipt reconciliation with bank statements.
Steps to Enable
No steps are required to enable this feature.
Support Transition to ASC 606 / IFRS 15
You can now specify when to transition revenue recognition from Receivables to Revenue Management by using the Support transition to ASC 606 / IFRS 15 feature.
This feature provides the following functions to enable this transition:
- Designate the date when revenue recognition of revenue management-enabled transactions ends in Receivables and begins in Revenue Management. On the date you designate, Revenue Management begins managing revenue recognition, based on your policies, that reflect the new ASC 606 and IFRS 15 accounting standard.
- Configure subledger accounting rules to end revenue accounting in Receivables and begin revenue accounting in Revenue Management.
- Disable manual adjustments of revenue management-enabled transactions in the Receivables Revenue Adjustments and Transactions Work Bench - Billing Adjustments user interfaces.
Steps to Enable
Use this feature in accordance with your overall policies for implementing the new accounting standard.
Tips And Considerations
The use of this feature is to be used in accordance with your policies in regards to executing the new accounting standard.
Key Resources
- For additional details on how to use this feature, please refer to the following MyOracle Support Doc ID 2446808.1.
Role Information
- Application Implementation Consultant
Clear Residual Account Balances on Fully Satisfied Contracts
The Clear Residual Account Balances on Fully Satisfied Contracts feature allows you to identify and automatically write off residual contract account balances that may arise due to early termination of a service in accounting contracts by creating the necessary accounting journals to clear the account balances. The newly introduced Revenue Write-off account facilitates tracking of the impact of clearing the account balances on revenue.
Using the Clear Residual Account Balances on Fully Satisfied Contracts feature, you can write-off residual balances of contracts if all of the following conditions apply to the contract:
- Fully satisfied and has undergone an early immaterial termination
- Has a residual balance adjustment status of Eligible for final adjustment
- Has the Exclude from Automatic Write-off option set to No or blank in the Edit Customer Contracts page
Billing applications or contract modifications are not accommodated on a contract after the residual balances on the contract are written off.
MANAGE SYSTEM OPTIONS FOR REVENUE MANAGEMENT
To use the Clear Residual Account Balances on Fully Satisfied Contracts feature, you must first define the Revenue Write-Off account on the Manage System Options for Revenue Management page.
RESIDUAL ACCOUNT BALANCE WRITE-OFF PROCESS
Execute the Residual Account Balance Write-Off process to:
- Identify contracts with residual balances.
- Generate write-off balances for the identified contracts by creating adjustment journal entries.
The Residual account balance write-off process provides the following processing parameters:
- Ledger – select the ledger name for which the process is to be executed.
- Residual Balance Threshold – define the threshold of the residual balance amount for a contract. Contracts with a residual balance amount of up to the predefined threshold in any of contract asset, contract liability, or contract discount accounts will be considered.
- Latest Contract Activity Date – the date on which the latest activity was performed on the contract. Contracts with latest activity of up to the predefined date are eligible to be picked up by this process.
- From Full Satisfaction Date – from date of the full satisfaction date range.
- To Full Satisfaction Date – to date of the full satisfaction date range.
- From Contract Number – beginning contract identification number of the contract number range.
- To Contract Number – ending contract identification number of the contract number range.
- Action – mode of processing of the Residual Account Balance Write-Off process.
- Review Draft – generates a list of eligible contracts selected. This is the default value for this parameter
- Perform Final Adjustment – identifies the list of eligible contracts based on the processing parameters, creates write-off journals for the contracts listed, and updates the Residual Balance Adjustment status of the contract to ‘Final adjusted’.
- Accounting Date – date used for the residual balance adjustment journal. The accounting date is required only when you run the process in Perform Final Adjustment mode.
CONTRACT RESIDUAL ACCOUNT BALANCE WRITE-OFF REPORT
The Residual Account Balance Write-Off process generates the Contract Residual Account Balance Write-Off report, which displays all of the eligible contracts based on the parameters.
The report displays the list of contracts, the full satisfaction date of each contract, the latest contract activity date of each contract, the balances of contract clearing, contract revenue, contract asset, contract liability, and contract discount accounts.
The report also displays the balances to be written off for the contract asset, contract liability, contract discount, and revenue write-off accounts.
CREATE ACCOUNTING PROCESS
Run the Create Accounting process for the revenue adjustment journal created by the Residual Account Balance Write-Off process.
MANAGE CUSTOMER CONTRACTS PAGE
The Manage Customer Contracts page will have the following two new attributes in the header:
-
Residual Balance Adjustment Status: The Residual Balance Adjustment Status is a read-only status displayed for each contract.
- Not Eligible for Final Adjustment – Initial status upon contract identification.
- Eligible for final adjustment – Contract is marked Eligible for final adjustment when it is fully satisfied and has at least one immaterial termination. A contract is deemed fully satisfied when all of the performance obligations in the contract are fully satisfied.
- Final adjusted – Contract is marked Final adjusted after the Residual Account Balances Write-Off process creates write-off journals for the contract.
- Exclude from Automatic Write-Off: Set to Yes, if you are managing your write-off outside of Revenue Management and you want to exclude the contract from the Residual Account Balances Write-Off process. The contract will be ignored by this process even if it is in Eligible for final adjustment status.
Once a contract has been final adjusted, no further processing on the contract is allowed such as discard, contract modification, or billing application.
Any revision lines received from source for a final adjusted contract will be rejected by the Validate Customer Contracts Data process and the error lines will be displayed in the Correct Contract Document Errors Spreadsheet.
Similarly billing lines received from source for a final adjusted contract will be rejected by the Import Billing Data process and the error lines will be displayed in the log if Import Billing Data process.
Steps to Enable
No steps are required to enable this feature.
Tips And Considerations
- You can view the accounting of the revenue adjustment journal in View Accounting report, Contract Activity Detail report, and Revenue Contract Account Activities report.
- You cannot discard a contract that is in Final Adjusted status..
Import Additional Satisfaction Events for Period-Based Revenue Contracts
The Import Additional Satisfaction Events for Period-Based Revenue Contracts feature allows you to temporarily hold revenue recognition without the need to cancel or terminate the existing contract and recreate a new contract.
For example, a telecommunication contract consists of a device with a talk and text plan for a period of 24 months. After nine months, the customer asks to temporarily suspend the contract for three months. In this case, the commitment end date of the contract is extended by three months. There is no regular billing and no revenue recognition during the three-month suspension period. Once the service is resumed, revenue is recognized periodically.
You can send details of the suspension or reinstatement through the Source Document Sublines tab of the Revenue Basis Data Import file-based data import template when integrating the data to Revenue Management. With this feature, you can send sublines for lines that have a satisfaction measurement model of Measure Period Satisfied as well. Two new attributes are added to the VRM_SOURCE_DOC_SUB_LINES worksheet of the Revenue Basis Data Import file-based data import template for this purpose:
- Period satisfaction event action type – This is a required attribute for the subline type code Period. Valid values are Reverse and Reinstate. Reverse indicates that revenue recognition is put on hold; Reinstate indicates that revenue recognition has resumed.
- Period satisfaction event effective date – Indicates the effective date for the period satisfaction event action. The Create Satisfaction Events process creates satisfaction events from this date. If the satisfaction event action type is Reverse it creates negative satisfaction events that result in a reversal of revenue recognition; if the satisfaction event action type is Reinstate it creates positive satisfaction events that result in revenue recognition being resumed.
To prevent revenue from being recognized, enter Reverse under the Period satisfaction event action type column and the effective date for that action under the Period satisfaction event effective date column in the VRM_SOURCE_DOC_SUB_LINES worksheet of the Revenue Basis Data Import file-based data import template. When this subline is processed, Revenue Management reverses the satisfaction events and the recognized recognized from the period satisfaction event effective date onwards.
To resume revenue recognition, enter Reinstate under the Period satisfaction event action type column and the date of reinstatement for that action under the Period satisfaction event effective date column in the VRM_SOURCE_DOC_SUB_LINES worksheet of the Revenue Basis Data Import file-based data import template. When this subline is processed, Revenue Management creates satisfaction events for that service and recognizes revenue from the period satisfaction event effective date. In this case, the plan end date is derived by Revenue Management as the original plan end date plus the number of days of suspension. Upon reinstatement, revenue is recognized from the reinstatement date to the calculated plan end date.
A contract update that is material in nature triggers a reversal of the existing allocation and accounting, and the contract is reallocated and accounted even if the contract has undergone a hold on the revenue recognition.
The Correct Contract Document Errors in Spreadsheet task launches a spreadsheet that shows the lines or sublines that fail validation, along with the relevant error message. You can rectify the errors and upload the lines for further processing. The spreadsheet now includes the following two attributes to facilitate error correction:
- Period satisfaction event action type
- Period satisfaction event effective date
Steps to Enable
No steps are required to enable this feature.
Tips And Considerations
- The new attributes in the VRM_SOURCE_DOC_SUB_LINES spreadsheet are valid only for lines which have Period as satisfaction measurement model.
- The new attributes are not valid if the corresponding line is renewed.
- The Create Contract Renewal Source Data process will not create renewal contract if revenue recognition of the base contract is put on hold and not yet resumed.
- If the base contract was suspended and reinstated before the renewal, then the Create Contract Renewal Source Data process will create the renewed contract with a start date that will be the effective plan end date of the base contract plus 1. For example, a service in the base contract has plan start date as 1 May 2018 and end date as 31 July 2018. And the service is suspended from 16 June 2018 and resumed from 1 July 2018. Upon resuming of the service, the effective plan end date of this service will be 15 August 2018. Create Contract Renewal Source Data process will create renewal contract for this base contract with plan start date as 16 August 2018.
- When a subline is received with Reinstate action and no earlier corresponding subline with Reverse option is received or processed, then the subline fails the validation and is displayed in the error correction spreadsheet.
- Period sublines will not be processed for lines that have an Immaterial change type as Immaterial.
- Sublines received with Reverse or Reinstate action corresponding to a devolved performance obligation will be ignored and not processed.
- You can send period sublines only for if the satisfaction plan is either Daily rates partial periods or Daily rates all periods.
- When a contract is discarded using the Discard Customer Contracts process, any period sublines related to the contract will also be reset and will be available for reprocessing by the Identify Customer Contracts process.
Key Resources
- Refer to Revenue Management documentation for further information on how to import revenue data and the satisfaction events from third party sources and to download the new Revenue Basis Data Import file-based data import template.
Revenue Management for Subscriptions
You can now automate your entire revenue recognition process using the new integration with Subscription Management Cloud based on your policies reflecting the new ASC 606 and IFRS 15 accounting standard.
The integration between Revenue Management and Subscription Management provides this functionality to:
- Automatically import subscription lines for subscriptions and usage-products.
- Automatically import subscription changes as revisions from Subscription Management, which are treated as retrospective accounting contract revisions in Revenue Management.
- Import various performance events from Subscription Management to record initial performance events and satisfaction events in Revenue Management.
- Import subscription billing from Receivables to Revenue Management to clear contract asset balances, record discounts or premiums, and record initial performance events.
Take full advantage of standard Revenue Management capabilities for all revenue recognition processing of subscriptions data:
- Automatically identify and create accounting contracts and performance obligations with revenue data from diverse sources.
- Determine and allocate transaction prices.
- Create accounting entries.
- Recognize revenue at a point in time or over time.
- Efficiently manage revenue based on your policies reflecting the new ASC 606 and IFRS 15 accounting standard.
Steps to Enable
This feature is available by default.
Additional setup is required to configure this feature. Follow these steps:
- Navigate to the Manage System Options for Revenue Management page.
- Click the + icon to add a row to the Source Document Types table under Integration section.
- Select the required ledger and the source document type Oracle Subscription Management.
- The Extraction Start Date is not required for Oracle Subscription Management source document type and will be greyed out.
- Click Save or Save and Close to save the record.
Tips And Considerations
- Subscription Management always sends the Unit Standalone Selling Price along with the subscriptions data.
- Revenue Management provides contract and performance obligation identification rules for Subscription Management revenue data processing.
Segregation of Duty Between Transfer to and Posting in General Ledger in Subledger Accounting
You can now segregate the posting and transfer to general ledger duty for subledger users without creating user-defined job roles by disabling the Enable Posting from Subledger Accounting option.
These changes take place when you disable the Enable Posting from Subledger option:
- The following processes will not post to general ledger, but you still have the option to transfer to general ledger:
- Create Accounting
- Create Accounting for Data Set
- Create Accrual Reversal Accounting
- Create Multiperiod Accounting
- Post Subledger Journal Entries process will transfer journal entries in Final status to general ledger without posting.
- Online accounting will transfer the journal entry to general ledger without posting if journal entries have been created successfully in final status.
- Manual subledger journal entries created from user interface or imported via spreadsheet will be transferred to general ledger without posting.
- Adjustment entries created by account override will be transferred to general ledger without posting.
You can submit Posting process separately to post subledger journals that have been previously transferred to general ledger.
Steps to Enable
Navigate to the Manage Subledger Accounting Options task, uncheck the Enable Posting from Subledger option to disallow subledger users to post subledger journals in general ledger.
By default, posting from subledger is enabled for all ledgers and subledgers.
Tips And Considerations
- The new option 'Enable Posting from Subledger' does not affect create accounting submitted by the automation feature. It will always post in general ledger if accounting is created by the automation feature regardless of the setting for the Enable Posting from Subledger option.
- If any of the above processes were scheduled to run on a regular basis, one or more of them may have the Post in General Ledger parameter set to Yes in the process. It is therefore recommended that if the Enable Posting from Subledger option is changed, cancel and reschedule these process to pick up the new setting.
- Import subledger journal entries spreadsheet downloaded prior to this release will have Final and Post to Ledger as completion status regardless of the Enable Posting from Subledger setting. The import process will validate against the Enable Posting from Subledger option to determine whether to post in general ledger or not. If posting from subledger is disabled, even though the Final and Post to Ledger status is chosen for the journal entry in the spreadsheet, it will transfer to general ledger without posting.
- If modified job roles have been implemented to segregate posting privileges for certain users, it is not necessary to uptake this new feature, unless you want to disable posting from the subledger for a specific ledger and subledger. Even if the Enable Posting from Subledger option is enabled, users who do not have posting privileges will not be able to post to general ledger.
Purchase Order Inclusive Tax Calculation
In some countries, the tax authority guidelines require that the transaction taxes are calculated and displayed as a part of the overall purchase price. The Purchase Order Inclusive Tax Calculation feature enables you to implement inclusive tax calculation on purchase orders processed in Oracle ERP Cloud.
Steps to Enable
- Navigate to the Functional Setup Manager.
- Select Manage Setup Content.
- Select Override Available Revision of Features.
- Click the Down Arrow icon and select Features.
- Select the Inclusive Tax handling in Procure to Pay flow feature to highlight it.
- Click Apply and then click Done.
- Click Save and Close.
- From the Navigator, click My Enterprise and select New Features.
- Click Offerings and select Financials.
- For the Financials offering, click Opt In Features.
- Select Financials, and click Features.
- Scroll down and locate the Inclusive Tax handling in Procure to Pay flow.
- For the Inclusive Tax handling in Procure to Pay flow feature, select the Enable check box.
- Click Done.
You can define inclusive tax rates and applicable tax rules using the Oracle ERP Cloud tax application.
NOTE: To apply inclusive tax calculation, you must set the tax inclusion method as Standard Inclusive Handling for the required inclusive tax rates.
Tax Partner Calculation for Non-Financial Applications
With the Tax Partner Calculation for Non-Financial Applications feature, you can now implement a tax partner calculation application for requisition, purchase order, sales order, and fiscal document capture transactions. However, you must select a tax partner who has the required supporting infrastructure available to properly integrate with Oracle ERP Cloud to apply transaction tax calculation on these types of transactions.
Steps to Enable
Perform the following steps to integrate the tax partner calculation application with Oracle ERP Cloud:
- On the Manage Tax Regimes page, select the Configuration Options tab.
- Assign the business unit(s) to the relevant country tax regime for partner tax calculation integration.
- Set all taxes under the country tax regime as Applicable, and enable them for both simulation and transactions purposes.
- Register the tax partner in Oracle ERP Cloud.
NOTE: You can obtain additional details from an individual tax partner.
- On the Manage Configuration Owner Tax Options page, from the Actions menu, select Manage Tax Partner Integration in a Spreadsheet to open the Manage Tax Partner Integration spreadsheet.
NOTE: If the Manage Tax Partner Integration ADFdi spreadsheet does not open, download the latest ADFdi plug-in. You can download the plug-in from the Download Desktop Integration Installer selection in the Tools menu of the Oracle ERP Cloud Navigator.
- Enter the tax partner name, connection user name, connection password, and end point URL.
NOTE: These values are provided by the individual tax partner. Only the registered tax partner names are available for selection in the Manage Tax Partner Integration ADFdi spreadsheet.
- Click Upload.
- On the Manage Configuration Owner Tax Options page, click Create.
- Enter the configuration owner, application name, event class, and start date.
- Set the regime determination set as Calculate tax by tax provider so that the Enable Tax Partner link becomes active.
NOTE: For tax partner calculation integration, sales orders don’t have unique application event classes. They use the Oracle Receivables application event classes that are enabled for tax partner calculation.
- Click the Enable Tax Partner link to view the tax partner currently registered for tax calculation purposes. Only a tax partner previously registered for tax calculation is displayed in this window.
- For the registered tax partner, select the Enabled check box, and click OK.
- Click Save and Close.
Transactional Business Intelligence for Financials
Enhancements to OTBI Expenses Subject Areas
We have enhanced the OTBI Expenses subject areas to include the following:
- Attendee information
- Cash advance details and cash advance history in the Expense Transactions Real Time subject area
- Descriptive flexfields for expense reports, expenses, attendee and cash advances
- Assignment details in Employee dimension
Steps to Enable
No steps are required to enable this feature.
New OTBI Subject Area for Cash Advances Reporting
Use the Expenses - Cash Advances Real Time subject area to review cash advances details, cash advance applications and cash advance history information.
The subject area is used to report on cash advances details, such as cash advance number, purpose, advance type, trip start and end dates, amount, adjusted amount, settlement date, and unapplied amount. The subject area is also used for reporting history information for cash advances.
Steps to Enable
No steps are required to enable this feature.
Drill Down from OTBI General Ledger Reports to General Ledger Journals
The action link framework in Oracle Business Intelligence Enterprise Edition (OBIEE) allows you to click on an object and navigate directly to the source application. Using this framework, OTBI for Financials provides the capability to drill from an OTBI ad hoc report based on OTBI General Ledger – Journals Real Time subject area to journals details in Oracle Fusion General Ledger Cloud. Links can be configured in the ad hoc GL OTBI reports to drill down to the Edit Journal screen.
Steps to Enable
No steps are required to enable this feature.
Journal Approver Name Available in GL Journals Real Time Subject Area
To monitor who is approving journals and what volumes of journals they are approving, journal approver name has been added to General Ledger - Journals Real Time subject area.
Steps to Enable
No steps are required to enable this feature.
Quarter-To-Date, Year-To-Date and Entered Currency Balance Metrics Added to the General Ledger Transactional Balances Subject Area
General Ledger - Transactional Balances Real Time subject area has been enhanced to include Quarter-To-Date (QTD), Year-To-Date (YTD) aggregated metrics, as well as entered currency balance metrics such as:
- Base Equivalent Quarter to Date (debit and credit)
- Base Equivalent Year to Date (debit and credit)
- Quarter to Date (debit and credit)
- Year to Date (debit and credit)
- Entered Quarter to Date (debit and credit)
- Entered Year to Date (debit and credit)
Steps to Enable
No steps are required to enable this feature.
Include Non-Qualified Segments for Distribution in Payables Invoices Transactions
Payables Invoices - Transactions Real Time subject area is enhanced to include non-qualified segments from the chart of accounts. The Invoice Distribution folder now displays all segments from the chart of accounts, not only the qualified segments (Balancing Segment, Cost Center, Natural Account).
Steps to Enable
No steps are required to enable this feature.
Support Notes in OTBI Receivables Subject Areas
Customer and internal notes entered in the Review Transaction pages are now available in the OTBI Receivables subject areas.
Steps to Enable
No steps are required to enable this feature.
Cross-Pillar Reporting Between SLA and Projects
Subledger Accounting - Journals Real Time subject area has been enhanced with a new folder: Project Revenue Details, to allow cross-pillar reporting with Project Billing.
Steps to Enable
No steps are required to enable this feature.
Regional and Country-Specific Features
Computation of GST Tax Liability on Receipt of Payment in Advance
The Computation of GST Tax Liability on Receipt of Payment in Advance feature provides these capabilities:
- Add receipt lines, attach tax determinants for each line, and calculate tax against the tax determinants.
- Import receipt lines and tax determinants, and calculate taxes in batches by using ADFdi.
- Generate appropriate tax accounting.
- Populate receipt lines and tax determinants against a sales order.
- Generate tax invoice number and tax invoice date for a tax invoice.
Currently, you can use this feature only in India.
Steps to Enable
The feature isn’t enabled in default. To enable the feature, you need to perform the following steps.
You must enable the feature using opt-in page in Functional Setup Manager as the following steps.
- Go to the Setup and Maintenance work area.
- Select Financials from the Setup drop down and click go to offerings in the actions drop down list.
- Click Financial work area and Click on the Change Feature Opt In.
- On the Opt In: Financials page, click the Features icon, then navigator to Regional Localization and enable ‘India’ localization.
Add the orphan privilege (Manage Advance Receipt in Tax for India) to the job role (such as Accounts Receivable Specialist) that user is assigned to perform receipt create and update.
- Go to Security Console, and copy one seed role (With ORA prefix for role code) which can perform receipt create and update, e.g. Accounts Receivable Specialist.
- Switch to Functional Security Policies tab and add Manage Advance Receipt in Tax for India privilege to the role.
- Click Next button until Submit and Close.
- Assign the custom role for Accounts Receivable Specialist to the user.
Tips And Considerations
The feature only handles the receipt with the receipt method which belongs to a receipt class that has GDF attribute 'Advance Receipt= Yes'.
Role Information
- Accounts Receivable Specialist
- Accounts Receivable Manager and so on.
Document Numbering for Receivables Transaction and Advance Receipt
You can now use the India GST Fiscal Document Numbering feature for a receipt voucher, which is issued on receipt of advance payments.
The ADFdi spreadsheet for document numbering now has the following additional columns:
- GST Fiscal Document: Use this column to specify if the document is a tax invoice or a receipt voucher.
- Third Part Tax Registration Status: Use this column to differentiate tax invoice numbering for a receivables transaction by the Third Party Tax Registration status, such as registered, non-registered, domestic, foreign customers, etc.
In addition, Localization System Options now control the enablement of India GST Fiscal Document Numbering.
Steps to Enable
The feature isn’t enabled by default. To enable the feature, you need to perform the following steps.
You must enable the feature using “Localization System Options” in Functional Setup Manager, with the detailed steps provided below.
- Sign in as a Tax Manager.
- Click Navigator > Setup and Maintenance.
- Search for the task 'Manage Localization System Options'.
- Chose business unit and country India.
- Chose ‘Yes’ for the field Enable Document Numbering.
Tips And Considerations
Any existing configuration for India GST document numbering prior to Release 13 Update 18C, will not be effective and you need to perform a fresh configuration for document numbering. If you use a document sequence that was used earlier, the numbering series will continue from the last number generated.
Thailand Withholding Tax Certificate Report and Sequence Numbering
The Thailand Withholding Tax Certificate Report and Sequence Numbering feature enables you to:
- Maintain the withholding tax certificate sequence numbering rule by using ADFdi.
- Add a revenue type in an AP invoice line by associating the tax reporting code with the product category.
- Add a PND type in a tax line by associating the tax reporting code with the tax rate.
- Add a condition in an AP payment header by using GDF.
- Generate the withholding tax certificate sequence number for AP payments.
- Generate the Thai withholding tax certificate report for AP payments according to the withholding tax certificate sequence number.
You can currently use this feature only in Thailand.
Steps to Enable
The feature isn’t enabled by default. To enable the feature, you need to perform the following steps.
You must enable the feature using opt-in page in Functional Setup Manager as the following steps.
- Go to the Setup and Maintenance work area.
- Select Financials from the Setup drop down list.
- Check Functional Areas and Click on the Change Feature Opt In.
- On the Opt In: Financials page, click the Features icon, then navigator to Regional Localization and enable ‘Thailand’ localization.
Add the duty role (APAC Financial Reporting) to the job role (such as Tax Manager) that user is assigned to manage the tax.
- Go to Security Console, and copy one seed role (With ORA prefix for role code) which can manage the tax, e.g.Tax Manager.
- Switch to Role Hierarchy tab and add role APAC Financial Reporting.
- Click Next button until Submit and Close.
- Assign the custom role to the user.
Tips And Considerations
For generate the withholding tax certificate number successfully, you have to:
- Setup the certificate numbering rule by ADFdi.
- Associate the PND Type Tax Reporting Code with withholding tax rate.
- Associate the Revenue Type Tax Reporting Code with Product Category.
- Withholding tax generated based on the payment.
- Enter the GDF Condition in payment header.
Role Information
- Tax manager for reporting in Thailand.
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
Date | Feature | Notes |
---|---|---|
20 APR 2018 | Created initial document. |
This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.
Customers Upgrading from Release 12
If you're upgrading from Release 12 to Release 13, then you should review all of the release readiness content for Release 13 (updates 17B - 17D, as well as, updates 18A - 18B) to learn about all of the features available in release 13.
GIVE US FEEDBACK
We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com
JOIN ORACLE CLOUD CUSTOMER CONNECT
Please take a moment to join the Cloud Customer Connect forums for Financials Cloud. Oracle Cloud Customer Connect is a community gathering place for members to interact and collaborate on common goals and objectives. This is where you will find the latest release information, upcoming events, or answers to use-case questions. Joining takes just a few minutes. Join now!
https://cloud.oracle.com/community
Take a look at the Customer Connect Events to help you learn more about your upgrade, and some of the new features in R13. You can sign up to attend Upcoming Events or watch replays of existing events.
Action Required to Enable Feature |
|||||
---|---|---|---|---|---|
Feature |
None (Automatically Available) |
Enable via Opt In UI Only |
Enable via Opt In UI Plus Additional Steps |
Not Enabled via Opt In UI but Setup Required |
Issue Service Request |
Ability to Clear Balances for Zero Price Transaction Line Without Bill |
|||||
Assign Standalone Selling Prices Through Revenue Basis Data Import FBDI |
|||||
Changes to Allocated Revenue on Open Performance Obligations Due to Immaterial Changes |
|||||
Devolve Performance Obligations Associated with Revenue Contracts |
|||||
View Consolidated Account Activity for Revenue Contract Group |
|||||
Drill Down From OTBI Payables Reports to AP Transaction Details |
|||||
Expose Description Columns in Essbase for Non-Qualified Segments |
|||||
Improved Cross-Pillar Reporting Between Projects and Receivables |
|||||
Common Technology and User Experience
Enhanced Data Segregation for Third-Party Service Providers
In Oracle Financials Cloud many transactions, such as payables invoices, payment requests, assets, and expense reports, include references to employees or persons. We allow any employees or persons defined in Oracle Financials Cloud to be referenced in these transactions. For third-party service providers who may be managing business processes from multiple entities, additional restrictions on employees may be required. With this enhancement, we have enabled data security to these references.
The following table lists the places where data security for references on employees, workers, and users is enabled.
Product | Task | Field |
---|---|---|
Assets | Asset Inquiry | Employee |
Add Asset | Employee | |
Prepare Source Lines | Preparer | |
Manage All Books | Preparer | |
Add Asset in Spreadsheet | Preparer Employee | |
Transfer Assets | Employee (Asset Selection Criteria) Employee (Transfer Details) | |
Perform What-If Analysis | Employee | |
Manage Asset Distribution Sets | Employee | |
Receivables | Manage Customer -> Edit Customer | Credit Analyst (Profile History) |
Manage Customer -> Edit Account | Credit Analyst (Profile History) | |
Manage Customer -> Edit Site | Credit Analyst (Profile History) | |
Credit Reviews | Credit Analyst | |
Manage Receivables Customer Profile Class | Credit Analyst | |
Manage Approval Limits | User | |
Collections | Manage Collectors | Employee |
Payables | Create Payables Invoice | Preparer |
Import Payables Invoice | Preparer | |
Submit Payment Process Request | First Approver | |
Manage Payment Process Request Template | First Approver | |
Expense | Manage Corporate Cards | Employee |
Manage Historical Credit Card Transactions | Employee | |
Review Corporate Card Transactions | Employee | |
Manage Expense Reports | Employee | |
Manage Expense Audit List Membership | Employee | |
Manage Cash Advances | Employee | |
Manage Expenses Contingent Worker | Employee | |
Review Payment Requests | Employee | |
Review Invoices | Contingent Worker | |
Manage Expense Reports | Employee | |
About Me -> Manage Delegates | Person |
Steps to Enable
To minimize upgrade impact, data security policies are shipped against predefined roles that need to access employees, workers, and users to provide access to all employees by default.
To implement enhanced data segregation, these predefined data security policies need to be replaced with data security policies that are more restrictive. Since predefined roles cannot be modified, such changes need to be made against copies of the predefined roles.
Steps to enable this feature are documented in the whitepaper Implementing Enhanced Data Segregation (Doc ID 2324377.1) available on My Oracle Support.
Role Information
The following predefined roles now include a new data security policy:
- Accounts Payable Manager
- Accounts Payable Specialist
- Accounts Payable Supervisor
- Accounts Receivable Manager
- Accounts Receivable Specialist
- Asset Accountant
- Asset Accounting Manager
- Collections Manager
- Financial Application Administrator
NOTE: Predefined roles in Expenses, including Corporate Card Administrator, Expense Auditor, Expense Audit Manager, and Expense Manager, do not include predefined data security policies that provide access to all employees by default.
Configurable Workflow Notifications
Oracle Financials Cloud lets you use Business Intelligence Publisher for workflow notifications. The templates are optimized for mobile devices and are easily configurable. Choose from a comprehensive list of attributes to modify the workflow notifications according to your requirements. You can change both layout and content – add images, change colors and styling, add or remove attributes or modify text.
Support for additional Expenses notifications and for Budgetary Control override requests is added in this release.
Steps to Enable
The feature needs to be enabled using the Feature Opt In page in Functional Setup Manager. It is not enabled by default.
To enable the feature, complete these steps:
- Go to the Setup and Maintenance work area.
- Select Financials from the Setup drop down.
- Click on the Change Feature Opt In.
- On the Opt In: Financials page, click the Features icon for the product for which you wish to enable the feature (Expenses or Budgetary Control and Encumbrance Accounting).
- On the Edit Features page, select the Enable option for each type of notification that you want to enable the feature for.
- Click on Done to go back to the Setup: Financials page.
Tips And Considerations
- Use the predefined email templates with no additional changes or modify them according to your business requirements.
- Preview your changed email templates before publishing.
- Revert to the classic approval notifications at any time by disabling the feature using the Feature Opt In page in Functional Setup Manager.
Key Resources
- Financials Configurable Workflow Notifications: Overview
- Configurable Workflow Notifications: Implementation Considerations (Doc ID 2215570.1) on My Oracle Support
As you review your budget on the Review Budgetary Control Balances page, you can select budget accounts that require budgetary transfers and add them to a Budget Transfer Request.You can transfer between any combination of budget accounts within the same budget period or budget year.
To transfer budget within a budget period, enter a search criteria with the Amount Type set to Period to date. The budget period of the transfer is based on the budget period of the selected accounts.
To transfer budget on an annual basis when the underlying control budget is on a monthly basis, enter a search criteria with the Amount Type set to Year to date and the Budget Period set to the last month of the year. The budget year of the transfer is derived from the budget period of the selected accounts.
After selecting the accounts to be transferred, click the Budget Transfer Request icon to open the request.
The budget accounts and period context for your Budget Transfer Request are predefined for you. Specify the budget amounts to transfer, and a Justification.
When transferring budget amounts on an annual basis, the Budget Transfer Request expects that the budget amounts you enter are annual amounts. Specify the Allocation Method for “All budget periods equally” to allocate the annual budget transfer amount evenly to all periods, or “First budget period” to allocate the amount to the first month of the year.
Submit the request to execute the Import Budget Amounts process to update the budget amounts.
When the budget transfer request is successful, you will receive a notification.
Steps to Enable
No steps are required to enable this feature.
Tips And Considerations
The new budget transfer action is available on the Review Budgetary Control Balances page for control budgets defined with a Source Budget Type of ‘Hyperion Planning’ and ‘Other’.
Role Information
The Import Budget Amounts (XCC_IMPORT_BUDGET_AMOUNTS) privilege is required to gain access to the Transfer Budget action on Review Budgetary Control Balances. This privilege is a member of the Budgetary Control Management Duty Role. Therefore any roles, such as budget manager, that inherit the Budgetary Control Management Duty Role will have access to the Transfer Budget action.
Disable Scan Option on Mobile Expenses
You can disable the Scan option on the Expenses mobile application by configuring a profile option.
Steps to Enable
To disable the Scan option, define the profile option EXM_MOBILE_DISABLE_SCAN and set the profile option value to Y.
To define the profile option, follow these steps:
- In the Setup and Maintenance work area, navigate to the Manage Profile Options page.
- On the Manage Profile Options page, click the Create (+) icon.
- On the Create Profile Option page in the Profile Option Code field, enter EXM_MOBILE_DISABLE_SCAN.
- In the Profile Display Name field, enter a profile display name.
- From the Application choice list, select Expenses.
- From the Start Date field, enter a start date.
- Click Save and Close.
- On the Manage Profile Options page in the Profile Options Levels section, select Site as the Level value.
- Select both the Enabled and the Updateable check boxes.
- Click Save and Close.
To define the profile option value, follow these steps:
- In the Setup and Maintenance work area, navigate to the Manage Administrator Profile Values page.
- Search for profile option code EXM_MOBILE_DISABLE_SCAN.
- In the Search Results: Profile Options section, select the EXM_MOBILE_DISABLE_SCAN profile option.
- In the Profile Values section, click the Create (+) icon.
- From the Profile Level choice list, select Site.
- From the Profile Value choice list, select Yes.
- Click Save and Close.
Role Information
You must have one of the following roles to disable the Scan option:
- Application Implementation Consultant
- Financial Administrator
- Expense Manager
Itemization of Meals Expense Categories
You can now itemize meals expense categories. Itemizing meals helps you capture the breakdown of meal expenses, such as tips and taxes.
Steps to Enable
To itemize a meal expense type, follow these steps:
- In the Setup and Maintenance work area, navigate to the Manage Expense Report Templates task.
- On the Manage Expense Report Templates page, select the applicable template and click the Edit icon.
- On the Expense Types tab, select the meal expense type that you want to itemize and click the Edit icon.
- On the itemization tab, select one of the following values from the Itemization choice list:
- Enabled to optionally enable itemization.
- Required to make itemization mandatory.
- Click the Include check box for the expense types that you want to make available for itemization.
- Click Save and Close.
Role Information
You must have one of the following roles to enable meals itemization:
- Application Implementation Consultant
- Financial Administrator
- Expense Manager
Configure Auditable Setup Attributes and View Audit Report
You can now configure setup attributes for audit from the Setup and Maintenance work area to maintain internal control over the validity of the enterprise transaction system. After configuration, you can track changes to these attributes using the Audit Report.
The following business setup objects are enabled for audit in General Ledger:
- Account Combinations
- Accounting Automation
- Allocations and Periodic Entries
- Accounting and Reporting Sequences
- AutoPost Criteria Sets
- Chart of Accounts Mapping
- Daily Conversion Types
- Encumbrance Types
- Encumbrance Carry Forward Rules
- Intercompany Processing Rules
- Journal Categories
- Journal Sources
- Journal Reconciliation Rules
- Journal Reversal Criteria Sets
- Ledgers
- Revaluations
- Suspense Accounts
Steps to Enable
Navigate to the Setup and Maintenance work area to configure the auditable setup attributes:
- Select the Manage Audit Policies task.
- Select the Configure Business Object Attribute.
- Select the product, business object, and attributes for audit enablement.
- Save the selection.
To view the audit report:
- From the Navigator, select Tools to open the Audit Reports.
Key Resources
Streamlined Payment Processing
During the payment process request, the installments selection process confirms that the business unit, currency, and payment method of the installment matches the usage rules defined on the payment process profile.
Similar matching occurs between the business unit and currency of the installment and the internal bank account. An installment is not selected if it is within the selection parameters, but does not match the configuration of the payment process profile or the internal bank account.
Matching during the installments selection process prevents later installment rejections during the build payment process due to a mismatch of installment attributes with the payment process profile or the internal bank account.
Steps to Enable
Enable the feature from the Functional Setup Manager Feature Opt In page. The steps are:
- Go to the Setup and Maintenance work area.
- Select Financials in the drop-down list at the top of the page.
- Click Change Feature Opt In.
- On the Opt In: Financials page, click the Features icon for Payables.
- On the Edit Features: Payables page, select the Enable icon for Streamlined Payment Processing feature.
- On the Feature Name: Streamlined Payment Processing pop-up window, select option Restricted Installments Selection and click Save and Close.
- Click Done on Edit Features: Payables page to return to the Setup: Financials page.
Flexible Routing and Approval of Receivables Credit Request
You can now configure Oracle Business Rules to determine whether a credit request against a Receivables transaction requires a manual review to create a credit memo. The notification process informs users of any required actions. Users will also be able to capture additional information on the credit request or on subsequent workflow notifications.
Two new human tasks are available to manage this process.
- FinArTrxnsCreditMemosAutomaticManual: To configure the decision for using a manual review to create a credit memo. This human task does not invoke any workflow notifications.
- FinArTrxnsCreditMemosCreationPostProcess: To initiate the workflow for manual review to create a credit memo, based on the decision from the previous human task FinArTrxnsCreditMemosAutomaticManual. You can configure multiple reviewers for this workflow through the task configuration assignee rules. Reviewers can review the credit request details and perform the required actions, including the creation of a credit memo for the requested amount. They can also capture and/or update additional information on the credit request using the new Review Credit Memo Request page.
You can use additional attributes within the Assignee rule conditions to configure the routing rules for both the existing and the new human tasks. These attributes include –
- Salesperson Name
- Salesperson Email ID
- Sum of all Adjustments Amounts
- Sum of all Receipts Amounts
- Credit Memo Reason Code Descriptive Flexfield Attribute 1 – 15
- Invoice Line Description
- Collector Descriptive Flexfield Attribute 1 – 15
- Line Level Credit
- Invoice Line Type
- Invoice or Line Adjustments
- Receipts Applied
- Receivables System Options Descriptive Flexfield Attribute 1 – 15
- Item Number
- Line Amount Requested
- Transaction Information Descriptive Flexfield Attribute 1 – 15
- Revenue Scheduling Rule Start Date
- Revenue Scheduling Rule End Date
- Revenue Scheduling Rule Number of Periods
- Revenue Scheduling Rule Rule Type
- Revenue Scheduling Rule Name
- Tax Credit Amount Requested
You can capture an additional attribute Dispute Type on the Manage Disputes page, to classify a transaction dispute. It can be updated from the Review Credit Memo request page, which can be accessed from FinArTrxnsCreditMemosApproval workflow notifications.
The Review Credit Memo Request page allows you to review the credit request information and do updates to the attributes like Dispute Type, Rebill Number, and Rebill Group. This page can be accessed from FinArTrxnsCreditMemosApproval and FinArTrxnsCreditMemosCreationPostProcess workflow notifications.
Steps to Enable
This feature is automatically opted in through the release update. To configure the feature for manual creation of a credit memo, you must complete these additional steps:
- Configure the Assignee Rules for the new SOA human task FinArTrxnsCreditMemosAutomaticManual with the output value HtOutcmeCreateManualCreditMemo. By default, FinArTrxnsCreditMemosAutomaticManual is set as 1 is 1 rule for automatic processing.
- Configure the Assignee Rules for the new human task FinArTrxnsCreditMemosCreationPostProcessing based on the earlier human task output value. You can configure different workflow approval models based on whether credit memo creation is manual or automatic. By default, it is set as 1 is 1 rule to ignore the manual process, that is, if the output of the earlier human task for Task.payload.CMCreationType is Automatic, then this process is ignored.
In addition to it, you can optionally use the lookup type ORA_IEX_DISPUTE_TYPE_CODE to extend the seeded values provided for the Dispute Type.
Tips And Considerations
A default BIP report is available as part of the human task 'FinArTrxnsCreditMemosCreationPostProcessing'. This is available in the folder path Shared Folders -> Financials -> Workflow Notifications -> Receivables -> Billing, with name 'Manual Credit Memo Request Notification'. You can copy the standard version of this report layout and customize its content using the existing BIP features.
Role Information
Three new privileges are available in the context of the new Review Credit Memo Request page:
- Review Credit Request (to view the Review Credit Request page, View Transaction Activities button, and Internal Comments attribute)
- Update Dispute Type on Credit Request (to allow an update to the Dispute Type attribute)
- Update Re-bill Details on Credit Request (to allow an update to the Re-bill Number and Re-bill Group attributes)
The privilege Review Credit Request is added by default to the Duty Roles Billing Management Duty and Collections Management Basic. You can add the other two privileges—Update Dispute Type on Credit Request and Update Re-bill Details on Credit Request—to the required duty roles based on the update authorizations given to specific users.
Ability to Clear Balances for Zero Price Transaction Line Without Bill
You can now automatically create a billing line with an amount of zero (for free goods or services) when a revenue source document line with a unit selling price of zero is imported into Revenue Management, and apply the bill line to the performance obligation value, thus clearing out the right to bill.
Revenue Management will create a zero bill line on full satisfaction of the transaction line to clear out the balances in contract asset and allocated discount accounts.
When the full satisfaction status of a zero priced transaction line is revised due to revisions, Revenue Management discards the system generated zero bill line and its accounting and creates a new zero bill line based on the new full satisfaction date.
If the source system sends a zero bill line after Revenue Management had created a zero bill line, the zero bill line generated by Revenue Management is discarded, and its accounting is reversed. Accounting entries will be created according to the zero bill line received from the source system.
When the full satisfaction status is attained, Revenue Management generates a zero bill line only if no zero bill line was received from the source system.
Steps to Enable
No steps are needed to enable this feature. This feature is available by default.
Key Resources
Refer to Revenue Management documentation for further information on how to import revenue data using Revenue Basis Data Import file-based data import and how to import billing data using Billing Data Import file-based data import.
Role Information
No new role access is needed to use this feature.
Assign Standalone Selling Prices Through Revenue Basis Data Import FBDI
Assign Standalone Selling Prices through Revenue Basis Data Import file-based data import provides the flexibility to import unit standalone selling price (SSP) of an item or memo line for the source document line through Revenue Basis Data Import file-based data import.
For customers who calculate and manage the standalone selling prices in third party systems, this feature provides the ability to import the unit SSP of an item or memo line along with the source document line through revenue basis data import file-based data import.
For customers who feed the unit standalone selling price through the Revenue Basis Data Import file-based data import, Revenue Management will not calculate or manage SSPs, the following setups related to managing SSPs can be bypassed:
- Manage Standalone Selling Price Profiles
- Manage Pricing Dimensions Value Sets
- Manage Pricing Dimension Structures
- Manage Pricing Dimension Assignments
- Manage Pricing Dimension Bands
- Manage Standalone Sales Pool Exclusion Rules and
- Manage Item Groups
Create Contract Renewal Source Data process copies the value of Unit SSP sent through the file-based data import while renewing the contract.
Steps to Enable
No steps are needed to enable this feature.
Tips And Considerations
- The value for Unit SSP sent through Revenue Basis Data Import file-based data import can be revised only until the contract is frozen.
- The value for Unit SSP should be an absolute value.
- If available SSP in a third party system is tracked as discount percentage of unit list price or gross margin percentage or perecentage of base unit price, only an absolute value of unit SSP can be sent through the Revenue Basis Data Import file-based data import.
- The values for Unit list price, Cost amount and Base price are irrelevant when unit SSP is sent through the Revenue Basis Data Import file-based data import.
- It is assumed that the approval has happened outside Revenue Management for the unit SSPs fed through Revenue Basis Data Import file-based data import.
- This feature can be used along with the existing standalone selling prices features supported by Revenue Management. For example, you can import unit SSP for a particular item or classification of items through Revenue Basis Data Import file-based data import and continue using the Observed standalone selling price or Estimated selling price for others.
Key Resources
Refer to Revenue Management documentation for further information on how to import revenue data using Revenue Basis Data Import file-based data import.
Role Information
No new role access is needed to use this feature.
Automatic Renewal of Revenue Contracts
You can now automatically renew customer contracts when the initial service term ends without receiving a new order (revenue) line for each renewal. You can either renew the original accounting contract or convert it to new periodic accounting contract, such as a month-to-month contract.
Revenue Management creates a new accounting contract for designated services for the period and amount, as indicated on the initial accounting contract. A new accounting contract is created at the end of each service period until terminated.
Indicate the period-based service lines to be renewed by defining the following recurring attributes on the original order line with the Revenue Basis Data Import:
- Recurring Indicator
- Recurring Frequency
- Recurring Pattern
- Recurring Amount
You then submit the Create Contract Renewal Source Data program to renew eligible expired recurring promised detail lines.
The process:
- Scans promised details lines for your existing performance obligation to determine which lines have reached their plan end date.
- Determines renewal eligibility of the promised details line and contract.
- Locates the latest source document header and line version for the eligible promised details line.
- Creates new source document headers and lines by using the latest source document version line, and then updates the data to reflect the new plan period and amount or termination.
- Writes the new source document header and lines to the source document tables for further processing.
After the process is complete, submit the Validate Customer Contract Source Data and Identify Customer Contracts programs to process the newly received source documents and lines into new accounting contracts.
Steps to Enable
There are no steps to enable this feature.
Key Resources
Refer to Revenue Management documentation for further information on how to import revenue data using Revenue Basis Data Import FBDI.
Role Information
Users with the job roles Revenue Manager or Revenue Analyst can access the Revenue Basis Data Import FBDI to define recurring attributes and execute the Create Contract Renewal Source Data process.
Changes to Allocated Revenue on Open Performance Obligations Due to Immaterial Changes
For immaterial changes on a contract, you can now reallocate revenue on open performance obligations on the current and future periods only, without impacting revenue that has been recognized.
This feature provides the following benefits:
- Modify an existing accounting contract.
- Prospectively reallocate and account open obligations as of the contract revision date.
- Uses the standalone selling prices on the contract revision date to reallocate unrecognized contract revenue to new performance obligations.
- Uses the standalone selling prices on the contract inception date to reallocate unrecognized contract revenue to existing obligations.
- Does not adjust or reverse performance obligations that are recognized on the contract revision date.
- Prospectively accounts revisions of performance obligations when the Satisfaction Measurement Model is Period and the Satisfaction Plan Name is Daily Revenue Rate, Partial Periods.
- Revenue Management processes the entire contract as an immaterial change if all of the changes processed at the same time are marked as immaterial.
- Processes the entire contract as a material change if the revisions to the existing contract consist of a mix of material and immaterial changes.
- If multiple revisions are processed at the same time, sets the contract revision date to the earliest revision date for the purpose of revenue reallocation.
- Retrospectively allocates revisions for accounting contracts that were generated on the basis of performance obligation templates.
- Reverses or adjusts initial performance accounting entries for terminated obligations and other open obligations on the contract revision date.
- Books and adjusts accounting entries related to billing of immaterial revisions when billing amounts are interfaced to Revenue Management.
In the Source Document Types setup page, you can set the default value of the Immaterial Change Type to Immaterial change if most of your revisions are immaterial changes. You can override the immaterial change type on the Revenue Basis Data Import file-based data import when importing revisions from the source systems.
Populate the following new attributes in the Revenue Basis Data Import file-based data import to prospectively reallocate and account the contract revisions.
ENHANCED MANAGE CUSTOMER CONTRACT PAGE:
When you make an immaterial change to your contract, revenue that was not recognized on the contract revision is reallocated on all of the open performance obligations within the contract. Revenue recognized as of the contract revision date remains intact. Any unrecognized revenue as of the contract revision date is reallocated to open performance obligations.
On the Manage Customer Contracts page, you can review the immaterial change calculations in the Contract Revision Details subtab under the Promised Details and Performance Obligations tabs. Only contract revision details associated with immaterial changes are displayed in the Contract Revision Details subtabs.
Steps to Enable
No steps are needed to enable this feature. This feature is available by default.
Tips And Considerations
This example illustrates a contract update resulting in a revision to the existing contract:
- The initial customer contract has three performance obligations for telephone, voice plan, and data plan. The phone is subsidized, and the voice and data plans cover a 24-month subscription period.
- The data plan upgraded from WR18533 to WR23763 starting from the start of 4th month.The business entity wants to treat this as an immaterial change and:
- Revise an existing contract.
- Calculate the revenue that was not recognized when the contract was revised for all open performance obligations.
- Reallocate unrecognized revenue using the standalone selling price basis, as of the contract revision date for new performance obligation and the contract inception date for existing open performance obligations.
- Recognize revenue in current and future periods only.
Initial Data File:
Data file for termination of service ‘WR18533’ and upgrade to service ‘WR23763’:
Use the Revenue Basis Data Import file-based data import to import revisions to your order lines or sales data from your source application to reflect the contract modifications to be applied. For successful processing of immaterial changes, ensure that the following attributes are included with the source document data in the Revenue Basis Data Import file-based data import:
TERMINATION ONLY USE CASE:
Termination Line Details
Attribute |
Expected Value |
---|---|
Quantity |
Revised line quantity |
Unit Selling Price |
Unit selling price of revised line |
Line Amount |
Revised line amount |
Performance Satisfaction Plan End Date |
Revised performance plan end date |
Termination Date |
Line termination date |
Immaterial Change Option |
Immaterial Change Option for terminated line (if not provided then default from Source Document Types setup page will be used) |
Contract Revision Date |
Contract Revision Date <Should be Termination Date + 1> |
Version Line |
Y |
Version Line Number |
Greater than earlier version number |
UPGRADE USE CASE:
Termination Line Details
Attribute |
Expected Value |
---|---|
Quantity |
Revised line Quantity |
Unit Selling Price |
Unit selling price of revised line |
Line Amount |
Revised line amount |
Performance Satisfaction Plan End Date |
Revised performance plan end date |
Termination Date |
Line termination date |
Immaterial Change Option |
Immaterial Change Option for terminated line (if not provided then default from Source Document Types setup page will be used) |
Contract Revision Date |
Contract Revision Date <Should be Termination Date + 1> |
Version Line |
Y |
Version Line Number |
Greater than earlier version number |
New Line or Upgraded Line details
Attribute |
Expected Value |
---|---|
Quantity |
New line quantity |
Unit Selling Price |
Unit selling price of new line |
Line Amount |
New line amount |
Performance Satisfaction Plan Start Date |
New performance plan start date |
Performance Satisfaction Plan End Date |
New performance plan end date |
Performance Satisfaction Plan Duration |
New performance plan duration |
Termination Date |
|
Immaterial Change Option |
Immaterial Change Option for new line (if not provided then default from Source Document Types setup page will be used) |
Contract Revision Date |
Contract Revision Date |
Add to Existing Contract |
Y |
Action code for adding new line to existing contract |
CREATE NEW PO |
Version Line |
N |
Key Resources
Refer to the Revenue Management documentation for further information on how to import revenue data using Revenue Basis Data Import file-based data import.
Role Information
No new role access is needed to use this feature.
Devolve Performance Obligations Associated with Revenue Contracts
You can now devolve a performance obligation into a series of performance obligations over time for service-based revenue contract lines.
This feature provides the following benefits:
- Automatically devolves a performance obligation into a series of performance obligations based on your setup on the Manage Performance Obligation Identification Rules page.
- Devolves performance obligations by accounting period.
- Includes a new Details Series subtab on the Manage Customer Contract page, which shows the automatically devolved performance obligations.
- Displays the logically split obligations for each accounting period along with the performance obligation amount, allocation amount, revenue recognized amount and initial performance amount on the Series tab on the Manage Customer Contract page.
- Creates the initial performance event for each obligation in the performance obligation series with the date as the first day of the accounting period.
- Uses the Daily Revenue Rate, Partial Periods rule to calculate the amounts displayed on the Details Series subtab.
- Automatically devolves implied performance obligations into a series of performance obligations based on setup in Manage Implied Performance Obligation Template page.
- Recalculates performance obligation series when contracts are revised or when products are returned.
Set the Devolve Performance Obligation option to Yes to devolve a performance obligation on the Edit Performance Obligation Identification Rule setup page.
Set the Devolve Performance Obligation option to Yes to devolve an implied performance obligation on the Edit Implied Performance Obligation Template setup page.
On the Performance Obligations tab on the Manage Customer Contracts page, you can review the automatically devolved performance obligations in the Series subtab under Details.
Steps to Enable
No steps are needed to enable this feature. This feature is available by default.
Tips And Considerations
- The use of this feature is driven by your company business practice and policy regarding the schedule of recording contract liability for given products and services.
Key Resources
Refer to the Revenue Management documentation for further information on how to configure performance obligation identification rules and implied performance obligation template rules.
Role Information
Users with the job roles Revenue Manager or Revenue Analyst can configure performance obligation setups to devolve a performance obligation into a series of performance obligations.
View Consolidated Account Activity for Revenue Contract Group
You can now view the consolidated accounting activities associated with all revenue contracts within a contract group or for an individual contract.
Assign contracts to a contract group by enabling the Use as Contract Group Number attribute on the Create Contract Identification Rule page or by enabling the Automatic Renewal of Revenue Contracts feature.
Indicate the grouping attribute to be used to assign the contract group number on the Create Contract Identification Rule page.
When the contract is created during the Identify Customer Contracts process, the contract group number is assigned using the attribute selected as Use as Contract Group Number in the Contract Identification Rule. If no attribute is designated and the contract is a recurring contract, a contract group number is assigned by Revenue Management when the contract renews as a new recurring contract.
You can view consolidated account activity for your revenue contract group by clicking the View Contract Activities button after selecting the row with the appropriate Contract Group Number on the Manage Customer Contracts page.
You can also view the report by selecting the View Contract Activities option in the Action window on the Edit Customer Contract page for the individual contract.
The Contract Activity Detail report displays the consolidated account activity for all of the contracts within the assigned contract group. If the contract does not belong to a contract group, the Contract Activity Detail report displays the accounting activity for the individual contract only.
The report lists the contract account balances by accounting date, accounting event, performance obligation, and promised detail line for each contract within the contract group.
Steps to Enable
No steps are needed to enable this feature.
Tips And Considerations
System Options for Revenue Management
The View Contract Consolidated Account Activity for Revenue Contract Group uses journal entries from the primary ledger to display the accounting activity. If you are using a ledger other than the primary ledger as your Revenue Management ledger, then you need to indicate the name of the ledger you are using in the Revenue Management Ledger attribute on the Manage System Options for Revenue Management page.
Key Resources
Refer to the Revenue Management documentation for further information on how to enable attributes on the Create or Edit Contract Identification Rule page to be used as a contract group number.
Role Information
Users with the job roles Revenue Manager or Revenue Analyst can execute the View Contract Activity action.
Transactional Business Intelligence for Financials
Drill Down From OTBI Payables Reports to AP Transaction Details
The action link framework in Oracle Business Intelligence Enterprise Edition (OBIEE) allows you to click on an object and navigate directly to the source application. Using this framework, OTBI for Financials provides the capability to drill from an OTBI ad-hoc report based on a Payables OTBI subject area to the Invoice and Payment Details in Oracle Payables Cloud.
Hyperlinks can be configured in the ad-hoc Payables OTBI reports to drill down to the following:
- View Invoice details
- Edit an Invoice
- View Payment details
- Create a Payment
Steps to Enable
The high level steps to configure a drill down from OTBI ad-hoc reports to Invoice or Payment transaction details are:
- Create an ad-hoc report using the appropriate Payables subject area.
- Select the column for which you wish to configure the drill down to transaction details.
- In the ‘Column Properties’, setup an Action link to drill down to the required transaction details.
For details on specific drill downs and examples, search for 'How to drill down from OTBI ad hoc reports to transaction details in Oracle Fusion Applications' white paper, soon to be available on Customer Connect.
Key Resources
For details on specific drill downs and examples, search for 'How to drill down from OTBI ad hoc reports to transaction details in Oracle Fusion Applications' white paper, soon to be available on Customer Connect.
Expose Description Columns in Essbase for Non-Qualified Segments
The General Ledger - Balances Real Time Subject Area has been enhanced to expose the description columns for non-qualified segments.
Steps to Enable
No steps are required to enable this feature.
Improved Cross-Pillar Reporting Between Projects and Receivables
OTBI for Receivables has been enhanced to support receivables reporting by project contracts.
In the Receivables - Transactions Real Time subject area, 'Transaction Details' > 'Project Contract Header Details' folder has been expanded to include information on project contracts. Users with the appropriate Projects subject area access can access Projects information in the Receivables subject area.
Steps to Enable
No steps are required to enable this feature.
New OTBI Subject Area for Asset Balances Reporting
Use the Fixed Assets - Asset Balances Real Time subject area to review balances for Cost, CIP Cost, Depreciation Reserve, Bonus Depreciation Reserve, Impairment Reserve, and Revaluation Reserve balance sheet accounts.
You can report on additions, adjustments, depreciation, impairments, retirements, revaluations, transfers, and unplanned depreciation during a period, and analyze summarized information by employee, which includes beginning and ending balance details.
For each asset, the subject area includes accounting details, asset book information, account balance details, category details, asset type, asset location, asset cost center, manager, employee, and asset account information.
Steps to Enable
No steps are required to enable this feature.
Regional and Country-Specific Features
Mexican Electronic Accounting Version 1.3
The Mexican Electronic Accounting version 1.3 feature includes the following three major enhancements:
- Compliance with XML reporting version 1.3
Compliance with XML reporting version 1.3 is required by the Mexican Tax Authority (SAT). It includes minor technical changes to all reports, i.e. Chart of Accounts, Trial Balance, Journal Entries and Accounts Auxiliary report. It also includes the reporting of proof of payments made and received (known as ´Comprobante de Pagos´), where key information such as CFDI Fiscal Unique Identifier and Taxpayer ID can now be captured through corresponding fields in the Additional Information region of the Cash Receipts and Payments transactions, and XML elements get generated to report such payment proof transactions.
- Inclusion of expense report accounting entries as part of the Mexican Electronic Accounting reporting
This enhancement impacts the Journal Entries (Polizas) report, that now generates XML elements to represent the expense report invoices, entered in Payables, either manually or imported from Expenses or legacy systems, where key information such as CFDI Fiscal Unique Identifier and third party Taxpayer ID are captured through existing merchant related fields such as Merchant Document Number and Merchant Taxpayer ID at invoice distributions level.
- Ability to identify and report journals entered in GL
This enhancement provides the ability to capture CFDI Fiscal Unique Identifier and Taxpayer ID information through corresponding fields in the Additional Information region, for manually entered or imported journals either at journal header or journal line levels, and generate XML elements such as CompNal for the journals that do have such information associated to them.
Steps to Enable
The feature is automatically available. Make sure users have access to the LAD Financial Reporting Duty role to access the reports.
Tips And Considerations
- Ensure that CFDI Fiscal Unique Identifier and Taxpayer ID fields are entered as additional information for any proof of payment transactions that require electronic accounting reporting.
- Ensure that CFDI Fiscal Unique Identifier and Taxpayer ID are entered as Merchant related fields in any Oracle Payables expense invoice that require electronic accounting reporting.
Role Information
- LAD Financial Reporting Duty
Tax Point Date Adjustment Using Spreadsheet
You can now use the Tax Point Date Adjustment feature to change the tax point date of multiple Payables or Receivables transactions using spreadsheet capabilities.
- Select the Payables or Receivables transactions at header and/or line level.
- Download the selected transactions to your spreadsheet application.
- Use the spreadsheet features to assign new tax point dates as applicable.
- Upload the modified spreadsheet to the application.
- Process the uploaded data to update the tax point date of the transactions in Payables or Receivables.
Please remember that adjusting the Tax Point Date of already reported transactions may result in a need to resubmit the Tax reports for the impacted tax periods.
PROCESSING
Submit the Select Transactions for Tax Point Date Adjustment process.When submitting the process, provide the criteria to identify which transactions should be selected, and the level of detail for the extract – transaction headers only, or both transaction headers and lines.
When the selection process completes successfully, download the comma-separated values (csv) output file to your spreadsheet application.Use macros, or other spreadsheet functionality to assign new tax point dates where applicable, and save your changes in csv format.
Upload the modified file to the Cloud applications using the Universal Content Management (UCM) infrastructure features.
Submit the Process Tax Point Date Adjustments process, select Process Type of Import. This process identifies which tax lines of a transaction require the tax point date to be updated, and processes those changes.
Steps to Enable
If you have previously enabled the Process Tax Point Date Adjustments feature, there are no additional steps required to use this feature.
Tips And Considerations
Complete all solution related setup for Payables and Receivables before using the Tax Point Date Adjustment feature.
Key Resources
- Oracle® Fusion Applications Financials Implementation Guide, Release 13
- Tax Point Date Adjustment Topical Essay
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
Date | Feature | Notes |
---|---|---|
25 MAY 2018 | Receivables Invoice Delivery in Open Applications Group Integration Specification 10.1 XML Format | Updated document. Revised feature information for clarity. |
25 MAY 2018 | Store Printed Receivables Transactions as Attachments | Updated document. Revised feature information for clarity. |
25 MAY 2018 | Web Service to Create Reference Accounts for Customers | Updated document. Revised feature information for clarity. |
19 JAN 2018 | Created initial document. |
This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.
Customers Upgrading from Release 12
If you're upgrading from Release 12 to Release 13, then you should review all of the release readiness content for Release 13 (updates 17B - 17D, as well as, updates 18A - 18B) to learn about all of the features available in release 13.
GIVE US FEEDBACK
We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com
JOIN ORACLE CLOUD CUSTOMER CONNECT
Please take a moment to join the Cloud Customer Connect forums for Financials Cloud. Oracle Cloud Customer Connect is a community gathering place for members to interact and collaborate on common goals and objectives. This is where you will find the latest release information, upcoming events, or answers to use-case questions. Joining takes just a few minutes. Join now!
https://cloud.oracle.com/community
Take a look at the Customer Connect Events to help you learn more about your upgrade, and some of the new features in R13. You can sign up to attend Upcoming Events or watch replays of existing events.
Action Required to Enable Feature |
|||||
---|---|---|---|---|---|
Feature |
None (Automatically Available) |
Enable via Opt In UI Only |
Enable via Opt In UI Plus Additional Steps |
Not Enabled via Opt In UI but Setup Required |
Issue Service Request |
Receivables Invoice Delivery in Open Applications Group Integration Specification 10.1 XML Format |
|||||
Subledger Accounting - Journals Real Time Subject Area Enhancements |
|||||
Configurable Email Notifications
Oracle Financials Cloud now uses Oracle Business Intelligence Publisher for configurable email notifications. The email templates are optimized for mobile devices and are easily configurable. Choose from a comprehensive list of attributes to modify the email notifications according to your requirements. You can change both layout and content. This includes adding images, changing colors and styling, adding or removing attributes, or modifying text.
Support for the following notifications has been added in the current update:
Product |
Feature |
Notification |
Intercompany |
Configurable Intercompany Email Notifications |
Intercompany Transaction Approval Notification Intercompany Enter Receiver Distribution Notification |
Payables |
Configurable Payables Email Notifications |
Invoice Account Coding Notification |
Expenses |
Configurable Expenses Notifications |
Expense Audit and Receipt Management Notifications
Cash Advance Notifications
|
Steps to Enable
You must enable the feature using the Opt In page in Functional Setup Manager. This feature is not enabled by default.
To enable the feature, complete these steps:
- Navigate to the Setup and Maintenance work area.
- Select Financials from the Setup choice list. .
- Click the Change Feature Opt In link.
- On the Opt In: Financials page, click the Features icon for the product that you want to enable for the Configurable Email Notifications feature (Expenses, Payables or Intercompany).
- On the Edit Features page, select the Enable option for the notification that you want to enable.
- Click Done.
The feature is now enabled.
Tips And Considerations
- Use the predefined email templates with no additional changes or modify them according to your business requirements.
- Preview your changed email templates before publishing.
- Revert to the standard approval notifications at any time by disabling the feature using the Opt In page in Functional Setup Manager.
Key Resources
- Financials Configurable Email Notifications: Overview
- Configurable Email Notifications: Implementation Considerations (Doc ID 2215570.1) on My Oracle Support at https://support.oracle.com
Fixed Assets Capitalization Thresholds
You can enforce the capitalization threshold limit automatically for all of your asset additions. Optionally specify the low value threshold limit for each asset category so that these low value assets are fully reserved using the specified method and life.
The following screenshot illustrates the feature and its benefits.
Steps to Enable
Complete the basic setup of your asset book from the Manage Asset Books task and complete your basic category setup for this book from the Manage Asset Categories task. Then, add your book name to the ORA_FA_ALLOW_CAP_THRESHOLD lookup values in the Manage Fixed Asset Lookups task.
After you load your assets from the Mass Additions File-Based Data Import template to the corporate book, the Prepare Asset Transaction data process determines whether the assets should be expensed or capitalized based upon the specified threshold values. For a tax book, the Mass Copy process evaluates the capitalization and low value thresholds. You can view the capitalization threshold evaluation results from the Edit Source Lines, Prepare Source Lines, or Add Asset pages.
Streamline the reconciliation and reporting of your lease liability balances using the Asset Lease Liability Report.
The following screenshot illustrates the feature and its benefits.
Steps to Enable
From the Manage Asset Books page, open your book. Ensure that the Asset Leases check box is enabled.
Reporting Currency Conversion for Asset Leases
Report your leases in any currency other than your ledger currency. Using reporting currencies, you can maintain and report lease accounting and balances in more than one currency. Convert right-of-use asset balances at historical rates and lease liability balances at the current rate. Load your asset lease terminations or reassessments in bulk using the supplied File-based data import templates.
The following screenshot illustrates the feature and its benefits.
You can view the lease amounts and accounting entries for primary and reporting currencies.
You can load your lease terminations or reassessments in bulk using the supplied File-based data import templates using the enhanced Import Asset Leases process.
Steps to Enable
From the Manage Asset Books page create a corporate book with a primary ledger that has reporting currencies. Ensure that the book’s Asset Leases check box is enabled.
Control Display of Fields by Expense Type
You can more easily control the information gathered for each expense type on the Create Expense Item page. You can enable fields, such as Description, Merchant Name, Expense Location, and Number of Days, on the Manage Expense Report Templates page for the expense template and on the Create Expense Type page for each expense type. The settings for the expense type override the settings for the expense template. The following settings are available for each field.
- Hidden. The field is not displayed.
- Optional. The field is displayed when the expense type is selected, but you are not required to enter data.
- Required. The field is displayed when the expense type is selected and you are required to enter data.
The fields available for configuration vary by expense category. The Number of Days field is available only for Accommodation, Car Rental, and Miscellaneous expense categories.The application does not allow you to control field display if an associated expense policy requires any of these fields for policy enforcement. The field display behavior at the expense type level overrides all other configurations, such as fields controlled by profile options, the Manage Tax Fields page, and the Manage Expense Fields by Category page.
Steps to Enable
To enable or disable fields by expense type in an existing template, you must complete these steps:
- In the Setup and Maintenance work area, navigate to the Manage Expense Report Templates task.
- On the Manage Expense Report Templates page, select the expense template and click the Edit icon.
- Click the Expense Fields tab.
- Select the expense field behavior for the Description, Merchant Name, Expense Location, and Number of Days fields. The behavior selected here applies to all expense types unless you define behavior for a specific expense type.
- To define expense field behavior for an expense type, click the Expense Types tab.
- Select the expense type and click the Edit icon.
- Click the Expense Fields tab.
- Select the expense field behavior.
- Click Save the details.
NOTE: The filed behavior defined for an expense type overrides the field behavior defined at the expense template.
Tips And Considerations
If you are already using Cloud Expenses, the Description, Merchant Name, Expense Location, and Number of Days fields are displayed by default. You can then disable the expense fields that are not applicable for the expense type or for the template.
Role Information
You must have one of the following roles to enable expense fields by expense type:
- Application Implementation Consultant
- Financial Administrator
- Expense Manager
Shortcuts for Attendee Selection
We have made it easier for you to add attendees to your expense items on the Create Expense Item page. Four new shortcuts are available for faster attendee selection as follows.
- Direct Reports. Allows you to select attendees from the list of people reporting to you. This short cut is available only for employee attendee selection.
- Favorites. Allows you to select attendees from a list of favorites. You can mark any attendee as a favorite when entering an expense item.
- Recent Attendees. Allows you to select any previously selected attendees. The Recent Attendees list shows attendees selected in reports during the past six months. The list conveniently filters to employees when you enter employee attendees and it filters to nonemployees when you enter nonemployee attendees.
- Others. Allows you to search for any employees and any nonemployees who are designated as attendees. You can select multiple attendees from the search results.
Steps to Enable
No steps are required to enable this feature.
Accounting Automation streamlines and automates your end-to-end accounting and transaction processes, including Import Daily Rates, Create Accounting, Import Journals and Posting, greatly reducing manual work and time lags in your business operations. The data flows through all of the required processing steps with no user intervention, while making it easy to involve the right people at the right time to resolve exceptions. This ensures the continuous availability of the most accurate and up-to-date financial information.
Users are notified of exceptions and guided through how to resolve them to allow accounting to be completed. Additional users can optionally be notified of errors generated during the transaction accounting process.
Main Components of the Accounting Automation Feature:
- When you opt in, the Manage Accounting Automation setup page automatically opens where you can complete the setup.
- Email notification and report for the default user: Summary of processed data, errors and pending approvals to the specified default user.
- Email notification and report for the other specified users: Summary of errors and pending approvals to the specified users.
Steps to Enable
Use the Manage Accounting Automation setup page to enable and schedule the accounting automation.
You can also optionally specify the users to be notified of the errors generated while processing accounting transactions, based on the ledger or ledger set, and the category that an error falls under.
Step 1: Enable Automation
Step 2: Specify the Scheduled Submission Time
Step 3: Specify the Default User to Notify
Step 4: Optionally specify additional users to be notified of the errors found while processing accounting transactions, based on the ledger or ledger set, and the category that an error falls under.
Tips And Considerations
- When you enable Accounting Automation, transaction data for all of the ledgers (primary, secondary, and journal and subledger level reporting currencies) in the system is processed.
- Accounting Automation should not be enabled if you are using or plan to use segment value security.
- Approvals are not automatically submitted for any type of journal batch. If a journal batch needs approval, it must be submitted for approval manually or through the AutoPost process.
- Accounting Automation should not be enabled if you are using or plan to use any form of coexistence.
- Accounting will only be generated for events with an accounting date of system date or earlier. Future-dated accounting will not be generated automatically.
- Incomplete journal batches will not be picked up by Accounting Automation for posting.
- Accounting Automation will not pick up transactions that were created on a date before Automation was enabled, unless the transaction has an accounting date the same as or after the date that Automation was enabled.
- If you use Oracle Receivables and plan to enable Accounting Automation, you must schedule to run the Create Receivables Accounting process daily, before the Accounting Automation scheduled time.
Role Information
The Accounting Automation feature is secured by the Manage Accounting Automation Setup and Run Accounting Automation Program privileges. The new accounting automation privileges are assigned to the General Accounting Functional Administration Duty, which rolls up to the Financial Application Administrator and Application Implementation Consultant job roles.
Invoice Routing for Account Coding
The Invoice Routing for Account Coding feature enables customers to route invoices to business users for entering accounting information. Generally, all unmatched invoices need the accounting information entered to complete it. The Payables clerk usually has to interact with multiple users to get this information. The information is internal, can differ from invoice to invoice, and depends on the expenditure incurred. In most cases, the business users that have incurred the expenditure can provide the details for the accounting information. This feature provides customers an efficient way to route unmatched invoices to these business users to provide the accounting information.
Users are notified about the assignment through email and workflow notifications. Accounting information can be entered directly in the workflow notification. Upon completion of the assigned task, the accounting information is updated on the invoice and it is ready for the next step in processing such as approval or payment.
Users on the invoice routing list can only access those invoices assigned to them. They can perform additional actions such as, request additional information, reassign to other users, or return the assignment.
Business validations are performed during the entry of the accounting information. User are alerted when there is any excess or shortfall of the accounting information.
Steps to Enable
- Enable the feature from the Functional Setup Manager Feature Opt In page. The steps are:
- Go to the Setup and Maintenance work area.
- Select Financials in the drop-down list at the top of the page.
- Click Change Feature Opt In.
- On the Opt In: Financials page, click the Features icon for Payables. On the Edit Features: Payables page, select the enable check box for ‘Invoice Routing for Account Coding’ feature
- Click Done to return to the Setup: Financials page.
- The feature must to be enable at the business unit level in Manage Invoice Options. The steps are:
- Go to the Setup and Maintenance work area.
- Select Financials in the drop-down list at the top of the page.
- Select Payables in the Functional Area.
- Select Manage Invoice Options; select the scope “Business Unit”.
- Select the “Enable invoice account coding workflow” option in the “Invoice Entry” region.
- Click on Save and Close.
Tips And Considerations
- The Account Coding workflow task is seeded with the assignment rules that assigns all invoices to users having the AP Supervisor role. The assignment rule can be modified based on business needs.
- The Invoice Account Coding Assignment rules can be defined based on the invoice attributes.
- The Configurable Payable Email Notification feature is available for the Account Coding workflow, however, this feature is not enabled by default. This can be enabled by using Opt In for the feature: ‘Configurable Payable Email Notification’.
Additional Attributes for Credit Checking Service
You can now use descriptive flexfields to pass additional values to credit case folders created as the result of credit checking failure. Pass additional information related to the source transaction requesting the credit check, such as Contract Start Date, Contract Billing Frequency, and Contract Invoicing Rule. The descriptive flexfields are displayed in the Additional Information section of the Edit and View Credit Case Folder pages. You can edit these additional attribute values before the case folder is approved. Once the case folder is approved, these values are rendered read-only.
Steps to Enable
No steps are required to enable this feature.
Tips And Considerations
Define the credit case folder descriptive flexfields to match the values passed through the Credit Checking Service. If the data types for the attributes do not match, or if the descriptive flexfields are not defined, these additional attributes will not appear in case folders created as a result of a credit check failure.
Role Information
No new role access is needed to use this feature.
Order Level Credit Recommendation
Credit Management now supports order level credit recommendation. This feature contains the following components:
- Creation of a case folder at the order level.
- Enhanced Credit Case Folder pages with the request type Credit Checking Failure.
- New public business event when a case folder is closed.
- Creation of case folder at order level
If a new order is submitted for a customer account that has an active case folder with the request type Credit Checking Failure for a different source transaction, the Credit Checking Service now creates a new case folder for the customer account with the request type Credit Checking Failure and the new source transaction information. You can view all the active case folders for a customer account in the Credit Reviews work area.
- Enhanced Credit Case Folder pages with the request type Credit Checking Failure
You can filter case folders by Source Transaction Number in the Credit Reviews work area. The Source Transaction Number column is hidden by default. You can view additional source information for a case folder using the Credit Case Folder page:
- The Source Transaction number is part of the page title, for example, “Credit Case Folder 2007 (Source Transaction 58910)”.
- Use the Credit Checking Details window to view details of a credit request, including the customer and customer account on the source document, and whether a case folder is created from a preauthorization request.
Two new recommendation types are introduced for case folders with the request type Credit Checking Failure:
- Approve Source Transaction Credit Request: Upon approval of the case folder containing this recommendation, the application uses the attributes passed using the Credit Checking Service to create a credit authorization, bypassing the available credit amount check or order amount limit check.
- Decline Source Transaction Credit Request: This recommendation indicates that the credit request from the source transaction is declined. No credit authorization is created upon case folder approval.
- New public business event when a case folder is closed
When a case folder status is updated to Closed, Receivables publishes a public Credit Case Folder Closure business event. When all recommendations in a case folder have been successfully implemented, the case folder status is automatically updated from Approved to Closed. A credit analyst can also manually close a case folder using the Close action. The public Credit Case Folder Closure business event contains the following information:
- Key attributes of the case folder, including case folder number, status, credit analyst, creation date, and last updated date.
- Key attribute values that the calling party has passed using the latest credit checking service call, including customer, customer account, requested authorization amount, source document information.
- Key attributes of the new credit authorization record (if Approve Source Transaction Credit Request is one of the recommendations), including credit authorization number, authorization expiration date, and authorization amount.
- List of all approved recommendations (if the case folder is approved), including the new values for credit limit and credit classification.
Steps to Enable
No steps are required to enable this feature.
Role Information
No new role access is needed to use this feature.
Receivables Invoice Delivery in Open Applications Group Integration Specification 10.1 XML Format
Use this feature to generate and deliver Receivables XML invoices in the latest Open Applications Group Integration Specification (OAGIS) 10.1 format using the Collaboration Messaging Framework (CMK).
Receivables XML invoicing now supports embedding invoice header attachments in the XML payload. You can receive inbound acknowledgements in OAGIS 10.1 Confirm Business Object Document (CBOD) format from your trading partner.
The new OAGIS 10.1 invoice format allows you to include unlimited additional user-defined attributes in the standard user area of the XML message.
Use the Customer Import FBDI to import Trading Partner and Customer Account Collaboration configuration into CMK, as part of Customer Account Profile import.
Steps to Enable
Use the Feature Opt-in page in Functional Setup Manager to enable the Receivables Invoice Delivery in Open Applications Group Integration Specification 10.1 XML Format feature.
NOTE: If you are using the existing Receivables XML Invoicing feature through Service Oriented Architecture (SOA) business-to-business (B2B) gateway and decide to opt-in to this new feature, you will need to re-do the Trading Partner setup in Fusion CMK.
SET UP YOUR RECEIVABLES CUSTOMER ACCOUNT PROFILE
In the Edit Account Profile page: Invoicing section, perform these two tasks:
- Set the Preferred Delivery Method field to XML.
- Select the Enable for XML Invoicing check boxes for all transaction classes that you want to enable for XML delivery: Invoice, Debit Memo, Chargeback, Credit Memo.
You can also perform this setup using the Customer Import spreadsheet.
SET UP THE COLLABORATION MESSAGING FRAMEWORK (CMK)
Complete the following required setup in Fusion CMK both to generate and deliver XML invoices and to receive inbound CBOD acknowledgement from your customer.
- Use the Manage Collaboration Messaging Configuration task in the Setup and Maintenance work area to enable the Order To Cash Collaboration Business Process.
- Define Service Providers for XML invoice delivery.
- Use the Manage Collaboration Messaging Service Providers task in the Setup and Maintenance work area to define your Service Providers.
- In the Edit Collaboration Messaging Service Provider page, define the Delivery Methods, Outbound Collaboration Message, and Inbound Collaboration Message.
- Outbound Collaboration Message to be added is OAGIS_10.1_PROCESS_INVOICE_COLLAB_MSG_OUT.
- Inbound Collaboration Message to be added is OAGIS_10.1_CONFIRM_BOB_COLLAB_MSG_IN.
- Associate the inbound CBOD message to the invoice outbound message as shown below.
- Define your Trading Partners, one for each Customer Account.
- Use the Manage B2B Trading Partners task in the Collaboration Messaging work area to define Trading Partners.
- In the Edit Trading Partners page, associate the outbound invoice (PROCESS_INVOICE_OUT) and inbound CBOD (CONFIRM_MESSAGE_RECEIPT_IN) collaboration documents to the Trading Partner.
- Associate the Service Provider and Trading Partner created in the previous steps to the Customer Account from Manage Customer Account Collaboration Configuration task in the Collaboration Messaging work area. Search for an existing Customer Account and click the Edit Collaboration Configuration button.
NOTE: It is not required to explicitly associate inbound CBOD collaboration document to the Customer Account as the association is already done at the Service Provider level.
This setup in Fusion CMK is required in order to generate and deliver XML invoices and to receive inbound CBOD acknowledgement from your customer.
NOTE: Fusion CMK supports delivering XML invoices directly to Trading Partners without a Service Provider. To enable this feature, use the predefined Service Provider 'None' and set up your Trading Partners.
SETUP FOR INCLUDING ATTACHMENTS WITH XML INVOICE DELIVERY
To include invoice header attachments in the XML payload, complete these steps:
-
In the Manage Attachment Categories page, create an Attachment Category to use exclusively for XML invoice attachments.
- In the Manage Receivables Profile Options page, search for the AR_BPA_PRINT_ATTACH_CATEGORY profile option. Add a profile value at Site level, and set this profile value to the Attachment Category Name defined in the previous step.
-
In the Attachments window of the Create Transaction page, select the Attachment Category that you associated with the AR_BPA_PRINT_ATTACH_CATEGORY profile option whenever you add an attachment to a transaction.
USING THE USERAREA EXTENSION ATTRIBUTES IN OAGIS 10.1 XML INVOICING
- The OAGIS 10.1 XML Invoice format lets you extend the XML invoice attributes using the Extension tag with the typecode 'UserArea'. For example, a customer may require a specific attribute on the XML invoice that is not mapped in the OAGIS 10.1 format and has no standard tag available in OAGIS 10.1. In cases like this, you can add the attribute to the UserArea extension of OAGIS 10.1.
- You can compute and load these extension attributes for Receivables transactions, according to your business needs, into the AR_EXTENSION_ATTRIBUTES table using the public API arp_util.insert_ar_extension_attributes.
- Receivables supports adding UserArea Extension attributes at the Invoice Header, Invoice Line and Invoice Tax Line levels in OAGIS 10.1 XML.
- The arp_util.insert_ar_extension_attributes API needs to be invoked by customizing the delivered Load Extension Attributes for XML Transactions Business Intelligence (BI) Publisher report.
- The Load Extension Attributes for XML Transactions BIP report process runs as a child process of the Generate and Transfer XML Transactions process. The extension attributes for Receivables transactions are computed and loaded into the table as part of the XML invoice creation process.
- This BIP report process, if customized to load extension attributes, generates an output containing any errors that occur during execution.
To customize the Load Extension Attributes for XML Transactions BIP report for loading extension attributes, complete these steps:
- Log into Oracle Fusion BI Publisher Enterprise using the xmlpserver URL for user with BI Administrator Role and navigate to Catalog.
- Customize the Load Extension Attributes for XML Transactions data model.
- Click on the gear icon and select 'Edit Data Set'.
- PL/SQL code should be written in the SQL Query section to compute and load extension attributes for transactions being processed. The arp_util.insert_ar_extension_attributes API needs to be invoked through this code.
NOTE: When using the extension attributes functionality, RA_CUSTOMER_TRX_ALL.READY_FOR_XML_DELIVERY flag needs to be set to Y for transactions once the extension attributes are inserted. The API to set this flag is arp_util.update_ready_for_xml_flag.
Signature of arp_util.insert_ar_extension_attributes API is:
PROCEDURE insert_ar_extension_attributes(extension_attr_tbl IN ARP_UTIL.EXTENSION_ATTR_TBL_TYPE, x_msg_count OUT NOCOPY NUMBER, x_msg_data OUT NOCOPY VARCHAR2, x_return_status OUT NOCOPY VARCHAR2);
EXTENSION_ATTR_TBL_TYPE is a PL/SQL table of EXTENSION_ATTRIBUTE_RECORD record type, and definition of EXTENSION_ATTRIBUTE_RECORD record type is as given below:
TYPE EXTENSION_ATTRIBUTE_RECORD IS RECORD(EXTN_ENTITY_ID AR_EXTENSION_ATTRIBUTES.EXTN_ENTITY_ID%type, ASSOCIATED_EXTN_ENTITY_ID1 AR_EXTENSION_ATTRIBUTES.ASSOCIATED_EXTN_ENTITY_ID1%type, ASSOCIATED_EXTN_ENTITY_ID2 AR_EXTENSION_ATTRIBUTES.ASSOCIATED_EXTN_ENTITY_ID2%type,ENTITY_TYPE_CODE AR_EXTENSION_ATTRIBUTES.ENTITY_TYPE_CODE%type,PROCESS_TYPE_CODE AR_EXTENSION_ATTRIBUTES.PROCESS_TYPE_CODE%type,ATTRIBUTE_NAME AR_EXTENSION_ATTRIBUTES.ATTRIBUTE_NAME%type,ATTRIBUTE_VALUE AR_EXTENSION_ATTRIBUTES.ATTRIBUTE_VALUE%type);
- The extension attributes once loaded can be updated using the arp_util.update_ar_extension_attributes API. ATTRIBUTE_NAME and ATTRIBUTE_VALUE columns in the AR_EXTENSION_ATTRIBUTES table can be updated using this API.
Signature of arp_util.update_ar_extension_attributes API is:
PROCEDURE update_ar_extension_attributes(extension_attr_tbl IN ARP_UTIL.EXT_ATTR_TBL_FR_UPDATE,x_msg_count OUT NOCOPY NUMBER, x_msg_data OUT NOCOPY VARCHAR2, x_return_status OUT NOCOPY VARCHAR2);
EXT_ATTR_TBL_FR_UPDATE IS PL/SQL table of EXT_ATTR_RECORD_FR_UPDATE record type, and definition of EXT_ATTR_RECORD_FR_UPDATE record type is as given below:
TYPE EXT_ATTR_RECORD_FR_UPDATE IS RECORD(EXTN_ENTITY_ID AR_EXTENSION_ATTRIBUTES.EXTN_ENTITY_ID%type, ENTITY_TYPE_CODE AR_EXTENSION_ATTRIBUTES.ENTITY_TYPE_CODE%type, PROCESS_TYPE_CODE AR_EXTENSION_ATTRIBUTES.PROCESS_TYPE_CODE%type, ATTRIBUTE_NAME AR_EXTENSION_ATTRIBUTES.ATTRIBUTE_NAME%type, NEW_ATTRIBUTE_NAME AR_EXTENSION_ATTRIBUTES.ATTRIBUTE_NAME%type, NEW_ATTRIBUTE_VALUE AR_EXTENSION_ATTRIBUTES.ATTRIBUTE_VALUE%type);
COLLABORATION MESSAGING SETUP USING THE CUSTOMER IMPORT FBDI
-
You can import both the CMK setup required for XML invoicing and Customer Account Profile information using the Customer Import FBDI template.
-
The prerequisite setup for importing CMK trading partners is to define Service Providers using the Manage Collaboration Messaging Service Providers task.
NOTE: You cannot use the predefined Service Provider None to import the trading partner setup using the Customer Import FBDI template.
- The new CMK setup related columns are hidden by default in the RA_CUSTOMER_PROFILES_INT_ALL sheet of the Customer Import template. To display these columns:
- Highlight the column XML Invoicing for Credit Memo and the next column.
- Right click to display the new CMK setup related columns:
- Enable Collaboration Messaging Configuration: If you want to import CMK setup for the Customer Account, set the value to Y in this column.
- Service Provider Name: Name of the B2B messaging service provider. This should have been defined in the system through Manage Collaboration Messaging Service Providers task.
- Trading Partner ID: User-defined code that identifies a customer account as a trading partner to receive XML transactions.
- Trading Partner ID Type: Labeling category for the identifier that you used to define the trading partner in the PARTNER_ID attribute. Valid values are: DUNS, Generic (typically the customer account number), GLN, MISC, PHONE, TAXID, Name (typically the customer account name).
- Receivables Outbound XML Transaction Document: Option that indicates whether the trading partner is enabled to receive Receivables transactions in XML format.
- Receivables Inbound Confirmation Document: Option that indicates whether the trading partner is enabled to send back a confirmation BOD after receiving an XML transaction.
Tips And Considerations
-
After a run of the Generate and Transfer XML Transactions process, use the Manage Transactions task in the Receivables Billing work area to view the XML Delivery status.
-
Use the Manage Collaboration Messaging History page in the Collaboration Messaging work area to verify successful processing of transactions with an XML payload.
- Review any errors during XML invoice generation and delivery, using the Manage Undelivered Collaboration Messages and Manage Failed Collaboration Messages pages in the Collaboration Messaging work area.
-
For transactions with the XML Delivery Status 'Processing Error', the error details are displayed in the Manage Undelivered Collaboration Messages page. You can either reprocess these transactions in the Manage Undelivered Collaboration Messages page or set them to the 'Delivery Failed' status by cancelling the transactions.
-
For transactions with the XML Delivery Status 'Delivery Failed', the error details are displayed in the Manage Failed Collaboration Messages page. You can reprocess with another run of the Generate and Transfer XML Transactions process. Set the Transactions Included parameter to Failed Transactions.
-
-
By default, the Inbound CBOD from the Customer must have an acknowledgement code of Success, Error, or Other to appear in the XML Delivery Status attribute in the Manage Transactions page. If customers want to use their own status codes, you can map the customer's codes to one of the three statuses using the Manage Confirmation Codes page from the Manage B2B Trading Partners task in the Collaboration Messaging work area.
Key Resources
- Refer to the following topics in the Collaboration Messaging Framework documentation for further information on: How to use Collaboration Messaging; how to reprocess messages in error; and how to process outbound and inbound messages using CMK:
- Using Collaboration Messaging
- Reprocessing Undelivered Messages
- Process Outbound Collaboration Messages
- Process Inbound Collaboration Messages
Role Information
Users with the Accounts Receivable Manager or Accounts Receivable Specialist role can access the Collaboration Messaging work area tasks, and import CMK setup using the Customer Import FBDI process. Users with access to Receivables Administration Duty will have access to the Manage Collaboration Messaging Configuration and Manage Collaboration Messaging Service Providers tasks under the Setup and Maintenance work area.
Store Printed Receivables Transactions as Attachments
Use the Store Printed Receivables Transactions as Attachment feature to retain and access original printed or emailed transactions as an attachment. When this feature is opted in, the Upload Printed Receivables Transactions background process, which runs as a post process to the Print Receivables Transactions process, ensures that printed and emailed transaction copies are stored as an attachment on the transaction. You can access the original printed transaction as an attachment in the Review Transaction page.
Steps to Enable
The Store Printed Receivables Transactions as Attachments feature is enabled by default in the Functional Setup Manager feature opt-in page.
Additional setup is required to enable this feature. Follow these steps:
- Navigate to the Setup and Maintenance work area.
- Search for the setup task Manage Receivables Lookups.
- In the Manage Receivables Lookups page, search for the AR_FEATURES lookup type. (If the lookup type AR_FEATURES does not exist, create it first using the setup task Manage Standard Lookups.)
- Add a lookup code AR_STORE_PRINTED_TRANSACTIONS to the AR_FEATURES lookup type and save the changes.
Tips And Considerations
- Printed and emailed transaction copies are stored as attachments on the transaction header as a post process to the Print Receivables Transactions background process.
- Use the Review Transaction page to access a copy of a printed or emailed transaction:
Web Service to Create Reference Accounts for Customers
Use the new Customer Bill-to Site Reference Accounts Service Data Object (SDO) in the Customer Profile web service to create reference account combinations for a customer bill-to site. The reference account combinations that you create are used to derive account combinations for distributions on Receivables transactions, when AutoAccounting is set up to derive account combinations based on Bill-to Site.
Steps to Enable
There are no steps to enable this feature. This is a new Web service operation.
Tips And Considerations
The name of the operation in the Customer Profile Web Service to create reference account combinations for a customer bill-to site is createReferenceAccountsForBillToSite.
SDO Name: Customer Bill-to Site Reference Accounts
SDO Description: Service to create bill-to site reference accounts for customer accounts. This setup is used for deriving account combinations for distributions on Receivables transactions, when AutoAccounting is set up to derive account combinations based on Bill-to Site.
Key Resources
- Refer to the SOAP Web Services for Oracle Financials Cloud documentation for details of this service: https://docs.oracle.com/en/cloud/saas/financials/r13-update17d/oeswf/Receivables-Web-Services-Overview.html
- Refer to the Usage Notes for Receivables Customer Profile Service in the Oracle ERP Cloud Integration for Credit to Cash section of the SOAP Web Services documentation: http://www.oracle.com/webfolder/technetwork/docs/fbdi-r13-17d/fbdi/supportingdocs/fin-CustomerProfileServiceAM.pdf
Role Information
- Users with Accounts Receivable Manager or Accounts Receivable Specialist role can access this service.
Transactional Business Intelligence for Financials
Replace Business Unit Views for Improved Performance
To improve query performance in Financial subject areas, Business Unit views were replaced with more optimized ones.
Steps to Enable
No steps are required to enable this feature.
Subledger Accounting - Journals Real Time Subject Area Enhancements
The Payables Transaction Details folder in the Subledger Accounting - Journals Real Time subject area has been synchronized with similar folders in the Payables subject areas, for better usability: new columns added to Header Information, Reference Information and Tax Information folders.
Steps to Enable
No steps are required to enable this feature.
Regional and Country-Specific Features
Online VAT Reporting for Spain
Effective January 1, 2017, Spanish companies with an annual turnover above 6 million Euros must report received and issued transactions in a predefined electronic format. From July 1, 2017 transactions must be reported within four days of reception or issuance date. Transactions created in the first semester must be reported by the end of the year.
The Online VAT Reporting for Spain solution provides the following components to support this legal requirement:
- Additional fields, which are specific to Online VAT Reporting for Spain, must contain the mandatory reporting information.
- Process, which extracts transactional details and creates an xml file in a predefined format.
- Process that updates the transaction reporting status based on the confirmation message received from the Spanish Tax Authority.
Online VAT Register Reporting for Spain process creates xml file for the following registers:
- Issued Invoices Register
- Received Invoices Register
- Selected Intra-EU Transactions Register
- Payments Register
- Receipt Collections Register
Online VAT Register Reporting Confirmation for Spain updates transactions with the response message details.
Annual Online VAT Register Reporting for Spain process creates an xml file for the following register:
- Cash Collection Register
Annual Online VAT Response for Spain updates customer accounts and sites that were reported to the Tax Authority with the corresponding confirmation information.
Annual Online VAT Investment Goods Register Reporting for Spain process creates xml file for the following register:
- Investment Goods Register
Steps to Enable
No steps are required to enable this feature.
Key Resources
- Online VAT Reporting for Spain Topical Essay
Role Information
- EMEA Financial Reporting duty role
---
Copyright © 2018, Oracle and/or its affiliates. All rights reserved.
This document is provided for information purposes only, and the contents hereof are subject to change without notice.This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.