Oracle Fusion Financials Cash Management

Release 9
Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Key Product Features

Fusion Financials Cash Management
Bank Statement Processing
Load
Load and
and import
import electronic
electronic bank
bank statements:
statements:
BAI2
BAI2
SWIFT
SWIFT
FINSTA
FINSTA
ISO20022
ISO20022

Parse
Parse Rule
Rule Sets
Sets can
can parse
parse information
information on
on the
the
bank
bank statement
statement into
into named
named attributes
attributes which
which can
can
be
be used
used for
for reconciliation
reconciliation
Support
Support for
for standard
standard transmission
transmission protocols
protocols to
to
load
load electronic
electronic bank
bank statements
statements

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Bank Statement Reconciliation

Flexible
Flexible reconciliation
reconciliation rules
rules to
to automatically
automatically
match
match bank
bank statement
statement lines
lines with
with transactions
transactions
Configurable
Configurable rule
rule sets
sets increase
increase the
the automatic
automatic
reconcoliation
match
rate
reconcoliation match rate
Configurable
Configurable date
date and
and amount
amount tolerance
tolerance rules
rules
apply
apply to
to both
both automatic
automatic and
and manual
manual
reconciliation
reconciliation
External
External cash
cash transactions
transactions such
such as
as manual
manual
entries,
entries, imported
imported transactions,
transactions, amount
amount
variances,
variances, are
are automatically
automatically created
created and
and
reconciled
reconciled using
using the
the Bank
Bank Statement
Statement
Transaction
Transaction Creation
Creation program.
program.

Key Product Features

Fusion Financials Cash Management
Productivity
Role-based
Role-based dashboards
dashboards
and
and work
work areas
areas that:
that:

Proactively
Proactively monitor
monitor
transactions
transactions and
and push
push
work
work to
to users
users

Allow
Allow collaboration
collaboration with
with
participants
participants

Provide
Provide easy
easy access
access to
to
transaction
transaction screens
screens and
and
reports
reports

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Reporting and Analysis

Cash
Cash to
to General
General Ledger
Ledger
Reconciliation
Reconciliation Report
Report
Bank
Bank Statement
Statement Report
Report
OTBI
OTBI Bank
Bank Statement
Statement Analysis
Analysis
Report
Report

Setup
Centralized
Centralized setup
setup
across
Financials,
across Financials,
Projects
Projects and
and
Supply
Supply Chain
Chain
Date-effective
Date-effective rules
rules

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.

Copyright 2013, Oracle and/or its 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.

Copyright 2013, Oracle and/or its 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.

Copyright 2013, Oracle and/or its 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.

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Key Setup Tasks: Required Setups in Fusion Payments

for Bank Statement Processing
Required 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.
Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Implementation Considerations
Bank Accounts
1.
1. Use
Use defining
defining attributes,
attributes, such
such as
as
bank,
bank, currency,
currency, and
and account
account use
use
in
in the
the bank
bank account
account name
name to
to
uniquely
uniquely identify
identify itit
2.
2. Consider
Consider assigning
assigning aa unique
unique GL
GL
cash
cash account
account to
to each
each bank
bank
account
account to
to record
record all
all cash
cash
transactions
transactions to
to facilitate
facilitate book
book to
to
bank
bank reconciliation
reconciliation

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Bank Statement Transmission Setup

1.
1. Define
Define aa transmission
transmission configuration
configuration to
to specify
specify the
the
parameters
parameters for
for transmitting
transmitting aa bank
bank statement
statement file
file
2.
2. Supports
Supports one
one format
format for
for each
each of
of the
the 44 seeded
seeded formats.
formats.
IfIf you
you need
need to
to modify
modify aa seeded
seeded format,
format, make
make aa copy
copy
and
and then
then make
make changes.
changes.
3.
3. The
The delivered
delivered code
code map
map groups
groups provide
provide only
only very
very basic
basic
mappings.
mappings. They
They can
can be
be extended
extended as
as required
required and
and new
new
code
code map
map groups
groups can
can also
also be
be created
created
4.
4. Transaction
Transaction types
types can
can be
be mapped
mapped to
to statement
statement lines
lines
through
through the
the transaction
transaction code
code setup
setup and
and the
the system
system
transactions
transactions through
through the
the cash
cash transaction
transaction type
type mapping
mapping
setup
setup
5.
5. Transaction
Transaction codes
codes must
must be
be defined
defined for
for both
both manual
manual and
and
electronic
electronic bank
bank statement
statement processing
processing

Implementation Considerations
Bank Statement Reconciliation
1.
1. When
When creating
creating rule
rule sets
sets for
for automatic
automatic reconciliation,
reconciliation, rules
rules should
should be
be ordered
ordered to
to
achieve
achieve aa greater
greater reconciliation
reconciliation success
success rate.
rate.
2.
2. Consider
Consider changing
changing the
the sequence
sequence number
number depending
depending on
on how
how accurately
accurately the
the
given
given rule
rule is
is likely
likely to
to reconcile
reconcile against
against the
the correct
correct transactions.
transactions.
3.
3. ItIt is
is recommended
recommended that
that ifif all
all other
other criteria
criteria in
in aa rule
rule is
is the
the same
same that
that one
one to
to one
one
match
match type
type rules
rules be
be sequenced
sequenced above
above rules
rules of
of other
other match
match types
types

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Other Fusion Documentation

http://docs.oracle.com/cd/E48434_01/nav/financials.htm

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Other Fusion Documentation

https://fusionhelp.oracle.com/

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Fusion Cloud Documentation

https://docs.oracle.com/cloud

Copyright 2013, Oracle and/or its affiliates. All rights reserved.