10- implementing cashmanagement

13
Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved. Oracle Fusion Financials Cash Management Release 9

Upload: pummysharma

Post on 10-Apr-2016

320 views

Category:

Documents


16 download

DESCRIPTION

Fusion

TRANSCRIPT

Page 1: 10- Implementing CashManagement

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

Oracle Fusion Financials Cash ManagementRelease 9

Page 2: 10- Implementing CashManagement

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

Key Product FeaturesFusion Financials Cash Management

• Load and import electronic bank statements:• BAI2 • SWIFT• FINSTA • ISO20022

• Parse Rule Sets can parse information on the bank statement into named attributes which can be used for reconciliation

• Support for standard transmission protocols to load electronic bank statements

Bank Statement Processing• Flexible reconciliation rules to automatically

match bank statement lines with transactions• Configurable rule sets increase the automatic

reconcoliation match rate• Configurable date and amount tolerance rules

apply to both automatic and manual reconciliation

• External cash transactions such as manual entries, imported transactions, amount variances, are automatically created and reconciled using the Bank Statement Transaction Creation program.

Bank Statement Reconciliation

Page 3: 10- Implementing CashManagement

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

Key Product FeaturesFusion Financials Cash Management

• Cash to General Ledger Reconciliation Report

• Bank Statement Report • OTBI – Bank Statement Analysis

Report

Reporting and Analysis• Role-based dashboards

and work areas that:Proactively monitor

transactions and push work to users

Allow collaboration with participants

Provide easy access to transaction screens and reports

Productivity• Centralized setup

across Financials, Projects and Supply Chain

• Date-effective rules

Setup

Page 4: 10- Implementing CashManagement

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

Key Setup Tasks: Financials Offering

Setup and Maintenance > All Tasks > Search region, enter Financials in the Name field > Search button > Expand Financials > Expand Define Receivables Configuration. The Define Cash Management and Banking Configuration folder contains the set up tasks for Cash Management.

Page 5: 10- Implementing CashManagement

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

Key Setup Tasks: Financials Offering• General setups including configuring the profile options, lookups, descriptive flexfields

and other common components for Cash Management. • Set Up Banks, Branches, and Accounts*: Create and edit banks, branches,

and accounts used throughout the applications. • Define Bank Statement Processing and Reconciliation*: Configure setup for

bank statement processing and reconciling bank statements. • (Optional) Modify Subledger Accounting Rules for Cash Management if Using

Custom Transaction Types or 3rd Party Systems: Configure application, source, and accounting methods.

Page 6: 10- Implementing CashManagement

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

Key Setup Tasks: Financials Offering

• Assign for Reconciliation the following: Manual Reconciliation Tolerance Rule, Exchange Rate, Automatic Reconciliation Rule Set, and the Reconciliation Start Date.

• Assign for Bank Statement Processing the following: Parsing Rule Set and Transaction Creation Rules.

Page 7: 10- Implementing CashManagement

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

Key Setup Tasks: Define Bank Statement Processing • In order to load electronic bank statements or use Cash

Management's Autoreconciliation feature, you must define the following processing and reconciliation rules: – Manage Bank Statement Transaction Codes that each bank uses to identify different types of

transactions on its statements. – Manage Parse Rule Sets which are used to transform data during the bank statement import

process. – Manage Bank Statement Transaction Creation Rules which allow you to configure rules to

create transactions from unreconciled statement lines to record items such as bank charges, interest, or other miscellaneous items.

• NOTE: These setups are defined independent of the bank accounts. Parse rules and Bank Statement Transaction Creations rules need to be assigned to the bank accounts that these rules apply.

Page 8: 10- Implementing CashManagement

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

Key Setup Tasks: Required Setups in Fusion Payments for Bank Statement ProcessingRequired setups in Fusion Payments for Bank Statement Processing: – Manage Transmission Configurations – Manage Formats – Manage Code Map Groups

• Payment Setup Details – Transmission Configuration: Define a transmission configuration to specify the parameters

for transmitting a bank statement file. – Formats: One format for each of the bank statement formats supported is delivered with Cash

Management. If a new format needs to be added, make a copy of a seeded format.– Code Map Groups: The bank statement processing program uses Code Map Groups for

mapping the balance codes and transaction codes that are reported on the external data file to the ones that are defined internally in Cash Management. The delivered code map groups provide only very basic mappings. They can be extended as required and new code map groups can also be created.

Page 9: 10- Implementing CashManagement

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

Implementation Considerations

1. Use defining attributes, such as bank, currency, and account use in the bank account name to uniquely identify it

2. Consider assigning a unique GL cash account to each bank account to record all cash transactions to facilitate book to bank reconciliation

Bank Accounts1. Define a transmission configuration to specify the

parameters for transmitting a bank statement file 2. Supports one format for each of the 4 seeded formats.

If you need to modify a seeded format, make a copy and then make changes.

3. The delivered code map groups provide only very basic mappings. They can be extended as required and new code map groups can also be created

4. Transaction types can be mapped to statement lines through the transaction code setup and the system transactions through the cash transaction type mapping setup

5. Transaction codes must be defined for both manual and electronic bank statement processing

Bank Statement Transmission Setup

Page 10: 10- Implementing CashManagement

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

Implementation Considerations

1. When creating rule sets for automatic reconciliation, rules should be ordered to achieve a greater reconciliation success rate.

2. Consider changing the sequence number depending on how accurately the given rule is likely to reconcile against the correct transactions.

3. It is recommended that if all other criteria in a rule is the same that one to one match type rules be sequenced above rules of other match types

Bank Statement Reconciliation

Page 11: 10- Implementing CashManagement

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

Other Fusion Documentation• http://docs.oracle.com/cd/E48434_01/nav/financials.htm

Page 13: 10- Implementing CashManagement

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

Fusion Cloud Documentation• https://docs.oracle.com/cloud